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

  • Bazaar — applet packaging, OCI distribution

  • Schemas — protobuf + OpenAPI contracts

  • 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

  • API Gateway — KrakenD routing, auth, rate limits

  • CLI — the flexgalaxy command-line tool

  • API Reference — Redoc-rendered service references by product and version

(Per-product dev pages are deployed by each project’s CI to /dev/<product>/. This landing page indexes them. Update when a product is added/removed. 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.)