[Integrations](https://spiral.ai/integrations) › [Muse](https://spiral.ai/integrations/muse) › [npm publisher packages](https://spiral.ai/integrations/muse/npm-publisher-packages)

# How to Use npm publisher packages in Muse

Returns public packages listed for an npm user or organization. Use it to inventory a publisher's catalog before looking up individual packages.

|  |  |
| --- | --- |
| Model | npm publisher packages |
| Available through | Alexandria |
| Category | E-commerce |
| Price | $0.00873 per call. |
| Returns | json |
| Runs | In the background |
| Setup | About 2 minutes, with a Spiral API key |

## Prompts to try with npm publisher packages in Muse

- Use npm publisher packages to list public packages from the babel organization and organize the returned names by apparent purpose.
- Use npm publisher packages to look this up and give me the result as a table.
- Pull the latest numbers from npm publisher packages and tell me what changed since last week.
- Check npm publisher packages and summarize what you find in three bullet points.
- Pull the newest data from npm publisher packages and give me the result as a table.

## How to set up npm publisher packages 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 npm publisher packages**: 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": "npmjs-com/packages/list_owner_packages",
    "input": {
      "org": "<org>"
    }
  }'
```

Then paste one of the prompts above: Muse finds npm publisher packages on Spiral, shows the price and runs it.

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

## npm publisher packages tools and prices

- [npm · List owner packages](https://spiral.ai/tools/alexandria/npmjs-com/packages/list_owner_packages) (Alexandria): $0.00873 per call.

## Settings you can ask for

| Setting | Allowed values | Default | Description |
| --- | --- | --- | --- |
| org |  | — | npm organization (scope without `@`), as in `https://www.npmjs.com/org/{org}`. Pattern: ^[A-Za-z0-9][A-Za-z0-9._-]*$. |
| page | 0 to … | 0 | 0-based page of 25 packages. |
| user |  | — | npm username, as in `https://www.npmjs.com/~{user}`. Pattern: ^[A-Za-z0-9][A-Za-z0-9._-]*$. |

## What can you do with npm publisher packages in Muse?

Create a comparison table for an npm package decision. Explain what the returned package records or download measurements contribute to that decision.

### Review a publisher's public catalog

Inventory an npm organization's packages, use search and name suggestions to locate packages of interest, and inspect their descriptions and repositories. Produce a catalog organized by purpose.

### Prepare a weekly package review

Compare saved publisher listings, package metadata, release details, and returned dependent names. Add changes in download totals, daily patterns, and version shares to identify items worth reviewing.

### Check package references in developer documentation

Resolve package names with search and suggestions, check publisher catalogs, and inspect package and release metadata. Use the results to correct package references and dependency requirements in a tutorial.

### Find downstream integrations

Start with dependent packages and publisher catalogs, then use search and name suggestions to find related integrations. Review descriptions and download totals to select packages for compatibility testing.

### Research package adoption

Define a package sample through search and publisher listings. Compare download totals, daily trends, version shares, and downstream package relationships for an adoption report.

### Check package identity before evaluation

Resolve a partial package name, compare search matches with publisher listings, and inspect repository and release metadata. Produce an identity check before testing the package.

## Overview

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

## npm publisher packages in other agents

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

## More Muse guides

- [npm package version details](https://spiral.ai/integrations/muse/npm-package-version-details)
- [AWS price file metadata](https://spiral.ai/integrations/muse/aws-price-file-metadata)
- [npm package search](https://spiral.ai/integrations/muse/npm-package-search)
- [AWS pricing publication history](https://spiral.ai/integrations/muse/aws-pricing-publication-history)
- [npm package name suggestions](https://spiral.ai/integrations/muse/npm-package-name-suggestions)
- [AWS pricing region coverage](https://spiral.ai/integrations/muse/aws-pricing-region-coverage)

## Questions about npm publisher packages in Muse

**Can Muse use npm publisher packages?**

Yes. Add Spiral to Muse as an MCP server, and Muse can find and run npm publisher packages like any built-in tool.

**How much does npm publisher packages 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 npm publisher packages in Muse?**

You need no Alexandria account. Muse uses one Spiral API key for every tool, and Spiral runs npm publisher packages on its own Alexandria account.

**How long does it take to set up npm publisher packages in Muse?**

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

**Does Muse wait while npm publisher packages runs?**

npm publisher packages runs in the background. Muse starts the run, checks on it and gives you the json when it's ready.

**How fresh are npm download statistics?**

npm documents a daily process that aggregates the previous day's logs after UTC midnight. Download statistics therefore describe completed reporting days.

**Why might a published package be missing from npm search?**

npm says newly published packages can take up to two weeks to appear. Deprecated packages are excluded from search results.

**Do npm download counts represent unique users?**

No. npm counts successful package tarball responses, including downloads from automated builds, mirrors, and analysis robots.

**How much download history can npm return at once?**

npm limits download queries other than bulk queries to 18 months per request. Per-version download counts cover only the previous seven days.

**Does npm search return every match in one response?**

npm registry search returns at most 250 matches per request and supports offset pagination. The response also reports a total.

