PyPI API

Name: PyPI API
Brand: PyPI API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsPackage Registrynone5 EndpointsREST

For Agents

Programmatically get project metadata, get version-specific project metadata. Covers 5 operations.

I need to project metadata, I want to version-specific project metadata, Search for all packages in the simple index, Find all distribution files for a project

Install Jentic One Beta

Connect the PyPI API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the PyPI API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with PyPI API.

Get project metadata

List all packages in the simple index

Search for packages

Access PyPI API developer tools resources via REST API

GET STARTED

Start building with PyPI API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use PyPI API for, with concrete tasks.

★ Developer Tools Operations

Use the PyPI API to perform developer tools operations programmatically. The API provides 5 endpoints covering core functionality including get project metadata, get version-specific project metadata, list all packages in the simple index.

Call GET /pypi/{project}/json to get project metadata

Automated JSON API Management

Automate json api operations by combining multiple PyPI API endpoints. Agents can get version-specific project metadata and then list all packages in the simple index in a single workflow.

Call GET /pypi/{project}/{version}/json to get version-specific project metadata, then verify the result

AI Agent Integration via Jentic

AI agents discover and call PyPI API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle none tokens manually.

Search Jentic for 'get project metadata', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

5 endpoints — the python package index (pypi) api provides read-only access to package metadata, release information, and download urls for python packages hosted on pypi.

METHOD

PATH

DESCRIPTION

GET

/pypi/{project}/json

Get project metadata

GET

/pypi/{project}/{version}/json

Get version-specific project metadata

GET

/simple/

List all packages in the simple index

GET

/simple/{project}/

List distribution files for a project

GET

/search/

Search for packages

GET

/pypi/{project}/json

Get project metadata

GET

/pypi/{project}/{version}/json

Get version-specific project metadata

GET

/simple/

List all packages in the simple index

GET

/simple/{project}/

List distribution files for a project

GET

/search/

Search for packages

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

PyPI API none credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'get project metadata') and Jentic returns the matching PyPI API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct PyPI API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Github

Alternative developer tools API

Choose Github when you need a different approach to developer tools operations

Alternative

Gitlab

Alternative developer tools API

Choose Gitlab when you need a different approach to developer tools operations

FAQs

Specific to using PyPI API through Jentic.

What authentication does the PyPI API use?

The PyPI API uses no authentication. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.

Can I get project metadata with the PyPI API?

Yes. Use the GET /pypi/{project}/json endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the PyPI API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I get project metadata through Jentic?

Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'get project metadata'. Jentic returns the matching PyPI API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.

How many endpoints does the PyPI API have?

The PyPI API exposes 5 endpoints covering json api, simple api, search operations.