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 work with selected Relewise capabilities through My Relewise. It gives these tools access on behalf of a real user without sharing Dataset API Keys.

Access remains controlled per Dataset. Agent Gateway checks the user's permissions, the credential's Dataset access, the enabled Connection Method, and the Allowed Areas before a tool can use a capability.

Choose How to Connect

Use Relewise with an AI Assistant

For ChatGPT, OpenAI Codex, Claude, Claude Code, and GitHub Copilot CLI, the Relewise plugin is the recommended option. It provides guided setup, discovers the Datasets available to you, and includes reusable Relewise workflows.

Install the Relewise plugin, then let your AI assistant guide you through connecting and resolving any remaining access requirements.

Build a Custom Integration

Use MCP to connect an MCP-compatible client directly, or use the REST API when building an application that makes HTTP requests to Agent Gateway.

Both connection methods support OAuth and Personal Access Tokens. Prefer OAuth for interactive clients. Use a Personal Access Token when the integration needs to store a bearer token.

Manage Agent Gateway

In My Relewise, open Administration > Agent Gateway for the active Dataset.

• 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.
• Connected Apps let OAuth clients authenticate through My Relewise and use approved Dataset access.
• Request Logs help you troubleshoot allowed and blocked Agent Gateway requests.
• Team Permissions control who can manage or use Agent Gateway for each Dataset.

See Configuration, Security and Permissions, and Request Logs for detailed administration guidance. Browse Areas to understand the available capabilities.

How Access Is Evaluated

To use a capability for a Dataset, these requirements must be met:

1. The credential must be valid.
2. The credential 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.

If installation, connection, or access fails, see Troubleshooting and FAQ.