Can AI replace Animam.ai?

KINDA · weekend project
price $32/moyou'd save $384/yrbuild time weekendcategory 🧩 no-code appsreplaced by 0 peoplebuild unverified

The chat is a weekend. Everything that makes it safe to point at customers is not. Ingest a site, search it, stream an answer · that part is commoditised and the prompt below really does it. What resists is the boring half: an amount computed by the server and never by the model, a visitor email verified before it triggers anything, signed webhooks with retries, and a sending domain whose reputation you did not build in an afternoon.

the prompt
Build a website chat widget that answers strictly from a site's own content. Node 20 + TypeScript, no framework.

1. Install hono, @anthropic-ai/sdk, cheerio, turndown, better-sqlite3.
2. scripts/ingest.ts takes a sitemap.xml URL as argv and fetches every page, concurrency 4, skipping non-HTML.
3. Strip nav, header, footer and script tags with cheerio, then convert what is left to markdown with turndown.
4. Upsert into SQLite pages(url PRIMARY KEY, title, body, fetched_at) so re-running updates rows instead of duplicating them.
5. src/search.ts takes the 3 to 6 most distinctive words of the question and runs SELECT url, title, substr(body,1,1200) FROM pages WHERE body LIKE ? for each.
6. Rank by number of hits and return the top 5. No embeddings: under ~500 pages LIKE is cheaper, instant, and you can read why a passage was picked.
7. src/server.ts is a Hono app with POST /chat {message, sessionId}.
8. Put the 5 passages and their URLs in the system prompt, call claude-haiku with stream:true, and pipe SSE to the client.
9. System prompt: "Answer only from the CONTEXT below, and cite the page you used."
10. Continue it: "If the answer is not in the context, say you do not know and offer to take a message."
11. And the line that matters: "Never state a price, a date or an availability that is not written in the context."
12. public/widget.js is an IIFE that injects a bubble into a shadow DOM and keeps sessionId in localStorage.
13. It consumes the SSE and writes every message with textContent, never innerHTML · the text comes from a model that read the internet.
14. Store sessions and messages in the same SQLite file, so you can read back what people actually asked.
15. ANTHROPIC_API_KEY lives in .env, server-side only, and never reaches the bundle.
16. No telemetry, no third-party script in the widget.
17. Serve /widget.js with CORS * and a 5 minute cache so a single <script> tag installs it on any page.

Out of scope on purpose, and each of these is a week rather than a line: booking on a real calendar, payments,
quotes with amounts computed server-side, human handover, transactional email that reaches the inbox,
multi-tenancy, GDPR consent, rate limiting and abuse protection.

$ open in your agent (prompt prefilled, you press enter) or copy it raw

why people still pay

Because the demo is the easy half. A chat that answers is a weekend; a chat you can leave in front of customers for a year is an operations job · someone watches deliverability, re-crawls the site, keeps the model from inventing a price, and is there the day it breaks. People pay for the second half, and they are right to.

what you lose

xAmounts computed server-side from a price grid · the model picks the SKU, it never produces the number

xVisitor identity verified by one-time code before any server-to-server action runs

xSigned outgoing webhooks with exponential backoff, delivery log and manual redelivery

xSSRF guard with DNS resolution on every URL the agent is allowed to call

xPer-tenant secrets encrypted at rest, and tenant isolation you did not have to think about

xEmail deliverability · a warmed sending domain is not something you prompt into existence

xThe evening the model provider changes a default and your widget starts making things up

prior art · use these instead of building, if you'd ratherChatwootSelf-hosted support inbox with a website widgetTypebotOpen-source conversational forms and chat flowsOnyx (ex-Danswer)Open-source RAG chat over your own documents
share on X ↗"I just replaced Animam.ai ($32/mo) with one prompt"
questions
Can AI replace Animam.ai?

Kinda. The core of Animam.ai is buildable in a weekend with the prompt on this page, but there are real gaps: Amounts computed server-side from a price grid · the model picks the SKU, it never produces the number, Visitor identity verified by one-time code before any server-to-server action runs. Read the honest list above before committing.

How much does Animam.ai cost?

Animam.ai costs about $32/month (Starter, checked 2026-07-30), which is $384 per year.

What do I lose by replacing Animam.ai?

Honestly: Amounts computed server-side from a price grid · the model picks the SKU, it never produces the number; Visitor identity verified by one-time code before any server-to-server action runs; Signed outgoing webhooks with exponential backoff, delivery log and manual redelivery; SSRF guard with DNS resolution on every URL the agent is allowed to call; Per-tenant secrets encrypted at rest, and tenant isolation you did not have to think about; Email deliverability · a warmed sending domain is not something you prompt into existence; The evening the model provider changes a default and your widget starts making things up. If any of those are load-bearing for you, keep paying.

Is there an open-source alternative to Animam.ai?

Yes — Chatwoot (Self-hosted support inbox with a website widget), Typebot (Open-source conversational forms and chat flows), Onyx (ex-Danswer) (Open-source RAG chat over your own documents). Using prior art is also a valid exit; the prompt is for when you want it exactly your way.