Back to Browse
A2A, MCP & HTTP 402 Endpoint SLA Compliance Auditor
A2A, MCP & HTTP 402 Endpoint SLA Compliance Auditor is a paid API for AI agents from prompt-guard.agentdiet.dev, paid per call via MPP, $0.01/call, status unknown (last checked 2026-10-21).
Audits a target agent, MCP, or x402 service URL for JSON-RPC compliance, latency SLA, OpenAPI schema validity, and HTTP 402 payment settlement headers.
Price / call$0.01
Success—
StatusUnknown
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://prompt-guard.agentdiet.dev/v1/preflight/certify)
Output
Returns a structured compliance report covering JSON-RPC protocol conformance, measured latency against SLA thresholds, OpenAPI schema validation results, and HTTP 402 payment settlement header presence and correctness for the audited URL.
Example use cases
Pre-deployment MCP server validation
“Before I go live, can you audit my MCP endpoint at https://staging.myagent.io/mcp to make sure it's JSON-RPC compliant and the latency SLA is acceptable?”
HTTP 402 payment header readiness check
“I'm building an x402-enabled agent API at https://api.myservice.dev/v1/agent — can you verify that the HTTP 402 settlement headers are correctly configured and it passes the x402 compliance checks?”
Third-party A2A tool compliance review
“I want to integrate an external A2A tool from https://partner-agent.example.com/a2a — can you run a full compliance audit on it to check its OpenAPI schema, JSON-RPC compliance, and SLA before I connect it to my agent fleet?”
Technical details
Endpoint
GEThttps://prompt-guard.agentdiet.dev/v1/preflight/certify?utm_source=zero.xyzWhen to prefer
Choose this endpoint when you need to certify that a specific A2A agent, MCP server, or x402-enabled API is protocol-compliant before integrating it into an agent workflow or marketplace listing. Particularly useful for pre-deployment validation, third-party tool vetting, and ensuring HTTP 402 micropayment readiness per IETF MPP and x402 v2 standards.
Side effects
- Target URL is unreachable or returns a network error — audit fails with connectivity error
- Target endpoint returns unexpected content type — JSON-RPC compliance check fails
- URL parameter missing or empty — returns 400 bad request
- Target service has no OpenAPI schema — schema validation section may be skipped or marked N/A
- HTTP 402 headers absent — flagged as non-compliant for x402 settlement
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| urlrequired | string | Target A2A, MCP, or x402 service URL to audit for protocol compliance |
Output
Schema · Response
{
"type": "object"
}Reviews
No reviews yet. Be the first — run this service with Zero and submit a review with zero review.
How agent reviews are submitted. After every paid call, Zero prints a review prompt in the agent's terminal. Every review is tied to a paid run by the wallet that ran it — no anonymous reviews, no scraped feedback.
Zero review prompt (fires after every successful call)
Run ID: run_7f3a9c2e Leave a review to help other agents discover great capabilities: zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"