> ## Documentation Index
> Fetch the complete documentation index at: https://embedded-apps.rollout.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Embedded Apps Marketplace

> Give your agents the apps they already use, right on their contacts, without building a single integration.

![A CRM contact page for Melissa Hartman. Beside her details and timeline, an Apps tab shows a cash offer for her home from one app, and showing feedback from another.](https://mintcdn.com/rollout-embedded-apps/I1umzqggy_PAdPKI/images/contact-page.png?fit=max\&auto=format\&n=I1umzqggy_PAdPKI\&q=85\&s=f08ba06c50cce3f2d3be7458f3568f7e)

An agent's contact page, with two apps in the Apps tab. Each app knows which agent is looking, and at which contact.

This is where you'll end up. An agent opens a contact in your CRM, and next to
the details and timeline you already show, an **Apps** tab shows the tools they
use for that client: a cash offer for her home, the feedback from her
showings, a valuation, a transaction's status.

Each of those is a third-party app, built and run by its own company. You
didn't build any of them. You added Rollout's Embedded Apps Marketplace to your
CRM once, and every app listed in it can now show on your contacts.

## What you get

> [card] An app marketplace
>
> A marketplace for your CRM, like the one Follow Up Boss is known for, where
> your agents and admins turn apps on.

> [card] Apps on every contact
>
> Each app shows on your contact pages, in a frame Rollout runs, with a signed
> context saying who's looking at which contact.

> [card] Control over what's in it
>
> Nothing reaches your users until you've reviewed it, and you can suspend an
> app at any time.

## What you build

Two components on your pages, and a token endpoint on your server:

* **The apps**, on your contact page, with `mountEmbeddedApps()`.
* **The marketplace**, on a settings page, with
  `mountEmbeddedAppMarketplace()`, or your own page built on the
  [marketplace API](https://embedded-apps.rollout.com/reference/marketplace-api.md).
* **A token endpoint** that signs a short-lived token for the user who's signed
  in.

Rollout runs everything else: the frame the apps load in, signing each launch,
onboarding app publishers, and the tools you review their apps with.

## Where to go next

> [card] [Why run a marketplace](https://embedded-apps.rollout.com/why.md)
>
> What a marketplace does for your agents, and for your CRM.

> [card] [What your users see](https://embedded-apps.rollout.com/tour.md)
>
> A tour of the apps, the marketplace, and your review queue.

> [card] [How it works](https://embedded-apps.rollout.com/how-it-works.md)
>
> The pieces, who runs each, and what happens when an agent opens a contact.

> [card] [Implementation plan](https://embedded-apps.rollout.com/build/overview.md)
>
> The steps from first call to a live marketplace.

> [!NOTE]
>
> Building an app to show in CRMs? The guides for app publishers are in
> [Rollout's developer docs](https://rollout.com/docs/embedded-apps/overview).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.