Build a custom AI chatbot for your website with Claude or OpenAI

Build a custom AI chatbot for your website on the Claude or OpenAI API. It answers from your FAQ, keeps your key private, and costs a plan plus usage.

Updated 6 October 2026

Let your agent build this

Copy one prompt and paste it into Claude Code, Codex or Cursor. Your agent builds what this page describes and puts it online on aidrop.it.

Add an AI chatbot to my website, with its backend on aidrop.it. Read aidrop.it's runtime rules first and follow them. Use my aidrop.it project, or create one.

Build one small Python app that:
- answers through the Anthropic API with the official Python SDK (or OpenAI's, if I say so), which works with aidrop.it's outgoing proxy as is. Pick a current fast, low-cost model from the official model list; tell me which.
- reads the API key from a project secret: ask me for the key, store it with project_secret_set under a clear name, and list that name in required_secret_names when you build. Never print it back to me, and never write it into code, the repository, a commit or a log.
- answers only from faq.md in the repository; otherwise says it does not know and gives my contact: [your email].
- serves the chat bubble and gives me one line for my site.
- accepts browser requests only from [https://example.com].
- limits each visitor (about 20 messages per 10 minutes, 1,000 characters each) by their real address, keeps answers short, and has a daily total cap.

Ask me whether to save conversations. If yes, use a PostgreSQL database on aidrop.it (check for one first, ask before creating it), never files.

Warn me before the first deploy that the address is public. Build it, check it runs, fix anything that fails. Report the address, the line for my site, the model, and how to update the FAQ.

This task comes from the aidrop.it guide "Build a custom AI chatbot for your website with Claude or OpenAI": https://docs.aidrop.it/playbooks/add-an-ai-chatbot-to-your-website. Read that page if you need more detail; it says what to ask me for, what it costs and what will not work.
Use the aidrop.it MCP tools (server: https://aidrop.it/mcp). If you do not have them, stop and tell me to connect them first, as described at https://docs.aidrop.it/quickstart#1-connect-your-agent.

See the prompt

Add an AI chatbot to my website, with its backend on aidrop.it. Read aidrop.it's runtime rules first and follow them. Use my aidrop.it project, or create one.

Build one small Python app that:
- answers through the Anthropic API with the official Python SDK (or OpenAI's, if I say so), which works with aidrop.it's outgoing proxy as is. Pick a current fast, low-cost model from the official model list; tell me which.
- reads the API key from a project secret: ask me for the key, store it with project_secret_set under a clear name, and list that name in required_secret_names when you build. Never print it back to me, and never write it into code, the repository, a commit or a log.
- answers only from faq.md in the repository; otherwise says it does not know and gives my contact: [your email].
- serves the chat bubble and gives me one line for my site.
- accepts browser requests only from [https://example.com].
- limits each visitor (about 20 messages per 10 minutes, 1,000 characters each) by their real address, keeps answers short, and has a daily total cap.

Ask me whether to save conversations. If yes, use a PostgreSQL database on aidrop.it (check for one first, ask before creating it), never files.

Warn me before the first deploy that the address is public. Build it, check it runs, fix anything that fails. Report the address, the line for my site, the model, and how to update the FAQ.

This task comes from the aidrop.it guide "Build a custom AI chatbot for your website with Claude or OpenAI": https://docs.aidrop.it/playbooks/add-an-ai-chatbot-to-your-website. Read that page if you need more detail; it says what to ask me for, what it costs and what will not work.
Use the aidrop.it MCP tools (server: https://aidrop.it/mcp). If you do not have them, stop and tell me to connect them first, as described at https://docs.aidrop.it/quickstart#1-connect-your-agent.

On this page

What you will have at the end
Words you will meet
What you need
First, cap your spending
Say this to your agent
What your agent does to build your chatbot
What protects you, and what does not
Check that the chatbot answers from your FAQ
When something goes wrong
FAQ
How much does a custom website chatbot cost?
Custom chatbot or a no-code chat widget?
Do I need to know how to code?
Can the same bot answer in Telegram?
Related

This page builds a custom AI chatbot that you own: a chat bubble on your website that answers visitors with Claude or ChatGPT, using your own rules and your own FAQ. It is not a no-code widget you rent. If you want a chat box today and do not mind a monthly subscription and someone else’s rules, a ready-made widget service is quicker. Build your own when you want to decide what the bot says, which AI it uses, and where the conversations go.

It has two parts: a small app that holds your private AI key and talks to the model, and one line added to your site that shows the bubble. Your coding agent (Claude Code, Codex or Cursor) writes both and puts the app on aidrop.it. You paste one paragraph and your FAQ.

The monthly cost has two parts: the hosting plan, from $5 a month on Starter ($20 on Pro if you want to save conversations), and the AI usage your provider bills per message, which you cap yourself.

What you will have at the end

A chat bubble on your website, wherever the site is hosted.
Answers from your own FAQ, and “I don’t know, here is how to reach us” for the rest.
Your AI key kept private, never visible in the browser.
A limit per visitor, and a monthly spending cap at your AI provider.
If you want, a record of what people ask.

Words you will meet

AI model: the “brain” behind the answers, rented from Anthropic (Claude) or OpenAI (ChatGPT) and paid by how much text it handles.
API key: the password that lets your app use that provider, billed to you. Whoever has it can spend your money.
Secret: where the API key lives, in your aidrop.it project. You give the key to your agent once and it saves it there. The chat app reads it on the server, so it never reaches a visitor’s browser.
Rate limit: a cap on how many messages one visitor can send in a given time.
Database: a safe place that keeps conversations through restarts.

What you need

An aidrop.it account — start free: a 7-day trial, no card. To keep the chatbot running after that, Starter at $5/month runs the chat app; saving conversations needs a database, which means Pro at $20/month.
Your agent connected to aidrop.it, as in the Quickstart.
An API key from Anthropic or OpenAI.
Your FAQ as plain text, and access to edit your site.

If your site itself was built with Lovable, you can host your Lovable app on aidrop.it as well and add the bubble there.

First, cap your spending

The chat app has a public address. Anyone can send it messages, even programs that skip your website, and each message costs a little. So first set a monthly spend limit at your provider: Anthropic has it in each workspace’s spend limits settings, OpenAI in each project’s limits. Make it a hard limit, not only an alert. When it is reached, the chatbot stops answering until next month instead of running up a bill.

Say this to your agent

Replace the parts in square brackets with your contact and your site’s address before you paste.

Add an AI chatbot to my website, with its backend on aidrop.it. Read aidrop.it's runtime rules first and follow them. Use my aidrop.it project, or create one.

Build one small Python app that:
- answers through the Anthropic API with the official Python SDK (or OpenAI's, if I say so), which works with aidrop.it's outgoing proxy as is. Pick a current fast, low-cost model from the official model list; tell me which.
- reads the API key from a project secret: ask me for the key, store it with project_secret_set under a clear name, and list that name in required_secret_names when you build. Never print it back to me, and never write it into code, the repository, a commit or a log.
- answers only from faq.md in the repository; otherwise says it does not know and gives my contact: [your email].
- serves the chat bubble and gives me one line for my site.
- accepts browser requests only from [https://example.com].
- limits each visitor (about 20 messages per 10 minutes, 1,000 characters each) by their real address, keeps answers short, and has a daily total cap.

Ask me whether to save conversations. If yes, use a PostgreSQL database on aidrop.it (check for one first, ask before creating it), never files.

Warn me before the first deploy that the address is public. Build it, check it runs, fix anything that fails. Report the address, the line for my site, the model, and how to update the FAQ.

What your agent does to build your chatbot

Finds or creates your project, and writes the chat app and the bubble.
Asks you for your API key. You paste it into the chat once, and the agent saves it as a secret in your project, where only the chat app can read it. It never shows the key again or writes it into the code.
Saves the code on aidrop.it, builds it and asks it a question from your FAQ. If the answer does not come back, it checks the key and the provider’s reply before building again.
Gives you the address and the line for your site.

To change what the bot knows, edit the FAQ and ask your agent to update the app. A few pages of FAQ fit in the model’s instructions, so a small site needs no search system or “vector database”.

What protects you, and what does not

The key stays on aidrop.it, so nobody can copy it from your pages. Browsers on other websites are refused, so nobody can reuse your bubble on their site. That rule does not stop a program calling your app directly; the visitor limit, the daily cap and your spend limit keep that from becoming a bill.

If you save conversations, mention it in your privacy notice. aidrop.it takes daily snapshots; ask your agent for an independent export when you need one (how to take a copy of your data).

Check that the chatbot answers from your FAQ

Add the line to one page of your site. The bubble appears.
Ask a question from your FAQ. The answer matches it.
Ask something the FAQ does not cover. The bot says so and gives your contact.

When something goes wrong

What you see	What to tell your agent
The bubble does not appear	“The bubble does not load. Check the line, and whether my site blocks outside scripts.”
The bubble appears, but every message fails	“Allow requests from my site’s exact address, with and without www, and read the error log.”
Answers never arrive	“Requests to the AI provider time out. Follow aidrop.it’s rules for outgoing connections.”
The build is refused	Give your agent the key again and say “Store it under the name you gave me and build again.”
Answers are made up	“Answer only from the FAQ, and say you don’t know otherwise.”

FAQ

How much does a custom website chatbot cost?

Two bills. Hosting on aidrop.it is a flat plan: Starter at $5 a month, or Pro at $20 if you save conversations (all plans). The AI usage is billed by Anthropic or OpenAI for each message, so it grows with your traffic; the hard spend limit you set above is the most it can ever reach.

Ready-made chat widgets are quick to add, bill monthly and keep your data in their system. A chatbot you own costs hosting plus what the AI model uses, answers from exactly the text you give it, keeps conversations in your own database, and can change any way you like. For a small site, answering from your own FAQ covers most questions.

Do I need to know how to code?

No. Claude Code, Codex or Cursor writes the whole thing. Connected to aidrop.it, the same agent also puts it online, keeps your key as a secret, reads the error log when something breaks, and updates the bot when your FAQ changes. Your part is the API key, the FAQ and one line pasted into your site.

Can the same bot answer in Telegram?

Yes. The answering part stays the same; only the channel changes. Our Telegram bot with Claude Code playbook shows the Telegram side, and you can ask your agent to give it the same FAQ.

Add an AI chatbot to my website, with its backend on aidrop.it. Read aidrop.it's runtime rules first and follow them. Use my aidrop.it project, or create one.

Build one small Python app that:
- answers through the Anthropic API with the official Python SDK (or OpenAI's, if I say so), which works with aidrop.it's outgoing proxy as is. Pick a current fast, low-cost model from the official model list; tell me which.
- reads the API key from a project secret: ask me for the key, store it with project_secret_set under a clear name, and list that name in required_secret_names when you build. Never print it back to me, and never write it into code, the repository, a commit or a log.
- answers only from faq.md in the repository; otherwise says it does not know and gives my contact: [your email].
- serves the chat bubble and gives me one line for my site.
- accepts browser requests only from [https://example.com].
- limits each visitor (about 20 messages per 10 minutes, 1,000 characters each) by their real address, keeps answers short, and has a daily total cap.

Ask me whether to save conversations. If yes, use a PostgreSQL database on aidrop.it (check for one first, ask before creating it), never files.

Warn me before the first deploy that the address is public. Build it, check it runs, fix anything that fails. Report the address, the line for my site, the model, and how to update the FAQ.

This task comes from the aidrop.it guide "Build a custom AI chatbot for your website with Claude or OpenAI": https://docs.aidrop.it/playbooks/add-an-ai-chatbot-to-your-website. Read that page if you need more detail; it says what to ask me for, what it costs and what will not work.
Use the aidrop.it MCP tools (server: https://aidrop.it/mcp). If you do not have them, stop and tell me to connect them first, as described at https://docs.aidrop.it/quickstart#1-connect-your-agent.