Locus product guide · Updated September 29, 2026

Connect AI Agent Tools with Locus Pro

To connect an AI agent to Locus Pro, create an account, add the hosted MCP server to a compatible client, and approve browser OAuth. The agent can then discover permitted tools and pay for supported calls from your prepaid credits. No separate account or API key is needed for each managed provider.

Which Locus account should own the usage?

Use a personal account for your own agent. Use an Enterprise workspace for teams and products that need shared access, customer attribution, pricing, and embedded billing. The Free plan has no monthly subscription, but paid tool calls still need credits.

Start with a defined task, such as finding a company website or extracting text from a page. Confirm the operation is in the current catalog before adding funds. A provider listing does not mean every endpoint or model that provider offers is available through Locus.

How do I add the Locus MCP server to my agent?

Add https://api.paywithlocus.com/api/credits/mcp as a remote HTTP MCP server, then finish the browser sign-in and authorization. The settings screen varies by client. The connection docs list current client-specific steps.

OAuth connects the client to your account. It does not create a new balance per connection or remove your spending limits. Review the account and access before you authorize, and revoke a connection when the agent no longer needs it.

Which setup guide matches my agent?

Every host connects to the same hosted MCP server, but the install steps differ. Pick the host your agent runs in:

How do I check that the connection works?

Make one small paid call with a known-positive input and compare the result and charge with what you expected. Ask the agent to find a tool for a specific outcome, read its input schema, and check its price or charging basis first.

A sign-in or catalog search proves connection and discovery only. A paid call proves the execution path. An empty result does not show a provider can answer your use case. Test an input you know should match, and check the response fields you depend on.

Check that the client points to the production MCP URL.
Check the tool is permitted and the balance covers the call.
Read the operation schema instead of guessing input names.
Review the resulting activity entry and charge.

How do I connect an agent that cannot sign in through a browser?

Use an authorized Agent Connection, available to Enterprise workspaces. These credentials can carry expiry, tool access, and spending limits. Keep tenant secret keys on trusted servers, never in prompts, browser bundles, or general agent config.

Application code that needs deterministic calls may fit the server SDK or HTTP API better than MCP. The balance and billing model still apply whichever interface you choose.

Frequently asked questions

Do I need cryptocurrency for Locus Pro?

No. Locus Pro uses prepaid credits and supported funding flows. Pay With Locus is the separate product that uses a USDC wallet on Base.

Does connecting MCP make API usage free?

No. The connection gives the agent access to permitted tools. Paid operations consume credits at the applicable tool price or usage basis.

Can every MCP client connect?

Use a client that supports the hosted server transport and the documented authentication flow. Check the current connection documentation for client requirements.

Implementation references

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