[Integrations](https://spiral.ai/integrations) › [Codex](https://spiral.ai/integrations/codex) › [npm package name suggestions](https://spiral.ai/integrations/codex/npm-package-name-suggestions)

# How to Use npm package name suggestions in Codex

Returns possible npm package names for a partial search. Use it to identify the package you mean before requesting its metadata.

|  |  |
| --- | --- |
| Model | npm package name suggestions |
| Available through | Alexandria |
| Category | E-commerce |
| Price | $0.00873 per call. |
| Returns | json |
| Runs | In the background |
| Setup | About 2 minutes, no API key |

## Prompts to try with npm package name suggestions in Codex

- Use npm package name suggestions to look this up and give me the result as a table. Save the result in ./assets.
- Pull the latest numbers from npm package name suggestions and tell me what changed since last week.
- Check npm package name suggestions and summarize what you find in three bullet points.
- Pull the newest data from npm package name suggestions and give me the result as a table.
- Check npm package name suggestions every morning and tell me only when something changed.

## How to set up npm package name suggestions in Codex

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

### Use Spiral's MCP server

1. **Add the hosted server**

```bash
codex mcp add spiral --url https://api.spiral.ai/mcp
```

2. **Sign in**: Codex opens the browser: sign in to Spiral and click Authorize. No API key. `codex mcp list` then shows Spiral.

```bash
codex mcp login spiral
```

### Use the Spiral skill

1. **Send Codex 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 package name suggestions**: 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/suggest_packages",
    "input": {
      "query": "<query>"
    }
  }'
```

Then paste one of the prompts above: Codex finds npm package name suggestions on Spiral, shows the price and runs it.

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

## npm package name suggestions tools and prices

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

## What can you do with npm package name suggestions in Codex?

Produce an npm dependency review tied to your project's requirements. Turn returned package metadata, discovery results, or download measurements into evidence for the review.

### Compare dependency candidates

Find package names for schema validation, inspect published metadata and release requirements, and compare download totals, daily patterns, and version shares. Build a shortlist for a project trial.

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

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

### 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 Codex guides](https://spiral.ai/integrations/codex)

## npm package name suggestions in other agents

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

## More Codex guides

- [npm package download totals](https://spiral.ai/integrations/codex/npm-package-download-totals)
- [npm package search](https://spiral.ai/integrations/codex/npm-package-search)
- [npm package details](https://spiral.ai/integrations/codex/npm-package-details)
- [npm package version details](https://spiral.ai/integrations/codex/npm-package-version-details)
- [npm package dependents](https://spiral.ai/integrations/codex/npm-package-dependents)
- [npm publisher packages](https://spiral.ai/integrations/codex/npm-publisher-packages)

## Questions about npm package name suggestions in Codex

**Can Codex use npm package name suggestions?**

Yes. Add Spiral to Codex as an MCP server, and Codex can find and run npm package name suggestions like any built-in tool.

**How much does npm package name suggestions cost in Codex?**

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

**Do I need an Alexandria account to use npm package name suggestions in Codex?**

No. Spiral runs npm package name suggestions on its own Alexandria account. You sign in to Spiral once and never paste a key.

**How long does it take to set up npm package name suggestions in Codex?**

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

**Does Codex wait while npm package name suggestions runs?**

npm package name suggestions runs in the background. Codex 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.

