Prove your first workflow with no commitment.
500 credits · $5.00 of usage
- 30-tool schema catalog
- 500 trial credits
- Rotatable API-key access
Every new account starts with 500 credits. One credit is worth $0.01 USD, so usage maps directly to a visible ledger.
500 credits · $5.00 of usage
3,000 credits/month · $30.00 of usage
1,000 credits · $10.00 of usage
Volume credits at $0.01 each
One credit is worth $0.01 USD. Tool calls debit the same atomic ledger shown in your account. Card checkout is not active; paid credits are arranged by invoice.
GET /api/tools publishes every tool's credit cost, and your account shows the resulting balance.| Capability | Starter | Builder | Pay as you go | Scale |
|---|---|---|---|---|
| Credit allocation | 500 trial | 3,000 / month | 1,000 once | Agreed |
| Tool schemas | 30 | 30 | 30 | 30 |
| Rotatable API keys | Included | Included | Included | Included |
| Rate limits | Standard | Standard | Standard | Agreed before traffic |
| Purchase path today | No card | Invoice | Invoice | Invoice |
The catalog contains 30 tool schemas. Provider-backed calls still require their named production integration; configuration failures return an error and do not pretend to succeed.
One credit is $0.01 USD. GET /api/tools returns the configured integer credit cost for every call.
Calls stop cleanly before side effects when the balance is too low. Request a top-up invoice; there is no uncontrolled overage bill.
The current ledger does not expire a paid credit balance. Any different future commercial term must be stated on the invoice before payment.
Create separate keys for development and production when you need clean credential rotation. Never put a production key in a public client bundle.