Rutificador Chile API - Buscar RUT por Nombre y Nombre por RUT

Use this Apify Actor as a Rutificador Chile API to search Chilean RUT records by RUT number or by full name. It helps with common workflows such as buscar RUT por nombre, buscar nombre por RUT, consulta RUT Chile, Nombre Rut y Firma, RUT finder Chile, and structured Chilean RUT lookup from the Apify platform.

The Actor queries the public nombrerutyfirma.com flow, normalizes common RUT formats, returns structured rows, and exports results to an Apify Dataset. You can download the data as JSON, CSV, Excel, XML, or consume it through the Apify API.

Related searches: Rutificador Chile, RUT Chile API, buscar RUT Chile, buscar RUT por nombre Chile, buscar nombre por RUT Chile, consulta RUT, verificar RUT Chile, Nombre Rut y Firma scraper, rutificador online, Chilean RUT lookup, RUT lookup API, Chile identity data lookup.

What Is This Actor For?

This Actor is designed for Chile RUT lookup tasks in internal data quality, CRM cleanup, lead deduplication, supplier onboarding support, contact record validation, API workflows, and bulk lookup jobs that need auditable results.

It is not an official government API. It packages the public Nombre Rut y Firma lookup flow into a cleaner Apify API, dataset, JSON and CSV output.

Main Features

• Search RUT by full name: buscar RUT por nombre.
• Search full name by Chilean RUT: buscar nombre por RUT.
• Query Nombre Rut y Firma and return clean structured data.
• Normalize RUT inputs with dots, without dots, with hyphen, or compact format.
• Calculate a missing verification digit when the base RUT is valid.
• Process one lookup or a controlled batch of lookups.
• Return clear success, no_results, and failed statuses.
• Export results to Apify Dataset, JSON, CSV, Excel, XML, or API.
• Use residential Chile proxy rotation by default for better reliability.

Typical Use Cases

Use case	How this Rutificador Actor helps
CRM enrichment in Chile	Add structured RUT, name, location, source, and status metadata to Chilean records for internal workflows.
Lead deduplication	Compare RUTs and names to reduce duplicate records in Chilean contact databases.
Supplier onboarding	Check submitted Chilean RUT or name data as one signal in an onboarding workflow.
Customer onboarding support	Compare user-submitted RUT/name combinations inside your own data matching process.
Data cleanup	Normalize inconsistent RUT values before storing, matching, or exporting them.
Data workflows	Run auditable Chile RUT lookups and export results to CSV, JSON, Excel or the Apify API.
Bulk lookup QA	Submit batches of RUT and name queries and review status, errors, and result counts for each item.

Output Data

Each dataset row can include:

Field	Description
search_type	Query mode: rut or nombre.
query_index	Position of the input query in the batch.
status	success, no_results, or failed.
search_term	Normalized RUT or name used for the lookup.
total_results	Number of rows found for the query.
name	Full name returned by the source.
rut	Chilean RUT returned by the source.
sex	Sex marker reported by the source, usually VAR, MUJ, or N/A.
address	Address when available from the source.
city	City or commune when available from the source.
source	URL queried.
scraped_at	Extraction timestamp.
error	Error detail when a query fails.

Example successful dataset item:

{
  "query_index": 0,
  "status": "success",
  "error": null,
  "search_type": "rut",
  "search_term": "<RUT_CHILENO>",
  "total_results": 1,
  "name": "<NOMBRE_APELLIDO>",
  "rut": "<RUT_CHILENO>",
  "sex": "N/A",
  "address": "No Disponible",
  "city": "No Disponible",
  "source": "https://www.nombrerutyfirma.com/rut_ext?term=%3CRUT_CHILENO%3E",
  "scraped_at": "2026-05-10T16:36:21"
}

If a lookup has no match, the Actor still writes an operational row so batch runs are easy to audit:

{
  "query_index": 0,
  "status": "no_results",
  "error": null,
  "search_type": "rut",
  "search_term": "<RUT_CHILENO>",
  "total_results": 0,
  "name": null,
  "rut": null,
  "sex": null,
  "address": null,
  "city": null
}

Quick Start

1. Open the Actor on Apify.
2. Click Try for free or Run.
3. Add one or more items to queries.
4. Start the run.
5. Open the Dataset tab to download JSON, CSV, Excel, or XML.

Minimal input for searching by RUT:

{
  "queries": [
    {
      "searchType": "rut",
      "term": "<RUT_CHILENO>"
    }
  ]
}

Search RUT by name:

{
  "queries": [
    {
      "searchType": "nombre",
      "term": "<NOMBRE_APELLIDO>"
    }
  ]
}

Batch lookup:

{
  "queries": [
    {
      "searchType": "rut",
      "term": "<RUT_CHILENO>"
    },
    {
      "searchType": "nombre",
      "term": "<NOMBRE_APELLIDO>"
    }
  ],
  "allowPartialResults": true,
  "proxyAttempts": 5
}

Accepted Chile RUT Formats

Users often paste Chilean RUTs in different formats. This Actor normalizes common variants before querying:

User input	Normalized query
<RUT_CHILENO>	<RUT_CHILENO>
<RUT_SIN_PUNTOS>	<RUT_CHILENO>
<RUT_COMPACTO>	<RUT_CHILENO>
<RUT_CON_ESPACIOS>	<RUT_CHILENO>
RUT <RUT_CHILENO>	<RUT_CHILENO>
<RUT_SIN_DV>	<RUT_CHILENO> when the missing verification digit can be calculated

If the input contains an explicit but invalid verification digit, the query is marked as failed with a clear error message.

Input Reference

Field	Type	Required	Description
queries	array	yes	List of lookups to run. Each item must include searchType and term.
queries[].searchType	string	yes	Use rut to search by RUT, or nombre to search by name. API calls also accept name as an alias for nombre.
queries[].term	string	yes	RUT or name to query. Accepted RUT examples: <RUT_CHILENO>, <RUT_SIN_PUNTOS>, <RUT_COMPACTO>, <RUT_SIN_DV>.
timeoutSecs	integer	no	Maximum seconds to wait for each upstream page. Default: 30.
proxyAttempts	integer	no	Number of residential proxy sessions to try per query. Default: 5.
allowPartialResults	boolean	no	If true, failed queries are saved with status: failed and the batch continues. Default: true.
proxyConfiguration	object	no	Apify proxy configuration. Residential Chile proxy is used by default unless custom proxyUrls are provided.
debugVisible	boolean	no	Local development only. Must stay disabled in Apify cloud.

Run From The Apify API

Python

from apify_client import ApifyClient

client = ApifyClient("<APIFY_API_TOKEN>")

run = client.actor("scraperschile/rutificador").call(
    run_input={
        "queries": [
            {"searchType": "rut", "term": "<RUT_CHILENO>"},
            {"searchType": "nombre", "term": "<NOMBRE_APELLIDO>"},
        ],
        "allowPartialResults": True,
    }
)

for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

cURL

curl -X POST \
  -H 'Content-Type: application/json' \
  -H 'Authorization: Bearer <APIFY_API_TOKEN>' \
  -d '{
    "queries": [
      { "searchType": "rut", "term": "<RUT_CHILENO>" },
      { "searchType": "nombre", "term": "<NOMBRE_APELLIDO>" }
    ],
    "allowPartialResults": true
  }' \
  'https://api.apify.com/v2/acts/scraperschile~rutificador/runs?waitForFinish=60'

Reliability

This Actor queries an upstream public website in real time. Coverage, freshness, address availability, response times, and success rate depend on that upstream source and its availability.

To make production runs easier to operate, the Actor includes:

• Residential Chile proxy configuration by default.
• Per-query proxy rotation with proxyAttempts.
• A lightweight HTTP path first, then browser fallback when needed.
• Headless Playwright browser fallback.
• Blocking of heavy browser resources such as images, fonts, stylesheets, and media.
• Partial result mode for batch runs.
• Explicit statuses for every query.

The Actor does not maintain its own private index, does not perform background sync, and does not send email notifications for missing records.

Technical Details

• Built with the Apify Python SDK.
• Uses Playwright for Cloudflare-protected flows.
• Parses the results table from nombrerutyfirma.com.
• Normalizes RUT input to dotted Chilean format when possible.
• Saves all rows to the default Apify Dataset.
• Stores an OUTPUT key-value record with the full run payload.
• Designed for API lookups, CSV/JSON exports, and controlled bulk jobs.

Pricing

Pricing is displayed in the Apify pricing panel for each run. The Actor is prepared for pay-per-success pricing: when the successful-rut-result event is active in Apify, successful records can be charged separately from operational rows.

• Actor start: low fixed start event.
• Successful result: ready to map to successful-rut-result.
• No result or failed query: still saved to the dataset for visibility and bulk QA.

Data Source Notes

This Actor structures the public nombrerutyfirma.com lookup flow into Apify Dataset, JSON, CSV, Excel and API output. It is built for integrations, data cleanup, CRM enrichment, deduplication and controlled bulk lookup workflows. It is not an official government API.

FAQ

Can I search RUT Chile by name?

Yes. Set searchType to nombre and provide the full name in term. The Actor returns possible matches from the source, including RUT and available metadata.

Can I search name by RUT?

Yes. Set searchType to rut and provide the Chilean RUT in term. The Actor accepts common formats with or without dots and hyphen.

Is this an official Chile government API?

No. This is not an official government API. It is an Apify Actor that structures results from the public nombrerutyfirma.com lookup flow.

Does this Actor scrape Nombre Rut y Firma?

Yes. It structures the public lookup flow from nombrerutyfirma.com into clean Apify Dataset rows for RUT and name queries.

Does it support bulk RUT lookups?

Yes. Add multiple objects to queries. Each query gets its own query_index, status, error, and result count.

Why use this instead of manual lookup?

Manual lookup is slow, hard to audit, and difficult to integrate. This Actor returns structured JSON/CSV data, exposes an API, and records success or failure for each query.

What happens if the source blocks a request?

The Actor uses residential Chile proxy rotation and retries. If a query still fails and allowPartialResults is enabled, the failed query is saved to the dataset with an error message.