sf-agent-api-integration-patterns
Installation
SKILL.md
Agent API Integration Patterns
Use This Skill When
- Choosing an integration pattern for the Agent API (website, headless, connector, agent-to-agent).
- Structuring a reusable client: token management, session lifecycle, message loop, streaming, retries.
- Setting the security and resilience posture before building.
Integration Patterns
| Pattern | Description | Delivery | Notes |
|---|---|---|---|
| Website chat | Embed agent chat on a site/app | Streaming | Token brokered server-side; browser never sees the secret |
| Headless automation | Automate functionality without UI | Sync | Server-to-server; ideal for jobs/workflows |
| Platform connector | Connect to Slack, Teams, custom workflows | Sync or streaming | Standardized REST calls per platform SDK |
| Agent-to-agent | One agent invokes another | Sync | Build an agentic ecosystem; watch credit consumption |
Reference Client Architecture
Structure any integration around four layers: