AI/ML API
AI · AI
Chat, embeddings, OCR, and image generation across models on their own key.
Connecting AI/ML API in practice
AI/ML API publishes almost no numbers: 429 is documented as covering both rate and concurrency without naming a threshold for either, and the free tier is "currently paused". The only stated ceiling anywhere in the reference is on the usage-log endpoint itself, at over 200 requests per 60 seconds.
Scopes that draw scrutiny
Management keyRequired to read usage logs for any key other than the one making the call. A regular key querying another key’s logs gets 403, so cost attribution across keys needs the administrative credential.
Rate limits
- /v2/logs: over 200 requests per 60 seconds returns 429.
- /v2/logs paging: 1 to 100 rows per page, default 50.
- /v2/logs time window: cannot exceed 92 days, and accepts at most 50 distinct model values as a filter.
- Per-plan request and concurrency limits are not published; 429 is documented as signalling that either a rate or a concurrency constraint was exceeded.
Worth knowing
- The free tier is paused, so an evaluation needs a funded account before the first call.
- Because 429 conflates rate and concurrency, a client cannot tell from the status code whether to slow down or to reduce parallelism.
- A regular key can only see its own request logs, which means per-agent spend reporting needs either one key per agent or a management key.
- The observable spend signal is the account balance and usage-log endpoints rather than headers on the inference response, so cost control is a separate polling loop.
Checked against AI/ML API usage logs (2026-09-29), AI/ML API free tier (2026-09-29)
What an agent can do
Each action is granted on its own. An agent allowed to read is not thereby allowed to write, and the scope beside each row is what the acting user must have connected for it to run at all.
Often connected alongside
Put AI/ML API behind one governed endpoint.
Same permissions, same audit trail, whatever else you connect next.