Reactor documentation

Your customers ask. Your loop answers, acts, and tells you what matters. plutonium.io Reactor runs AI agents for your business, on your site and in your tools, around the clock. You say what the loop should do. We run it safely, on a budget you set, and everything it collects is yours. 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.

Reactor loop

Start here

• Getting Started — from signing in to your first run
• Core Concepts — loops, versions, runs, subjects, gates, budgets and deliveries

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, or from your server
• Identity and Keys — who a loop’s user is, which sites may load it, and the API keys your server uses
• 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

Reactor search

• 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