Readiness Report
by Latitude 10 in Weather & location
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>"}.
https://latitude10.tech/api/readiness/report- Price
- $0.1
- per call in USDC
- Uptime
- 100%
- last 30 days
- Response time
- 1.1 s
- 2.1 s slowest 5%
- Last check
- Passed
- 2 h ago, next in 3 h
Reliability
Status and outage history · Atom feed · Watch with other listings
How to call it
POST https://latitude10.tech/api/readiness/report
Each call costs $0.1 in USDC on Base, paid with the request over x402.
Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.
Example request
From the listing.
POST https://latitude10.tech/api/readiness/report
content-type: application/json
{
"url": "https://api.example.com/openapi.json"
}Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
spec | string or object | No | The OpenAPI document itself, as JSON or YAML text or as an object. Send url or spec, not both. |
url | string (uri) | No | https URL of the OpenAPI 3.0 or 3.1 document (JSON or YAML, up to 2 MB). |
Example response
The provider's example. We can't check it without paying.
Example response, 44 lines
{
"api": {
"openapi": "3.1.0",
"title": "Orders API",
"version": "1.0.0"
},
"findings": [
{
"message": "no description",
"rule": "descriptions",
"where": "GET /orders"
}
],
"findingsTotal": 31,
"operations": 5,
"payment": {
"network": "eip155:8453",
"transaction": "0x…"
},
"report": "agent-readiness-report",
"rules": [
{
"applicable": 5,
"fix": "…",
"id": "descriptions",
"passing": 0,
"title": "Descriptions say what the operation does, when to use it, and what it returns",
"weight": 10
}
],
"score": 54,
"source": "https://api.example.com/openapi.json",
"suggestions": [
{
"description": "Lists orders, filtered and paged with status, limit, cursor. …",
"fields": [
"description"
],
"operation": "GET /orders",
"tool": "listOrders"
}
],
"verdict": "Agents will struggle with this API as it is."
}Call it from code
The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.1.
curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i -X POST 'https://latitude10.tech/api/readiness/report' \
-H 'content-type: application/json' \
--data-raw '{"url":"https://api.example.com/openapi.json"}'
# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - -X POST 'https://latitude10.tech/api/readiness/report' \
-H 'content-type: application/json' \
--data-raw '{"url":"https://api.example.com/openapi.json"}' \
| grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decodeJavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";
// Pays at most $0.1 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.1" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);
// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.1 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Flatitude10.tech%2Fapi%2Freadiness%2Freport&method=POST
const res = await pay("https://latitude10.tech/api/readiness/report", {
method: "POST",
headers: { "content-type": "application/json" },
body: JSON.stringify({
"url": "https://api.example.com/openapi.json"
}),
});
console.log(res.status, await res.text());Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client
# Pays at most $0.1 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.1"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))
with x402_requests(client) as session:
res = session.post(
"https://latitude10.tech/api/readiness/report",
json={
"url": "https://api.example.com/openapi.json",
},
)
print(res.status_code, res.text)Security scan
No findings
We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time | Price |
|---|---|---|---|---|
| 2 h ago | Passed | 402 | 1.4 s | $0.1 |
| 13 h ago | Passed | 402 | 567 ms | $0.1 |
| 24 h ago | Passed | 402 | 311 ms | $0.1 |
| 35 h ago | Passed | 402 | 1.3 s | $0.1 |
| 46 h ago | Passed | 402 | 598 ms | $0.1 |
Show 10 older checks
| 2 days ago | Passed | 402 | 1.1 s | $0.1 |
| 3 days ago | Passed | 402 | 1.1 s | $0.1 |
| 3 days ago | Passed | 402 | 333 ms | $0.1 |
| 4 days ago | Passed | 402 | 1.2 s | $0.1 |
| 4 days ago | Passed | 402 | 1.1 s | $0.1 |
| 5 days ago | Passed | 402 | 1.5 s | $0.1 |
| 5 days ago | Passed | 402 | 318 ms | $0.1 |
| 5 days ago | Passed | 402 | 272 ms | $0.1 |
| 6 days ago | Passed | 402 | 1.4 s | $0.1 |
| 6 days ago | Passed | 402 | 1.2 s | $0.1 |