# Pricing

> What Gomry Cloud costs: the per-unit rate for every API operation, billed monthly in arrears with no plans, seats or minimums.

Source: https://cloud.gomry.com/pricing

You pay for the units you consume, at the same rate from the first request to the millionth. No plans, no seats, no minimum, and no free tier to outgrow.

## Rates

| Service | Unit | Price |
| --- | --- | --- |
| Scrape | per page | $0.02 |
| Scrape | per fetch | 0.5¢ |
| ToolsAPI | per µ$ of tool cost | 0.00015¢ |
| ToolsAPI | per lookup | 0.2¢ |
| Superagent | per task | $0.03 |
| Superagent | per source | 0.7¢ |
| Superagent | per round | 0.8¢ |

Operations within one service are priced separately because they cost separately — rendering a page and running a structured extraction over it are not the same work, so they are not the same rate.

## What you pay for

- **Only results.** A failed, timed-out or refused request is never billed.
- **Per unit, per month.** Usage accrues over the calendar month and is invoiced to your card at the end of it.

Every response tells you the quantity it metered, in the same payload as the result — so what you were charged is visible at the call site, not only on the invoice.

## Controlling spend

Each project can carry a monthly budget cap, checked before the work runs, that either blocks or flags requests once the month's spend reaches it. It is the control that bounds a runaway loop, and setting one on day one is the recommendation. See [Billing](https://cloud.gomry.com/docs/billing) for how caps, invoicing and payment failures behave.

> **Note:** Cloud is postpaid, so an active payment method is required before any API will serve. There is no free tier and no development tier: every request carries real upstream cost the moment it runs, and is billed at the same rate whoever makes it.