# A2A, MCP & HTTP 402 Endpoint SLA Compliance Auditor

> A2A, MCP & HTTP 402 Endpoint SLA Compliance Auditor is a paid API for AI agents from onchain-risk.agentdiet.dev, paid per call via MPP, $0.01/call, status unknown (last checked 2026-11-21).

Audits a remote agent, MCP, or x402 service URL for JSON-RPC compliance, latency SLA, OpenAPI schema validity, and HTTP 402 payment settlement headers

## Facts

- Endpoint: POST https://onchain-risk.agentdiet.dev/v1/paywall-check?utm_source=zero.xyz
- Price: $0.01/call
- Payment: MPP
- Status: unknown
- Last checked: 2026-11-21
- Activations on Zero: 0
- Provider: onchain-risk.agentdiet.dev
- Website: https://onchain-risk.agentdiet.dev
- Canonical page: https://www.zero.xyz/c/onchain-risk-agentdiet-dev-a2a-mcp-http-402-endpoint-sla-compliance-a3bfeb72
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_yBzVpz_zyCliSe9wlcy-V

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability onchain-risk-agentdiet-dev-a2a-mcp-http-402-endpoint-sla-compliance-a3bfeb72 -d '<json body>'
```

Example prompt: Can you audit this MCP endpoint for me — https://myagent.example.com/mcp — and tell me if it's JSON-RPC compliant, whether it passes latency SLA, and whether the HTTP 402 settlement headers look correct?

## When to prefer this

Use this endpoint when you need to programmatically verify that an A2A agent, MCP server, or x402-gated API is correctly implementing protocol standards — especially JSON-RPC compliance, latency SLAs, OpenAPI schema correctness, and HTTP 402 payment settlement headers — rather than just checking basic HTTP reachability. Prefer it over generic uptime monitors when protocol-level compliance and payment header validation are the primary concerns.

## Known failure modes

- Target URL is unreachable or times out — audit fails with a connectivity error
- Malformed or non-URL input causes a validation error before the probe is sent
- Target endpoint returns an unexpected protocol making JSON-RPC checks inconclusive
- HTTP 402 headers are absent or malformed, reported as non-compliant rather than an auditor error
- Rate limiting or network restrictions on the target side may cause incomplete SLA measurements

## How this service works

Audits any remote agent or MCP URL for JSON-RPC compliance, latency SLA, OpenAPI schema, and HTTP 402 settlement headers. (Live x402 v2, IETF MPP & MCP endpoint at https://onchain-risk.agentdiet.dev/v1/paywall-check)

## Output

Returns a structured compliance report covering JSON-RPC spec adherence, measured latency versus SLA thresholds, OpenAPI schema validity findings, and HTTP 402 / x402 settlement header correctness for the audited endpoint URL.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "url"
 ],
 "properties": {
  "url": {
   "type": "string",
   "minLength": 1,
   "description": "Target A2A, MCP, or x402 service URL to audit for protocol compliance"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/onchain-risk-agentdiet-dev-a2a-mcp-http-402-endpoint-sla-compliance-a3bfeb72/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from onchain-risk.agentdiet.dev](https://www.zero.xyz/host/onchain-risk.agentdiet.dev/llms.txt)
