AgentStatus
- How it works
- Pricing
-
Featured · September 2026
State of MCP Reliability in Production
We tested every public MCP server we could find. Calling is solved. Delivery is not.
Read the reportThoughts
The blog
In short
API keys are shown once, stored as a hash, and can be revoked. The API is rate limited and may return HTTP 429. The API is part of the Services, and has no separate uptime promise unless a signed order says so.
1. Introduction
These API Terms are part of the Terms of Service. They apply when you use the AgentStatus API, official SDKs, API keys, OAuth access, or webhooks. The Services include a documented API, published at https://agentstatus.dev/openapi.json, with keys you can create in the dashboard.
If these API Terms conflict with the Terms of Service on a point about the API, these API Terms control for that point.
2. Keys, OAuth, and your responsibility
API keys are issued to your account. In the current product, a key is shown once at creation, stored as a hash, may have an expiry you choose, and can be revoked. Keep keys confidential. You are responsible for activity that uses your keys or your OAuth tokens, unless you have told us the key was stolen and we have had a reasonable time to revoke it.
Do not share a key in a public repository or a client-side application that would expose it. If a key is leaked, revoke it in the dashboard and create a new one.
3. Rate limits and fair use
The API is rate limited. Different routes have different limits. If you exceed a limit, the API may return HTTP 429 and Retry-After or related rate-limit headers. You should back off and retry as those headers indicate. We may change limits to protect the Services.
You may not attempt to bypass rate limits, probe the API for vulnerabilities except as allowed by the Responsible disclosure page, or use the API in a way that degrades the Services for others.
4. Webhooks
If you configure webhooks, you are responsible for the URL you give us, for verifying signatures when they are provided, and for handling retries in an idempotent way. We may stop sending events to an endpoint that is repeatedly failing or that presents a security risk.
5. License and restrictions
We grant you a limited, non-exclusive, non-transferable license to call the API to use the Services for your own internal business purposes, or as otherwise agreed in writing. You may not resell, sublicense, or provide the API as a competing service to third parties, or scrape the API to build a substitute for the Services, without our written agreement.
The API, like the rest of the Services, is provided as is. No uptime or support commitment applies to the API unless a signed order or a separate agreement says so.
6. Changes
We may change or withdraw API endpoints with notice when we can reasonably give it. We may make breaking changes. It is your responsibility to follow the documentation then in effect.
7. Contact
Questions about the API can be sent to legal@carmel.so.