# MX Data Helper - Mexican Identifier Validator

> MX Data Helper - Mexican Identifier Validator is a paid API for AI agents from temporary-prompt-onyx-8ryoe7p.vercel.app, paid per call via x402, $0.002/call, status unknown (last checked 2026-09-16).

Validates Mexican identifiers (CURP, RFC, phone numbers) via a pay-per-call API on Base mainnet

## Facts

- Endpoint: POST https://temporary-prompt-onyx-8ryoe7p.vercel.app/v1/data_validate
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/mx-data-helper-mexican-identifier-validator-8e7017da
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_5t8jhovcR1_HYKkOucTJ5

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-mexican-identifier-validator-8e7017da -d '<json body>'
```

Example prompt: Can you validate this CURP for me: LOOA531113HTCPBN07 — I need to know if it's a properly formatted and valid Mexican identifier.

## When to prefer this

Use this endpoint when you need to validate Mexican government-issued identifiers (CURP, RFC) or Mexican phone numbers in a pay-per-call model without a subscription. It is well-suited for low-volume or on-demand validation workflows using the x402 micropayment protocol on Base mainnet. Avoid if you need bulk validation or if you require detailed breakdown beyond a validity check.

## Known failure modes

- Missing required 'value' field returns 400 Bad Request
- Malformed or unrecognized identifier format may return validation failure or error
- Payment failure on Base mainnet (insufficient USDC balance or x402 protocol error) blocks the call
- Temporary Vercel deployment downtime may cause 503 errors
- Identifier type not recognized if value doesn't match CURP, RFC, or phone patterns

## How this service works

Pay-per-call x402 data services on Base mainnet

## Output

Returns a validation result indicating whether the submitted Mexican identifier (CURP, RFC, or phone number) is valid, along with any relevant details about the identifier's format or status.

## 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-mexican-identifier-validator-8e7017da/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from temporary-prompt-onyx-8ryoe7p.vercel.app](https://www.zero.xyz/host/temporary-prompt-onyx-8ryoe7p.vercel.app/llms.txt)