Create a gateway
The New Gateway wizard creates a gateway with a Production environment, the APIs you pick and, optionally, a first credential. Everything the wizard sets can be changed afterwards.
Before you begin
- An API in APIs whose analysis has finished. You can create the gateway without one and add the API later. See Analyze your first API.
Create the gateway
To create a gateway:
- In the portal, go to Agent Gateway and select New Gateway.
- Under Who is this gateway for?, select one option. The choice sets the kind of the first credential and what it does with operations that require confirmation.
- People using chat and coding agents creates a gateway user that asks the person before those operations run.
- Automations and code creates an API key that refuses those operations.
- Both starts with a gateway user. You add keys later.
- Under APIs, select the APIs this gateway serves, then select Continue. If you have no API yet, select Skip for now.
- Under Name & URL, enter a Name. The Slug is filled in from the name and is the last part of the URL. The MCP URL field shows the address clients will use.
- Select Continue.
- Under First credential, select A user, An API key or Later.
- For a user, enter a Display name and a Username, and generate or type a password.
- For a key, enter a Key name.
- Select Continue, review the summary, and select Create gateway.
A dialog shows the key, or the username and password, once. Copy it before you close the dialog. Faustine stores only a hash of a key, and a user's password can only be reset, not read.
The gateway opens on its Overview tab, which lists what is left to set up.
What the wizard creates
| Item | Value |
|---|---|
| Environment | Production, as the default environment. |
| Operations | Every operation of the selected APIs is exposed, except recipes and deprecated operations. |
| First credential | Scoped to every operation, not read-only. |
| Confirmation | Ask the person for a user created under People or Both. Refuse for a key created under Automations and code. |
Change the name or the slug
The name and the slug are in the gateway's Settings tab.
Warning
Changing the slug changes the MCP and REST URLs. Every client configured with the old URL stops working.
Next steps
- Choose which operations are exposed: hide what clients should not call.
- Connect clients: set up Claude, ChatGPT, Cursor, n8n or your own code.
- Create a gateway user: add more people.
- Environments: add Staging next to Production.
Last updated November 11, 2026