1. Create an account
One Zoe account — for the console and every bot you build. Already have one? Sign in on the same screen.
For developers · ZoeBot by WISHGOODS
A smart assistant on your site — in one line
Create an account, describe your product in the console, paste one install line. You do not build an AI system, an orchestrator, memory or a chat UI — that is ours. What you write is who the bot is and what it helps with.
- No backend
- No build step
- Half an hour
- 560 free messages a month
See it in action
From the console to the assistant on your site — a short look at ZoeBot in the real workflow.
WISHGOODS console
● ONLINEWhy this is not another widget
Most widgets take documents and answer from them. ZoeBot takes your product’s world — and, if you want, the ability to act in it.
A bot that only talks is a whole product
Write who the bot is, what it helps with and what it knows about your product — that is it, it works. A tool contract is an upgrade you add when you want it to take actions, not a condition of entry.
Your data stays yours
We do not import your database and do not hold a copy that goes stale. When a record is needed, Zoe calls your endpoint and it arrives live.
Actions go through a policy layer
For each tool you declare what it does: read, write or delete. Reads run on their own; anything with a side effect goes to approval. An unclassified tool counts as an action — the default is always the stricter one.
Your persona, our identity anchor
You set the name, the tone, what it helps with and what it declines. What you cannot set: that it denies being an AI or claims to be a person. A persona can narrow the bot, never widen it.
Four steps
All of it in the console. The only thing that enters your code is the line in step 4.
2. Register an application
Like creating an application to connect OAuth — except here the details you fill in are the personalisation itself. A name, an id, and the application exists with an isolated domain of its own.
3. Describe your product
What your product does, what the bot helps with, the knowledge it may quote (terms, policies, FAQ), how it sounds and what it should decline. The more precise this is, the more often the bot is right — and the less it invents.
4. Paste it into your site
Copy the publishable key and paste one line. The launcher appears in the corner, the conversation is remembered, and answers stream word by word. No server of yours, no build step.
HTML
<script src="https://jarvis-935d.onrender.com/api/zoebot/embed.js"
data-key="zk_pk_your_key"></script>Want the bot to take actions too? Add a tool contract in the console and point it at your endpoint. That can come later.
What keeps customers apart
A visitor on your site is not a Zoe user and cannot become one. These boundaries are enforced in code, not in a prompt.
Identity is derived, never supplied
The browser never names who it is. The visitor id is generated by us and only ever returns inside a signed token, so one application cannot name another’s user — impossible rather than merely forbidden.
The publishable key is not a key to conversations
It is visible in your page source and that is fine: it can start a new anonymous conversation and nothing else. It cannot reach an existing one and cannot claim a role inside your domain.
The secret never reaches the browser
Your secret key stays on your server and is only used to mint a token for a user you have identified. The console will not hand one out in a web page under any circumstances.
The address is re-checked on every call
Your endpoint is resolved again at call time, not only at registration — a hostname that resolves publicly today can point at an internal address tomorrow.
Text from your site is material, not instruction
Product knowledge is read and quoted, never obeyed. A document with “ignore previous instructions” pasted into it is text, not a command.
Your business rules are enforced by you
We enforce authority and effect; your endpoint enforces its own rules. Only the system holding the invoices can decide a project may not be closed while one is open — and a refusal from there is a legitimate outcome the bot knows how to handle.
Where this stands — honestly
What works, works. What does not is written here rather than hidden, because you would find out on day one anyway.
- Working: the console, sign-up, applications, persona, product knowledge, tool contracts, approvals, per-application isolation, and signed calls to your endpoint.
- Working: the client library — launcher, chat panel, streaming answers, remembered conversations, mobile and Hebrew. One script tag, no dependencies, no build.
- Working: sandbox mode — you can talk to the bot before writing a line on your server.
- Working: usage billing — one credit per message, on your Zoe account, with an automatic refund on a message that failed.
- Not yet: invoicing and developer-specific bundles. Today it draws on the Zoe plan you already have.
- Not yet: a bot that starts conversations on its own inside your domain. It answers and acts; it does not yet reach out.
- Early access: we would like to talk before you build something large on this.
Questions
Do I have to define tools?
No. A persona-only bot is the ordinary case and it works: it talks, remembers the conversation, and knows what you wrote about your product. Tools add the ability to take actions — an upgrade you can add whenever you want, without creating a new bot.
Do I need my own server?
Not to start. The publishable key opens conversations straight from the browser. A server is needed for two things only: if you want the bot to recognise your signed-in user, and if you want it to take actions in your system.
Do you store my data?
Not your records. We store what you configured — persona, product knowledge, tool contract — and the conversations that happened, isolated per application and per user. The records themselves stay with you and arrive on a live call.
What happens when the bot wants to do something dangerous?
It depends on the effect you declared. Read runs on its own. Write and delete go to approval. A tool we could not classify counts as an action — the default is always the stricter one.
Can I try it without building an endpoint?
Yes. Sandbox mode gives you a demo domain with projects, tasks, blockers and invoices — including cases that need two sources crossed. It is how you see whether the reasoning works before you invest.
What does it cost?
One credit per bot message — half what a full Zoe turn costs, because the bot carries a smaller prompt. It is charged to your Zoe account, never to your users, and a failed message is refunded automatically. The free plan covers 560 messages a month; Basic 1,000; Pro 5,000; Max 20,000. The price is deliberately low in early access, at our expense — it will change, and we will say so first.
Do my users need an account, or pay?
No. A visitor on your site opens a conversation with no account and no payment — they are not even a billing entity here. What they use is charged to the application they arrived through, and from there to your account.
Is this the same as Zoe for Business?
No. Zoe for Business is Zoe running inside an organisation’s boundary. ZoeBot is putting an assistant inside a product you are building, for your users.
Your first bot — now
Create an account, describe your product, paste one line. No account yet? You can open one on the same screen.