Developer Docs

Integration reference for FlexGalaxy.AI APIs, SDKs, and CLIs.

By product

  • DotID — identity APIs, OIDC client setup, FRN, JWT validation

  • TrustMint — device + scope API, OTA

  • DDI — unified device SDKs, protocol surface, MQTT, and OTA routes

  • Bazaar — marketplace publishing, entitlements, catalog, and OTA rollouts

  • NovaBell — notification delivery for first-party services

  • wes-contract — planner-to-executor REST + gRPC contract between any WMS / OMS / ERP and any WES

  • WMS — FGAI WMS public ingest API for pushing master / documents / inventory from any upstream system

Platform-wide

  • The FlexGalaxy.AI API — the one public host, its capability paths, authentication, errors, rate limits and versioning

  • API Reference — the versioned, edge-assembled reference for every public capability

(Per-product dev pages are deployed by each project’s CI to /dev/<product>/. This landing is NO LONGER hand-maintained: scripts/check-landing-coverage.mjs derives the product set from the publish lanes and fails in BOTH directions.

Measured 2026-08-17: this list omitted bazaar and novabell, both live at 200. /dev/api-gateway/ was worse than missing — it was live at 200 with content frozen at 2026-07-12, advertising a base URL on the BANNED .com domain, with NO source tree in any repository and NO publisher: the lane had been deliberately disabled on 2026-08-12 (api-gateway adc060d, “no neo docs content”) and nothing removed the bytes or this link. It now has a real MyST source tree and a live strict lane again, so the page has an owner and every future correction has somewhere to land. /help/api-gateway/ was deleted outright — a gateway has no product users.) Cross-product links use raw HTML anchors with absolute paths (/dev/<product>/) because the same built page ships to two locations per build-landings.yml: the audience prefix s3://fgai-docs-flexgalaxy-ai/dev/ and the bucket root s3://fgai-docs-flexgalaxy-ai/ (the latter so that docs.flexgalaxy.ai/ resolves). Relative paths like dotid/ would resolve correctly from /dev/index.html but break to /dotid/ (404 / AccessDenied) when the same file is served at root. Absolute paths work from both locations. MyST link syntax can’t be used either because the target .md files live in sibling repos that the landings build cannot resolve at build time.)