Accounts / Value infrastructure
Store value. Move value. Organise value. Program value. Accounts are the financial foundation behind the wider platform—for people, businesses, and autonomous agents.
The account layerValue + authority
A balance shows what is there. A Smart Account shows who can act, under what conditions, and how that action is recorded. Give people, companies, platforms, and software the same durable financial foundation—without rebuilding control logic for every new use case.
A Smart Account holds balances alongside the permissions, limits, and approvals that govern them. Money and mandate never drift into separate systems.
Start with one account. Add structured accounts for a person, team, product, or task without rebuilding identity, authority, or oversight at every step.
Balances, approvals, and policy decisions belong to the same financial record. Your team sees what happened, who authorised it, and what can happen next.
Account typesOne control plane
Personal, Business, and Agent accounts share one architecture. What changes is the mandate: who owns the value, who may act, and the controls required before money moves.
Personal accounts
Spend, save, and separate. The master smart account for one individual—and the root that opens programmable sub-accounts beneath it.
For every ownerOne durable model
People make personal decisions. Teams create operating policy. Software acts within a mandate. The architecture stays consistent as the owner, organisation, and complexity evolve.
Individuals
Personal
A clear home for daily money, longer-term goals, and the people you choose to share access with.
Freelancers and sole traders
Personal → Pro
Keep business income, taxes, and personal spending distinct without multiplying financial relationships.
Startups
Business
Launch with a treasury that is already multi-currency, collaborative, and ready for scrutiny.
Small and medium businesses
Business
Give departments their own operating room while finance keeps one accountable view of capital.
Enterprises
Business
Separate initiation, approval, and release with policy that matches how your organisation is governed.
Finance teams
Business
Operate from current financial state—not a reconciliation project—and preserve the decision trail behind every movement.
AI agents
Agent
Let software pay, settle, and procure within a mandate enforced outside the model itself.
Autonomous businesses
Business + Agent
Keep human ownership and machine execution on one control plane, with neither operating beyond its role.
Developers
Any type
Model the account structure your product needs through one API, with the hierarchy preserved in the ledger.
Digital platforms
Any type
Issue financial accounts that feel native to your product, each with its own balance, policy, and record.
PersonalDesigned around real life
Your Personal account is the root for value and authority. Create distinct accounts for independent work, shared commitments, or a young person—each with clear boundaries and an identity context already established.
Root account
Personal account
Identity, balance, and the authority to open everything below.
A segregated sub-account for freelancers and sole traders, keeping business income apart from personal spending.
A shared account co-owned by two or more people—partners, housemates, family—where movements can require more than one signature.
A restricted sub-account for a minor, linked to and supervised by the parent personal account that created it.
BusinessTreasury, without the blind spots
Receive in one currency. Pay in another. Give the right people the right authority. The Business account is a live system of record for company capital—multi-currency, multi-user, and designed to stand up to review from the first transaction.
The account brings settlement state, access policy, and the approval trail into one place. Finance works from the financial state itself—not a spreadsheet waiting to catch up with it.
Balances held natively, in every currency you operate in
Live settlement
EUR
€1,284,600.00
USD
$742,180.00
USDC
310,450.00 USDC
Incoming revenue
Settles on receipt
Outgoing payouts
Settles on release
Multi-user access with granular permissions — roles, approval thresholds, and an audit trail on every movement.
AgentAutonomy with boundaries
An agent should be able to pay for work without becoming the financial system's trust boundary. Agent accounts give software a treasury and a clear mandate, then enforce that mandate in the account layer—outside the model, prompt, or integration.
const session = await accounts.sessions.create({
account: "acc_agent_4f21c8",
expires_in: "6h",
allow: ["transfer", "swap"],
caps: {
per_transaction: "50.00 USDC",
per_hour: "500.00 USDC",
total: "2500.00 USDC"
},
counterparties: ["mch_compute_grid"]
});Scope a session key to one task, approved counterparties, and a defined expiry. When that work ends, the authority ends with it.
Set per-transaction, hourly, and lifetime caps at the account layer. An agent that exceeds its mandate is declined—not merely logged after the fact.
Support fine-grained payments for calls, inference, compute, or energy without putting a human into every operational decision.
Define which protocols, actions, and exposure limits are permitted. Requests outside the policy do not leave the account.
Revoke a key or freeze an account the moment operating conditions change. The agent loses authority at the source, not after a manual clean-up cycle.
CapabilitiesPolicy where value lives
Every account begins with the same financial primitives. Configure the rights, limits, settlement behaviour, and audit requirements that make sense for that account's owner and purpose.
Keep fiat and stablecoin balances side by side in one account, so operations are not forced through conversion at every edge.
Incoming revenue, releases, and policy decisions are visible in the account record as they happen—not deferred to a nightly interpretation layer.
Create purpose-built accounts beneath a root account. They inherit verified context while retaining their own balance, rules, and statement.
Decide per person, system, and account what can be viewed, initiated, approved, released, or revoked.
Require the right number of approvals at the right threshold—whether the account belongs to two people or a global finance team.
Issue narrowly scoped, short-lived credentials so an agent or integration never needs standing authority.
Enforce caps, approved counterparties, and category rules at the account—not in the judgment of whoever holds a key.
Allow direct protocol interactions only where the account owner has defined the action, venue, and exposure as acceptable.
Every movement, permission change, and approval is attributed to the verified actor or system that made it.
DevelopersModel the real world
Create the account, attach the owner and policy, then extend the hierarchy when the product needs a new financial boundary. The structure your customers see is the structure your ledger and permissions understand.
POST /v1/accounts
{
"type": "personal",
"owner": "idt_9c1f4a2b",
"currencies": ["EUR", "USD", "USDC"]
}
// then, underneath it
POST /v1/accounts/acc_2b91e7/sub-accounts
{
"type": "junior",
"owner": "idt_7d20e1a4",
"supervisor": "idt_9c1f4a2b",
"controls": {
"spend_limit": "50.00 EUR / week",
"requires_approval_above": "20.00 EUR"
}
}Build on AccountsThe financial control plane
Give every person, business, platform, and agent an account with explicit authority, policy they can trust, and a record ready for the moment it matters.