Build on The Spine

Every account, deal, order, pick, and ticket in Omnox already lives in one shared record — we call it The Spine — and there are two real, working ways to reach it from outside the product: an MCP server and a REST API.

Let AI agents act on your data directly

Omnox runs a real Model Context Protocol server — the same one that powers Assist, the in-app AI help agent. It exposes 116 distinct tools that read and write straight into CRM and warehouse operations: pipeline and deal data, support tickets, pick waves and inventory, dock and labor metrics, projects, dispatch routes, automation workflows, and more. Point Claude (or any MCP client) at it and an agent can query live state or take action, instead of working from a stale export.

A small sample of 116 tools total — not an exhaustive list.

A plain HTTP API sits underneath

Underneath the MCP layer is a real REST API — the same one the product itself runs on, organized by resource (accounts, contacts, deals, tickets, and more). Requests authenticate with a scoped API key sent via an X-AMPL-API-Key header, so a key can be limited to read access, write access, or scoped further per product area.

We're being direct about where this stands: it's a beta-stage API, built to run the product first and opened up second. It's genuinely useful today, but treat it as evolving rather than a frozen contract.

Docs are still catching up to the code

There's no published docs site or SDK yet — both the MCP tool surface and the REST API are still moving as the product does, and we'd rather be honest about that than point you at documentation that's already out of date. If you're building something on either one, the fastest path right now is talking to us directly: we'll walk you through the tools, help you scope an API key, and hear what you actually need from either surface.