> ## Documentation Index
> Fetch the complete documentation index at: https://vendo-mintlify-24213046.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.
# What is Vendo
> Your users build their own features inside your product: screens on their real data pinned into your pages, automations that run on a schedule, their own accounts connected — all through your own API, as them.
Vendo lets your users add new features to your product and customize it to how
they work. They describe what they want in plain language, and an agent builds
it inside your app — through your own API, as them.
A screen on their real data, pinned into one of your pages. A digest that runs
every Friday with nobody there. Their own Gmail or Slack, working inside your
product. They build these themselves, and they keep them.
Answering questions is the least of what it does.
## What it looks like
The path a request takes to get there is in
[how Vendo works](/product/how-it-works).
## Screens that stay
Ask for something to look at and the agent writes a screen instead of describing
one. It is a real React component running on live data from your own API, in
your fonts, colors, and radii.
The screen can stay. Put a slot in one of your pages and every finished screen
grows a button that puts it there. Press it and the screen holds that spot,
re-running on every open, so it opens on today's numbers.
`vendo init` reads your brand out of your app into `.vendo/theme.json`. Register
your own components and a screen renders your real UI, not the built-in kit.
## What they build from
Whatever a user builds is made of these three things.
One command reads your OpenAPI, tRPC, server actions, or routes and writes
the tool set everything runs on.
API tools →
Each user connects their own Gmail, Slack, or GitHub once, and later calls
run as them.
Connected accounts →
A user says when, and the same tools fire on a cron or an event.
Automations →
## It acts as the signed-in user
Every call runs inside your process, through your routes and your auth, carrying
the asking user's own identity. Vendo's servers never call your API. The agent's
hands are a fixed set, and a user can build only what they could already do by
clicking.
Reads go through. Writes and deletes stop and ask, quoting the exact request
rather than the tool's name, and every call writes an audit line either way.
## Start where you are
The embedded surface is the step after that, and `vendo init` asks which of
these you are doing and wires that one.
Vendo runs the loop and renders screens in your brand.
``
Quickstart →
Keep your loop. Vendo adds tools and renders the result.
`vendoTools(vendo)`
Quickstart →
Your own agent, acting as the signed-in user.
`createVendo({ mcp: true })`
Quickstart →
`vendo init` reads your brand out of your app into `.vendo/theme.json`. Register
your own components and a screen renders your real UI, not the built-in kit.
## What they build from
Whatever a user builds is made of these three things.
## Start where you are
The embedded surface is the step after that, and `vendo init` asks which of
these you are doing and wires that one.