# A2A, MCP & HTTP 402 Endpoint SLA Compliance Auditor

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

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

## Facts

- Endpoint: POST https://alpha-stream.agentdiet.dev/v1/x402-mpp-paywall-verifier?utm_source=zero.xyz
- Price: $0.01/call
- Payment: MPP
- Status: unknown
- Last checked: 2026-11-21
- Activations on Zero: 0
- Provider: alpha-stream.agentdiet.dev
- Website: https://alpha-stream.agentdiet.dev
- Canonical page: https://www.zero.xyz/c/alpha-stream-agentdiet-dev-a2a-mcp-http-402-endpoint-sla-compliance-758ab65a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_G-19mZlOuRQcSEJhR4g0p

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 alpha-stream-agentdiet-dev-a2a-mcp-http-402-endpoint-sla-compliance-758ab65a -d '<json body>'
```

Example prompt: Can you audit this MCP endpoint for me — https://myagent.example.com/mcp — and tell me if it's JSON-RPC compliant, whether it passes latency SLA, and whether its HTTP 402 x402 payment headers are correctly configured?

## When to prefer this

Use this endpoint when you need to programmatically verify whether any A2A, MCP, or HTTP 402 service URL is protocol-compliant before integration, during CI/CD pipeline checks, or when debugging agent-to-agent communication failures. Especially valuable when working with x402 micropayment-gated APIs where settlement header correctness is critical.

## Known failure modes

- Target URL is unreachable or returns a network error
- Target endpoint does not respond within latency SLA window
- Malformed or missing URL input returns a 400 validation error
- Target endpoint blocks probing requests with authentication requirements
- Incomplete or unexpected response schema from target causes parsing failure

## 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://alpha-stream.agentdiet.dev/v1/x402-mpp-paywall-verifier)

## Output

Returns a compliance report covering JSON-RPC conformance status, measured latency against SLA thresholds, OpenAPI schema validation results, and HTTP 402 x402 payment settlement header inspection 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/alpha-stream-agentdiet-dev-a2a-mcp-http-402-endpoint-sla-compliance-758ab65a/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from alpha-stream.agentdiet.dev](https://www.zero.xyz/host/alpha-stream.agentdiet.dev/llms.txt)
