CaptAPI Account

GET /v1/account/daily-usage

Daily Usage API

Day-by-day credit usage for spend monitoring (0 credits).

0 credits per request

Try in Playground Get your API key — free Read the docs

TL;DR

Day-by-day credit usage for spend monitoring (0 credits). The Daily Usage API (CaptAPI Account) is a single authenticated GET request to /v1/account/daily-usage that responds with clean JSON and costs 0 credits. Account endpoints are always live (never cached). Start with 100 free credits — no credit card.

What is the Daily Usage API?

Daily credit usage buckets for your Captapi key — date, requests, creditsUsed, success/fail counts. Live account data — not cached. Free.

What you get

Live data for your Captapi API key (never cached)
No credit charge for account endpoints
Clean JSON ready for dashboards and low-balance alerts
Useful for monitoring usage and spend

Try it

Open in Playground

Fill in the parameters below and copy a ready-to-run request, or open the live Playground to run it against your account (no API key paste).

Parameters

daysoptionalintegerNumber of days to include (default 30, max 365).

API keyoptionalPaste your key to get a ready-to-run snippet. It stays in your browser.Sign in to run live

curl "https://api.captapi.com/v1/account/daily-usage?days=value" \
  -H "Authorization: Bearer capt_live_..."
# or: -H "x-api-key: capt_live_..."

Edit the parameters and the code updates instantly. Switch languages and hit copy.

Example response

{
  "success": true,
  "data": {
    "days": 7,
    "totalRequests": 251,
    "totalCreditsUsed": 498,
    "usage": [
      {
        "date": "2026-07-18",
        "requests": 251,
        "creditsUsed": 498,
        "successfulRequests": 242,
        "failedRequests": 9
      }
    ]
  }
}

Billing metadata is returned in response headers: X-Captapi-Credits (credits charged), X-Captapi-Cache (hit or miss), and X-Captapi-Source. Failed requests (4xx/5xx) are never charged. See the full list of error codes in the error reference.

Response structure

A successful call returns success, cached, creditsUsed, and a data object with the following fields:

Top-level fields

daysDays. Example: 7.
totalRequestsTotal requests. Example: 251.
totalCreditsUsedTotal credits used. Example: 498.

Usage

Each item in usage contains:

dateDate. Example: "2026-07-18".
requestsRequests. Example: 251.
creditsUsedCredits used. Example: 498.
successfulRequestsSuccessful requests. Example: 242.
failedRequestsFailed requests. Example: 9.

Parameters

Name	Type	Required	Description
days	integer	No	Number of days to include (default 30, max 365).

Authentication: send your key as Authorization: Bearer capt_live_.... A typical call costs 0 credits. Always live — account endpoints are never cached.

Using an AI agent? This endpoint is the MCP tool account_daily_usage via @captapi/mcp. Set it up →

How it works

1. Sign up — get 100 free credits, no card required.
2. Create a key from your dashboard.
3. Send one request to /v1/account/daily-usage and parse the JSON response.

Use cases

Spend charts

Plot creditsUsed per day for budgeting and anomaly detection.

Reliability

Compare successfulRequests vs failedRequests over the window.

Frequently asked questions

What does the Daily Usage API do?+

The Daily Usage API returns daily usage for your Captapi API key via one GET request to /v1/account/daily-usage. It returns clean JSON and does not charge credits.

How many credits does the Daily Usage API cost?+

Account endpoints are free — they do not consume credits.

Do I need a CaptAPI Account API key or OAuth?+

You only need your Captapi API key (Authorization: Bearer). No third-party OAuth is required.

Is the Daily Usage API suitable for production use?+

Yes. It is a stable REST endpoint with predictable JSON. Account endpoints are always live (never cached) and do not charge credits.

More CaptAPI Account APIs

Credit Balance API Request History API Most Used Routes API

Ready to use the Daily Usage API?

Get started free