Sign in
Open agents.london/civilization and sign in with Google or Microsoft — the same two doors as genome, through the same identity service. Your organisation and first project are created on arrival; the project tabs along the top switch between workspaces, and everything you do is scoped to the project you are standing in.
Playground — the one prompt surface
The Playground is where you talk to civilization. Give it a goal in plain words and watch it compose: a founder routes the request, a planner breaks it into stages, each stage is matched to a published agent, the pipeline is pinned, and then each agent runs on the output of the one before it — every step showing its real inputs, outputs, and timings. You can also run a single published agent directly, or stop a run mid-flight.
Runs are kept. The rail on the left holds every run for this project — click one to replay the whole thing (plan, agents, answer), start a new one, or delete it. (The old Chatbot was a thinner door onto a weaker engine and has been retired; this is the single surface now.)
The answer is the answer — but click How this was built and it opens into the combination that produced it: each agent as a node, each handoff as an A2A exchange, and every node expands to the exact context it received and the context it passed on. When a combination earns its keep, Save this combination as an agent catalogues it — a pipeline of agents becomes a pipeline of one, and it appears in the Agent Registry ready to be a stage inside the next, larger deal.
Discovery — describe a goal, get a team
In Discovery, describe a goal that needs more than one pair of hands — the platform proposes the multi-agent collaboration to meet it, drawing on the agents and tools in the registry. The Agent Graph view shows the resulting civilization as a living network: who exists, who talks to whom, and what flows between them.
Agents and tools
The Agent Registry holds the population: prime agents, genesis nodes, and the ontological registry that types them. From here you can materialize a new agent into a project. Registered agents can carry an ed25519 signing key — only a real, verifying signature earns the verified badge.
The Tools registry is the catalogue of capabilities agents may hold — register a tool once and any agent in the project can be granted it.
Combinations you catalogue from the Playground land here too, in their own section — each a whole pipeline kept as one reusable agent, with the handle it is invoked by.
Documents — the registry
The Documents view is your project's library. Upload a file or paste text; extraction and indexing run as a job you can watch, and large uploads stream — a 200MB PDF is handled incrementally, never held whole. Once indexed, a document is retrievable by every agent in the project, chunk by chunk, inside your organisation's own schema and no one else's.
Deleting a document means it: the catalogue entry is tombstoned and its chunks are removed. Quotas answer with numbers — how much you used, how much remains — never with a shrug.
Sessions and guardrails
Sessions is the shared memory of agent work: every revision recorded with the step that wrote it, so you can walk backwards from any answer to how it was made. Guardrails is the other half of trust: policy checks on what agents attempt, with violations blocked and audited rather than silently dropped.
Read the meter
Everything above lands on the same meter: 1 Consumption Unit per byte processed, a token counted as four bytes — ingestion, retrieval, and inference alike, written to an append-only ledger as it happens. Usage views show the month-to-date; when a quota is hit, the error names the numbers. What you did and what it cost are the same record.