{"uid":"cap_idQ97iRovn95MviT0_aEL","slug":"mx-record-bulk-lookup-239e19ff","name":"MX Record Bulk Lookup","description":"Bulk mx record lookup: up to 20 domains in one call, processed concurrently, results returned in input order with a per-item error field and a count of failures. Same answer per item as the single /mx-lookup endpoint (MX record lookup). Batch enrichment for agents that hold a list. $0.01 per batch.","url":"https://intel.rallylive.ca/bulk/mx-lookup","method":"GET","headers":{},"bodySchema":{"type":"object","$schema":"https://json-schema.org/draft/2020-12/schema","required":["input"],"properties":{"input":{"type":"object","required":["type","method"],"properties":{"type":{"type":"string","const":"http"},"method":{"enum":["GET"],"type":"string"},"queryParams":{"type":"object","properties":{}}},"additionalProperties":false},"output":{"type":"object","required":["type"],"properties":{"type":{"type":"string"},"example":{"type":"object"}}}}},"responseSchema":null,"example":null,"exampleRequest":null,"tags":["x402"],"displayCostAmount":"0.1","displayCostAsset":"USDC","priceDynamic":false,"priceHint":null,"priceStatus":"priced","priceSource":"probe","requiresHandshake":false,"reviewCount":0,"rating":{"score":"0.00","successRate":"0.00","reviews":0,"stars":null,"state":"unrated"},"availabilityStatus":"unknown","priceObserved":null,"sessionDeposit":null,"pricing":{"kind":"static","summary":"$0.1/call","primary":{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.1","per":"call","confidence":"exact"},"accepted":[{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.1","per":"call","confidence":"exact"}]},"paymentMethods":[{"uid":"pm_tUfo6gDcTnyBQbr8-PpAP","protocol":"x402","methodType":"crypto","chain":"base","mode":"charge","costAmount":"0.1","costPer":"request","priority":0,"asset":"0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913","unit":"request","depositMicros":null,"planRef":null}],"brandName":null,"brandSlug":null,"brandBaseUrl":null,"brandDocsUrl":null,"whatItDoes":"Looks up MX (mail exchange) DNS records for up to 20 domains in a single concurrent batch call, returning results in input order with per-item error fields.","exampleAgentPrompt":"Look up the MX records for all 15 domains on my list — acme.com, globex.org, initech.net, and the rest — in one batch and tell me which mail servers each one uses, flagging any that fail.","exampleUseCases":[{"title":"Email deliverability audit for prospect list","prompt":"I have a list of 18 prospect domains from our CRM — can you batch-check the MX records for all of them at once and tell me which mail provider each one uses and which domains don't have mail configured?"},{"title":"Detecting shared mail infrastructure across competitors","prompt":"Look up MX records for these 12 competitor domains in one shot and tell me if any of them share the same mail servers or use the same email provider."},{"title":"Validating onboarded customer domains before sending","prompt":"Before we send onboarding emails, can you bulk-check MX records for these 20 newly registered customer domains and flag any that are missing mail exchange records or returning errors?"}],"resultDescription":"Returns an ordered array matching the input domain list, where each item contains the MX records (mail server hostnames and priority values) for that domain. Each item also includes a per-item error field indicating any lookup failure. A summary count of total failures across the batch is included. Results are processed concurrently and returned in the same order as the input.","failureModes":["Domain does not exist or has no MX records — per-item error field is populated","Input exceeds 20 domains — request rejected or truncated","Invalid domain format in input — per-item error returned for that entry","DNS resolution timeout for a specific domain — that item marked as failed","Network or upstream DNS failure — entire batch may fail with an error response","Payment not provided or insufficient — 402 payment required response"],"whenToPreferThis":"Use this endpoint when you need MX record data for multiple domains (up to 20) and want to minimize API round-trips by processing them concurrently in a single call. Prefer this over the single /mx-lookup endpoint whenever you have a list of 2 or more domains to check. Ideal for enrichment pipelines, lead qualification workflows, pre-send email validation, or any agent that holds a batch of domains and needs mail server data efficiently. Not suitable if you need more than 20 domains per call (split into multiple batches) or if you need deeper email validation beyond MX records (use the validate-email-address sibling endpoint instead).","instructions":null,"reviewSummary":null,"reviewSummaryHighlights":null,"reviewSummaryConcerns":null,"reviewSummaryGeneratedAt":null,"activationCount":0,"lastUsedAt":null,"lastSuccessfullyRanAt":null,"lastHealthCheckAt":"2026-09-14T07:21:56.568Z","isFirstParty":false}