RequestRocket Platform
Glossary
The RequestRocket terms used throughout this documentation.
Use these definitions when moving between the app, Core MCP tools, and Core API. API fields can retain older names even when the app uses a different label.
| Term | Meaning |
|---|---|
| Core API | The management HTTP API under https://api.requestrocket.com/api. A user token authorizes its calls. |
| Core MCP | The RequestRocket management MCP server at https://api.requestrocket.com/mcp. An agent uses its tools to manage RequestRocket records. |
| Inbound credential | The credential a caller presents to a proxy or published MCP server. Some API fields and paths call it a proxy credential. |
| Target credential | The credential RequestRocket uses when it calls a target API. |
| Target | The upstream API and base URL that RequestRocket calls. |
| Proxy | A regional record that binds one inbound credential, target, and target credential, then applies policy to calls. |
| MCP server | A customer-published MCP server on a regional gateway. It can be backed by a proxy or configured directly. |
| Consumer | A person who authenticates to a customer-published MCP server. A consumer is separate from a RequestRocket app user. |
| Organisation | The workspace that owns records. Core API paths and MCP tools use client and clientId for the same concept. |
| Region | The deployment location of a regional record. A proxy and the target and credentials it binds use the same region. |
| Predicate | A deterministic set of request or response checks that decides whether a policy record applies. |