AI Talent Agencies Synthetic Influencers
Agencies are building AI influencers — synthetic personalities with their own face, handle, and following. Each one needs a financial identity on the internet: brands pay her, not the agency behind her.
Two products, one nervous system. Maya is an AI employee that works inside your Payouts.com tenant. Agent Identities let you provision financial identities for the external agents you ship to customers — each with its own email, card, rails, and MCP credentials.
Claude Sonnet 4.6, wrapped in a LangGraph state machine, running in-process inside your Payouts.com tenant. She has her own email at maya-{you}@agent.payouts.com, her own MCP key, and access to 30+ platform tools. She onboards vendors, collects tax forms, matches invoices, creates payouts, and chases on WhatsApp, email, or voice.
Maya loads tools at runtime via MCP. Each call is scoped to your tenant, hits the same storage layer your team uses, and is fully auditable.
Watch Maya's active conversations, tool calls, and decisions stream in real-time. Filterable by channel, vendor, severity.
autoApproveInvoices · autoCreatePayouts · fraudCheckEnabled · callEnabled · weekendPause. Every flag auditable.
One encrypted key per tenant, injected at run-time, never in UI metadata. Rotate anytime.
Your customers ship agents that need to send money, receive money, hold a card, and prove who they are. Payouts.com provisions a complete financial identity in eight steps — email, phone, collection accounts, payout rails, virtual card, limits — and hands your agent an API key plus an MCP endpoint it can call from day one.
source_type = agent_identity.
Give the agent an identifier. Pick a purpose from presets (Sales SDR, Support, Procurement, Finance, Ops). Assign a human principal — the person accountable for this agent's actions.
Every identity gets a real mailbox at {slug}@agent.payouts.com. Inbound mail is available via the Inbox API. The agent can send outbound mail using its own API key — no third-party email service required.
We're rolling out per-agent phone provisioning — dedicated numbers for SMS and two-way voice (ElevenLabs-powered). Skip for now; enable with one click when it ships.
Spin up a Global Account in 40+ jurisdictions. Each account exposes its own capabilities — e.g. UAE supports Domestic IPI (0–1d), Domestic RTGS (0–1d), International SWIFT (0–3d). One click per country.
Pick from your enabled rails. Each one exposes the routings it can be triggered through — Transfer, API, Payout Link, AP Automation, Agent ID. Toggle on; server-side schema cascade adapts the rest of the agent's behavior.
Optional. Issues a virtual Visa on creation with a configurable spend limit. PAN is tokenized via VGS — your infrastructure never touches card data. Freeze, rotate, and top up from the admin dashboard.
Per-transaction, per-day, and per-month caps in USD. Leave blank for no limit. Add an ISO-country allowlist to geo-fence the agent. Limits are recorded today and enforced by the agent-auth middleware as it ships.
Final confirmation. On "Create Identity & Generate Credentials" we mint an API key (shown once), an MCP endpoint bound to the identity, the email inbox, the virtual card, and register the agent with id:agent-1 · iss:payouts.com.
Everything the wizard does, the API does. Mint an inbox, a card, a collection account, an MCP endpoint, and an API key — in one POST.
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.
Save the API key now — it's the only time the full key will be shown. Rotate it later from the identity detail page. Identity provisioning is live; credential enforcement ships alongside the agent-auth middleware.
Whenever a company delegates a repeated action to an agent — and that action touches money — the agent needs a real financial identity. Here's who's asking.
Agencies are building AI influencers — synthetic personalities with their own face, handle, and following. Each one needs a financial identity on the internet: brands pay her, not the agency behind her.
A network represents 2,000 websites across 40 countries. Each top-performing site runs an agent that negotiates rates, books campaigns, and settles to the publisher.
A marketplace gives every high-volume seller an agent that manages inventory financing, supplier payments, ad spend, and scheduled payouts to the seller.
Live-ops agents reward top players, pay tournament winners, and buy user-generated assets from creators — at scale, 24/7, across every region.
Mid-market companies deploy one agent per department — marketing buys ads, ops buys SaaS, facilities pays vendors. Maya matches receipts to invoices.
A staffing platform manages 10,000 contractors across 60 countries. Each pod (LATAM engineers, PH support, EU designers) has an agent that owns onboarding, timesheets, tax forms, and payroll.
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 a real participant in commerce, not a webhook.
One-time-reveal API key, scoped MCP endpoint, AES-256-GCM-encrypted at rest. No shared service accounts leaking into a hundred LLM prompts.
Both products ship in the same tenant. Run Maya for your finance ops. Provision Agent Identities for your customers' agents. One bill, one auditable ledger.