Manage API Keys and Track Usage in Capriole AI

The Capriole AI API page keeps key management and usage accounting in one place. You can create named keys, disable or delete them, filter requests by time, key, model, or status, and compare raw token usage with the charged tokens deducted from your balance. API access requires an active Premium membership or eligible Team access. Personal Premium costs USD 8 per month and includes 5 million charged API tokens alongside unlimited browser chat across the supported Premium model set. The same account therefore covers everyday chat, application code, and coding agents without separate provider keys or billing pages.

Create a named API key

Open the API page

Open Capriole AI API and sign in. The page shows API keys, Playground, and Usage for an account with API access.

Create and name the key

Select Create key. The Name (Optional) field can identify the client that will use it, such as local-codex, support-agent, or test-script.Use separate named keys for long-lived clients or team members. That makes a request easier to attribute and lets you revoke one client without replacing every credential.

Copy the secret immediately

Select Create, then copy the value from the Secret key dialog. Capriole shows the full secret only after creation. The key list displays a masked value later.

Do not place the secret in source control, screenshots, support messages, or client-side application code. If the full value is lost, create a replacement key.

Send one test request

Follow the API quickstart or the OpenAI and Anthropic SDK guide. Return to Usage after the request completes.A model response is useful, but the usage row is the stronger confirmation. It shows that Capriole received the request under the expected key and model.

Read the current balance

The Usage section separates the current included quota from purchased on-demand tokens.

Summary	What it means
Included usage	Current membership quota, billing cycle, used tokens, and remaining percentage
On-demand usage	Purchased top-up tokens, used amount, and remaining balance
Total requests	Successful and failed requests inside the selected usage filters
Charged tokens	Quota deducted for the filtered successful usage, alongside total and cached tokens

The Time filter changes the request analytics and rows. It does not change the billing cycle or recalculate the quota summary for that selected window. Read Capriole AI Charged Tokens Explained for the cached-input formula and rounding rule.

Filter the request history

Use the filters to answer one question at a time.

Filter	Available choices	Useful for
Time	Last 24 hours, 7 days, 30 days, or all time	Isolating a deployment or recent test
Key	All keys or one named key	Confirming which client sent traffic
Model	Models found in the visible usage history	Comparing traffic across model routes
Status	All status, success, or error	Separating completed calls from failures
Member	Team members, for owners and admins	Reviewing team traffic by person

Each request row can show the time, key, model, input tokens, cached tokens, output tokens, charged tokens, total tokens, latency, status, and an error message. Some metrics can be unavailable when an upstream response or failed request does not provide them.

Verify a client used the intended key

After sending a test request:

Set Time to Last 24 hours.
Select the named Key used by the client.
Select the expected Model if several models are present.
Set Status to Success.
Confirm that the new row has the expected time and token activity.

This check catches a common setup mistake. A coding tool can produce a response through a built-in or fallback provider even when its Capriole configuration is not active. A matching Capriole usage row removes that ambiguity.

Deactivate, reactivate, or delete a key

Action	Result	Can it be reversed?
Deactivate	New requests using that key stop authenticating	Yes, turn the key back on
Reactivate	The existing key can authenticate again	Yes
Delete	The key is permanently removed	No

Use deactivation when you are investigating a client or temporarily stopping traffic. Delete a key after replacing it, or when the credential may have been exposed. The list shows Created and Last used values to help identify stale keys. A displayed status of Inactive means the key has been revoked until it is reactivated.

Team visibility

Team owners and admins can filter usage by member and compare requests or charged tokens across members. A regular team member sees only the usage permitted for that member. Team top-ups and team-wide controls are also limited to eligible team roles. The usage filters do not expose Capriole’s internal provider route, upstream cost, or fallback diagnostics. They report the customer-facing model, request result, and token accounting needed to manage API access.

Continue from here

Use one key with coding agents for an initial compatibility test, or open the maintained integration guides for client-specific configuration. The dated API cost comparison explains how Capriole’s quota units differ from provider input and output pricing. Try GPT-5.6 Thinking, Claude Fable 5, or Gemini 3.1 Pro in limited free browser chat. Upgrade to Premium when you want to create a key and use the included monthly API balance. Facts checked: 2026-08-10.

​Create a named API key

​Read the current balance

​Filter the request history

​Verify a client used the intended key

​Deactivate, reactivate, or delete a key

​Team visibility

​Continue from here

Create a named API key

Read the current balance

Filter the request history

Verify a client used the intended key

Deactivate, reactivate, or delete a key

Team visibility

Continue from here