[Integrations](https://spiral.ai/integrations) › [Manus](https://spiral.ai/integrations/manus) › [OpenAddresses source history](https://spiral.ai/integrations/manus/openaddresses-source-history)

# How to Use OpenAddresses source history in Manus

Returns a source's processing jobs, including dates, outcomes, and address counts. Use it to investigate count changes or select an earlier available output for comparison.

|  |  |
| --- | --- |
| Model | OpenAddresses source history |
| Available through | Alexandria |
| Category | Listings |
| Price | $0.00873 per call. |
| Returns | json |
| Runs | In the background |
| Setup | About 2 minutes, no API key |

## Prompts to try with OpenAddresses source history in Manus

- Use OpenAddresses source history to compare the available successful processing runs for Bristol Bay Borough, Alaska, by date and address count.
- Use OpenAddresses source history to look this up and give me the result as a table.
- Pull the latest numbers from OpenAddresses source history and tell me what changed since last week.
- Check OpenAddresses source history and summarize what you find in three bullet points.
- Pull the newest data from OpenAddresses source history and give me the result as a table.

## How to set up OpenAddresses source history in Manus

Pick the way that suits you. Each takes about two minutes.

### Use the Manus connector

1. **Add a custom MCP connector**: In Manus open Settings › Connectors (or the connectors icon under the chat box), then Add connectors › Custom MCP and Add MCP by URL. Name it Spiral, set Transport to HTTP and paste this Server URL:

```text
https://api.spiral.ai/mcp
```

2. **Sign in to Spiral and approve**: Manus asks you to sign in the first time it uses Spiral. Spiral opens: sign in, pick the organization and click Authorize. No API key. Spiral gives the connection its own key; Manus never sees it, and you can remove it under Settings › Connected apps in the console.

### Use the Spiral skill

1. **Send Manus this message**: Your agent reads Spiral's skill and sets itself up.

```
set up https://spiral.ai/SKILL.md
```

2. **Sign in or paste a key**: Approve Spiral in the browser, or give the agent a key from the console.

### Use the Spiral CLI

1. **Install and sign in**: Installs the Spiral CLI, signs you in and adds its skill to your coding agents.

```bash
npx -y spiral-cli@latest init
```

### Call the Spiral API

1. **Create an API key**: In the console, under API keys.

2. **Run OpenAddresses source history**: One request; the result comes back by polling or a webhook.

```bash
curl https://api.spiral.ai/v1/runs \
  -H "Authorization: Bearer $SPIRAL_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
    "provider": "alexandria",
    "model": "batch-openaddresses-io/addresses/source_history",
    "input": {
      "name": "<name>"
    }
  }'
```

Then paste one of the prompts above: Manus finds OpenAddresses source history on Spiral, shows the price and runs it.

Setup guide in the docs: https://spiral.ai/docs/quickstarts/manus

## OpenAddresses source history tools and prices

- [OpenAddresses per-source runs · Source history](https://spiral.ai/tools/alexandria/batch-openaddresses-io/addresses/source_history) (Alexandria): $0.00873 per call.

## Settings you can ask for

| Setting | Allowed values | Default | Description |
| --- | --- | --- | --- |
| name |  | — | Coverage name when a source has more than one data entry per layer (e.g. `us/mn/statewide` addresses has `default` and `state`); the function says so when it is needed. |
| layer | addresses, buildings, parcels, centerlines | addresses | OpenAddresses layer of the source. This program shapes `addresses` rows; other layers are listed and status-checked but their records are not decoded. |
| limit | 1 to 500 | 100 | Keep the newest N jobs. |
| source |  | — | OpenAddresses source path, e.g. `us/ak/bristol_bay_borough` or `us/me/statewide` (lowercase `<country>/<region>/<name>`, no `.json`). Pattern: ^[a-z]{2}(/[a-z0-9_.-]+){1,3}$. |
| status | Success, all | all | `Success` keeps only successful jobs. |
| data_id | 1 to … | — | Data entry id; when given, `source` is ignored for the lookup. |

## What can you do with OpenAddresses source history in Manus?

Assess whether OpenAddresses has suitable source data for a local mapping project. A chat agent can explain available publications, processing history, and address samples in one research conversation.

### Monitor address publication changes

Compare source publication details on a schedule and consult processing history when a new output appears. Report changes in processing outcomes and address counts.

### Investigate an address count drop

Use job history to locate a count change, then inspect the current publication and its address rows. Reread examples from the collected output to help distinguish processing problems from changes in the available data.

### Create a reproducible geocoding benchmark

Choose an available processing job and collect its address rows as a benchmark dataset. Reread selected records from that publication when investigating changes in a geocoder's results.

### Compare address sources for a region

List geographic sources, compare their publication details and processing histories, and examine address samples. Use the results to choose which source to evaluate for a regional mapping project.

### Review source availability

Inventory the sources serving a region and compare their current publications with their processing histories. Identify sources that need investigation before the next address import.

## Overview

- [Alexandria](https://spiral.ai/providers/alexandria)
- [All Manus guides](https://spiral.ai/integrations/manus)

## OpenAddresses source history in other agents

- [Amp](https://spiral.ai/integrations/amp/openaddresses-source-history)
- [ChatGPT](https://spiral.ai/integrations/chatgpt/openaddresses-source-history)
- [Claude](https://spiral.ai/integrations/claude-desktop/openaddresses-source-history)
- [Claude Code](https://spiral.ai/integrations/claude-code/openaddresses-source-history)
- [Cline](https://spiral.ai/integrations/cline/openaddresses-source-history)
- [Codex](https://spiral.ai/integrations/codex/openaddresses-source-history)
- [Cursor](https://spiral.ai/integrations/cursor/openaddresses-source-history)
- [Devin](https://spiral.ai/integrations/devin/openaddresses-source-history)
- [dots](https://spiral.ai/integrations/dots/openaddresses-source-history)
- [Factory Droid](https://spiral.ai/integrations/factory-droid/openaddresses-source-history)
- [Gemini](https://spiral.ai/integrations/gemini/openaddresses-source-history)
- [Gemini CLI](https://spiral.ai/integrations/gemini-cli/openaddresses-source-history)
- [Google Antigravity](https://spiral.ai/integrations/antigravity/openaddresses-source-history)
- [goose](https://spiral.ai/integrations/goose/openaddresses-source-history)
- [Grok](https://spiral.ai/integrations/grok/openaddresses-source-history)
- [Grok Build](https://spiral.ai/integrations/grok-build/openaddresses-source-history)
- [Hermes](https://spiral.ai/integrations/hermes/openaddresses-source-history)
- [Instinct](https://spiral.ai/integrations/instinct/openaddresses-source-history)
- [Muse](https://spiral.ai/integrations/muse/openaddresses-source-history)
- [Muse Code](https://spiral.ai/integrations/muse-code/openaddresses-source-history)
- [n8n](https://spiral.ai/integrations/n8n/openaddresses-source-history)
- [Notion](https://spiral.ai/integrations/notion/openaddresses-source-history)
- [OpenClaw](https://spiral.ai/integrations/openclaw/openaddresses-source-history)
- [opencode](https://spiral.ai/integrations/opencode/openaddresses-source-history)
- [Perplexity](https://spiral.ai/integrations/perplexity/openaddresses-source-history)
- [Raycast](https://spiral.ai/integrations/raycast/openaddresses-source-history)
- [VS Code](https://spiral.ai/integrations/vscode/openaddresses-source-history)
- [Windsurf](https://spiral.ai/integrations/windsurf/openaddresses-source-history)
- [Zapier](https://spiral.ai/integrations/zapier/openaddresses-source-history)

## More Manus guides

- [OpenAddresses source catalog](https://spiral.ai/integrations/manus/openaddresses-source-catalog)
- [OpenAddresses source status](https://spiral.ai/integrations/manus/openaddresses-source-status)
- [OpenAddresses address record](https://spiral.ai/integrations/manus/openaddresses-address-record)
- [Oregon contractor license details](https://spiral.ai/integrations/manus/oregon-contractor-license-details)
- [OpenAddresses address points](https://spiral.ai/integrations/manus/openaddresses-address-points)
- [Oregon contractor search](https://spiral.ai/integrations/manus/oregon-contractor-search)

## Questions about OpenAddresses source history in Manus

**Can Manus use OpenAddresses source history?**

Yes. Add Spiral to Manus as an MCP server, and Manus can find and run OpenAddresses source history like any built-in tool.

**How much does OpenAddresses source history cost in Manus?**

$0.00873 per call. You pay from your Spiral balance as you go, with no subscription, and a failed run is not charged. Your Manus plan is separate.

**Do I need an Alexandria account to use OpenAddresses source history in Manus?**

No. Spiral runs OpenAddresses source history on its own Alexandria account. You sign in to Spiral once and never paste a key.

**How long does it take to set up OpenAddresses source history in Manus?**

About two minutes: add a custom MCP connector, then sign in to Spiral and approve.

**Does Manus wait while OpenAddresses source history runs?**

OpenAddresses source history runs in the background. Manus starts the run, checks on it and gives you the json when it's ready.

**Where does OpenAddresses get its data?**

OpenAddresses collects authoritative geographic data from existing publishers. It does not create its own address data.

**Is OpenAddresses limited to US addresses?**

No. OpenAddresses includes geographic sources from around the world, so research can extend beyond US counties and states.

**How often is OpenAddresses refreshed?**

Its processing library runs the dataset weekly and on demand. That schedule describes OpenAddresses processing, not how often an original publisher edits its address records.

**Are all address coordinates equally precise?**

OpenAddresses defines accuracy categories that include interpolation, coded 4, and unknown accuracy, coded 5. Those categories make a blanket rooftop-accuracy assumption inappropriate.

**Does one license cover every OpenAddresses dataset?**

Each source retains its own license. For example, the San Francisco address source specifies PDDL 1.0, so reuse terms need to be checked for the geographic source you select.

