Your CLI has traffic. Now it has sponsors.

TipCLI helps open-source maintainers turn human-visible software surfaces into reviewed sponsor inventory without terminal logs, prompt injection, cookies, or fake payout balances.

Your CLI, agent, or MCP server has an audience. TipCLI turns that attention into Stripe-backed campaigns and verified delivery.

Add your project Create paid campaign

tipcli sponsor previewhuman-visible

Add the sponsor surface where developer attention already is.

The integration stays intentionally small: identify your approved surface, request a reviewed card, and let the tool continue when there is no match.

import { showSponsorCard } from "@tipcli/sdk";

await showSponsorCard({
  publisherKey: process.env.TIPCLI_PUBLISHER_KEY,
  surface: "cli-run-summary",
  category: "developer-tools",
});

Money loop

Sponsors pay with Stripe. Maintainers get paid after proof.

The Payout policy requires verified delivery before balances become payable, so setup alone never creates fake revenue.

Four gates before money becomes real.

Add one visible surface

Fund a campaign

Pass review

Get paid after proof

No fake payout balances

No LLM context injection

No MCP tool-response injection

Starter

Controlled launch package for one reviewed sponsor campaign.

$50

Marketplace fit

Maintainers bring trusted surfaces. Sponsors bring useful offers.

TipCLI keeps both sides legible: maintainers approve where cards can appear, while sponsors get reviewed developer workflow placement instead of noisy ad inventory.

For maintainers

Add one labeled sponsor card to a workflow people already run. TipCLI handles advertiser payment, manual review, delivery records, and payout readiness.

CLI output, agent summaries, setup pages, and local dashboards
Fast failure path when no sponsor is available
No source-code access, cookies, fingerprints, or terminal logs

For advertisers

Reach developers inside useful open-source software without buying borrowed logos or guessing where the message appears.

Reviewed destination and copy before delivery starts
Category fit across developer-tool surfaces
Registry listing and policy boundaries for launch trust

Trust flow

Review first. Serve carefully. Verify without surveillance.

The launch path is deliberately narrow so TipCLI can grow trust before it grows inventory.

Campaigns are checked before they serve.

TipCLI reviews destination quality, sponsor claims, category fit, and the exact surface where the card can appear.

Manual approval

No borrowed logos

No instant placement

Launch path

Add one software surface, or apply to sponsor one.

Add your project Create paid campaign