Skip to main content
A connection links a workspace agent to an external toolkit or provider — a SaaS integration, a data source, or a model vendor — so the agent can act through it with managed auth and billing.

​
The proxy

The proxy is the single authenticated surface agents use to reach connected tools, model providers, and selected external data providers. It centralizes:
  • Authentication (the pak_ API key).
  • Billing and credit preflight.
  • Permission and access checks.
  • Request attribution.
  • Provider-specific request routing.
Because the proxy handles auth and billing uniformly, an agent uses one credential and one base URL rather than managing per-vendor secrets.

​
What the proxy covers

  • Tools API — search toolkits, authorize, inspect, and execute connected tools. See Tools API.
  • App Connection API — use source-agent connections from server-side App code. See App Connection API.
  • Model APIs — OpenAI-, Anthropic-, Gemini-, and other-compatible model routes. See Model APIs.
  • Provider APIs — non-model data providers. See Provider APIs.
Start at the Proxy Overview.