{
  "markdown": "# Locus plugin\n\n[![skills.sh installs](https://skills.sh/b/locus-technologies/locus-pro-plugin)](https://skills.sh/locus-technologies/locus-pro-plugin)\n\nPay-per-use APIs for coding agents. This plugin connects the [Locus](https://paywithlocus.com)\nMCP server and teaches your agent how to use it well: cited web research, paid\ndata and API lookups, and thousands of metered provider endpoints billed to one\nprepaid workspace credit balance.\n\nOne repo, one plugin, many agents. The same plugin installs into Claude Code,\nCodex, Cursor, Grok, OpenClaw, and any client that speaks the\n[Agent Plugins](https://agent-plugins.org) or\n[Agent Skills](https://agentskills.io) open standards.\n\n## What you get\n\n- **MCP server connection** to `https://api.paywithlocus.com/api/credits/mcp`\n  (streamable HTTP). Sign-in is OAuth with browser consent; no keys are stored\n  in configuration.\n- **The `locus` skill**: operating instructions for the agent covering tool\n  routing, cost quotes, idempotent billing, error recovery, and spend safety.\n- **The `locus-setup` skill**: full self-serve onboarding — account creation\n  (human sign-up through the OAuth page, or agent-owned accounts via\n  AgentID), capability selection, and a user-requested Stripe funding\n  handoff — so the whole product works from inside the plugin.\n\nNo account yet? The OAuth sign-in page includes account creation, and the\nsetup skill walks agents through the rest: [platform.paywithlocus.com](https://platform.paywithlocus.com).\n\n## Install\n\n### Claude Code\n\n```\n/plugin marketplace add locus-technologies/locus-pro-plugin\n/plugin install locus@locus\n```\n\nThen run `/mcp`, select `locus`, and authenticate.\n\n> Already added the server manually as `locus-pro` via `claude mcp add`? Remove\n> it first (`claude mcp remove locus-pro`) so you don't carry two connections\n> to the same server.\n\n### Codex\n\n```\ncodex plugin marketplace add locus-technologies/locus-pro-plugin\ncodex plugin add locus@locus\ncodex mcp login locus\n```\n\n### Cursor\n\nAdd the MCP server directly in `~/.cursor/mcp.json`:\n\n```json\n{\n  \"mcpServers\": {\n    \"locus\": {\n      \"url\": \"https://api.paywithlocus.com/api/credits/mcp\",\n      \"headers\": { \"X-Source-Name\": \"cursor-plugin\" }\n    }\n  }\n}\n```\n\nCursor's OAuth flow completes in the browser on first use. Once the Locus\nlisting clears Cursor Marketplace review, you will also be able to install\nit from **Customize → Plugins** (search \"Locus\") or with `/add-plugin locus`\nin chat.\n\n### Grok\n\n```\ngrok plugin install locus-technologies/locus-pro-plugin --trust\n```\n\nGrok requires explicit trust to install plugins (they can run MCP servers\nand skills); review the repo, then pass `--trust`. Grok discovers the\nserver's OAuth automatically and opens the browser flow on first use.\n\n### OpenClaw\n\nInstall the plugin from this repo as a marketplace source; the bundle\nalready maps the MCP server, so no manual server configuration is needed:\n\n```\nopenclaw plugins install locus --marketplace locus-technologies/locus-pro-plugin\nopenclaw gateway restart\nopenclaw mcp login locus\n```\n\nA new marketplace source triggers a one-time trust prompt (pass `--force`\nfor non-interactive installs), and the gateway restart applies plugin\nchanges.\n\n### Skill only (77+ agents)\n\n```\nnpx skills add locus-technologies/locus-pro-plugin\n```\n\nDiscovers both Locus skills (usage and setup) and installs your selection\ninto whichever agents you have. The skills include the connection\ninstructions; add the MCP server in your client's settings to make the\ntools available.\n\n### Any Agent Plugins client\n\n```\nnpx plugins add locus-technologies/locus-pro-plugin\n```\n\n### Plain MCP (no plugin)\n\n```\nclaude mcp add --transport http locus https://api.paywithlocus.com/api/credits/mcp\ncodex mcp add locus --url https://api.paywithlocus.com/api/credits/mcp\n```\n\n## Data handling\n\nThe plugin-managed MCP configs send one static request header,\n`X-Source-Name` (for example `cursor-plugin`). It identifies the\nconfiguration format a host selected and may be used solely for anonymous\nadoption telemetry; multi-format hosts can prefer a different bundled\ndefinition than their own overlay — OpenClaw's bundle loader, for example,\nhonors the root `.mcp.json` and therefore reports `grok-plugin`. The header\nis cosmetic: plain MCP clients that cannot configure static headers still\nwork without it.\n\nThe repository contains no credential values, and its MCP configurations\nstore none. Tool calls send the arguments the agent provides to\n`https://api.paywithlocus.com` and are billed to the authenticated workspace.\nIf the user explicitly chooses the optional agent-owned setup path, the setup\nskill also calls `https://api.agentmail.to` to create and verify an inbox and\nregister a public signing key, `https://api.auth.agentid.com` to submit a\nsigned approval, and `https://auth.agentid.com` to continue that\nauthorization transaction. AgentMail receives only the user-approved email\naddress and inbox name, the user-provided one-time code, and the public key;\nAgentID receives the inbox identity and a one-time signed assertion. The\nprivate signing key is generated locally and is never sent. Funding calls\n`https://api.paywithlocus.com` and returns a server-provided Stripe Checkout\nURL that the user opens in a browser; neither the plugin nor the agent\nhandles card details.\n\n## Authentication and credentials\n\nHuman-owned MCP connections use OAuth 2.1 with dynamic client registration:\nyour client discovers it from the URL, opens a browser sign-in, and a consent\nscreen in the Locus dashboard scopes the connection. Access and refresh\ntokens stay in the client's native OAuth store, never in this repo's files.\n\nThe optional agent-owned setup path may create an `AGENTMAIL_API_KEY`, a\nlocally generated P-256 signing key, and an `lcac_` value stored as\n`LOCUS_AGENT_CREDENTIAL`. Keep them only in the runtime's approved secret\nstore; never put them in MCP configuration, chat, project files, source\ncontrol, logs, or command arguments. `LOCUS_SECRET_KEY` is referenced only as\na credential class to protect; the skills never read or set it, and neither\n`lcr_` nor `lcac_` values belong in MCP configuration.\n\n## Costs and safety\n\nPaid provider calls are live and billed to your workspace credit balance;\ncatalog discovery, quotes, and balance checks are free. The skill instructs\nagents to pass idempotency keys so a retry reusing its key never\ndouble-charges, to quote\nsignificant calls with `estimate_cost` first, and to confirm with you before\nunusually large spends. Spend limits and approvals are configured per workspace\nin the [dashboard](https://platform.paywithlocus.com).\n\n## Repository layout\n\n| Path | Consumed by |\n| --- | --- |\n| `.claude-plugin/` | Claude Code (plugin + marketplace manifest) |\n| `.codex-plugin/`, `agents/codex/.mcp.json`, `.agents/plugins/` | Native Codex plugin, MCP configuration, and marketplace manifest |\n| `.cursor-plugin/` | Cursor |\n| `.mcp.json`, `skills/` | Effective Grok components while the root `plugin.json` is present (Grok prefers the root manifest) |\n| `.grok-plugin/`, `agents/grok/` | Grok marketplace extraction and fallback configuration when no root manifest exists |\n| `plugin.json`, `mcp.json` | Agent Plugins (open standard) |\n| `agents/<client>/` | Per-client MCP server config |\n| `skills/` | Shared Agent Skills-format instructions; `metadata.openclaw` is an intentional host extension for credential declarations |\n\n## Links\n\n- Docs: https://docs.paywithlocus.com\n- Dashboard: https://platform.paywithlocus.com\n- MCP reference: https://paywithlocus.com/agent/mcp.md\n\n## License\n\n[MIT](./LICENSE)\n",
  "bytes": 7615,
  "sha": "a50a970d2ef770eb1210783b8e33c5d81ff6f1edb7e0c00625d43e47d1363f79",
  "repo_slug": "locus-technologies/locus-pro-plugin",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_com_paywithlocus_locus_4e0fda73/readme"
}