Docs

Short and plain. If something here and the code disagree, the code in the public repository wins and this page has a bug.

Chat

Answers stream as they are written. The conversation is kept in your browser's IndexedDB and sent with each message, because this site remembers nothing between requests. The model has no web access and may be wrong, so answers are labelled as drafts.

• One message is capped at 4,000 characters. The last 16 messages go to the model.
• Three free uses a day per network where the site has a shared store. Without one, two, plus a smaller limit for the whole server.
• A chat message, a picture and an app draft each take one use. A request refused by the word list costs nothing. A use comes back only if the provider never accepted the call: a timeout, an error status or a model over the price limit. Once it accepts, the use is spent, even if the answer turns out empty.

Pictures

One sentence, one picture. It comes back as data inside the page, is stored in this browser with the chat, and can be saved or anchored. If the site has no picture model set, this says "not configured". Video is planned, not built.

Build and its sandbox

The model drafts one HTML file. It runs in an iframe with sandbox="allow-scripts" and srcdoc, without allow-same-origin, so the browser treats it as an unrelated origin: no cookies, no storage, no reach into this page or your wallet. A content security policy placed ahead of the draft's first byte shuts its network too.

Those walls exist only here. A file you download runs with none of them, so read it first. Hosted publishing and databases are planned.

Content rules

Refused in every mode, with no setting to turn it off: sexual content, anything suggestive involving minors, depicting or impersonating real people, malware, stealing credentials or wallets, and weapons meant to hurt people.

There are three layers: a word list on the server before any paid call, instructions the model cannot be talked out of on purpose, and a check of the stream as it arrives. Pictures also get a model-side reading of the request, and if that check fails the picture is refused. The finished picture itself is not checked by this site: the rules act on the words going in, and on any words sent back with it. None of these is perfect, and people can word around lists and steer a model, which is why the rules are stated plainly here.

Origin Book

A contract on Robinhood Chain with no owner, no fee and no funds. A wallet anchors a keccak256 hash with a kind, an optional name, an optional link and an optional parent for a remix.

• Versions. The author and named editors can add up to 256.
• Attest. Another wallet says it has seen a version, once, and can take that back. A wallet that was ever the author or an editor of the record cannot attest it.
• Handover. The author offers, the other wallet accepts, and until then nothing moves. The old author keeps no write access.
• Retire. Final. The record stays readable.

A record proves a wallet published a hash at a time. Anyone who has a file can hash it, so Verify lists every entry, oldest first. Names and links are public for good. This site hides any that break its content rules, but it cannot remove them from the chain.

Until the contract is deployed, every step runs in practice mode: same rules, signed as a message, kept in this browser, nothing sent. The ABI is at /contracts.json.

Questions and risks