# 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 adherence, OpenAPI schema validity, and HTTP 402 payment settlement headers.

## Facts

- Endpoint: GET https://prompt-guard.agentdiet.dev/v1/x402-verifier?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-4bea7f04
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_s9Q7WYk5866lxP0oCmhKD

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-4bea7f04
```

Example prompt: Can you audit my MCP endpoint at https://myagent.example.com/mcp and tell me if it passes JSON-RPC compliance, latency SLA, OpenAPI schema checks, and HTTP 402 settlement header validation?

## When to prefer this

Choose this endpoint when you need to programmatically verify that a remote A2A agent, MCP server, or x402-enabled service correctly implements JSON-RPC, meets latency SLAs, exposes a valid OpenAPI schema, and has properly configured HTTP 402 payment headers — especially before integrating or deploying agent-to-agent workflows that depend on these protocol guarantees.

## Known failure modes

- Target URL is unreachable or times out, resulting in a connectivity error
- Target URL returns unexpected content type, making JSON-RPC compliance check fail
- Missing or malformed HTTP 402 headers cause payment compliance to fail
- OpenAPI schema absent or invalid at the target, resulting in schema check failure
- Invalid or empty 'url' parameter returns a 400 bad request 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://prompt-guard.agentdiet.dev/v1/x402-verifier)

## Output

Returns a compliance report object covering: JSON-RPC protocol conformance, latency SLA pass/fail with timing data, OpenAPI schema validity assessment, and HTTP 402 / x402 settlement header correctness for the audited 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/prompt-guard-agentdiet-dev-a2a-mcp-http-402-endpoint-sla-compliance-4bea7f04/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)