APIVoid MCP integration for AI agents.
Connect AI agents to APIVoid through 5 structured actions, including check domain reputation, verify email, and check ip reputation. Review authentication, i…
- ACTION CONTRACTS
- 5
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the APIVoid integration exposes
The APIVoid Agent App exposes 5 provider-backed actions for security and data work. Its current contract lets an authorized agent check the reputation, blacklist status, category flags, and risk score of a domain with apivoid, verify an email address or email domain with apivoid, and check the reputation, blacklist status, and risk score of an ip address with apivoid. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected APIVoid account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real APIVoid capabilities.
Showing 5 of 5 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
check_domain_reputationREADCheck the reputation, blacklist status, category flags, and risk score of a domain with APIVoid.
INPUTS: host / excludeEngines / spamhausKey / includeDomainAge / domainAgeCacheOnly
verify_emailREVIEWVerify an email address or email domain with APIVoid.
INPUTS: email / domain
check_ip_reputationREADCheck the reputation, blacklist status, and risk score of an IP address with APIVoid.
INPUTS: ip / excludeEngines / spamhausKey / disableReverseDns
check_url_reputationREADCheck DNS, blacklist, file, and risk signals for a URL with APIVoid.
INPUTS: url
get_account_infoREADGet APIVoid account credit, overage, and usage information.
INPUT CONTRACTS
Know what the action needs before it runs.
check_domain_reputation
hostREQUIRED- The domain or host to submit, for example google.com.
excludeEnginesOPTIONAL- Comma-separated APIVoid engine names to exclude from the scan.
spamhausKeyOPTIONAL- Optional Spamhaus DBL DQS key to enable the Spamhaus engine.
includeDomainAgeOPTIONAL- Whether APIVoid should include domain age as a risk factor. This may consume an additional credit.
domainAgeCacheOnlyOPTIONAL- Whether to use only cached domain age data when includeDomainAge is enabled.
verify_email
emailOPTIONAL- The email address to submit for APIVoid verification.
domainOPTIONAL- The email domain to submit when verifying domain-level email signals.
check_ip_reputation
ipREQUIRED- The public IPv4 or IPv6 address to scan with APIVoid.
excludeEnginesOPTIONAL- Comma-separated APIVoid engine names to exclude from the scan.
spamhausKeyOPTIONAL- Optional Spamhaus DBL DQS key to enable the Spamhaus engine.
disableReverseDnsOPTIONAL- Whether to disable reverse DNS lookup to reduce response time.
check_url_reputation
urlOPTIONAL- The URL to submit for reputation scanning.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Check Domain Reputation
Check the reputation, blacklist status, category flags, and risk score of a domain with APIVoid. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
check_domain_reputationVerify with Check Ip Reputation
Check the reputation, blacklist status, and risk score of an IP address with APIVoid. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
check_ip_reputationSAFETY BOUNDARY
Operate APIVoid with explicit limits
- Authorize APIVoid with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned APIVoid data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in APIVoid rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the APIVoid task completed successfully.
CONNECTION MODEL
API key
APIVoid API key sent with the X-API-Key header. Create or view API keys in the APIVoid dashboard: https://dash.apivoid.com/.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 4
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 1
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by APIVoid.