# 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-10-21).

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

## Facts

- Endpoint: GET https://onchain-risk.agentdiet.dev/v1/x402-verifier?utm_source=zero.xyz
- Price: $0.01/call
- Payment: MPP
- Status: unknown
- Last checked: 2026-10-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-1444862f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_4DQp8WQglhFBwW6f2OE2F

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-1444862f
```

Example prompt: Can you audit https://my-agent-service.example.com/mcp for JSON-RPC compliance, check its latency SLA, and tell me if it has proper HTTP 402 x402 payment settlement headers configured?

## When to prefer this

Choose this endpoint when you need to verify that a remote agent, MCP server, or x402-enabled API meets protocol standards before integration or listing — especially when HTTP 402 payment compliance, JSON-RPC correctness, or latency SLA validation are required. Prefer this over generic uptime monitors when protocol-level compliance (x402 v2, IETF MPP, MCP, OpenAPI) is the concern.

## Known failure modes

- Target URL is unreachable or returns a network error — audit fails with connectivity error
- Target URL lacks any recognized protocol (not A2A/MCP/x402) — compliance fields return null or unsupported
- Malformed or missing URL parameter — returns 400 bad request
- Target endpoint has extremely high latency causing audit timeout
- Target returns unexpected content type preventing schema parsing

## 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/x402-verifier)

## Output

Returns a structured compliance report including JSON-RPC conformance status, measured latency against SLA thresholds, OpenAPI schema validation findings, and HTTP 402 x402 settlement header presence and validity for the target 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-1444862f/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)