Embeddable

Track API token usage

See how many Developer API requests and tokens your workspace has used, and what each API action costs.

2 min readPublished by Daniel Sternlicht on Nov 22, 2026, 10:32 AM UTCUpdated Nov 22, 2026

Every Developer API request is recorded against your workspace, and you can review the totals in the dashboard. This article shows where to find them and what each API action costs.

Open the Usage tab

You need access to your workspace's settings. You don't need to make a request first, but the page shows zeros until your keys have been used.

  1. Sign in to your Embeddable workspace.
  2. Open Settings from the left navigation.
  3. Select the For developers tab.
  4. Select API Keys.
  5. Switch from Keys to Usage.

The Usage view shows Requests (30d) and Tokens used (30d) for your workspace, plus a Requests over time chart. Use the 30 days and 12 months toggles to change the chart's range.

The Usage view on the API Keys page

API keys are scoped to a single workspace, so the numbers cover only the workspace you're currently working in.

Read per-request usage

Usage is recorded per request. Each call to the API adds to Requests (30d), and calls that cost tokens also add to Tokens used (30d).

Only some actions consume API tokens:

ActionTokens
Create widget (POST /v1/widgets)1
Edit widget (POST /v1/widgets/:id/edit)1
Create agent (POST /v1/agents)1
Run agent (POST /v1/agents/:id/run)1
Read, list, delete or publish0

This means Requests can be much higher than Tokens used. Polling a job with GET /v1/jobs/:id or listing widgets, for example, doesn't use tokens. Creating a widget and then polling its build until it finishes costs 1 token in total.

Does API use count as messages? API tokens are consumed from your workspace's plan, not from a separate API-only allowance. The Usage tab is where you see how many have been spent through the API. The Messages left this month indicator in the dashboard sidebar shows your plan's remaining allowance.

Stay within limits

Plan limits apply to API usage. Check the Tokens used (30d) figure against your plan's allowance before you run a large batch of widget or agent creations.

To keep usage predictable:

  • Count only the creating, editing and running calls. Reads, lists, deletes and publishes are free.
  • Don't retry a create call blindly after an error. Each successful create call costs a token. Poll the job with the jobId the original call returned instead.
  • Check the Usage tab after a test run to confirm the numbers match what you expected.
  • If you need a higher allowance, use Upgrade in the dashboard sidebar.

The figures may take a moment to update, so if you've just made a request and see zeros, refresh the page and look again.

Did this answer your question?

Your feedback helps us improve.