# 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 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/paywall-check?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-447675bc
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_H67X_Tu_d1yPPK_sIPaW8

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-447675bc
```

Example prompt: Can you audit https://my-agent-service.example.com/rpc and check if it's properly JSON-RPC compliant, meets latency SLA, and has the right HTTP 402 payment headers set up?

## When to prefer this

Use this endpoint when you need to programmatically verify that a remote A2A agent, MCP server, or x402-enabled API correctly implements protocol standards — especially JSON-RPC compliance, HTTP 402 payment headers, latency SLAs, and OpenAPI schema correctness — before integrating with or deploying it in a production agent workflow.

## Known failure modes

- Target URL unreachable — audit fails with connectivity error
- Invalid or malformed URL input returns validation error
- Target service has no OpenAPI spec — schema check returns not-found
- Latency measurement timeout if target is too slow
- Non-standard 402 headers cause ambiguous compliance verdict

## 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/paywall-check)

## Output

Returns a compliance report object containing JSON-RPC protocol conformance status, measured latency vs. SLA thresholds, OpenAPI schema validation results, and HTTP 402 / x402 payment header inspection findings 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/polymarket-odds-agentdiet-dev-a2a-mcp-http-402-endpoint-sla-447675bc/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)