/ developers · inferrexcli
Authenticate with the provider's own CLI, not with a pasted key.
InferrexCLI drives the platform from a terminal — and runs provider authentication inside an ephemeral sandbox, so the credential is established the way the provider intended rather than copied into a form.
Pasting a key is the weakest step in most integrations.
Connecting a system usually starts by generating a long-lived credential in one provider's console and pasting it into another vendor's form. It is the least examined step in the whole process and the one with the widest blast radius: the key is typically broader than the task needs, it outlives the person who created it, and it now exists in a second place.
Most providers already ship a better path — their own CLI, with their own login flow, their own scopes and their own expiry. The obstacle has never been that the better path does not exist. It is that a hosted platform has nowhere safe to run someone else's CLI.
Somewhere safe to run someone else's tooling.
Inferrex runs provider authentication in an ephemeral, isolated sandbox — the same isolation used for agent operations. The provider's own CLI executes there, its login flow completes there, and the sandbox is discarded afterwards.
The provider's flow, unchanged
Authenticate the way the provider designed, with their scopes and their expiry, rather than a key minted to fit a form field.
Isolated and ephemeral
Execution is contained and thrown away. Nothing persists in the sandbox between connections.
Read the security commitmentsAudited like everything else
Connection and authentication events are logged and queryable — who, what, when.
Scoped to the task
Access is per-key and workspace-isolated, so a connection made for one job does not quietly become a credential for another.
Not published yet — and this page will say so until it is.
InferrexCLI is part of the developer surface alongside InferrexAPI, InferrexSDK and InferrexMCP. It is not published to npm yet, so there is deliberately no install command on this page.
InferrexAPI is the surface that is live today: every platform capability over HTTP, authenticated with API keys you create in the product. Everything the CLI will do is reachable there now.
Build against InferrexAPI today.
The REST surface is live, and the CLI sits on top of it when it ships.
Connect something without minting a key for it.
Join the Beta and try the authentication path on a provider you already use.