DOCS

How to build one,
and how to call one.

Two halves. The first is the machine as you meet it on the canvas; the second is the same machine driven from your own code. Every chapter is its own page, so a chapter is something you can send somebody.

This is a skeleton in the open: 144 of 144 sections are written, and the rest carry the outline they will be filled with rather than nothing. Everything in the API half that shows a route is real and verified against the live server.

Building a tron

What the thing is, and how it is put together on the canvas

  1. 01What a tron isA tron is one machine made of several models. It has agents, wiring between them, memory, and a place to put files, and it is the unit everything else in Vibetron is scoped to.
  2. 02The canvasWhere a tron is drawn. Agents are objects you pick up, wire and open.
  3. 03AgentsOne agent is one model with a soul, a set of tools, and a budget.
  4. 04GhostA check on an agent's own steps: n ghosts redo the same step of the model, one hunter says what the majority did, and a step that loses the vote is asked about, stopped or replaced.
  5. 05MemoryA memory belongs to the tron, and the agents wired to it use it — reading, or reading and writing. Five kinds; the platform keeps what they hold.
  6. 06Skills, plugins and serversThree different things an agent can be handed, each at a route of its own name.
  7. 07Libraries and documentsDrive → Library: collections of documents, indexed so that agents can search them and cite what they found.
  8. 08BridgesA tron reached from a chat app, an inbox or a phone number, and answering there.
  9. 09Privacy proxyPersonal data replaced with placeholders before a model provider sees it, images redacted by a redactor you run (one command, no open ports), and what it does not cover.
  10. 10ReferencesEvery name an agent can be given — keys, secrets and plain values — in one registry, with one order.
  11. 11Deploying and watchingA deployed tron is a real container. It has logs, a state, and a stop button.
  12. 12FilesOne workspace per tron: a working folder shared by every agent and by you.
  13. 13PublishingPutting a tron, a skill or a plugin in the public catalogue, and what goes out with it.
  14. 14Organizations, invitations and leavingHow people join a company, what happens to their trons when they leave, how a company is deleted, and how to take your data.
  15. 15Build a tron with a conversationDescribe what you need and the tron builder designs it with you: agents, models, memory and tools, checked against the catalogue, proposed as a tron you import with one click. It runs on your own keys.

The API

The same machine, driven from your own code

  1. 01AuthenticatingThere is no password. You prove an address, and the address is the account. Two calls, and the second is the only place a token comes from.
  2. 02TronsReading, creating and editing the machine itself.
  3. 03The .tron documentA tron as one JSON document: export it, check it, import it, change a tron from it, and pack everything into a zip. Never a secret, only the slots to fill.
  4. 04Deploy and runtimeBringing a tron up, seeing what it is doing, and putting it back down.
  5. 05Talking to a tronSending work in, and reading the answer as it is written.
  6. 06The Tron APIYour trons, called from your own code with a key: a message is a job, queued, which you read, follow, cancel or receive by webhook, with the files it produced and the shared folder of the tron.
  7. 07Memory and filesWhat an agent remembers, and what it has written down.
  8. 08ReferencesOne route writes an entry, by name, in one of five scopes.
  9. 09SchedulesWork that starts without anybody pressing anything.
  10. 10Errors and limitsWhat the server says when it refuses, and how to tell the kinds apart.
  11. 11Public API and MCPThe catalogue, the .tron schema, the writing guide and a validator, free and without an account: for anyone building a tron from outside Vibetron, from a script or from a chatbot.