Build on Vendu

Vendu exposes four seams. Which one you want depends on where your code needs to sit relative to a conversation.

The REST API

Read and write orders, products and conversations from your own systems. Authentication is an API key scoped to one workspace; every list endpoint is cursor-paginated.

Start with making your first API call. The full endpoint reference is generated from the OpenAPI specification and lives in the API reference.

Outbound webhooks

Vendu calls you when something happens — an order is created, a conversation is escalated to a human. Delivery is at-least-once, so every consumer must be idempotent: the same event will arrive twice eventually, and a handler that assumes otherwise will double-charge or double-ship.

See outbound webhooks for the event catalogue and payload shapes.

Apps

An app extends the agent itself rather than sitting beside it. An app can declare its own record types, give the agent new tools backed by your HTTPS endpoints, add domain knowledge to what the agent retrieves, and render its own screens inside the dashboard — all without a change to Vendu's core.

This is the seam to reach for when your case has its own nouns. See building an app.

MCP

Vendu is also an MCP server with OAuth and per-workspace scopes, so another AI agent can work with a workspace directly. Useful when the thing integrating with Vendu is itself an agent rather than a service.

What to read first

If you are integrating an existing system, start with the REST API and webhooks. If you are adding capability to the agent — a calculator, a lookup against your own data, a custom screen — start with apps.