Agent Endpoint and My Agent Access
Instead of adding a separate URL for every persona or MCP server, people add one URL to their AI agent and ask for the work they need. The gateway works out which persona or server fits the job, checks that the person is allowed to use it, and opens only those tools.
There are two pages for this:
- Agent Endpoint, under Operations, is where administrators see the URL, what it offers, and change its settings.
- My Agent Access, at the top of the navigation, is where everyone gets the URL, adds it to their agent, and sees what they can get done.
Quick Start
| I want to... | Go to |
|---|---|
| Add my organization's URL to Claude Code, Cursor or VS Code | Add the URL to your agent |
| See what my agent can do for me | What you can get done |
| Choose what the URL offers | Change the endpoint settings |
| Understand who can use what through the URL | Who can use what |
| Connect my own account to an app | Connect your apps |
The Agent Endpoint page
Open Operations → Agent Endpoint. Super admins, platform operators, network admins, security admins and auditors can view this page. Only a super admin can change its settings; everyone else sees "You can view these settings. Only a super admin can change them."
Select See what people see to open My Agent Access as the people in your organization see it.
Your Organization Endpoint
This card shows the URL to share. The endpoint is always on.
Each gateway in your organization serves the same path at its own address, so the URL ends in the same path, such as /ap, on every gateway. When you have more than one gateway, choose one from the list to see and copy its URL. The line below the URL tells you how many gateways serve it.
If no gateway has a public URL yet, the page says so. Deploy a gateway pool first, and the URL appears here.
Available through this URL
Four cards show what people can reach through the URL, and how many of each are available across your gateways.
| Card | What it means |
|---|---|
| Agent Personas | Always on. A persona is offered once it is deployed to the gateway and has Interactive Login turned on. The card tells you how many personas aren't available yet and why. |
| MCPs | When on, agents can use an MCP server directly by its short code. Off by default. |
| APIs | Follows the MCPs setting. Agents can call an API Registry entry by its short code, with only the operations that entry allows. |
| Skills | When on, approved skills that are ready become readable by everyone in your organization. Off by default. |
Each card links to the page where you manage those items.
Gateways
The Gateways panel lists each gateway with its URL and what is deployed to it. The numbers can differ between gateways, because each one serves only what is deployed to it.
Access & security
This panel summarizes how people get in:
- People sign in with your company SSO.
- Group changes and people leaving take effect within minutes.
- The first time someone uses a new agent app, such as Cursor, they approve it once.
It also shows the Persona session length. When a session ends, the gateway asks the agent to renew and retry, so long-running work carries on without interruption. Every renewal checks access again, so a shorter session means someone who has been removed loses access sooner.
How it works
Select How it works for a short walkthrough of one person's day using the URL, from signing in to a call the gateway refuses. The names and codes in it are examples.
Change the endpoint settings
To change the settings (super admin only):
- Open Operations → Agent Endpoint.
- Select Edit settings.
- Make your changes, then select Review changes.
- Check each change and what it will do, then select Confirm and update.
Nothing changes until you confirm. Changes reach every gateway within about a minute.
| Setting | What it does | Default |
|---|---|---|
| Path | The part of the URL after the gateway address. Use / or a single segment of lowercase letters, numbers, - and _, such as /ap. You can't use /mcp or a path the gateway already uses. | /ap |
| MCPs and APIs | Lets agents use an MCP server or API Registry entry directly by its short code. | Off |
| Skills | Makes approved, ready skills readable by everyone in your organization. | Off |
| Persona session length | How long a persona session lasts before the agent renews it. Choose from 1 hour to 7 days. | 12 hours |
Agent personas are always available and have no switch.
Before you confirm, keep in mind:
- Changing the path changes the URL on every gateway. The old URL stops answering, and everyone has to add the new URL to their agents. If some of your gateways are too old to serve a new path, the dialog lists them; upgrade them first, or keep
/ap. - Turning off MCPs and APIs cuts off anyone using an MCP server or API directly. Agent personas keep working.
- Turning off Skills hides every skill from agents on this URL.
- A new session length applies to sessions that start after the update. Sessions already open keep their current expiry.
Who can use what
The URL never gives anyone more than they already have. The same rules apply to personas and to MCP servers used directly:
| If the persona or server... | Who can use it |
|---|---|
| Has no teams | Everyone in your organization |
| Is limited to teams | Members of those teams |
| Is private | Its owner only |
Team membership comes from your company's SSO groups. Portal roles, such as super admin, don't widen what someone can use through the URL; they only control what they can do in the portal. To set teams on a persona or MCP server, see Teams.
Every item the URL offers has a Short Code, shown on its overview page, such as PGA-AED. The first letter tells you what it is: P for a persona, M for an MCP server, A for an API and S for a skill. Codes never change, and people can mention one to point their agent at exactly that item.
If someone asks for something they aren't allowed to use, the agent is told it doesn't exist, the same answer as for something that really doesn't exist.
When a persona changes
Each persona's General settings, on its Configuration tab, include When this persona changes:
- Agents reload it: an agent working through the URL is asked to activate the persona again, and then sees the new tools.
- Keep running: an agent working through the URL carries on with the updated tools without being asked.
My Agent Access
Everyone in your organization, including employees who use nothing else in the portal, can open My Agent Access from the top of the navigation.
Add the URL to your agent
Your Endpoint shows your organization's URL with a copy button. If your organization has several gateways, choose one from the list.
Under Add it to your agent, choose your agent and follow the instruction shown:
| Agent | What to do |
|---|---|
| Claude Code | Run the command shown, then type /mcp and sign in with your company account. |
| Cursor | Add the snippet to .cursor/mcp.json, then press Connect. |
| VS Code | Add the snippet to .vscode/mcp.json. VS Code asks you to sign in. |
| Other agents | Add the URL as a remote MCP server or custom connector, then sign in with your company account. |
For example, the Cursor snippet looks like this, with your own URL in place of the example:
{
"mcpServers": {
"aigw": {
"url": "https://your-gateway.example.com/ap"
}
}
}
If the page says your organization's endpoint isn't set up yet, ask your administrator.
What you can get done
This list is built from the tools in the personas you can use. Each row shows an example of something to ask, the persona that does it and its short code, and whether it's ready:
- Ready means you can ask for it now.
- Connects followed by app names means the first job will ask you to connect those apps with your own account.
Select the copy button on a row to copy the request, with the persona's short code, and paste it into your agent. Select More ideas to get more suggestions for a persona. Suggestions marked Suggested were written by AI from the persona's tools.
Use the search box to find work by app or task, such as Jira or invoices. The list shows what the selected gateway serves; if some of your personas run on another gateway, the page tells you, and you can pick it from the list above.
If nothing is shared with you yet, ask your administrator for an agent persona for your work.
Connect your apps
Some apps act as you, so you connect them once with your own account. Apps to connect, on My Agent Access, lists the apps your personas use that you haven't connected yet. You don't have to connect them in advance: when a job first needs an app, your agent shows you a link to connect it.
To connect ahead of time, connect from the portal:
- From an MCP server. In the MCP Registry, servers you can connect show a Connect button. On the server's Overview tab, select Connect, sign in to the app, and approve access. Once connected, the server shows "Your … account is connected", with Reconnect and Disconnect.
- From a persona. When a persona has apps waiting, its Overview tab shows how many, with a Connect Apps button. The Connections section on the persona's Configuration tab lists every app the persona uses that needs your own sign-in. Select Connect for one app, or Connect all.
For servers that use Cross App Access, connecting signs you in with your organization's identity provider instead of the app. See Cross App Access.
Tips
- Share one URL. Put the URL from Your Organization Endpoint in your onboarding guide instead of a list of persona and server URLs.
- Check what people see after a change. See what people see opens My Agent Access as your employees find it.
- Leave MCPs and APIs off unless people need them directly. A persona gives people the tools for one job; direct access offers every tool a server exposes.
- Check the Agent Personas card if a persona isn't showing up. It tells you how many aren't available yet, usually because they aren't deployed or don't have Interactive Login turned on.
Cequence AI Gateway