01
Connect your agent
Use a compatible client’s base URL setting or the planned local daemon. Keep the protocol your tool expects, with a scoped key for each workspace.
How it works · Product preview
One route.
A lot more control.
Keep your preferred coding workflow. Enable permitted data capture for a later sale, or choose an eligible program that lowers inference costs as you work.
THE REQUEST PATH01 — 04
01 / YOUR WORKSPACEYour coding agent
Your toolsOptional local protection
02 / ON YOUR MACHINELocal daemon
OptionalYour policy travels with the request
03 / ONE GATEWAYOptinRouter
Eligible route, selected for your request
04 / INFERENCEThe model provider
Your choiceGateway-assisted example. Direct BYOK can use supported capture hooks without rerouting inference. Live routing is not yet available.
ONE ROUTE. A WORLD OF MODELS.
Your workflow enters one policy-aware route. OptinRouter selects an eligible model and keeps the response connected to its request.
One endpointAcross compatible clients
Your policyBefore route selection
Explicit consentBefore any contribution
From request to result
The familiar workflow. A clearer picture.
OptinRouter is designed to sit between your agent and its model provider, with the controls and context you need in one place.
02
Set the boundaries
Choose model preferences, budgets, and permitted routes. Organization rules take priority, including the option to keep every repository Private.
03
See what happened
The gateway links permitted requests and replies. Supported hooks add tool results, tests and outcome evidence, with capture and sale permissions kept separate.
Two ways in
Meet your workspace
where it is.
Start with a hosted connection, or add a local layer when you need protection and session context on your own machine.
Explore the integration designHosted connection
PlannedPoint a compatible client at the gateway with a scoped key. A simple path for remote workspaces, tools, and CI.
- No local daemon required
- Request attribution through scoped keys
- No local redaction; capture needs separate consent
Local daemon
PlannedAdd local secret filtering, repository policies, and device-signed work context before a request or submission leaves your machine.
- Review configuration before applying
- Separate egress and submission checks
- User-controlled local session history
Optional contributions · Planned
Your work can create value.
Choose the terms.
The planned platform captures and organizes work only with permission. Keep your existing inference arrangement and prepare data for a later sale, with optional brokerage, or accept a qualifying data-for-discount agreement before use. Approved benefits may include inference discounts, nonwithdrawable credits or direct revenue.
Understand the consent flow- 01Choose capture permissions
Choose permitted repositories and fields. Keep private work outside capture.
- 02Choose a data program
Sell prepared data later, or review a qualifying agreement before use.
- 03Keep the agreement explicit
Specify buyers, uses and benefits. Automatic delivery follows only accepted rules.
Does using the gateway mean sharing my work?
No. Private is the planned default. Routing a request to a model provider is separate from submitting a session to the contribution program. Your provider still receives the input required to answer your request under its own terms.
Can an organization keep everything Private?
Yes, this is a core design requirement. Organization policy can lock the workspace to Private and restrict which repositories are ever eligible for contributions. These controls are part of the planned gateway release.
Will every coding tool work?
Compatibility depends on whether a tool allows a custom endpoint and on its protocol features. The initial focus is OpenAI-format and Anthropic-format clients. Tested tool versions and known limitations will be published before production support is claimed.
What is available today?
This website and the interactive workspace demo are available to explore. The inference gateway, local daemon, account billing, and contribution program are in development. Request early access to discuss your workflow.
Build with us
Your workflow. Your choice.
Help shape a model gateway built around the way developers actually work.