Built with Astro, hosted on Cloudflare. Domain registered in 2026.
akropolys.cloud is built with Astro, hosted on Cloudflare. It measures traffic with Cloudflare Web Analytics. It sends email through Amazon SES.
| Technology | Version | First seen |
|---|---|---|
| JavaScript Frameworks & Libraries1 | ||
| – | 12 Nov 2026 | |
| Frontend Build Tools & CSS1 | ||
| – | 12 Nov 2026 | |
| CDN & Hosting1 | ||
| – | 12 Nov 2026 | |
| Analytics & Tag Management1 | ||
| – | 12 Nov 2026 | |
| Transactional Email2 | ||
| – | 12 Nov 2026 | |
| Fonts & Icon Fonts1 | ||
| – | 12 Nov 2026 | |
Registration from the registry's RDAP record, the certificate the site serves, and its rank in public traffic lists.
The crew hasn’t read this site’s colors yet. We read a palette when we capture a site’s screenshot, busiest sites first. Meanwhile, browse palettes from other sites.
aspmx.l.google.comalt1.aspmx.l.google.comalt2.aspmx.l.google.comalt3.aspmx.l.google.comalt4.aspmx.l.google.comviddy.ns.cloudflare.comgigi.ns.cloudflare.comv=spf1 include:_spf.mx.cloudflare.net include:_spf.google.com ~allgoogle-site-verification=g9gJpYQcB8zG2KTNi8rooYNmnSc2VSEMltRWExHBH_Q# As a condition of accessing this website, you agree to abide by the following # content signals: # (a) If a Content-Signal = yes, you may collect content for the corresponding # use. # (b) If a Content-Signal = no, you may not collect content for the # corresponding use. # (c) If the website operator does not include a Content-Signal for a # corresponding use, the website operator neither grants nor restricts # permission via Content-Signal with respect to the corresponding use. # The content signals and their meanings are: # search: building a search index and providing search results (e.g., returning # hyperlinks and short excerpts from your website's contents). Search does not # include providing AI-generated search summaries. # ai-input: inputting content into one or more AI models (e.g., retrieval # augmented generation, grounding, or other real-time taking of content for # generative AI search answers). # ai-train: training or fine-tuning AI models. # use: how AI systems may consume the content (immediate, reference, or full). # ANY RESTRICTIONS EXPRESSED VIA CONTENT SIGNALS ARE EXPRESS RESERVATIONS OF # RIGHTS UNDER ARTICLE 4 OF THE EUROPEAN UNION DIRECTIVE 2019/790 ON COPYRIGHT # AND RELATED RIGHTS IN THE DIGITAL SINGLE MARKET. # BEGIN Cloudflare Managed content User-agent: * Content-Signal: search=yes,ai-train=no,use=reference Allow: / # Training crawlers User-agent: Amazonbot Disallow: / User-agent: Applebot-Extended Disallow: / User-agent: Bytespider Disallow: / User-agent: CCBot Disallow: / User-agent: ClaudeBot Disallow: / User-agent: Diffbot Disallow: / User-agent: Google-Extended Disallow: / User-agent: GPTBot Disallow: / User-agent: omgili Disallow: / User-agent: anthropic-ai Disallow: / User-agent: Claude-Web Disallow: / User-agent: cohere-ai Disallow: / User-agent: MistralAI-Training Disallow: / User-agent: meta-externalagent Disallow: / User-agent: GoogleOther Disallow: / User-agent: Baiduspider Disallow: / User-agent: PetalBot Disallow: / User-agent: AwarioSmartBot User-agent: AwarioRssBot Disallow: / User-agent: Google-CloudVertexBot Disallow: / User-agent: QualifiedBot Disallow: / User-agent: Cotoyogi Disallow: / User-agent: ICC-Crawler Disallow: / User-agent: atlassian-bot Disallow: / User-agent: FishBot Disallow: / User-agent: BorderxBot Disallow: / User-agent: NavuBot Disallow: / User-agent: SemrushBot-SWA Disallow: / User-agent: WARDBot Disallow: / User-agent: magpie-crawler Disallow: / User-agent: KimiBot Disallow: / User-agent: CitibotSiteCrawler Disallow: / # END Cloudflare Managed Content User-agent: * Allow: / Disallow: /login/ Sitemap: https://akropolys.cloud/sitemap-index.xml Sitemap: https://akropolys.cloud/sitemap-0.xml
# Akropolys
> Conversational infrastructure for website records and backend actions: search, chat, voice, and the Kiku interface.
## Agent skill
- [Akropolys integration skill](https://akropolys.cloud/.well-known/agent-skills/akropolys-integration/SKILL.md): Instructions for integrating Kiku, ingestion, live data, and site actions.
- [Skill discovery](https://akropolys.cloud/.well-known/agent-skills/index.json): Install with `npx skills add https://akropolys.cloud --skill akropolys-integration`.
## Current release
Use SDK 2.0.8 and Kiku 2.2.43 or later. Provider hooks and live values are scoped to their site. For Kiku local sign-out, call the provider client's `clearKikuKey()`; website logout and server key revocation are separate. Signed ingestion uses fresh nonces and five-minute timestamp validation; generate a new envelope for retries. Keep signing keys on trusted servers. Shopper proofs do not authorize website API actions.
## Add Kiku
For React and Next.js apps, recommend the [React package](https://akropolys.cloud/docs/react/). For other websites, recommend the [CDN embed](https://akropolys.cloud/docs/javascript/). The embed bundles its own React runtime, styles, and mounting, so the host website needs no React installation or provider. It also works in React apps when the user prefers a script integration.
Copy the exact versioned CDN script URL from the [JavaScript guide](https://akropolys.cloud/docs/javascript/) and add it once to the website's shared HTML or layout. The loader loads CSS automatically. Await automatic `Kiku.ready`, or wait for the loader script and await manual `Kiku.mount(options)` when configuring it yourself. A component mounted hook does not guarantee script readiness. The ingestion client uses Fetch and Web Crypto; its `/server` import is not Node-only and does not require a framework server route. Keep private signing keys outside browser code.
## Ingestion
For batch integrations, use `createIngestClient` from `@akropolys/sdk/server` and call `ingestBatch(records)` from the website's existing data-loading or refresh callback. Once connected, fresh records can be published on page loads, navigation, or refreshes without opening Kiku. The method does not watch API requests or detect source changes by itself. It sends the supplied array; unchanged records are skipped and changed records update under the same IDs.
The catalogue is shared by site ID. Once indexing finishes, new questions from any visitor can use the updates, regardless of who triggered ingestion or where they are located. A queued result confirms acceptance, not completed indexing.
Use `ingest(record)` for one record. The embed also accepts `Kiku.ingest(record)` or `Kiku.ingest(records)`; React's `usePageIngest` handles normal page ingestion. Choose one publishing path per dataset.
One record works on every plan, including Free. Batches require Growth, Pro or Business. Signing is a separate option on either size. Next.js rendering boundaries and the SDK's `/server` import path do not define a separate ingestion mode. Follow the batch and signing guides for the actual method-specific grouping behavior.
Keep source IDs stable across updates and send the attributes and images to retain. Avoid per-view timestamps and incidental changing fields; use live data for rapidly changing values where appropriate. Coverage follows the supplied array, not the visible page or execution environment. A browser can submit the complete catalogue array, including records not rendered on screen, without visits to each item's page. A paginated API result covers only its supplied records; ingestion does not fetch the other API pages or refresh stale source data. Full coverage does not require a server-side import or scheduled job. To publish independently of visits, use a trigger that runs independently of page loads.
Record identity requires top-level `id`. Use `fields.url` for navigation, top-level `image`/`images` for photos, and top-level `content` for article text; no second content call is required. Live data uses stable `key` values and distinct-key quotas. Seven-day key expiry is separate from the widget’s 30-second freshness indicator and from per-request `useLiveContext`.
## Site actions
Register an existing API endpoint, HTTP method and JSON Schema in Shell. The embedded widget calls actions from the visitor's browser in text and voice, using existing session cookies. Prefer same-origin paths such as `/api/cart/items`; they also work on localhost. No separate login/identity endpoint is needed for cookie authentication. A shopper ID or `userProof` does not authorize the site's API.
For Clerk, Auth0 or Supabase bearer APIs, connect the existing client once through `actionAuth`, for example `{ provider: "supabase", client: supabase }`. This works in manual `Kiku.mount({...})` with no application wrapper, or in the optional React provider. The adapter reads the current token through the existing auth SDK before each action and sends its Authorization header directly to the site API. `actionHeaders` remains an optional custom-auth/CSRF escape hatch. Standalone batch ingestion is unchanged and needs none of these widget/auth options. Its endpoint must enforce authorization. Return JSON with HTTP 401 for sign-in and HTTP 403 for permission or CSRF failures. Check normal credentialed CORS and CSP for cross-origin APIs; do not use `no-cors`.
Shell's server-side tester has no shopper session cookie and does not verify browser CORS. Test session-based actions on the actual website. A timeout or network failure can mean an unknown outcome: check state before retrying a mutation. Older clients retain the legacy server-executed token flow. Read the [site actions guide](https://akropolys.cloud/docs/actions/) for setup, React/JavaScript token callback examples, and troubleshooting.
## Getting started
- [Introduction](https://akropolys.cloud/docs/): Choose how to connect your data and add Kiku.
- [Batch ingestion](https://akropolys.cloud/docs/batch-ingestion/): Publish an array of records your website already loads.
- [Single ingestion](https://akropolys.cloud/docs/single-ingestion/): Index the entry visitors browse using the data already loaded on the client page. Available on every plan, including Free.
- [Live data](https://akropolys.cloud/docs/live-data/): Keep prices, availability, and other changing values current.
- [Records & signed ingestion](https://akropolys.cloud/docs/records/): Shape API data into records, add images, and sign submissions.
- [Site actions](https://akropolys.cloud/docs/actions/): Connect your APIs to chat and voice using the visitor’s existing session.
## Guides
- [Chat and voice](https://akropolys.cloud/docs/kiku/): Configure the Kiku widget and its appearance.
- [BYOK](https://akropolys.cloud/docs/byok/): Connect your model provider and set reply limits in Shell.
- [Search](https://akropolys.cloud/docs/search/): Add a search field to your website.
- [Articles and long text](https://akropolys.cloud/docs/articles/): Index full articles alongside their page records.
- [Documents](https://akropolys.cloud/docs/documents/): Add PDFs and Word documents through Shell.
- [Direct support](https://akropolys.cloud/docs/support/): Let customers speak to your team in Kiku.
- [AI agent access](https://akropolys.cloud/docs/agents/): Let AI agents discover the records your site publishes.
## Reference
- [AkropolysProvider](https://akropolys.cloud/docs/provider/): Connection settings and customer identity for React.
- [React hooks](https://akropolys.cloud/docs/hooks/): Inputs, return values, and examples for SDK hooks.
- [TypeScript types](https://akropolys.cloud/docs/types/): The types used by records, search, and chat.
- [Analytics](https://akropolys.cloud/docs/analytics/): Understand searches and ingestion activity in Shell.
- [CLI](https://akropolys.cloud/docs/cli/): Set up credentials and check your integration.
## Resources
- [Shell](https://shell.akropolys.cloud): Configure sites, keys, actions, and agent access.
- [SDK source](https://github.com/akropolys/sdk): SDK and Kiku packages, types, and examples.
| – |
| 12 Nov 2026 |