Overview
What you need before your first call to the Walletguide API, and which credential to pick for what you are building.
Two things stand between you and a first response: a credential, and a wallet id.
Pick a credential
An API key
A wg_ key, scoped to one wallet. For scripts, CI, a local MCP server, anything without a person sitting in front of it.
OAuth
Browser sign-in, for a tool acting on someone else's behalf. What `walletguide login` and the hosted MCP endpoint use.
A key is the shortest path and the right one for your own automation. OAuth is what you want when the person and the software are not the same party: they approve the scopes, they can revoke it, and the grant is theirs rather than a secret you hold.
Then a wallet
Almost every route is scoped to one wallet, and the id is a uuid rather than a name. An API key already belongs to a wallet, so the CLI and the MCP server work it out on their own. Otherwise ask:
curl -H "Authorization: Bearer $WALLETGUIDE_API_KEY" \
https://api.walletguide.com/wallets