Treasury
Allocate to Wallet
Vault → pocket internal USDC transfer (server-signed orgs only)
POST
Allocate to Wallet
Allocates USDC from the organization vault to an agent pocket. This is the Allocate from Vault path — an internal transfer signed by the server on behalf of the vault.
The route path (
The target org is browser-signed; vault allocation is not available because the server holds no vault signer. Use Deposit to Wallet (external on-chain transfer to the pocket’s address) instead.
See Error Codes for the full enumeration.
This is a convenience alias for
POST /v1/orgs/:id/transfers/fund scoped to a single wallet. The vault is resolved automatically from the wallet’s organization.…/fund) is preserved for backward compatibility. The user-facing action is “Allocate”, not “Fund” — funding now refers specifically to external deposits.
Request Body
Response Fields
Errors
400 VAULT_ALLOCATION_UNAVAILABLE
The target org is browser-signed; vault allocation is not available because the server holds no vault signer. Use Deposit to Wallet (external on-chain transfer to the pocket’s address) instead.
404 NOT_FOUND
wallet_id does not exist or the caller is not authorized for the organization that owns it.
See also
- Wallet Details — inspect
funding.vault_allocation.availablebefore calling this route - Allocate from Vault — the org-scoped variant that accepts explicit vault + pocket ids
- Deposit to Wallet — external on-chain funding path (universal; works in both signing modes)