Provisional tariff · tariff-v0
A plan, not a purchase.
This is our proposed pricing structure for API actions. The rates may change before launch. They are not final prices, an offer of access or something you can buy today.
The unit
Planned action meter
We plan to measure action usage in credits. The examples below explain that proposed structure; they do not grant access to a service.
1,000 credits are one US dollar. An answer from your decisions costs 100 credits — about $0.10.
The rule
Heavier work, more credits
The proposed structure gives each action an input limit and a stated price. More demanding work would need a separately agreed scope and price.
The floor
An answer, or a free refusal
The rate card records the intended boundaries of an action and its refusal behavior. It does not establish a final service contract or purchase entitlement.
What each action costs.
1,000 credits = US$1.00. Prices are in US dollars, computed from that peg.
| Action | Price | Input cap |
|---|---|---|
| Remember Write one memory item. | $0.002 2 credits | 32,768 bytes |
| Recall Retrieve relevant memory items. | $0.01 10 credits | 4,096 bytes |
| Answer from my decisions Answer from grounded decisions with citations. | $0.10 100 credits | 4,096 bytes |
| Record a decision Record one ruling or commitment, for later citation. | $0.002 2 credits | 32,768 bytes |
| Declared multi-hop over 40 decisions A multi-hop answer that has to reason across more of your record. | $0.15 150 credits = 100 × 1.5 | — |
| Stored memory Retention is metered per GB-month and declared before it is priced. | not yet priced per GB-month | — |
Provisional tariff, subject to launch review — shown as capability and plan, not a live sale. The credit-to-dollar rate may change before launch.
What we won't do to your bill.
No silent escalation
A cheap action never gets quietly routed to an expensive model and billed to you. Input caps are enforced, not advisory — over the cap you get a free rejection, not a surprise charge.
You're not charged to be told no
Refusal returns charged: false — designed
behaviour, not an error. Requests touching money, legal, irreversible, outward-facing classes
are classified before any work is charged. The boundary is drawn conservatively on
purpose: it cannot invent coverage, so at the edge it refuses, free.
Storage is named before it's billed
Keeping a memory forever for the price of writing it once is how a business bankrupts slowly. Retention meters separately, per GB-month, and we declared the meter before pricing it.
Every charge comes with its receipt
Each response states what it cost and how it was verified, so a bill is something you can audit line by line rather than take on faith.
Where this actually stands
These rates are proposals, not final prices. They may change before launch. This page does not offer checkout or general access.
We show the structure so a future offer can make scope, included usage and charging rules clear before anyone relies on it.
Questions about the foundation?
Tell us which application, API route or builder direction you are trying to understand. Access and commercial terms are described only when an offer is ready.