Tool — OpenAPI (type: openapi)
Expose a REST API to the agent from its OpenAPI 3.x spec. The spec is embedded inline in the toolbox tools: block (under an openapi object) — this is a connectionless built-in, not a connection-backed tool. API-key auth is the one mode that also needs a custom-keys connection. For the toolbox concept, versions, and endpoint, see toolbox.md.
Each operation becomes one tool named \{name\}___\{operationId\}, so every operation in the spec needs an operationId (letters, -, _ only).
🚦 Before creating a toolbox/connection either way, read create-hosted.md → Toolbox creation boundary.
Tool entry shape
yaml
tools:
- type: openapi
openapi:
name: catfacts # tool-name prefix: {name}___{operationId}
spec: { <inline OpenAPI 3.x document> }
auth: { type: anonymous } # or connection / managed_identity — see belowAuth modes
| Auth | auth object | Connection needed? |
|---|---|---|
| Anonymous | \{ type: anonymous \} | No |