[Feature request] Server-side deposit addresses + capability descriptor for agent wallets

Context

We're building Open Agent Wallet (https://github.com/Abelhubprog/open-agent-wallet) — a vendor-neutral, open (Apache-2.0) standard + reference implementation for AI agents that are autonomous economic actors (hold a wallet, bind to many trading venues, fund across chains, act safely from a chat surface). Privy's server-wallet-v2 / agent wallet is our default Mode A spending authority, and it composes beautifully: because Virtuals' EconomyOS agent wallets are also built on Privy, a Privy agent wallet and a linked Virtuals wallet share one signer substrate.

Two targeted, additive surfaces would turn "Privy has the pieces" into "Privy is the turnkey substrate for agent economic actors." Reference adapter that consumes these: @oaw/adapter-privy (interface in our repo, currently injected via callbacks).

---

Ask 1 (highest value) — server-side chain-agnostic deposit address for agent wallets

useDepositAddress is great for users, but an agent is funded by a backend, not a browser hook. We'd like to generate deposit addresses headlessly with a server/agent wallet as the destination:

POST /v1/wallets/{agent_wallet_id}/deposit-address
  { "source_chains": ["eip155:1","eip155:56","solana:..."], "asset": "USDC" }
→ { "addresses": [{ "chain": "...", "address": "..." }],
    "destination_chain": "...", "estimated": {...} }

This unlocks "deposit USDC from any chain → the agent funds the venue" without a user present — the single piece devs can't easily build themselves.

Ask 2 — non-secret agent-wallet capability descriptor

A read API returning { supported_chains (CAIP-2), policy (spend_caps, allowed_methods, allowed_destinations), signer_status } so a backend can route funding/execution and surface limits without holding secrets or inferring.

Ask 3 (nice-to-have) — provider-signed action receipts/webhooks

{ wallet_id, action, chain, tx_hash, policy_decision, timestamp, signature } for tamper-evident ledgering of autonomous money movement.

---

What we contribute back

• An open-source @oaw/adapter-privy reference implementation.
• A conformance suite (Mode A idempotency, no-secrets, policy enforcement, deposit-address routing) you can run against changes.
• A working end-to-end demo (bind → fund → trade from chat) already passing in our reference repo.

Minimal viable subset: if only one ships, Ask 1. Happy to pair on the API shape. — Abelhubprog · Open Agent Wallet