Connect AI Agent Tools with Locus Pro

Choose the account that owns the usage

Use a personal account when you want tools for your own agent. The Free plan has no monthly subscription; paid tool calls still require credits. Enterprise workspaces are for teams and products that need shared access, customer attribution, pricing, and embedded billing.

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

Connect through hosted MCP

The production MCP server is https://api.paywithlocus.com/api/credits/mcp. Add it as a remote HTTP MCP server in a compatible client, then complete the browser sign-in and authorization flow. The exact settings screen varies by client; the connection documentation is the source for current client-specific steps.

OAuth connects the client to your account. It does not create a new balance for every connection or remove your existing spending limits. Review the account and allowed access before authorizing. Revoke a connection when the agent no longer needs it.

Verify a useful first tool call

Ask the agent to discover a tool for the specific outcome, inspect the returned operation and input schema, and review its price or charging basis. Use a small request with an expected useful result. Then compare the result and recorded charge with the request you intended.

A successful sign-in or catalog search verifies connection and discovery only. A paid operation verifies the execution path. An empty result is not evidence that a data provider can answer your use case; test a known-positive input 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.

Use a scoped credential for an unattended runtime

An enterprise agent that cannot complete an interactive browser flow can use an authorized Agent Connection. These credentials can carry expiry, tool access, and spending constraints. Keep tenant secret keys in trusted server infrastructure; do not place them in prompts, browser bundles, or general agent configuration.

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