[Integrations](https://spiral.ai/integrations) › [Muse](https://spiral.ai/integrations/muse) › [Notion developer documentation index](https://spiral.ai/integrations/muse/notion-developer-documentation-index)

# How to Use Notion developer documentation index in Muse

Returns entries from Notion’s developer documentation index. Use it to map the available technical documentation before choosing pages to read.

|  |  |
| --- | --- |
| Model | Notion developer documentation index |
| Available through | Alexandria |
| Category | Developer |
| Price | $0.00873 per call. |
| Returns | json |
| Runs | In the background |
| Setup | About 2 minutes, with a Spiral API key |

## Prompts to try with Notion developer documentation index in Muse

- Use Notion developer documentation index to find technical pages about webhooks and explain which titles look most relevant to an engineering review.
- Use Notion developer documentation index to look this up and give me the result as a table.
- Pull the latest numbers from Notion developer documentation index and tell me what changed since last week.
- Check Notion developer documentation index and summarize what you find in three bullet points.
- Pull the newest data from Notion developer documentation index and give me the result as a table.

## How to set up Notion developer documentation index in Muse

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

### Use the Muse connector

1. **Create an API key**: Create one under API keys in the Spiral console.

2. **Send Muse this message**: Muse reads Spiral's skill and asks for an API key.

```text
set up https://spiral.ai/SKILL.md
```

3. **Give Muse the key**: Paste the key when Muse asks for it, never in the chat itself.

### Use the Spiral skill

1. **Send Muse 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 Notion developer documentation index**: 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": "notion-com/developer-documentation/list_pages",
    "input": {
      "q": "<q>"
    }
  }'
```

Then paste one of the prompts above: Muse finds Notion developer documentation index on Spiral, shows the price and runs it.

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

## Notion developer documentation index tools and prices

- [Notion Docs, Help Center, Pricing, Blog and Templates · List pages](https://spiral.ai/tools/alexandria/notion-com/developer-documentation/list_pages) (Alexandria): $0.00873 per call.

## Settings you can ask for

| Setting | Allowed values | Default | Description |
| --- | --- | --- | --- |
| q |  | — | Case-insensitive text matched against title, path and description. |
| group |  | — | Directory prefix of the page path, e.g. `reference`, `reference/webhooks`, `guides/mcp`, `cli`. |
| limit | 1 to 500 | — | Page size, 1-500. Defaults to 100. |
| offset | 0 to … | — | Records to skip. Defaults to 0. |

## What can you do with Notion developer documentation index in Muse?

Prepare a Notion rollout brief with help topics, technical references, product announcements, and template examples. Turn the retrieved material into reading lists for users and engineers.

### Build a Notion onboarding resource pack

Collect help areas for new users, technical documentation for engineers, product announcements for context, and project template examples. Produce separate reading lists for the people configuring workflows and the people implementing integrations.

### Research a project management pilot

Find project plans, sprint boards, and status report templates. Pair the shortlist with relevant help areas, developer references, and product announcements to prepare a pilot that covers both daily use and integration requirements.

### Refresh monthly Notion training

Compare product announcements with an existing training outline. Find the help categories, developer references, and template examples worth reviewing before revising lessons for users and engineers.

### Prepare a feature adoption review

Start with a Notion product announcement and collect related help topics, technical references, and workflow templates. Turn the findings into a review brief that separates announced functionality from implementation questions that still need documentation.

### Map developer references for an integration

Inventory relevant developer pages, then search for specific sections about webhooks, data sources, or page content. Create a reference list engineers can consult while reviewing implementation choices.

## Overview

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

## Notion developer documentation index in other agents

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

## More Muse guides

- [Notion developer documentation](https://spiral.ai/integrations/muse/notion-developer-documentation)
- [Notion developer documentation search](https://spiral.ai/integrations/muse/notion-developer-documentation-search)
- [Notion blog post](https://spiral.ai/integrations/muse/notion-blog-post)
- [Notion help article](https://spiral.ai/integrations/muse/notion-help-article)
- [Notion blog index](https://spiral.ai/integrations/muse/notion-blog-index)
- [Notion help article index](https://spiral.ai/integrations/muse/notion-help-article-index)

## Questions about Notion developer documentation index in Muse

**Can Muse use Notion developer documentation index?**

Yes. Add Spiral to Muse as an MCP server, and Muse can find and run Notion developer documentation index like any built-in tool.

**How much does Notion developer documentation index cost in Muse?**

$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 plan is separate.

**Do I need an Alexandria account to use Notion developer documentation index in Muse?**

You need no Alexandria account. Muse uses one Spiral API key for every tool, and Spiral runs Notion developer documentation index on its own Alexandria account.

**How long does it take to set up Notion developer documentation index in Muse?**

About two minutes: create an API key, then send Muse this message, then give Muse the key.

**Does Muse wait while Notion developer documentation index runs?**

Notion developer documentation index runs in the background. Muse starts the run, checks on it and gives you the json when it's ready.

**Does the developer documentation index cover all of Notion’s website?**

It is an index of developer documentation. Notion’s Help Center has its own category tree and article lists, so a developer page inventory should not be treated as a complete website inventory.

**Are product release notes the same as the developer changelog?**

No. Notion’s product feed covers releases, improvements, and fixes, while its separate developer changelog records technical changes such as the November 11, 2026 webhook delivery update.

**Can API behavior change while an integration stays on the same version?**

Yes. Notion says additive changes, including new response fields and optional parameters, apply to older API versions too. A pinned version does not freeze the documentation or response shape.

**What freshness information does Notion publish?**

Product announcements carry dates, including the August 19, 2026 developer sidebar announcement. Those dates identify announcements, rather than establishing a fixed refresh schedule for documentation retrieval.

**What kinds of project workflows can I research through Notion’s templates?**

Notion’s project template category explicitly covers project plans, timelines, sprints, and status reports. Use those as concrete starting points when comparing project workflows.

