# US Address Geocoder: Census Bureau Lookup (`naimurhasanrwd/census-geocoder-scraper`) Actor

Geocode US street addresses to coordinates and standardised components via the official US Census Bureau geocoder. No login, no proxy, no browser.

- **URL**: https://apify.com/naimurhasanrwd/census-geocoder-scraper.md
- **Developed by:** [Naimur Hasan](https://apify.com/naimurhasanrwd) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per usage

This Actor is paid per platform usage. The Actor is free to use, and you only pay for the Apify platform usage, which gets cheaper the higher subscription plan you have.

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

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

## US Address Geocoder

Geocodes US street addresses to coordinates and standardised components
through the official US Census Bureau geocoder. No login, no proxy, no
browser, no API key.

### Input

| Field | Type | Notes |
|---|---|---|
| `addresses` | array | Required. One-line US addresses, e.g. `1600 Pennsylvania Ave NW, Washington, DC`. |

### Output

One row per match: `inputAddress`, `matchedAddress`, `latitude`,
`longitude`, `fromAddress`, `toAddress`, `preDirection`, `streetName`,
`suffixType`, `suffixDirection`, `city`, `state`, `zip`, `tigerLineId`,
`tigerLineSide`.

### Notes

- **The API returns coordinates as `x` and `y`, where `x` is longitude and
  `y` is latitude.** Reading them positionally in the wrong order is the
  classic way to land every US address in the Indian Ocean, so they are named
  explicitly here.
- `inputAddress` is kept next to `matchedAddress` so you can see what the
  geocoder decided you meant. The match is standardised and uppercased, and it
  is not always the address you submitted.
- An address can return more than one candidate match, so the row count can
  exceed the number submitted. Unmatched addresses are logged and skipped; the
  run only fails if nothing matched at all.
- Coverage is US-only, and `fromAddress`/`toAddress` describe the *block
  range* the match sits in, not the building — this is street-segment
  interpolation, not rooftop accuracy.
- The underlying TIGER data lags reality, so newer and corporate addresses can
  legitimately return no match while the street around them geocodes fine —
  `1 Apple Park Way, Cupertino, CA` is one such miss. Treat a no-match as
  "not in this dataset", not as "not a real address".

# Actor input Schema

## `addresses` (type: `array`):

One-line US street addresses, e.g. 1600 Pennsylvania Ave NW, Washington, DC

## Actor input object example

```json
{
  "addresses": [
    "1600 Pennsylvania Ave NW, Washington, DC",
    "350 Fifth Ave, New York, NY"
  ]
}
```

# Actor output Schema

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

Every address match the run produced.

# 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 = {
    "addresses": [
        "1600 Pennsylvania Ave NW, Washington, DC",
        "350 Fifth Ave, New York, NY"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("naimurhasanrwd/census-geocoder-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 = { "addresses": [
        "1600 Pennsylvania Ave NW, Washington, DC",
        "350 Fifth Ave, New York, NY",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("naimurhasanrwd/census-geocoder-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 '{
  "addresses": [
    "1600 Pennsylvania Ave NW, Washington, DC",
    "350 Fifth Ave, New York, NY"
  ]
}' |
apify call naimurhasanrwd/census-geocoder-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,naimurhasanrwd/census-geocoder-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/5Lcm1WHVDNftHk3Wj/builds/pHLYADrC49z9rxs2w/openapi.json