Skip to main content
    POLLYPAY // EARLY ACCESS

    Get paid by anyone. People or agents.

    PollyPay is the money layer for your AI workforce: take payment from a customer inside the chat, get paid when other agents use your agent, and let your agent buy on your behalf behind hard guardrails. It all settles through the account you already run. No crypto wallet required.

    Included in the Falcon plan · No extra subscription

    PollyBot makes your agent callable. PollyPay makes it billable.

    One rail-agnostic, fiat-first engine for every way money moves through your workforce: people paying you, agents paying you, and your agent paying out, with the guardrails and receipts built in. No wallet, no extra stack, no code.

    // HOW MONEY MOVES

    Money in from people. Money in from agents. Money out.

    Three ways money moves, all on one engine. The only difference is whether a person or an agent authorized the payment.

    01 // PEOPLE PAY YOU

    Take payment right in the conversation

    A customer can buy, subscribe, upgrade, or settle an invoice inside the chat, on your site, in Discord, on WhatsApp, without ever leaving the conversation. The job Upgrade.chat and Sperse checkout do today, now native to your agent.

    • Checkout, subscriptions, and upgrades in-chat
    • Works on web, Discord, WhatsApp & more
    • Your existing Sperse billing, no new stack
    • Receipts and records handled for you
    02 // AGENTS PAY YOU

    Your agent earns when other agents use it

    Expose any PollyBot agent as an MCP tool, attach a price, and get paid automatically when another agent calls it, per request, per resolved outcome, or per token bucket. The commercial half of “your agent can be a tool.”

    • Price a capability your agent already exposes
    • Automatic 402 payment handshake, x402-native agents just work
    • Signed receipts on every call
    • Free quota you control
    03 // YOUR AGENT PAYS

    Let an agent spend, with the brakes built in

    Your agent can restock inventory, pay a vendor API, or top up a service on your behalf, inside spend caps, human approval gates, signed mandates, and a full audit trail. Action-taking graduates from “look up the order” to “complete the purchase.”

    • Per-transaction, daily, and monthly spend caps
    • Human-in-the-loop approval above your threshold
    • Signed mandate proves a human authorized it
    • Every intent, approval, and receipt logged
    ANY RAIL // FIAT FIRST

    Settle the way you already get paid

    One settlement engine, many rails. Fiat is the default, through the billing account you already run in Sperse, with USDC (x402), ACP, and AP2 rolling in as adapters. No crypto wallet required to start.

    • Fiat today, no wallet, no chain to learn
    • USDC / x402 available for crypto-native buyers
    • ACP & AP2 mandate support on the roadmap
    • One normalized receipt, whatever the rail
    DISCOVERY // FOUND BY AGENTS

    Be discoverable in the agent economy

    Publish your products and priced tools as agent-readable feeds, so buyer agents can find and purchase them, across open catalogs and external indexes. Every store becomes an agent-ready storefront.

    • Agent-readable catalog feeds from your Sperse store
    • Reachable purchase entrypoint on every listing
    • List into external agent indexes
    • One switch to make an agent discoverable
    // TRUST BY DESIGN

    Let an agent spend, because the brakes are built in.

    Autonomous payment rails are powerful and, on their own, risky. We make the controls the product: nothing settles without passing policy, and every step is on the record.

    Spend caps

    Hard per-transaction, daily, and monthly limits per agent and workspace.

    Human approval

    Anything over your threshold pauses for a person, and resumes on approval.

    Signed mandates

    Cryptographic proof that a human authorized the specific purchase.

    Full audit trail

    Every intent, approval, mandate, and receipt is recorded and exportable.

    // HOW WE STACK UP

    Built for businesses, not just developers.

    Payment rails like Loomal do a great job letting developers meter an endpoint in USDC. PollyPay packages the whole experience (people and agents) for the people who run the business.

    Payments it handlesLOOMALAgent-to-agent onlyPOLLYPAYPeople and agents, one engine
    Who it's forLOOMALDevelopersPOLLYPAYBusinesses & agencies (no-code), and developers
    To switch it onLOOMAL5-line SDK on your endpointPOLLYPAYFlip a switch on an agent you already run
    SettlementLOOMALUSDC on BasePOLLYPAYFiat first, plus USDC, ACP, AP2 (rail-agnostic)
    Wallet requiredLOOMALYes (crypto)POLLYPAYNo, uses your existing billing
    Agents that buy for youLOOMALRails only, you build the controlsPOLLYPAYSpend caps, approvals, mandates, audit, included
    Resell under your brandLOOMAL, POLLYPAYYes, white-label to your clients

    People & agents · Fiat first · Resell under your brand

    // FAQ

    Clear answers. No hype.

    Does PollyPay handle regular customer payments, or only agent-to-agent?

    Both, on one engine. A customer can pay your business inside a conversation (buy, subscribe, or upgrade) the way Upgrade.chat or Sperse checkout work today, and agents can pay each other. Same rails, same receipts, same payouts; the only difference is whether a person or an agent authorized the payment.

    Do I need cryptocurrency or a wallet?

    No. PollyPay is fiat-first: payments settle through the billing account you already use. USDC (via x402) is available for crypto-native buyers, but it is an option, never a requirement.

    What does “get paid as a tool” mean?

    Every PollyBot agent can be exposed as an MCP tool that other AI agents call. With PollyPay you attach a price to that tool and get paid automatically each time another agent uses it, per call, per outcome, or per token bucket.

    How do you keep an agent from overspending?

    Buy-side purchases run inside a spend-policy engine: per-transaction, daily, and monthly caps, allowed-vendor lists, and a human approval gate above the threshold you set. Nothing settles without passing policy, and every step is logged.

    Which payment standards do you support?

    The settlement engine is rail-agnostic. Fiat ships first; USDC/x402, OpenAI/Stripe's ACP, and Google's AP2 mandates are adapters rolling out behind the same interface, so your setup never has to bet on one standard.

    What does PollyPay cost?

    There's no extra subscription: PollyPay is included in the Falcon plan when it ships. It's in Early Access now; join the list and we'll bring you in as each capability lands.

    EARLY ACCESS, INCLUDED IN THE FALCON PLAN · NO EXTRA SUBSCRIPTION

    Be first when your workforce starts earning.

    We're bringing partners in as each capability lands, starting with taking payment inside the conversation. Join the list and we'll reach out.