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

## Facts

- Endpoint: GET https://x402-audit.agentdiet.dev/paid?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-1c64f52a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_bcNLVevYAUVqq049ypLDC

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-1c64f52a
```

Example prompt: Can you audit https://my-agent-service.example.com/mcp to check whether it's properly compliant with MCP and JSON-RPC specs, passes latency SLA thresholds, and has valid HTTP 402 x402 settlement headers?

## When to prefer this

Choose this endpoint when you need to programmatically verify that an A2A agent, MCP server, or x402-enabled HTTP service is correctly implementing protocol standards — specifically JSON-RPC correctness, OpenAPI schema validity, latency SLA compliance, and HTTP 402/x402 payment settlement headers — rather than doing a generic health check or uptime ping.

## Known failure modes

- Target URL is unreachable or returns a network error
- Target URL does not implement any of the expected protocols, yielding empty or N/A results
- Malformed or missing URL parameter causes a 400 bad request
- Target URL has SSL/TLS certificate errors preventing connection
- Rate limiting or access restrictions on the target service blocking the audit

## 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/paid)

## Output

Returns a structured compliance report covering JSON-RPC protocol adherence, measured latency against SLA thresholds, OpenAPI schema validation findings, and HTTP 402 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-1c64f52a/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)