Agent Gateway

Agent Gateway lets approved AI assistants, automation tools, and external apps use selected Relewise capabilities through My Relewise. Access is controlled per Dataset, by user permission, by Personal Access Token, and by the Agent Gateway areas you enable.

Use Agent Gateway when you want tools outside My Relewise to work with Relewise on behalf of a real user, without sharing Dataset API Keys.

What You Can Configure

• Dataset Access Policy controls whether Agent Gateway is enabled for the active Dataset, which transport types are allowed, and which Agent Gateway areas are available.
• Personal Access Tokens authenticate external requests with your My Relewise user identity.
• Request Logs help you troubleshoot allowed and blocked Agent Gateway requests.
• Team Permissions control who can manage or use Agent Gateway for each Dataset.

Agent Gateway Documentation

• Get Started
• Dataset Access Policy
• Personal Access Tokens
• Security and RBAC
• Request Logs

API Reference and MCP

Agent Gateway includes an interactive API reference for the public REST API. Open https://my.relewise.com/agents/ to view it.

The API reference uses the public OpenAPI document at https://my.relewise.com/agents/openapi/v1.json.

MCP clients connect to the Dataset-specific MCP endpoint:

https://my.relewise.com/agents/{Dataset ID}/mcp

MCP tools are discovered through the MCP protocol after the client connects. The URL identifies the Dataset and MCP surface, not an individual tool.

How Access Is Evaluated

Agent Gateway checks several gates before a request is allowed:

1. The Personal Access Token must be valid.
2. The token must be available for the requested Dataset.
3. The requested transport must be enabled globally for Agent Gateway.
4. The Dataset must exist and be available to the user.
5. The user must have permission to use Agent Gateway for that Dataset.
6. Agent Gateway access must be enabled for the Dataset.
7. The requested transport must be enabled for the Dataset.
8. The requested area must be enabled for the Dataset.

If a request is blocked, the request log shows the outcome and failure reason.