Spiral gives your agent every tool with one account. Browse the tools →

Factory Droid · Maps & Reviews

How to Use OpenStreetMap element history in Factory Droid

Returns earlier versions of a map object in version order. Use it to trace how a road, building, or public place changed, rather than inspecting only its current record.

Prompts to try with OpenStreetMap element history in Factory Droid

Copy an example into Factory Droid, or ask in your own words.

Use OpenStreetMap element history for the Tower Bridge object referenced in this project. Generate a report showing how its returned tags changed between versions.

OpenStreetMap element historyFactory Droid
Try asking
  • Use OpenStreetMap element history to look this up and give me the result as a table. Save the result in ./assets.

  • Pull the latest numbers from OpenStreetMap element history and tell me what changed since last week.

  • Check OpenStreetMap element history and summarize what you find in three bullet points.

  • Pull the newest data from OpenStreetMap element history and give me the result as a table.

How to set up OpenStreetMap element history in Factory Droid

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

Use Spiral's MCP server

  1. Add the server

    Droid saves it to your user config, ~/.factory/mcp.json, so it works in every project.

    droid mcp add spiral https://api.spiral.ai/mcp --type http
  2. Sign in

    Start droid, type /mcp, select spiral and authenticate it. Sign in to Spiral in the browser and click Authorize. No API key.

  3. Check it

    Spiral shows as connected. needs authentication means the sign-in did not finish: run /mcp again.

    droid mcp list

Use the Spiral skill

  1. Send Factory Droid 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.

    npx -y spiral-cli@latest init

Call the Spiral API

  1. Create an API key

    In the console, under API keys.

  2. Run OpenStreetMap element 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": "openstreetmap-org/places/element_history",
        "input": {
          "id": 1,
          "type": "node"
        }
      }'

Then paste one of the prompts above: Factory Droid finds OpenStreetMap element history on Spiral, shows the price and runs it.

OpenStreetMap element history providers and prices

Spiral runs OpenStreetMap element history through Alexandria. Open a card for today's price, with every fee included.

AlexandriaMaps & Reviews
OpenStreetMap · Element history
openstreetmap-org/places/element_history

Settings you can ask for

Ask Factory Droid for any of these in your prompt.

SettingAllowed valuesDefaultDescription
IDa number from 1

Numeric OSM element id.

Typenode, way, or relation

OSM element type.

Every API field of OpenStreetMap · Element history is on its tool page: open its card above.

What can you do with OpenStreetMap element history in Factory Droid?

Build a reviewable map-data audit for a public district in your project. Use OpenStreetMap locations, feature records, or editing evidence to explain what the returned data supports.

Investigate an unexpected map change

Compare a changed public feature with its earlier versions, surrounding map data, nearby edit sessions, and reported map problems.

Review accessibility mapping

Inspect available accessibility tags on public amenities, compare saved records, trace relevant edits, and collect map reports for human review.

Check an administrative boundary

Locate a municipality, inspect its mapped boundary and nearby features, then review object history and edit sessions when the boundary changes.

Investigate a station map discrepancy

Compare saved station-area records with current objects, inspect the surrounding block, and use history, edit sessions, and issue reports to explain discrepancies.

Questions about OpenStreetMap element history in Factory Droid

Can Factory Droid use OpenStreetMap element history?

Yes. Add Spiral to Factory Droid as an MCP server, and Factory Droid can find and run OpenStreetMap element history like any built-in tool.

How much does OpenStreetMap element history cost in Factory Droid?

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

Do I need an Alexandria account to use OpenStreetMap element history in Factory Droid?

No. Spiral runs OpenStreetMap element 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 OpenStreetMap element history in Factory Droid?

About two minutes: add the server, then sign in, then check it.

Does Factory Droid wait while OpenStreetMap element history runs?

OpenStreetMap element history runs in the background. Factory Droid starts the run, checks on it and gives you the json when it's ready.

Which parts of the world does OpenStreetMap cover?

OpenStreetMap has worldwide scope, including roads, trails, cafés, and railway stations. Its records come from a community of contributors.

Does worldwide coverage mean every local feature is mapped?

No. OpenStreetMap's accuracy documentation says basic map coverage is still being built in many areas, so a local result set cannot establish that every feature is present.

How frequently are OpenStreetMap changes distributed?

OpenStreetMap publishes minute, hourly, and daily change files. Those replication intervals do not establish one refresh schedule for every service that uses the data.

Are these map images or underlying geographic records?

OpenStreetMap's editing API exposes raw geographic data. Nodes, ways, and relations describe the underlying features rather than a rendered map image.

Is an OpenStreetMap number enough to identify a feature?

No. Nodes, ways, and relations have separate ID spaces, so retain the object type alongside the number.

Get started

Start using OpenStreetMap element history in Factory Droid

One Spiral account for every tool your agent needs. No subscription; you pay per run.

Paste this into Factory Droid:

Set up Factory Droid

set up https://spiral.ai/SKILL.md
Are you an AI agent? See setup options