Agent Orchestrator - the new AI agent module

Everyone has an AI agent demo. Almost nobody has one you can safely let into a real business — real data, real processes, real customer money. A demo runs in a sandbox; production runs on your permissions, audit trail, and liability. Agent Orchestrator closes that gap — out of the box with Open Mercato Enterprise.

FLEXIBLE RUNTIMES

Run your agent where you already run

No walled garden. Pick the runtime that fits your stack. Your agent, your environment. We adapt to it — not the other way around.

self-hosted

OpenCode

Runs inside your Open Mercato Docker container.

Vercel AI SDK

In-process

Lightweight agents, no extra infrastructure.

A2A protocol

Cloud runtimes

Azure AI Foundry, Google, Amazon and others via one connector.

start with 80%
NATIVE WORKFLOW INTEGRATION

An agent becomes a function in your workflow

The Agent Orchestrator plugs into Open Mercato Workflows through a new node — Invoke Agent. No glue code, no separate integration project.

Pass context

The workflow hands the agent a well-defined context.

It does the work

The agent runs as any other function.

Workflow waits

It resumes on the agent's response.

PRODUCTION CONTROLS

Two controls make it production-grade

Confidence thresholds

>80% → auto
<80% → human

Set the bar. Above your threshold the agent decides and the workflow moves on. Below it, the decision escalates to a person. You decide how much autonomy you hand over.

Human-in-the-loop

>80% → auto
<80% → human

When output needs sign-off, the workflow stops and routes it to the right person.
The agent proposes, the human disposes.

Runs on top of the Open Mercato MCP Server — the tools you already expose are discoverable and callable by agents. No new tooling to wire up.

TWO-LAYER AUDIT

Trust, because you can see everything

Most platforms ask you to take their word for it. We log instead. Every agent action is audited exactly like a human action — a data change by an agent is traced the same way as one made by a person. Nothing off the record.

01
Autonomous action - a clean agent-level record.
02
Person-triggered action - both the agent and the person who set it in motion.

You always know what the agent did — and who put it to work. For regulated buyers, that's the price of entry.

EVALS & OBSERVABILITY

Stop guessing whether your agent is any good

Agent Evals

define
benchmark

You don't ship code without tests. Define evaluation scenarios, benchmark your agents against them, and watch how they hold up on real cases — in the same place they run.

Observability

models
cost
performance

See which model an agent used, what it cost in tokens, and how it performs over time. Admins and AgentOps teams tune behavior with real numbers.

WHY IT'S DIFFERENT

How is this different from n8n?

Fair question — people ask it first.

The difference between automating a step and trusting an actor.

What an agent is
How it runs
Relationship

In n8n

Another node that calls an API
Fires a request, hopes for the best
Bolted on, outside your system

In Open Mercato

A supervised participant in the process
Runs inside your data, permissions and audit
Governed, native to the platform
ONE COHERENT LAYER

One layer, not three features

Runtimes, workflow integration, audit, evals — not four separate things. One coherent layer, start to finish.

01

Create

Define an agent, its tools and the runtime it runs on.

02

Run

As a standalone function or as a step inside a workflow.

03

Trace

Every action audited, two layers deep — agent and person.

04

Understand

Model, token cost and performance, all in one place.

05

Benchmark

Run evals against real-world scenarios.

AI agents spent two years doing impressive demos. This is the boring, hard part nobody screenshots — getting them safely into production.

Software is about to be built
completely differently.

Start with 80% done.
$ git clone https://github.com/open-mercato/open-mercato.git
Clone the Repo