Captcha.ad is building a way for verification providers and publishers to add sponsored advertising to existing CAPTCHA experiences, while keeping the provider’s security decision in control.
Corporate cards. Expenses. Bill payments.
Sponsored CAPTCHA places a brand message inside an interaction that accompanies a human-verification flow. The advertiser supplies creative; the verification provider remains responsible for deciding whether a visitor can continue.
Captcha.ad is developing this advertising layer for existing verification networks. The model connects advertiser demand with eligible publisher placements and shares revenue from qualifying interactions. Explore the proposed integration or model the potential economics.
Current release: an interactive product concept. The demo, dashboard figures, and revenue calculator are simulations. Live ad delivery, partner integrations, and self-service registration are not available yet. The Ramp creative is an illustrative example, not an announced sponsorship.
Keep control of risk assessment, verification, and fallback behavior. The proposed integration adds sponsor selection and interaction reporting alongside your existing service.
See the provider integration →Offer eligible sponsored experiences on your site through a participating verification provider. Planned controls include placement eligibility, ad categories, and a provider-only fallback.
Explore publisher economics →The planned advertiser workspace supports campaigns, creative uploads, and prepaid budgets. Campaigns will require review and available inventory before delivery can begin.
Preview the advertising format →CaptchAD is not trying to rebuild bot defense from scratch. We give verification providers a commercial layer they can distribute across their installed base.
Your existing risk score, device signals, challenge policy, token validation, and anti-abuse systems stay in control.
CaptchAD supplies approved static creative and simple interaction recipes that fit inside your existing widget boundary.
Advertisers buy verified attention. CaptchAD handles demand and measurement. Provider partners participate in the media revenue.
If CaptchAD is unavailable, blocked, has no eligible sponsor, or is disabled by the publisher, the provider simply renders its normal verification experience.
Privacy-minimized placement context is sent to CaptchAD.
Approved creative + challenge recipe are returned.
A 1–3 second branded action creates an attention signal.
The incumbent provider performs its normal security decision.
Only provider-verified completions become billable attention.
Creative is static and rendered inside the controlled verification surface.
Advertisers never touch publisher forms, cookies, credentials, or page data.
Ad delivery failure can never break login, signup, checkout, or access.
Users can always choose a provider-only accessible verification route.
Model what a provider network could generate from a sponsored format. These are editable planning assumptions, not a revenue promise.
The first product surface gives providers, publishers, and advertisers a shared source of truth without mixing their underlying data.
The MVP is designed around an explicit rule: a sponsored interaction is a media event and an optional behavioral signal—not a replacement for the provider’s security decision.
Ad serving can fail open into a neutral provider challenge. Authentication never depends on sponsor availability.
Static reviewed assets only. No advertiser scripts, DOM access, browser storage, or page-level data collection.
Contextual eligibility can work with publisher, coarse region, device class, category, and placement—not cross-site identity.
The sponsored visual format is never the only path. The underlying provider can offer its accessible method directly.
The planned production integration uses short-lived signed challenges and duplicate-event protection. This public preview is a browser simulation.
Provider verification plus media-side IVT filtering protects both advertisers and network settlement.
The ideal integration is server-to-server between CaptchAD and the verification provider, with a lightweight creative payload rendered inside the provider’s existing controlled UI.
// 1. Your provider decides a visual verification is needed.
const sponsor = await captchad.decision({
placement: "signup",
publisherId: "pub_456",
country: "US",
allowedCategories: ["software", "consumer"]
})
// 2. Render sponsor inside your existing widget boundary.
providerWidget.renderSponsoredFormat(sponsor)
// 3. Your normal verification remains authoritative.
const verified = await provider.verify(token)
if (verified) {
await captchad.recordVerifiedAttention(sponsor.id)
}No. Captcha.ad is designed as an advertising layer alongside an existing verification provider. The provider’s security decision remains authoritative. The public demo simulates verification and must not be used to protect a real login, form, or checkout.
The proposed model shares revenue from qualifying sponsored interactions across participating partners. Actual earnings would depend on available advertiser demand, eligible traffic, completion rates, pricing, and the agreed revenue share. The calculator shows assumptions, not guaranteed income.
The proposed billing model is based on qualifying, provider-verified sponsor interactions. Advertisers would set a campaign budget and submit creative for review. Final pricing and delivery terms are not available in this public preview, and the demo does not charge anyone.
The intended integration falls back to the existing provider’s normal verification experience when an ad is unavailable, blocked, or ineligible. Access to a website should not depend on advertiser demand.
The planned integration connects Captcha.ad with the verification provider for sponsor selection and event reporting. Publishers would enable supported placements through that provider. The code sample on this page illustrates the architecture; it is not a released SDK.
The design includes a provider-only alternative so people do not have to complete the visual ad interaction. Production accessibility must be verified with each provider integration. The demo’s slider also supports keyboard input.
Public registration and live campaigns are not open yet. This release lets providers, publishers, and advertisers explore the format and proposed economics. The advertiser app and payment integration are being prepared for a later release.
We’re looking for security providers, high-volume publishers, and brands willing to test verified-attention formats with conversion and security guardrails.
We’re preparing self-service accounts for advertisers and publishers, plus onboarding for verification partners. Explore the interactive demo while we get ready.
Try the demo