# 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-21).

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

## Facts

- Endpoint: GET https://serp-extract.agentdiet.dev/v1/bazaar-verifier?utm_source=zero.xyz
- Price: $0.01/call
- Payment: MPP
- Status: unknown
- Last checked: 2026-10-21
- 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-4341546c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_gG1W0YnDVITx7kHoQ3C2i

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-4341546c
```

Example prompt: Can you audit https://my-agent-service.example.com/mcp to check if it's JSON-RPC compliant, passes latency SLA, has a valid OpenAPI schema, and returns the right HTTP 402 payment settlement headers?

## When to prefer this

Choose this endpoint when you need to programmatically verify that a remote A2A agent, MCP server, or x402 payment-enabled API meets protocol compliance standards including JSON-RPC correctness, latency SLAs, OpenAPI schema validity, and HTTP 402 settlement headers — especially before integrating a third-party agent into a production swarm or publishing your own agent to a marketplace.

## Known failure modes

- Target URL is unreachable or returns a network timeout — audit fails with connectivity error
- URL does not expose any recognized A2A, MCP, or x402 protocol — compliance fields returned as non-compliant
- Malformed or missing OpenAPI spec at target — schema validation returns failure with details
- Target service rate-limits the auditor probe — latency SLA measurement may be inaccurate
- Invalid or missing URL parameter — request rejected with 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/bazaar-verifier)

## Output

Returns a structured audit report covering JSON-RPC protocol compliance status, measured latency against SLA thresholds, OpenAPI schema validation findings, and HTTP 402 payment settlement header correctness for the target agent or MCP 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"
  },
  "limit": {
   "type": "integer",
   "default": 20,
   "maximum": 100,
   "minimum": 1,
   "description": "Maximum number of items to return per page (1-100)"
  },
  "cursor": {
   "type": "string",
   "description": "Opaque pagination cursor for fetching the next page"
  }
 }
}
```

## 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-4341546c/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)