# A2A, MCP & HTTP 402 Endpoint SLA Compliance Auditor

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

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

## Facts

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

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

Example prompt: Can you audit this MCP endpoint for me — https://tools.example.com/mcp — and tell me if it's JSON-RPC compliant, whether it passes latency SLA, and whether its HTTP 402 payment headers are set up correctly?

## When to prefer this

Use this endpoint when you need to programmatically verify that an A2A agent, MCP server, or x402-enabled service meets JSON-RPC protocol standards, SLA latency thresholds, OpenAPI schema requirements, and HTTP 402 payment header specs — especially before integrating a third-party tool into an agent workflow or before listing a service on an agent marketplace.

## Known failure modes

- Target URL is unreachable or returns a network error
- Target service does not respond within latency timeout window
- URL does not expose any recognizable A2A, MCP, or x402 protocol surface
- Malformed or missing OpenAPI schema causes schema validation to fail
- HTTP 402 headers absent or misconfigured, flagged as non-compliant
- Invalid or missing 'url' query parameter returns a 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://mesh.agentdiet.dev/v1/x402-audit)

## Output

Returns a structured audit report covering JSON-RPC compliance status, measured latency vs SLA thresholds, OpenAPI schema validation results, and HTTP 402 x402 payment settlement header presence and 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/mesh-agentdiet-dev-a2a-mcp-http-402-endpoint-sla-compliance-auditor-9c319f30/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from mesh.agentdiet.dev](https://www.zero.xyz/host/mesh.agentdiet.dev/llms.txt)