What this key has spent (alias of /api/v1/won/usage)

GET/api/v1/memory/usage

In the SDKs: usage

Identical behaviour and rate-limit budget — see /api/v1/won/usage.

Authentication

Every call carries your API key in an X-API-Key header. Keys are created in the console.

Request body

None. This call takes no JSON body.

Returns

The 200 body. Fields nested one level are shown as parent.child.

window_days integer

Days covered by the workspace figures.

key object

This key only — never a roster of the account's other keys.

key.requests integer

key.cost_cents number

Lifetime, priced at each serving model's rate plus the per-request fee.

key.input_tokens integer

key.output_tokens integer

key.since "lifetime"

workspace object

The workspace this key belongs to, over the requested window.

workspace.workspace_id string,null

workspace.requests integer

workspace.cost_cents number

stores object[]

Per-store spend over the window, highest spend first, at most 50. other is the overflow bucket once an account meters more than 200 distinct stores in a day, not a real store.

stores.store string

stores.requests integer

stores.cost_cents number

balance_cents number

Prepaid balance left on the account. Negative means overdrawn.

expiring_soon_cents number

Of what is left, how much expires within 90 days.

Example

curl -X GET https://api.wontopos.com/api/v1/memory/usage \
  -H "X-API-Key: $WOS_API_KEY"

Status codes

Rate limits per tier and the full status list are in Errors & limits.

In the SDKs

The Python, TypeScript, and Rust SDKs wrap this endpoint so you do not build the request by hand — pip install wontopos, npm i wontopos, or cargo add wontopos, then the method list is on the SDK reference. A coding agent can take the whole API in one file at llms.txt, or over MCP with npx -y wontopos-mcp.

Related

• Usage (Won)
• Revisions (Won)
• Revisions (alias)
• Lineage