Developers

Available

API Documentation

A public orientation page for AINMAX API documentation boundaries.

AINMAX APIs are versioned and backend-enforced. Public API documentation should explain available contracts without exposing secrets or private data.

What this means

Frontend pages must not invent API contracts.
Protected APIs should remain authentication-required when called without credentials.
OpenAPI and implementation must stay synchronized when backend work is approved.

How AINMAX supports this

Current Resources API documentation page is static public orientation content.
Accepted frontend release gates include route and protected-state smoke tests.
Backend API changes require separate implementation and release-gate phases.

What is available now

Public API documentation placeholder converted to real orientation content.
Versioned backend routes exist for accepted protected features.
Unauthenticated protected route behavior is tested in release gates.

What is planned

More complete API reference content.
Developer quick-start resources.
Federation/API materials only after accepted protocol and security work.

Privacy / safety note

This page does not publish credentials, tokens, internal endpoints, private schemas, or new API contracts.