Deep Chat without a server

Deep Chat can talk to an AI provider straight from the browser, but its docs say to do that only for demos, because the provider key ends up in the page. For a real site you are told to run a proxy server.

This is one file that connects Deep Chat to OneTag AI instead. The OneTag key is public by design: it only answers on the domains you registered it for, and it has a hard spending cap. So a static page is enough.

Live demo, served from GitHub Pages: https://fengyiqicoder.github.io/deepchat-onetag/

Use it

<deep-chat></deep-chat>

<script type="module" src="https://cdn.jsdelivr.net/npm/[email protected]/dist/deepChat.bundle.js"></script>
<script type="module">
  import { connectOneTag } from './onetag.js';
  connectOneTag(document.querySelector('deep-chat'), { key: 'ot_YOURKEY' });
</script>

On localhost you can leave the key out: a shared demo key answers there. Its small daily budget is shared by everyone, so use your own key on a live site.

Before you deploy, get your own key: enter your email at onetagai.com and the key is sent to you. No card is needed. The free plan is 1,000,000 tokens, one time, with no monthly reset.

Options

Option	What it does
key	Your OneTag AI key.
system	Instructions for the model, for example the tone or what the chat is about.
maxTokens	Longest answer, in tokens.

What works

• Streaming answers.
• Follow-up questions: earlier turns are sent as history, newest first, up to 24,000 characters.
• Errors from OneTag (quota used up, key not valid for this domain) are shown as they are.

What does not

• Files, images, audio and the camera. Only text is sent.
• Tool calling.

As a built-in service

upstream/ holds a patch for Deep Chat itself that adds OneTag AI to directConnection, next to the other services:

<deep-chat directConnection='{"oneTag": {"key": "ot_YOURKEY"}}' connect='{"stream": true}'></deep-chat>

It is not part of a Deep Chat release. A build with the patch runs at https://fengyiqicoder.github.io/deepchat-onetag/built-in/ and upstream/README.md says how to build and test it yourself.

Tested

Deep Chat 2.5.1 in Chrome, with canned answers for every case above, and one real question against the live service. The stop button is wired up but not tested. test/browser.mjs is the script; it needs playwright-core and the page served on port 4402.

The demo site is built by scripts/build-site.sh and checked by test/site.mjs, served on port 4404.