How to Use OpenAddresses address points in Muse Code
Returns pages of address rows from one geographic source, pinned to one processing job. Use it to build a local address index or collect points within a geographic area.
Prompts to try with OpenAddresses address points in Muse Code
Copy an example into Muse Code, or ask in your own words.
Use OpenAddresses address points to collect a sample from us/ak/bristol_bay_borough, then compare its returned address components with this project's database schema.
Use OpenAddresses address points to look this up and give me the result as a table. Save the result in ./assets.
Pull the latest numbers from OpenAddresses address points and tell me what changed since last week.
Check OpenAddresses address points and summarize what you find in three bullet points.
Pull the newest data from OpenAddresses address points and give me the result as a table.
How to set up OpenAddresses address points in Muse Code
Pick the way that suits you. Each takes about two minutes.
Use Spiral's MCP server
- Install Muse Code
curl -fsSL https://dev.meta.ai/install.sh | bash
- Ask Muse to add the server
Start muse and ask:
Add the Spiral MCP server at https://api.spiral.ai/mcp
- Sign in
In your terminal, run:
muse mcp login spiral
Use the Spiral skill
- Send Muse Code 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 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 address points
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/records_list", "input": { "source": "<source>" } }'
Then paste one of the prompts above: Muse Code finds OpenAddresses address points on Spiral, shows the price and runs it.
OpenAddresses address points providers and prices
Spiral runs OpenAddresses address points through Alexandria. Open a card for today's price, with every fee included.
Settings you can ask for
Ask Muse Code 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 |
| Page size | 1 to 1000 | 500 | Rows per page in whole-file mode (tile mode returns one z14 tile per page). |
Every API field of OpenAddresses per-source runs · Records list is on its tool page: open its card above.
What can you do with OpenAddresses address points in Muse Code?
Build a local address index with a defined OpenAddresses publication behind each import. A coding agent can inspect geographic sources, compare processing history, and examine address rows while adapting the project's geocoding code.
Build a local geocoding index
Find a geographic source, check its publication, and collect its address points. Inspect selected rows before importing street numbers, street names, and coordinates into a local search index.
Assess coverage for a municipal map
Discover county and statewide sources, inspect their available publications, and collect points for the map area. Reread sample rows to check the address components your map needs.
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.
Prepare an address extract for reuse
Find a source and review its license classification before selecting a publication. Collect the address extract and inspect sample records alongside the original source's reuse terms.
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.
More on OpenAddresses address points and Muse Code
Overview
OpenAddresses address points in other agents
Questions about OpenAddresses address points in Muse Code
Can Muse Code use OpenAddresses address points?
Yes. Add Spiral to Muse Code as an MCP server, and Muse Code can find and run OpenAddresses address points like any built-in tool.
How much does OpenAddresses address points cost in Muse Code?
$0.00873 per call. You pay from your Spiral balance as you go, with no subscription, and a failed run is not charged. Your Muse Code plan is separate.
Do I need an Alexandria account to use OpenAddresses address points in Muse Code?
No. Spiral runs OpenAddresses address points 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 address points in Muse Code?
About two minutes: install Muse Code, then ask Muse to add the server, then sign in.
Does Muse Code wait while OpenAddresses address points runs?
OpenAddresses address points runs in the background. Muse Code 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 address points in Muse Code
One Spiral account for every tool your agent needs. No subscription; you pay per run.
Paste this into Muse Code:
set up https://spiral.ai/SKILL.md


