Synthetic influencerspaid like real talent
Agencies build AI personas with their own face, handle, following. Brands contract with the persona directly — the handle is the IP. She pays her own GPU time, voice license, stylist model.
Every AI agent you deploy needs to send money, receive money, hold a card, sign for itself. AgentWallet provisions a complete financial identity — inbox, phone, collection accounts, payout rails, virtual card, API key, MCP endpoint — in one call.
One email. One API key. One MCP endpoint. Every outbound call is signed, every inbound message captured, every transfer tagged source_type = agent_identity in your ledger.
Every identity gets a real mailbox at {slug}@agent.wallet. Read inbound via the Inbox API. Send outbound signed by the agent's own key — no third-party SMTP needed.
Scoped, rotatable, one-time-reveal. Every outbound tool call, transfer, card charge is signed by the agent itself — never a shared service account shared across a hundred LLM prompts.
A scoped MCP server is provisioned per identity. Your agent calls mcp://agent/{slug} for wallet, card, inbox, ledger — with its limits and policy enforced server-side.
Give each agent an identifier, an inbox, a phone, collection accounts, payout rails, a virtual card, limits, and a policy — in one wizard, or one POST.
Pick a slug (becomes the email + MCP route). Choose a purpose preset — SDR, Support, Procurement, Finance, Ops. Assign a human principal who's accountable.
Real mailbox. Inbound via Inbox API, outbound signed by the agent's key. No third-party SMTP.
Per-agent phone provisioning — dedicated numbers for SMS and two-way voice. Skip for now, enable when it ships.
Spin up a Global Account in 40+ jurisdictions. Each exposes its own capabilities. One click per country.
Toggle each rail. Rails expose the routings they can be triggered through — Transfer, API, Payout Link, AP Automation, Agent ID.
Optional virtual Visa, configurable spend limit. PAN tokenized via VGS — your infrastructure never touches card data.
Per-transaction, per-day, per-month caps. ISO country allowlist. Enforced by the agent-auth middleware server-side — so a prompt injection can't drain the float.
On create we mint an API key (shown once), an MCP endpoint, an inbox, a virtual card, and register the agent with id:agent-1 · iss:payouts.com.
Whenever a company hands a repeated, money-touching action to an agent — that agent needs a real financial identity. Not a shared service account.
Agencies build AI personas with their own face, handle, following. Brands contract with the persona directly — the handle is the IP. She pays her own GPU time, voice license, stylist model.
A network represents 2,000 sites in 40 countries. Each top site runs an agent negotiating rates, booking campaigns, settling to publishers on local rails.
A marketplace gives every high-volume seller an agent that manages inventory financing, supplier payments, ad spend, scheduled payouts.
Live-ops agents reward top players, pay tournament winners, buy user-generated assets — at scale, across every region.
One agent per department — marketing buys ads, ops buys SaaS, facilities pays vendors. Receipts match invoices automatically.
A staffing platform manages 10,000 contractors. Each pod (LATAM eng, PH support, EU designers) has its own agent for onboarding, timesheets, tax forms, payroll.
One POST to /v1/agents mints an inbox, a card, a collection account, an MCP endpoint, and an API key. Every transfer is ledgered as source_type = agent_identity.
Agents don't need another permission grant.
They need their own passport.
An email a human can reply to. A card a merchant can charge. An account a vendor can wire into. A key that rotates when that one agent gets compromised — without taking down the fleet.
Every payout, email, and tool call is tagged with the identity. If an agent misbehaves, you know which one, when, why — and you revoke without taking down the fleet.
Your agent has an email a human can reply to, a card a merchant can charge, a bank account a vendor can wire into. It's not a webhook — it's a counterparty.
One-time-reveal API key, scoped MCP endpoint, AES-256-GCM at rest. No shared service accounts leaking into a hundred LLM prompts.
One API call. One inbox. One card. One MCP endpoint. One rotatable key. For every agent you deploy.