{"uid":"cap_gG1W0YnDVITx7kHoQ3C2i","slug":"serp-extract-agentdiet-dev-a2a-mcp-http-402-endpoint-sla-compliance-4341546c","name":"A2A, MCP & HTTP 402 Endpoint SLA Compliance Auditor","description":"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://serp-extract.agentdiet.dev/v1/bazaar-verifier)","url":"https://serp-extract.agentdiet.dev/v1/bazaar-verifier?utm_source=zero.xyz","method":"GET","headers":{},"bodySchema":{"type":"object","required":["url"],"properties":{"url":{"type":"string","minLength":1,"description":"Target A2A, MCP, or x402 service URL to audit for protocol compliance"},"limit":{"type":"integer","default":20,"maximum":100,"minimum":1,"description":"Maximum number of items to return per page (1-100)"},"cursor":{"type":"string","description":"Opaque pagination cursor for fetching the next page"}}},"responseSchema":{"type":"object"},"example":null,"exampleRequest":null,"tags":[],"displayCostAmount":"0.01","displayCostAsset":"USD","priceDynamic":false,"priceHint":null,"priceStatus":"priced","priceSource":"probe","requiresHandshake":false,"reviewCount":0,"rating":{"score":"0.00","successRate":"0.00","reviews":0,"stars":null,"state":"unrated"},"availabilityStatus":"unknown","priceObserved":null,"sessionDeposit":null,"pricing":{"kind":"static","summary":"$0.01/call","primary":{"kind":"static","protocol":"mpp","network":"tempo","amountUsd":"0.01","per":"call","confidence":"exact"},"accepted":[{"kind":"static","protocol":"mpp","network":"tempo","amountUsd":"0.01","per":"call","confidence":"exact"}]},"paymentMethods":[{"uid":"pm_Y-z8jKfaaLV_1PbilCBLm","protocol":"mpp","methodType":"crypto","chain":"tempo","mode":"charge","costAmount":"0.01","costPer":"request","priority":0,"asset":"0x833589fcd6edb6e08f4c7c32d4f71b54bda02913","unit":"request","depositMicros":null,"planRef":null}],"brandName":"serp-extract.agentdiet.dev","brandSlug":"serp-extract-agentdiet-dev-mpp","brandBaseUrl":"https://serp-extract.agentdiet.dev","brandDocsUrl":null,"whatItDoes":"Audits any A2A agent, MCP, or x402 service URL for JSON-RPC protocol compliance, latency SLA, OpenAPI schema validity, and HTTP 402 payment settlement headers","exampleAgentPrompt":"Can you audit https://my-agent-service.example.com/mcp to check if it's JSON-RPC compliant, passes latency SLA, has a valid OpenAPI schema, and returns the right HTTP 402 payment settlement headers?","exampleUseCases":[{"title":"Pre-launch MCP server compliance check","prompt":"Before I publish my MCP server, can you audit https://tools.mycompany.com/mcp to confirm it's fully JSON-RPC compliant, has acceptable latency, and exposes proper OpenAPI schema?"},{"title":"Verify x402 payment headers on agent API","prompt":"I just deployed an x402-enabled agent at https://payments.mybot.dev/v1/agent — can you check that it returns the correct HTTP 402 settlement headers and is IETF MPP compliant?"},{"title":"SLA health check on third-party A2A tool","prompt":"We're about to integrate a third-party agent at https://partner-tools.ai/a2a — can you run a full compliance audit to see if it meets our latency SLA requirements and is properly JSON-RPC spec compliant?"}],"resultDescription":"Returns a structured audit report covering JSON-RPC protocol compliance status, measured latency against SLA thresholds, OpenAPI schema validation findings, and HTTP 402 payment settlement header correctness for the target agent or MCP URL","failureModes":["Target URL is unreachable or returns a network timeout — audit fails with connectivity error","URL does not expose any recognized A2A, MCP, or x402 protocol — compliance fields returned as non-compliant","Malformed or missing OpenAPI spec at target — schema validation returns failure with details","Target service rate-limits the auditor probe — latency SLA measurement may be inaccurate","Invalid or missing URL parameter — request rejected with validation error"],"whenToPreferThis":"Choose this endpoint when you need to programmatically verify that a remote A2A agent, MCP server, or x402 payment-enabled API meets protocol compliance standards including JSON-RPC correctness, latency SLAs, OpenAPI schema validity, and HTTP 402 settlement headers — especially before integrating a third-party agent into a production swarm or publishing your own agent to a marketplace.","instructions":null,"reviewSummary":null,"reviewSummaryHighlights":null,"reviewSummaryConcerns":null,"reviewSummaryGeneratedAt":null,"activationCount":0,"lastUsedAt":null,"lastSuccessfullyRanAt":null,"lastHealthCheckAt":"2026-10-21T07:20:44.603Z","isFirstParty":false,"canonicalSlug":"serp-extract-agentdiet-dev-a2a-mcp-http-402-endpoint-sla-compliance-100ccc18"}