External agent API
External agent runtimes use a dedicated signed-service API, not a human bearer token. The current machine-readable contract is available from the external-agent OpenAPI document in the authorised Gamut environment.
Operation families
Section titled “Operation families”| Operation | Purpose |
|---|---|
| Context | Request bounded workspace context through the governed context adapter. |
| Model | Request Gateway-mediated model inference. |
| Tool invocation | Request one exact registered adapter operation. |
| Child-agent request | Request bounded delegated identity when parent policy permits delegation. |
| Heartbeat | Record runtime liveness and version metadata. |
| Result | Record bounded result metadata without sending secrets or unrestricted payload dumps. |
Security model
Section titled “Security model”Requests are authenticated, integrity-protected, time-bounded and protected against replay. The runtime identity, tenant, agent and request context must match current governance. A valid signature does not authorise an action by itself: Gateway still evaluates identity, connection, Tool Permission, Runtime Access Policy, approval and live request context.
Client responsibilities
Section titled “Client responsibilities”- Keep service credentials in a secrets manager.
- Generate a fresh request identifier, timestamp and signature for each request.
- Follow the exact canonical signing contract from the current OpenAPI/SDK version.
- Do not retry an action with stale signed material.
- Treat context, connector results and user content as untrusted input.
- Do not send provider credentials, full secret-bearing payloads or unnecessary personal data in result metadata.
- Handle denials and dependency failure as stops, not advisory warnings.
Change management
Section titled “Change management”Pin and test the supported SDK or contract version. Revalidate after runtime, agent identity, connection, policy, model or tool changes. Use a non-production environment before enabling live actions.