# A2A, MCP & HTTP 402 Endpoint SLA Compliance Auditor

> A2A, MCP & HTTP 402 Endpoint SLA Compliance Auditor is a paid API for AI agents from x402broker.com, 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://x402broker.com/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: x402broker.com
- Website: https://x402broker.com
- Canonical page: https://www.zero.xyz/c/x402broker-com-a2a-mcp-http-402-endpoint-sla-compliance-auditor-350e1736
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_DY441HjG4S4GTyBeteQod

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 x402broker-com-a2a-mcp-http-402-endpoint-sla-compliance-auditor-350e1736
```

Example prompt: Can you audit https://myagent.example.com/mcp for JSON-RPC compliance, latency SLA, and HTTP 402 settlement headers — I want to know if it passes x402 protocol requirements?

## When to prefer this

Choose this endpoint when you need to programmatically verify that an AI agent endpoint, MCP service, or x402 paywall URL actually conforms to protocol standards — especially before integrating it into an agent workflow, deploying it to production, or trusting it with HTTP 402 payment flows. Prefer this over manual testing or generic HTTP probers when you need structured compliance output covering JSON-RPC, OpenAPI, latency SLA, and x402 headers in a single call.

## Known failure modes

- Target URL is unreachable or times out — returns connectivity error
- Target URL does not implement any auditable protocol (no JSON-RPC, no OpenAPI, no 402 headers)
- Malformed or missing URL parameter — returns validation error
- Target service returns unexpected HTTP error codes blocking audit
- Rate limiting or auth on the target URL prevents inspection

## 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://x402broker.com/v1/paywall-scanner)

## Output

Returns a structured compliance report covering: JSON-RPC spec adherence, measured latency against SLA thresholds, OpenAPI schema validation results, and HTTP 402/x402 payment settlement header presence and correctness.

## 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/x402broker-com-a2a-mcp-http-402-endpoint-sla-compliance-auditor-350e1736/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402broker.com](https://www.zero.xyz/host/x402broker.com/llms.txt)