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

## Facts

- Endpoint: GET https://workflows.agentdiet.dev/v1/paywall-check?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-c4fb1e3d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_SyDmLqnikyoAa3mDBsluw

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

Example prompt: Can you audit https://api.myagent.ai/mcp to check if it's JSON-RPC compliant, meets latency SLAs, has a valid OpenAPI schema, and supports HTTP 402 payment headers?

## When to prefer this

Use this endpoint when you need to programmatically verify that an A2A agent, MCP server, or x402-enabled API is correctly implementing relevant protocol standards before integrating it into a workflow. It is especially valuable when validating HTTP 402 payment header compliance (x402 v2), confirming JSON-RPC correctness, or checking latency SLA before production deployment.

## Known failure modes

- Target URL is unreachable or times out — audit fails with connectivity error
- Target URL does not implement any recognized protocol (A2A, MCP, or x402) — compliance check returns non-compliant with no partial results
- Malformed or missing URL parameter — request rejected with validation error
- Target service returns unexpected HTTP status codes that block audit probes

## 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/paywall-check)

## Output

Returns a compliance audit report covering JSON-RPC protocol conformance, measured latency against SLA thresholds, OpenAPI schema validity, and presence/correctness of HTTP 402 payment settlement headers 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-c4fb1e3d/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)