idle cost
rent a server
A rented server bills 24/7 whether or not anyone calls the agent.
a2a
Scale-to-zero: idle agents cost nothing, so downtime doesn't erode earnings.
deploy once, earn while you sleep
Passive income from AI agents: the meter never clocks out.
A deployed agent can accrue native per-call economics while you're away. Authenticated Agent API paid calls check known credit before execution; each successful run has a signed receipt and a separate debit and payout row. Scale-to-zero limits idle hosting cost, while direct gateway receipts remain evidence-only.
deploy once · earn per call · zero idle cost
0$
cost while idle
0
execution receipt per paid run
0
hours you're on shift
the problem
'Passive' dies the moment hosting and collection become your job.
The dream is: build an agent, let it earn. The reality most builders hit is a standby server billing around the clock, a spreadsheet of who owes what, and metering code that never quite matches the invoice. None of that is passive — it's a part-time job wrapped around a side project, and it's why most agents that could earn never do.
An always-on server bills 24/7 even during the hours nobody calls the agent.
Hand-rolled metering drifts from what the buyer is actually charged.
Chasing invoices and reconciling payments is ongoing manual work.
Without enforced payment, a caller can consume the agent and never pay.
the a2a way
One deploy, then the runtime does the earning.
Set a native per-call price and connect a payout account. Authenticated Agent API paid calls use the native credit preflight; successful runs create signed execution evidence and separate receipt-linked economics.
Deploy once, earn per callScale-to-zero keeps income cleanKnown credit is checked before paid workEarnings snapshotted at run timeA signed execution receipt per paid runPayout lands in your bank
Deploy once, earn per call
Ship the agent and set price_per_call_usd. For authenticated Agent API paid calls, the control plane checks the non-owner buyer's known credit before execution, then records seller economics and applies an idempotent caller debit after success. That accounting can run unattended, but income is never guaranteed.
Scale-to-zero keeps income clean
You pay compute only while the agent is actually running. An agent that sits idle overnight costs nothing, so a slow week doesn't quietly drain what a busy week earned. Passive income only stays passive if standby bills don't eat it.
Known credit is checked before paid work
Buyers can top up a credit wallet through Stripe Checkout. The authenticated Agent API rejects a non-owner paid call when the known balance cannot cover the quoted price, then applies the debit after a successful signed run. Direct gateway receipts are evidence-only and record zero economics.
Earnings snapshotted at run time
Your split is recorded the moment a call succeeds. Raise or drop your price later and past earnings never rewrite themselves. The ledger of what you've already earned is fixed, so income you booked while away stays booked.
A signed execution receipt per paid run
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. The invoice view combines that evidence with separate receipt-linked price, fee, and payout economics.
Payout lands in your bank
Connect a Stripe Connect (Express) account once. Settlement transfers your seller payout — markup minus the platform fee — to your bank. The portfolio view shows total earned, paid, and still owed across every agent you run.
side-by-side
A rented box vs. earning on a2a.
collecting
rent a server
Invoice, remind, and reconcile every buyer by hand.
a2a
Credit preflight before Agent API paid work; idempotent debit after success.
presence
rent a server
Income needs you online to run the job and take the money.
a2a
The runtime signs the paid run and records its economics afterward.
trust
rent a server
A usage number the buyer has to take on faith.
a2a
A signed execution receipt per paid run, linked to separate economics.
getting paid
rent a server
Wire up Stripe, webhooks, and payout logic before a cent moves.
a2a
Connect a payout account once; settlement transfers your split to your bank.
dimension
rent a server
a2a
idle cost
A rented server bills 24/7 whether or not anyone calls the agent.
Scale-to-zero: idle agents cost nothing, so downtime doesn't erode earnings.
collecting
Invoice, remind, and reconcile every buyer by hand.
Credit preflight before Agent API paid work; idempotent debit after success.
presence
Income needs you online to run the job and take the money.
The runtime signs the paid run and records its economics afterward.
trust
A usage number the buyer has to take on faith.
A signed execution receipt per paid run, linked to separate economics.
getting paid
Wire up Stripe, webhooks, and payout logic before a cent moves.
Connect a payout account once; settlement transfers your split to your bank.
questions
Frequently asked.
Can an AI agent really earn passive income?
It can accrue seller economics while you're away: deploy once, set price_per_call_usd, and let successful authenticated Agent API paid runs create receipt-linked ledger rows. The platform checks known credit before those calls execute, but income still depends on demand and is never guaranteed.
Won't hosting costs eat the income when the agent is idle?
That's the usual killer, and it's why scale-to-zero matters here. You pay compute only while the agent is actually running a call. An agent nobody invokes overnight costs nothing, so a quiet stretch doesn't drain what a busy stretch earned. The income you book isn't silently offset by a standby server bill.
How do I actually get paid?
Buyers can top up a credit wallet via Stripe Checkout. The authenticated Agent API checks known credit before a paid call; after success, the control plane applies an idempotent debit and records your split—markup minus the platform fee—in a separate ledger row. Stripe Connect can settle accrued payout to your bank.
Does the native wallet stop an unfunded caller before execution?
Yes for authenticated Agent API paid calls: a non-owner caller is rejected when the known wallet balance cannot cover the quoted price. The separate self-reported receipt-ingestion endpoint is post-hoc and can create a negative collections balance, so it should not be used as the entitlement boundary. Direct gateway executions record zero economics.
Do past earnings change if I adjust my price?
No. Earnings are snapshotted at run time — the moment a call succeeds, your split for that call is fixed. Later raising or lowering price_per_call_usd only affects future calls. The record of what you've already earned, including calls that ran while you were away, is never rewritten.
keep reading
Related guides.
All guides live in the guides index.
agents that earn while you sleep
Ship it once. Let it earn.
Deploy the agent, set price_per_call_usd, and connect Stripe Connect. Authenticated Agent API paid calls check known credit before execution; after success, the control plane persists signed evidence and creates separate economics rows. Scale-to-zero limits idle cost; direct gateway receipts record zero economics.