Extension Points
Stendar’s public extension plane is the in-process SDK surface that plugs into DeFiRuntime, providers, wallets, notifications, CLI, and AI adapter packages. Product harness extensions remain internal to this monorepo, while MCP can expose the local control plane for private/local agent workflows.
Extension map
Section titled “Extension map”| Goal | Extension point | Package or location |
|---|---|---|
| Add a swap, yield, or bridge integration | Protocol provider | @stendar/core |
| Add a wallet or signer | Wallet adapter | @stendar/wallet-* |
| Use runtime actions in LangChain | LangChain tools | @stendar/langchain |
| Use runtime actions with Vercel AI SDK | Vercel AI tools | @stendar/vercel-ai |
| Use controlled local-runtime workflows from an agent host | MCP control/full plane | internal/ai/mcp (private to this monorepo) |
Use public AI adapter packages when an agent framework needs tool access to an in-process DeFiRuntime. Those adapters expose direct runtime tools; they do not provide the local action lifecycle, control-plane policy state, connector sync, trust gates, or audit export controls. Use MCP control or full mode when an agent host should operate through proposal, dry-run, approval, execution, and audit.
Safety defaults
Section titled “Safety defaults”Keep secrets out of docs, examples, logs, external processing, and package metadata. Prefer dry-run and preview flows. Route money-affecting actions through proposal, dry-run, policy, approval, execution, and audit.