# A2A, MCP & HTTP 402 Endpoint SLA Compliance Auditor

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

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

## Facts

- Endpoint: GET https://llms-generator.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: llms-generator.agentdiet.dev
- Website: https://llms-generator.agentdiet.dev
- Canonical page: https://www.zero.xyz/c/llms-generator-agentdiet-dev-a2a-mcp-http-402-endpoint-sla-compliance-94a7f22a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ttxaG0aor8lOF85bzssbv

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 llms-generator-agentdiet-dev-a2a-mcp-http-402-endpoint-sla-compliance-94a7f22a
```

Example prompt: Can you audit this MCP server URL for JSON-RPC compliance, latency SLA, OpenAPI schema, and HTTP 402 payment header support: https://my-agent-service.example.com/mcp?

## When to prefer this

Use this endpoint when you need to programmatically verify that a remote A2A, MCP, or HTTP 402 agent service meets protocol standards before integrating it into an agent workflow, or when diagnosing why an existing integration is failing due to compliance or payment header issues. Prefer this over manual inspection or generic HTTP probing tools when you specifically need structured compliance results across JSON-RPC, OpenAPI, SLA, and x402 payment header dimensions in a single call.

## Known failure modes

- Target URL is unreachable or returns a network error — audit fails with connectivity error
- Target URL does not implement any recognized protocol (A2A/MCP/x402) — returns non-compliant result with no structured findings
- Malformed or missing URL parameter — returns validation error
- Target service is too slow to respond within audit timeout — latency SLA marked as failed
- Target URL returns unexpected content type — schema audit returns inconclusive

## 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://llms-generator.agentdiet.dev/v1/paywall-check)

## Output

Returns a compliance audit report for the target URL, including JSON-RPC protocol conformance status, measured latency vs. SLA thresholds, presence and validity of an OpenAPI schema, and analysis of HTTP 402 / x402 v2 settlement headers, along with any detected protocol violations or warnings.

## 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/llms-generator-agentdiet-dev-a2a-mcp-http-402-endpoint-sla-compliance-94a7f22a/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from llms-generator.agentdiet.dev](https://www.zero.xyz/host/llms-generator.agentdiet.dev/llms.txt)