What actually runs where. Useful if you're deciding whether to depend on this API, debugging something unexpected, or just curious.
| Domain / path | What it is |
|---|---|
| www.israelgpt.site | The main site: web chat and docs. |
| www.israelgpt.site/api/v1/chat/completions, /models | The OpenAI-compatible API (the base URL is .../api/v1; .../v1 works too). |
| www.israelgpt.site/api/v1/chat | The native API, with personas. |
| www.israelgpt.site/dashboard | Your API keys and their request logs. |
| www.israelgpt.site/docs | This documentation. |
Always use www.israelgpt.site. No other hostname is supported.
| Service | Role |
|---|---|
| Hosting and security provider | Hosts everything: the site, the API worker, rate limiting and the database. There is no other hosting, database or cache provider. |
| Model hosting | IsraelBot 1 is our own model, trained and tuned in-house (see Personas & Models). YahooBot 1 is a fine-tuned DeepSeek V4, served through OpenRouter. Only the API worker talks to either. |
| Discord | Only relevant if you use or fork the reference Discord bot (see Discord Bot). It runs as a separate process outside this stack. |
sig).502. There is no switch to a different model. See Errors.www.israelgpt.site.The OpenAI-compatible endpoint streams: yahoobot-1's reply is passed on as the model writes it, in OpenAI's event format, with small batches about ten times a second to stay inside the hosting plan's CPU budget. israelbot-1's reply is finished first so it can be checked as a whole, then sent as a stream.
The native endpoint doesn't stream, on purpose: the reference client (a Discord bot) posts one finished message rather than editing it token-by-token, and a plain JSON contract keeps onboarding to a curl command and a 10-line snippet.
// native /chat: one response, once generation finishes
const data = await res.json();
console.log(data.reply);