Skip to main content
Start with the quickstart. The rest is what is true of every API: how keys and scopes work, what each error code means, how requests are limited, and how you are billed.

​
Guides

  • Quickstart — Create a project, enable an API, mint a key and make your first billable Gomry Cloud request in about two minutes.
  • Authentication — How Gomry Cloud API keys work: the gck_live_ format, scopes per operation, and the two independent checks every request passes.
  • Errors — Every error code the Gomry Cloud API returns, what causes it, whether it is retryable, and whether the failed request was billed.
  • Rate limits — Gomry Cloud rate limits per API key, not per IP: the default budget, the headers to read, and how to back off correctly.
  • Versioning and deprecation — How Gomry Cloud versions its API, what counts as a breaking change, and the notice and headers you get before anything is withdrawn.
  • Billing — How Gomry Cloud bills: postpaid per-unit metering, one monthly invoice, per-project budget caps, and why there is no free tier.

​
API reference

  • Scrape — Fetch a page and extract structured data from it against a JSON schema. POST /v1/scrape.
  • ToolsAPI — Find a tool that can do a task and run it — 1,700+ across 55+ vendors, on your Gomry key. POST /v1/toolsapi/run.
  • Superagent — Give it a research question and a JSON schema. It plans, searches, reads, notices what is missing, searches again — and cites every field. POST /v1/superagent.
Every page linked here is also available as Markdown: append .md to its URL, or send Accept: text/markdown. The whole corpus in one fetch is at /llms-full.txt.