# MX Data Helper - Validate Mexican Identifier

> MX Data Helper - Validate Mexican Identifier is a paid API for AI agents from temporary-fleet-eclipse-duogf0d.vercel.app, paid per call via x402, $0.002/call, status unknown (last checked 2026-09-13).

Validates Mexican identifiers (CURP, RFC, or phone number) and returns a validation result

## Facts

- Endpoint: POST https://temporary-fleet-eclipse-duogf0d.vercel.app/v1/data_validate
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/mx-data-helper-validate-mexican-identifier-618af721
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_BSQ8tsdm-GGVDMfTIh4GC

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 mx-data-helper-validate-mexican-identifier-618af721 -d '<json body>'
```

Example prompt: Can you check if this Mexican CURP is valid: BADD110313HCMLNS09?

## When to prefer this

Use this endpoint when you need to validate Mexican government or tax identifiers — specifically CURP (national population registry code), RFC (tax ID), or Mexican phone numbers — as part of KYC flows, onboarding checks, invoice validation, or compliance pipelines. It is pay-per-call via x402 on Base mainnet, making it suitable for low-volume or on-demand validation without a subscription. Prefer this over manual regex checks when you need authoritative format and checksum validation for Mexican identifiers.

## Known failure modes

- Missing or empty 'value' field returns a 400 validation error
- Unrecognized identifier format may return an ambiguous or invalid result
- Network timeout on the Vercel deployment
- Payment failure on Base mainnet blocks the call (402 response)
- Ambiguous input that matches no known identifier type may return an error or low-confidence result

## How this service works

Pay-per-call x402 data services on Base mainnet

## Output

Returns a validation result indicating whether the submitted identifier (CURP, RFC, or phone number) is valid, along with parsed components or error details if the identifier is malformed or fails checksum/format rules.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "value"
 ],
 "properties": {
  "value": {
   "type": "string",
   "description": "Identifier to validate (CURP, RFC, phone)"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/mx-data-helper-validate-mexican-identifier-618af721/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from temporary-fleet-eclipse-duogf0d.vercel.app](https://www.zero.xyz/host/temporary-fleet-eclipse-duogf0d.vercel.app/llms.txt)