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

## Facts

- Endpoint: GET https://workflows.agentdiet.dev/v1/bazaar-verifier?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-fcd0ca2d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_bDXQWbo-Bm8fwbTF0l3Iv

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

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

## When to prefer this

Choose this endpoint when you need to programmatically verify that an A2A agent, MCP server, or HTTP 402 x402 service conforms to protocol standards before integrating it into a workflow, deploying it to production, or listing it in a marketplace. It is especially useful for validating third-party agent endpoints you do not control, or confirming your own endpoint meets SLA and payment protocol requirements.

## Known failure modes

- Target URL is unreachable or returns a network error — audit fails with connection error
- Target URL returns non-standard responses that cannot be parsed for JSON-RPC compliance
- SLA measurement may be affected by transient network latency rather than the target service itself
- Malformed or missing OpenAPI spec at the target URL results in schema validation being skipped or errored
- x402 header inspection may return false negatives if the target requires authentication before returning 402

## 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/bazaar-verifier)

## Output

Returns a structured compliance audit report covering: JSON-RPC spec conformance, measured latency vs SLA thresholds, OpenAPI schema validity findings, and HTTP 402 x402 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/workflows-agentdiet-dev-a2a-mcp-http-402-endpoint-sla-compliance-fcd0ca2d/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)