Developers

Developer Payout Terms

How AgentAds developer earnings, clearing, Connect onboarding, manual beta payouts, reversals, and support work.

Last updated 2026-06-18

These terms explain how developer earnings work during the AgentAds beta.

Do not treat dashboard, CLI, or portal balances as a promise of immediate payment. Balances can be pending, under review, delayed, adjusted, or reversed under the rules below.

Earning credits

  • Developers earn only for eligible, viewable, accepted ad events attributed to a signed-in device.
  • Duplicate events, expired tokens, invalid traffic, tampering, automation, or fraudulent activity do not qualify.
  • A displayed ad can be credited once for the same fill, ad, and display nonce even if additional wait samples arrive.
  • Earnings may depend on advertiser billing, campaign budget, invalid-traffic review, and reconciliation.

Balance states

  • Pending earnings are credited but have not cleared the hold window or invalid-traffic gate.
  • Cleared earnings have passed review and may be eligible for payout if payout requests are enabled and other requirements are met.
  • Processing payouts reserve cleared balance while provider transfer work is attempted.
  • Paid, failed, reversed, or bank-settlement states may appear after Stripe or support updates the payout record.

Beta payout operation

  • External beta payouts are manual, gated, or delayed by default.
  • Live production payout requests and transfer execution can remain disabled unless AgentAds explicitly enables them for a controlled window.
  • US-only Connect onboarding is the current private-beta payout posture. Expansion requires support and finance approval.
  • Minimum payout thresholds, timing, and eligibility may change during beta.

Stripe Connect, tax, and KYC

  • Payouts may require Stripe Connect onboarding, identity verification, tax information, and an eligible payout country.
  • Stripe may require additional information or restrict payouts based on its own rules and account requirements.
  • Developers are responsible for taxes and accurate payout information unless a written agreement says otherwise.

Adjustments and reversals

  • AgentAds may delay, adjust, claw back, or reverse earnings tied to invalid traffic, duplicate credit, chargebacks, refunds, disputes, abuse, account error, or provider reversal.
  • A connected-account bank payout failure is settlement telemetry and does not automatically create a second payment obligation.
  • If reconciliation fails or provider evidence conflicts with AgentAds records, payout support may pause until engineering or finance resolves the issue.

Relationship

Using AgentAds does not by itself make a developer an employee, contractor, partner, franchisee, or agent of AgentAds. Final tax and contractor language should be reviewed by counsel before broader payout rollout.