Callable orchestrator — hires specialist agents on-chain, grades their work, delivers one vetted result
The Orchestrator Workflow. Request → Maestro Hires Specialists → Agents Work → Maestro Grades & Consolidates → Final Result Delivered.
Single agents fail at complex tasks because they lack specialized context and self-reflection. Managing a multi-agent system manually is cumbersome and non-scalable. Maestro solves this by acting as an autonomous orchestrator. It intelligently provisions the right specialist agents from the Constellation network, oversees their work, and distills their outputs into a single, high-fidelity result.
Key Features:
- ⚡ Autonomous Hiring: Automatically selects the best specialist agents for a specific prompt.
- 🔒 Quality Assurance: Integrates with grading agents to evaluate outputs before delivery.
- 🎨 Consolidated Outputs: Delivers a single, cohesive response instead of raw multi-agent logs.
- 🔄 Active State Recovery: Recovers and resumes pending pipeline executions upon startup if container restarts.
- ⚡ Fast Fallover Retry Bypass: Intercepts subcontractor rejections/expirations instantly, bypassing retry loops to cascade to backup providers.
- 💼 Dynamic Payout Wallet: Uses
MAESTRO_PAYOUT_ADDRESSto route fee revenues directly to custom cold storage.
Maestro is the hub of a multi-agent constellation. Every arrow below is a real CAP order settled in USDC on Base — escrow-backed, with automatic refunds on failure. This composition is impossible (or far worse) on a flat REST marketplace: there is no escrow, no on-chain provenance, and no way to refund a buyer when a sub-agent underperforms.
graph LR
User([Any Agent / User]) -->|hires| M[Maestro 🎼]
M -->|research| W[Worker 🛠]
M -->|self-correct retry| FW[Fallback Worker 🛠]
M -->|grade 0-100| L[Litmus 🧪]
M -->|human sign-off| S[Summon 👤]
G[Gauntlet 🧤] -.->|certifies| M
GL[Goldilocks 🧈] -.->|prices| M
classDef hot fill:#F59E0B,stroke:#111,color:#111,font-weight:bold;
class M hot;
- Depth: Maestro runs a cognitive reflection loop — if Litmus scores a draft below threshold, it re-hires a fallback Worker with the grader's critique, re-grades, then escalates to a human via Summon.
- Fiduciary refund: if quality stays critically low, Maestro autonomously refunds the buyer's escrow instead of delivering substandard work.
- One request → many CAP orders: a single pipeline run can generate 4–5 on-chain sub-orders across 3–4 distinct agents.
Real CAP orders settled in USDC during the hackathon. As the constellation hub, one Maestro request fans out into several sub-hires — so each run adds multiple rows.
Total real CAP orders: 6 · last updated: 2026-07-07 · one Navigator request → 5 autonomous sub-hires, incl. human-in-the-loop.
Topic: "Well-sourced research brief on zero-knowledge proofs in DAOs." Grade climbed 69 → 76 via a self-correction loop, then escalated to a human who approved. Each row is [pay tx] · [deliver tx] on Base Mainnet.
| # | Date | Role | Counterparty | USDC | Order ID | Tx (BaseScan) | Result |
|---|---|---|---|---|---|---|---|
| 1 | 2026-07-07 | Provider (paid) | Navigator | 1.00 | 98d0adae | pay · deliver | PDF brief delivered (human-approved) |
| 2 | 2026-07-07 | Requester (hired) | Worker | 0.10 | 82878d87 | pay · deliver | research draft |
| 3 | 2026-07-07 | Requester (hired) | Litmus 🧪 | 0.05 | 9da4458a | pay · deliver | score 69/100 |
| 4 | 2026-07-07 | Requester (hired) | Worker (fallback) | 0.10 | 9087342c | pay · deliver | self-correction re-research |
| 5 | 2026-07-07 | Requester (hired) | Litmus 🧪 | 0.05 | 3f72221e | pay · deliver | score 76/100 |
| 6 | 2026-07-07 | Requester (hired) | Summon 👤 | 0.05 | 9dc01628 | pay · deliver | ✅ human approved (Telegram) |
| Layer | Technology |
|---|---|
| Runtime | Node.js (TypeScript) |
| Ecosystem | Constellation A2A (croo-core) |
| Testing | Vitest |
Maestro builds on the shared @edycutjong/croo-core SDK. The methods it actually calls:
| Method | Source | Role in Maestro |
|---|---|---|
makeClient(sdkKey) | croo-core | Instantiates the shared CROO AgentClient (Base Mainnet config) from the SDK key. |
runProvider(...) | croo-core | Runs Maestro as an on-chain provider — subscribes to order/negotiation events and fulfils incoming hires. |
hire(...) | croo-core | Acts as a consumer — Maestro orchestrates by placing orders against other Constellation agents (A2A). |
isMockMode() | croo-core | Branches between offline mock mode and live on-chain execution. |
client.uploadFile(...) | @croo-network/sdk | Uploads the composed deliverable artifact. |
client.rejectOrder(...) | @croo-network/sdk | Declines an incoming order that fails policy checks. |
client.getNegotiation(id) | @croo-network/sdk | Reads negotiation/order state while orchestrating. |
Any agent can hire Maestro on-chain through croo-core's hire() primitive — it's live on the CROO Agent Store.
import{makeClient,hire}from'@edycutjong/croo-core';constclient=makeClient(process.env.CROO_SDK_KEY!);const{ delivery }=awaithire(client,{serviceId: '625f15c8-61ba-4b11-8201-0bb019ef5ef2',// Maestro on the CROO Agent Storerequirement: {topic: 'Write a vetted brief on Base L2 fee mechanics',qualityThreshold: 90,// optional — re-research until Litmus grade ≥ 90},maxPrice: 5.0,// Maestro sub-hires Worker/Litmus/Summon, so budget higher});delivery → { results, audit, totalSpent } (audit trail of every sub-order it placed)
- Node.js ≥ 20
- npm
- Clone:
git clone https://github.com/edycutjong/maestro.git - Enter the directory:
cd maestro - Install:
npm install - Configure:
cp .env.example .env.localand fill in your service IDs (skip for mock mode)
npm install
npm run demo # full Research → Grade → Human → Deliver pipeline, end-to-end# …or boot the live provider loop in mock mode:
CROO_MOCK=true npm run devnpm run demo exercises the real work() path against deterministic mock sub-agents — no funding required, perfect for reproducing the orchestration locally.
4-stage pipeline: Quality → Security → Build → Deploy Gate
# ── Code Quality ────────────────────────────
make lint # ESLint
make typecheck # TypeScript check
make test# Run tests
make test-coverage # Coverage report
make ci # Full quality gate# ── Security ────────────────────────────────
make security-scan # npm audit + license check| Layer | Tool | Status |
|---|---|---|
| Code Quality | ESLint + TypeScript | ✅ |
| Unit Testing | Vitest (65 tests) | ✅ |
| Security (SAST) | CodeQL | ✅ |
| Security (SCA) | Dependabot + npm audit | ✅ |
| Secret Scanning | TruffleHog | ✅ |
maestro/
├── docs/ # README assets (hero, screenshots)
├── src/ # Application source code
├── scripts/ # Build and run scripts
├── __tests__/ # Vitest test suites
├── .github/ # CI workflows
└── README.md # You are here
Containerized for any PaaS (Railway, Render, Fly.io, Cloud Run). Maestro is a background worker (connects out to the CROO WebSocket — no inbound port):
docker build -t maestro .
docker run --env-file .env.local maestroMIT © 2026 Edy Cu
Built for the DoraHacks CROO Hackathon 2026.