Reactor documentation

You build the agent. We run it. Give an AI agent any job, from answering your customers to writing the Monday report. Describe it in plain words, or write it as a file. Reactor runs it, shows what every run costs, and keeps it inside the limits you set, whatever a customer types. We call each agent a loop, and each loop does one job. We run the loop. You own the data.

Reactor names a family of two products. Each works on its own, and they work together.

  • Reactor loop is loops as a service. You define a loop: what it is for, what it may read and call, and what each run may cost. Your users run it where you put it — a chat on your web page, or your own interface over the run API. The platform keeps every run inside the limits of the version you published, and shows you every run and every cent.
  • Reactor search makes your content searchable: a website, files you upload, or a collection’s records. You search it on the console, your visitors search it on your site, and your servers search it with a search key, with no loop at all.

Together: a loop can search your indexes, so it answers from your docs, your files or your records. See Letting a Loop Search.

Looking for something? Press / on any docs page, or press Search or ask over the page list. Search finds the pages that hold your words, and opens a result at its section. Ask is a loop that plutonium.io runs on these docs: it answers a question from these pages and names the page it used.

Reactor loop

Start here

Guides

  • Building a Loop — write a loop with LoopAssistant or by hand, try the draft, and publish it
  • Testing a Loop — try a draft on the bench, and the test cases that must pass before a version publishes
  • Agents — the workers a loop runs, their roles, and how to add your own
  • Tools — the built-in tools, and how to give your loops your own HTTP endpoints
  • Asking the User — questions, forms no model reads, email checks, and consent before the loop acts
  • Collections and Outputs — where a loop keeps its records, and where it sends a result when a run ends
  • Pages — markdown pages that show your collections, previewed as each reader sees them and published like a loop
  • Embedding the Chat — put a loop’s chat on your own web page, for anonymous visitors or for users your site signs in
  • Letting a Loop Search — name a search index in a loop, and let the loop’s visitors search it
  • Triggers and Schedules — start runs with no person: on a schedule, from a webhook, from a new record, from your server, or from your own machine
  • Identity and Keys — who a loop’s user is, which sites may load it, and the API keys your server uses
  • Connect an AI tool — work in your account from an AI tool that speaks MCP, such as Claude or Cursor
  • The Command Line — rxr: describe or write a loop, try it as you edit, test, publish and run it from a terminal, as a person or as an AI agent
  • Tools on Your Own Machine — let a loop read a file or run a command on your own machine, through rxr, and only what a file there allows
  • Operating Loops — watch runs, stop one, take over, answer the decisions a loop waits on, and read Metrics
  • Money, Limits and Members — the wallet and the four budgets, the limits on who may start runs, and the people in your account
  • Search Indexes — what Reactor search is; create an index from a crawl, your files or a collection, search it, and what it costs
  • Writing a Search — words, an exact phrase, a typo, a pattern, words or meaning, and what each searcher may send
  • Search API — search from your server with a search key, or through a loop

API reference

  • API Overview — the run API your server or page calls, how it authenticates, and what its limits answer
  • Identity — the doors that give one of your users a token
  • Runs — start a run, read it, talk to it and follow it
  • Search — search your indexes with a search key, or what a loop searches
  • Collections — read a collection’s records from your server
  • Webhooks — start a run with a signed request, and receive a loop’s outputs

For AI tools

A program can read this site as easily as a person can.

  • Markdown. Every page has a markdown form at its own address with .md added: this page is /docs.md, and the home page is /index.md. A request that sends Accept: text/markdown to a page’s own address gets the same markdown.
  • An index. /llms.txt lists every page with one line on what it holds. /llms-full.txt is the whole documentation in one file.
  • Your account. Connect an AI tool to work in your account from a tool that speaks MCP: draft, test, publish and run your loops. An agent in a terminal can use the command line, rxr, which has a --json output and a guide written for it.