Overview
How Appstrate connects to third-party services and model providers, and how personal agents and coding agents connect to Appstrate.
Appstrate connects in two directions.
Inbound, plug things into Appstrate. Integrations (Gmail, Slack, Notion, and 64 others) give agents access to third-party services without exposing credentials: each is an AFPS package, connected per user or end-user, called through the sidecar. Model providers supply the LLM that runs the agent: you bring an API key for one of the supported vendors or a custom OpenAI or Anthropic compatible endpoint, or an operator enables a Claude or ChatGPT subscription provider.
Outbound, plug Appstrate into other systems. A personal agent running on your own machine can use Appstrate as an execution backend: it reasons locally, then launches runs through the REST API or MCP when you need multi-tenant execution, credential-hidden tool calls or parallel runs. Coding agents such as Claude Code can drive Appstrate the same way.
None of the outbound patterns is shipped as an SDK. They are patterns over the REST API and the MCP endpoint, documented below so you know what to build.
Inbound
| Page | What it covers |
|---|---|
| How Integrations Work | What an integration is, local and remote sources, auth methods, how accounts are connected, scopes, connection selection and credential isolation |
| Built-in Integrations | The 70 integrations shipped with every instance, with auth method and source, plus setup guides for the most used ones |
| Custom Integrations | Write your own integration as an AFPS package: REST API, OAuth 2.0, custom fields, hosted or local MCP server |
| LLM Models | Model providers (API key and subscription), models, defaults, per-agent overrides, system models and aliases |
Outbound
| Page | Pattern |
|---|---|
| Personal Agents | Your personal agent is the brain, Appstrate is the arms: multi-tenant, isolated, credentialed execution |
| Coding Agents | Drive Appstrate from Claude Code, Codex or any agent with HTTP or MCP access |
Sandbox and Sidecar
How a run is isolated, and how the sidecar lets agents call the outside world without ever holding a credential.
How Integrations Work
What an integration is, how an agent reaches a third-party service through it, how users connect accounts, and how credentials stay out of the agent's reach.