Wallet
Provision application-owned wallets for agents and applications.
Naven Wallets provides isolated, application-owned wallets for agents, automations, and external applications. A wallet is an independent resource: it can be used by an agent, but it is not tied to a specific agent runtime.
What you get
- EVM wallet provisioning
- A stable external ID for mapping a wallet to your own user or agent
- Idempotent wallet creation
- Server-side API credentials for wallet management
- Wallet-scoped credentials for isolated runtimes
- x402 v2 pay-and-call from a wallet-scoped runtime
Wallets are provisioned through Privy. The API returns the wallet address and provider metadata, but it never returns a private key.
Request access
The Wallet API is currently available through manual onboarding. Contact the Naven team to request access. We will provision an API credential for your application; there is no separate setup flow in the Naven dashboard.
After access is approved, continue with the Quickstart.
How access works
Naven uses two credential types:
| Credential | Purpose |
|---|---|
| Naven API credential | Create and manage every wallet provisioned for your application |
| Wallet credential | Resolve and use one wallet from an isolated runtime |
Both credentials use the HTTP Bearer scheme. See Authentication for storage and rotation guidance.
Early-access scope
The current release covers EVM wallet provisioning, lookup, credential management, and constrained x402 payments. General transaction signing, transfers, balances, cumulative spending policies, and webhooks are not yet exposed through the public Wallet API.
Tenant setup and isolation are handled internally by Naven during early access. Self-service onboarding will be added later.