Agent Gateway

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 lets approved AI assistants, automation tools, and external apps use selected Relewise capabilities through My Relewise. Access is controlled per Dataset by user permissions, Personal Access Token Dataset Scope, Connection Methods, and Allowed Areas.

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

• Agent Gateway Configuration controls which Connection Methods are enabled for the active Dataset and which Allowed 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
• Agent Gateway Configuration
• Core Area
• Analytics Area
• Merchandising Area
• Personal Access Tokens
• Security and RBAC
• Request Logs

Connect to Agent Gateway

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.

See Connect with the REST API for authentication, endpoint, and AI tool guidance.

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.

See Connect an MCP Client for setup and authentication guidance.

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 Dataset must exist and be available to the user.
4. The user must have permission to use Agent Gateway for that Dataset.
5. Agent Gateway must be enabled for the Dataset.
6. The requested Connection Method must be enabled for the Dataset.
7. The requested Allowed Area must be enabled for the Dataset.

Missing, invalid, expired, and revoked tokens are rejected with 401 Unauthorized before the request reaches the Dataset authorization checks. These authentication failures do not appear in Request Logs.

For requests that pass authentication, Request Logs show the authorization outcome and failure reason.