AgentStatus
We tested every public MCP server we could find. Calling is solved. Delivery is not.
Read the reportSLAs are about to change.
For decades, SLAs have meant one thing: uptime. "We guarantee 99.9% availability."
For AI agents, uptime is necessary but not sufficient. An agent can be "up" while being completely useless.
The next generation of SLAs will include something new: semantic correctness.
Traditional SLA:
What it doesn't guarantee:
For a database or payment API, uptime is a reasonable proxy for "working." The API either returns the data or doesn't.
For an AI agent, uptime is only the beginning.
Industry research reveals the true scope of the problem:
An agent returning "I cannot help with that" to every query shows 100% uptime. It's also 0% useful.
SLAs that only measure uptime miss these failures entirely.
The baseline. Endpoint responds.
Metric: Percentage of successful HTTP responses
Typical target: 99.9%
This is table stakes. Necessary but insufficient.
Does the agent actually work correctly?
Metric: Gold prompt pass rate
Typical target: 95-99%
This catches "up but broken" states. If the agent can't answer "What is 2+2?", it's not working, regardless of HTTP status.
Traditional: "Average response time under X seconds"
Agent: "TTFB P95 under X seconds"
Metric: Time to First Byte, 95th percentile
Typical target: 3-5 seconds
For streaming agents, TTFB is the user experience metric. P95 catches tail latencies, not just averages.
Does it work everywhere your users are?
Metric: Per-region availability and latency
Typical target: 95%+ per region, latency within 2x of baseline
Catches regional outages that global metrics miss.
Service Level Agreement: AI Assistant
1. Availability
- Endpoint availability: 99.9%
- Measured: Percentage of checks returning HTTP 2xx
2. Semantic Correctness
- Gold prompt pass rate: 95%
- Measured: Standard health prompts answered correctly
3. Performance
- TTFB P50: <2 seconds
- TTFB P95: <5 seconds
- Measured: Time to first byte across all checks
4. Geographic Coverage
- All covered regions: >95% availability
- Covered regions: US, EU, APAC
5. Credits
- Each 0.1% below target: 10% credit
- Maximum credit: 50% of monthly fee
- Exclusions: Scheduled maintenance, customer-caused issuesService Level Agreement: Enterprise AI Assistant (Premium)
1. Availability
- Endpoint availability: 99.95%
2. Semantic Correctness
- Health gold prompt pass rate: 99%
- Contract gold prompt pass rate: 98%
3. Performance
- TTFB P50: <1 second
- TTFB P95: <3 seconds
- Total latency P95: <15 seconds
4. Geographic Coverage
- Primary regions (US, EU): >99% availability
- Secondary regions (APAC, LATAM): >97% availability
- Latency variance: <2x between regions
5. Incident Response
- Detection to acknowledgment: <15 minutes
- Acknowledgment to resolution: <2 hours
6. Credits
- Availability miss: 25% credit per 0.1% below target
- Correctness miss: 20% credit per 1% below target
- Performance miss: 10% credit per violation
- Maximum credit: 100% of monthly feeTraditional uptime is easy to measure. Ping the endpoint, check for 200.
Semantic correctness requires more:
We designed Agent Status specifically for agent SLAs:
Availability:
Semantic Correctness:
Performance:
Geographic:
All with an API for integration into your SLA reporting.
If you provide an AI agent to customers:
If you buy AI agents:
If you run an agent marketplace:
"We'll try to keep it running."
Most agents today.
"99.9% availability."
Standard web service SLA applied to agents.
"99.9% availability, P95 latency <5s."
Adds latency, but still no semantic correctness.
"99.9% availability, P95 latency <5s, 95% correctness."
This is where agents need to be.
"99.9% availability, P95 latency <5s, 95% correctness, per-region guarantees, incident response targets."
Best-in-class.
Most vendors are at Level 0 or 1. The market is moving to Level 3-4.
Without SLA:
With SLA:
SLAs force the math to work for reliability.
Agents with strong SLAs command premium pricing:
SLAs signal seriousness:
Agent SLAs will become:
We're early. The companies that figure out agent SLAs now will have an advantage when they become mandatory.