# A2A, MCP & HTTP 402 Endpoint SLA Compliance Auditor

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

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

## Facts

- Endpoint: GET https://workflows.agentdiet.dev/v1/preflight/certify?utm_source=zero.xyz
- Price: $0.01/call
- Payment: MPP
- Status: unknown
- Last checked: 2026-10-21
- Activations on Zero: 0
- Provider: workflows.agentdiet.dev
- Website: https://workflows.agentdiet.dev
- Canonical page: https://www.zero.xyz/c/workflows-agentdiet-dev-a2a-mcp-http-402-endpoint-sla-compliance-5596c142
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_-lZlFtU8oL3FMgGBm-9th

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 workflows-agentdiet-dev-a2a-mcp-http-402-endpoint-sla-compliance-5596c142
```

Example prompt: Can you run a full compliance audit on https://my-agent.example.com/mcp — I want to know if it passes JSON-RPC spec, meets latency SLA, has valid OpenAPI schema, and has the correct HTTP 402 x402 settlement headers?

## When to prefer this

Choose this endpoint when you need to verify that a remote A2A agent, MCP server, or x402 service is protocol-compliant before integrating it into a workflow or swarm — especially when you need to check JSON-RPC spec adherence, latency SLA, OpenAPI schema correctness, and HTTP 402 payment header configuration in a single call. Prefer it over manual curl-based probing or generic HTTP health checks when A2A/MCP/x402 protocol semantics matter.

## Known failure modes

- Target URL is unreachable or times out — returns connectivity error
- Target URL does not implement any recognized protocol (A2A/MCP/x402) — returns unsupported protocol result
- Malformed or missing URL parameter — returns validation error
- Target service returns unexpected non-standard responses — partial compliance report with warnings
- Rate limiting or payment failure on the auditor endpoint itself — returns 402 or 429 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://workflows.agentdiet.dev/v1/preflight/certify)

## Output

Returns a structured compliance report for the target URL covering: JSON-RPC protocol conformance, measured latency vs SLA thresholds, OpenAPI schema validity, and HTTP 402/x402 settlement header correctness — effectively a pass/fail certificate for agent protocol readiness.

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