RuntimeAds is an AI Attention Network: it turns idle AI-agent waiting states inside your editor into a sponsor surface, and shares the resulting revenue with the builders who see those messages. The answers below cover earning, payouts, fraud rules, and what we do (and never do) with your data. For the full legal text see our Terms of Service and Privacy Policy.

How do I earn?

Install the extension and sign in with Google. While your AI assistant is working, the “thinking…” state is replaced by a short sponsored line on supported surfaces. You accrue credit for verified visibility — currently up to a 50% share of the net ad revenue from your verified impressions. No extra actions are required; just keep coding as usual.

What counts as a verified impression?

An impression is eligible for earnings only when our server-side measurement confirms:

the ad actually rendered and stayed visible on a billable surface for a minimum dwell time during active coding;
the underlying request was genuinely human-initiated, not automated or scripted;
the extension is properly installed and signed in;
activity is within the applicable spacing rules and hourly/daily caps; and
the event is not excluded by the fraud system.

Some surfaces are impression-only and never billable (for example the plain CLI spinner verb and banner text). Exact thresholds, spacing rules, and caps are not published, to keep them robust against gaming.

When and how do I get paid?

Verified impressions accrue to your balance. Payouts are processed in batches — the next payout date is always shown on your dashboard. Before accrued earnings become payable they must clear:

a minimum payout balance (currently $10.00 USD);
a cooling period (currently 7 days) after the earnings accrue; and
identity verification, handled by our payment provider when you claim.

You request a payout from your dashboard with your full legal name. When a batch is sent, our payment provider (Wise) emails you a secure link to add your bank details and receive the funds; the transfer fee is deducted from the payout.

Balances shown in the dashboard are estimates until reconciliation. Payouts may be held while activity is under fraud review, and amounts tied to fraud, error, or chargeback may be withheld or reversed.

Which regions can receive payouts?

Payouts run through our payment provider, which doesn’t operate in every country. A few regions aren’t supported yet — if you sign up from one, we’ll let you know, and we can’t create a developer account or process payouts there until we add a provider that covers your region. If your region becomes supported later, your dashboard will reflect it.

What are the fraud ground rules?

To keep earnings fair, the following are prohibited:

operating more than one account per person or entity;
automated or scripted clicking, prompting, or impression generation;
account pooling or coordinated farming schemes;
tampering with, reverse engineering, or circumventing the extension’s integrity checks or telemetry; and
evading limits or caps through network rotation or device switching.

How does fraud detection work?

Automated systems and human reviewers monitor activity patterns in both directions — detecting farms (many accounts behind one network) and rotation (one account across many networks). The exact signals and thresholds stay undisclosed. Builders coding normally will not trip the detection.

What happens if my account is flagged?

A blocked account stops earning immediately, and credit accrued from the abusive activity is voided; the extension surfaces a blocked-account indicator. Fraudulent earnings that were already paid out may be recovered. Established accounts in particular are reviewed by a person before any action sticks — if you believe a flag is a mistake, contact us (below) for human review.

What do you collect, and never collect?

We collect operational signals only: your Google account email and a builder/advertiser ID, a random install ID, the IP-derived country (and, for the extension, your timezone) at signup and install for fraud review, operational telemetry, attention-signal metadata, render/impression/click telemetry, and the campaign content advertisers submit.

We never collect your prompts, AI responses, terminal output, source code, file contents or paths, repository or branch names, environment variables, secrets, or clipboard. Hook payloads are stripped to metadata on your machine before anything is sent. The full breakdown is in our Privacy Policy.

I'm an advertiser: how does billing work?

You fund your wallet through secure checkout, and campaign spend is drawn from your funded balance. Because we aggressively exclude fraudulent traffic, you are billed for delivery to real, verified humans. Credits are issued for undelivered or fraud-tainted impressions.

Appeals & contact

For appeals, support, or anything else, email [email protected] or reach us on X (@devanujhere). To report a bug or request a feature, open an issue on GitHub.

Frequently Asked Questions