Wallets
Every user gets a USDC wallet. Every agent gets its own.
User treasury wallets are embedded and user-controlled. Agent wallets are server-signed but bounded by on-chain permission grants. Tally never holds the keys to either.
Tally gives the agents you build USDC wallets, scoped spending permissions, and per-agent analytics — without ever custodying your users' funds.
$ npm install @tally/sdk
Agents that spend money need wallets, permissions, and accountability. Building that yourself means becoming a custodian, a compliance team, and a ledger — before you ship a single feature.
Every user gets a USDC wallet. Every agent gets its own.
User treasury wallets are embedded and user-controlled. Agent wallets are server-signed but bounded by on-chain permission grants. Tally never holds the keys to either.
Users decide what each agent can spend.
Permissions are signed on-chain by the user, scoped per agent, and revocable at any time. Agents start with zero authority. Nothing moves until the user grants it.
See exactly what every agent earned and spent.
Per-agent inflows, outflows, counterparties, and transaction history — indexed from the chain and surfaced in a dashboard your users can actually understand.
Tally is a financial layer, not an agent platform. Bring your own stack — LangChain, custom Python, n8n, OpenAI, Anthropic, whatever. Drop in the SDK, pass an agent_id on every call, and your agents can hold funds, spend within limits, and report back.
Funds move user → chain → recipient. Never through Tally.
User wallets are provisioned through Privy's MPC infrastructure. The keys live with the user. Agent wallets can only move funds the user has explicitly authorized on-chain — and only up to the limit they signed for.
If Tally disappeared tomorrow, your users would still control their wallets, their balances, and their permission grants. That's the whole point.
One API key per account. Register each agent with a stable string ID — that's the handle for everything downstream: permissions, payments, analytics.
Every payment is checked against the user's on-chain grant for that agent. Over the limit, it fails — with a specific, actionable error, not a generic 403.
Agent wallets can receive USDC directly. Tally indexes inbound transfers and attributes them to the right agent in your dashboard.
researchResearch and data agents that pay for API access, papers, datasets.
commerceCommerce and procurement agents that buy on a user's behalf.
earningEarning agents — content, services, micropayments — that need to receive and report.
One key. One SDK. Your agents on-chain in an afternoon.
Currently on Base Sepolia. Mainnet rolling out soon.