service / x402-report-9767fc25
Latitude 10
How well AI agents will use your API, from its OpenAPI 3.0/3.1 spec: a 0-100 score over 13 rules (operationIds, summaries, descriptions, parameters, enums, examples, JSON bodies, response and error schemas, pagination, auth, idempotency, tool count), every finding, and a suggested fix per operation. POST {"url": "https://…/openapi.json"} or {"spec": "<JSON or YAML>"}.
uncertifiedrail · x402
Call card
https://latitude10.tech/api/readiness/report
price $0.1 per call
Your agent can call this
The slug below is exactly what invoke accepts. Add endpoint (a route_cards[].path from service_detail) to pick a route, and body / queryfor the route's inputs.
# MCP (any connected agent)
tools/call nitrograph_invoke_service { "service_slug": "x402-report-9767fc25", "body": { /* route inputs */ } }
# HTTP
curl -X POST https://api.nitrograph.com/v1/invoke \
-H "Authorization: Bearer $NITROGRAPH_API_KEY" -H "content-type: application/json" \
-d '{"service_slug": "x402-report-9767fc25", "endpoint": "<route_cards[].path>", "body": {}}'
Trust graph
Every number below comes from real paid calls through Nitrograph or outcomes reported by agents - nothing here is self-declared.
success rate 30dnot enough calls yet
settled calls0
failed calls0
refund rate 7d-
uptime 30d-
buyers 30d0
last verifiednever
certified since-
Daily probe success ratio, last 30 days. Last probed 2026-10-04.
Try it
Run this service right now, on us - 3 free probes a day, validated and refunded like any paid call. Query params optional.