[Integrations](https://spiral.ai/integrations) › [Muse](https://spiral.ai/integrations/muse) › [PyPI package changes](https://spiral.ai/integrations/muse/pypi-package-changes)

# How to Use PyPI package changes in Muse

Returns PyPI change events with package names, versions, actions, timestamps, and serial numbers. Use it to follow uploads, removals, and ownership changes between checks.

|  |  |
| --- | --- |
| Model | PyPI package changes |
| 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 PyPI package changes in Muse

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

## How to set up PyPI package changes 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 PyPI package changes**: 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": "pypi-org/packages/changelog",
    "input": {
      "limit": 500
    }
  }'
```

Then paste one of the prompts above: Muse finds PyPI package changes on Spiral, shows the price and runs it.

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

## PyPI package changes tools and prices

- [PyPI · Changelog](https://spiral.ai/tools/alexandria/pypi-org/packages/changelog) (Alexandria): $0.00873 per call.

## Settings you can ask for

| Setting | Allowed values | Default | Description |
| --- | --- | --- | --- |
| limit | 1 to 5000 | 500 | limit |
| since_serial | 0 to … | — | Return events with a serial greater than this (use `next_serial` or `head_serial` from a previous call). |

## What can you do with PyPI package changes in Muse?

Get a readable PyPI research brief covering package requirements, release activity, publishing evidence, or repository storage. Ask for the specific records behind a comparison so you can choose what deserves closer review.

### Plan package mirror capacity

Use PyPI's total storage and largest packages to estimate scale. Inventory files for selected releases and use change events to identify additions and removals that need reconciliation.

### Review publishing identity changes

Compare saved file provenance with new artifacts and examine ownership change events. Use publisher project roles and release records to document which packages and versions need review.

### Investigate artifact storage growth

Compare storage snapshots, identify packages appearing among the largest, and inspect their file inventories. Use upload and removal events to investigate changes between snapshots.

### Triage release notifications

Establish a watchlist from a public publishing account, collect recent release entries, and inspect version details before flagging an upgrade. Use the journal to distinguish releases from other package changes.

## Overview

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

## PyPI package changes in other agents

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

## More Muse guides

- [PyPI file provenance](https://spiral.ai/integrations/muse/pypi-file-provenance)
- [PyPI package details](https://spiral.ai/integrations/muse/pypi-package-details)
- [Promocodes.com top coupons](https://spiral.ai/integrations/muse/promocodes-com-top-coupons)
- [PyPI package files](https://spiral.ai/integrations/muse/pypi-package-files)
- [Promocodes.com store search](https://spiral.ai/integrations/muse/promocodes-com-store-search)
- [PyPI publisher projects](https://spiral.ai/integrations/muse/pypi-publisher-projects)

## Questions about PyPI package changes in Muse

**Can Muse use PyPI package changes?**

Yes. Add Spiral to Muse as an MCP server, and Muse can find and run PyPI package changes like any built-in tool.

**How much does PyPI package changes 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 PyPI package changes in Muse?**

You need no Alexandria account. Muse uses one Spiral API key for every tool, and Spiral runs PyPI package changes on its own Alexandria account.

**How long does it take to set up PyPI package changes in Muse?**

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

**Does Muse wait while PyPI package changes runs?**

PyPI package changes runs in the background. Muse starts the run, checks on it and gives you the json when it's ready.

**How reliable is PyPI's package metadata?**

PyPI's JSON metadata uses values supplied during upload and may differ from the uploaded files. The first metadata uploaded for a release is retained even when more files are added to that release.

**How quickly do PyPI changes appear?**

PyPI caches API responses, including JSON, RSS, and Index responses through its CDN. Its API documentation does not promise that every upload or change appears immediately.

**How much release history do PyPI feeds contain?**

The upstream implementation returns up to 100 site-wide release updates, 40 newly created projects, or 40 releases for one project. These are entry limits, so the time span depends on publishing activity.

**Does PyPI provenance prove a package is safe?**

A provenance record links an individual file to its publishing or build origin. PyPI explicitly says that an attestation does not establish that the code or build environment is safe.

**Does every PyPI file have provenance?**

No. PyPI documents releases with no attestations, especially older releases or projects without attestations configured, and a release can have attestations for only some files.

