Why Sequence by Timeline Instead of by Platform

Limited-time promotions, festival campaigns and launch perks share one property: they all have windows, and the windows compete with each other. A launch perk on a given platform usually applies only to a first-time activation; a festival bundle often requires the account to be active; a flash sale frequently requires a real call made on the campaign page. If you browse platform by platform, you will miss the launch window on A and lose the festival bundle on B because the account went inactive.

The right move is to build the timeline first, then pick platforms: claim launch perks first (lock slots) → top up with festival campaigns (add volume) → close with flash sales (fill gaps). The three sections below spell out the concrete actions.

Steps

Part 1: Claim launch perks first — lock the "first-activation" benefits

  1. List 3–5 platforms that are launching or about to launch a new model. Judge by whether the site has a "Launch Week", "Early Access" or "Preview" page that explicitly offers trial credit or a discount to early users — not by brand fame.
  2. Register and make a first call inside the launch window. Most launch perks require the account to be created during the campaign and to produce one successful request; registering without calling usually does not count. A single minimal request (one chat completion or one embedding) is enough.
  3. Keep evidence: screenshot the campaign terms, record registration time and first-call time. Disputes over launch perks almost always hinge on "was it activated inside the window", and the evidence is worth more than the credit itself.
  4. Do not burn the credit in this phase. Launch credit usually has a short validity (roughly 7–30 days, subject to terms). Log it in your ledger with an expiry date.

Part 2: Top up with festival campaigns — the "activity-gated" bundles

  1. Check campaign pages a week ahead. Festival campaigns (developer days, anniversaries, year-end sales) usually publish their rules page 3–7 days in advance, including eligibility such as "N calls during the campaign" or "submit one doc feedback".
  2. Finish the activity conditions early. If the bundle requires a call record during the campaign, run a real task on day one — many campaigns are first-come-first-served and close when slots run out.
  3. Prefer stackable bundles. Festival bundles often exclude launch perks (one new-user discount per account). Read the "cannot be combined" clause before claiming.
  4. Treat festival bundles as volume, not quality: they usually carry more credit but tighter limits (model restrictions, rate limits, expiry). Use them for batch jobs, evaluations and data cleaning — work that does not care which model runs it.

Part 3: Close with flash sales — fill structural gaps

  1. Only join a flash sale when you have a defined gap. A flash sale (limited-time discount, multiplier, bonus credit) is you paying for credit. It is worth it only when free credit is fully allocated and one gap remains.
  2. Check stacking rules. Many flash sales explicitly exclude new-user offers. If you have not used your launch perk yet, do not buy.
  3. Use flash sales to cover long-tail models. Your free credit tends to concentrate on flagship models; if a flash sale covers Embedding, speech or multimodal models, fill those gaps first.
  4. Record the effective unit price. Convert the flash sale into "cost per million tokens" in your ledger and use it as the baseline next time you build the timeline.

Part 4: Merge the three parts into one table

Build a four-column table: platform / window start-end / eligibility / expiry. Update it weekly and strike out closed windows. This table beats any "free credit roundup" because it reflects the real state of your own accounts.

Caveats

  • Launch perks mostly apply only to first-time activation. Re-registering under the same entity usually does not work and may trigger risk controls.
  • "First come, first served" on festival campaigns is a hard constraint. The slot counts on the rules page are usually real; one day late can mean nothing left.
  • Limited-time promotions often exclude free credit. Read the "cannot be combined" clause before claiming.
  • Credit expiry is not announced. Most platforms will not remind you; you must track expiry dates yourself.
  • Do not spam calls to meet campaign conditions. Abnormal call patterns can trigger rate limits or account suspension — not worth it.
  • Exact amounts, validity periods and stacking rules vary by platform and campaign; always defer to the campaign page terms. This article deliberately gives no specific numbers.

When to Use This

  • Individual developers: multiple platform accounts, wanting to keep a daily-usable token supply at minimal cost.
  • Small teams: needing temporary volume for a focused build period (e.g., a two-week sprint) without going through procurement.
  • Educators and content creators: producing reviews and tutorials during campaign periods, where festival bundles cover the cost.

Action Checklist

  • [ ] Review launch/preview pages of 3–5 platforms this week
  • [ ] Make one minimal successful call per platform and screenshot it
  • [ ] Log festival campaign rules pages one week ahead
  • [ ] Run one real task on the first day of each campaign
  • [ ] Confirm no unused launch perk before joining a flash sale
  • [ ] Mark every credit's expiry date in the ledger