# Mexican RFC Structural Validator with EFOS Blacklist Check

> Mexican RFC Structural Validator with EFOS Blacklist Check is a paid API for AI agents from x402-api-24223879872.us-east1.run.app, paid per call via x402, $0.03/call, status unknown (last checked 2026-10-11).

Validates the structure of a Mexican RFC (tax ID) — checking persona física/moral format, embedded date, SAT check digit — and queries the Article 69-B EFOS blacklist status.

## Facts

- Endpoint: POST https://x402-api-24223879872.us-east1.run.app/v1/mx/rfc?utm_source=zero.xyz
- Price: $0.03/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-11
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/mexican-rfc-structural-validator-with-efos-blacklist-check-8edbb8cb
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_BQAO0E-W2-FtdFKoC6fBA

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 mexican-rfc-structural-validator-with-efos-blacklist-check-8edbb8cb -d '<json body>'
```

Example prompt: Can you validate the Mexican RFC 'EKU9003173C9' — check if it's structurally correct, whether it belongs to a persona física or moral, and whether it appears on the EFOS blacklist?

## When to prefer this

Use this endpoint when you need to validate a Mexican RFC's structural correctness AND cross-check it against the SAT EFOS Article 69-B blacklist in a single call. It is specifically suited for Mexican tax compliance workflows, supplier onboarding, CFDI invoice preparation, or KYC checks involving Mexican entities. Prefer this over generic string validators because it understands the persona física/moral distinction, embedded date, and SAT check digit algorithm, and it performs a live or cached EFOS lookup.

## Known failure modes

- Malformed RFC string returns validation error with structural breakdown
- RFC not found in SAT/EFOS database may return unknown blacklist status
- Network timeout or SAT service unavailability may cause delayed or failed EFOS lookup
- Input missing 'rfc' field returns 400 bad request
- Extremely new or recently issued RFCs may not yet appear in EFOS dataset

## How this service works

Structural validation of a Mexican RFC (sent as a JSON body, not a query param): persona física/moral, embedded date, SAT check digit, plus Article 69-B (EFOS) blacklist status.

## Output

Returns a structured JSON response indicating: whether the RFC is structurally valid, whether it belongs to a persona física or moral, the validity of the embedded date, whether the SAT check digit is correct, and whether the RFC appears on the Article 69-B EFOS blacklist of tax offenders.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "rfc": {
   "type": "string",
   "description": "RFC to validate, e.g. EKU9003173C9"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/mexican-rfc-structural-validator-with-efos-blacklist-check-8edbb8cb/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402-api-24223879872.us-east1.run.app](https://www.zero.xyz/host/x402-api-24223879872.us-east1.run.app/llms.txt)