Use DNSai in Meta Muse

Meta's Muse agent, the Muse Code CLI and the Meta Model API each reach DNSai a different way: a custom connector built from the OpenAPI spec, a streamable-HTTP MCP entry, or plain function calling.

✓ Free key works — Muse Code header or REST Bearer

Works with: Muse app · Muse Code · Meta Model API · one domain per request

Each lookup = one domain or IP. Free: 10 lookups/day per IP (anonymous) or 100 lookups/day per key (free key).

↓ Download this guide (.md) drop it into your repo or paste it into your assistant

Running bulk / multi-domain or enterprise-scale lookups? → DNSai Pro & Enterprise

Set it up

Muse app (web, iOS, Android, WhatsApp)

Muse builds Custom Connectors from a service's API on request (Settings → Connectors, or just ask in chat). Send Muse the message below; it reads the OpenAPI spec and keeps any key in its Secure Credentials Store. Meta's help page documents API-built connectors; pasting the MCP URL (https://mcp.dnsai.com/mcp, streamable HTTP) is reported to work but is not in Meta's docs yet.

Create a custom connector for DNSai.
OpenAPI spec: https://api.dnsai.com/openapi.json
Auth header: Authorization: Bearer dk_free_xxxxxxxx
(optional — without it DNSai allows 10 lookups/day)

Muse Code (CLI) — MCP

Add a streamable-HTTP server to ~/.config/muse/settings.json (the file must carry "schema_version": 1). A static Authorization header is sent as-is, so the free key works; drop headers for anonymous use.

{
  "schema_version": 1,
  "mcpServers": {
    "dnsai": {
      "type": "streamable-http",
      "url": "https://mcp.dnsai.com/mcp",
      "headers": { "Authorization": "Bearer dk_free_xxxxxxxx" }
    }
  }
}

Meta Model API (Muse Spark) — function calling

Building your own agent on api.meta.ai/v1? Muse Spark takes function tools in the tools array. Generate them from the OpenAPI spec and have the handler call the REST API with the Bearer key. No MCP tool type is documented on the Model API yet.

# tool definitions come from
https://api.dnsai.com/openapi.json

# your function handler calls
curl -H "Authorization: Bearer dk_free_xxxxxxxx" \
     https://api.dnsai.com/v1/email-security/acme.com

Your key. Muse Code and the REST API both take a Bearer header, so the free key works for 100 lookups/day. In the Muse app, hand Muse the key when it asks for credentials. Get a free key, or stay anonymous for 10 lookups/day.

Verify it works

Ask Muse:

Use dnsai to check the email security of shopify.com

Every result ends with a plain-English summary, a source link on dnsai.com, and your remaining quota.

Troubleshooting

Muse connects from Meta's cloud, so only public HTTPS endpoints work — DNSai already is.
Muse Code refuses to start without "schema_version": 1 in settings.json. Remote MCP tools run outside its sandbox; every DNSai tool is read-only.
Meta does not review Custom Connectors, so Muse will ask you to confirm the service. DNSai's tools and limits are listed at dnsai.com/api.

Sources: How Muse works with Connectors (Meta Help) · Muse Code MCP servers · Build with Muse Spark (Meta Model API)

Need bulk, multi-domain, or the full API?

Pro unlocks bulk / multi-domain lookups; Enterprise adds large-scale scanning and the full programmatic API.

See plans & pricing →

Already on DNSai Domain Manager? Connect your monitored portfolio to Meta Muse through the account MCP connector (Enterprise plans): app.dnsai.com/integrations/meta-muse/