OpenAI · MCP with API key

DNSai for OpenAI Codex

Give the Codex CLI live DNS, email-security and change data: add DNSai to config.toml and Codex reads the key from your environment.

What you can ask OpenAI Codex

Example answers use made-up domains.

“Write a script that posts new DMARC changes to our Slack channel.”

Here is a script that polls /api/v1/changes/?field=dmarc_policy_p with a stored since_id and posts each change's summary to your webhook.

Connect in 3 steps (about 2 minutes)

Create a DNSai API key and set it as DNSAI_API_KEY.
Add a [mcp_servers.dnsai] table to ~/.codex/config.toml.
Start Codex and ask about your domains.

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

OpenAI Codex requirements: Codex CLI. DNSai Enterprise plan.

Security

OpenAI Codex sends an API key in the Authorization header. Use an expiring key made for OpenAI Codex and keep it in an environment variable.
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 OpenAI Codex 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.