Skip to contentAINMAXSTORIES CONNECT

Developers

Available

API Reference

A high-level API reference orientation without changing API contracts.

AINMAX API references should help developers understand accepted platform areas without inventing endpoints or implying that planned integrations are live.

What this means

  • API documentation must follow the implemented backend and OpenAPI contract.
  • Public pages can describe API areas at a high level, but they must not create new contracts.
  • Authentication, authorization, privacy, and rate limits remain backend concerns.

How AINMAX supports this

  • Current static Resources content explains developer boundaries.
  • Accepted API details remain documented through project OpenAPI and API docs.
  • Future API expansion requires separate backend, OpenAPI, tests, and acceptance.

What is available now

  • Static API Reference orientation page.
  • High-level references to public/authenticated API areas already accepted elsewhere.
  • No new endpoint behavior from this page.

What is planned

  • Detailed public API reference when contracts are ready for publication.
  • Examples tied to accepted OpenAPI definitions.
  • Versioned changelog for API changes if future contracts change.
Privacy / safety note

This page does not add endpoints, change API contracts, expose tokens, enable federation, or promise inactive API features.

Related resources

Continue reading