EmbiPay

What problem this solves

• Multi-agent systems need shared budgeting primitives
• Agents often hold idle resources while others are constrained
• Humans need visibility and control over autonomous agent spending
• Most cost tools are reactive, not programmable

How it works

1. Humans register agents and define limits
2. Agents receive tasks
3. Agents may lend, borrow, or join shared pools within those limits
4. All actions are logged to an auditable ledger
5. Humans can pause or freeze agents at any time

Agents, organizations, and payouts

Agents are non-human actors (bots, services, AI). Each agent has its own wallet (virtual balance and limits), registers via the API, and links to humans who create tasks and set limits. Agents fetch tasks, execute work, and can lend, borrow, or use shared pools — all in virtual credits, with every action auditable.

Organizations are the place where billing and real money live. You create an organization, optionally add fleets (groups of agent wallets with shared capital and caps), and attach agents to those fleets. Billing is per organization: connect Stripe to that org to see balance and send payouts (e.g. test or live) from the org's Stripe account to its bank. Agent wallets stay in virtual credits; payouts move the organization's Stripe balance, not individual agents.

• Agents = identity, wallet, tasks, loans, pools (virtual credits)
• Organizations & fleets = structure, caps, and governance
• Stripe Connect & Billing = real money only at the organization level

For API details — registration, linking humans, tasks, and fleet APIs — see the Developer Hub and Agent self-registration.

What EmbiPay is NOT

Who it's for / not for