The terminal blips network

Get paid for using Claude Code, Codex, Grok, Copilot & Antigravity.

OpenCrater renders sponsored Blips inside AI coding CLIs and pays maintainers for every impression and click, while developers earn AI compute tokens they can spend with Claude, Codex, and Grok — like AdSense for the terminal, with an opt-out developers actually use.

We never read your environment, your code, your files, or your secrets. The SDK sends only an anonymous id and a few coarse tags like lang:python — and advertisers only ever see anonymized aggregates. Read what we collect →

yourtool — ✳ Claude Code — node — 80×24

~/projects/yourtool

yourtool — OpenAI Codex — 80×24

~/projects/yourtool

yourtool — 🦞 OpenClaw — 80×24

~/projects/yourtool

yourtool — Antigravity — 80×24

~/projects/yourtool

yourtool — Grok — 80×24

~/projects/yourtool

The terminal is the last honest sponsor slot. Claim yours.

maintainers

Earn from your tool

Register your CLI, MCP server, or agent and get paid for every impression and click — paid out in USDC.

register a package →

advertisers

Reach developers in-terminal

Run Blips inside Claude Code, Codex & CLIs. Pay per click plus a small per-impression fee, fraud-gated, precisely targeted.

advertise with us →

for maintainers

Earn from the tools you already shipped

  • Earn from impressions and clicks — in USDC. Clicks are the headline; impressions add a small per-view earning on top. It settles on a double-entry ledger, clears after a 48-hour fraud window, and withdraws to your own wallet (min $25).
  • Five-minute setup. Register the package, drop in the SDK or install the Claude Code hook. Done.
  • Never breaks your tool. Fail-silent SDK, ≤500ms hard timeout, zero dependencies, suppressed in CI.
  • Fallback that funds you. No campaign fills? Your GitHub Sponsors card renders instead.

for advertisers

Reach developers where they actually work

  • The terminal, not a feed. Your message renders inside real engineering sessions — Claude Code, Codex, CLIs.
  • Pay per click plus a small per-impression fee. Clicks are the headline price — signed single-use tokens, fraud-gated before a cent moves — with a small flat fee per impression.
  • Precise targeting. Package type, category, language, placement, country — down to US states.
  • Developer-grade taste. Plain-text cards. No tracking pixels, no popups, no autoplay anything.

for developers · new

Hit your weekly limit? Keep coding on compute you earned.

The blips you see while coding aren't only for maintainers — they top up your own compute wallet. Earn across every supported CLI — Claude Code, Codex, Antigravity, Copilot CLI — and when you run out of your weekly plan, switch to OpenCrater compute and finish the session. Attention in, compute out — no card, no cash.

1 · earn

See a card, bank the compute

Install once and keep coding. The Blips that appear at natural pauses credit your wallet — refreshed weekly from what you see.

npm i -g opencrater
opencrater login

2 · spend

Run your agent on it

One command points Claude Code or Codex at your earned compute — nothing on disk is touched. Args pass through, so you resume the exact session your limit cut off.

opencrater claude -c
opencrater codex -c

cards that guide you through it

Limit hit

When your plan taps out and you have compute, a card hands you the one command to continue.

Live usage

While spending, a HUD shows the % of your weekly compute left — on its own cadence, never spammy.

Backup ready

A quiet heads-up that you have compute waiting, so the wall is never a surprise.

Topped out

Out of compute? It shows when your plan limit resets and nudges you to earn more.

how it works

Four commands between your tool and its first payout.

Nothing here touches your build. You keep shipping the tool you already maintain — the terminal it runs in starts paying rent.

  1. step 01

    Claim your package

    Sign in with GitHub, point us at the CLI, MCP server, or agent you already ship. Thirty seconds, start to finish.

    $ open opencrater.to

  2. step 02

    Pocket your key

    One ock_ key, stored hashed on our side. Rotate it on a bad day, revoke it on a worse one.

    $ ock_live_4f2a…

  3. step 03

    Paste the hook

    One dependency — or zero code at all: drop the hook into settings and walk away. It can never break your tool.

    $ npm i opencrater

  4. step 04

    Get paid for impressions and clicks

    Cards appear at natural pauses, never mid-stream. Each click clears a 48-hour fraud window, then it’s your money.

    $ +$509.22 · settled

the deal with end users

Ads in a terminal only work if leaving is effortless. So we made opting out a one-liner.

OPENCRATER_DISABLE=1

One env var kills every card, everywhere, forever.

npx opencrater off

Persistent per-machine opt-out, no env management.

Auto-suppressed

Never renders in CI, non-TTY pipes, or scripts. Honors NO_COLOR.

We never collect prompts, code, or credentials — see the full policy.