Choose Date, Time, or Range, then test any Aion presentation without leaving this page.
Everything here becomes hosted API options. Nothing is downloaded into the client site.
Set Minimum age to 18, 21, or another age and Aion calculates the birth-date cutoff automatically. Leave “Age checked on” empty to use the current date.
Leave a token untouched and Aion keeps the selected preset. These values publish with your configuration.
Your Aion host stores the configuration. Client sites still call you; they never download an Aion package.
Load that script, then call InfinisAion.openPublished().
No downloads. No API keys. No client-side package to maintain. Use the built-in presets immediately, or publish an exact configuration.
Load this once from your Aion domain. It exposes Date, Time, Range, all presentations, styles, themes, restrictions, and color options.
Load Aion from your own host once on the page.
Build it in Design, publish it, then give clients the generated hosted asset URL. The configuration stays on your server.
Instead of explaining Aion from scratch, attach the implementation manual to Chat. It documents the hosted API model, every picker mode, presentation, theme, style, calendar layout, color token, restrictions, published configurations, inline rules, events, logging, and implementation patterns.
Use the attached Aion Chat Implementation Manual as the source of truth. Integrate Aion through my externally hosted API endpoint. Do not download, copy, or recreate Aion locally. Choose the best mobile-first Date, Time, or Range implementation and only use the documented Aion controller methods, presentations, styles, themes, calendar layouts, restrictions, published configurations, and color tokens. If I provide a published configuration endpoint, use openPublished().