Developers

Build on contracts that can be verified.

AION developer documentation is evidence-gated. APIs, SDKs, schemas and integration guidance become public only after their contracts are stable, validated and safe to expose.

API contracts

Versioned interface definitions, authentication requirements, request/response schemas and failure behavior.

Integration patterns

HTTPS APIs, signed webhooks and authenticated queues are preferred boundaries between runtime systems and external product surfaces.

Security boundaries

Shared databases, shared secrets, direct volume mounts and unauthorized cross-system data access are not part of the public integration model.

Evidence & compatibility

Published examples must map to a tested interface version and include clear compatibility and update information.

Developer preview status: public API reference, SDK downloads and production credentials are intentionally unavailable until their release gates pass.