Integration

Connect DNSFilter to Enrich.so

When Blocked Page Form Submitted fires in DNSFilter, your agent runs Email Finder in Enrich.so. Describe the whole flow and it is built, tested on every scenario and kept running.

What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.

Build solutions, not workarounds.

What do you want DNSFilter and Enrich.so to do together?

Ask the assistant

You'll sign in before anything runs. What you typed comes with you.

Examples

Pick one to fill the box, then change anything: the steps, the wording, even the apps. Go as long as you like.

Connect your AI client

Give your AI client this address.

https://mcp.apiant.ai

Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.

Set it up in your client
Claude Code

Run this in the directory you want to work in.

claude mcp add --transport http -s project apiant-ai https://mcp.apiant.ai

Start Claude Code there, approve the server, and sign in in the browser page it opens.

Claude Code guide (opens in a new tab)
Claude, web and desktop

Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.

Setup guide (opens in a new tab)
Cursor

Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.

Setup guide (opens in a new tab)
Zed

Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.

Setup guide (opens in a new tab)
Codex and the ChatGPT desktop app

Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.

Setup guide (opens in a new tab)
Any other MCP client

Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.

Setup guide (opens in a new tab)

DNSFilter tells you when a blocked page is hit, when someone asks for an exception on the block page form, when a policy changes and when an invoice lands. Enrich.so turns an email address into a professional profile, verifies deliverability and searches companies. Joined up, every unblock request arrives with a name, company and job title attached, and allow list notes say who asked and why.

Example flows

What DNSFilter can start in Enrich.so

Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.

Everything your agent can do with DNSFilter and Enrich.so

Triggers and actions 4 triggers · 15 actions

Each app on its own

Reviews

What our customers say

More from DNSFilter

More into Enrich.so

Questions

DNSFilter and Enrich.so, answered

Can the agent check that an unblock request came from a real person before touching a policy?

Yes. The Verify Email action in Enrich.so returns a valid, invalid or risky verdict for the address on the blocked page form, and the agent only runs Add to Allow List in DNSFilter when the verdict comes back valid.

Does this work the other way, with Enrich.so starting things off?

No. Enrich.so has no triggers available, so every scenario starts from a DNSFilter event such as a blocked page visit, a form submission, a policy change or an invoice. Enrich.so is used for the lookup, verification and search actions that follow.

What can start an automation from DNSFilter?

Any of DNSFilter's 4 triggers in the catalog, including Blocked Page Form Submitted, Blocked Page Visited, Invoice Available and Policy Changed. Describe the moment in plain language and your agent picks the right one.

What can your agent do in Enrich.so when something happens in DNSFilter?

Any of Enrich.so's 8 actions, including Email Finder, Enrich Person Lite, Find Person and Search Company. Your agent maps the data both ways and tests every scenario before it ships.

Can it also run from Enrich.so to DNSFilter?

Enrich.so has no triggers in the catalog today, so automations start in DNSFilter. If you need the other direction, ask: your agent reads Enrich.so's API documentation and adds it.

Do I have to build a connector for DNSFilter or Enrich.so?

No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.

What happens when something fails?

Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.

Is there a free plan?

Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.