# A2A, MCP & HTTP 402 Endpoint SLA Compliance Auditor

> A2A, MCP & HTTP 402 Endpoint SLA Compliance Auditor is a paid API for AI agents from github-audit.agentdiet.dev, 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://github-audit.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: github-audit.agentdiet.dev
- Website: https://github-audit.agentdiet.dev
- Canonical page: https://www.zero.xyz/c/github-audit-agentdiet-dev-a2a-mcp-http-402-endpoint-sla-compliance-835a8459
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_rd1YyzozxQ7E96q4-fdKU

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 github-audit-agentdiet-dev-a2a-mcp-http-402-endpoint-sla-compliance-835a8459
```

Example prompt: Can you audit https://myagent.example.com/mcp for JSON-RPC compliance, latency SLA, and HTTP 402 payment headers, and tell me if it passes all protocol checks?

## When to prefer this

Choose this endpoint when you need to verify that a remote agent, MCP server, or x402-enabled API meets protocol compliance standards before integrating it into an agent workflow, when debugging HTTP 402 payment header issues, or when checking SLA latency and JSON-RPC conformance of agent infrastructure.

## Known failure modes

- Target URL is unreachable or returns a network error
- Target URL does not implement any recognized protocol (A2A, MCP, x402), returning empty or irrelevant compliance results
- Malformed URL input causes a validation error
- Target endpoint has rate limiting that interferes with probing
- Ambiguous or incomplete OpenAPI schema at target makes schema validation 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://github-audit.agentdiet.dev/v1/paywall-scanner)

## Output

Returns a compliance audit report covering JSON-RPC protocol conformance, measured latency against SLA thresholds, OpenAPI schema validation results, and HTTP 402 settlement header presence and correctness 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/github-audit-agentdiet-dev-a2a-mcp-http-402-endpoint-sla-compliance-835a8459/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from github-audit.agentdiet.dev](https://www.zero.xyz/host/github-audit.agentdiet.dev/llms.txt)