# A2A, MCP & HTTP 402 Endpoint SLA Compliance Auditor

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

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 company-enrich-agentdiet-dev-a2a-mcp-http-402-endpoint-sla-compliance-9c998cc9
```

Example prompt: Can you audit this MCP server URL — https://myagent.example.com/mcp — and tell me whether it's JSON-RPC compliant, what its latency looks like, and whether it properly returns HTTP 402 payment headers?

## When to prefer this

Use this endpoint when you need to programmatically verify that a remote agent, MCP server, or x402 paywall URL meets protocol standards before integration or deployment — especially when checking HTTP 402 payment header compliance, JSON-RPC correctness, or latency SLA. Prefer this over generic HTTP testing tools when the target is specifically an AI agent or MCP endpoint.

## Known failure modes

- Target URL is unreachable or times out — returns error with connection failure details
- Target URL does not implement any recognized protocol (A2A/MCP/x402) — returns partial or empty compliance results
- Malformed or missing URL parameter — returns 400 bad request
- Target URL returns unexpected HTTP status codes that prevent auditing — compliance fields may be null or incomplete

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

## Output

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