# A2A, MCP & HTTP 402 Endpoint SLA Compliance Auditor

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

Audits a 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://hn-pulse.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: hn-pulse.agentdiet.dev
- Website: https://hn-pulse.agentdiet.dev
- Canonical page: https://www.zero.xyz/c/hn-pulse-agentdiet-dev-a2a-mcp-http-402-endpoint-sla-compliance-auditor-837c6c4e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_MwloA9VxhaTGB9pWAV2mM

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 hn-pulse-agentdiet-dev-a2a-mcp-http-402-endpoint-sla-compliance-auditor-837c6c4e
```

Example prompt: Can you audit my MCP server at https://my-agent.example.com/mcp and tell me if it's passing JSON-RPC compliance, meeting latency SLAs, and has the HTTP 402 payment headers set up correctly?

## When to prefer this

Choose this endpoint when you need to programmatically verify that a remote agent endpoint, MCP server, or x402 payment service correctly implements protocol standards — especially JSON-RPC compliance, HTTP 402 settlement headers, OpenAPI schema, and latency SLAs. Prefer it over generic HTTP health-checkers when the target is specifically an AI agent or MCP tool endpoint and protocol-level correctness is required.

## Known failure modes

- Target URL is unreachable or returns a connection error
- Target URL is not an A2A, MCP, or x402 endpoint and produces irrelevant audit results
- Malformed or missing URL parameter returns a validation error
- Target endpoint enforces access controls that block the auditor probe
- Partial results returned if the target times out during latency measurement

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

## Output

Returns a compliance report object covering: JSON-RPC spec conformance, measured latency vs SLA thresholds, OpenAPI schema validation results, and HTTP 402 / x402 settlement header presence and correctness 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/hn-pulse-agentdiet-dev-a2a-mcp-http-402-endpoint-sla-compliance-auditor-837c6c4e/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from hn-pulse.agentdiet.dev](https://www.zero.xyz/host/hn-pulse.agentdiet.dev/llms.txt)