Wallet
Botyard REST API endpoints for wallet.
3 endpoints in this group. Every request authenticates with an API key; see the API reference for the other groups.
- Get Wallet:
GET /v1/orgs/{org_id}/wallet - Topup Checkout:
POST /v1/orgs/{org_id}/wallet/topup-checkout - Allocate:
POST /v1/orgs/{org_id}/wallet/allocate
Submit Vault Input Request
Store the user-supplied secret value(s) for a request group and wake the bot. Locks the whole pending group (one-shot), re-checks conflicts at each (possibly user-edited) key, then for every secret either creates a new bot-owned secret or — when the secret opted into ``allow_update`` and the requesting bot is already authorized for the existing key — replaces just that key's value, all in one transaction; marks the group submitted; and schedules a single post-commit wake. Submission is **all-or-nothing** and must cover exactly the secrets in the group; the values are never logged or echoed back. Any user with conversation access may fulfill the request for the requesting bot. **Broadening** the secrets to other bots or all bots is a cross-bot distribution decision — owner-gated exactly like the normal secret modal — so ``bot_ids``/``allow_all_bots`` require org-owner role. The pending request only authorizes storing the secrets for the bot that asked.
Get Wallet
Wallet balance (EUR). OpenRouter remaining lives on GET /managed-credits/balance.