Your product, everywhere your users already work.
Faustine maps your API into a governed set of operations and publishes them as an MCP server, so the agents your users already have can operate your product on your terms.
and anything else that speaks the protocol
Your Agent Gateway
The operations you published, and nothing else
Become a place their agent knows how to use.
Your users are already assembling their day out of agents. Agent Gateway makes your product one of the things those agents reach for, with a real interface you own and govern.
Be where the work happens
Your users live in their agents now. When your product is one of the things those agents can operate, it becomes part of every workflow they build.
One integration, every client
Publish once and every agent that speaks the protocol can use it, including the ones your users adopt next year.
On your terms, start to finish
You choose the operations, the identities, the limits and the audit trail. Access to your product stays a decision you make.
Derived from your API. Guarded on every call.
As with everything in the platform, one pipeline builds the map and a governed surface serves it. Here the surface faces outward, so the interesting part is what stands between an agent and your systems.
Four ways in, from one decision.
You curate a set of operations once. Faustine publishes that same set in every shape an agent, a developer or a script might want to use.
An MCP server
The protocol agents already speak. Your operations show up as tools, ready to use.
A REST endpoint
The same operations over plain HTTP, for everything that prefers a normal API call.
An OpenAPI document
A precise description of exactly the surface you chose to publish.
Documentation and snippets
Rendered docs and ready-made connection snippets, generated for each client.
Opening your product to agents is a series of choices, and they are all yours.
Choose what is on offer
Pick the operations you want available, mark the ones that only read, and require an explicit confirmation before anything consequential runs.
Know who is calling
Issue API keys or let users sign in with OAuth. Every request carries an identity, and every identity carries the scopes you granted it.
Set the pace
Rate limits, hourly and daily quotas, concurrency caps and network rules, applied per key and across the whole surface.
See everything
Every call is recorded with who made it, which operation ran, what your API answered and how long it took.
Ship changes safely
Each published surface is versioned with a changelog. Consumers can pin the version they built against and move when they are ready.
Separate your environments
Point one surface at staging and another at production, each with its own credentials, and keep a key to the environment it belongs to.
Your API evolves. So does the surface.
Faustine re-reads what changed when you ship and brings the published operations along with it. Your curation carries over, because operations are matched by what they are rather than by what they were called, and every version arrives with a changelog so the agents built against it know what moved.
You ship a change
A push to the branch you connected.
Faustine re-reads it
Only what the commit touched.
The surface follows
Operations updated, curation preserved.
A new version lands
With a changelog, and pinning if you want it.
Give your users an agentic experience.
Bring your repository to a 30-minute call and we will show you what Faustine builds from it.