Lists are the platform
You own a list — countries, products, clinics, anything people pick from. AutoSugges publishes it as an immutable version and serves it from the edge, never from a live database query.
Every list has exactly one owner tenant. A platform list — like the built-in countries list — is owned by the AutoSugges platform tenant itself, using the same model a customer list uses; there is no separate code path for “global” data.
From list to lookup
Three steps, and queries never touch your list's live data — they read the version you published.
1. Author a list
Add items with a display value, optional hierarchy, aliases, locale variants and metadata (emoji, flags, icons) through the dashboard or import.
2. Publish an immutable version
Publishing creates a new version of your list. A version activates only after it verifies, and once published it never changes — a client never sees data mixed from two versions.
3. Serve it from the edge
Every query is answered from the edge, so a keystroke never waits on a database.
Publishing and quota
Publishing is reversible, and running out of allowance never returns made-up results.
Superseded versions stay available rather than deleted immediately, so rolling back to a previous published version is one action in the dashboard, not a re-import.
Usage is counted on our side against your subscription, never the client’s say-so. When the allowance is exhausted, a query returns a structured quota_exceeded / upgrade_required response — never placeholder results standing in for real data.
What an item can carry
One item structure, flexible enough for a flat list or a hierarchy, without a second data model for each domain.
Aliases and synonyms
“US”, “USA” and “United” all resolve to the same same item — an alias costs nothing extra at query time.
Hierarchy with ancestor auto-fill
Selecting a city can return its state and country in the same selection, so a form fills three fields from one pick instead of three separate lookups.
Localization
A list can carry locale-specific display values, so the same canonical item reads correctly for every audience it serves.
Rich display metadata
Items carry emoji, flags and icons as data, not as a rendering hack — a country item can carry its own flag without your code computing one.
One SDK, one embeddable component
The same @autosugges/client package powers a plain HTML page, a React app, Next.js and Expo — and the AutoSugges dashboard's own playground is not a special build, it's the same package.
Debounce and result-limit policy come from the list’s own configuration, delivered with the runtime key rather than hard-coded in the client. Every integration guide carries a Copy for AI / LLM control next to the ordinary code sample, so an agent and a person get the same instructions.