Your project writes the spec.
We ship the rest, free.
Client libraries in ten languages, published under your own namespace. A documentation site on your own domain. An MCP server so assistants can call your API. All generated from the OpenAPI document you already publish, and rebuilt whenever it changes.
Free permanently for open source projects, and not a trial. We ask for an attribution line and the right to say we work with you. That is the whole trade.
Applications are read by a person, usually within three working days.
Everything needed to ship SDKs
The grant lifts the three limits that matter for shipping a client library: how many languages you can publish, how large your spec can be, and whether releases go out on their own.
All ten SDK languages
TypeScript, Python, Go, Rust, Ruby, PHP, Java, Kotlin, Swift and Dart, generated from your spec and rebuilt every time it changes.
Publishing under your own namespace
Automatic releases to npm, PyPI, crates.io, Maven Central, Packagist and the rest. The packages are yours, on your account, not ours.
A docs site on your own domain
Generated from the same spec, with your branding and your custom domain. Search, versioning and an API reference that stays in step with the code.
An MCP server
One executable tool per endpoint, so an assistant can call your API instead of only reading about it. Regenerated with everything else.
A thousand endpoints
Above every self-serve tier. Measured against real projects: the largest specs we looked at run past five hundred operations and keep growing.
Permanent, reviewed once a year
This is not a trial or a twelve-month coupon. The annual review is a conversation, and a withdrawn grant drops a project onto a paid tier with its packages intact.
Two things are at free-tier volume, on purpose
Monitoring is included at 100 MB of ingress a month and AI documentation credits are a one-time grant of one hundred. Both are enough to see what the features do and neither will carry a busy project. We put the numbers on the page so they are not a surprise in week three. Going over the monitoring allowance does not switch ingestion off, and we do not bill grant recipients for it.
All we ask is credit
Every SDK runtime we ship is MIT, all ten of them. We want to be part of this ecosystem, and a grant is where that costs us something.
There are two reasons beyond goodwill and both are worth naming. An SDK under your namespace puts us in front of every developer who installs it. And large, awkward, real-world specs are the best thing that can happen to a generator: several projects we would like on this list have specs bigger than anything we see day to day, and fixing what they break makes the product better for everyone.
- A small "Docs by Octri" credit in your documentation footer, linked back to us.
- A one-line credit in each generated SDK README.
- Your permission to mention that we work together, and to point at the generated SDKs as examples of our work.
- If you are happy after a couple of months, a sentence we can quote. If you are not, we would much rather hear that instead.
Nothing beyond that. We do not ask for exclusivity, a press release, or any say in your roadmap, and nothing here changes who owns your code or your packages. Support is the same community channels everyone else uses.
Eligibility
Four things. The last one is the one to read twice.
- 01An OSI-approved licence on the project itself.
- 02A published OpenAPI or Swagger document. It does not have to be tidy, and fixing it is part of what we do.
- 03Actively maintained, which we read as a release in the last six months.
- 04No paid hosted tier of the project. If you have one, talk to us about a commercial plan instead.
One email, six lines
There is no form and no account to create first. The button below opens a mail draft with the questions already in it.
- 01Project and repository
- 02Licence
- 03Your OpenAPI or Swagger spec, as a URL
- 04The languages you would ship first
- 05Rough API traffic per month
- 06Who maintains it, and who we would work with
The traffic figure is the only one people hesitate on. A rough order of magnitude is fine; it tells us whether the monitoring allowance will frustrate you, and it lets us set that expectation up front.
Or write to hello@octri.dev in your own words.
Questions
No. Every SDK runtime we publish is MIT licensed, all ten of them, plus the command-line tool and the MCP layer. Nothing you hand your users is proprietary, and the generated code is yours under whatever licence you choose for it. If your project has licensing commitments that rule out generated dependencies, tell us and we will not push back; that is a values question, and we will take your word for it.