Meta · OpenAPI actions

DNSai for Meta Muse

Meta's Muse models (behind Meta AI and the Meta Model API) call tools through standard function calling. Point them at DNSai's OpenAPI spec, or run Muse inside an agent that supports MCP.

What you can ask Meta Muse

Example answers use made-up domains.

“Compare email security for these five competitors.”

Two enforce DMARC reject, one has quarantine, two have none. Only northwind.example publishes BIMI.

Connect in 3 steps (about 10 minutes)

Create a DNSai API key.
Give Muse DNSai functions built from the OpenAPI spec, or run Muse in an MCP-capable agent.
Ask about your domains.

Signed-in Enterprise customers get the exact click-by-click steps and ready-to-paste configuration for Meta Muse, a one-click API key for it, and a live connection check.

Meta Muse requirements: Meta Model API access. DNSai Enterprise plan.

Security

Meta Muse calls the REST API with an API key stored in Meta Muse's own secret settings.
Account and organization owners can make API keys and assistants read-only, so they can read your data but never change it or start scans.
Starting a credit-spending Deep Scan always needs an estimate and your explicit confirmation.
DNSai data comes from public DNS and web records. Your watchlists, notes and tags stay private to your account and are only shared with an AI tool you connect yourself.

Connect Meta Muse to DNSai

The API and AI connectors are included with DNSai Enterprise plans. Every member of your organization shares one set of limits, and every call counts from the first one.

Other integrations

Last checked 2026-10-29.