Platform
Credits and billing
One credit is $0.001 of underlying vendor cost. Every metered action declares its price before it runs.
| Plan | Price | Credits | Connections | Scope |
|---|---|---|---|---|
| Solo | $299/mo | 20,000 | 2 | 1 workspace, 1 seat |
| Agency | $499/mo | 50,000 | 10 | 5 client workspaces, 5 seats |
| Enterprise | Custom | Negotiated | Negotiated | SSO, custom DPA, SLA |
Overage is opt-in
$0.004 per credit, and off by default. Agents pause at the allowance and nothing is invoiced. A platform that silently bills past an allowance is one surprise invoice away from a churned agency.
Connections and workspaces are separate line items
Because the vendors behind them charge fixed fees that scale with client count rather than with usage. Connections are billed per connected account; a client workspace is an isolation boundary an agency adds per client. Bundling either means agency margin degrades with every client added — the cost grows while the subscription does not.
Charges are idempotent
Every charge requires an idempotency key, and a unique index on the org and the external id is the only thing that makes a retry after a timeout safe. A duplicate is treated as success rather than as an error, because the caller retrying is the expected case, not the exceptional one.