chatagent.ca

Home · Guides · API Portal

How to use the LYGO API Portal

By Justin Helmer · updated 24 September 2026 · Free

On this page Two products Connect an API (this page) Browser agent tools Generate images (2 routes) Attach your own console Download the FULL local console If Connect fails Disclaimer

Two products — keep them separate

https://chatagent.ca/portal/ is an API portal. You bring a free or paid key. This domain does not host a GPU.

FULL local LYGO LLM Console is a download. Your GGUF models, folders, SkillHub FULL, USB CLAW. That kit is not this webpage.

Connect an API (3 steps)

  1. Open chatagent.ca/portal/. Default provider is Groq (free tier) — get a key at console.groq.com/keys.
  2. Paste the key. It stays in this browser tab. GitHub Pages never receives it.
  3. Click Connect, then chat.

Also in the list: OpenRouter, Gemini, Cerebras, Hugging Face, Mistral, NVIDIA NIM, Cohere, SambaNova, LLM7, Z.ai, DeepInfra, Hyperbolic, Novita, SiliconFlow, DeepSeek, Together, Fireworks, OpenAI, Anthropic, Perplexity, GitHub Models, or any OpenAI-compatible URL.

Free-key roundup (limits change): Groq, Google AI Studio, OpenRouter :free models, Cerebras, Hugging Face, Mistral Free, NVIDIA NIM, Cohere trial. Full table on the portal.

Browser agent tools

Skills and 15 Δ9 champions are already on the page. Toggle them on/off in the left rail (same idea as the local console). Visitors cannot install or download skills here — that is the bonus of the online portal. The model uses skill_list / skill_read on enabled items only. Soul / Identity / Memory files ship with the portal (editable in your browser).

After Connect, browser tools: Wikipedia, page fetch, weather, time, calc, SHA-256, HN, arXiv, GitHub search, Wayback. Geolocation and clipboard ask you first.

Save session as… and Save notepad as… write a file wherever you choose (File System Access, or a download). Load session restores a JSON you saved. Attach file puts text into this chat only — nothing is uploaded to chatagent.ca.

No server disks. No GGUF scan. That is the local kit.

Generate images — two routes, and they are labelled

Scroll to the Image generation suite at the bottom of the portal. Two routes, and the module says which one is answering:

  1. Your own key, in the tab. A picture-capable provider key you already have. Nothing is installed, nothing is sent to us, and the picture is displayed in the module. Vendors differ in price, quality, and whether they serve image models at all — so the module reports what it actually got back instead of pretending.
  2. Your own console's engine — no key, no per-picture limit. Run the LYGO console on your machine, start its public gateway, and attach this page to it. The picture is then drawn on your own hardware by the same engine the console uses, and the module shows the receipt: route, engine, checkpoint, steps, seconds, bytes.

What it costs in time, measured rather than guessed — CPU route, no graphics card, while the chat model was holding the card: SD 1.5 at 20 steps took 173.9 s for a 512×512 picture; a distilled 4-step checkpoint took 63.3 s. The engine has travelled inside the console since build 1.3.2 (PC and stick), so a machine with nothing installed can still draw — only the checkpoint is fetched, once, and its licence is shown with it.

Attach your own console (this is what the Modules list needs)

  1. Install the console: SkillHub — build 1.3.2, and boot it.
  2. Start its public gateway — PUBLIC_GATEWAY.bat in the kit (it listens on 127.0.0.1:9642).
  3. Open the portal attached to it: https://chatagent.ca/portal/?console=http://127.0.0.1:9642
  4. Chrome will ask whether this page may look for and connect to devices on your local network. Choose Allow. That prompt is the browser protecting you, not a fault: a public page may not call a program on your machine without your say-so, and when it is refused the failure arrives as a bare "Failed to fetch" that looks exactly like a console that is not running.

The left rail's Modules list then shows what that console offers this page — GGUF scan, folders, the image engine, SkillHub FULL. Anything marked needs your machine is running in your console, not in this tab. The console's own admin UI is on :9641 (PC) and :9651 (stick); the gateway is the address this public page talks to, and it is the one that carries the CORS and private-network headers.

Download the FULL local console

If you want models on your machine:

  1. SkillHub — FULL LYGO LLM kernel
  2. Docs: lygo-llm-console.html
  3. ClawHub map: @deepseekoracle/lygo-llm-console

Windows: unzip, run the BAT, Scan, Boot a GGUF. Admin USB is a separate steward channel.

Build 1.3.2 (September 2026) is the one to take: the picture engine ships inside it — PC and stick — so image generation works on a machine that has nothing else, and the SD 1.5 checkpoint its licence permits us to redistribute travels in the FULL and ALL-IN-ONE sets. Sizes, SHA-256 digests, and what each installer carries are on SkillHub.

The entrance, and turning the donation reminders off

On your first visit the portal covers itself with a one-time entrance: the Δ9Φ963 handshake, what the page is, and what it is not. Press Enter the portal and it does not come back (the click is remembered in that browser). To see the page with no intro at all, open https://chatagent.ca/portal/?intro=0.

The only thing that interrupts the portal is a donation reminder every 15 minutes. The portal is free either way — nothing is locked behind a code. If you would rather not see the reminder, supporters get a monthly code from the supporter post on Patreon. Press ⚿ Supporter in the top nav (or the door on the reminder card, or the button on the entrance) and the page takes you to the Supporter access module below the image suite — paste the code there and the reminders stay off in that browser. The panel tells you the date the code is good through; codes rotate every month, so the Patreon post always holds the current one, and a code stays valid through the 5th of the next month as a grace window. The code is checked inside your browser — the portal never sees it, and neither your keys nor your chats are involved.

Straight about the limits: a code turns the reminders off in one browser, it is a thank-you rather than a licence, and because the check runs in the page it is not a security boundary. Everything the portal does, it does for free, with or without a code.

If Connect fails

Many vendors block browser CORS. Try Groq or OpenRouter first. Or use the local console, which talks to llama.cpp on 127.0.0.1.

Two different failures look similar and are not. Vendor CORS: the provider refuses requests from any page that is not its own — switching provider fixes it. Local network access: a console route that never answers because the browser has not been given permission to reach your machine — the fix is the Allow prompt (above), and the console's own gateway answers the preflight that prompt depends on. The page now tells you which of the two it hit instead of blaming CORS for both.

Disclaimer

Open the API portal