# 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 A2A, MCP, or HTTP 402 service URL for JSON-RPC compliance, latency SLA adherence, OpenAPI schema validity, and x402 payment settlement headers

## Facts

- Endpoint: POST https://onchain-risk.agentdiet.dev/v1/mpp-verifier?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-18a710f4
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_TnfXKR08g3RtkjtFvoffI

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-18a710f4 -d '<json body>'
```

Example prompt: Can you audit https://my-agent.example.com/mcp for JSON-RPC compliance, latency SLA, OpenAPI schema validity, and HTTP 402 settlement headers — I want to know if it's fully protocol-compliant before I ship it?

## When to prefer this

Use this endpoint when you need to programmatically verify that a remote A2A agent, MCP server, or HTTP 402-gated API is protocol-compliant before integration, deployment, or ongoing monitoring. It is specifically suited for validating JSON-RPC structure, latency SLAs, OpenAPI schemas, and x402 payment headers in a single call — prefer it over generic HTTP health-check tools when the target is an AI agent or payment-gated service endpoint.

## Known failure modes

- Target URL is unreachable or times out — audit returns connectivity error
- Target URL does not implement any recognized protocol (A2A/MCP/x402) — report shows no compliant protocol detected
- Malformed URL input — returns validation error on the url field
- Target server returns unexpected non-standard responses — partial compliance results with warnings
- Rate limiting or network errors from the audited endpoint — latency SLA marked as failed or inconclusive

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

## Output

A structured compliance report covering JSON-RPC conformance, measured latency versus SLA thresholds, OpenAPI schema validity findings, and HTTP 402 / x402 settlement header status for the audited 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-18a710f4/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)
