Fix a stubborn bug.
A failing case, your patch and a follow-up test keep the problem and result together.
For open-source buildersEarly access
Build great software.Make the work count twice.
The fix. The tests. The path to a working result. Your everyday dev work holds useful evidence for better AI.
Keep your CLI and provider. We’re building OptinRouter to capture what you permit, clean it up, and help you sell a useful dataset or get lower inference costs through a program you choose.
Your toolsYour chosen projectsYour permission
Good work. More possibilities.
From your next pull requestto a reviewable work record.
THE WORK BECOMES THE RECORD.
Requests, changes and outcomes stay linked. OptinRouter prepares the work you permit for your review, with its origin and permissions attached.
01 / Real work, useful evidenceSmall fixes.
Small fixes.
Rich evidence.
Open-source work often has a visible trail: diffs, tests, reviews and releases. Put that trail together, and a small change can tell a much more useful story.
The work you choose to shareExample workflow
A project you choose
your-project / cli
src/paths.tsdiff
paths.test.tschecks
The work behind the change
The patch
projectDiff + permitted context
Tools & tests
hooksObserved commands and results
Review & outcome
evidenceWhat changed, with its source
Organized for reviewA useful
work record.
work record.
contextchangesoutcomessources
Sale permission is a separate step.
Ship a careful migration.
Bring the before-and-after diff, tool results and review notes into one useful work record.
Make a project easier to use.
Keep the example, feedback and checks that help explain whether the new instructions work.
02 / Choose what works for youTwo ways to get more
Two ways to get more
from the work.
Prepare your work and decide whether to sell it later. Or choose an approved data-for-discount offer before you run.
01 / Prepare now, sell later
Keep your setup.
Open a new possibility.
Capture permitted work from a supported workflow and prepare a reviewable dataset. Then choose whether to sell directly or ask OptinRouter to help broker an agreed deal.
- Keep using your provider account
- Prepare before agreeing to a sale
- Choose direct sale or optional brokerage
PrepareReviewYou decide
Explore the capture-only path02 / Agree first, benefit at use
Know the deal.
Then hit run.
Choose an approved offer: share qualifying work in exchange for a lower inference price. You see the terms and price before you run, and an approved budget backs the discount.
- See the scope and terms before use
- Use an eligible, funded inference route
- Know the quoted price before you run
AgreeFunded quoteRun
Explore the discount pathThese are the early-access paths we’re building. Buyer terms, supported integrations and funded offers are confirmed before use.
A direct provider bill stays with your provider unless a provider-supported agreement changes it. Later data rejection cannot raise an already accepted past inference quote.
03 / Less preparation, more buildingMake the useful details
Make the useful details
travel with the code.
OptinRouter’s job is to track, classify, clean and organize the material you choose. The goal: a coherent work record you can inspect, with its context and evidence still attached.
Help shape the builder betaThe context.
The issue, selected files and permitted model exchanges that explain the starting point.
The change.
The patch and tool results your supported workflow can observe, with their sources.
The outcome.
Tests, reviews or a release, with missing evidence and reported results clearly identified.
Choose work you can authorize. Public availability alone does not clear every file, contributor or buyer use. Each offer still needs review of the material, its permissions and the intended use. A source record helps explain where work came from; it does not prove ownership or make a sale automatic.
04 / A few practical questionsBefore your
Before your
next commit.
Start with the work you know. Bring the questions that matter to your project.
Do I have to change my CLI or model provider?
The capture-only path is designed to fit supported existing workflows, including direct use of your own provider account. Client support is checked integration by integration. A funded inference discount uses an eligible route and an approved offer; your direct provider bill stays separate unless that provider supports the arrangement.
What would I choose to capture?
You choose the permitted project and kinds of work evidence: selected model exchanges, file changes, tool results and outcomes that a supported client can observe. The design separates gateway traffic from local tool hooks, so missing or unobserved outcomes stay visible. Capture permission is separate from permission to sell or license the result.
Does preparing a dataset automatically sell it?
No. Preparation organizes material for review. A sale needs an accepted offer or a match to a bounded agreement you already approved, plus current rights, buyer and intended-use checks. You can keep prepared work private, explore a direct sale, or choose optional brokerage under agreed terms.
How can I try it?
Request a builder invite and tell us what you maintain and how you work. We’re building a focused early-access program, with supported clients and terms confirmed before use. This page is for open-source developers; OptinRouter’s own public repository and release details have not been announced here.
Built with buildersMake your next merge
Request a builder inviteMake your next merge
the start of something more.
Maintain a project. Ship a useful fix. Bring your workflow.
Help shape a better deal for the people doing the work.