[Integrations](https://spiral.ai/integrations) › [Cursor](https://spiral.ai/integrations/cursor) › [Stack Exchange post edit history](https://spiral.ai/integrations/cursor/stack-exchange-post-edit-history)

# How to Use Stack Exchange post edit history in Cursor

Retrieves recorded revisions of a question or answer, including edited content and edit comments. Use it to explain how a cited solution changed; several edits can collapse into one revision.

|  |  |
| --- | --- |
| Model | Stack Exchange post edit history |
| Available through | Alexandria |
| Category | Social Media |
| Price | $0.00873 per call. |
| Returns | json |
| Runs | In the background |
| Setup | About 2 minutes, no API key |

## Prompts to try with Stack Exchange post edit history in Cursor

- Use Stack Exchange post edit history for https://stackoverflow.com/a/1732454 and summarize recorded changes that affect any explanation we cite in our parsing guide.
- Use Stack Exchange post edit history to look this up and give me the result as a table. Save the result in ./assets.
- Pull the latest numbers from Stack Exchange post edit history and tell me what changed since last week.
- Check Stack Exchange post edit history and summarize what you find in three bullet points.
- Pull the newest data from Stack Exchange post edit history and give me the result as a table.

## How to set up Stack Exchange post edit history in Cursor

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

### Use Spiral's MCP server

1. **Add the hosted server**: Use Add to Cursor on the console's Agents & MCP page, or add this to `.cursor/mcp.json` (one project) or `~/.cursor/mcp.json` (every project):

```json
{
  "mcpServers": {
    "spiral": { "url": "https://api.spiral.ai/mcp" }
  }
}
```

2. **Sign in**: Open Cursor Settings › MCP, click Connect next to spiral, sign in to Spiral and click Authorize. No API key. Spiral then shows as connected, with its tools listed.

### Use the Spiral skill

1. **Send Cursor 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 Stack Exchange post edit 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": "stackexchange-com/questions/revisions",
    "input": {
      "post_id": 1
    }
  }'
```

Then paste one of the prompts above: Cursor finds Stack Exchange post edit history on Spiral, shows the price and runs it.

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

## Stack Exchange post edit history tools and prices

- [Stack Exchange · Revisions](https://spiral.ai/tools/alexandria/stackexchange-com/questions/revisions) (Alexandria): $0.00873 per call.

## Settings you can ask for

| Setting | Allowed values | Default | Description |
| --- | --- | --- | --- |
| key |  | — | Optional Stack Exchange application key. Raises the per-IP quota from 300 to 10,000 requests per day and unlocks pages above 25, which the API refuses anonymously. Keys are public identifiers, not secrets. |
| url |  | — | A pasted revision history URL (/posts/<id>/revisions), revision source URL (/revisions/<guid>/view-source) or revision page URL (/revisions/<post_id>/<n>, returns the whole history) on any Stack Exchange site. The site is derived from the host; an explicit `site` must match it. |
| page | 1 to 10000 | 1 | Pages above 25 need `key`: Stack Exchange serves deeper pages only with an application key (`access_denied` otherwise). Without one the last page reports partial coverage. |
| site |  | stackoverflow | Stack Exchange site API parameter, e.g. stackoverflow, superuser, math, askubuntu, english, physics. Use `sites` to list them. Pattern: ^[a-z0-9]+(\.[a-z0-9]+)*$. |
| post_id |  | — | post_id |
| pagesize | 1 to 100 | 30 | pagesize |

## What can you do with Stack Exchange post edit history in Cursor?

Build a cited troubleshooting guide around the libraries and errors in your project. A coding agent can use Stack Exchange community information, questions, answers, and recorded edits to select relevant evidence and check whether saved explanations have changed.

### Review migration advice

Find communities covering Ubuntu and Python, search migration problems, collect accepted solutions, and inspect cited answers and their revisions for changes in recommended commands.

### Audit technical citations

Refresh questions and individual answers cited in a handbook, then inspect revisions to identify changes that alter the cited explanation or code.

### Prepare a weekly topic digest

Find recent Kubernetes discussions, summarize accepted solutions and competing answers, and review recorded edits to explanations already covered in earlier digests.

### Explain changes in technical advice

Find discussions about Python packaging, inspect individual answers and alternatives, and compare recorded revisions to explain how installation recommendations changed.

## Overview

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

## Stack Exchange post edit history in other agents

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

## More Cursor guides

- [Stack Exchange answer details](https://spiral.ai/integrations/cursor/stack-exchange-answer-details)
- [Stack Exchange question answers](https://spiral.ai/integrations/cursor/stack-exchange-question-answers)
- [Stack Exchange accepted answers](https://spiral.ai/integrations/cursor/stack-exchange-accepted-answers)
- [Stack Exchange question details](https://spiral.ai/integrations/cursor/stack-exchange-question-details)
- [Spotify track details](https://spiral.ai/integrations/cursor/spotify-track-details)
- [Stack Exchange question search](https://spiral.ai/integrations/cursor/stack-exchange-question-search)

## Questions about Stack Exchange post edit history in Cursor

**Can Cursor use Stack Exchange post edit history?**

Yes. Add Spiral to Cursor as an MCP server, and Cursor can find and run Stack Exchange post edit history like any built-in tool.

**How much does Stack Exchange post edit history cost in Cursor?**

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

**Do I need an Alexandria account to use Stack Exchange post edit history in Cursor?**

No. Spiral runs Stack Exchange post edit 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 Stack Exchange post edit history in Cursor?**

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

**Does Cursor wait while Stack Exchange post edit history runs?**

Stack Exchange post edit history runs in the background. Cursor starts the run, checks on it and gives you the json when it's ready.

**Does Stack Exchange search cover the whole network at once?**

Question searches run against one community at a time. The site directory lists communities across the network so you can choose where to search.

**How fresh is Stack Exchange data?**

API responses are heavily cached, and Stack Exchange considers repeating an equivalent request more than once per minute abusive. The site directory changes much less often; its documentation recommends caching it for at least one day.

**Does one response contain every matching result?**

Stack Exchange generally limits upstream result pages to 100 items, and an endpoint may return fewer. A response indicating more results requires additional pages before the collection is complete.

**Does an accepted answer mean the solution is still correct?**

Acceptance means the question author received an answer that worked for them personally. Stack Exchange explicitly warns that authors may leave an answer accepted even after a better answer appears.

**Does revision history show every edit separately?**

No. Stack Exchange documents that multiple edits can result in a single revision, so recorded revisions cannot establish the exact number of editing actions.

