# Toll402 Mexican RFC Validator

> Toll402 Mexican RFC Validator is a paid API for AI agents from toll402.dev, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-14).

Validates and parses a Mexican RFC (Registro Federal de Contribuyentes) tax ID, verifying format and embedded date for both individuals and companies.

## Facts

- Endpoint: POST https://toll402.dev/v1/t/rfc_validate
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/toll402-mexican-rfc-validator-bf272c2b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_aXbgq7-BdJuyKc07L8I5D

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 toll402-mexican-rfc-validator-bf272c2b -d '<json body>'
```

Example prompt: Can you check if this Mexican RFC is valid: 'GOFJ850101AB3' — and tell me what birth date it encodes and whether it's for an individual or a company?

## When to prefer this

Use this endpoint when you need to validate a Mexican RFC tax ID offline without any external SAT API calls. Ideal for form validation, user onboarding, invoice pre-checks, or any compliance workflow involving Mexican individuals (persona física) or companies (persona moral). Prefer this over manual regex checks because it also validates the embedded date as a real calendar date, not just the format.

## Known failure modes

- Invalid format — wrong number of letters in the name prefix
- Embedded date is not a real calendar date (e.g., month 13 or day 32)
- Homoclave portion does not match expected 3-character alphanumeric pattern
- Empty or missing RFC input returns validation error
- Non-string input type causes schema rejection

## How this service works

Offline validator for a Mexican RFC (Registro Federal de Contribuyentes). Checks the format for persona física (4 letters + 6-digit date + 3-char homoclave) or persona moral (3 letters + 6-digit date + 3-char homoclave), verifies the embedded date is a real calendar date, and returns the parsed birth/incorporation date. Pure string/date logic, no network calls.

## Output

Returns whether the RFC is valid, the detected type (persona física or persona moral), the parsed calendar date (birth date for individuals, incorporation date for companies), and details about the homoclave. On failure, returns an explanation of which part of the format is invalid.

## 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",
    "bodyType",
    "body"
   ],
   "properties": {
    "body": {
     "type": "object",
     "properties": {}
    },
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "POST"
     ],
     "type": "string"
    },
    "bodyType": {
     "enum": [
      "json",
      "form-data",
      "text"
     ],
     "type": "string"
    }
   },
   "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/toll402-mexican-rfc-validator-bf272c2b/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from toll402.dev](https://www.zero.xyz/host/toll402.dev/llms.txt)