Pricing

Two meters — robot-hours and environment-hours — visible in every quote and every result. Metered per minute.

Everything you buy from Roborama reduces to two meters: robot-hours (occupancy of an embodiment) and environment-hours (occupancy of a scene). A queue priority — burst | standard | soak — multiplies both. There are no credits, no seats, no platform fee. Every quote and every result shows both meters, so the bill is an arithmetic exercise, never a surprise.

The rate card

The comparison above is arithmetic over one public rate card — a JSON file, /fixtures/pricing.json, the same one the quote endpoint prices from.

A worked quote: 600 humanoid episodes

What does it cost to run 600 episodes on g1-edu-pro in the kitchen-std@v1.2 replica at standard priority?

episodes            600
est. minutes/ep     2.0   (task time + scripted reset)
robot-hours         600 × 2.0 min = 20.0 h
environment-hours   600 × 2.0 min = 20.0 h

robot meter         20.0 h × $148/robot-hour  = $2,960
environment meter   20.0 h × $39/env-hour     = $780
                                        total = $3,740   queue ETA ~6h

That is exactly what the quote endpoint returns — the same shape ships in /fixtures/quote.json and in the POST /v1/quote examples:

import roborama  # reads ROBORAMA_API_KEY from the environment

quote = roborama.quote(
    robot="g1-edu-pro",
    environment="kitchen-std",
    episodes=600,
)
print(quote)
# {robot_hours: 20.0, env_hours: 20.0, usd: 3740, queue_eta: "6h"}

For comparison, the canonical run on the product page was auto-sized (episodes="auto(ci=0.95, moe=0.03)") and stopped at n=612 with realized robot_hours=20.4, environment_hours=20.4, cost_usd=3,812 — billing uses exact minutes; displayed hours are rounded to 0.1.

Outcome pricing: the threshold contract

If what you actually want to buy is "iterate until verified at a 0.99 success rate (95% CI) on bin_pick@v1", buy that. A threshold() contract iterates your checkpoint stream on soak-tier commodity pods (e.g. nori-a3, single-digit dollars per robot-hour) and escalates to verification-tier hardware like g1-edu-pro@fw2.3 only when the target is crossed. You set the monthly_cap_usd; the on_verified webhook gates your release.

import roborama  # reads ROBORAMA_API_KEY from the environment

contract = roborama.threshold(
    policy_stream=roborama.PolicyStream(webhook="https://acme.ai/ckpt"),
    target={"success_rate": 0.99, "ci": 0.95, "task": "bin_pick@v1"},
    iterate_on="soak",               # commodity tier, e.g. nori-a3 pods
    escalate_to="g1-edu-pro@fw2.3",  # verification tier on crossing
    monthly_cap_usd=12_000,
)

contract.on_verified(webhook="https://acme.ai/release-gate")
print(contract.id, contract.status)

Budgets are hard stops

Every run accepts max_budget_usd, metered live: the run stops at the cap and keeps its partial result (with n and CI — partial data is still data). Account budgets work the same way via roborama.budgets.set(monthly_usd=25_000, hard=True). See billing & budgets.

FAQ