[Integrations](https://spiral.ai/integrations) › [goose](https://spiral.ai/integrations/goose) › [Stack Exchange question details](https://spiral.ai/integrations/goose/stack-exchange-question-details)

# How to Use Stack Exchange question details in goose

Returns a question with its tags, score, and answers, with the accepted answer identified separately. Use it when you need the problem's context alongside proposed solutions.

|  |  |
| --- | --- |
| Model | Stack Exchange question details |
| 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 question details in goose

- Use Stack Exchange question details for https://stackoverflow.com/questions/11227809 and compare the discussion's performance claims with the benchmark code in this repository.
- Use Stack Exchange question details to look this up and give me the result as a table. Save the result in ./assets.
- Pull the latest numbers from Stack Exchange question details and tell me what changed since last week.
- Check Stack Exchange question details and summarize what you find in three bullet points.
- Pull the newest data from Stack Exchange question details and give me the result as a table.

## How to set up Stack Exchange question details in goose

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

### Use Spiral's MCP server

1. **Add the extension**: In goose Desktop, open the sidebar, click Extensions, then Add custom extension. Enter:

2. **Sign in**: When goose first connects to Spiral, your browser opens. Sign in to Spiral, pick the organization and click Authorize. No API key. If the browser does not open, goose prints the link to open yourself.

### Use the Spiral skill

1. **Send goose 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 question details**: 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/question",
    "input": {
      "question_id": 1
    }
  }'
```

Then paste one of the prompts above: goose finds Stack Exchange question details on Spiral, shows the price and runs it.

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

## Stack Exchange question details tools and prices

- [Stack Exchange · Question](https://spiral.ai/tools/alexandria/stackexchange-com/questions/question) (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 |  | — | HTTPS question URL on any Stack Exchange site, e.g. https://stackoverflow.com/questions/3940128/..., https://ru.stackoverflow.com/questions/1624500/... or https://math.stackexchange.com/q/11. Answer links of the form /questions/<question_id>/<slug>/<answer_id> resolve to their question. The site is derived from the host; an explicit `site` must match it. Question feed URLs (/feeds/question/<id>) are accepted too. |
| 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]+)*$. |
| question_id |  | — | question_id |
| answers_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. |
| answers_sort | votes, activity, creation | votes | answers_sort |

## What can you do with Stack Exchange question details in goose?

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.

### Build a troubleshooting handbook

Choose the relevant community, find recurring PostgreSQL errors, collect accepted solutions, and compare other answers against each question's constraints.

### Find gaps in product documentation

Locate the community serving a product's users, search recurring configuration questions, and compare problem descriptions with the explanations supplied in answers.

### Create a technical reading list

Choose a subject community, collect questions with accepted solutions, read the full problem context, and retrieve individual answers selected for a linked study guide.

### Compare conflicting solutions

Start with accepted solutions to a topic, compare the remaining answers and their scores, then inspect selected answers alongside the original question's requirements.

### 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.

## Overview

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

## Stack Exchange question details in other agents

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

## More goose guides

- [Stack Exchange question answers](https://spiral.ai/integrations/goose/stack-exchange-question-answers)
- [Stack Exchange question search](https://spiral.ai/integrations/goose/stack-exchange-question-search)
- [Stack Exchange post edit history](https://spiral.ai/integrations/goose/stack-exchange-post-edit-history)
- [Stack Exchange site directory](https://spiral.ai/integrations/goose/stack-exchange-site-directory)
- [Stack Exchange answer details](https://spiral.ai/integrations/goose/stack-exchange-answer-details)
- [Telegram Channel Details](https://spiral.ai/integrations/goose/telegram-channel-details)

## Questions about Stack Exchange question details in goose

**Can goose use Stack Exchange question details?**

Yes. Add Spiral to goose as an MCP server, and goose can find and run Stack Exchange question details like any built-in tool.

**How much does Stack Exchange question details cost in goose?**

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

**Do I need an Alexandria account to use Stack Exchange question details in goose?**

No. Spiral runs Stack Exchange question details 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 question details in goose?**

About two minutes: add the extension, then sign in.

**Does goose wait while Stack Exchange question details runs?**

Stack Exchange question details runs in the background. goose 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.

