API Reference

The API reference starts with reviewed setup pages and public-safe references.

Use the product guides for the current supported workflows. Do not publish raw endpoint inventories, internal routes, private auth headers, provider details, or generated stubs before public filtering is complete.

Current scope

• External MCP clients for connecting compatible developer tools to approved website actions.
• Connect developer docs for connector package installation.
• Workflow quickstart for dashboard-first workflow setup.
• Knowledge & Capabilities for safe action boundaries.
• TROPIKAL Connect for approved Connected Data.
• Website quickstart for the current website connection workflow.
• Publish to website for sending reviewed workflow content to a connected website.
• Error reference for common user-visible failures.
• Rate limits for retry and usage guidance.

Publishing rule

Endpoint pages should be added only after they are reviewed for public use and rewritten into customer/developer language. API docs should explain what a customer can safely do, not expose operations plumbing.