Agent Reliability · Checks on whether a service’s reliability records agree with each other and with what it advertises
Every reliability record, read against the records behind it.
Reliability records hold up when the published uptime figure is the one the downtime log supports; the error budget follows from the SLO it cites; the failover arrangement delivers the standby, recovery objectives and triggers the terms claim; the dependency disclosure names the providers, dependent functions and fallbacks the listing states; the degraded behavior on record is the behavior advertised; the incident summary buyers see carries every incident in the history with its duration and cause; maintenance follows the notice, length and frequency the policy sets; and the periodic report’s headlines are the figures its records hold. Agent Reliability reads the records an agent or its principal supplies, checks each one for consistency against the document behind it, and returns a signed verdict with the evidence read and what would change it.
- Tool access
- 0.10 USDC / call
- Tools
- Eight tools: eight checks
- Connection
- /mcp
- Result
- Signed report
Start with the two free tools.
On https://weverlabs.com/mcp-free, anonymous and with no wallet, two Agent Reliability tools map the family and show the uptime check at work on synthetic data. Each returns an unsigned result in the family's report shape and ends with a line naming the main tools.
wever_rely-snapshot
- Reads
- Nothing, or the situation in hand, such as publishing uptime, planning failover or writing a reliability report, and optionally the names of the documents in hand.
- Returns
- The eight reliability record checks with what each reads, its four verdicts and when each fits, with the checks that fit the situation listed first.
- Access
- Free on /mcp-free
wever_rely-uptime-sample
- Reads
- Nothing, or one synthetic service: a search API, a file storage service or a messaging service.
- Returns
- A synthetic uptime report faithful to its downtime log beside a misreported one, both read by the uptime check’s own reading, with the availability, the downtime, the incidents and the period annotated with why they pass or fail.
- Access
- Free on /mcp-free
How agents and people use it.
Your agents
- Call
wever_rely-snapshot with the situation in hand to see which checks fit first, before reading any record. - Call the check that answers the question on
https://weverlabs.com/mcp: when an uptime figure is published, when an error budget is reported, when continuity is claimed, when dependencies are disclosed, when degraded behavior is advertised, when incidents are summarized, when maintenance is scheduled and when a reliability report goes to buyers. - Read the verdict, the evidence read and what would change it, each report carrying an Ed25519 receipt anyone can verify, signed.
- Act on the verdict and its findings: ask for a corrected report, record, disclosure or summary, the records behind it, or carry on as checked.
You
- See each uptime figure, error budget and failover claim read against the log, SLO or arrangement behind it, with the figure on each side.
- Read every dependency disclosure, degradation record, incident summary, maintenance record and reliability report against the listing, advertised behavior, history, policy or records behind it.
- Verify any check against Wever's published trust key whenever you need to show where a verdict came from.
A worked example
One uptime report, read against the downtime log behind it.
The request
{
"name": "wever_rely-uptime-check",
"arguments": {
"report": {
"service": "Harbor Search API",
"period_from": "2026-10-01",
"period_to": "2026-10-31",
"availability_percent": 99.95,
"downtime_minutes": 22,
"incident_count": 3
},
"log": {
"service": "Harbor Search API",
"period_from": "2026-10-01",
"period_to": "2026-10-31",
"entries": [
{
"id": "SR-1",
"started_at": "2026-10-03T02:00:00Z",
"ended_at": "2026-10-03T02:25:00Z"
},
{
"id": "SR-2",
"started_at": "2026-10-17T14:10:00Z",
"minutes": 12
},
{
"id": "SR-3",
"started_at": "2026-10-28T08:00:00Z",
"ended_at": "2026-10-28T08:08:00Z"
}
]
}
}
}What the report returns
Verdict: rely_uptime_misreported.
| Finding, availability overstated | The report publishes 99.95% availability where the log’s 45 minutes of downtime over 2026-10-01 to 2026-10-31 leaves 99.899%. |
|---|
| Finding, downtime understated | The report states 22 minutes of downtime where the log records 45 minutes. |
|---|
| Fix, availability overstated | Publish the availability the log supports for the period, or record the downtime the log leaves out. |
|---|
| Fix, downtime understated | State the downtime minutes the log records for the period. |
|---|
The uptime report misreports the log: availability overstated and downtime understated.
The log records 45 minutes of downtime across three incidents in October, which leaves 99.899% availability over the month’s 44,640 minutes; the report publishes 99.95% and 22 minutes. The incident count, the period and the service match the log, and the report’s own 22 minutes would give 99.95%, so the report is consistent with itself and not with its log. The report states that publishing the figure the log supports and its downtime moves the verdict to rely_uptime_faithful.
Call it from your agent.
Connect to https://weverlabs.com/mcp and call any of the eight tools. Each call costs 0.10 USDC on Base. Eligible calls share 10 free calls per wallet over a rolling 30 days with the other paid tools. For free access, send X-Wever-Wallet-Proof signed over the exact JSON arguments and the tool route. The payment challenge supplies the x402 terms for a paid call.
Every report comes with an Ed25519 receipt signed with Wever's published trust key. The Agent Reliability contract lists the schemas, limits, verdicts and signing details. To probe one live MCP or x402 endpoint, Endpoint reliability; to restate one SLA, status page or incident on its own, Diligence checks; for your own incident plan, recovery arrangements and an operator’s continuity, Preflight; for retry, rollback and failure-notice designs, Agent Recovery; for an agent’s own traces, logs and summaries, Agent Observability; and for SLA terms and deadlines kept on record, Agent SLA Rail.
Browse all tools