# A2A, MCP & HTTP 402 Endpoint SLA Compliance Auditor

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

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 domain-osint-agentdiet-dev-a2a-mcp-http-402-endpoint-sla-compliance-3d4c7f17
```

Example prompt: Can you audit the MCP endpoint at https://myagent.example.com/mcp to check if it's JSON-RPC compliant, meets latency SLAs, has a valid OpenAPI schema, and properly returns HTTP 402 payment headers?

## When to prefer this

Use this endpoint when you need to programmatically verify whether a remote A2A agent, MCP server, or x402 paywall endpoint correctly implements protocol standards including JSON-RPC, OpenAPI schemas, latency SLAs, and HTTP 402 payment headers — especially before integrating a third-party agent or deploying your own.

## Known failure modes

- Target URL is unreachable or times out — returns connectivity error
- Target URL does not implement any recognized protocol — returns non-compliant status
- Invalid or malformed URL input — returns validation error
- Target service blocks automated probes — may return incomplete or failed audit
- Upstream service at agentdiet.dev unavailable — returns 5xx error

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

## Output

Returns a compliance report covering JSON-RPC protocol adherence, measured latency against SLA thresholds, OpenAPI schema presence and validity, and HTTP 402 payment header 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/domain-osint-agentdiet-dev-a2a-mcp-http-402-endpoint-sla-compliance-3d4c7f17/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from domain-osint.agentdiet.dev](https://www.zero.xyz/host/domain-osint.agentdiet.dev/llms.txt)