How to Use OpenAddresses source history in OpenClaw
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.
Prompts to try with OpenAddresses source history in OpenClaw
Copy an example into OpenClaw, or ask in your own words.
Every Monday, use OpenAddresses source history for Bristol Bay Borough, Alaska, and report new processing outcomes and address count changes.
Every Monday at 9am: 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 OpenClaw
Pick the way that suits you. Each takes about two minutes.
Use the Spiral skill
- Send OpenClaw this message
Your agent reads Spiral's skill and sets itself up.
set up https://spiral.ai/SKILL.md
- Sign in or paste a key
Approve Spiral in the browser, or give the agent a key from the console.
Use Spiral's MCP server
- Add the server
On the machine that runs OpenClaw's Gateway:
openclaw mcp add spiral \ --url https://api.spiral.ai/mcp \ --transport streamable-http \ --auth oauth
- Sign in
In Settings › MCP, select Sign in on the Spiral server, sign in to Spiral and click Authorize. No API key.
openclaw mcp login spiral
- Reload and check
A running Gateway may keep its old tool list: restart it, or Save & Publish in the Control UI.
openclaw mcp reload openclaw mcp doctor spiral --probe
Use the Spiral CLI
- Install and sign in
Installs the Spiral CLI, signs you in and adds its skill to your coding agents.
npx -y spiral-cli@latest init
Call the Spiral API
- Create an API key
In the console, under API keys.
- Run OpenAddresses source history
One request; the result comes back by polling or a webhook.
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: OpenClaw finds OpenAddresses source history on Spiral, shows the price and runs it.
OpenAddresses source history providers and prices
Spiral runs OpenAddresses source history through Alexandria. Open a card for today's price, with every fee included.
Settings you can ask for
Ask OpenClaw for any of these in your prompt.
| Setting | Allowed values | Default | Description |
|---|---|---|---|
| Layer | addresses, buildings, parcels, or centerlines | addresses | OpenAddresses layer of the source. This program shapes |
| Limit | 1 to 500 | 100 | Keep the newest N jobs. |
| Status | Success or all | all |
|
| Data ID | a number from 1 | Data entry id; when given, |
Every API field of OpenAddresses per-source runs · Source history is on its tool page: open its card above.
What can you do with OpenAddresses source history in OpenClaw?
Maintain a recurring report on OpenAddresses publications for a region. An always-on agent can compare source availability, processing outcomes, and address samples across scheduled checks.
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.
More on OpenAddresses source history and OpenClaw
Overview
OpenAddresses source history in other agents
Questions about OpenAddresses source history in OpenClaw
Can OpenClaw use OpenAddresses source history?
Yes. Add Spiral to OpenClaw as an MCP server, and OpenClaw can find and run OpenAddresses source history like any built-in tool.
How much does OpenAddresses source history cost in OpenClaw?
$0.00873 per call. You pay from your Spiral balance as you go, with no subscription, and a failed run is not charged. Your OpenClaw plan is separate.
Do I need an Alexandria account to use OpenAddresses source history in OpenClaw?
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 OpenClaw?
About two minutes: add the server, then sign in, then reload and check.
Does OpenClaw wait while OpenAddresses source history runs?
OpenAddresses source history runs in the background. OpenClaw 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.
Start using OpenAddresses source history in OpenClaw
One Spiral account for every tool your agent needs. No subscription; you pay per run.
Paste this into OpenClaw:
set up https://spiral.ai/SKILL.md


