# A2A, MCP & HTTP 402 Endpoint SLA Compliance Auditor

> A2A, MCP & HTTP 402 Endpoint SLA Compliance Auditor is a paid API for AI agents from x402-audit.agentdiet.dev, paid per call via MPP, $0.01/call, status unknown (last checked 2026-10-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: GET https://x402-audit.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: x402-audit.agentdiet.dev
- Website: https://x402-audit.agentdiet.dev
- Canonical page: https://www.zero.xyz/c/x402-audit-agentdiet-dev-a2a-mcp-http-402-endpoint-sla-compliance-7743516c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_kueIG7C3T04EoURILi4LW

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 x402-audit-agentdiet-dev-a2a-mcp-http-402-endpoint-sla-compliance-7743516c
```

Example prompt: Can you audit my MCP server at https://my-agent.example.com/mcp and tell me if it's JSON-RPC compliant, meets latency SLAs, has a valid OpenAPI schema, and returns proper HTTP 402 payment headers?

## When to prefer this

Use this endpoint when you need to programmatically verify whether a remote A2A agent, MCP server, or x402 payment endpoint meets protocol compliance requirements — specifically when you care about JSON-RPC correctness, OpenAPI schema validity, latency SLAs, and HTTP 402 settlement headers simultaneously. Prefer this over generic HTTP health-check tools when the target is an AI agent or MCP tool and protocol-level compliance matters.

## Known failure modes

- Target URL is unreachable or returns a network error — audit fails with connection error
- Target URL does not implement any recognized protocol (A2A, MCP, x402) — partial or empty compliance report
- URL parameter missing or malformed — 400 Bad Request
- Target endpoint is too slow or times out during latency probe — SLA marked as failed
- Firewall or IP block prevents the auditor from reaching the target — connection refused error

## 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://x402-audit.agentdiet.dev/v1/x402-verifier)

## Output

Returns a structured compliance report covering: JSON-RPC protocol adherence, measured latency against SLA thresholds, OpenAPI schema validation status, and HTTP 402/x402 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/x402-audit-agentdiet-dev-a2a-mcp-http-402-endpoint-sla-compliance-7743516c/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402-audit.agentdiet.dev](https://www.zero.xyz/host/x402-audit.agentdiet.dev/llms.txt)