Appearance
Agent Gateway Configuration
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.
The Agent Gateway Configuration controls how tools can connect to a specific Dataset and which capabilities they can use.
Open Administration > Agent Gateway in My Relewise to manage the configuration for the active Dataset.
Connection Methods
Connection Methods control how connected tools can reach Agent Gateway. Select one or more Connection Methods. Agent Gateway is enabled when at least one Connection Method is selected and disabled when none are selected.
| Connection Method | What It Means |
|---|---|
| REST API | For applications making direct HTTP requests. |
| MCP | For AI assistants and MCP-compatible clients. |
Enable only the Connection Methods your connected tools need. The REST API option includes a link to the interactive API Reference.
Allowed Areas
Allowed Areas control which Relewise capabilities connected tools can use with the Dataset.
Core is required, always enabled, and cannot be deselected. The Allowed Areas controls are unavailable when no Connection Methods are enabled.
| Area | What It Allows |
|---|---|
| Core (Required) | Read-only Dataset context and consumption information. |
| Analytics | Read-only insights into Relewise performance and user behavior. |
| Merchandising | View and manage rules that influence Search and Recommendation results. |
If a request targets an area that is not enabled, Agent Gateway blocks it and records the reason in the request log.
Request Throttling
Agent Gateway applies request throttling to protect the service and the connected Dataset. If too many requests are sent in a short time, the request may be rejected with a rate-limit response. Retry later or reduce the request frequency from the connected tool.