Gateway API
The enforcement plane. Agents talk here and nowhere else.
These routes are served by the gateway process, not the control plane, and they are the authorization boundary. The SDK is a convenience layer over them: deleting the SDK changes nothing about what an agent is allowed to do.
#Endpoints
| Endpoint | Permission | Notes | |
|---|---|---|---|
POST |
/gateway/v1/token |
none | — |
POST |
/gateway/v1/handshake |
none | — |
POST |
/gateway/v1/actions |
none | — |
POST |
/gateway/v1/mcp/call |
none | — |
POST |
/gateway/v1/a2a/invoke |
none | — |
#What each endpoint does
#POST /gateway/v1/token
Exchange a signed assertion for an agent session token.
Requires no console permission.
#POST /gateway/v1/handshake
Establish an agent session and receive authorized tools.
Requires no console permission.
#POST /gateway/v1/actions
Request a protected action through the enforcement pipeline.
Requires no console permission.
#POST /gateway/v1/mcp/call
Invoke an authorized MCP tool through Veefore.
Requires no console permission.
#POST /gateway/v1/a2a/invoke
Invoke a verified A2A peer through Veefore.
Requires no console permission.