Qualified delivery
Earnings are tied to eligible measured impressions rather than raw installation counts.
Loading AdFrolic
Preparing your workspace securely…
For developers
AdFrolic keeps the host integration narrow. It authenticates the installation, requests an eligible sponsored placement, renders approved structured creative and reports the impression lifecycle. Campaign selection, moderation, budgets, fraud controls and accounting stay server-side.
Interactive product example
Switch the host and placement state to see how an implemented AdFrolic surface behaves. The creative below is explicitly an interface example, not a live advertiser or performance claim.
1 import { serve } from "./server";
2
3 serve({ port: 3000 });
Review release risk before deployment
Ad request can include
Installation identifier, placement, client and version, protocol version, plus supported coarse context such as language, country or operating system.
Ad request does not include
Source code, file contents, prompts, AI conversation contents, clipboard contents or terminal output.
Integration architecture
The host integration is not an advertising decision engine. Its job is to preserve the host experience while participating in a controlled request and measurement flow.
Link the installation to a developer account through the supported device-authorisation flow.
Ask for a specific implemented placement with the narrow context permitted by the ad request schema.
Display approved structured creative inside the reserved host surface, with a clear sponsored label.
Report the impression lifecycle so qualified delivery can be accounted for on the backend.
Platforms
Data boundary
Source code, file contents, prompts, AI conversation contents, clipboard contents and terminal output are not part of the advertising request contract.
Review trust and securityEarnings and control
Earnings are tied to eligible measured impressions rather than raw installation counts.
Developer accounts show recorded earnings, payout status and connected installation information.
Stripe Connect onboarding is separate from access to the developer workspace and gates payout readiness rather than portal access.
Supported clients are designed so ad-serving failure does not block normal editor or CLI use.
VS Code and Claude Code are implemented in the current repository. JetBrains and ChatGPT are planned and are labelled as such throughout the public site.
An ad request is not automatically a billable impression. The integration reports the sponsored placement lifecycle and the backend applies qualification rules before advertiser spend and developer earnings are recorded.
No. Source code, file contents, prompts, AI conversation contents, clipboard contents and terminal output are outside the advertising request contract.
The developer dashboard shows earnings and payout status for the developer account. AdFrolic does not publish a generic earnings promise because demand, placement and qualified delivery vary.
No blanket guarantee is made. Platform and marketplace rules can change, and developers remain responsible for the obligations that apply to their own extension, plugin or integration.
Start with an implemented host