# Package registries · Version history

Get developer and code data with Package registries · Version history from Alexandria through one Spiral API key. A package's version history from deps.dev, newest first, with publish time, default flag and deprecation; paged with offset and limit. All four registries. It runs in the background and returns structured JSON. Pay as you go, with no subscription.

- Provider: Alexandria
- Category: Developer
- Runs: In the background
- Returns: json
- Tool id: `alexandria` / `package-registry-metadata-download-stats/packages/versions`
- Page: https://spiral.ai/tools/alexandria/package-registry-metadata-download-stats/packages/versions

## Pricing

$0.001746 per call.

## Limits

- Longest queue wait: 1 hour
- Run deadline: 5 minutes
- Longest run, end to end: 225 minutes
- Largest inline input: 1 MB
- Largest input file: 2 GB
- Largest output: 5 GB

## Input

| Field | Kind | Allowed | Default | Description |
| --- | --- | --- | --- | --- |
| `name` (required) | text |  | — | Package name as the registry knows it: npm `express` or `@types/node`; PyPI `requests` (any PEP 503 spelling); crate `serde`; Maven `groupId:artifactId` such as `com.google.guava:guava`. |
| `registry` (required) | one of | npm, pypi, crates, maven | — | Which registry the name belongs to: npm (registry.npmjs.org), pypi (pypi.org), crates (crates.io) or maven (Maven Central). |
| `limit` | number | 1 to 200 | 50 | Versions per page, 1 to 200. |
| `offset` | number | 0 to 100000 | 0 | Versions to skip, newest first. Page by passing the previous response's next_offset. |

## Example

```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": "package-registry-metadata-download-stats/packages/versions",
    "input": {
      "name": "<name>",
      "registry": "npm"
    }
  }'
```

Try it in the Playground: https://spiral.ai/start?provider=alexandria&model=package-registry-metadata-download-stats%2Fpackages%2Fversions

## Common questions

### Package registries · Version history

**How much does Package registries · Version history cost?**

$0.001746 per call. You pay as you go from one Spiral balance, with no subscription, and a failed run is not charged.

**How do I use Package registries · Version history through an API?**

Send `POST /v1/runs` with `"provider": "alexandria"`, `"model": "package-registry-metadata-download-stats/packages/versions"` and the input fields on this page, using one Spiral API key. It runs in the background: poll the run, or name a webhook to be told when it finishes.

**Do I need an account with Alexandria to use Package registries · Version history?**

No. Spiral runs it on its own Alexandria account and charges your Spiral balance.

**Can my AI agent use Package registries · Version history?**

Yes. Agents find and run it through Spiral's MCP server, CLI or agent skill, with the same API key.

