- What is a Deployment, and what does it cost?
- A Deployment is one trained agent, hosted by us on a container dedicated to your organization and wired to your own Slack app. It is priced in three parts: a one-time setup fee for onboarding the agent to your operation, a monthly subscription per deployed agent, and model usage above the bundle that subscription includes. The agents are built; setup and monthly rates are quoted for your configuration and deployment requirements — ask us and we will price your case.
- Do you replace my CRM, LOS, or e-sig vendor?
- No. CapitalSource sits alongside your existing stack — your CRM, LOS, e-sig vendor, bank-data feed, and credit bureaus stay in place. What we take over is labor: intake, document filing, chasing what is missing, and packaging a deal for a funder. Most of the integrations catalog is intent rather than shipped code: /integrations badges every row with its real status, and you should read it before assuming a connector exists.
- What does the Growth tier actually pay for?
- Included quota across the platform rails — 50 originations and 100 invocations before any overage — plus OAuth client management, MCP server access, and configurable rate-limit budgets. Reviews are not part of any tier: the rail is planned, not built. The finance agents are built and ready, but we do not publish an unmeasured labor-savings multiplier; outcomes depend on your workflow and configuration.
- What counts as one origination?
- One certified CSG-1003 package dispatched to a funder. Discarded drafts, validation failures, and gating-rule rejections are free. Processor is built, but automated funder dispatch needs a separate platform submit route that is not available yet — so this rail does not bill today.
- When do reviews go live?
- No date. Reviews ship alongside the funder portal, which is not built: there is no way today for one organization to pull another organization’s certified package, so there is nothing to bill. The prices on this page are indicative and will be reconfirmed before the rail opens.
- What counts as one invocation?
- One successful call to a registered capability, whether it arrives over REST (POST /v1/capabilities/:slug/invoke) or MCP (tools/call). Seven capabilities are registered; two are functional today and five are contract-locked stubs that return a valid envelope and are billed at zero. The prices listed for those five are the list prices that take effect when each one flips functional.
- How does the token passthrough rate relate to Anthropic's published rate?
- 3× Anthropic published. The wrapper provides multi-provider failover, prompt caching, audit logging, Stripe-reconciled usage records, and per-tenant routing — value the bare Anthropic API doesn't include. Tenants who want to use their own Anthropic key can switch to BYO Keys for a flat 30% wrapper fee instead of the 3× passthrough rate.
- How do rate limits interact across capabilities?
- Rate limits are isolated per (organization, capability) tuple. A noisy capability cannot starve another — exceeding a limit returns a structured 429 with retry-after metadata, scoped to that capability only.
- Are there per-seat fees?
- No. Adding members to your organization is free, and nothing on this page is priced per user. A Deployment is priced per agent — setup once, then monthly — and every platform rail bills on activity. Ten people can talk to the same agent for the same money.
- How is the spend cap enforced?
- The Core service tracks usage_events against the cap in real time and rejects work over the limit. /app/settings/billing shows your cap, your month-to-date spend, and the headroom between them. Changing the cap is not self-serve yet — email us and we will change it.