AreaGenesisAlternativeRequirement
IntegrationREST offer API, SDKs, React rendering, MCP server, hosted tracking URLs, signal APIs, and prompt-weaving helpers that preserve exact links and identify referenced offers.Public docs describe REST offer retrieval, MCP signal collection, impression tracking, and woven-offer patterns.Keep `/v1/offers`, `/v1/signals`, hosted tracking, SDK, and MCP examples documented side by side.
SDK coverageNode.js/TypeScript, Python, React, React Native, Flutter, iOS, and Android SDK tracks.Public docs emphasize API-based integration, offer rendering fields, and signal collection rather than broad native SDK claims.Maintain broad SDK coverage and keep the API-direct path simple for teams that do not want prebuilt UI.
MCP and agent workflowDedicated Genesis MCP tools for offer retrieval, signal recording, and copyable agent instructions.Public docs describe an MCP Signal Server for broadcasting preference and intent signals to improve later offers.Keep MCP config copyable and ensure signal capture stays optional, scoped, and privacy-reviewed.
Ad deliveryLabeled text recommendations, action cards, banners, inline renderers, lead forms, prompt-weaving modes, and referenced-offer impression helpers.Public docs describe rich structured offer fields and guidance for separate UI rendering or weaving offers into generated text with exact links and reference-based impression tracking.Return enough metadata for native rendering while enforcing visible sponsored disclosure, exact hosted links, and impression tracking only for rendered references.
Auction and matchingQuality-weighted expected-value auction with trust, relevance, and policy quality inputs.Public docs focus on matching offers from real-time context and learned signals.Publish transparent auction documentation so Genesis is not a black box.
AnalyticsPublisher analytics, advertiser analytics, placement filters, experiment reports, export jobs, and raw-event audit paths.Public docs expose ad requests, impressions, clicks, estimated earnings, signal counts, freshness, time series, geo metrics, and async exports.Keep exports and metric definitions launch-level surfaces rather than afterthoughts.
Privacy and controlsNo third-party cookies, raw PII rejection, publisher-initiated calls, hashed identifiers, optional signals, app-level allow/block controls, and per-request controls.Public docs describe privacy-first signal collection, no cookies, and hashed PII requirements.Keep signal collection optional and make hashed-identifier and persistent category-control rules visible in docs and dashboards.
Revenue modelsCPM, CPC, CPA, affiliate, and lead-gen bids clear one quality-weighted auction and settle through event-derived advertiser ledgers, publisher earnings ledgers, and scheduled payouts with admin hold/release controls. Developer Rewards pays per payable session with duplicate-session, fraud, tax, and payout gates — not a percentage of transaction revenue.Public pricing reviewed 2026-10-14: $0 setup fee, no monthly platform fee, and 5% of agent-transaction revenue on ZeroClick storefront commerce.Keep the 5% figure tied to the zeroclick.ai pricing source and re-check it each review; publish Genesis eCPM or payout case studies only after real demand campaigns run.