# A2A, MCP & HTTP 402 Endpoint SLA Compliance Auditor

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

Audits a remote A2A agent, MCP server, or x402 URL for JSON-RPC compliance, latency SLA, OpenAPI schema validity, and HTTP 402 settlement header correctness

## Facts

- Endpoint: GET https://agentdiet.dev/v1/preflight?utm_source=zero.xyz
- Price: $0.01/call
- Payment: MPP
- Status: unknown
- Last checked: 2026-10-21
- Activations on Zero: 0
- Provider: agentdiet.dev
- Website: https://agentdiet.dev
- Canonical page: https://www.zero.xyz/c/agentdiet-dev-a2a-mcp-http-402-endpoint-sla-compliance-auditor-a1b5a05c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_z3TUzjdbsnjWsE9a-hRso

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 agentdiet-dev-a2a-mcp-http-402-endpoint-sla-compliance-auditor-a1b5a05c
```

Example prompt: Can you audit https://myagent.example.com/api for A2A and MCP protocol compliance — I want to know if its JSON-RPC is valid, whether it passes latency SLA, and whether the HTTP 402 settlement headers are correctly configured?

## When to prefer this

Use this endpoint when you need to verify that a specific remote URL correctly implements A2A, MCP, or x402/HTTP 402 protocols — especially for pre-integration vetting, debugging payment-gated APIs, or confirming SLA and JSON-RPC compliance before deploying agent infrastructure. Prefer this over generic HTTP health-check tools when the audit needs to cover protocol-specific concerns like x402 settlement headers or JSON-RPC schema conformance.

## Known failure modes

- Target URL is unreachable or times out — audit fails with connectivity error
- Invalid or malformed URL provided — validation error returned
- Target URL does not expose any recognizable A2A/MCP/x402 protocol — partial or empty compliance report
- Remote endpoint returns unexpected non-standard responses — compliance checks may be inconclusive
- Payment failure for the $0.01 per-call fee — request rejected with 402

## 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://agentdiet.dev/v1/preflight)

## Output

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