An account holds your API key, your projects, and everything the engine has established in them.
Four steps, one terminal. The last one shows you the engine's actual decision — including why it stayed quiet, which no other API will tell you.
loading…
Treat it like a password: it can create projects and read everything in them. Keep it on a server, never in a browser or a public repo. For a server that should only reach one project, mint a gw_proj_ key with project keys.
A project is one group's shared context — its items, members and memory. Everything below is personalised to the one you pick.
Two contributions from two people — the minimum the engine will ever connect. Paste into a terminal; the ids are already yours.
loading…
Analysis starts on its own about three seconds after the last item lands. Nothing else to call.
A finding if two pieces of work added up to something; otherwise the recorded reason it stayed silent. Silence with a reason is the system working.
The same answer, from the terminal:
Replace it. The old key stops working immediately, and any Buzz community you have connected reconnects with the new one automatically.
Anything else using the old key — your own scripts, another server — stops working until you paste the new key there.