Skip to main content
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.
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.
Server-signed orgs only. This route requires the server to sign with the vault private key. In browser signing mode the server has no vault key, so the call returns 400 VAULT_ALLOCATION_UNAVAILABLE — browser-signed orgs must use Deposit to Wallet (external on-chain transfer) instead. Check funding.vault_allocation.available on GET /v1/wallets/:wallet_id before calling this route.
The route path (…/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.
See Error Codes for the full enumeration.

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.available before 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)