Coding assistants

Revenue that stays out of the way.

Show useful developer-tool offers after real decisions: dependencies, cloud setup, observability, security, compliance, or API choices.

Request IDE beta access

Offer call: Bounded; timeout and no-fill fallback
Disclosure: Required; every sponsored response
Auction: Quality-weighted; publisher-weighted ranking
Integration: 1 endpoint; REST, SDK, MCP, React

Dependency decisions

Keep recommendations tied to real coding work with placement IDs and category controls.

Cloud setup

Keep recommendations tied to real coding work with placement IDs and category controls.

Security reviews

Keep recommendations tied to real coding work with placement IDs and category controls.

Developer-specific placements

Developer recommendations, placed with care.

Use Genesis when a developer is actively choosing a product, library, service, or workflow.

Always preserve the Sponsored label, respect category controls, and fall back to the normal coding answer on no fill. Do not send source code, prompts, completions, filenames, raw paths, commands, terminal output, or transcripts.

await genesis.requestOffers({
  placement: {
    placementId: "ide_extension_selection",
    appId: "vscode_extension",
    agentType: "ide_extension",
    surface: "ide"
  },
  context: {
    userMessage: "Developer is comparing approved observability options.",
    categories: ["developer_tools"]
  }
});

Developer-side rewards

Rewards are separate from publisher monetization.

Publishers use Genesis APIs for their products. Developers can opt in separately to Genesis Rewards for quiet wait-state moments in their own tools.

Rewards stay off until opt-in, never collect code or prompts, and keep credits pending until review is complete.

Genesis Rewards

Opt-in

Wait-state rewards for CLI and VS Code

Built for explicit wait states, adapter controls, and duplicate session review.