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

## Facts

- Endpoint: GET https://x402-audit.agentdiet.dev/v1/preflight?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-ca6400d7
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_4qSCTjB-TAj8WAgI99aRa

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

Example prompt: Can you audit https://my-agent-service.example.com/rpc and tell me whether it's JSON-RPC compliant, meets latency SLAs, has valid OpenAPI schema, and properly implements HTTP 402 payment headers?

## When to prefer this

Use this endpoint when you need to verify that a specific A2A, MCP, or x402 service URL actually implements the protocol correctly end-to-end — covering JSON-RPC compliance, latency SLA, OpenAPI schema, and HTTP 402 payment headers — rather than just checking availability or doing a generic HTTP health check.

## Known failure modes

- Target URL is unreachable or times out — audit returns connectivity failure
- Invalid or malformed URL provided — returns validation error
- Target endpoint returns unexpected content type — schema audit may be inconclusive
- HTTP 402 headers absent or malformed — flagged as non-compliant but not an auditor error
- Rate limiting or auth on target endpoint may prevent full audit completion

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

## Output

Returns a structured audit report covering JSON-RPC protocol compliance status, measured latency vs. SLA thresholds, OpenAPI schema validity findings, and HTTP 402 x402 payment header presence and correctness for the target 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-ca6400d7/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)