# A2A, MCP & HTTP 402 Endpoint SLA Compliance Auditor

> A2A, MCP & HTTP 402 Endpoint SLA Compliance Auditor is a paid API for AI agents from agentdiet.dev, paid per call via MPP, $0.01/call, status unknown (last checked 2026-10-21).

Audits any A2A agent, MCP, or x402 URL for JSON-RPC compliance, latency SLA, OpenAPI schema validity, and HTTP 402 payment settlement headers

## Facts

- Endpoint: GET https://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: agentdiet.dev
- Website: https://agentdiet.dev
- Canonical page: https://www.zero.xyz/c/agentdiet-dev-a2a-mcp-http-402-endpoint-sla-compliance-auditor-4b6eddf3
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_PrLezbyzWgFLfsF1zt3vY

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 agentdiet-dev-a2a-mcp-http-402-endpoint-sla-compliance-auditor-4b6eddf3
```

Example prompt: Can you audit https://myagent.example.com/mcp for JSON-RPC compliance, latency SLA, and HTTP 402 payment header support?

## When to prefer this

Choose this endpoint when you need to programmatically verify whether an A2A agent, MCP server, or x402-enabled service URL correctly implements JSON-RPC, meets latency SLAs, exposes a valid OpenAPI schema, and carries proper HTTP 402 payment settlement headers — especially before listing a tool on an agent marketplace or integrating a third-party agent into a swarm.

## Known failure modes

- Target URL is unreachable or times out — returns error indicating connection failure
- Target URL does not implement any recognized protocol (A2A, MCP, x402) — returns non-compliance findings
- Malformed or missing URL parameter — returns validation error
- Target server returns unexpected non-standard HTTP responses that cannot be parsed for compliance
- Rate limiting or payment failure on the auditor itself — returns 402 or 429 response

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

## Output

Returns a compliance report object covering JSON-RPC protocol conformance, measured latency against SLA thresholds, OpenAPI schema validation findings, and HTTP 402 / x402 payment settlement header presence and correctness for the submitted 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/agentdiet-dev-a2a-mcp-http-402-endpoint-sla-compliance-auditor-4b6eddf3/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agentdiet.dev](https://www.zero.xyz/host/agentdiet.dev/llms.txt)