# Connection and installation ## Connect an account Create a key in [API Keys](https://app.primexos.com/keys) and configure it through the host's private secret settings as `PRIMEX_API_KEY`. Send it only to the Gateway. If the host has no private mechanism, guide the user to configure it outside the conversation. Your agent subscription and Primex API usage have separate billing. For Codex or Claude Code, the key must reach the HTTP executor, not just the CLI process. Set it privately in the launching environment and check availability without printing its value. Existing Codex [shell environment filters](https://developers.openai.com/codex/config-reference/) can exclude secret variables. Preserve those policies; use an approved private credential mechanism or explain missing access rather than loosening the filters. Keep the service key separate from the agent's reasoning-provider key. For project-installed Claude skills, use normal Claude Code mode and include `project` if you restrict `--setting-sources`. Minimal modes can omit project skill discovery even while the files remain readable. The normal runtime inspection verifies the credential without inference; no separate check is needed before every task. For a standalone credential problem, `GET https://gateway.primexos.com/v1/models` with the privately injected key is non-billable and works at zero balance. This verifies credentials, not funding or another client's configuration. Funding and usage are in the [App](https://app.primexos.com/billing). ## Keep the skill available An HTTP-capable agent can use the public SKILL.md instructions directly. To retain it for future tasks, download the [package](https://docs.primexos.com/skills/primex-0.1.0.zip), inspect it and install its `primex` folder using the host's skill mechanism. See [installation locations](https://docs.primexos.com/integrations/primex-skill/). Preserve existing skills/settings and review updates before replacing them. Archive/file checksums verify integrity, not independent authenticity. Reading the URL does not install a persistent skill or configure a key. HTTP and required file tools are sufficient for service use. The [helper](helper.md) is optional; only that helper needs Python. No Primex MCP or local server is required.