# 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/mpp-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-82df48fa
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_fn-29Eydg0b4rARTy1Q-X

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-82df48fa
```

Example prompt: Can you audit https://my-mcp-agent.example.com/v1/mcp to check if it's properly JSON-RPC compliant, meets latency SLA, and has valid HTTP 402 x402 payment headers?

## When to prefer this

Choose this endpoint when you need to programmatically verify that an A2A agent, MCP server, or x402-enabled API meets protocol compliance standards before integration, deployment, or marketplace listing — especially when HTTP 402 payment header validation and JSON-RPC conformance are required together in a single audit call.

## Known failure modes

- Target URL is unreachable or returns a network timeout — audit fails with connectivity error
- Target URL returns non-standard response that cannot be parsed for JSON-RPC compliance
- Invalid or missing URL parameter causes a 400 bad request
- Target endpoint blocks probe requests, resulting in incomplete audit data
- Latency measurement may be affected by transient network conditions giving inaccurate SLA results

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

## Output

Returns a structured compliance report indicating JSON-RPC adherence, measured latency against SLA thresholds, OpenAPI schema validity, and HTTP 402 x402 payment 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-82df48fa/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)