# A2A, MCP & HTTP 402 Endpoint SLA Compliance Auditor

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

Audits any remote 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://shopify-spy.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: shopify-spy.agentdiet.dev
- Website: https://shopify-spy.agentdiet.dev
- Canonical page: https://www.zero.xyz/c/shopify-spy-agentdiet-dev-a2a-mcp-http-402-endpoint-sla-compliance-fe55298f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_r2LakM22Ciea_dmCodoxa

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 shopify-spy-agentdiet-dev-a2a-mcp-http-402-endpoint-sla-compliance-fe55298f
```

Example prompt: Can you audit my MCP server at https://my-agent.example.com/mcp and tell me if it's JSON-RPC compliant, what its latency looks like, and whether it has proper HTTP 402 payment headers set up?

## When to prefer this

Use this endpoint when you need to programmatically verify that a remote MCP server, A2A agent, or x402-paywalled API conforms to protocol standards — specifically JSON-RPC compliance, HTTP 402 payment header correctness, latency SLA, and OpenAPI schema validity — rather than doing a general uptime ping or full security vulnerability scan.

## Known failure modes

- Target URL is unreachable or returns a network timeout
- Malformed or non-HTTP URL provided
- Target service blocks probe requests (e.g. firewall or rate limiting)
- Target returns unexpected content type that cannot be parsed for compliance
- Ambiguous or partial HTTP 402 headers preventing full settlement analysis

## 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://shopify-spy.agentdiet.dev/v1/paywall-check)

## Output

Returns a compliance audit report covering JSON-RPC protocol adherence, measured latency against SLA thresholds, OpenAPI schema validation results, and HTTP 402 payment settlement header inspection for the provided 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/shopify-spy-agentdiet-dev-a2a-mcp-http-402-endpoint-sla-compliance-fe55298f/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from shopify-spy.agentdiet.dev](https://www.zero.xyz/host/shopify-spy.agentdiet.dev/llms.txt)