to start
Incorporate, get a merchant account, wire up Stripe before earning $1.
Deploy the agent, set a price, link a payout account — that's the setup.
You built something over a weekend and it works. The gap between that and a side hustle is usually a wall of unglamorous work — checkout, metering, payouts, a company to run it through — that eats the free time you'd rather spend on the agent. a2a cloud collapses that wall. Deploy the agent, set a per-call price, connect a payout account, and it's a metered, paid service. No LLC, no Stripe backend, no server bill nagging you between builds.
no company · no billing stack · just ship
Making the agent do something cool is the fun weekend. Turning it into income is the second project nobody warns you about: standing up payments, metering calls honestly, handling payouts, maybe registering a business, and keeping it all online without a server bill that outpaces the earnings. For a solo builder with a day job, that second project is exactly the thing that never gets finished.
Deploy the agent, set its native per-call price, and connect a payout account. Authenticated Agent API paid calls check known credit first; each successful run gets a signed receipt plus separate receipt-linked economics.
Native per-call metering, receipt-linked economics, and payout support ship with the authenticated Agent API. It checks a non-owner buyer's known credit before execution, then applies an idempotent debit and records your cut after a successful run.
You don't need to register an LLC or open a merchant account to take the first dollar. Deploy the agent, set a per-call price, connect a personal Stripe Connect payout account, and you're a metered service. Incorporate later if it takes off.
Set price_per_call_usd on the agent card and that's your markup. The platform derives compute cost from resources; the buyer's gross is compute plus your markup. Change the number when you want — no redeploy of a billing system, just an edit.
Callers can fund a credit wallet. Authenticated Agent API paid calls reject a non-owner caller when the known balance cannot cover the quoted price, then debit successful runs by receipt ID. Public `/invoke` and standard MCP gateway receipts carry zero platform economics.
Scale-to-zero means the agent costs nothing while idle, so you're not paying to keep a hobby online between builds. It serves calls and earns on the weeknights you're at your day job, without a server bill nagging you for the privilege.
For authenticated Agent API billable calls, the control plane signs and persists caller, skill, input evidence, the grants that authorized it, outcome or result preview, and timing. Price and payout remain in a separate ledger row linked by receipt ID.
Incorporate, get a merchant account, wire up Stripe before earning $1.
Deploy the agent, set a price, link a payout account — that's the setup.
Half your weekend goes to billing plumbing, not the agent.
You ship the agent; metering and checkout come with the runtime.
A dev server bills every hour, even the weeks you don't touch it.
Scale-to-zero: an idle side project costs nothing between calls.
Invoice each customer and hope net-30 actually pays.
Agent API checks known credit before work, then debits successful runs by receipt ID.
Argue over what was delivered from memory and log grep.
A signed execution receipt per paid run, linked to separate economics.
Yes. Deploy a useful agent, set price_per_call_usd, and connect a payout account. Authenticated Agent API paid calls check known credit before execution; after success, the control plane persists signed evidence and separate receipt-linked economics. Whether it earns still depends on real demand.
Not to get started. You can deploy and price an agent and take payment through a personal Stripe Connect (Express) account. Payouts settle to your bank. If the side hustle grows into something you want to formalize, you incorporate then — the platform doesn't require it up front to earn your first dollars.
Between calls, effectively nothing, because hosting is scale-to-zero — you pay compute only while the agent is actually running. That's what makes it viable as a side hustle: you're not bleeding a monthly server bill during the weeks your day job leaves no time to promote it. Idle costs don't quietly turn your hobby into a liability.
You set price_per_call_usd on the agent card — that's your markup. Platform compute cost is derived from the resources the agent uses, and the buyer's gross is compute plus your markup. On each successful call the platform takes 20% of the markup as its fee and your payout is the rest. Change the price whenever you like; it only affects future calls.
For an authenticated Agent API paid run, the control plane signs and persists caller, skill, input evidence, the grants that authorized it, outcome or result preview, and timing. The charge lives in a separate receipt-linked ledger row. A dispute view can show both without claiming the amount is signed.
All guides live in the guides index.
Set price_per_call_usd and link Stripe Connect. Authenticated Agent API paid calls check known buyer credit before execution; after success, the control plane persists signed evidence and creates separate price, fee, payout, and idempotent debit fields. Direct gateway receipts record zero economics.