$49.00 a month,
plus what you actually use.
One subscription turns on API keys, the workbench, and the Rowe runtime. Usage is metered in spatial tokens and billed only on requests that succeed. Stripe handles Checkout and invoices; we never see a card number.
Developer
Live billingSelf-serve. Subscribe, mint a key, and call the API in the same sitting.
- Base access
- Keys, workbench, Rowe runtime
- $49.00 / month
- Input spatial tokens
- Scene context and uploaded file bytes
- $5.00 / 1M
- Output spatial tokens
- Rowe's typed result or the extraction JSON
- $20.00 / 1M
- Failed requests
- Non-2xx never reaches the meter
- Not billed
- Rowe 1.0 Responses API, Four Cad extraction API, MCP server, SDKs
- Four Cad workbench in the dashboard
- Input and output itemized on a Stripe invoice; cancel any time
Design partner
For teams that need private formats, PLM or CAD integrations, security review, volume commitments, or a say in how Rowe is evaluated and deployed.
- Negotiated volume rates and annual commitments
- Private formats and PLM or CAD integration work
- Security review and written data-handling terms
- A jointly designed evaluation with success criteria agreed up front
- Terms and success criteria agreed before any quote
1M in / 0.2M out
$58.00/ mo
$49.00 + $5.00 in + $4.00 out
10M in / 2M out
$139.00/ mo
$49.00 + $50.00 in + $40.00 out
100M in / 20M out
$949.00/ mo
$49.00 + $500.00 in + $400.00 out
Arithmetic on the list rates, not typical usage. For your own files, use the calculator below; for any request, the usage object on the response is the exact charge.
What your files would cost
Enter how many CAD files and drawings you extract in a month. Input tokens are exact (file bytes / 4). Output tokens come from a sample of 78 public files measured on 2026-09-02, shown at the median and at the p90 upper bound. The method and every file are in the usage and cost docs.
| Format | Files / month | Avg size (KB) | Tokens / file (p50) | Sample |
|---|---|---|---|---|
| STEP / STP | 35.1k in / 1.8k out | n=18 | ||
| IGES / IGS | 30.7k in / 415 out | n=10 | ||
| DXF | 5.4k in / 761 out | n=12 | ||
| PDF drawing | 30.5k in / 44.9k out | n=8 | ||
| SVG drawing | 1.5k in / 1.5k out | n=8 | ||
| draw.io diagram | 1.3k in / 15.6k out | n=22 |
Input tokens are file bytes / 4, exactly as the API bills them. Output tokens per file are the measured median for the format (the structured contract, which is the default). Adding the both contract appends a point cloud whose size does not track file size, so it is not estimated here — read the usage object on a real response instead.
Estimated monthly bill
$93.20/ mo expected
Up to $111.72/ mo at the sample's p90 output volume.
- Base access
- $49.00
- 4.39M input tokens
- $21.93
- 1.11M output tokens (p50)
- $22.27
- 2.04M output tokens (p90)
- $40.80
- Files
- 170
Estimate, not a quote. Measured on 78 public CAD files on 2026-09-02; the p90 is the upper bound of that sample, not a guarantee. Drawing and diagram formats (PDF, DXF, SVG, draw.io) vary several-fold with content — a dense drawing can exceed the p90. draw.io files are small but expand to many output tokens per input token, because every node, connector, and relation is spelled out. Failed conversions are never billed.
What counts as a spatial token
Input spatial tokens
The scene context you send: cad_scene geometry, point clouds, images, sensor readings, goals, and object ids. Uploaded file bytes count here too.
Output spatial tokens
Rowe's structured result: measurements, relations, issues, comparisons, predictions, plans, and the extraction JSON returned by Four Cad.
CAD extraction
Metered exactly like any other request — file bytes in, extraction JSON out. There is no separate per-file fee.
Failed requests
Non-2xx results are recorded for debugging and are never billed. You pay for answers, not attempts.
Questions we get asked
- What does the $49.00 actually buy?
- Access. It enables API keys, the workbench, and the Rowe runtime for your account. It is not a usage credit — token usage is billed on top of it, in arrears.
- Are there prepaid credits?
- No. Billing is a base subscription plus metered usage on your Stripe invoice. There is no credit balance to buy or top up.
- What happens if a request fails?
- It is not billed. Failed model requests are recorded against your request id for support, but they never reach the meter.
- Is there a request cap?
- There is a default ceiling of 100,000 requests per billing period per owner. It is an abuse and safety control, not an included-usage allowance, and it can be raised for an account.
- How do I cancel?
- From the Stripe Customer Portal, any time. Cancellation stops the next base charge; usage already metered in the current period still invoices.
- Do you offer volume or annual pricing?
- Talk to us. If your usage is large enough that per-token list pricing is the wrong shape, we would rather agree terms than have you guess.
- Will these rates change?
- Possibly. This is launch pricing for a developer preview, set against comparable developer platforms rather than measured willingness to pay. We will revisit it once we have real payload and cost data, and existing subscribers will hear from us before anything changes.
Get a key and send one request.
The response comes back with a usage object showing the exact token counts you were charged for. That is the fastest way to know what this costs you.