# A2A, MCP & HTTP 402 Endpoint SLA Compliance Auditor

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

Audits any 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://mcp-compiler.agentdiet.dev/v1/paywall-scanner?utm_source=zero.xyz
- Price: $0.01/call
- Payment: MPP
- Status: unknown
- Last checked: 2026-10-21
- Activations on Zero: 0
- Provider: mcp-compiler.agentdiet.dev
- Website: https://mcp-compiler.agentdiet.dev
- Canonical page: https://www.zero.xyz/c/mcp-compiler-agentdiet-dev-a2a-mcp-http-402-endpoint-sla-compliance-0f4840a7
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_hkXwcvRU3-EuW7NA1PNp-

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 mcp-compiler-agentdiet-dev-a2a-mcp-http-402-endpoint-sla-compliance-0f4840a7
```

Example prompt: Can you audit https://myagent.example.com/mcp for JSON-RPC compliance, latency SLA, and HTTP 402 payment headers to see if it's fully protocol-compliant?

## When to prefer this

Choose this endpoint when you need to programmatically verify that a remote MCP, A2A agent, or x402-paywalled service conforms to protocol standards — especially JSON-RPC compliance, OpenAPI schema correctness, HTTP 402 settlement header validity, and latency SLAs. It is the right choice over generic HTTP health-check tools when the target is specifically an AI agent protocol endpoint and you need structured, protocol-aware compliance output rather than a simple ping or uptime check.

## Known failure modes

- Target URL is unreachable or returns a network timeout
- Target URL is not an A2A, MCP, or x402 endpoint and returns unexpected content
- Missing required 'url' query parameter returns a 400 error
- Target endpoint blocks probing requests with auth or IP restrictions
- Malformed URL input causes validation failure before probe

## 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://mcp-compiler.agentdiet.dev/v1/paywall-scanner)

## Output

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