# Mexico RFC Validator (`parseforge/mexico-rfc-scraper`) Actor

Bulk-validate Mexican RFC tax IDs against the official SAT registry. Returns registration status and taxpayer name for each RFC. No SAT login or e.firma certificate needed.

- **URL**: https://apify.com/parseforge/mexico-rfc-scraper.md
- **Developed by:** [ParseForge](https://apify.com/parseforge) (community)
- **Categories:** Lead generation, Other
- **Stats:** 2 total users, 1 monthly users, 90.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $19.00 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

[![ParseForge](https://raw.githubusercontent.com/ParseForge/apify-assets/main/banner.jpg)](https://apify.com/parseforge?fpr=vmoqkp)

### Mexico RFC Validator

**Validate Mexican RFC tax IDs in bulk against the official SAT registry.** Each RFC returns its registration status, registered taxpayer name, and fiscal situation. No API key, no SAT portal login. Export results to CSV, JSON, Excel, or XML.

The SAT portal only lets you check one RFC at a time, and the official API requires a cumbersome e.firma certificate. This Actor validates lists of Mexican RFCs directly, returning the official registration status and taxpayer name for each one. It works for both persona física and persona moral IDs, so you can verify suppliers, customers, or payroll records without manual lookups.

| Who uses it | What they scrape Mexico RFC Validator for |
|---|---|
| Contadores y despachos contables | Validar listas de RFCs de clientes y proveedores antes de emitir facturas electrónicas (CFDI). |
| Compliance officers | Verify supplier RFCs during onboarding to confirm they are registered and active with SAT. |
| Accounts payable teams | Bulk-check vendor RFCs before processing payments to avoid rejected CFDI invoices. |
| HR and payroll departments | Validate employee RFCs in bulk to ensure correct payroll tax withholding and IMSS registration. |

### What it does

This Actor validates a list of Mexican RFC tax IDs against the SAT public registry and returns each RFC with its status, registered name, and fiscal details as a flat row.

- 📋 **Bulk validation:** Paste a list of RFCs and validate up to a million per run, no SAT portal login required.
- ✅ **Registration status:** Returns whether each RFC is registered, active, and its current fiscal situation.
- 🏢 **Taxpayer name:** Retrieves the registered business or individual name (razón social or nombre) tied to each RFC.
- 📄 **Flat row output:** Every validated RFC comes back as one row with its status and name, ready for CSV, JSON, Excel, or XML export.

Results export to CSV, JSON, Excel, or XML, or straight from the API.

### What you can do with Mexico RFC Validator data

**🧾 Validate supplier RFCs before CFDI invoicing.**

An accounts payable team uploads a list of 500 vendor RFCs, validates them all in one run, and flags any unregistered IDs before issuing purchase invoices.

**👥 Bulk-check employee RFCs for payroll.**

An HR department validates a new-hire RFC list against SAT to confirm each employee's tax ID is active before the first payroll run.

**📊 Audit a client portfolio for fiscal compliance.**

A contador runs a client's full supplier list through the Actor and delivers a report showing which RFCs are active and which need updating.

**🔍 Screen potential business partners.**

A compliance officer validates the RFCs of prospective vendors during due diligence to confirm they are registered and in good standing with SAT.

### Why choose this scraper

| | What you get |
|---|---|
| **Bulk validation** | Check hundreds or thousands of RFCs in one run instead of one-by-one on the SAT portal. |
| **No e.firma needed** | Skip the SAT API's certificate requirement; this reads the public registry directly. |
| **Fixed schema** | Every RFC returns the same fields: status, name, and fiscal situation, no parsing required. |
| **Export ready** | Results land in your dataset as CSV, JSON, Excel, or XML for direct import into your ERP or accounting system. |

### How it compares

This Actor focuses on bulk SAT registry validation with no e.firma requirement, while the competitor adds Lista 69-B blacklist checks for a different compliance use case.

| Feature | ParseForge | Verificador RFC Mexico - SAT + Lista 69-B |
|---|---|---|
| Bulk RFC validation (100+ RFCs) | Yes, up to 1,000,000 per run | Up to 100 RFCs |
| SAT registration status | Yes | Yes |
| Taxpayer name (razón social) | Yes | Yes |
| Lista 69-B (EFOS) blacklist check | Not listed | Yes |
| No e.firma or SAT login required | Yes | Not listed |
| Fiscal situation status | Yes | Not listed |

### Configure the run

Drive the Actor from a list of RFC strings, and each one is validated against the SAT registry so only matched results reach your dataset. The Input tab lists every parameter.

A first run with the defaults:

```json
{
 "maxItems": 10,
 "rfcList": [
 "XAXX010101000",
 "BIMB400702BS6",
 "XEXX010101000"
 ]
}
```

A larger pull:

```json
{
 "maxItems": 200,
 "rfcList": [
 "XAXX010101000",
 "BIMB400702BS6",
 "XEXX010101000"
 ]
}
```

### Pricing

Pay-per-result: **$0.021 per result** collected. You pay only for the results written to your dataset.

| Results collected | Approximate cost |
|---|---|
| 100 results | $2.10 |
| 1,000 results | $21.00 |
| 10,000 results | $210.00 |

New Apify accounts start with $5 in free credit.

### Free users

Free-plan runs return up to 10 results as a preview. [Upgrade your Apify plan](https://console.apify.com/sign-up?fpr=vmoqkp) to collect up to 1,000,000 results per run.

### Run it

1. [Create a free Apify account with $5 in credit](https://console.apify.com/sign-up?fpr=vmoqkp).
2. Open the [Mexico RFC Validator](https://apify.com/parseforge/mexico-rfc-scraper?fpr=vmoqkp).
3. Set your inputs and any filters, then click **Start**.
4. Export the results as CSV, Excel, JSON, or XML from the **Dataset** tab.

Run it programmatically through the [Apify API](https://docs.apify.com/api/v2) (`run-sync-get-dataset-items`) or the [ApifyClient](https://docs.apify.com/api/client/js) for JavaScript and Python.

### Use with AI agents (MCP)

Give an AI agent live access to Mexico RFC Validator through the Model Context Protocol. Add the Actor to Claude, Cursor, or any MCP client:

```bash
claude mcp add --transport http apify "https://mcp.apify.com/?tools=parseforge/mexico-rfc-scraper"
```

Then prompt it in plain language to run the scraper and read back the results.

### Troubleshooting

**Why am I getting no results for my RFC list?**

Check that your RFCs are in the correct format (12 or 13 characters for persona moral, 13 for persona física). Remove any spaces, dashes, or special characters. Also confirm the maxItems setting is high enough to cover your list.

**The Actor returns 'not found' for an RFC I know is valid.**

The SAT registry may have a temporary outage or the RFC might be newly registered and not yet indexed. Wait a few hours and retry. Double-check the RFC string for typos or extra characters.

**The run is taking too long.**

Large lists of thousands of RFCs take time because each one requires a separate SAT lookup. Reduce the maxItems limit or split your list into smaller batches across multiple runs.

**I get an error about the input format.**

The RFC List input expects an array of strings. Paste one RFC per line in the string list editor. Do not include commas, quotes, or other delimiters between RFCs.

**Some RFCs return a status I don't understand.**

The Actor returns the raw status as provided by the SAT registry. Common statuses include 'Activo', 'Suspendido', or 'No encontrado'. Refer to the SAT's own documentation for the full list of fiscal situation codes.

### FAQ

| Question | Answer |
|---|---|
| Does this Actor check the Lista 69-B (EFOS) blacklist? | This Actor validates RFCs against the SAT public registry for registration status and taxpayer name. It does not check the Lista 69-B blacklist of presumed shell companies. For that, use a dedicated EFOS verification tool. |
| Do I need an e.firma or SAT login to use this? | No. This Actor reads the public SAT registry directly. You do not need an e.firma certificate, a SAT portal account, or any API credentials. |
| How many RFCs can I validate in one run? | You can validate up to one million RFCs per run. Paste your list into the RFC List input field and set the maximum records limit. |
| What does the Actor return for an invalid or unregistered RFC? | It returns the RFC along with a status indicating it is not found or not registered in the SAT database, so you can identify which IDs need correction. |
| Does it work for both persona física and persona moral RFCs? | Yes. The Actor validates both individual (persona física) and business (persona moral) RFC formats and returns the registered name for each. |
| Can I validate RFCs with foreign tax IDs or non-Mexican formats? | No. This Actor only validates Mexican RFCs against the SAT registry. Foreign tax IDs use different formats and registries. |
| What export formats are supported? | Results can be exported to CSV, JSON, Excel, or XML directly from your Apify dataset, ready for import into accounting software or ERPs. |
| Is the data real-time or cached? | Each RFC is validated against the live SAT registry at the time of the run, so you get the current registration status and taxpayer name. |
| Can I schedule recurring validations? | Yes. You can schedule the Actor to run daily, weekly, or monthly via Apify's scheduler to keep your RFC records up to date. |
| What happens if the SAT portal is slow or down? | The Actor retries failed lookups automatically. If the SAT registry is temporarily unavailable, the run may take longer or return partial results. |

### Related actors

Browse the full [ParseForge collection](https://apify.com/parseforge?fpr=vmoqkp) for more scrapers.

🆘 **Need help?** Email parseforge@protonmail.com with your run ID, your input, and what you expected.

⚠️ **Disclaimer.** This Actor is unofficial and is not affiliated with, endorsed by, or sponsored by Servicio de Administración Tributaria (SAT). It collects only publicly available data. You are responsible for using the collected data in compliance with the source's terms of service and applicable data-protection laws, including GDPR, CCPA, and PIPL. Do not use it to collect personal data unlawfully.

# Actor input Schema

## `maxItems` (type: `integer`):

Maximum number of records to collect per run.

## `rfcList` (type: `array`):

List of RFC strings to validate

## Actor input object example

```json
{
  "maxItems": 10,
  "rfcList": [
    "XAXX010101000",
    "BIMB400702BS6",
    "XEXX010101000"
  ]
}
```

# Actor output Schema

## `results` (type: `string`):

Scraped records

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "maxItems": 10,
    "rfcList": [
        "XAXX010101000",
        "BIMB400702BS6",
        "XEXX010101000"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("parseforge/mexico-rfc-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "maxItems": 10,
    "rfcList": [
        "XAXX010101000",
        "BIMB400702BS6",
        "XEXX010101000",
    ],
}

# Run the Actor and wait for it to finish
run = client.actor("parseforge/mexico-rfc-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "maxItems": 10,
  "rfcList": [
    "XAXX010101000",
    "BIMB400702BS6",
    "XEXX010101000"
  ]
}' |
apify call parseforge/mexico-rfc-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,parseforge/mexico-rfc-scraper"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/lwhfs1PEzaxIS9gHs/builds/XySOFr3HhVVFqMT0b/openapi.json