Locus product guide · Updated September 27, 2026

Prepaid Credits for AI Agents: How They Work

Prepaid credits fund AI agent tool usage before execution. Locus Pro checks the available balance, reserves or charges the applicable amount, and records the result. The Free plan has no monthly subscription; optional plans add monthly included credits. Included credits expire each billing period, while purchased top-ups are a separate balance source.

Credits represent a dollar value

The default denomination is 1,000 credits per dollar. At that denomination, an illustrative $0.0039 operation costs 3.9 credits. An enterprise workspace can choose its denomination during setup; changing the unit does not change the underlying dollar cost.

Treat amounts as exact decimal values when integrating. Converting a charge to a rounded display string and then using that string for accounting can lose precision across many calls. Use the charge and ledger values returned by the service.

Separate a subscription from tool consumption

A plan price pays for its stated workspace features and included monthly credit allowance. It does not mean unlimited free upstream API usage. The pricing page publishes the current Free, Plus, Enterprise, and Enterprise Plus plans, alongside custom commercial options.

Included monthly credits expire at the end of the billing period and are used before purchased credits. Purchased top-ups are separate. Existing subscriptions and signed agreements retain their terms until explicitly changed. Check the live plan and funding quote before purchase rather than relying on a historical screenshot or an example in a guide.

A reservation and a final charge are different

Some operations have a fixed per-call price. Others depend on tokens, pages, generated output, or a live upstream quote. A response-priced operation can reserve a maximum, capture measured usage, and release the unused part. If usage cannot be recorded after a response is delivered, the authorized maximum can remain charged.

An underfunded call returns HTTP 402 before execution. A non-streaming failure before success releases the reservation. A streaming request is captured when the provider accepts the stream; a later disconnect can remain charged. Do not assume that every failed-looking client request is free.

Choose funding and controls deliberately

Personal accounts can add credits, configure supported auto-reload, and set account spending controls. An auto-reload limit controls replenishment; a spend cap controls new spending. A low-balance alert informs you but is not itself a hard spending limit.

Enterprise products can use the workspace pool for internal agents, allocate pool credits after collecting payment themselves, or let end users fund balances through Locus-hosted checkout. Decide which model applies before wiring customer attribution into your calls.

Frequently asked questions

Are prepaid credits the same as a crypto wallet?

No. Locus Pro credits are the product’s prepaid usage balance. Pay With Locus provides the separate on-chain USDC wallet product.

What happens when credits run out?

If available credits cannot cover the authorized call, Locus Pro rejects it before provider execution. Add funds or use an already-configured eligible funding flow before retrying.

Does an account cap cancel work already running?

A spend cap stops new spending. Work already in progress or completed can still be charged; review committed usage as well as completed usage.

Implementation references

Use these first-party references for current request contracts and account requirements. Tool availability, prices, and negotiated terms can change.