Skip to main content
Fund one workspace balance for your own agents, or give your customers their own balances and charge them your prices for usage.

Choose a funding model

You top up a workspace pool, and your own calls pay the base price from it. You fill a customer balance from your pool, or the customer fills it by buying credits through Locus checkout. Customer calls pay your price. If you allocated the credits, the markup returns to your pool. If the customer bought them, the markup is paid out to you as earnings. Monthly plans are billed separately from these balances; see Plans and trials. For self-serve funding, see Account and usage.

Fund your workspace

Add credits under Billing → Credits with Stripe Checkout, from a $5 minimum. Larger top-ups earn volume bonuses, and auto-recharge refills the pool when it runs low. See Fund your workspace.

Set a spending ceiling

Set a monthly hard limit and email alerts for monthly spend and low balance. Locus rejects a call that would go over the limit before it reaches the provider. See Spend controls.

Fund customer balances

Let customers buy credits through the billing widget or a checkout link, or allocate credits from your pool after you bill them yourself. See Customer balances.

Collect earnings

When customers buy credits through Locus-hosted checkout, your markup accrues as earnings when they use those credits. Earnings become payable after a holdback period, 30 days by default. Open Billing → Payouts to connect a Stripe account for bank payouts or set a USDC address on Base. See Earnings and payouts.

Refunds and disputes

A call that fails before the provider succeeds isn’t charged. A retry with the same idempotency key (an ID you send with a call so Locus can spot a retry) never charges twice. If a Locus-hosted top-up is disputed, Locus reclaims the disputed credits and freezes the account until the dispute is resolved. See How a call is charged.

Follow payments with webhooks

Add a webhook URL under Settings → Webhooks to receive top-up, charge, refund, balance, and dispute events. Use them to update your product after a payment or to warn a customer their balance is low. Recent deliveries on the same page shows the latest attempts and results. Verify each delivery’s signature, reject stale timestamps, and deduplicate by event ID. The API reference and signed fixtures cover the details.

Review transactions

  • Analytics lists top-ups, charges, allocations, refunds, and payouts. Filter by customer, agent, provider, endpoint, or your own attribution fields.
  • Billing → History lists your top-ups and auto-recharge payments, with a Stripe receipt for each card payment.
Financial history is append-only, so corrections appear as new entries. See Analytics.

Next steps

Add the billing widget

Put balance display and top-ups in your app.

Set customer prices

Choose your markup and understand your margin.