gate

MCP-powered intent routing works by delegating user requests through a central gateway to specialized vendor skills. This gateway validates intents, enforces read-only safety checks with permissions, and coordinates actions across trading, data, and insights domains to aggregate structured responses.

To route trading intents, provide your request to the gateway entry point. It automatically delegates the task to appropriate vendor skills like gate-exchange-spot, validates safety checks, and aggregates the results into a structured response for read-only operations.

Yes, you can orchestrate multiple vendor domains through one gateway. It centralizes routing across trading, data, and insights domains by delegating actions to dedicated vendor skills while managing validation, permissions checks, and structured response aggregation.

The best way to add new vendor domains is by plugging in new vendor skills under the vendor/ directory. The gateway is extensible and automatically routes user intents to these newly integrated skills for orchestration across different domains.

The gateway routing is limited to read-only actions. It coordinates safe operations by enforcing confirmation and safety checks per the referenced vendor skill workflows, ensuring that all delegated tasks across domains maintain strict read-only permissions.

User intents may not reach the correct vendor skill if the specialized skill is not properly plugged in under the vendor/ directory. The gateway relies on these vendor skills to execute domain-specific actions, so missing extensions will prevent successful routing and task delegation.