Hooky docs
Hooky adds a chat bubble to your sites. Your visitors message you, you reply from your dashboard or your phone, and you count what counts: signups, orders, clicks.
Getting started
- Create your account with Google or a link sent by email. No password. You’re asked for your first site: its name and address.
- In Sites, open your site and copy the install prompt. Paste it into the tool that builds your site, or into your AI assistant.
- Publish your site: the bubble shows up at the bottom of the screen. Messages land in Messages.
The prompt works in any tool that writes code:
- Claude
- ChatGPT
- Codex
- Claude Code
- Lovable
- Bolt
- v0
- Cursor
- Replit
- Windsurf
And on any site where you can add a <script> tag: Framer, Webflow, WordPress, a hand-coded site… On Shopify, install the Hooky app instead: nothing to paste.
Even quicker: ask your AI to do it all. “Create a Hooky account with my email lila@example.com and install the bubble on https://example.com.” See Create an account from an AI.
Install the bubble
With a prompt
The easiest way. Your dashboard gives you this prompt with your site’s key already in it:
Add the Hooky chat bubble to this site, on every page.
Paste this tag once, just before </body>, in the HTML template shared by every page (index.html for a React or Vite app, app/layout.tsx for Next.js, using the Script component from next/script with strategy="afterInteractive"):
<script src="https://heyhooky.com/widget.js" data-site-key="SITE_PUBLIC_KEY" async></script>
Do not change the script URL or the data-site-key attribute. Do not add any other code: the bubble shows up by itself at the bottom of the screen.With Claude, ChatGPT or Codex, paste it into the conversation where you work on your site: the AI hands you back the edited file, or edits it itself if it has access to your code.
By hand
One line, just before </body>, on every page:
<script src="https://heyhooky.com/widget.js" data-site-key="SITE_PUBLIC_KEY" async></script>With Next.js (App Router), in app/layout.tsx:
import Script from "next/script";
export default function RootLayout({ children }) {
return (
<html lang="en">
<body>
{children}
<Script src="https://heyhooky.com/widget.js" data-site-key="SITE_PUBLIC_KEY" strategy="afterInteractive" />
</body>
</html>
);
}The public key (data-site-key) identifies your site. Anyone can see it in the page’s code: that’s expected. You’ll find it in Sites, under the prompt.
Script tag options
| Attribute | Meaning |
|---|---|
data-site-key | Required. The site’s public key. |
data-lang | Optional. The bubble’s language: fr, en, es, pt, it or de. Without it, the bubble follows the page’s language (<html lang>), then the browser’s, and English by default. |
Color, side of the screen (right or left) and welcome message (on or off, in the visitor’s language) are set in Sites, with a live preview. Changes apply without touching your site’s code.
The bubble’s style is chosen in the same place, with a thumbnail for each: Neo (neo, the default), thick black borders and solid offset shadows; Soft (doux), no borders, very rounded, blurred shadows and a white header with an initials badge; Minimal (minimal), flat, thin lines and small corners; Night (nuit), a dark panel. Your site’s color applies in every style.
Site addresses
AI tools often publish your site on their own address (my-site.lovable.app, my-site.vercel.app…) before your real domain. Add every address in Sites: conversations and stats stay in one place.
- As long as no address is declared, the bubble works everywhere.
- Once there’s one, the bubble and stats only work on the addresses in the list. Nobody can use your key anywhere else.
www.doesn’t count:example.comalso coverswww.example.com.- To test locally, add
localhost(any port). A page opened as a file (file://) has no address: serve it with a small local server. - On an address that isn’t allowed, or with a key that no longer exists, the bubble just stays hidden.
Open the bubble from a button
Once the bubble has loaded, your page can open or close it:
<button type="button" onclick="window.Hooky && Hooky.open && Hooky.open()">Contact us</button>
Hooky.open(); // opens the bubble
Hooky.close(); // closes itHandy for a “Contact us” button in your menu or at the bottom of a product page.
Identify the visitor and attach data
Your site already knows who is signed in: tell the bubble. On the conversation’s details, your team reads the name, the email, your own user ID and the data you attach (their plan, their cart…). The visitor no longer has to give their first name or email.
A signed-in user
// After sign-in, or on every page for a signed-in user
Hooky.identify({
name: "Lila Martin",
email: "lila@example.com",
userId: "u_1042", // your own ID
plan: "Pro", // any other key becomes free data
customer_since: "2025-03-14"
});
// On sign-out
Hooky.reset();A cart, a step
// Merged with the previous data: only these keys change
Hooky.setAttributes({ cart: 49.9, items: 3, step: "payment" });
// null removes a key
Hooky.setAttributes({ step: null });Before the bubble has loaded
As with stats, if your code calls Hooky very early, first add this line to the <head>. It covers Hooky.track too: calls are queued, then sent in order as soon as the bubble is there.
<script>window.Hooky=window.Hooky||{q:[]};"track identify setAttributes reset".split(" ").forEach(function(m){Hooky[m]=Hooky[m]||function(){Hooky.q.push([m].concat([].slice.call(arguments)))}});</script>How it works
- No conversation yet: everything stays in the page and is sent with the first message. After that, each change is sent right away, grouped (a single request for everything that changes within the same second). Offline, it goes out with the next message.
nameandemailreplace the conversation’s. With the email, the bubble no longer asks for a first name or email; with the name alone, the first name is already filled in.- A
userIddifferent from the current conversation’s means another account on the same device: the bubble forgets the conversation, likeHooky.reset(). The new visitor doesn’t see the previous one’s thread. Hooky.reset()forgets the conversation, the identity, the data and the draft. Call it on sign-out.- None of these calls ever throws an error in your page.
Data rules
| Field | Rule |
|---|---|
| Free data | A flat object: 50 keys at most, 8 KB in total (beyond that, the last keys are dropped). New keys replace old ones, the others stay. |
| Key | 1 to 64 characters: letters, digits, spaces, _, . and -. Otherwise it is ignored. |
| Value | A string (cut at 500 characters), a number or a boolean. null removes the key. Arrays and objects are ignored. |
userId | A string or a number, 200 characters at most. |
name, email | The name: 100 characters at most. The email: a valid address, otherwise it is ignored. |
| Rate limit | 30 updates per minute per visitor. |
Hooky cleans up whatever goes over, and never refuses the visitor’s message because of it.
What your team sees
On the conversation’s details, under the email, site and page: Device (“Chrome · macOS”, read from the browser; “iPhone 15 Pro · iOS 18.2” from an app), User ID (your userId), then Data: each key and its value, “Yes” or “No” for a boolean, numbers formatted for the reader’s language, links clickable. The details update live.
This data is declarative: the site key is public, so anyone can call Hooky.identify from their browser console with any ID they like. It helps your team place the visitor; it doesn’t prove who they are. Never put a secret in it (password, token, card number), and never use it to grant access or act on an account: always check on your side.
Mobile apps (iOS, Android, Flutter)
The same conversation, native in your app: no WebView, your site’s color, live replies, photos and PDFs, the device’s language and dark mode. The public key is the web bubble’s; messages land in the same inbox. Apps have no address: they get through even when your site has declared its own.
| SDK | Requirements | Installation |
|---|---|---|
| iOS | iOS 15 or later, SwiftUI and UIKit | Swift Package Manager: https://github.com/Defdjamel/hooky-ios |
| Android | Android 6 or later (minSdk 23), Compose and XML views | Maven (GitHub): maven("https://defdjamel.github.io/hooky-android") then implementation("com.heyhooky:hooky-android:1.1.0") |
| Flutter | Android 7 or later (API 24) and iOS 15 or later | GitHub, a git dependency in pubspec.yaml: https://github.com/Defdjamel/hooky-flutter (ref: 1.1.0) |
Three lines are enough: configure at launch, the bubble on your screen, or open from your own button.
// iOS (Swift)
Hooky.configure(siteKey: "SITE_PUBLIC_KEY")
ContentView().hookyBubble()
// Android (Kotlin)
Hooky.configure(context, "SITE_PUBLIC_KEY")
HookyBubble(Modifier.align(Alignment.BottomEnd).padding(20.dp))
// Flutter (Dart)
Hooky.configure('SITE_PUBLIC_KEY');
Scaffold(floatingActionButton: const HookyBubble())Then, the same calls as on the web: identify, setAttributes and reset to identify the user (see Identify the visitor and attach data), track for stats (see Stats in the page), and the number of unread replies, live.
The full docs, platform by platform:
Stats in the page
Count what happens on your site with Hooky.track. Call it right after the action has succeeded:
// Someone signs up
Hooky.track("signup");
// A purchase: value is summed (an amount)
Hooky.track("purchase", { value: 49 });
// With details
Hooky.track("purchase", { value: 49, product: "vase", delivery: true });Cards show up in Stats, site by site, over 7, 30 or 90 days, in your time zone.
With your AI
You don’t have to write this code. Ask for it, or copy the full prompt from the Stats tab:
Add Hooky conversion tracking to this site. The Hooky bubble is already installed (widget.js script tag from heyhooky.com).
Call Hooky.track("event_name") right after the action has succeeded:
- signup: after the account is created;
- purchase: after payment, with the amount: Hooky.track("purchase", { value: 49 });
- contact: after a form is sent.
If this code can run before widget.js has loaded, first add in the <head>:
<script>window.Hooky=window.Hooky||{q:[],track:function(n,d){this.q.push(["track",n,d])}};</script>
Do not send any personal data (no email, name or phone number) in the properties.Before the bubble has loaded
The bubble loads async: if your code calls Hooky.track very early, first add this line to the <head>. Events are queued, then sent as soon as the bubble is there.
<script>window.Hooky=window.Hooky||{q:[],track:function(n,d){this.q.push(["track",n,d])}};</script>Rules
| Field | Rule |
|---|---|
| Name | Free text, 64 characters max. Lowercased, and spaces become _. Letters, digits and _ . : - only. "Newsletter Signup" becomes newsletter_signup. |
value | Optional. A number, summed in the card (an amount, a quantity). Without value, a single numeric property is used instead. |
| Properties | Optional. 20 max, flat: strings (500 characters max), numbers or booleans. They show up in the latest events. |
| Rate limit | 120 events per minute per visitor. |
Never send personal data (email, name, phone, address) in an event. Count actions, not people.
Stats from a server
Some events are only known server-side: a payment confirmed by Stripe, a signup created by your API. Send them with the site’s secret key.
curl -X POST https://api.heyhooky.com/v1/events \
-H "Authorization: Bearer hks_your_secret_key" \
-H "Content-Type: application/json" \
-d '{"name": "purchase", "value": 49, "properties": {"product": "vase"}}'The secret key
It starts with hks_. The owner and admins find it in Sites, on the site’s page, under “Secret key (server)”, and can regenerate it: the old key stops working right away. Keep it on your server (in an environment variable), never in your page’s code or in a public repo.
The request
| Field | Meaning |
|---|---|
name | Required. The event name (same rules as in the page). |
value | Optional. A number, summed. |
properties | Optional. A flat object, 20 keys max. |
occurred_at | Optional. When the event happened, in ISO 8601 (2026-10-04T14:30:00Z), up to 7 days in the past. Otherwise, now. |
Responses
| Status | Meaning |
|---|---|
201 | Saved. The body returns the event: {"event": {"id", "name", "value", "properties", "source": "api", "occurred_at"}}. |
401 | {"error": "invalid_secret_key"}: missing, wrong or regenerated key. |
422 | {"error": "invalid", "errors": {…}}: empty or malformed name, too many or nested properties. |
429 | More than 600 events per minute for this key. Try again a bit later. |
Examples
Node.js (18 or later):
await fetch("https://api.heyhooky.com/v1/events", {
method: "POST",
headers: {
Authorization: `Bearer ${process.env.HOOKY_SECRET_KEY}`,
"Content-Type": "application/json",
},
body: JSON.stringify({ name: "purchase", value: 49 }),
});Python:
import os, requests
requests.post(
"https://api.heyhooky.com/v1/events",
headers={"Authorization": f"Bearer {os.environ['HOOKY_SECRET_KEY']}"},
json={"name": "purchase", "value": 49},
timeout=5,
)In a Stripe webhook (checkout.session.completed), the amount paid is session.amount_total / 100.
Channel: receive notifications
Every site has a channel, a bit like a Slack channel you only read: your server, Stripe, Zapier, GitHub, a cron… post notifications to it, and you read them in Channels, live, with a notification on your phone. Nobody replies.
The channel speaks the Slack incoming-webhook format: any tool that can “send to Slack” can send here. Its address is in Sites, on the site’s page, or in Channels (“Channel address” button).
curl -X POST https://api.heyhooky.com/hooks/hkc_channel_key \
-H "Content-Type: application/json" \
-d '{"text": "*New order*: €49 :tada:", "username": "Shop"}'The channel address isn’t public: anyone who has it can write to it. Call it from your server, not from the page, and regenerate it if it leaks (the old one stops right away). The owner and admins can see it.
The message
| Field | Meaning |
|---|---|
text | The message, in Slack mrkdwn (4,000 characters max). Required unless blocks or attachments provide one. |
username | Optional. Who is speaking (“Shop”, “Stripe”, “CI”). Otherwise, the site name. |
attachments | Optional. Cards, as in Slack: color (good, warning, danger or #RRGGBB), pretext, title, title_link, text, fields (title, value), footer. 10 cards max. |
blocks | Optional. The Slack blocks header, section (with fields), context and divider, flattened to text. |
The body can be JSON (whatever the Content-Type) or a form with payload=<json>, like Slack. Response 200 {"ok": true}; 400 no_text without a message; 404 if the address no longer exists; 429 beyond 60 messages per minute. Messages are kept 90 days.
Formatting
*bold* _italic_ ~strike~ `code` ```code block```
<https://example.com/admin/123|See the order> <https://example.com>
> a quote
- a list
:tada: :rocket: :warning: :white_check_mark: :moneybag:Write &, < and > to show &, < and >, like Slack.
With your AI
In Channels, the “Channel address” button gives you a prompt to paste into the tool that builds your site: it sends a notification for every order, signup or form, from the server, with no personal data.
With an API key, GET /v1/sites returns each site’s channel address (channel_url), GET /v1/channels/:site_id reads its notifications and GET /v1/channels/search searches them.
Create an account from an AI
No account yet? Your AI can create one for you, then install the bubble right after. Just tell it:
Read https://heyhooky.com/llms.txt, then create a Hooky account with my email lila@example.com and install the bubble on https://example.comWhat happens next:
- The AI calls the Hooky API with your email and your site’s address. The account and the site are created immediately, with a default API key.
- It gets the site’s
<script>tag and installs it. The bubble works right away: messages wait for you. - You get an email, “Your Hooky account is ready”. Click Activate my account (the link is valid for 7 days) and log in with Google or a link sent by email.
- Answer your visitors on the web (the dashboard, which also works on your phone) or in the Hooky app for iPhone, iPad, Mac and Android (on the App Store and Google Play).
The email proves the address is really yours: the AI never gets the activation link, the API key or the messages. Without activation, the account and its messages are deleted after 7 days.
The request
curl -X POST https://api.heyhooky.com/v1/agent/signup \
-H "Content-Type: application/json" \
-d '{"email": "lila@example.com", "site_url": "https://example.com", "locale": "en"}'| Field | Meaning |
|---|---|
email | Required. The person’s email address: the activation link is sent there. |
site_url | Required. The site’s address, which becomes its first allowed address. |
domains | Optional. More allowed addresses (10 max): the tool’s preview address (my-site.lovable.app), localhost to test locally. |
site_name, account_name | Optional. Otherwise, taken from the address (example.com → “Example”). |
locale | Optional. The email’s language: fr, en, es, pt, it or de. |
Response 201: the account (status: "pending_activation"), the site with install.script_tag and install.instructions, the address the activation link is sent to, and next_steps, the steps to tell the person. Errors: 422 (invalid_email, invalid_site_url), 429 (too many requests, or three accounts already waiting for activation for this email).
The API with a key
An API key (hka_…) opens your account to a script or an AI: creating sites, reading their install tag, the stats, conversations and channels, answering visitors, sending events. Every account gets one when it’s created. The owner and admins manage them in Developers: create one per use, revoke them.
An API key opens the whole account. Keep it server-side (HOOKY_API_KEY), only give it to an AI that works on your code, and revoke it if it leaks.
curl https://api.heyhooky.com/v1/sites \
-H "Authorization: Bearer hka_your_api_key"| Request | Meaning |
|---|---|
GET /v1/account | The account, its plan, the number of sites. |
GET /v1/sites | The sites, with their public key, their secret key, their channel address (channel_url) and install.script_tag. |
GET /v1/sites/:id | One site. |
POST /v1/sites | Create a site: {"url": "https://example.com"} or {"name", "domains": […]}, with optional color, position, theme, greeting_enabled (greeting_enabled: true shows the welcome message, translated into the visitor’s language). theme: neo (default), doux, minimal or nuit, otherwise 422. 402 plan_limit beyond the plan. |
PATCH /v1/sites/:id | Change a site: name, color, position, theme, greeting_enabled; domains replaces the allowed addresses, add_domains adds to them. |
GET /v1/stats | Stats: site_id, days (7, 30 or 90), time_zone (Europe/Paris by default). |
POST /v1/events | An event, with site_id added (or the site’s secret key, without site_id). |
GET /v1/conversations | Ongoing conversations, most recent first: closed=true for closed ones, site_id for one site, cursor (the value of next_cursor) for the next page. |
GET /v1/conversations/:id | The visitor and the latest messages of the thread; before (a message id) to go back, after for new ones. Reading marks nothing as read. |
POST /v1/conversations/:id/messages | Answer the visitor: {"body": "…"}, or multipart/form-data with files[] (up to 4 files). The reply is signed by the key’s creator (otherwise the owner) and the conversation becomes read. |
GET /v1/channels | The sites’ channels, with their last message. |
GET /v1/channels/:site_id | The latest 50 messages of a channel; before, after or around (a message id) to move around. |
GET /v1/channels/search | Search the channels: q (2 to 200 characters), optional site_id and before; 30 results per page. |
Errors: 401 invalid_api_key (missing, wrong or revoked key), 404 (a site, conversation or channel of another account), 429 beyond 300 requests per minute.
Read and answer messages
Your script or your AI reads the ongoing conversations, opens a thread, then answers. The visitor sees the reply live, or gets it by email if they left their address.
curl https://api.heyhooky.com/v1/conversations \
-H "Authorization: Bearer hka_your_api_key"
curl -X POST https://api.heyhooky.com/v1/conversations/42/messages \
-H "Authorization: Bearer hka_your_api_key" \
-H "Content-Type: application/json" \
-d '{"body": "Yes, we deliver to Lyon within 48 hours."}'A reply reaches a real visitor, signed with the name of the person who created the key. If an AI answers for you, ask it to show you every reply before sending it.
The MCP server
The MCP server connects your Hooky account to your AI (Claude, Claude Code, Cursor, Codex…): it creates your sites and installs the bubble, reads your conversations and notifications, answers your visitors and reads your stats, without you copying anything.
Address: https://api.heyhooky.com/mcp (HTTP transport). Your AI connects with your account: a Hooky page opens, you sign in (or create your account) and allow access. It can also use an API key, in the Authorization: Bearer hka_… header.
Claude Code
In a terminal, then type /mcp in Claude Code and pick hooky to sign in:
claude mcp add --transport http hooky https://api.heyhooky.com/mcpClaude on the web and desktop
Add Hooky from Claude’s connector directory, then Connect. Or go to Settings › Connectors › Add custom connector, with the address https://api.heyhooky.com/mcp.
Codex
In ~/.codex/config.toml, then codex mcp login hooky to sign in:
[mcp_servers.hooky]
url = "https://api.heyhooky.com/mcp"Cursor and other tools
In .cursor/mcp.json, or in your tool’s MCP configuration file. Without the header, a tool that supports it signs you in with your account:
{
"mcpServers": {
"hooky": {
"url": "https://api.heyhooky.com/mcp",
"headers": { "Authorization": "Bearer hka_your_api_key" }
}
}
}| Tool | What it does |
|---|---|
get_account | The account, its plan, the number of sites. |
list_sites | The sites, with their install tag. |
create_site | Add a site, and get its install tag. |
update_site | Change a site: name, color, side, style, welcome message, addresses. |
list_conversations | Ongoing (or closed) conversations. |
get_conversation | A conversation’s messages. |
reply_to_visitor | Answer a visitor. |
list_channels | The sites’ notification channels. |
get_channel | A channel’s notifications. |
search_channels | Search the channels. |
get_stats | The stats. |
reply_to_visitor sends a real message to a real visitor, signed with your name: your AI should show it to you before sending. Each connected tool gets a key in its name (for example “Claude · MCP”): remove it in Developers to cut its access.
Answering visitors
- Visitors write without creating an account. They can leave their first name and email.
- All your sites land in one inbox, Messages, live. You can filter by site.
- Tab open, you get a sound and the unread count in the title; tab closed, a browser notification, if you allowed it.
- Notifications from your tools (orders, deployments…) land in Channels, one per site: see Channel.
- A script or an AI can also read your conversations and answer them, with an API key.
- A message stays unread for a few minutes? An email alerts your team. On the other side, if the visitor left their email before leaving, your reply reaches them by email, with a link that reopens the conversation on your site.
- If the visitor closed the bubble, your reply doesn’t go unnoticed: a red badge counts unread messages on the bubble, the bubble wiggles and a discreet sound plays (browsers only play a sound after the visitor has interacted with the page).
Message translation
You and your visitor each write in your own language.
- By default, messages written in another language than yours arrive already translated into your language, with See original to read them as written. The visitor gets your replies translated the same way, in their bubble’s language.
- To turn translation off: the Always translate switch at the top of the conversation for you, the translate button at the top of the bubble for the visitor. The choice stays on the device. Turned off, translation is one tap away: Translate under each message.
- A message’s language is the visitor’s bubble language, or yours for your replies; translating corrects it when it is wrong.
- Only text is translated, not attachments. Inbox previews and notifications stay in the original language.
AI agent
On the Creator and Studio plans, an AI agent answers visitors in the bubble, based on what your site says, and hands over to your team when needed.
- Open Sites, your site, then AI agent, and give one address: your site, its
sitemap.xmlor a Google Merchant product feed. It reads the useful pages (FAQ, shipping, returns, contact…), and the catalog of a Shopify, WooCommerce or PrestaShop shop (with the Hooky module), detected on its own. It reads the address again every night. - No Shopify or WooCommerce shop, or an incomplete catalog? Attach a product file (CSV or Excel, up to 5 MB and 2,000 products): it replaces the catalog read online.
- Add your instructions (opening hours, shipping, returns…): they win over the site.
- Try it in the test area, then turn it on.
- The visitor can see they are talking to an AI assistant and can tap Talk to a human at any time. The agent also hands over on its own (an answer it doesn’t have, an order, a refund, a complaint…), when the quota is reached or if something fails.
- While the agent is answering, your team isn’t notified. When it hands over to a human, the conversation becomes unread again, with a notification and a reminder email. As soon as your team replies, the agent stays silent in that conversation.
- Its replies can be rich: up to 3 product cards (picture, name, price, stock and a View button, only products from your catalog), a button to a page of your site, and up to 4 quick replies the visitor taps instead of typing. The agent understands the tapped choice and carries on. Pictures come from Shopify, WooCommerce, Google Merchant or an “image” column in your file. Taps on View count in your stats (
agent_product_click). - Quotas per account: 1,000 replies a month (Creator), 5,000 (Studio), tests included.
All the details: The AI agent.
Team and plans
An account groups your sites, their conversations, their stats and your team. You can belong to several accounts and switch between them.
| Role | Can |
|---|---|
| Owner | Everything, including the subscription and deleting the account. |
| Admin | All sites: manage them, see the secret key and API keys, invite the team. |
| Member | The sites given to them: reply and see stats, without editing anything. |
Invite people with a single-use link, valid for 7 days, from Team.
| Plan | Sites | People | Price |
|---|---|---|---|
| Free | 1 | 1 | €0 |
| Creator | 10 | 1 | €9 / month |
| Studio | 50 | 5 | €29 / month |
Every plan includes the bubble, stats, several addresses per site and the API; the AI agent is reserved for paid plans: 1,000 replies per month with Creator, 5,000 with Studio. Subscribe on the web, by card with Stripe, in Subscription, or in the app, through the App Store or Google Play, at the same price: one subscription per account. A year costs ten months (€90 or €290).
Data and privacy
- The bubble sets no cookies. It keeps the visitor’s conversation token in the site’s
localStorage, to find the conversation again on their next visit. - It lives in a Shadow DOM: your site’s styles don’t distort it, and it doesn’t touch yours.
- Stats don’t track anyone: they count the events you send, with no visitor identifier.
Hooky.identifyandHooky.setAttributesonly send what your page gives them. This data stays with the conversation, visible to your team only.
For AIs
These docs also exist in Markdown, a format AIs read directly:
heyhooky.com/llms.txt: the essentials, and the links.heyhooky.com/llms-full.txt: the full docs, in one piece.
Give one of these addresses to Claude, ChatGPT or Codex: “Read heyhooky.com/llms.txt, create a Hooky account for me and install the bubble on my site.” Soon, an MCP server will let Claude Code, Codex or Cursor install Hooky by themselves.