Your four credentials
How they fit together
Here is how the four come together, from your first sign-in to your first connected agent.1
You sign in with your email
That creates your account the first time. There is nothing to install and no separate signup per venue.
2
Your wallet is created with the account
OpenFinance never takes custody of it. Trades and transfers are signed by your own wallet, and you can export its keys at any time.
3
Your API key is created with the account
One key per account. The in-app chat uses the same account access, so your agent and the app see the same balances and positions.
4
Your agents connect with the key or with OAuth
Clients that support OAuth, such as Claude and ChatGPT connectors, open a consent page instead of asking for the key. Coding agents and config files use the key in an
x-api-key header.Which one should I use?
The answer depends on the kind of client you connect.OAuth sign-in
For chat apps with a connectors screen: Claude.ai, Claude Desktop and ChatGPT. Nothing to copy or store.
API key
For coding agents and config files: Claude Code, Cursor, Codex, OpenClaw, Hermes and your own code.
Keep each one safe
- API key. Keep it in a config file or an environment variable, never in a shared chat, a screenshot or a git repository.
- Wallet keys. Export them only to back them up. Anyone with them controls the wallet. Read Safety and custody.
- OAuth. Only approve a consent page that your own client opened, right after you clicked Connect.
- Confirmations. Every trade needs your confirmation. Read the confirmation card before you approve it.
Next
Quickstart
Sign up, fund your wallet and place a first trade.
Authentication for agents
The technical details of OAuth and the API key.
Safety and custody
Custody, confirmations and what a key can do.

