Developers

Available

OpenAPI

How OpenAPI should describe implemented AINMAX APIs without overclaiming.

OpenAPI is the contract language for implemented HTTP APIs. AINMAX public OpenAPI content must stay aligned with real backend behavior.

What this means

OpenAPI should document accepted routes, request models, responses, and errors.
Draft or planned routes should not be presented as production contracts.
OpenAPI changes require implementation, validation, and release gate acceptance.

How AINMAX supports this

Release gates include OpenAPI validation where API changes are involved.
Resources can explain the role of OpenAPI without publishing unsupported routes.
Developer pages remain static orientation content in this phase.

What is available now

Static OpenAPI resource page.
Existing project API documentation references accepted API areas.
No browser-exposed secrets or private schemas.

What is planned

Public OpenAPI download or explorer only after separate approval.
Versioned schema publication process.
Examples and generated clients only from accepted contracts.

Privacy / safety note

This page does not publish a new OpenAPI contract, add endpoints, or activate developer integrations.