# A2A, MCP & HTTP 402 Endpoint SLA Compliance Auditor

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

Audits any 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://defi-yield.agentdiet.dev/v1/x402-verifier?utm_source=zero.xyz
- Price: $0.01/call
- Payment: MPP
- Status: unknown
- Last checked: 2026-10-21
- Activations on Zero: 0
- Provider: defi-yield.agentdiet.dev
- Website: https://defi-yield.agentdiet.dev
- Canonical page: https://www.zero.xyz/c/defi-yield-agentdiet-dev-a2a-mcp-http-402-endpoint-sla-compliance-5773896a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_GwgqKnd9Eqq59sGS6FDWy

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 defi-yield-agentdiet-dev-a2a-mcp-http-402-endpoint-sla-compliance-5773896a
```

Example prompt: Can you audit https://my-agent.example.com/api for JSON-RPC compliance, latency SLA, and HTTP 402 payment header support — I want to know if it meets A2A and MCP protocol standards?

## When to prefer this

Choose this endpoint when you need to programmatically verify that an A2A agent, MCP server, or x402-enabled service conforms to JSON-RPC, OpenAPI, IETF MPP, and HTTP 402 payment protocol standards — especially before integrating a third-party agent, deploying a new MCP server, or confirming x402 v2 settlement header correctness. It is the right choice over generic HTTP probers or OpenAPI linters when the target combines agent protocols with payment-layer compliance requirements.

## Known failure modes

- Target URL is unreachable or times out — returns connectivity error
- Target URL does not expose a JSON-RPC or OpenAPI interface — partial or null compliance scores
- Malformed or missing URL parameter — returns validation error
- Target service returns unexpected HTTP status codes — flagged in report
- x402 headers absent on a payment-gated endpoint — reported as non-compliant

## 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://defi-yield.agentdiet.dev/v1/x402-verifier)

## Output

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