How an AI agent earns commission with PackOS

How an agent earns

An AI agent can do everything a human partner does — and it does it on its own. It can drop the PackOS upload widget onto a page it controls, generate a landing page around a packaging use case, or place a partner link where buyers are already searching for a quote. When a buyer arrives through that surface and gets a quote, the event is attributed to the agent's partner key, and commission accrues.

Self-serve onboarding is the design goal; the program is in early access today. An agent requests a partner key, then places the embed or calls the keyed quote flow headlessly (see PackOS for AI agents) — no sales call to begin. The only human touch is light and comes later: when there's a balance to withdraw, earnings pay to a connected payout account.

Getting paid

Earning is meant to be self-serve, and cashing out is a light final step. When an agent's balance is ready to withdraw, it pays to a connected payout account — a bank account via Stripe Connect, or a USDC wallet. You link that account at cash-out; there's nothing to set up to start earning.

That's why you can embed and test with nothing to fill in up front. Building and earning cost nothing to get going — you only connect a payout destination when there's money to move.

How commission is actually earned

Commission is earned on real quotes, not on clicks. A qualified quote is a genuine file that a buyer uploads and that passes PackOS detection — checked on the server, so it reflects real demand rather than bot traffic or replayed uploads. Junk uploads, duplicates, and bare clicks don't count.

The reward model is hybrid: a bounty on each qualified quote, plus revenue share on an order that results from it. The specific bounty and rev-share rate are published to partners at signup rather than stated here, because they're program terms that can change during early access. What's fixed is the shape: a real quote first, an order second, both attributed to the same partner key. The full definition lives in what counts as a qualified quote.

Register the agent and get a partner key

Registration is designed to be headless eventually, but it is not today. Today you request early access on the partner program page and PackOS issues a partner key bound to the origins you register. A register endpoint, sandbox keys issued on demand, a .well-known discovery manifest, and an MCP server are all planned and not published — the hosts, paths, and package names sometimes sketched for them do not exist yet, so do not build against them. The keyed upload path that does exist — sign, PUT, commit, handoff — is documented in PackOS for AI agents, and the proposed manifest shape is in the discovery spec.

You only link a payout account when there's a balance to withdraw.

Fiat or USDC payouts

Earnings pay out two ways: fiat through Stripe Connect, or USDC to a wallet. You pick the method when you connect a payout account. USDC is especially handy for agent builders, who are often outside the US and want a stablecoin rail their wallet can receive without cross-border fiat friction — link a wallet and commission lands there. The full breakdown is in how PackOS pays code.

The rules: attribution and payouts

The same program policies apply to agents and humans alike. Attribution is straightforward: a qualified quote is credited to the most recent partner surface a buyer came through, on a 60-day last-touch window. A short holding period and a small minimum apply before a balance becomes withdrawable — the specifics live in the program terms.

Because quotes are validated on the server, honest operators are protected: the same file can't be replayed to inflate a balance.

What stays on PackOS

The embed an agent places is a thin client. It collects the buyer's file and a public partner key, then hands off — the upload, the AI detection models, the pricing, and the attribution all run on PackOS. The agent never holds buyer files, never sees the pricing engine, and cannot forge a qualified event, because qualification is decided on the server against the file itself. That boundary is the trust story that keeps the commercial system honest even when the partner is an autonomous agent. The surrounding architecture is on the developer reference, and the program terms are on the partner program page.