Plans and billing
The Free, Pro and Team plans and what each includes, how units and credits are counted, and how to subscribe, change plans, cancel and handle a failed payment.
On this page
Forecall has a Free plan and two paid plans, Pro and Team. A plan belongs to an organization, and everyone in it shares the plan's units. Prices are in US dollars and include tax.
Compare the plans
| Item | Free | Pro | Team |
|---|---|---|---|
| Price, tax included | Free of charge | USD 29 a month | USD 199 a month |
| Units a month for evaluations and Scripts keys | 100 | 30,000 | 200,000 |
| Units a month for CI keys | 100 | 5,000 | 50,000 |
| Failure KB lookups a month (Agents keys) | 1,000 | 20,000 | 200,000 |
| Evaluation cases per tool | — | 8 | 20 |
| Japanese utterances | No | No | Yes |
| Failures reported on your servers | No | Yes | Yes |
| API requests a minute, per key | 10 | 60 | 300 |
Evaluations come with Pro and Team; a dash means the plan has none. Team writes more cases for each tool, and can write the utterances in Japanese. Every plan can choose any model: the units tell them apart. Pro and Team also show the failures agents reported on every server of the organization.
Units
Each plan includes units for each calendar month (UTC), counted for the whole organization:
- Evaluations and Scripts keys share one allowance. An evaluation takes units by the models' prices and the size of what they are asked (see Units); saving a lint with a Scripts key takes one.
- CI keys have their own allowance. Saving a lint takes one unit.
- Agents keys have their own allowance too. A lookup in the Failure KB takes one unit; reports, confirms and disputes take none, and a key may report 100 times a day.
Reading results, estimating an evaluation and GET /v1/me take none. Units left at the end of a
month do not carry over. The dashboard's API keys page shows this month's use, and an
evaluation's estimate shows the units left.
Each key may also make a number of requests a minute, the last row above. Past it, the API answers
429. This stops runaway scripts and leaked keys; it is not what a plan sells.
Credits
When a month's units run out, credits keep you going. They are bought once, in packs, on any plan, Free included:
| Units | Price, tax included |
|---|---|
| 10,000 | USD 10 |
| 60,000 | USD 50 |
Credits are used after the month's units, those that expire first first, and expire six months after purchase. The units of an evaluation that failed come back as credits, valid for six months too.
Subscribe
The organization's owners and admins open Plan and billing in the dashboard at app.forecall.dev and choose Pro or Team, or a pack of credits. Payment goes through Stripe, and Forecall never sees the card. The plan starts once Stripe confirms the payment, usually within seconds, and renews each month on the same day until you cancel.
Change or cancel
Manage the plan, cards and invoices opens Stripe's page for the subscription, where you can:
- Move up from Pro to Team. It takes effect at once, and the difference for the rest of the month is charged then, prorated.
- Move down from Team to Pro. It takes effect at the end of the month you have paid for.
- Cancel. The plan stays until the end of the month you have paid for, and then the organization is on Free. Until then, you can take the cancellation back.
- Change the card, and see the invoices and receipts.
Payments are not refunded, in full or in part, unless the law requires it. The terms and the commercial disclosure set out the details.
When a payment fails
Stripe tries a failed payment again over about two weeks, and emails you each time it fails.
Meanwhile the plan stays, but evaluations and the other operations that take units stop: the API
answers 402 with payment_failed, and the dashboard says so. Fix the card through Manage the
plan, cards and invoices; once the payment goes through, everything works again. If every try
fails, the subscription is canceled and the organization is on Free.