# As a condition of accessing this website, you agree to abide by the following # content signals: # (a) If a Content-Signal = yes, you may collect content for the corresponding # use. # (b) If a Content-Signal = no, you may not collect content for the # corresponding use. # (c) If the website operator does not include a Content-Signal for a # corresponding use, the website operator neither grants nor restricts # permission via Content-Signal with respect to the corresponding use. # The content signals and their meanings are: # search: building a search index and providing search results (e.g., returning # hyperlinks and short excerpts from your website's contents). Search does not # include providing AI-generated search summaries. # ai-input: inputting content into one or more AI models (e.g., retrieval # augmented generation, grounding, or other real-time taking of content for # generative AI search answers). # ai-train: training or fine-tuning AI models. # ANY RESTRICTIONS EXPRESSED VIA CONTENT SIGNALS ARE EXPRESS RESERVATIONS OF # RIGHTS UNDER ARTICLE 4 OF THE EUROPEAN UNION DIRECTIVE 2019/790 ON COPYRIGHT # AND RELATED RIGHTS IN THE DIGITAL SINGLE MARKET. # BEGIN Cloudflare Managed content User-agent: * Content-Signal: search=yes,ai-train=no Allow: / User-agent: Amazonbot Disallow: / User-agent: Applebot-Extended Disallow: / User-agent: Bytespider Disallow: / User-agent: CCBot Disallow: / User-agent: ClaudeBot Disallow: / User-agent: CloudflareBrowserRenderingCrawler Disallow: / User-agent: Google-Extended Disallow: / User-agent: GPTBot Disallow: / User-agent: meta-externalagent Disallow: / # END Cloudflare Managed Content SAI — Sponsored AI Credits
Sponsored AI Credits
Local-first Open ledger Now launching

Your agent is thinking.
Sponsored credits the wait.

SAI puts one quiet sponsor line in your coding agent’s wait state and records sponsor-funded developer earnings in the backend ledger. Your code never leaves the machine.

Install the CLI → earn ≈ +12.96 credits / month while it thinks at 45 min/day of agent wait · launch pricing · not a guarantee
Become a sponsor → no cloud account · 1 credit funds USD 1 of model usage · one command to kill it
wallet 0.000 credits
sai · claude

The market is public

loading /v1/market
funded campaigns live0
top bid / 1,000 cards$20.00
you earn / card+0.012
you earn / click+0.60
price · top bid / 1,000 QP top bid dev share ×0.6 $0.00 / 1k QP

Price history begins when the first sponsor funds the book — currently $0.00 / 1,000 QP, no live demand.

Order book — every campaign, ranked by bid PROJECTED
CampaignStatusBid / 1k cardsYou / cardYou / clickInventory left

Install CLI

npm launcher · platform binary · no source checkout
$npm install -g @sponsoredai/cli
$sai login # local user + key, nothing uploaded
$sai claude # your agent, now with a wallet

The ledger stays honest

earn → hold → settle, backend authoritative
01 · WRAP

Run the same agent command

Start with sai claude instead of claude. SAI opens a real terminal session around your agent and measures idle timing only — not prompts, code, or output.

No agent patches, no forks. Interactive terminals only; CI and headless runs are detected and left alone.

02 · WAIT

Quiet waits become cards

After 10 seconds with no terminal output, SAI can render one sponsor line at the bottom of the terminal. At most one card every 45 seconds — tune it or shut it off.

A spinner that keeps redrawing counts as output. A card earns credits only after it stays visible for at least 5 seconds.

03 · SETTLE

Earnings stay server-side

Qualified paid placements credit the backend developer ledger after sponsor funds are verified. The local wallet is display-only.

Spending works without SAI seeing traffic: the backend provisions a provider key whose spend limit equals your balance, and the gateway calls the provider directly. SAI reads the usage counter, never your prompts.

What does waiting pay?

market bid split, not a guarantee
What is a credit?

One credit pays for one US dollar of AI model usage — prepaid by a sponsor, spent from your terminal.

  • Earned from real campaigns. Sponsors pay per qualified placement through Stripe; 60% of net spend lands in your ledger as credits.
  • Spent without a card. The gateway gets a provider key whose spend limit equals your balance — model calls bill the sponsor’s money, not yours.
  • Never minted from thin air. No funded campaign live means cards pay zero. The ledger only credits what a sponsor already paid for.

Your agent’s idle time

How long does your agent spend thinking, per day? Count the spinners, the test runs, the long diffs. If no paid sponsor campaign is available, the wait pays zero.

45 min / day of agent wait

Normal frequency: a card needs ≥10s of quiet and cards sit ≥45s apart. The market ranks funded campaigns by bid, then pays only qualified five-second placements.

payout / qualified cardPROJECTED+0.012
cards / day36
developer credits / day60% NET+0.432
bonus / qualified click50×+0.60
+12.96 developer credits / month when funded · ≈ USD 12.96 of model usage

Projected at launch pricing while the live market loads from /v1/market.

Beta cap: developer credits are capped at USD 5 per installation per hour — earnings above the cap in a rolling hour are not credited.

1 · EARNED

A sponsor card stays visible ≥5 seconds during a real wait. The payout was printed on the card — that exact amount is yours.

2 · PENDING

The backend ledger holds it while the sponsor’s payment is verified. No sponsor funds, no credit — nothing imaginary gets minted.

3 · AVAILABLE

Spend it on model calls from the same terminal — the gateway bills your balance instead of your card.

Never leaves your machine

the schema is the contract
  • promptsNEVER SENT
  • source codeNEVER SENT
  • file pathsNEVER SENT
  • terminal outputNEVER SENT
  • shell historyNEVER SENT
  • repository URLsNEVER SENT

The runner tracks when output happens, not what it says. An event is eleven boring fields, and anything outside the schema is stripped before it exists. Audit it yourself: sai privacy schema

KILL SWITCH One command hard‑stops every sponsor surface, with a reason on the record: sai config kill-switch on

For sponsors: buy qualified wait-state inventory

Stripe checkout · paid placements

A developer watching an agent think is a sponsored moment with measurable qualified views.

Sponsors create campaigns, pay through Stripe Checkout, and buy blocks of 1,000 qualified five-second placements. After reserved infra cost, 60% of net sponsor spend becomes developer credits and 40% is platform revenue.

  • ✓Qualified impressions only. A card renders after ≥10s of real agent wait, in an interactive terminal, never in CI.
  • ✓No fatigue by design. Cards sit ≥45 seconds apart, with campaign and installation delivery caps — scarcity is the format.
  • ✓Clicks bill 50× the placement rate. You only pay the multiple on real intent — a click-through on an already-qualified card — and the developer earns the same 60% share of it.
  • ✓Developers opt in knowingly, because the card pays them in sponsored credits. Goodwill is the product model.
  • ✓Reporting follows the event schema. Rendered and qualified placements are recorded without prompts, code, logs, or terminal output.
What you buy, exactly
developer’s terminal · live
✦ thinking… 14s
▌ sponsored Your Brand · Ship faster agent workflows · sponsoredai.dev/sponsor ↗ +0.012 AI credits
✦ thinking…

That’s the unit: sponsor name, 3–80 characters of copy, a destination, and the developer payout visible before the card renders.

Fair questions

So… this is adware?
It’s one line of text, in a moment you were staring at a spinner anyway, that pays you in AI credits. It only appears in interactive terminals, never in CI, at most every 45 seconds. You control frequency (sai config set frequency low), and sai config kill-switch on stops every sponsor surface instantly. Adware doesn’t ship a kill switch on the front page.
Can you read my code or prompts?
No, and not as a policy promise — as a mechanism. The runner watches output timing through a PTY, never content. Events are sanitized against a fixed schema where code_uploaded, prompt_uploaded and logs_uploaded are hard-coded false. Run sai privacy schema and read the whole contract.
What is a credit actually worth?
Credits are server-side developer earnings backed by paid sponsor placements. The backend debits funded sponsor campaigns and credits the developer share of net spend; the local wallet is only a display cache. You spend credits on model calls through the gateway: the backend provisions a per-installation upstream key whose spend limit equals your balance, your machine calls the provider directly, and usage is debited from the ledger — SAI reads the key’s usage counter, never your traffic. During Beta, credited earnings are capped at USD 5 per installation per hour to limit abuse.

The spinner is sponsor inventory.
Qualified waits fund AI credits.

Install it from the repo, connect sponsor inventory, and watch qualified placements fund the backend ledger.

Get SAI ↑ Become a sponsor Sign in with Google
∗ ∗ ∗ ∗ ∗ ∗ ∗ ∗ ∗ ∗ ∗ ∗
≈ +12.96 credits/mo while your agent thinks install →