[Integrations](https://spiral.ai/integrations) › [Muse](https://spiral.ai/integrations/muse) › [Vercel blog posts](https://spiral.ai/integrations/muse/vercel-blog-posts)

# How to Use Vercel blog posts in Muse

Returns entries from Vercel's blog index. Use it to find engineering explanations and product context, then read the linked article for the full discussion.

|  |  |
| --- | --- |
| Model | Vercel blog posts |
| 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 Vercel blog posts in Muse

- Use Vercel blog posts to find engineering articles about Fluid Compute published during 2026 and give me a reading shortlist.
- Use Vercel blog posts to look this up and give me the result as a table.
- Pull the latest numbers from Vercel blog posts and tell me what changed since last week.
- Check Vercel blog posts and summarize what you find in three bullet points.
- Pull the newest data from Vercel blog posts and give me the result as a table.

## How to set up Vercel blog posts 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 Vercel blog posts**: 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": "vercel-com/developer-documentation/list_blog_posts",
    "input": {
      "q": "<q>"
    }
  }'
```

Then paste one of the prompts above: Muse finds Vercel blog posts on Spiral, shows the price and runs it.

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

## Vercel blog posts tools and prices

- [Vercel · List blog posts](https://spiral.ai/tools/alexandria/vercel-com/developer-documentation/list_blog_posts) (Alexandria): $0.00873 per call.

## Settings you can ask for

| Setting | Allowed values | Default | Description |
| --- | --- | --- | --- |
| q |  | — | Words that must all appear in title, slug or summary. |
| limit | 1 to 100 | — | Results per call, 1 to 100. Defaults to 20. |
| since |  | — | Only posts on or after this date. Pattern: ^[0-9]{4}-[0-9]{2}-[0-9]{2}$. |
| until |  | — | Only posts on or before this date. Pattern: ^[0-9]{4}-[0-9]{2}-[0-9]{2}$. |
| offset | 0 to 100000 | — | Skip this many matches; pass the previous `next_offset` (also the continuation). |
| category |  | — | Category as listed in `categories`, e.g. `Engineering` (case-insensitive). |

## What can you do with Vercel blog posts in Muse?

Build a source-linked research brief for a Next.js application on Vercel. A chat assistant can explain the published guidance and help compare documented options for the application you describe.

### Plan a Next.js AI application

Prepare an architecture brief with documentation, engineering articles, release announcements, model candidates, a starter template, Marketplace services, plan feature boundaries, and documented automation operations.

### Research a move to Vercel

Assess a move for an AI application: compare framework guidance and starters, identify replacement integrations and models, check plan features, and locate deployment automation references.

### Prepare a weekly platform review

Collect product announcements and engineering articles, then compare saved model, integration, starter, and plan-feature snapshots to identify items worth investigating.

### Build an internal Vercel reference library

Organize public guidance, announcements, model references, plan comparisons, integration listings, API references, and starters into a searchable engineering reference with source links.

### Design deployment automation

Find documented deployment and domain operations, read their references, and use guides, announcements, and plan feature information to draft an implementation checklist.

### Prepare an AI application workshop

Choose a Next.js starter, research its supporting services, shortlist models, and assemble documentation and engineering reading material for participants.

### Create a model evaluation shortlist

Find model candidates by documented capabilities, inspect their individual guidance, and collect relevant AI Gateway documentation and announcements before running application-specific evaluations.

## Overview

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

## Vercel blog posts in other agents

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

## More Muse guides

- [Vercel REST API endpoint reference](https://spiral.ai/integrations/muse/vercel-rest-api-endpoint-reference)
- [Vercel changelog entries](https://spiral.ai/integrations/muse/vercel-changelog-entries)
- [Vercel Marketplace integrations](https://spiral.ai/integrations/muse/vercel-marketplace-integrations)
- [Vercel documentation page](https://spiral.ai/integrations/muse/vercel-documentation-page)
- [Vercel AI Gateway model details](https://spiral.ai/integrations/muse/vercel-ai-gateway-model-details)
- [Vercel documentation search](https://spiral.ai/integrations/muse/vercel-documentation-search)

## Questions about Vercel blog posts in Muse

**Can Muse use Vercel blog posts?**

Yes. Add Spiral to Muse as an MCP server, and Muse can find and run Vercel blog posts like any built-in tool.

**How much does Vercel blog posts 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 Vercel blog posts in Muse?**

You need no Alexandria account. Muse uses one Spiral API key for every tool, and Spiral runs Vercel blog posts on its own Alexandria account.

**How long does it take to set up Vercel blog posts in Muse?**

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

**Does Muse wait while Vercel blog posts runs?**

Vercel blog posts runs in the background. Muse starts the run, checks on it and gives you the json when it's ready.

**Does this data include my deployed application's logs or project settings?**

The coverage is limited to public Vercel pages and catalogs. Private project records and runtime logs are outside that boundary.

**Are documentation search results the full documentation?**

Vercel describes its sitemap as a high-level semantic index and explicitly says it does not replace individual docs. Read the linked page for the full explanation.

**What does the documentation's update date mean?**

Vercel's Markdown metadata defines the date as the day the source page last changed. That date describes the documentation page.

**Do Markdown documentation pages retain code examples and tables?**

Yes. Vercel says the Markdown body preserves headings, links, fenced code blocks, and tables.

**Does Vercel provide a separate index for product announcements?**

Yes. Vercel publishes a dedicated Markdown changelog sitemap, separate from its documentation sitemap.

