flmnt → request access
Private beta · onboarding teams one at a time
Tell us what your agents keep getting wrong.
The decision that won't die. The mistake that keeps coming back. The file someone swears is current. We read every signup, and what you write decides whether this helps you yet — sometimes the honest answer is that your project isn't big enough.
Who it's for
Teams running coding agents on a project with real history behind it.
What you get
A workspace, an MCP endpoint, and your existing agents connected to it.
What it costs
Nothing during the beta. Pricing →
After you register
Three things, in order.
Within a few days
We read it and reply. Every signup gets an answer, including the ones we turn down. If your project is too small for this to earn its place yet, we'll say so rather than take the seat.
When your spot opens
A workspace and an endpoint. You create a workspace and get the MCP URL for it. That's the whole setup — no SDK, no rewrite, no change to how your team works.
First session
Point your agents at it. Register the endpoint in Claude Code, Cursor, Codex or whatever you run. The client-by-client steps →
Why it's gatedWe onboard one team at a time because the first week matters more than the signup. Access is granted rather than self-served while we're in beta.
Not what you're looking for?
Three other doors.
You're building a product
The SDK is public on npm and doesn't wait on a beta seat. You'll still want a key, but the package and its docs are open now.
You need the security review first
Dedicated deployment, residency, DPA and MSA. Tell us your constraints and we'll tell you what's possible.
You want to check the claims
Every probe, every score and the judge rubric are public, including the arm where the vector-only baseline scores zero.