Expert catalog

Five Etch SDK experts are registered in this demo. Each exposes one tool to Etch and streams a full reasoning trace while calling GLC microservices.

Order Status Inquiry

Customer support · 4 tool calls · ~1s

Parses messy customer emails for order UUIDs or email addresses, looks up GLC orders and event timelines, fetches customer profiles, and drafts a support reply grounded in live data.

Try: “Was my package delivered? My email is [email protected]

Full trace →

Supplier Invoice 3-Way Match

Accounts payable · 6 tool calls · ~0.1s

Loads a supplier invoice, purchase order, and receiving record from GLC AP services. Compares quantities and amounts line-by-line, flags variances, and returns a match verdict with audit notes.

Try: “Run a three-way match on supplier invoice INV-000001”

Full trace →

Procure-to-Pay

Procurement + AP · 14 tool calls · ~0.4s

Scans SKUs below reorder point, drafts purchase orders, reviews receiving exceptions, and three-way matches open invoices — a cross-functional workflow in one deterministic pass.

Try: “Run procure-to-pay: scan below reorder, draft POs, review receiving exceptions…”

Full trace →

Morning Ops Brief

Cross-functional ops · scales with max_cases

Aggregates order exceptions, AP signals, procurement alerts, and optional customer escalations into a prioritized action plan. Tool count grows linearly with cases scanned — use quick pill “Operations” or pass a customer email.

Try: Morning ops brief quick pill (includes Quinn Martinez escalation).

Sales

Revenue analytics · 4+ tool calls · ~1s

Company KPIs, top SKUs and states, promotions, customer history, product/stock lookup, and margin analysis over sampled order pages. Handles focused SKU queries without redundant KPI fetches.

Try: “Top products last 30 days with margin analysis — sample 5 pages”

Full trace →

How Etch invokes experts

Each expert registers as a single function tool on Etch’s agent. Etch’s system prompt describes when to use which expert. The expert runs synchronously from Etch’s perspective but streams progress events to the browser (tokens, tool count, elapsed ms) while it executes.

Read captured runs in Example traces, or compare economics in Determinism vs LLMs.