The marketplace · Access and pricing
Start free. Enter paid use with the price visible.
The trial is public. Workspace and vault access are in pilot. Authenticated core API access is separately provisioned through a confirmed engagement or checkout path.
Four signposts
Choose the access path that matches your stage.
No public price is presented as final unless the billing path can quote, reserve, meter, settle, and read it back.
Bounded trial
Use one of three no-key recipes. The trial performs no external action, stores no customer memory, and returns its result directly.
POST /v1/trial
Workspace and vault
Create a workspace key for the pilot workspace and customer vault. That key does not authenticate the separate core API today.
No subscription is created merely by opening a pilot workspace.
Managed core access
Authenticated core API credentials are provisioned separately from workspace keys. Choose a defined engagement or request an invoice from the main site.
Commercial terms are confirmed before any paid use.
Usage and budgets
Authenticated customers can inspect usage, estimate proposed work, and configure budgets through the core contract.
GET /v1/usage · POST /v1/usage/estimate
How paid work should cross the bridge
Quote, reserve, execute, settle, read back.
| Step | Customer-visible requirement | Why it matters |
|---|---|---|
| 1 · Estimate | Show the expected usage basis and applicable commercial terms. | The customer can decide before money is reserved. |
| 2 · Reserve | Hold only the admitted amount with an idempotency key. | A retry cannot create duplicate charges. |
| 3 · Execute | Expose the run’s real state and approval boundaries. | Payment does not silently authorize effects. |
| 4 · Settle | Charge actual admitted usage and release the remainder. | The final charge stays bounded by the reservation. |
| 5 · Read back | Return updated usage, balance, and completion evidence. | The customer can verify both work and billing state. |
Included in every durable result
The receipt is part of the product.
These behaviors describe the current product contract; they are not optional premium decorations.
Observable progress
Read accepted, planning, waiting, executing, verifying, completed, failed, and needs-attention states.
Idempotent creation
Use the same key to read the same admitted run rather than paying for duplicate work.
Completion receipt
Inspect the verification class, action boundary, source coverage, digests, and unresolved remainder.
Customer context controls
Search, correct, quarantine, forget, and inspect the integrity of customer-controlled context.
Commercial clarity
What this page does—and does not—promise.
The public trial is free
No account or API key is required for the bounded trial route.
Workspace access is early
Workspace keys authenticate workspace and vault routes only. Core API credentials are provisioned separately.
No invented flat rate
This page does not publish an arbitrary per-run amount disconnected from actual model and service usage.
No silent paid transition
A free or pilot workspace does not become a paid subscription without a separate, visible commercial action.