Skip to content
opsveraopsvera
Agent library

Four agents we've built, and the pattern behind them.

These are examples, not a catalogue. Every engagement starts with your workflow — these show the shape of what we build and how far it goes into your systems.

Reference agents

Order intake
Demo available

PO → Order entry agent

Reads purchase orders arriving as email or scanned PDF, extracts the header and every line, creates the order in your OMS, and flags low-confidence fields for approval before anything posts.

PO → Order entry agent

watching ops@ · 3 in queue

purchasing@northline-trading.com

scanned · 2 pages · 412 KB

  • CustomerNorthline Trading Co.99%
  • PO numberNL-PO-447199%
  • Line items14 · 2,480 units97%

Held for approval

NetSuite · Sales ordersSO-118204 · draft
  • Outlook
  • NetSuite
  • Zoho
  • custom OMS
Accounts payable
Demo available

Invoice → PO matching agent

Matches incoming invoices against open POs on vendor, totals and line items. Clean matches post themselves; anything off routes to AP with the discrepancy shown side by side.

Invoice → PO matching agent

watching ap@ · 41 today

billing@harborfreight-lines.com

digital · 1 page · 96 KB

  • VendorHarbor Freight Linesmatch
  • PO referenceNL-PO-4402match
  • Total18,420.00 AEDmatch

Exception routed

QuickBooks · BillsBILL-7741 · on hold
  • Gmail
  • QuickBooks
  • Xero
  • SAP B1
Customer ops
Demo available

Shipment status auto-reply agent

Reads “where’s my order” emails however they’re phrased, looks up live status, and drafts a customer-ready reply. On-time answers can send unattended; delays always show a person first.

Shipment status auto-reply agent

watching support@ · 27 today

ops@midlandretail.co.uk

plain email · 1 thread

  • Intentorder status enquiry98%
  • Order ref8821399%
  • Current statusin transit · DXB → LHRlive

Draft ready

Outlook · support@RE: Any update on order 88213?
  • Outlook
  • Zendesk
  • carrier APIs
Cross-cutting
In every build

Exception routing agent

Not a separate product — the trust layer under the other three. You define what counts as an exception; it routes each one to a named owner with full context and a clock, instead of guessing quietly.

Exception routing agent

spanning 3 agents · 6 open

system · confidence monitor

live queue · 6 open

  • Short shipment→ warehouse leadhigh
  • Price variance >2%→ AP leadhigh
  • Unknown vendor→ procurementmed

Routed with context

Slack · #ops-exceptions6 open · oldest 22 min
  • Slack
  • Teams
  • email
  • your ticketing tool

Your workflow isn't on this list.

That's the normal case. The four above share the same ingestion, extraction, approval and audit core — pointing it at a new document type and a new system is the work, and it's measured in days.

Describe your workflow