# A2A, MCP & HTTP 402 Endpoint SLA Compliance Auditor

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

Audits a remote agent, MCP, or x402 URL for JSON-RPC compliance, latency SLA, OpenAPI schema validity, and HTTP 402 payment settlement headers

## Facts

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

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 prompt-guard-agentdiet-dev-a2a-mcp-http-402-endpoint-sla-compliance-1a9cfcb0
```

Example prompt: Can you audit https://my-agent.example.com/mcp to check if it's properly JSON-RPC compliant, meets latency SLAs, has a valid OpenAPI schema, and has the right HTTP 402 settlement headers set up?

## When to prefer this

Use this endpoint when you need to programmatically verify that a remote A2A agent, MCP server, or x402-enabled API meets protocol compliance standards — especially JSON-RPC spec adherence, HTTP 402 payment header correctness, OpenAPI schema validity, and latency SLAs. Prefer it over manual inspection when building automated CI checks, marketplace listing validators, or agent fleet health monitors.

## Known failure modes

- Target URL is unreachable or returns a non-2xx/402 response
- Target URL does not implement JSON-RPC, causing protocol mismatch errors
- Malformed or missing OpenAPI schema at the target endpoint
- Latency SLA thresholds cannot be evaluated if the service is too slow or timing out
- Invalid or missing `url` query parameter returns a validation error
- Target endpoint blocks probe requests due to authentication or firewall rules

## 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://prompt-guard.agentdiet.dev/v1/usdc-quote-audit)

## Output

Returns a structured audit report covering JSON-RPC compliance status, measured latency against SLA thresholds, OpenAPI schema validation findings, and HTTP 402 / x402 settlement header compliance — effectively a pass/fail compliance summary with details per check

## 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/prompt-guard-agentdiet-dev-a2a-mcp-http-402-endpoint-sla-compliance-1a9cfcb0/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from prompt-guard.agentdiet.dev](https://www.zero.xyz/host/prompt-guard.agentdiet.dev/llms.txt)