OneCLI is an open-source credential gateway for AI agents: a secure gateway, an encrypted vault, and a dashboard, installed with one command. Agents make API calls through OneCLI, and credentials are injected at the network layer, so keys never leave the vault.

Credentials live in an encrypted vault (local KMS or OneCLI Cloud) and are injected per-request at the proxy boundary. The agent and the LLM never see a key: not in environment variables, not in prompts, not in logs.

Yes. OneCLI is framework-agnostic: OpenClaw, NanoClaw, IronClaw, Dify, n8n, OpenHands, or any custom pipeline that makes HTTP calls. There are no code changes. Agents route through the gateway with one command.

No, it covers more than MCP. An MCP gateway only governs MCP tool calls. OneCLI enforces at the network layer, so it secures every way an agent reaches a service: MCP tool calls, CLI commands, curl from a shell, or HTTP requests from code the agent writes. Same vault, same policies, same audit log for all of them.

Block specific endpoints, rate-limit per agent, require human approval for sensitive operations, and scope credentials per project. Policies are enforced at the network layer, outside the agent and outside the LLM. They are rules, not suggestions.

Yes. OneCLI is Apache 2.0 licensed and developed in the open on GitHub. Self-host it for free with a one-line install, or use OneCLI Cloud if you want a managed vault and dashboard.

One command: curl -fsSL https://onecli.sh/install | sh installs and starts the gateway, vault, and dashboard. The free tier covers 2 agents forever, with no credit card required.