Appearance
Get Started with Agent Gateway
Use this guide to enable Agent Gateway for a Dataset and authenticate your first request.
Prerequisites
You need access to My Relewise and a Dataset where you can use Agent Gateway.
To change the Dataset Access Policy, you need either:
- The Administrator role, or
- The Manage Agent Gateway permission.
To call Agent Gateway with a Personal Access Token, you need either:
- The Administrator role, or
- The Use Agent Gateway permission.
Step 1: Enable Dataset Access
In My Relewise, open the Dataset and go to Administration > Agent Gateway.
Enable Agent Gateway Access, then choose the transport types and areas the Dataset should allow.
Start with the smallest access you need. For example, enable MCP Access and Core if you only want an AI assistant to verify that it can connect to the Dataset.
Step 2: Create a Personal Access Token
From the Agent Gateway page, select Manage Your Tokens.
Create a token, store the token value immediately, and choose which Datasets the token can access:
- No Datasets blocks the token from all Datasets.
- All Datasets allows every Dataset available to your user.
- Selected Datasets allows only the Datasets you select.
The token value is shown once. If you lose it, regenerate the token and update the connected tool.
Step 3: Authenticate Requests
Agent Gateway uses bearer-token authentication.
Send the token in the Authorization header:
http
Authorization: Bearer <personal-access-token>When Agent Gateway is reached through My Relewise, public Agent Gateway routes are available under https://my.relewise.com/agents.
For REST API calls, the public route shape is:
text
https://my.relewise.com/agents/api/v1/datasets/{Dataset ID}/...You can explore the REST API in the interactive API reference at:
text
https://my.relewise.com/agents/The API reference loads the public OpenAPI document from:
text
https://my.relewise.com/agents/openapi/v1.jsonStep 4: Connect an MCP Client
MCP lets an AI assistant discover and call Agent Gateway tools through the Model Context Protocol.
For MCP clients, the public route shape is:
text
https://my.relewise.com/agents/{Dataset ID}/mcpConfigure your MCP client to use the full My Relewise URL for that route and authenticate with the Personal Access Token as a bearer token.
MCP tools are discovered by the client after it connects. You do not add a tool name to the URL.
Step 5: Check Request Logs
If a request does not work as expected, open View Request Logs on the Agent Gateway page. The logs show allowed and blocked requests with outcomes and failure reasons.