Orbox
Waitlist
For developers and automation agencies

The process is described. You build it.

The company describes the process in Orbox, and Orbox breaks it into steps with an owner, tool, input and output. Whether you build for your own company or for a client, connect Claude, Codex or another AI agent and automate one step after another.

Get startedConnect your AI agent
claude · connected to Orbox
> Take the next step from the “Invoice processing” process and automate it.● orbox · next_step("invoice-processing")Step 3/9: Check against the purchase order (Xero)Takes: data extracted with AI, step 2Hands off: Slack (approval) or Asana (mismatch)● Writing the check and tests from the brief…✓ orbox · complete_step(3) — done, 4 tests passed

Three steps. Zero back-and-forth.

Stop piecing requirements together from email threads and meetings. The work arrives already scoped.

  1. Your client or team explains the process

    They walk Orbox through how the work gets done. Orbox digs into the exceptions, rules and ownership, so you don’t have to.

    Description · Processing incoming invoices

    Invoices arrive in Gmail, accounting checks them in Xero and the manager approves them in Slack.

    Reply to Orbox…

  2. Orbox breaks it into steps

    The conversation becomes a structured process. Every step has an input, an output, its rules and the systems it touches.

    Clarifying · Processing incoming invoices
    1. 1
      Receive invoiceGmail
    2. 2
      Accounting checkXero
    3. 3
      Manager approvalSlack

    Writing up the steps…

  3. You ship it, step by step

    Connect Claude, Codex or another AI agent to Orbox. Your agent picks up the next step with full context, automates it and marks it done.

    Automation · Processing incoming invoices
    1. 1
      Receive invoice
      Gmail
    2. 2
      Accounting check
      Xero
    3. 3
      Manager approval
      Slack

    0 of 3 steps run automatically

Step 3 of 9 · Check against the purchase order

Check against the purchase order

Ready to automate
Takes
Data extracted with AI: supplier, amount, order number
Does
Compares the invoice with the purchase order in Xero
Hands off
Matches → approval in Slack. Does not match → task in Asana
Rule
Price deviation over 2 % from the order = mismatch
Exception
Invoice without an order number → always a task for accounting
Owner
Accountant

What you get

Every step is specced so you and Claude can start building right away.

  • A clear spec for every step

    Input, output, rules and exceptions. Everything you’d otherwise have to chase down.

  • Full-process context

    Claude sees what comes before and after each step, so everything fits together.

  • Shared visibility

    Every step has a status. Your client sees what’s automated; you know what’s next.

Connect your agent. Sign in, no token to copy.

Connect Claude, Codex or ChatGPT by signing in through the browser; other MCP clients with an API token. The example below is for Claude Code. Then just tell your agent which process to work on.

1. Add Orbox to Claude Code and sign in

terminal
claude mcp add --transport http --scope user orbox https://orbox.dev/api/mcp
# then in Claude Code: /mcp → orbox → Authenticate

Sign in to Orbox in the browser and pick Read and write if the agent should edit processes, or Read only.

Codex, ChatGPT, Claude in the browser and tokens for CI

2. Tell your agent what to build

claude
Take the next step in the
“Invoice processing” process and automate it.

What your agent can do in Orbox

Full tool list

  • Read

    Searches and reads processes, steps, entities and the catalog.

  • Write

    Creates and edits process drafts, steps, flow and entities.

  • Batch edits

    Writes a whole process or an initial catalog in a single call.

  • Submit

    Submits or archives a process. Every change lands in the version history.

Install the orbox-process skill with one command from github.com/ordexai/orbox-skills.

For integrations from your own systems there is a REST API v1 with an OpenAPI spec: orbox.dev/api/v1/docs.

For automation agencies and freelancers

Building for clients?

You work in Orbox exactly like an in-house developer. The Partner program adds the business side on top.

Partner programProgram terms
Less unpaid discovery
The client describes the process on their own. You start from a finished step-by-step description.
Scope priced per step
Every step is priced on its own, and the version history shows who changed what.
20 % of every payment
From customers who sign up through your link, for as long as they pay.

Questions, answered

  • Who describes the process in Orbox?

    Your client: a manager, the owner or whoever actually does the work. Orbox talks it through with them and writes it up. You get a finished spec, already broken into steps.

  • Do I have to automate the whole process at once?

    No, and that’s the point of steps. Automate one, verify it, move on to the next. Steps that should stay with a person simply stay that way.

  • Does Orbox touch my code or my client’s systems?

    Never. Orbox holds the spec and the status of each step. You write the code with Claude, in your own environment and tools.

  • How does my agent sign in to Orbox?

    Claude, Codex and ChatGPT connect over OAuth: you sign in with your Orbox account in the browser and choose read-only or read/write. The agent acts as you, sees only what you see, and the connection lasts 90 days. Scripts and CI use a personal API token instead.

  • What happens when the process changes?

    Your client updates it in Orbox. You and Claude see exactly which steps changed and what needs revisiting.

  • Can I bring Orbox to my clients?

    Yes. Invite them and let them describe the process themselves. You skip the kickoff meetings and get a more accurate spec.

Your next spec, already broken into steps

Create an account, let your team or your client describe the process, and build from the finished steps.

Get startedSee it from the client’s side