What is API Connector?

Every API is idiosyncratic. Gmail wants OAuth and returns base64 message parts; Stripe cursors through pages; Slack rate-limits per method. A connector absorbs that so the caller doesn't have to: it holds the credentials, refreshes tokens before they expire, maps a clean action like send email onto whatever the service actually wants, walks pagination, retries the 429s, and turns a wall of provider-specific error codes into something a caller can reason about. Written once, it's the difference between an integration and a weekend of glue code.

Velaris connectors don't sit in the prompt. Their actions become entries in the capability mesh — searchable data the agent queries at runtime — so a catalog of a thousand tools costs a run nothing until it needs one. Each action is tagged read, write or destructive, which is what an approval gate keys off: archiving an email and deleting one are the same API surface but not the same decision. Credentials stay scoped to the run rather than being handed to the model.