# 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 server, or x402 URL for JSON-RPC compliance, latency SLA, OpenAPI schema validity, and HTTP 402 payment settlement headers.

## Facts

- Endpoint: GET https://workflows.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: 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-e8caded8
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_2zosjADu6lLUCEj61wKAQ

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-e8caded8
```

Example prompt: Can you audit https://api.myagent.example.com/mcp for JSON-RPC compliance, latency SLA, OpenAPI schema validity, and HTTP 402 settlement headers?

## When to prefer this

Use this endpoint when you need to programmatically verify that an A2A agent, MCP server, or x402-enabled URL meets protocol compliance standards before integrating, deploying, or paying for its services. It is the right choice when you want a single-call audit covering JSON-RPC, OpenAPI, latency SLA, and HTTP 402 headers together, rather than manually probing each concern separately.

## Known failure modes

- Target URL unreachable or returns non-2xx/402 status — audit may partially fail or return connectivity error
- Invalid or malformed URL input — returns validation error
- Target server times out before SLA measurement completes — latency result may be incomplete
- Endpoint does not implement JSON-RPC or OpenAPI — audit returns non-compliant flags rather than an error
- Rate limiting or auth on the target URL blocks the audit probe

## 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/x402-audit)

## Output

Returns a structured audit report covering: JSON-RPC compliance status, latency SLA measurements, OpenAPI schema validity, and HTTP 402 / x402 settlement header inspection 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/workflows-agentdiet-dev-a2a-mcp-http-402-endpoint-sla-compliance-e8caded8/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)