Questions, answered honestly.

WaitLayer is a verified attention network for AI coding agents. It shows clearly labeled, developer-relevant sponsor lines during eligible AI-agent wait states in your terminal, and lets you earn from verified impressions without sharing your work.

You earn from verified sponsor impressions delivered during eligible wait states. Each payout traces back to a single impression that cleared visibility, validity, and fraud-review checks. Developers receive 70% of verified media spend allocated to their eligible impressions.

Earnings depend on how often you use AI coding agents, how much eligible wait time you create, sponsor demand, campaign fill rate, and payout availability. WaitLayer is designed to help active users offset part or all of their AI coding-tool costs over time — not to create guaranteed passive income.

No. Source code is never collected. It is blocked in the client before anything leaves your machine.

No. Prompts, AI completions, and terminal output are never collected.

No. Terminal output is on the never-collected list and is blocked before any payload is assembled.

Yes. The Claude Code terminal status line is the first supported surface and is available in beta.

Codex CLI support is in beta. See the roadmap for current status.

tmux status integration is planned, not yet available. We will not claim it as live until it ships.

WaitLayer is terminal-first and uses official integration points rather than patching editor bundles. Editor surfaces are not supported at launch.

You choose a payout rail. Some methods may require identity, tax, sanctions, wallet-risk, or compliance checks. Minimum payout thresholds apply and the first payout may require manual review.

USDC is planned as a payout option. Availability depends on jurisdiction and compliance checks, and is not the brand identity — it is one rail among cash and credits.

Compute-credit and API-credit payouts are planned payout options. Credits may include sponsor-funded bonuses.

Scripted farming, bot loops, click manipulation, multiple-account abuse, telemetry tampering, VM farms, prompting solely to generate ads, and collusion with advertisers. WaitLayer is for real developers doing real work.

Payouts may be held while we review eligibility and fraud signals. Verified, legitimate activity is released; abusive activity may be reversed or withheld.

Yes. WaitLayer is designed to be removable with one command and to restore any settings it modifies.

A local event ledger, inspectable telemetry payloads, and exportable event history are product commitments. The allowlist is enforced in the client — if a field is not on it, it is never assembled into a payload.

We do not claim open source until the client or telemetry schema is actually published. Publishing the telemetry schema is on the roadmap.

AI-native developers running supported coding agents during eligible terminal wait states. Targeting is limited to agent surface, coarse region, and self-declared category.

A sponsor line rendered during an eligible AI-agent wait state for a minimum visible duration.

An impression that passed token validity, minimum visibility, duplication, and fraud-review checks. Only verified impressions are billable as media spend.

Clicks on a sponsor line are recorded as discrete click events and reported alongside impressions, without exposing developer work.

Starter ($750/mo), Growth ($2,500/mo), and Category ($7,500/mo) founding packages, plus custom. Each separates media spend from platform fees.

You can target by agent surface, terminal surface, coarse region, developer self-declared category, and campaign category.

No. WaitLayer never targets based on source code, prompts, completions, files, terminal output, repo names, or dependency files.

Developer-relevant tools with one-line, clearly labeled, non-deceptive creative.

No adult, gambling, weapons, malware, surveillance, or predatory products, and no sketchy crypto offers.

Verified and gross impressions, rejected or held impressions, clicks, CTR, spend, remaining budget, delivery by surface and coarse region, creative comparison, fraud-review status, and rollover credits.

Undelivered verified inventory rolls forward as credit rather than being lost.

Yes. Campaigns can be paused between flights, and remaining verified media value is preserved as rollover.

Agent recommendation beta access is included with Category sponsorship and can be requested in the sponsor form.

A short, fixed allowlist that describes the ad surface, not your work: install ID, agent type, surface type, client version, eligible display duration, sponsor impression ID, click event, coarse region, payout account status, and fraud-review signals.

Source code, prompts, AI completions, terminal output, shell history, file contents, repo and branch names, directory paths, dependency files, transcript contents, and secrets or environment variables.

Fraud reduces payouts for honest developers and damages sponsor trust. Fraud-review signals describe delivery integrity, not the contents of your work.

No. Developer data is not sold as an audience dataset.

No. Repo names, branch names, and repo contents are never collected.

No. Dependency files are on the never-collected list.

Verification and payout events are retained as long as needed to verify delivery, prevent fraud, process payouts, and meet legal obligations, then minimized. See the Privacy Policy for the retention summary.

Yes. Account deletion removes your account and associated identifiers, subject to records we are legally required to retain.