# Brevo Domain Verification TXT Record Checker

> Brevo Domain Verification TXT Record Checker is a paid API for AI agents from dns.intel.rallylive.ca, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-20).

Checks whether a domain's apex TXT records contain a Brevo (formerly Sendinblue) domain-verification token, indicating the company uses Brevo's email/marketing platform.

## Facts

- Endpoint: GET https://dns.intel.rallylive.ca/dns/verification/brevo?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/brevo-domain-verification-txt-record-checker-654eddba
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_tB-8PQj2MK_CCr0U6eHL_

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 brevo-domain-verification-txt-record-checker-654eddba
```

Example prompt: Can you check whether example.com has a Brevo domain-verification TXT record in its DNS — I want to know if they're using Brevo for email marketing?

## When to prefer this

Use this endpoint when you need to determine whether a specific company or domain uses Brevo (formerly Sendinblue) as their email marketing or transactional email provider, by checking for the canonical Brevo domain-verification TXT record. Prefer this over general DNS TXT lookup endpoints when you specifically want Brevo presence detection with pre-parsed, actionable output rather than raw TXT record data.

## Known failure modes

- Domain does not exist or has no TXT records — returns not present
- DNS resolution failure via Cloudflare DoH — may return an error or timeout
- Domain has Brevo token but it is malformed or non-standard — may not be detected
- Rate limiting or payment failure — request blocked
- Input domain missing from query — returns validation error

## How this service works

Does the domain carry a brevo domain-verification TXT record? Reads the apex TXT records (Cloudflare DoH) and reports whether the brevo ownership token is present and the token value (truncated). A present token usually means the company uses brevo's product; absence means not verified there. $0.01 per lookup.

## Output

Returns whether a Brevo domain-verification TXT record is present at the apex of the queried domain, along with the truncated token value if found. Absence indicates the domain is not verified with Brevo.

## Request schema (JSON Schema)

```json
{
 "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"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/brevo-domain-verification-txt-record-checker-654eddba/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from dns.intel.rallylive.ca](https://www.zero.xyz/host/dns.intel.rallylive.ca/llms.txt)