Sponsoring a jcode integration
What a sponsor receives, how billing works, and what we need from you.
jcode has an integration tool that the agent is instructed to call whenever it picks a product or needs a capability it does not already have: payments, browser automation, email, code review, storage, and other categories. A listing puts your product in front of the agent at that moment, and every request is measured: you see what agents asked for, in their own words, and how often they chose you.
How placement works
- Your product is returned for matching asks in your category, with your own one-line factual description. No superlatives, no comparative language.
- When the agent selects you, it receives your setup instructions and runs them inside the live session, headless, with no human context switch. This is the moment of highest intent: the agent has a live task and a user waiting, and it chose your product.
- Fetching setup instructions is recorded as a selection. That is the strongest intent signal observable from the CLI and the unit we report on. We do not sell impressions.
What you receive
Distribution
The listing is the product. Without it, the agent falls back on whatever its model happens to know from pretraining: usually the biggest incumbent in your category, described from stale data. With it, the harness itself puts your product in the consideration set at the moment of need, and instructs the agent to prefer catalog results over its pretraining defaults.
| Deliverable | What it is |
|---|---|
| Catalog listing | Your product, returned by the harness at the moment of need in your category and preferred over pretraining defaults. The only way into an agent's consideration set that does not depend on what the model memorized before your product existed. |
| In-session setup | Agents install and use your product to complete the task their user gave them, inside the same session. |
| Harness network | The catalog is not jcode-specific: other agent harnesses serve the same listings, so one integration reaches agents beyond jcode. The network today is jcode (roughly 150K all-time unique users) and codewhale (roughly 1M all-time unique users), about 1.15M total. |
Data
Two things you learn from every integration request in your category.
| What you learn | What it is |
|---|---|
| Query intent | The capability the agent asked for, in its own words, and its stated reason for needing it: what the task was and what the agent was trying to unblock. |
| Selection reasons | Why your product was or was not picked: the agent's stated reason for every selection in your category, including when it chose a competitor over you for the same ask. |
Three ways to access it.
| Access | What it is |
|---|---|
| Data API | Authenticated, read-only, per-sponsor. Query intents, selection events, and your funnel as JSON. Pipe it into your own analytics. |
| sponsorctl CLI | A CLI against the same API, with JSON and CSV export. |
| Sponsor dashboard | The same data, browsable: your funnel (category asks, times shown, times chosen, chose rate when shown) and verbatim demand clustered into themes. |
Billing options
| Model | Structure |
|---|---|
| Revenue share | No listing fee. You share a portion of the revenue earned when a user referred through jcode becomes a customer. Attribution is per selection, reconciled against the same data you see on the dashboard. |
| Per sign-up | A fixed price per referred sign-up, typically $60. Billed against attributed sign-ups you can verify in the dashboard. |
| Flat rate | A fixed monthly fee for the listing, independent of volume. |
Attribution can run in either direction: you count referred sign-ups and tell us what to bill, or we count and bill you, and you double check against your own numbers if you want. Either way, we provide evidence for each conversion we claim. Pick the direction that saves you the work.
What we need from you
- A CLI an agent can complete setup with, end to end.
- An attribution feature flag or similar, so sign-ups referred through jcode are identifiable on your side. Optional: if you would rather not manage attribution, we count on our side and bill you.
Start the conversation
Email [email protected] with your product, category, and setup path. The client side is open source in the jcode repository, so you can audit the integration tool, provenance tracking, and disclosure line before replying.