# A2A, MCP & HTTP 402 Endpoint SLA Compliance Auditor

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

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

## Facts

- Endpoint: POST https://serp-extract.agentdiet.dev/v1/preflight?utm_source=zero.xyz
- Price: $0.01/call
- Payment: MPP
- Status: unknown
- Last checked: 2026-10-23
- Activations on Zero: 0
- Provider: serp-extract.agentdiet.dev
- Website: https://serp-extract.agentdiet.dev
- Canonical page: https://www.zero.xyz/c/serp-extract-agentdiet-dev-a2a-mcp-http-402-endpoint-sla-compliance-9d4513c8
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_rUVNTG8lcyAk7j9J2dDul

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 serp-extract-agentdiet-dev-a2a-mcp-http-402-endpoint-sla-compliance-9d4513c8 -d '<json body>'
```

Example prompt: Can you audit the endpoint at https://myagent.example.com/mcp and tell me if it passes JSON-RPC compliance, meets latency SLA, has valid OpenAPI schema, and has the right HTTP 402 payment headers set up?

## When to prefer this

Use this endpoint when you need to verify that an A2A agent, MCP server, or x402 payment endpoint meets protocol standards before integration or deployment — especially when checking JSON-RPC compliance, HTTP 402 settlement headers, OpenAPI schema validity, and latency SLA in a single call. Prefer this over general uptime monitors or HTTP probes when protocol-level and payment-header compliance is the concern.

## Known failure modes

- Target URL unreachable or DNS resolution failure
- Target endpoint returns non-JSON or malformed response
- Latency measurement timeout if remote service is too slow
- Invalid or missing HTTP 402 headers result in partial audit failure
- Input URL missing or too short triggers schema validation 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://serp-extract.agentdiet.dev/v1/preflight)

## Output

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