Get your service listed in Meta Muse
Meta Muse launched in September 2026 and opened to outside connectors ten days later. Millions of people are now asking an assistant to do things for them, and the list of things it can do is short. Your category is probably not on it. Being early is the product.
We make your service one of the things Muse can do, usually within two working days, and then we file the directory submission so Meta's review clock starts on day one. This page is for SaaS founders and for local business owners who sell something an assistant could book, order or look up.
The two paths
Muse has two ways in. We ship both, because only one of them is on your timetable.
- Custom connector. Live immediately, no Meta review. Your customer pastes one prompt into Muse. Muse reads the brief we publish for you, writes its own client inside its secure cloud machine, tests it, and saves it as a reusable skill. This path needs nobody's permission and works the day we finish.
- Directory listing. Meta reviews it. The entry in Settings, then Connectors. The timeline is unknown, so we file on day one and you keep earning from path one while it sits in the queue.
What you get
- A hosted MCP server over HTTPS on your domain. If you have a REST API we wrap it. If your API is awkward for an agent, we build a facade shaped for an agent rather than for a developer.
- Read and write split into separate scopes, so a cautious customer can grant read-only access and your risky operations sit behind their own permission.
- Approval gates on anything that spends money or touches the real world. Preview, price, confirm, then act. This is what Meta's security layer expects and it is what stops an agent doing something expensive by accident.
- The connector brief: a short machine-readable document Muse reads to build its client. This is the artefact the whole custom-connector path runs on.
- An
llms.txtat your site root, so other agents and agent directories can find you too. - Per-connector privacy policy and terms as publishable drafts, including the AI-agent clauses your current terms almost certainly do not have. Your counsel reviews them; we do not give legal advice.
- A 512x512 icon built to the directory's spec.
- The submission packet: every form field filled, in form order, with reviewer notes that pre-answer the questions a Meta reviewer asks about scopes, approval gates, test accounts and rate limits.
- We file the submission with you, on your account, and we set up a test account for Meta's end-to-end review run.
- Monitoring on the endpoint, the OpenAPI document and both legal URLs, with alerts to us. A privacy page returning 404 during review is an avoidable rejection.
- Example prompts written in customer language, which is what actually drives discovery inside a chat box.
What we need from you
Short list. Most of it is an email.
- API access: docs, a test key, and a sandbox if you have one.
- One technical contact who can answer a question inside a day.
- Brand assets: a vector logo, the product name, the company legal name.
- A decision on scope: which operations are read, which are write, which need a human to confirm.
- Your existing privacy policy and terms, so the connector pages match them.
- A US Muse account for the submission, or authority to use yours.
- Pricing, if the connector charges for anything.
No public API at all? We can still do it. It becomes a facade build, which is the top of the price band.
Timeline: one to two days
| Day | What happens |
|---|---|
| 0 | Kickoff call, API access, scope decision. About 45 minutes. |
| 1 | Connector built and deployed. Brief, llms.txt and icon published. Legal drafts sent to your counsel. |
| 1 to 2 | Endpoint checks green. Packet generated. The custom-connector path is live and your team can test it. |
| 2 | Directory submission filed. Monitoring on. |
The part that is not on our clock is Meta's review. See the caveats below.
What it costs
| Your situation | Build, one-off | Hosting and monitoring |
|---|---|---|
| Clean REST API with an OpenAPI document | $1,500 | $200/mo |
| An API, no OpenAPI, some awkward authentication | $2,500 to $3,500 | $300/mo |
| No usable public API, we build the facade | $5,000 | $500/mo |
Each additional connector under the same company is $1,000 off the build, because the kit is already there.
Hosting and monitoring covers the running endpoint, uptime alerting on the endpoint and the legal URLs, keeping the brief in sync when your API changes, and re-submitting if Meta comes back with questions. Cancel any month. You get the source either way.
Why us
No Errands runs on the same stack. The connector briefs Muse reads for
our own mail, fax and booking services, the llms.txt, the
per-connector legal pages, the 512x512 icons and the endpoint monitoring are
all the same tooling your build runs through on day one. We wrote it because we
needed it, not because we wrote a deck.
Read what we publish and judge it before you pay us anything: the mail connector brief Muse reads, the same thing for humans, our llms.txt, a per-connector privacy page and the API docs.
The honest caveats
We would rather you hear these from us than find them later.
- Meta has published no review SLA. No queue, no status page, no promise. As of September 2026 nobody had publicly reported an approval. The custom-connector path is what makes this worth doing today; the directory listing is the upside, not the plan.
- The Muse connector terms are not public. The submission form asks you to attest to terms Meta has not published. We ask for a copy in writing before you tick that box. Agreeing to a contract you have not read is your call to make, not ours.
- Muse is United States only. Customers outside the US cannot use your connector yet.
- No SDK, no published spec, no published fee schedule. Meta has said it will take a very small cut of transactions Muse completes. The number is not public. Assume it lands on the business side.
- Approval is not guaranteed and featured placement is explicitly editorial. We can make you meet every stated requirement. We cannot make an editor pick you.
- The platform is weeks old. Facts move. We re-verify before every build and we tell you when something we said last month has changed.
Get in touch
What to put in the email, so the first reply is useful:
- What your service does, in one sentence.
- A link to your API documentation, or "no public API" if that is the case.
- The two or three things a customer would ask an assistant to do.
- Which of those spend money or change something in the real world.
- Whether you already have a US Muse account.
- Your deadline, if you have one.
We come back with a scope decision and a fixed price within one working day.
Selling online rather than through an API? The related offer is a Muse-ready storefront audit, which checks whether an agent can already find, read and buy from your store.