# Mail Routing Readiness Check for Vendor Screening

> Mail Routing Readiness Check for Vendor Screening is a paid API for AI agents from market.datapackvibe.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-02).

Checks MX, SPF, and DMARC DNS records for a domain to assess its mail routing readiness for vendor screening purposes.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/demand-domain-mail-routing-readiness-vendor-screening?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/mail-routing-readiness-check-for-vendor-screening-767bd3a7
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_nWM3nzOXtM6znzx7fIBvM

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability mail-routing-readiness-check-for-vendor-screening-767bd3a7 -d '<json body>'
```

Example prompt: Can you check whether acmecorp.com has its MX, SPF, and DMARC DNS records properly set up? I need to assess their mail routing readiness before we bring them on as a vendor.

## When to prefer this

Use this endpoint when you need to screen a vendor or third-party domain for basic email infrastructure readiness using only DNS data — no email is sent, no inbox is probed. Prefer this over general email validation tools when you specifically need MX, SPF, and DMARC checked together in a single call for procurement or vendor due diligence workflows. It is not suitable for verifying whether a specific email address exists or whether an inbox is active.

## Known failure modes

- Domain does not exist in DNS — no records returned
- Domain has no MX records, indicating it cannot receive email
- SPF or DMARC records are absent, resulting in partial readiness data
- Malformed domain input causes a validation error
- DNS lookup timeout if the authoritative nameserver is unresponsive

## How this service works

Mail routing readiness for Vendor screening: Check MX, SPF, and DMARC DNS records together. DNS data only; does not send email or verify that an inbox exists.

## Output

Returns the DNS-based mail routing readiness assessment for the given domain, including the presence and contents of MX records (indicating where email is delivered), SPF records (indicating authorized senders), and DMARC records (indicating email authentication policy). No email is sent and no inbox existence is verified — this is purely DNS data.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "domain": {
   "type": "string",
   "default": "example.com",
   "description": "Public DNS domain, e.g. example.com."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/mail-routing-readiness-check-for-vendor-screening-767bd3a7/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from market.datapackvibe.com](https://www.zero.xyz/host/market.datapackvibe.com/llms.txt)