# Delx Commerce SPF Record Flags Parser

> Delx Commerce SPF Record Flags Parser is a paid API for AI agents from commerce.delx.ai, paid per call via x402, $0.001/call, status unknown (last checked 2026-10-01).

Parses an SPF TXT record string and returns boolean flags indicating which mechanisms are present (a, mx, include, all).

## Facts

- Endpoint: POST https://commerce.delx.ai/api/v1/x402/spf-record-flags?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-01
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/delx-commerce-spf-record-flags-parser-2cc5d2b5
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_KaHx3Ikbfk7j0OR9-7z1h

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 delx-commerce-spf-record-flags-parser-2cc5d2b5 -d '<json body>'
```

Example prompt: Can you parse this SPF record and tell me which mechanisms it uses — specifically whether it has a, mx, include, or all? The record is: 'v=spf1 include:_spf.google.com ~all'

## When to prefer this

Use this endpoint when you need to programmatically inspect the mechanisms present in a raw SPF TXT record string without building a full SPF parser. It is ideal for agents auditing email deliverability configurations, validating DNS records before publishing, or checking compliance with SPF policy requirements. Prefer it over writing custom regex-based parsing logic.

## Known failure modes

- Missing or malformed SPF string input returns an error
- Non-SPF string passed as input may produce incorrect flags
- Empty string input may cause a parsing failure
- Record with non-standard formatting may yield unexpected boolean values

## How this service works

Pay-per-result APIs for agents. No signup. Exact price. Verifiable delivery. USDC on Base + Solana via x402.

## Output

A JSON object containing boolean flags: 'a' (whether the a mechanism is present), 'mx' (whether the mx mechanism is present), 'include' (whether an include directive exists), and 'all_mechanism' (whether an all qualifier is present), plus a schema identifier string.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "spf": {
   "type": "string",
   "description": "SPF TXT record body"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "a": false,
  "mx": false,
  "schema": "delx/util-spf-record-flags/v1",
  "include": true,
  "all_mechanism": true
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/delx-commerce-spf-record-flags-parser-2cc5d2b5/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from commerce.delx.ai](https://www.zero.xyz/host/commerce.delx.ai/llms.txt)
