# Georef Argentina — address normalize & geocoding (no key) (`synthetic.ia/georef-argentina`) Actor

Official Argentine geo-reference API: normalize/parse addresses (street, number, locality, department, province), reverse-geocode lat/lon, and look up provinces, departments, municipalities and localities. Government open data. Clean HTTP API + MCP, no key. Pay per query.

- **URL**: https://apify.com/synthetic.ia/georef-argentina.md
- **Developed by:** [Synthetic](https://apify.com/synthetic.ia) (community)
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.00 / 1,000 geo queries

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.
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?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## 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.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Georef Argentina — address normalize & geocoding (no key)

The official **Argentine geo-reference** service (Georef, `datos.gob.ar`) as a clean HTTP API (and MCP tool): **normalize/parse** an Argentine address into street, number, locality, department and province; **reverse-geocode** a lat/lon; and **look up** provinces, departments, municipalities and localities. Government open data, ideal for validating and enriching Argentine addresses — almost no one wraps this for the world. **No API key.** Pay per query.

- 🏠 **Address** — turn "Av. Corrientes 1234, CABA" into structured fields (street, number, locality, department, province) with the official nomenclature.
- 📍 **Reverse geocode** — a lat/lon → province / department / municipality.
- 🗺️ **Places** — search provinces, departments, municipalities and localities by name (and parent), with centroids.
- 🇦🇷 **Official & keyless** — the same data the Argentine state publishes.
- 💵 Pay per query · no key.

### The use case it was built for

Argentine forms, e-commerce checkouts, logistics and CRMs need clean, validated addresses. Feed a messy address string and get canonical province/department/locality back; or geocode/reverse-geocode for maps and routing. Also perfect for enriching locally-scraped listings.

### Sample output (`address`)

```json
{
  "ok": true, "input": "Av. Corrientes 1234, CABA", "count": 1,
  "addresses": [
    { "street": "AV CORRIENTES", "streetType": "AV", "number": 1234,
      "locality": "Ciudad Autónoma de Buenos Aires", "department": "Comuna 1",
      "province": "Ciudad Autónoma de Buenos Aires",
      "fullName": "AV CORRIENTES 1234, Comuna 1, Ciudad Autónoma de Buenos Aires" }
  ]
}
```

### How to use

- **HTTP API (Standby):** POST or GET `/address`, `/reverse`, `/places`. `GET /` returns help. Example: `GET /reverse?lat=-34.6037&lon=-58.3816`.
- **Normal run:** pass `{ operation, ... }`; results land in the dataset + key-value store.
- **MCP tool:** expose it to your agent via Apify's MCP server.

### Input

- **operation** — `address` · `reverse` · `places`.
- **address** — the address string. **lat / lon** — for reverse geocoding.
- **type** — (places) `province`/`department`/`municipality`/`locality`. **name / province / department** — filters. **max** — cap results.

### Pricing

**Per query** from **$0.004** (down to $0.0015 on higher tiers). One call = one query.

### Related Actors

- **[Argentina Economic Data](https://apify.com/synthetic.ia/argentina-economic-data)** — official Argentine economic time series.

### FAQ

**Do I need a key?** No — Georef is keyless Argentine government open data.

**Does it geocode to coordinates?** Address results include a location when available; use `reverse` for lat/lon → place.

**Coverage?** All of Argentina — provinces, departments, municipalities, localities and streets.

### Notes & limits

Data from the Argentine national open-data Georef API (`apis.datos.gob.ar/georef`). Address normalization quality depends on the input; provide province when known to disambiguate.

# Changelog

This Actor's version history is a separate document: https://apify.com/synthetic.ia/georef-argentina/changelog.md

# Actor input Schema

## `operation` (type: `string`):

What to do.

## `address` (type: `string`):

Argentine address, e.g. Av. Corrientes 1234, CABA.

## `lat` (type: `string`):

Latitude for reverse geocoding.

## `lon` (type: `string`):

Longitude for reverse geocoding.

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

Administrative level.

## `name` (type: `string`):

Filter places by name.

## `province` (type: `string`):

Restrict to a province (name or id).

## `department` (type: `string`):

Restrict municipalities/localities to a department.

## `max` (type: `integer`):

Max results.

## Actor input object example

```json
{
  "operation": "address",
  "address": "Av. Corrientes 1234, CABA",
  "lat": "-34.6037",
  "lon": "-58.3816",
  "type": "province",
  "max": 10
}
```

# Actor output Schema

## `result` (type: `string`):

No description

## `runs` (type: `string`):

No description

# 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 = {
    "address": "Av. Corrientes 1234, CABA",
    "lat": "-34.6037",
    "lon": "-58.3816"
};

// Run the Actor and wait for it to finish
const run = await client.actor("synthetic.ia/georef-argentina").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 = {
    "address": "Av. Corrientes 1234, CABA",
    "lat": "-34.6037",
    "lon": "-58.3816",
}

# Run the Actor and wait for it to finish
run = client.actor("synthetic.ia/georef-argentina").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 '{
  "address": "Av. Corrientes 1234, CABA",
  "lat": "-34.6037",
  "lon": "-58.3816"
}' |
apify call synthetic.ia/georef-argentina --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,synthetic.ia/georef-argentina"
        }
    }
}
```

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/jJ4jmUwRYGzUaASOy/builds/Kgj2dQpP9IOBDTgvI/openapi.json