You can now control exactly which Enterspeed APIs each environment client can access. 

What's new 

Environment clients now support API Scopes, letting you follow the principle of least privilege by granting each client access only to the endpoints it actually needs. The available scopes are: 

• Delivery API – access to content delivery endpoints 

• Query API – access to transformed, schema-based data 

• Routes API – access to route management and execution 

• Source API – access to raw, auto-indexed source data 

• MCP Server – enables MCP tool endpoints for AI agents (requires Query API and/or Source API) 

To make configuration easier, the Management App includes preset configurations: Standard (Delivery + Routes + Query), AI Assistant (Transformed Data), AI Assistant (Source Data), AI Assistant (Full Access), and Custom for manual control. 

Why it matters 

Not every client needs full platform access. Scopes let you issue purpose-specific clients – for example, an AI agent that only queries transformed data doesn't need Delivery or Routes access. This is especially useful when integrating with AI agents or third-party services where limiting exposure matters. 

The MCP Server scope is worth calling out specifically: it enables tool endpoints for AI agents but does not provide data access on its own. It must be paired with Query API and/or Source API to function. 

What you need to do 

Nothing breaks. All existing environment clients will continue to work with the default scope configuration – Delivery API, Query API, and Routes API – ensuring full backward compatibility. 

To configure scopes on a client, open the Management App, navigate to your environment client, and select Edit Scopes. You can choose a preset or configure scopes manually. 

Full documentation is available in the Enterspeed docs. 

Questions? Reach out on our support Slack channel or at support@enterspeed.com.