# A2A, MCP & HTTP 402 Endpoint SLA Compliance Auditor

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

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

## Facts

- Endpoint: POST https://email-verify.agentdiet.dev/v1/bazaar-verifier?utm_source=zero.xyz
- Price: $0.01/call
- Payment: MPP
- Status: unknown
- Last checked: 2026-11-21
- Activations on Zero: 0
- Provider: email-verify.agentdiet.dev
- Website: https://email-verify.agentdiet.dev
- Canonical page: https://www.zero.xyz/c/email-verify-agentdiet-dev-a2a-mcp-http-402-endpoint-sla-compliance-8edece92
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_HyIGMU0Cpd9oqtSmbsEyq

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 email-verify-agentdiet-dev-a2a-mcp-http-402-endpoint-sla-compliance-8edece92 -d '<json body>'
```

Example prompt: Can you audit my MCP server at https://my-agent.example.com/mcp to check if it's JSON-RPC compliant, passes latency SLA, has a valid OpenAPI schema, and supports HTTP 402 payment headers?

## When to prefer this

Choose this endpoint when you need to programmatically verify that an A2A agent, MCP server, or x402-enabled service meets protocol compliance standards — specifically JSON-RPC correctness, latency SLA bounds, OpenAPI schema validity, and HTTP 402 payment header conformance. Prefer this over generic HTTP testing tools when the target is an AI agent endpoint or payment-enabled MCP service that must satisfy x402/IETF MPP standards.

## Known failure modes

- Target URL unreachable or returns connection error — audit fails with connectivity error
- Target endpoint returns non-JSON or malformed response — JSON-RPC compliance check fails
- Latency exceeds SLA thresholds — flagged in report but audit still completes
- Missing or malformed HTTP 402 headers — reported as non-compliant
- Invalid or missing OpenAPI schema at target — schema validation returns failure
- Malformed input URL — returns 400 bad request

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

## Output

Returns a structured compliance report covering JSON-RPC protocol adherence, measured latency vs. SLA thresholds, OpenAPI schema validation findings, and HTTP 402 payment 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/email-verify-agentdiet-dev-a2a-mcp-http-402-endpoint-sla-compliance-8edece92/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from email-verify.agentdiet.dev](https://www.zero.xyz/host/email-verify.agentdiet.dev/llms.txt)
