Integration
Connect MailCheck.ai to District of Columbia Open Data
When something happens in MailCheck.ai, your agent does the next thing in District of Columbia Open Data. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want MailCheck.ai and District of Columbia Open Data to do together?
Describe it and your agent reads both APIs, builds the automation, tests every branch and ships it. The list below is what exists today, not the limit.
Ask the assistant
You'll sign in before anything runs. What you typed comes with you.
Or work from Claude Code
Install the APIANT plugin for Claude Code and build, edit, test and read run history from your terminal. Every plan gets this, including free, and it spends no assistant credits.
Connect Claude CodeEverything your agent can do with MailCheck.ai and District of Columbia Open Data
Triggers and actions 4 triggers ยท 5 actions
Trigger
Domain added to blocklist (instant)Fires when a domain is added to the account's blocklist.
Trigger
Domain flagged as relay (instant)Fires when a previously-looked-up domain is newly flagged as a relay/forwarding domain.
Trigger
Domain flagged as spam (instant)Fires when a previously-looked-up domain is newly flagged as a spam domain.
Trigger
Domain unflagged as spam (instant)Fires when a previously-looked-up domain changes from spam to non-spam.
Action
Get domainCheck a domain for disposable/relay/spam status, MX configuration, age, SPF/DMARC posture, and blocklist status.
Action
Get emailCheck an email address for disposable/relay/role-account status, normalized form, and its domain's signals.
Action
Find datasetsSearch the DC Open Data catalog for datasets by keyword, category, or tag, returning matching dataset ids, titles, and descriptions.
Action
Find recordsQuery a dataset's features/records with attribute filters, spatial filters, sorting, and paging, returning JSON or GeoJSON results.
Action
Get datasetGet a dataset's metadata and field/schema definitions by dataset or layer id, so callers know what attributes can be filtered or returned.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews