Appearance
Security and Permissions
BETA
Agent Gateway is in BETA, and we're continuing to expand its capabilities. Your feedback helps shape what we build next—reach out to us through Relewise Support.
Agent Gateway uses OAuth or Personal Access Tokens, Agent Gateway Configuration, and My Relewise permissions to decide whether a request is allowed.
Permissions
Agent Gateway has two Dataset permissions.
| Permission | What It Allows |
|---|---|
| Manage Agent Gateway | View and update Agent Gateway settings for a Dataset. This permission also includes Use Agent Gateway. |
| Use Agent Gateway | Access the Dataset through Agent Gateway using OAuth or a Personal Access Token. |
Users with the Administrator role have access by default.
Members do not get Agent Gateway permissions by default. An Administrator or a user with Manage Members can grant the relevant permissions.
Authentication
Agent Gateway uses bearer-token authentication. OAuth access tokens and Personal Access Tokens can be used for REST and MCP connections.
Send the token in the Authorization header. Replace <token> with your OAuth access token or Personal Access Token:
http
Authorization: Bearer <token>The token identifies the authenticated My Relewise user. Agent Gateway verifies that the user still exists and is enabled.
Authorization Gates
Agent Gateway authenticates the credential before evaluating Dataset authorization. The credential must exist, must not be expired or revoked, and must identify an enabled user and permitted connection.
Missing, invalid, expired, and revoked tokens are rejected with 401 Unauthorized and do not appear in Request Logs.
To use a capability for a Dataset, all of these requirements must be met:
- The token is available for the requested Dataset.
- The Dataset exists.
- The Dataset is visible to the user, who has Use Agent Gateway for it.
- Agent Gateway is enabled for the Dataset.
- The requested Connection Method is enabled for the Dataset.
- The requested Allowed Area is enabled for the Dataset.
Agent Gateway records the outcome and failure reason for requests that reach these authorization checks.
If access is denied, check the error message and Request Logs to identify the missing permission or setting.
Public Routes
When Agent Gateway is accessed through My Relewise, public routes are exposed under https://my.relewise.com/agents.
Use https://my.relewise.com/agents/ to open the interactive API reference for the Agent Gateway REST API.
Use https://my.relewise.com/agents/mcp when connecting an MCP client. See Get Started for connection and Dataset selection instructions.
Internal Agent Gateway routes are not exposed through the My Relewise reverse proxy.