# A2A, MCP & HTTP 402 Endpoint SLA Compliance Auditor

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

Audits a remote A2A, MCP, or x402 service URL for JSON-RPC compliance, latency SLA, OpenAPI schema validity, and HTTP 402 payment settlement headers.

## Facts

- Endpoint: GET https://token-intel.agentdiet.dev/v1/preflight/certify?utm_source=zero.xyz
- Price: $0.01/call
- Payment: MPP
- Status: unknown
- Last checked: 2026-10-22
- Activations on Zero: 0
- Provider: token-intel.agentdiet.dev
- Website: https://token-intel.agentdiet.dev
- Canonical page: https://www.zero.xyz/c/token-intel-agentdiet-dev-a2a-mcp-http-402-endpoint-sla-compliance-427df2f1
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_cFuUMBe04_SOqbO9htr3y

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 token-intel-agentdiet-dev-a2a-mcp-http-402-endpoint-sla-compliance-427df2f1
```

Example prompt: Can you run a compliance audit on https://my-agent-service.example.com/mcp and tell me whether it passes JSON-RPC validation, meets latency SLA, has a valid OpenAPI schema, and properly handles HTTP 402 payment headers?

## When to prefer this

Use this endpoint when you need to validate that a remote A2A, MCP, or x402-enabled service URL meets protocol standards before integration, deployment, or payment routing — especially when you need simultaneous coverage of JSON-RPC compliance, SLA latency, OpenAPI schema, and HTTP 402 settlement headers in a single audit call rather than running separate checks.

## Known failure modes

- Target URL unreachable — endpoint returns error indicating the remote service could not be contacted
- Invalid URL format provided — validation fails before audit begins
- Target service returns non-JSON-RPC responses — compliance flagged as failed
- Latency SLA exceeded — report shows failure threshold breach
- HTTP 402 headers absent or malformed — payment compliance marked as non-conformant
- Generic object response schema makes it hard to predict exact error structure

## 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://token-intel.agentdiet.dev/v1/preflight/certify)

## Output

Returns a structured compliance report covering: JSON-RPC protocol conformance, measured latency against SLA thresholds, OpenAPI schema presence and validity, and HTTP 402/x402 payment settlement header correctness — effectively a pass/fail certification for the audited endpoint.

## 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/token-intel-agentdiet-dev-a2a-mcp-http-402-endpoint-sla-compliance-427df2f1/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from token-intel.agentdiet.dev](https://www.zero.xyz/host/token-intel.agentdiet.dev/llms.txt)