agentis-pay
Install
Managed installer (recommended)
Use the managed installer for the best CLI experience. This is the default install path for users and AI agents, and it is the only install mode we intend to auto-update silently.
|
Optional flags:
|
|
The managed installer places a stable launcher in ~/.local/bin/agentis-pay by default and keeps managed payloads under ~/.agentis-pay/.
Developer install methods
Package-manager installs remain available for developer workflows, local testing, and ecosystem-specific setups. These installs should follow their own package manager's upgrade flow.
Homebrew
npm
pip
Cargo
Build from source
Options for the source-build installer:
--bin-dirto change the binary destination (default:~/.local/bin).- Shell completion installation is currently not bundled in this CLI package.
Usage
Discover available commands with:
Example commands:
MCP
Install and run the local MCP server:
The generated JSON can be pasted directly into Claude Desktop config.
For local MCP clients, agentis-pay mcp serve automatically reuses the session already saved by the CLI. Sensitive session material is stored in the OS-native credential store (Keychain on macOS, Credential Manager on Windows, native keyring on Linux when available), while non-sensitive metadata remains in ~/.agentis-pay/credentials.json. When mcp install writes Claude Desktop config, it uses an atomic write and restricts file permissions on Unix systems.
For container/server deployments, set AGENTIS_PAY_SERVER_MODE=true and inject runtime credentials via environment variables (for example from Kubernetes Secrets synchronized from Google Secret Manager). In server mode, mcp serve does not read credentials.json and does not initialize the native keyring.
For local agents, prefer the managed installer so the CLI can stay on the supported update path.
The local MCP server currently exposes these agent-facing tools:
agentispay_whoamiagentispay_accountagentispay_balanceagentispay_history(supportsid?andlimit?)agentispay_brcode_decodeagentispay_depositagentispay_pix_keysagentispay_limitsagentispay_pay(and aliasagentispay_pix_send)
Host/bootstrap commands such as login, verify, logout, mcp serve, and mcp install remain CLI-only.
Trust-related tools are intentionally omitted from MCP for now.
Most local agents should use the saved-login flow above and avoid embedding JWTs in config files. If you must pre-seed a config snippet with a token, prefer agentis-pay mcp install --jwt-file /path/to/token or agentis-pay mcp install --jwt-stdin over passing secrets on the command line. For advanced runtime cases, MCP still supports explicit env overrides:
AGENTIS_PAY_OUTPUT=json \
AGENTIS_PAY_JWT=<token> \
AGENTIS_PAY_AGENT_NAME=<name> \
AGENTIS_PAY_DEVICE_ID=<device-id> \
agentis-pay
For non-interactive server deployments, prefer env-only auth and include refresh metadata so the process can renew tokens in memory without touching local files:
AGENTIS_PAY_SERVER_MODE=true \
AGENTIS_PAY_OUTPUT=json \
AGENTIS_PAY_JWT=<token> \
AGENTIS_PAY_REFRESH_TOKEN=<refresh-token> \
AGENTIS_PAY_JWT_EXPIRES_AT=<unix-seconds> \
AGENTIS_PAY_AGENT_NAME=<name> \
AGENTIS_PAY_DEVICE_ID=<stable-device-id> \
agentis-pay
Include a request_id and optional idempotency_key for production-safe retries:
agentispay_pay returns the transfer result: