Getting Started

This is the path an admin takes from an empty account to a loop that a user can run. Only admins sign in to Reactor. The people who run your loop never do — they meet it on your page or in your product.

Try one first

This is a loop that plutonium.io runs on these docs. Ask it a question: it answers from these pages and names the page it used. A loop you build meets your users the same way.

Not sure what to build? What Loops Are For lists the jobs a business hands a loop, with a person in the conversation or with nobody at all.

Reactor is not open for sign-up yet. Join the waitlist on the home page: we add people by hand, and we email you when your account is ready. You are its owner, and its wallet starts with $5.00 of starter credit. Then sign in to the console with Google, at the address we wrote to. The console opens on Home: your credit, what needs you, what is running, and this month against its budgets. A new account sees Getting started first: set up your first loop, then publish it. Each step ticks itself when it is done, and Hide puts the list away. Describe it in Chat opens Chat on LoopAssistant, a loop plutonium.io owns that helps you write your own. After your first publish, Home shows Your loop is live, with the code to put it on your site.

Each screen shows its title. Press the ? beside a title to read what that screen is for.

2. Add money to the wallet

Nothing runs until the account’s wallet holds money: every call a run makes is reserved against it first. A new account starts with its $5.00 of starter credit; an owner of the account adds more on Wallet & budgets. The same page shows what each loop has spent this month and the caps you set.

3. Describe the loop to LoopAssistant

Tell LoopAssistant what the loop is for. It interviews you and proposes the loop as a record you read and edit before anything runs — its instructions, the tools it may call, what it must produce, who may use it and what a run may cost. The model that drafts the loop never publishes it.

You can also start a loop yourself: Loops → New loop.

4. Know what a loop is built from

A loop does its work through parts you can see and manage on their own pages, in the Build group of the console:

Agents — the workers a loop runs: their instructions, the tools they may call, their model and their role. The console lists plutonium.io’s own agents beside the ones you create. Publishing a loop pins the agent version it uses.
Tools — your own HTTP endpoints. Install one once from a form, and several loops can declare it. A header secret you give it is stored and never shown again.
Collections — the records your loops write, collection by collection.
Indexes — what your loops can search: a crawl of a website, files you upload, or one of your collections. A loop’s page lists the indexes its runs may search, and an index that a published loop uses cannot be deleted.

5. Test it, then publish

A loop is written as a draft, and a draft never serves a user. Try it from Chat: a new conversation lets you pick the loop and the version it runs in, draft included. If the loop declares test conversations, the version publishes only after they have run against it.

Then publish the version. What you published is what runs, and it does not change afterwards: the next change is the next version. Publishing gives the loop its public id (pl_…), which is how the world outside the console names it.

6. Choose where it runs

A loop reaches users only through the deliveries it declares, and only from the web origins it allows. On Loops, a published loop’s Keys tab shows its public id, and what each delivery needs from you:

Embed — a chat on your own web page. For a loop that declares it, the Keys tab shows the snippet to paste.
API — your own server or interface calls the run API. Mint a key on the Keys tab with the create_runs scope; the key is shown once. See Runs in the API reference.

Keys are for owners. A key can do only what its scopes allow, and only within what the loop declares.

7. Watch it run

Runs shows every run live: who it was for, what it did, what it cost, and why it ended. You can stop any run from there. Metrics shows how each loop is doing for the version it publishes now: its runs, how they ended, what they cost and how long people waited.

Ask the Assistant

The Assistant answers questions about the console from these docs, and ends each answer with the address of each page it used. On a desktop it is a panel at the right of every screen; on a phone it is a sheet that opens over the bottom 60% of the screen. Press or drag its handle up to make it full screen, and drag it down to make it smaller or to hide it. It is open on Home. On any other screen, press Assistant at the bottom right. Hide closes it, and the console remembers that choice in this browser.

When the panel leaves too little room for a list and the item it opens side by side, the screen shows one at a time, as on a phone: press an item to open it, and the link above it (‹ Loops, ‹ Chats) returns to the list. Hide the Assistant to see both again.

Besides answering, it can do three things:

Take you to a screen. “Take me to Schedules” opens Schedules, and the Assistant stays open.
Point at a control. “Where is the publish button?” opens the screen and outlines the control for a few seconds. If the control is not on the screen now (Publish shows only on a loop that has a draft), it tells you what to do first.
Hand you to LoopAssistant. “I want a loop that qualifies leads” shows a card with a short brief of the loop you asked for. Press Open LoopAssistant with this brief, and a new chat opens on LoopAssistant with the brief in the box, for you to change; Not now leaves you where you are. Nothing is sent until you press Send. An agent you ask for goes to AgentAssistant the same way.

The Assistant reads nothing in your account: it knows these docs and where the console’s controls are. plutonium.io pays for its runs. Each member can start 60 conversations with it a day and send it 60 messages an hour.