# 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/usdc-quote-audit?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-15172423
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_j8L1mjEj3VK1jbi0PqfyY

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-15172423
```

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

## When to prefer this

Choose this endpoint when you need to programmatically verify that an A2A agent, MCP server, or x402 payment endpoint meets protocol standards — including JSON-RPC 2.0, OpenAPI schema, latency SLA, and HTTP 402 settlement header requirements — rather than doing a simple HTTP health check or a general-purpose uptime ping.

## Known failure modes

- Target URL is unreachable or returns a network error — audit cannot proceed
- Target URL does not expose a recognizable A2A, MCP, or x402 interface — partial or empty compliance results
- Missing required 'url' query parameter — request rejected with validation error
- Target service is too slow to respond within audit timeout — latency SLA marked as failed
- Malformed or non-standard HTTP 402 headers — flagged as non-compliant in settlement header section

## 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/usdc-quote-audit)

## Output

Returns a structured compliance report covering JSON-RPC conformance, measured latency against SLA thresholds, OpenAPI schema validity, and HTTP 402/x402 payment header 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-15172423/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)
