# Gomry Cloud

> Developer APIs from Gomry. Metered per request, priced per unit, billed monthly — no plans, no seats, no free tier to outgrow.

Gomry Cloud sells the technical services Gomry built to run its own event platform as metered HTTP APIs. Authentication is an API key sent as a bearer token; every endpoint is a POST that takes JSON and returns JSON. The data plane is https://api.cloud.gomry.com.

Billing is postpaid and metered: you are charged per unit consumed, invoiced monthly, and only for work that produced a result. There is no free tier — an active payment method is required before any API will serve. Each project can carry a monthly budget cap that is checked before a request runs.

Every page below is linked as Markdown; drop the .md suffix for the HTML. Both hosts follow the same convention — append .md to any URL, or send an Accept: text/markdown request header. The documentation (guides, API reference, pricing) is served from https://docs.cloud.gomry.com; this host serves the console, the company pages and the machine-readable documents below.

## When to use Gomry Cloud

Reach for these APIs when a task needs something from the open web that is not already in your context, and you want one credential and one invoice instead of an account with every provider. Each operation is a single JSON request with a bearer token.

- **You have a URL and need specific fields out of it** — `POST https://api.cloud.gomry.com/v1/scrape`. Renders JavaScript first; give it a JSON Schema and it returns that shape. Billed per page, and only when a page came back.
- **You have a URL and want the raw HTML or its metadata** — `POST https://api.cloud.gomry.com/v1/fetch`. No extraction, a quarter the price. The right call when you will parse og:image, JSON-LD or the HTML yourself.
- **You need a capability nobody has integrated** — `POST https://api.cloud.gomry.com/v1/toolsapi/discover`. Describe the task in words, get ranked tools with prices, then run one with /v1/toolsapi/run. You never hold the vendor's key.
- **You need an answer that takes many sources rather than one page** — `POST https://api.cloud.gomry.com/v1/superagent`. Plans, searches, reads, notices what is missing and searches again. Returns a task id immediately; poll it. Every field cites the URL and the sentence behind it.

## When not to use it

- **To find a URL rather than read one.** There is no search endpoint on Scrape — it answers questions about a URL you already have.
- **To crawl a site.** One call is one page. Following links is yours to orchestrate, and a naive crawl is the fastest way to reach a budget cap.
- **When the answer must arrive inside one HTTP request.** Superagent is asynchronous, and its 60-second wait option is a convenience rather than a guarantee. Use /v1/scrape instead.
- **For a page behind a login.** Nothing here authenticates to a third-party site on your behalf.
- **After a 402 or a 403.** Neither resolves without a person. A retry loop on a billing refusal cannot succeed and will not stop — it is the most expensive mistake an unattended caller makes here.

Start with a test key (the gck_test_ prefix): the identical request path against the real upstream provider, metered at zero. Set the project's monthly budget cap before handing any key to an unattended process.
Full guidance: https://cloud.gomry.com/agents.md

## API reference

- [Scrape](https://docs.cloud.gomry.com/services/scrape.md): Fetch a page and extract structured data from it against a JSON schema. Endpoints: /v1/scrape, /v1/fetch.
- [ToolsAPI](https://docs.cloud.gomry.com/services/toolsapi.md): Find a tool that can do a task and run it — 1,700+ across 55+ vendors, on your Gomry key. Endpoints: /v1/toolsapi/run, /v1/toolsapi/discover, /v1/toolsapi/inspect, /v1/toolsapi/runs/{runId}.
- [Superagent](https://docs.cloud.gomry.com/services/tasks.md): Give it a research question and a JSON schema. It plans, searches, reads, notices what is missing, searches again — and cites every field. Endpoints: /v1/superagent, /v1/superagent/{taskId}, /v1/superagent/{taskId}.
- [Ember](https://docs.cloud.gomry.com/services/inference.md): One model call, priced per token, at three grades — with the routing, compression and caching that make the cheap grade cheap. Endpoints: /v1/inference.

## Guides

- [Quickstart](https://docs.cloud.gomry.com/quickstart.md): Create a project, enable an API, mint a key and make your first billable Gomry Cloud request in about two minutes.
- [Authentication](https://docs.cloud.gomry.com/authentication.md): How Gomry Cloud API keys work: the gck_live_ format, scopes per operation, and the two independent checks every request passes.
- [Errors](https://docs.cloud.gomry.com/errors.md): Every error code the Gomry Cloud API returns, what causes it, whether it is retryable, and whether the failed request was billed.
- [Rate limits](https://docs.cloud.gomry.com/rate-limits.md): 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](https://docs.cloud.gomry.com/versioning.md): How Gomry Cloud versions its API, what counts as a breaking change, and the notice and headers you get before anything is withdrawn.
- [Billing](https://docs.cloud.gomry.com/billing.md): How Gomry Cloud bills: postpaid per-unit metering, one monthly invoice, per-project budget caps, and why there is no free tier.

## Pricing

- [Pricing](https://docs.cloud.gomry.com/pricing.md): What Gomry Cloud costs: the per-unit rate for every API operation, billed monthly in arrears with no plans, seats or minimums.

## Company

- [About Gomry Cloud](https://cloud.gomry.com/about.md): Gomry Cloud sells the web-fetching, tool-running and research services Gomry built for its own event platform as metered HTTP APIs, billed per unit with no plans or seats.
- [Contact](https://cloud.gomry.com/contact.md): How to reach Gomry Cloud about an API problem, a billing question, a security report or a partnership — including what to include so the first reply is useful.
- [Privacy](https://cloud.gomry.com/privacy.md): What Gomry Cloud stores when you call an API, what it does not store, who processes it, and how long each category is kept.
- [Authentication for agents](https://cloud.gomry.com/auth.md): How an automated caller obtains, uses, rotates and revokes a Gomry Cloud credential, and which parts of the agent-auth specs this platform does and does not implement.
- [Gomry Cloud for agents](https://cloud.gomry.com/agents.md): When an AI agent should call Gomry Cloud and when it should not — the jobs each API is right for, the ones it is wrong for, and how to call it safely under a budget.

## Machine-readable

- [Gomry Cloud OpenAPI description](https://cloud.gomry.com/openapi.json): Every endpoint, verb, required scope and example body. Start here to call the API. (application/openapi+json, https://spec.openapis.org/oas/v3.1.0)
- [Agent-readable site index](https://cloud.gomry.com/llms.txt): Every public page, annotated, linking the Markdown twin of each. (text/plain, https://llmstxt.org/)
- [The whole corpus, in one fetch](https://cloud.gomry.com/llms-full.txt): The full text of every public page, concatenated. (text/markdown, https://llmstxt.org/)
- [How to obtain a credential](https://cloud.gomry.com/auth.md): Discover, register, claim, use, and revoke — and which agent-auth mechanisms this platform does not implement. (text/markdown, https://github.com/workos/auth.md)
- [When to call this platform, and when not to](https://cloud.gomry.com/agents.md): Best-fit jobs for each API, the cases it is wrong for, and how to call it under a budget. (text/markdown, https://llmstxt.org/)
- [API catalog](https://cloud.gomry.com/.well-known/api-catalog): RFC 9727 linkset pointing at the description and the documentation. (application/linkset+json, https://www.rfc-editor.org/rfc/rfc9727)
- [Protected-resource metadata](https://cloud.gomry.com/.well-known/oauth-protected-resource): The resource, every scope it defines, and the bearer methods it accepts. (application/json, https://www.rfc-editor.org/rfc/rfc9728)
- [Agent Skills index](https://cloud.gomry.com/.well-known/agent-skills/index.json): The same nine operations, as a skills index. (application/json, https://agent-skills.org/)
- [Agentic Resource Discovery catalog](https://cloud.gomry.com/.well-known/ard.json): Every agentic resource this platform publishes, in one document. (application/json, https://agenticresourcediscovery.org/)
- [Gomry Cloud documentation MCP server](https://cloud.gomry.com/mcp): Search and read these docs as MCP tools. Streamable HTTP, no credential required. (application/json, https://modelcontextprotocol.io/)
- [Gomry Cloud product MCP server](https://api.cloud.gomry.com/mcp): Call the APIs as MCP tools. Streamable HTTP, bearer API key required. (application/json, https://modelcontextprotocol.io/)
- [Sitemap](https://cloud.gomry.com/sitemap.xml): Every indexable page. (application/xml, https://www.sitemaps.org/protocol.html)

## Documentation, in one fetch

- [Documentation llms.txt](https://docs.cloud.gomry.com/llms.txt): the docs site's own index — guides, every API reference page, and pricing.
- [Documentation llms-full.txt](https://docs.cloud.gomry.com/llms-full.txt): the entire manual as one document. Prefer this to fetching the pages above one at a time.

## Other

- [Documentation](https://docs.cloud.gomry.com/index.md): Gomry Cloud documentation: quickstart, authentication, error codes, rate limits and billing, plus a reference for every API.
- [Services](https://docs.cloud.gomry.com/services.md): Every API Gomry Cloud sells, with what each one does and what each operation costs per unit.
- [Console](https://cloud.gomry.com/sign-in): sign in to create a project, enable an API and mint a key.