# A2A, MCP & HTTP 402 Endpoint SLA Compliance Auditor

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

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

## Facts

- Endpoint: GET https://polymarket-odds.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: polymarket-odds.agentdiet.dev
- Website: https://polymarket-odds.agentdiet.dev
- Canonical page: https://www.zero.xyz/c/polymarket-odds-agentdiet-dev-a2a-mcp-http-402-endpoint-sla-255a805e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_2y0Hkt-tWeaEM_k5e73RL

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 polymarket-odds-agentdiet-dev-a2a-mcp-http-402-endpoint-sla-255a805e
```

Example prompt: Can you audit this MCP endpoint for me — https://myagent.example.com/mcp — and tell me if it's JSON-RPC compliant, hitting its latency SLA, has a valid OpenAPI schema, and has proper HTTP 402 settlement headers set up?

## When to prefer this

Choose this endpoint when you need to verify that a specific A2A agent endpoint, MCP server, or x402-enabled service correctly implements JSON-RPC, meets latency SLAs, exposes a valid OpenAPI schema, and has properly configured HTTP 402 settlement headers — particularly before deploying or integrating a new agent tool into a production swarm or marketplace.

## Known failure modes

- Target URL is unreachable or returns a network error — audit fails with connectivity error
- Invalid or malformed URL provided — returns validation error before probe
- Target endpoint times out — latency SLA marked as failed
- Non-standard protocol on target causes JSON-RPC parse errors — compliance marked as non-conformant
- HTTP 402 headers absent or malformed on target — payment compliance check fails

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

## Output

Returns a structured audit report covering JSON-RPC compliance status, measured latency versus SLA thresholds, OpenAPI schema validation results, and HTTP 402 payment settlement header compliance for the submitted 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/polymarket-odds-agentdiet-dev-a2a-mcp-http-402-endpoint-sla-255a805e/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from polymarket-odds.agentdiet.dev](https://www.zero.xyz/host/polymarket-odds.agentdiet.dev/llms.txt)