# 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 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://x402broker.com/v1/x402-mpp-paywall-verifier?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-e0b4ebe9
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ZjZWl5RpiRDWfahrahuPH

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-e0b4ebe9
```

Example prompt: Can you audit https://myagent.example.com/mcp and tell me if it's passing JSON-RPC compliance, latency SLA, OpenAPI schema checks, and HTTP 402 payment header requirements?

## When to prefer this

Choose this endpoint when you need to programmatically verify that an A2A agent, MCP server, or x402-enabled service URL conforms to JSON-RPC, OpenAPI, HTTP 402 settlement, and latency SLA standards — especially before integrating a new agent or going live with a paywall service. Prefer it over manual testing or generic HTTP checkers when you need structured, multi-dimensional protocol compliance output including x402/MCP-specific checks.

## Known failure modes

- Target URL is unreachable or times out — returns error indicating connection failure
- Target URL returns non-standard or malformed responses preventing compliance analysis
- Invalid or missing URL parameter — returns validation error
- Target service blocks probing requests (e.g. firewall, auth required) — returns access error
- Ambiguous compliance results when target partially implements a protocol

## 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/x402-mpp-paywall-verifier)

## Output

Returns a structured compliance report covering JSON-RPC protocol conformance, measured latency versus SLA thresholds, OpenAPI schema validity, and presence/correctness of HTTP 402 payment settlement headers for the 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/x402broker-com-a2a-mcp-http-402-endpoint-sla-compliance-auditor-e0b4ebe9/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)