Skip to main content
The original four profile operations passed in the native Muse app on October 17, 2026 through its existing private REST integration. This custom connector uses an API key, rather than MCP/OAuth sign-in.
1

Prepare a dedicated key

Open Connections in Datalayer. Reuse an existing Datalayer integration and its protected key. For a new setup, create a dedicated API key named Muse so you can revoke it separately.
2

Ask Muse to create the connector

Copy the setup prompt below into Muse. It contains no secret. Keep the API key out of chat, generated source, URLs, logs and shared repositories.
3

Supply the key through secure entry

Supply the key only through Muse’s secure credential-entry flow and store it in the Secure Credentials Store. If no secure entry is available, stop instead of pasting the key into chat.
4

Check authentication only

Have Muse run GET /v1/auth first. It should return {"authenticated":true}. This check uses no credits and makes no data lookup. Confirm the data operations and get_account_details are available before requesting research.

Paste this

Copy this into Muse. It contains no secret. The same prompt is on Get started. If Muse needs every field bound, use the full operation list below.

Full operation list

This is a private custom setup, not a marketplace listing. The OpenAPI specification is the field reference. For a company lookup by domain, supply only the hostname, such as stripe.com, without a scheme or path. Omit absent optional fields instead of sending null. Once authentication succeeds and your account has an active allowance, copy:
On the published plan for new signups, a search with results costs 1 credit and an empty search costs nothing. A new profile costs 1 credit, and a verified work email costs 2. All clients share the same allowance. Review usage and saved results in your dashboard. Do not interpret a timed-out search as no matching records; follow usage and retries. Muse documents custom connectors and a Secure Credentials Store. If that secure entry flow is unavailable, stop setup and use dashboard Support. See Meta’s connector guide. Revoke the dedicated API key in Connections when removing this integration. The October 17 acceptance above covers the original four operations. It does not by itself verify this expanded credit release in the installed client. Saved connections keep their existing names.