Why the referral route

In 2026, most model vendors and API aggregators put their acquisition budget into referral rewards: an existing user invites a new one, and both sides receive credits (usually as platform credit vouchers or account balance). Compared with launch-day rushes or promo hunting, referrals are repeatable, stackable, and not tied to a countdown, but they have anti-abuse rules, so you must follow the platform-approved path.

This guide is organized as a ladder: each level maps to one reward type, stacked progressively rather than pushed all at once.

Steps

Level 1: Base invite reward (two-sided credit)

  1. In the target platform console, find the Referral / Invite page (common on OpenAI-family products, the Anthropic console, OpenRouter, Together AI, Groq and similar inference/aggregator platforms) and copy your invite link.
  2. Confirm the reward form: is it granted on sign-up, or only after the invitee's first API call / first top-up? The former is low-friction but small; the latter is usually larger.
  3. Invite only real, independent users who will keep using the account. Bulk sign-ups from the same device, payment method or IP range almost always trip risk controls and the credits get clawed back.

Level 2: First top-up linkage reward

Most platforms pay a second round of credits once the invitee completes a first top-up. Key moves:

  • Put the first top-up into your invite pitch, stating the minimum amount and the payout window.
  • As the inviter you usually receive an extra credit too; check the arrival time (commonly 24 hours to 7 days, per the platform's rules page).
  • Record the expiry date of each reward. Referral credits often expire sooner than purchased balance and should be burned first.

Level 3: Activity-tier reward

Some platforms tie referral rewards to the invitee's usage within 30 days, unlocking another tier at a threshold. How to handle it:

  1. Check the tier thresholds in the invite panel (usually measured in call count, token consumption or spend).
  2. Help the invitee make their first API call (provide a minimal runnable snippet) so the account is flagged as active.
  3. Tier rewards usually settle monthly; avoid concentrating several invitees' activity on the same day, which can look like abnormal traffic.

Level 4: Community / channel referral codes

Once personal invite credits cap out, move to channel-type rewards:

  • Developer ambassador programs, Builders projects, and Discord/forum contributor codes usually pay a higher rate than standard invites.
  • Open-source maintainers can request a project-specific referral link and point the docs' "Try it" button at it.
  • Note: channel codes generally require genuine content, not pure advertising; link-spamming disqualifies you.

Level 5: Team / organization referral pool

For teams: an org admin issues invites centrally and pools rewards into the organization account. Requirements:

  • The platform supports Organization / Team accounts with member invitations.
  • Agree in advance on credit ownership and consumption priority so personal and team credits don't blur.

Caveats

  • Compliance first: don't buy invites, don't mass-register via VMs, don't use fake emails. Rules pages typically spell out what counts as an abnormal invite and the clawback terms.
  • Credits are not cashable: referral rewards are almost always in-platform credits — not withdrawable, not portable across platforms.
  • Expiry differences: referral credits often last 30–90 days and are consumed before purchased balance — spend them on experimental calls first.
  • Tax and invoicing: on business accounts, some platforms count referral credits as account balance, affecting invoicing; confirm with finance.
  • No invented numbers: reward amounts change with campaigns; this article gives no fixed figures — check the live invite page in your console.

Where it fits

  • Small teams or labs that need steady experimental credits and whose members would sign up anyway.
  • OSS maintainers who want a "try it now" entry in their docs and some credit back.
  • Community organizers running study groups, converting referral rewards into a shared group pool.

Suggested cadence

Week 1: complete Level 1 (base invites). Weeks 2–3: drive invitees through first top-up and first call to trigger Levels 2–3. Week 4: apply for a channel code or org pool to reach Levels 4–5. At this pace you can typically secure, each quarter, enough credit to cover routine experimentation.