Open Portal
Developer Portal

The Technical Entry Surface

developer.iai.one is the live technical-facing portal for APIs, SDKs, node development, and integration onboarding. The public page currently returns 200 HTML and presents itself as an IAI Developer Portal.

Portal Purpose

Onboarding

Give developers a fast path from curiosity to first authenticated call, first flow integration, or first node or plugin build.

Reference

Hold API contracts, SDK packages, webhook semantics, and integration examples that are too implementation-heavy for landing pages.

Extension

Explain how builders, nodes, agents, or connectors extend the system without forcing developers to reverse-engineer the runtime.

Recommended Content Map

Should Live On developer.iai.one

  • Auth, sessions, tokens, and environment setup.
  • Webhook guides, event contracts, and retry semantics.
  • SDK install docs, package references, and sample apps.
  • Node-development and extension-author workflows.
  • Changelogs specific to developers and integrators.

Should Stay Canonical On docs.iai.one

  • Global ecosystem map and ownership boundaries.
  • Cross-surface architecture and product model.
  • Security principles and deployment model.
  • Service registry and live surface inventory.
  • High-level docs that apply beyond developers alone.

Sync Rules Between Docs And Developer Portal

Avoid dual truth

If a contract, auth flow, or SDK version is published in two places, one of them will drift unless the ownership rule is explicit. The portal and the docs hub need a clean split.

  • docs.iai.one explains the system and links out to technical detail.
  • developer.iai.one owns integration detail, reference depth, and implementation examples.
  • API docs on docs.iai.one should summarize observed public surfaces and point to the developer portal for deeper route-by-route references.
  • Each API release should update both the developer portal reference and the high-level docs summary at the same time.

What The Developer Team Should Add

  • Explicit auth model for api.iai.one and api.flow.iai.one.
  • Route catalogs for Flow Engine APIs, webhook entrypoints, and error envelopes.
  • Node or extension authoring guide with lifecycle hooks and execution context.
  • SDK status table: planned, experimental, stable.
  • Annotated screenshots for onboarding if the portal includes interactive consoles or config screens.