Most agent auth infrastructure locks you into a predefined tool catalog. We shipped a direct proxy layer that lets agents call any API endpoint — REST, SOAP, internal services — with auth injected automatically from the connected account. Your agents aren't limited to what's on our connector list.

Production systems run on raw REST APIs, SOAP endpoints, and internal services that don't fit a predefined schema model. ToolProxy gives agents a direct, authenticated path to any connector's API surface — SaaS systems, custom APIs, and internal APIs alike — without requiring a pre-built tool definition.

A developer builds an agent that needs to POST to Salesforce's Bulk API at /services/data/v58.0/jobs/ingest — not a standard tool in any catalog. Using ToolProxy, the agent sends the endpoint path and payload to Scalekit. Scalekit injects the correct OAuth token, routes through the provider-specific proxy URL, and returns the response. Zero custom auth handling in agent code.

Same pattern for internal APIs: a finance automation agent calling a proprietary GL system routes through the same proxy layer. Agent code is identical regardless of whether the target is Salesforce, Snowflake, or an internal microservice.

How it works

• proxy_url and proxy_enabled fields on the provider schema point to any endpoint.
• Works across REST, SOAP, and XML — not just JSON.
• Auth injected from connected account credentials. No separate setup per endpoint.
• Foundation for Atlassian dynamic routing, Tableau session refresh, and Salesforce SOAP proxy — all built on top of this layer.