# RESET Verifica — Mexican RFC Format Validator

> RESET Verifica — Mexican RFC Format Validator is a paid API for AI agents from api.resetparatodos.com, paid per call via x402, $0.03/call, status unknown (last checked 2026-09-15).

Deterministically validates a Mexican RFC (taxpayer ID) for correct format, person type (individual vs. company), embedded date, and check digit — structural validation only, no external lookup.

## Facts

- Endpoint: POST https://api.resetparatodos.com/x402/v1/rfc/validate
- Price: $0.03/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/reset-verifica-mexican-rfc-format-validator-11e2a03f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_FhBGYdo3w0gPlPB4u01AR

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 reset-verifica-mexican-rfc-format-validator-11e2a03f -d '<json body>'
```

Example prompt: Can you check whether the RFC 'LOAF800101AAA' is a valid Mexican taxpayer ID — tell me if the format is correct, whether it's for an individual or a company, and if the check digit is valid?

## When to prefer this

Use this endpoint when you need fast, cheap, offline-style structural validation of a Mexican RFC before performing more expensive registry lookups (e.g., SAT blacklist or public record verification). Ideal for pre-validating user input in onboarding forms, invoice processing pipelines, or KYC workflows where you want to catch obvious errors immediately. Prefer this over the full SAT registry verification endpoint when you only need format correctness and don't require confirmation that the RFC is actually registered.

## Known failure modes

- RFC is fewer than 12 or more than 13 characters — validation fails with format error
- Invalid characters in RFC string — returns format invalid
- Check digit mismatch — returns check digit invalid with details
- Missing or malformed request body — returns 400 bad request
- Payment not provided or insufficient — returns 402 Payment Required

## How this service works

Deterministically validate a Mexican RFC (taxpayer ID): format, person type (individual/company), embedded date, and check digit. Structural validation only.

## Output

Returns a structured JSON object indicating whether the RFC is valid, the detected person type (individual or moral/company), the date embedded in the RFC, and whether the check digit is correct — all derived purely from structural analysis without any external registry lookup.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "rfc": {
   "type": "string",
   "description": "Mexican RFC (12-13 chars)"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/reset-verifica-mexican-rfc-format-validator-11e2a03f/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.resetparatodos.com](https://www.zero.xyz/host/api.resetparatodos.com/llms.txt)