How Giwaagent works

The console is a static page. When you talk to an agent, the request goes from your browser to the provider you chose. It does not pass through a machine we own, because there isn’t one in the path.

That is also the limitation: your key is in your browser, so an agent only runs while this tab is open. A relay that keeps them running is on the list and is honestly marked live.

Keys live in this browser’s local storage under one entry. They are sent to one place, the provider, and there is no copy anywhere else. Clearing them in the console or clearing site data removes them completely.

Anthropic is reachable from a browser because they publish a header for exactly that, anthropic-dangerous-direct-browser-access. The others accept a normal bearer token.

• Anthropic sk-ant-…
• OpenAI sk-…
• Groq gsk_…

An agent is a name, a brief and a model. The brief is the system prompt; it is sent with every message. Switching model mid-conversation is fine, and the last twenty turns go with each request so a long chat does not quietly become an expensive one.

GIWA Sepolia, chain id 91342, one second blocks. The RPC and the explorer both allow cross-origin reads, so the chain page reads it live with no key.

No Chainlink feeds are deployed on GIWA. Anything showing a token price on this chain today is showing an invention, so nothing here does.

The relay and on-chain payments are both written down and neither is built. They are labelled planned on every surface, read from one file, so they cannot quietly start sounding real.