Every fleet endpoint answers common questions with a small set of exact parameters — but until now you had to guess them. Pick a template below: a plain-language question, the exact params object that answers it, and a copy-paste curl. Every template was traced from the endpoint's own declared schema or server code (the same derivation as the request schema page) — param names, required params and enum values are never invented. Free-form values (a query, a domain, a ticker) are realistic examples; swap in your own. Endpoints that read no input carry one params: {} template; the document endpoint is a multipart upload and says so honestly.
Library — served live by GET /clinic/query-templates from the fleet catalogue, so URLs and prices never drift.
Loading library…
GET https://api.mekongtradeintel.com/clinic/query-templates
-> { ok: true, template_count, endpoint_count, endpoints: [...], usage }
GET https://api.mekongtradeintel.com/clinic/query-templates?endpoint=macro
-> { ok: true, endpoint: "macro", count: 4,
templates: [ { id: "macro-cpi", question: "What is the latest US CPI
inflation reading?", params: { indicator: "cpi" }, method: "GET",
price_usd: 0.002, endpoint_url: "...", curl: "curl ..." }, ... ] }
GET https://api.mekongtradeintel.com/clinic/query-templates?q=cpi
GET https://api.mekongtradeintel.com/clinic/query-templates?all=1
GET https://api.mekongtradeintel.com/clinic/query-templates?format=md
Check a concrete input against an endpoint's declared schema before paying with POST /clinic/validate-input, and read the schema itself at GET /clinic/request-schema?endpoint=<slug>.
Request schema — parameters and valid enum values per endpoint · Input validator — check a sample input before paying · Cheapest-answer routing — state a need, get the cheapest route · Demand digest — trial-demand data for other x402 sellers