Skip to main content
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

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.

​
What a Superagent task costs

Superagent is the one service billed on more than one dimension: a flat unit for the task itself, one per source it fetched and extracted, and one per reasoning round it completed. A task that reads less costs less, and the totals below are the worst case at each tier — the ceiling, not the estimate. A task that fails before producing output is not charged the task unit, but the sources it already fetched and the rounds it already ran are charged — that work really happened. Narrow maxSources in the request body to cap it below the tier, or set a project budget cap to bound the month.

​
Common questions

Gomry Cloud sells the technical services Gomry built to run its own event platform as metered HTTP APIs. You authenticate with an API key, call a JSON endpoint, and are billed per unit consumed — currently web page fetching and structured data extraction.
Per unit, postpaid. Each operation has its own per-unit rate, usage accrues over the calendar month, and the total is invoiced to your card at the end of it. There are no plans, no seats and no minimum commitment.
No. Every request carries real upstream cost the moment it runs, so an active payment method is required before any API will serve. Free usage, when granted, is a credit on the account that applies to any service and runs out, rather than a permanent free allowance.
No. Only work that produced a result is billed. Validation errors, authentication failures, rate limits, timeouts and upstream failures all cost nothing, and every response reports the quantity it metered in its own body.
Every request is billed at the same per-unit rate, including the ones you make while integrating — there is no separate development tier. In practice wiring up an integration costs cents, because only work that produced a result is billed and a few hundred calls is a few hundred units. Set a budget cap on the project to put a hard ceiling under it.
Set a monthly budget cap on the project. It is evaluated before each request against the calendar month’s spend in UTC, and can either block further requests with a 402 or allow them and flag the overage.

​
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 for how caps, invoicing and payment failures behave.
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.