# 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-17).

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

## Facts

- Endpoint: POST https://onchain-risk.agentdiet.dev/v1/bazaar-verifier?utm_source=zero.xyz
- Price: $0.01/call
- Payment: MPP
- Status: unknown
- Last checked: 2026-11-17
- 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-35369fd3
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_PJC0jzShv99YpLreQN579

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-35369fd3 -d '<json body>'
```

Example prompt: Can you audit this MCP endpoint — https://example-agent.com/mcp — and tell me whether it's JSON-RPC compliant, passes latency SLA, has valid OpenAPI schema, and has the right HTTP 402 payment headers set up?

## When to prefer this

Choose this endpoint when you need to programmatically verify that a remote A2A agent, MCP server, or x402-gated API actually conforms to protocol standards — covering JSON-RPC, OpenAPI schema, latency SLAs, and HTTP 402 payment headers in a single audit pass. Prefer it over manual inspection or generic HTTP probing tools when you need a structured compliance report that covers all four dimensions simultaneously.

## Known failure modes

- Target URL unreachable or times out — audit fails with connectivity error
- Malformed or missing URL input — validation error returned
- Target returns unexpected protocol (e.g. plain HTTP redirect) — compliance checks may be inconclusive
- Rate limiting on target endpoint causes latency measurements to be skewed
- x402 headers absent or malformed — reported as non-compliant rather than erroring

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

## Output

Returns a structured compliance report covering JSON-RPC protocol adherence, measured latency versus SLA thresholds, OpenAPI schema validation results, and HTTP 402 payment settlement header presence and correctness 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-35369fd3/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)
