# 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 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/bazaar-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-b9a83e77
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ws-aje5KgzKsZhhP6USP5

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

Example prompt: Can you audit this MCP server URL for JSON-RPC compliance, latency SLA, and HTTP 402 payment header correctness: https://my-agent-service.example.com/mcp?

## When to prefer this

Use this endpoint when you need to programmatically verify that a remote A2A agent, MCP server, or x402-enabled service meets protocol compliance standards before integrating it into an agent pipeline, listing it in a marketplace, or trusting it with payments. Prefer this over manual inspection or generic HTTP checkers when you specifically need JSON-RPC compliance, latency SLA measurement, OpenAPI schema validation, and HTTP 402 header verification in a single call.

## Known failure modes

- Target URL is unreachable or times out — returns connectivity error
- Target URL does not implement JSON-RPC or MCP — returns non-compliance finding
- Invalid or missing URL parameter — returns 400 bad request
- Target service returns unexpected HTTP status codes confounding audit logic
- HTTP 402 headers absent or malformed — flagged 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://x402-audit.agentdiet.dev/v1/bazaar-verifier)

## Output

Returns a structured compliance report covering JSON-RPC spec adherence, measured latency vs SLA thresholds, OpenAPI schema validity findings, and HTTP 402/x402 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-b9a83e77/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)