Skip to main content
A REST connector exposes an HTTP API as tools — one tool per operation.

​
Creating one

In the Portal, Connectors → New connector → REST API. The drawer asks for an OpenAPI specification, either pasted inline or fetched from a URL. Importing a spec is how a REST connector is created. There is no hand-build path in the Portal that starts from an empty operation list. Anything else is rejected as an unsupported version.

​
What import produces

From the spec the importer derives:
  • Base URL — servers[0].url for OpenAPI 3.x; schemes + host + basePath for Swagger 2.0.
  • One operation per endpoint, each with a name, description, HTTP method, path template, and input schema.
  • Parameter mappings — path, query, and header parameters wired to input fields, and a body configuration.
  • Parameter validation — type, regex pattern, minimum, maximum, and enumerated values, carried over from the spec’s schemas.
Supported methods are GET, POST, PUT, PATCH, and DELETE.
Import does not configure authentication. Set it separately after import — see Authentication.

​
What you configure at import

A connector’s configuration is fixed once it is created. Get these right in the create drawer — afterwards you can change the name, description, and whether it is active, but not the configuration itself. To change anything below, create a replacement connector and rebind.
  • An operation’s parameter mapping — see Parameter mapping.
  • Common headers, applied to every request the connector makes. Values are stored encrypted.
  • A response transform per operation.

​
Response transform

A json_path of $.data on an API that wraps everything in {"data": …} keeps the model’s context clean.

​
Working with large specs

Cloud provider specs run to thousands of operations, and every operation becomes a tool. Import a trimmed spec covering the endpoints you actually need rather than the whole surface — and if you do bind a large connector, expect Adaptive tool presentation to switch to Discovery mode once the surface reaches 30 bound tools in total, counting every capability on it, not just this connector.

​
Autonomy

Connector tools are Act tier, kind-wide. The platform cannot tell a read from a write inside somebody else’s API, so every connector tool sits at the tier that pauses under Supervised autonomy and is denied under Read-only. If a connector has genuinely read-only operations you want running unattended, put them on the agent’s auto-approve list explicitly. See Autonomy and approvals.

​
Next