# 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 a remote agent, MCP, or x402 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/preflight?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-129b6afe
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_aR4fP47o3p73XHcG-wjN_

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-129b6afe
```

Example prompt: Can you audit https://my-mcp-server.example.com/rpc for JSON-RPC compliance, check its latency SLA, and tell me whether it has proper HTTP 402 x402 payment settlement headers?

## When to prefer this

Use this endpoint when you need to verify that a remote A2A agent, MCP server, or x402-enabled service meets protocol standards before integration, deployment, or payment flow activation. It is specifically suited for auditing JSON-RPC compliance, HTTP 402 settlement header correctness, latency SLA, and OpenAPI schema validity in one call — prefer it over generic HTTP probing tools when the target is an AI agent or MCP endpoint.

## Known failure modes

- Target URL is unreachable or times out — audit fails with connectivity error
- Target URL returns non-standard responses that cannot be parsed for compliance
- Missing or malformed 'url' query parameter returns a 400 validation error
- Target service blocks probe requests, resulting in incomplete audit data
- HTTP 402 headers absent at target leads to failed x402 compliance status

## 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/preflight)

## Output

Returns a structured compliance report covering JSON-RPC protocol conformance, measured latency against SLA thresholds, OpenAPI schema validity findings, and HTTP 402 / x402 settlement header presence and correctness for the audited 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-129b6afe/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)