The boundary
What Stacklink owns, and what your app owns.
Stacklink is a boundary layer. It sits between your AI agent and the messy outside world — provider APIs, OAuth, webhooks, legal corpora, code execution — and exposes one clean contract.
When your application runs the agent
Stacklink owns external provider accounts, provider toolkits, tool search, tool execution, knowledge packs, verified evidence receipts, triggers, polling, webhooks, jobs, artifacts, and raw provider events. Your consumer app owns final answer generation, product policy, and product-specific UI.
With Bots, Stacklink also runs the model/tool loop, stores the conversation and produces the answer. Your application still owns its sign-in, product policy and customer-facing UI. The ownership table below describes the tool-integration path.
This split is deliberate. Your app never stores a provider credential, never writes an OAuth callback handler, and never maintains a polling cursor. Stacklink returns provider results, artifacts, events, normalized metadata, and verified evidence — and you decide how to present or act on them.
Who owns what
| Stacklink owns | Your app owns |
|---|---|
| Provider accounts & encrypted credentials | The conversation and final answer |
| Tool catalog, search, and execution | Product policy and guardrails |
| Knowledge packs & evidence receipts | How evidence is presented to the user |
| Triggers, polling, webhooks, events | What to do when an event arrives |
| Jobs, artifacts, raw provider objects | Your UI and user experience |
Next: how a request actually flows through the platform — see Architecture.