Справочник API публикуется на английском языке.

Handle named MCP gateway protocol requests

POST/api/tool-gateway/gateways/{gatewayId}/mcp
No API key
Veyra Docs TeamОбновлено Версия 3 · История

Handle named MCP gateway protocol requests.

Авторизация

No API key is needed: the token or id in the path, or the request's own signature, authenticates the call. Как работают ключи.

Параметры пути

gatewayIdstringОбязательныйThe gateway's id.

Тело запроса

application/json · обязательно

Любой JSON-объект.

Ответы

200SuccessThe request worked; the body holds the result.
202SuccessAccepted; the work continues in the background.
400Bad requestThe request is malformed or failed validation. details names each field that failed.
401UnauthorizedNo key, or the key is unknown, revoked or expired.
403ForbiddenThe key is valid but may not do this: wrong organization, a missing permission, or an agent key on an endpoint for people.
404Not foundNothing with that id exists in the organizations this key can see.
429SuccessToo many requests; wait for Retry-After seconds.

Ошибки возвращают {"error": "..."}, часто вместе с code и details. Подробнее: ошибки и ограничения.

MCP gateway