Orchestrate API: Trigger a no-code automation with one HTTP request.
Start a saved automation by name and it runs on Chrome in our cloud. Pass input data, check status, pull run reports, cancel runs, query runtime used, all over REST.
1const api = (path) =>2 fetch(`https://lar.axiom.ai/api/v3/${path}`, {3 method: "POST",4 headers: { "Content-Type": "application/json" },5 body: JSON.stringify({6 key: process.env.AXIOM_API_KEY,7 name: "scrape-product-prices",8 }),9 }).then(r => r.json());10 11await api("trigger");12const { status, data } = await api("run-data");13console.log(status, data);What it runs
It runs saved bots, not scripts.
This layer runs the bots you built in the No-Code Tool and saved to your account. The steps, selectors, and logic stay in the automation, so none of the flow moves into your codebase.
Built in the No-Code Tool
Point and click the steps in the Chrome extension, save the automation to your account, then start it by name from the API.
Explore no-code
Edit the bot, not your code
Change what the automation does in the extension and the request that starts it stays the same. No redeploy on your side.
Explore code
Runs in our cloud
The browser is ours. The extension doesn't need to be open, and the machine that sent the request drops out once the run starts.
See infrastructure
Code is the layer below
This endpoint only starts bots that already exist. To write the steps yourself, the Step API gives you functions on a cloud browser and the Chrome API gives you raw CDP.
Explore the Step API
What it does
Trigger, watch, stop.
The endpoints all work on the name you gave the automation, so there are no session IDs or browser handles to keep track of.
Read the Orchestrate API docsTrigger by name
POST /trigger One POST starts any saved automation in the cloud, with input data in the request body.
Trigger an automation
Pass input data
POST /trigger Send rows in with the trigger and the automation runs against them, so one bot serves every set of inputs.
Pass input data
Check status and pull data
POST /run-data Poll a run for its current status and retrieve whatever it has written out.
Check run status
List run reports
POST /run-reports Pull the report for a past run: its status, timing, and the data it produced.
List run reports
List automations
POST /list-automations Fetch the automations on your account and their names, so you know exactly what to trigger.
List automations
Stop a run
POST /stop Cancel a run that's still going and free its concurrency slot for something else.
Stop a run
Webhooks from a step
A Trigger webhook step pushes data to your endpoint mid-run, so you hear about progress without polling.
Webhooks from a step
Docs
Every layer, documented.
Quickstarts, worked examples, and full endpoint references for each layer. Start with the quickstart, generate a key, and build from there.
Start with the quickstartGet an API key and try the Orchestrate API for free.
2 free hours of runtime. No card required.