pypi.versions
Uses the official Simple Index API with application/vnd.pypi.simple.v1+json. Returns version names and file counts; details returns all distribution files with download URLs, hashes, Python requirements and yanked status. Version order is provider-defined, not a recommendation of which release to install. No provider key needed.
- operationId
- execute
Pypi Versions - Source
- PyPI Simple Index
- Typical credits
- 0 (free source)
- Search deadline
- 15 s server-side
- Paging
- single result
- Availability
- ConfiguredChecked 2026-11-03 16:34 UTC
GET /v1/catalog (available). The timestamped snapshot describes configuration, not provider uptime or your account's enabled choices. Check the catalog with your own key before a call. Credits are explained under credits and limits.Request body
Body of POST /v1/capabilities/pypi.versions/execute, JSON, validated against the PypiVersionsRequest component of the public OpenAPI document. Defaults are applied server-side, so an omitted optional field behaves exactly as its default.
| Field | Description |
|---|---|
| packagestringREQUIRED | PyPI project name. Case and runs of hyphens, underscores and dots are normalized.min length 1 · max length 214 · pattern ^[A-Za-z0-9](?:[A-Za-z0-9._-]*[A-Za-z0-9])?$ |
- Unknown keys are rejected with
400 invalid_request.
Examples
curl -s -X POST https://api.powerups-ai.store/v1/capabilities/pypi.versions/execute \
-H "Authorization: Bearer $AIPA_API_KEY" -H "Content-Type: application/json" \
-d '{"package":"requests"}'Record fields
Each item in results[] carries record_id and title (contract, always present) and usually url and snippet. The other keys below are the documented tier: produced deterministically by this capability, omitted when the source has no value, checked against recorded source fixtures in our test suite, and published as the PypiVersionsRecord component (all optional, extra keys allowed) so generated clients type them. The wire schema itself still validates only the base keys. Anything else comes from the provider and may change; see stability tiers.
| Key | Note |
|---|---|
| record_idstringALWAYS | Use it with record actions on POST /v1/follow-up. |
| titlestringALWAYS | Contract key. |
| urlstring | Contract key; usually present. |
| snippetstring | Contract key; usually present. |
| packagestringALWAYS | On every record. |
| versionsstring[]ALWAYS | On every record. |
| version_countintegerALWAYS | On every record. |
| file_countintegerALWAYS | On every record. |
| sourcestringALWAYS | On every record. |
Caveats
- Uses the JSON Simple Index API, not the deprecated releases field. Yanked files remain listed with their markers. Version order is provider-defined. Responses have an 8 MiB limit.
Follow-ups
Paging: Single result; more is refused with 400 invalid_request.
Not offered: update.
Detail behaviour: Stored at search time; details is free and never calls the provider. Free cached Simple Index document with all files.
curl -s -X POST https://api.powerups-ai.store/v1/follow-up \
-H "Authorization: Bearer $AIPA_API_KEY" -H "Content-Type: application/json" \
-d '{"record_id":"rec_…","action":"details"}'Record detail objects of this capability are provider-shaped: documented by observation, not by schema. Full follow-up semantics: follow-up.
Typed client
With types generated from the public document (see types, client and samples) the call is path-keyed and the body is checked at compile time:
const { data, error } = await client.POST("/v1/capabilities/pypi.versions/execute", {
body: {
"package": "requests"
},
});
if (error) throw new Error(`${error.error.code}: ${error.error.message}`);
for (const record of data.results) console.log(record.record_id, record.title);POST /v1/capabilities/pypi.versions/execute
{
"package": "requests"
}