Repository README
readme_badgeGenesis Reward Badge
A small sponsored badge in an approved public README.
SponsoredTraceWorksdebug agent workflows faster
inventory: inv_repo_badge_8f1Genesis Rewards
Your agent waits.Genesis can make it count.
Genesis Rewards turns approved CLI and IDE wait states, plus reviewed public developer surfaces, into opt-in inventory. Sponsor moments are labeled, separate from output, and never need code, prompts, or terminal text.
Actual surface
The reward moment is one disclosed line.
In CLI and VS Code, Genesis can replace an approved wait-state spinner or status line with a sponsored line. It is visibly labeled, easy to ignore, and separate from agent output.
The same inventory model extends to reviewed public developer surfaces: Genesis Reward Badges, package README slots, docs, examples, changelogs, templates, and MCP listings. Every placement is approved before serving and tracked by opaque inventory IDs.
Placement previewnpx @genesis/rewards init
Stock agent wait
Planning...
With Genesis
SponsoredAtlasDBview
claude - ~/app
> refactor billing tests to use the new client
* Reading fixtures and planning the patch.
Read client.ts (142 lines)
Updated payments/service.ts
SponsoredAtlasDB - agent test databasespending review
Approved inventory units
One surface model, multiple placements.
CLI wait
agent.statusline.waitVS Code
agent.panel.waitReward Badge
public.badge.repoDocs slot
public.docs.blockPublic inventory
Reward Badges, README slots, docs blocks, and listings.
Genesis Rewards can extend beyond wait states when the surface is public, reviewed, and represented by an approved inventory unit.
Public placement previewapproved inventory units
README.md
# atlas-paymentspublic repository
Payment workflow helpers for agent-built SaaS applications. Includes examples, fixtures, and typed clients.
SponsoredAtlasDB for test databuild passingtyped
01
[![Sponsored by Genesis Rewards] (/v1/developer-rewards/inventory/inv_repo_badge_8f1/badge.svg)](...)Package page
package_readmePackage README slot
A disclosed line or badge on npm, PyPI, crates.io, or similar pages.
SponsoredTraceWorksdebug agent workflows faster
inventory: inv_pkg_readme_2a7Docs page
docs_pageDocs sponsorship slot
A compact docs block placed only on reviewed developer documentation.
SponsoredTraceWorksdebug agent workflows faster
inventory: inv_docs_slot_42MCP listing
mcp_listingListing inventory
A sponsored line for approved examples, templates, and MCP listings.
SponsoredTraceWorksdebug agent workflows faster
inventory: inv_mcp_list_19Built for trust
Private by design. Fair by default.
Rewards only work if developers trust the system. Genesis keeps the surface small, visible, and separate from the work.
Your work stays yours
Genesis Rewards never needs source code, prompts, completions, filenames, raw paths, commands, terminal output, transcripts, credentials, or private files.
Quiet by design
A reward moment can appear only in approved wait states or approved public developer inventory. It stays separate from the work.
Inventory stays explicit
Genesis Reward Badges, package README slots, docs pages, examples, and MCP listings use reviewed inventory units before any serving.
Fair from the start
Multiple windows, panes, wrappers, and extension hosts are grouped by default.
Clear before cash
Credits stay pending until review, tax setup, and payout checks are complete.
How it pays
Payout model
Per payable session, not a revenue share.
Some AI ad networks monetize a percentage of transaction revenue — ZeroClick publicly lists 5% of agent-transaction revenue on its storefront commerce (source: zeroclick.ai, reviewed 2026-10-14). Genesis Rewards instead pays developers for each payable session: one payable stream per session, grouped duplicates, fraud review, tax setup, and payout availability all gate the amount. Genesis has not yet published eCPM or payout case studies; those follow real demand campaigns, and the full ZeroClick comparison keeps every claim source-linked.
Credits
See progress before payout.
Genesis shows estimated rewards while activity is reviewed. Amounts become payable only after eligibility, duplicate-session checks, fraud review, tax setup, and payout availability clear.
Where it works
CLI first. IDE ready. Public inventory next.
Genesis starts with terminal-first workflows and a VS Code extension path, with adapters for Codex, Claude Code, OpenCode, and generic CLI sessions. Public placements use the same approved inventory-unit model for Reward Badges, package README slots, docs, changelogs, examples, CLI help, templates, and MCP listings.
Beta access
Start small. Keep control.
Genesis Rewards is opening through a private beta. Early users help tune the experience across editors, shells, agent tools, and public developer inventory.
You stay in control from the first run: disabled by default, opt-in only, easy to pause, and built with a kill switch.
One rule
No code. No prompts. No hidden capture.
Genesis looks for approved reward moments. It does not need to see what you typed, what the agent answered, or your files.
Learn more
Everything important, in plain language.
Read how setup, privacy, review, feedback, and rewards work before you join.
Developer guide
Practical details for installing, testing, and understanding Genesis Rewards.
Open docDeveloper inventory
Practical details for installing, testing, and understanding Genesis Rewards.
Open docEnvironment onboarding
Practical details for installing, testing, and understanding Genesis Rewards.
Open docFeedback channel
Practical details for installing, testing, and understanding Genesis Rewards.
Open docPrivate alpha plan
Practical details for installing, testing, and understanding Genesis Rewards.
Open docPrivacy rules
Practical details for installing, testing, and understanding Genesis Rewards.
Open docFraud policy
Practical details for installing, testing, and understanding Genesis Rewards.
Open docAdvertiser policy
Practical details for installing, testing, and understanding Genesis Rewards.
Open docFrequently asked
Common launch questions.
Are rewards guaranteed?
No. Rewards depend on eligible moments, reconciliation, duplicate-session controls, fraud review, tax setup, payout setup, and program availability.
Does Genesis read my code or prompts?
No. Genesis Rewards is designed not to collect source code, prompts, AI responses, chat history, filenames, raw paths, terminal command contents, terminal output, or transcripts.
Can duplicate windows or panes multiply earnings?
No. Multiple windows, panes, wrappers, or extension hosts are grouped by default. Duplicate sessions remain visible for review, but they should not create extra payable streams.
Can README files or docs become inventory?
Yes, only after approval. Genesis Rewards supports reviewed public developer inventory such as Genesis Reward Badges, package README slots, docs pages, changelog lines, examples, templates, and MCP listings through opaque inventory IDs.