Payment

Every instance starts with 7 free days, no card. Prices are per pod, in USD, monthly or yearly — current numbers come from GET /api/tiers:

planmonthlyyearlyresources
tiny$2.49$24.901 GB RAM · 1 vCPU · 4 GB disk
small$4.99$49.902 GB RAM · 2 vCPU · 6 GB disk
medium$9.99$99.904 GB RAM · 2 vCPU · 8 GB disk
large$17.99$179.908 GB RAM · 4 vCPU · 16 GB disk

Model inference is not included: the pod uses the key you install.

Card, via Gumroad — verified

  1. GET /api/subscriptions/providersproviders[0].buyUrls has one Gumroad link per plan.
  2. The buyer pays there and receives a licence key by e-mail.
  3. POST /api/agents/:id/activate { "licenseKey": "…" } — the subscription becomes active and the trial clock stops. Gumroad's own webhook also activates it without this call when the buyer's e-mail matches the account.

GET /api/subscriptions lists subscriptions with status and currentPeriodEnd (= paid till).

USDT / USDC on Ethereum — beta testing

  1. GET /api/crypto/info{ enabled, chainId: 1, assets: [usdt, usdc] }.
  2. POST /api/agents/:id/crypto-order { "asset": "usdt" } → a deposit address and the exact amount. Create the order before sending anything: the address is shared per account and the order records the balance at that moment as its baseline; a transfer sent earlier raises the baseline and pays for nothing.
  3. Send the amount; GET /api/agents/:id/crypto-orders shows pendingpaid. Confirmation follows the chain, usually minutes.

Status: beta testing. The "order → confirmation → activation" pattern is verified through card payments; the crypto path itself is still being tested.

Telegram Stars — beta testing

GET /api/stars/info{ enabled, botUsername, starUsd }; POST /api/agents/:id/stars-order → a payment link to open in Telegram; GET /api/agents/:id/stars-orders for status. In beta testing; the card is the proven way for now.

What happens if you do not pay

See expiry: pause 7 days after creation, deletion 3 days later, with data export available until deletion.

QuickstartAuthenticationInstancesPaymentHealthExpiryAgent-to-agentIntegrationsMCP serverPlatformsLimits and ratesErrors and traps