Agent Gateway Areas

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.

Areas group the capabilities available through Agent Gateway. Enable the ones your client needs under Allowed Areas.

Area	What You Can Do
Core	Read-only Dataset settings, metadata, and consumption information. Core is required and always allowed.
Entities	Find and inspect Products, Variants, Content, Categories, and Brands. Access is read-only and excludes User entities.
Analytics	Read-only insights into Search performance and attributed revenue.
Merchandising	Inspect rules that influence Search and Recommendation results, and change their enabled state or schedule.
Search Tools	Inspect Search rules and Search Indexes that refine search terms and results, and change rule approval.
Retail Media	Inspect Retail Media configuration and Campaign performance, and update Advertiser state and Campaign approval, schedules, and budgets.
Triggers	Read-only Trigger configurations for marketing automation, including criteria, evaluation windows, and enabled states.
Administration	Read-only Jobs, schedules, custom configuration, and execution history, including execution summaries and log messages.

Each Area page explains its capabilities and essential usage guidance. For complete inputs and response schemas, use the API reference or MCP tool discovery. To choose a connection option, see the Agent Gateway overview.

Page-Number Pagination

Use pageNumber (default 1, one-based) and pageSize (default 50, from 10 through 100). MCP accepts them as top-level tool arguments, REST GET lists use query parameters, and REST Analytics POST bodies nest them under pagination.

Responses include pagination with pageNumber, pageSize, totalResults, and totalPages. Totals describe the full list. Keep the Dataset ID, filters, period, and page size unchanged while advancing pages. Stop when the returned page reaches totalPages or contains no results. Collections can change between calls; pagination does not provide a consistent snapshot.

For example, call list_trigger_configurations with these arguments, replacing the illustrative Dataset ID with one selected from get_me:

{
  "datasetId": "a01c9fe4-a603-4661-b132-fce9a53be432",
  "pageNumber": 1,
  "pageSize": 50
}

If the returned pagination is {"pageNumber": 1, "pageSize": 50, "totalResults": 73, "totalPages": 2}, call the same tool again with:

{
  "datasetId": "a01c9fe4-a603-4661-b132-fce9a53be432",
  "pageNumber": 2,
  "pageSize": 50
}

Combine the two configurations arrays and stop after page 2.