Loading…
Keys are issued by hand right now
Self-serve sign-up opens shortly. Until it does, tell us what you are building and we will send you a key the same day.
Ask for a key — one line about the problem is enough.
Or run it yourself today
The server is one container and it carries this same console, behind this same sign-in, at your own address. Nothing is held back from the self-hosted build.
docker run -p 8080:8080 \
-e HEBB_ACCOUNTS=1 \
-e HEBB_KEK="$(python -m hebb.serve.crypto --new-kek | tail -1)" \
-e HEBB_ADMIN_KEY="$(openssl rand -base64 32)" \
hebb-serveIt needs no GPU: reads where your application names the rule make no model call at all. The four endpoints are the whole API.
Sign in
One account, up to three API keys, and your usage in one place. No card.
This period
API keys 0 of 3
One for development, one for staging, one for production. Each one reaches the same memory. The key is shown once when it is created, because only its hash is kept.
| Key | Label | Last used |
|---|
New key
That is all three. Revoke one to free a slot — the limit counts live keys, not keys ever created.
Memories 0
Everything this account has taught the model. Nobody else can read it, and forgetting one returns a receipt reporting what was actually removed.
| Rule | Value | Version | Page | Updated |
|---|
Deletion receipt
The receipt reports the result of re-reading the page tensor and the store after the delete, not the intent to delete.
Ask
Name the rule and the stored value comes back exactly, with no model call. Leave it blank and the memory has to work out which rule you meant, which is the part still being improved.