the network
Start with moments developers already watch.
Generic APIs, SDKs, and stars are not the surface. The product needs to own a recurring moment where the user is present and waiting for work to finish.
- publishers
- Developer tools define the eligible states, placement, categories, frequency, and kill switch. They receive 50% of billable impression revenue on their surface.
- advertisers
- Commercial developer products can appear when their product is genuinely relevant. The network is early, so fit comes before budget or self-serve campaign setup.
- individual users
- Open-source integrations for Claude Code, OpenCode, Hermes, and the terminal prove the format and let individual installs share in billable revenue.
for publishers
Turn attention you already earned into a controlled distribution surface.
The sponsor line belongs to the product surface, not the model response. It is one fixed, clearly marked unit that the publisher can style, limit, or remove.
- surface fit
- Agent runs, tests, reviews, deploys, evaluations, progress states, and handoffs qualify when users actually watch them.
- publisher control
- Choose eligible moments, allowed categories, frequency, and placement. Turn the integration off without changing the rest of your product.
- privacy boundary
- Keep sponsor content outside prompts, tool results, model output, and customer data. Send only the minimum pseudonymous metadata needed to serve and account for a line.
- revenue share
- Publishers receive 50% of billable impression revenue. Demand and fill can vary, so revenue is never presented as guaranteed.
for advertisers
Show up at the exact developer moment, not around it.
ADtention is building an early network of product-owned developer moments. We are looking for commercial devtools that can name a specific task, run, or handoff where their product would be useful.
- format
- One concise sponsor line, clearly labeled and reviewed before it can serve. No banner, popup, third-party pixel, or content inside the model response.
- context
- Target broad work categories inferred locally. Prompts, code, files, and direct user identity are not sent for targeting.
- current proof
- ADtention's integrations have 50+ daily active users across Claude Code, OpenCode, Hermes, and Terminal. Wider publisher supply and paid advertiser demand are still being validated.
- measurement
- Billable impressions are the pricing unit. Clicks can be reported as engagement, but they are not the billing unit.
the boundary
Context without sending the work.
sent when needed:
- a broad category such as infra
- a pseudonymous install or publisher ID
- client, surface, and version labels
- delivery and engagement metadata
not sent for targeting:
- source code or files
- prompts or conversations
- tool results or model output
- direct account, email, or chat identity
The integrations and SDK are open source. Inspect the payloads and placement logic. view source
Run by Julian and Len at codecoast labs GmbH in Switzerland. Every advertiser passes their personal review before it can enter the network. Who is behind this
individual integrations
Try the format inside a tool you already use.
These integrations are the first live surfaces; more are planned. Pick a tool to inspect the placement and installation path.
Pick your tool to get the install command
Illustrative placement preview. Revenue depends on billable impressions and available demand. Serving uses pseudonymous delivery metadata, not prompts, code, or files.
/plugin marketplace add adtention-ai/claude /plugin install adtention@adtention
Run each line on its own inside Claude Code: paste the first command, press enter, then paste the second.
FAQ
ADtention is a developer distribution and monetization network for product-owned moments people already watch, such as agent runs, tests, reviews, deploys, evaluations, progress states, and handoffs.
A product needs to own a recurring human-watched surface. A generic API, SDK, CLI, MCP server, or GitHub audience is not enough by itself. The useful question is: what state does the user already watch while the product works?
The publisher chooses an eligible wait, progress, or result-handoff surface. The sponsor is one clearly labeled line outside prompts, tool results, model output, code, and customer data.
The serving request can include a broad category, a pseudonymous install or publisher ID, client and surface labels, and delivery metadata. It does not send prompts, code, files, tool results, model output, or direct account identity for targeting.
The billing unit is a billable impression. Clicks can be recorded as engagement, but they are not the billing unit. Campaign availability, fill, and results are not guaranteed.
Publishers receive 50% of billable impression revenue served on their surface. Earnings depend on eligible activity and available demand. Cash-out requires a linked account and payout method in the ADtention dashboard.