Skip to main content
Caesar API usage is credit-backed. Sign up in the Caesar app, create an API key, and add credits when you need more capacity. For a limited time, all accounts receive a $1,000 starting credit grant.

Getting started

All API calls use the same public endpoints and response shapes. A key identifies the account that owns usage, rate limits, document grants, and feedback attribution. See authentication.

Rate limits

Every response includes X-RateLimit-* headers and an access.rate_limit block so agents can back off without guessing. Details: rate limits.

Credits

Credits fund API usage across search, read, and feedback. The app shows balance, usage, payment methods, and top-ups for the account or team that owns the key.
For a limited time, all accounts receive a $1,000 starting credit grant. The grant is meant to cover evaluation and early integration work before you add paid credits.

Getting more capacity

Create additional API keys, manage credits, and add payment methods in the Caesar app. Keep keys in CAESAR_API_KEY, the CLI key store, or your secret manager; never paste key material into a chat or docs page.

FAQ

Yes. Search, read, and feedback calls require an API key. Create one in the Caesar app.
A key attaches requests to your account for credits, rate limits, document grants, and feedback attribution. It does not change endpoint URLs, response fields, or the search-read-feedback contract.
For a limited time, all accounts get a $1,000 credit grant for API usage while they evaluate and build their first integration.
The API returns HTTP 429 with X-RateLimit-* headers. Wait until X-RateLimit-Reset, reduce fan-out, or contact Caesar if your integration needs a higher per-key limit.
Use the app to manage keys and billing, then contact Caesar if you need a custom per-key limit.