Custom APIs: connect any HTTP API with any auth

• No auth for public APIs.
• Bearer token, with a custom prefix such as Token or Bot.
• API key sent as a header, a query parameter or a cookie.
• Basic and Digest auth with a username and password.
• Custom headers: any number of secret headers, for schemes built on headers.
• OAuth 2.0 client credentials: Novalink fetches a token and renews it before it expires.
• OAuth 2.0 authorization code, with PKCE: sign in once and the token is refreshed for you.
• AWS Signature v4 for AWS services and API Gateway.

An endpoint is a saved request with a name. Write {name} anywhere in its path, query, headers or body to make an input. Inputs in the path are required; the others are left out when empty.

PATCH /items/{item_id}
Body: { "title": "{title}", "count": "{count}" }

In the editor palette, My APIs lists your APIs. Adding one creates an API node; pick an endpoint and fill its inputs with values or templates, or choose Custom request to send any method and path on that API. Attached to an Agent as a tool, the agent fills the inputs you left empty.

• Secrets are encrypted at rest, never returned to the browser, and scrubbed from responses and run records.
• A path can never leave the base URL's host, and redirects are not followed.
• Private and loopback addresses are refused, the same as the HTTP Request node.