Choose your surface
Every surface is a view of the same state layer. Pick by how you work; mix freely. Sellers and buyers each get the full set.
| Surface | Best for | Sellers | Buyers |
|---|---|---|---|
| Web app | Human order desk, catalog console, approval queue | ✓ | ✓ |
| REST API | Your own systems and agents | ✓ | ✓ |
| MCP server | LLM agents (Claude, or any MCP client) | ✓ | ✓ |
| CLI | Scripts, ops, quick checks | ✓ | ✓ |
| Webhooks | Reacting to state changes | ✓ | ✓ |
| Files (S3/SFTP) | Catalogs, rates, and avails by drop; order exports | ✓ | |
| Your own API (we call it) | Sellers who already run order and inventory systems: host the endpoints, VAMOS pulls | ✓ | |
| Shared queue (SQS) | Event delivery without a public endpoint | ✓ | ✓ |
| Email gateway | Authorized senders: structured orders and files in, decisions and confirmations out | ✓ | ✓ |
| EDI (agency and traffic systems) | Confirmed orders delivered into agency systems of record (Prisma, Strata) on the industry's EDI rails; station-generated EDI invoices and as-run log times accepted from traffic systems and reconciled against orders | ✓ | ✓ |
If you never want to write code: sellers work entirely from a spreadsheet drop and the approval console, buyers from the order desk. If you want everything as software: the API and MCP server cover the full lifecycle on both sides. Where the line sits between the platform and the parties: Who does what.