[Integrations](https://spiral.ai/integrations) › [Devin](https://spiral.ai/integrations/devin) › [OpenStreetMap element history](https://spiral.ai/integrations/devin/openstreetmap-element-history)

# How to Use OpenStreetMap element history in Devin

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.

|  |  |
| --- | --- |
| Model | OpenStreetMap element history |
| Available through | Alexandria |
| Category | Maps & Reviews |
| Price | $0.00873 per call. |
| Returns | json |
| Runs | In the background |
| Setup | About 2 minutes, no API key |

## Prompts to try with OpenStreetMap element history in Devin

- Use OpenStreetMap element history for the Tower Bridge object referenced in this project. Generate a report showing how its returned tags changed between versions.
- 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 Devin

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

### Use Spiral's MCP server

1. **Add a custom MCP**: Open Customize › MCPs. Click + and choose New MCP. Fill in:

2. **Sign in to Spiral and approve**: In Customize › MCPs, open Spiral and choose Connect. Spiral opens: sign in, pick the organization and click Authorize. No API key.

3. **Check it**: On Spiral's configuration page, click Test tools. Devin lists Spiral's tools.

### Use the Spiral skill

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

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

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

## OpenStreetMap element history tools and prices

- [OpenStreetMap · Element history](https://spiral.ai/tools/alexandria/openstreetmap-org/places/element_history) (Alexandria): $0.00873 per call.

## What can you do with OpenStreetMap element history in Devin?

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.

## Overview

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

## OpenStreetMap element history in other agents

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

## More Devin guides

- [OpenStreetMap element details](https://spiral.ai/integrations/devin/openstreetmap-element-details)
- [OpenStreetMap feature search](https://spiral.ai/integrations/devin/openstreetmap-feature-search)
- [OpenStreetMap coordinate lookup](https://spiral.ai/integrations/devin/openstreetmap-coordinate-lookup)
- [OpenStreetMap local map data](https://spiral.ai/integrations/devin/openstreetmap-local-map-data)
- [OpenStreetMap batch element lookup](https://spiral.ai/integrations/devin/openstreetmap-batch-element-lookup)
- [OpenStreetMap map edits](https://spiral.ai/integrations/devin/openstreetmap-map-edits)

## Questions about OpenStreetMap element history in Devin

**Can Devin use OpenStreetMap element history?**

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

**How much does OpenStreetMap element history cost in Devin?**

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

**Do I need an Alexandria account to use OpenStreetMap element history in Devin?**

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 Devin?**

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

**Does Devin wait while OpenStreetMap element history runs?**

OpenStreetMap element history runs in the background. Devin 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.

