Dev · PyPI Simple Index
pypi.versions
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.- Operation
- POST /v1/capabilities/pypi.versions/execute
- operationId
- executePypiVersions
- Typical credits
- 0
- Search deadline
- 15 s server-side
- Paging
- single result
- Availability
- Not checked
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 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 | Type | Required | Default | Constraints and description |
|---|---|---|---|---|
| package | string | yes | min length 1, max length 214, pattern ^[A-Za-z0-9](?:[A-Za-z0-9._-]*[A-Za-z0-9])?$ PyPI project name. Case and runs of hyphens, underscores and dots are normalized. |
- Unknown keys are rejected with
400 invalid_request.
Examples
Requests releases and distributions
curl -s -X POST https://ai-powerups.smalltree.cloud/v1/capabilities/pypi.versions/execute \
-H "Authorization: Bearer $AIPA_API_KEY" -H "Content-Type: application/json" \
-d '{"package":"requests"}'ExecuteResponse component (see sessions and records); the record keys below are what the adapter emits. A first call with the example above returns search_id, the records and the charge.Result record
Every item in results[] carries record_id and title (contract, always present) and usually url and snippet. The 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. See stability tiers.
| Key | Type | Presence | Note |
|---|---|---|---|
| package | string | always | |
| versions | string[] | always | |
| version_count | integer | always | |
| file_count | integer | always | |
| source | string | always |
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;
moreis refused with400 invalid_request. - Update: not offered.
- Record actions:
details: Complete cached Simple Index document, including all files, hashes and yanked markers.
- Detail behaviour: Stored at search time;
detailsis free and never calls the provider. Free cached Simple Index document with all files.
curl -s -X POST https://ai-powerups.smalltree.cloud/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);