FAQ & Fraud Ground Rules

FundUrPrompt pays developers a share of ad revenue for sponsored lines shown during AI wait states. This page mirrors the trust surface on the same wait-state marketplace model, with production attribution on Cloudflare.

How do I earn?

Install the Codex CLI shim, approve the install once, and keep coding. When a real wait state is active, the sponsored line becomes a qualified impression only after five seconds of visible time. The product target is a 50% developer revenue share on attributable ad revenue.

Which assistants are supported?

• Codex CLI in an interactive macOS or Linux terminal is the supported earning path.
• The same shim works when Codex is launched from a terminal inside an editor.
• VS Code extensions, Claude Code, and non-interactive output are not current earning surfaces.

What counts as a real impression?

• The ad is visible on screen for at least five seconds during an actual AI wait state.
• The session comes from normal human tool use, not automation.
• The install is signed in, connected, and within platform limits.
• The event is not excluded by fraud review or spacing rules.

When do payouts happen?

Payout transfer is not active yet. Dashboard earnings are based on accepted impressions, but no cash withdrawal should be expected until payout onboarding and payment operations are launched.

Fraud ground rules

• One earning account per person.
• No prompt loops, bots, or scripted impression farming.
• No telemetry replay, spoofing, or event tampering.
• No account networks, payout collusion, or device pooling.
• No circumvention of caps, spacing rules, or review controls.

What do we collect and what do we not collect?

We collect only the telemetry needed to credit earnings, bill advertisers, and limit abuse: install identifiers, event types, timestamps, ad metadata, host versions, and temporary IP-derived abuse signals. We do not collect code contents, prompts, responses, file names, or project structure.