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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fpypi.org%2Fpypi" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fpypi.org%2Fpypi" | 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

Use Cases

Patterns agents use PyPI API for, with concrete tasks.

GET STARTED

Start building with PyPI API

Explore with Jentic One

View OpenAPI Document

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?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the PyPI API by hand means choosing between the JSON metadata and simple index endpoints and parsing each response shape yourself. Through Jentic you install once, import the PyPI API from the API Directory, and your agent calls it with no key to manage.

Permission scoping

PyPI puts the project name in the URL path (/pypi/{project}/json), so a rule can pin your agent to reads of one project: it can fetch that project's metadata and nothing else. You choose the operations it may call, so the simple index or search is not included unless you add it.

Credential isolation

PyPI needs no credential, and Jentic One runs it the same way as any imported operation, so nothing secret ever enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'get metadata for a Python package' or 'look up a package version', and Jentic returns the matching PyPI operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

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 your Jentic One instance 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 through Jentic One, the self-hosted execution layer, 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.

Can I limit what my agent is allowed to do with the PyPI API?

Yes. Jentic One is self-hosted, so your own rules decide which PyPI operations your agent may call. Because the project name sits in the URL path (GET /pypi/{project}/json), you can pin the agent to reads of a single project's metadata and nothing else. The simple index listing and package search stay out of reach unless you explicitly add those operations.

PyPI API

Name: PyPI API
Brand: PyPI API
Availability: InStock

Community OpenAPI document · agent-readyDeveloper ToolsPackage Registrynone5 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

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

Use for: 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

Not supported: Does not handle payments, communications, or crm - use for developer tools only.

The Python Package Index (PyPI) API provides read-only access to package metadata, release information, and download URLs for Python packages hosted on PyPI. The API includes a JSON API for structured metadata and a Simple API (PEP 503) for package file listings. All endpoints are publicly accessible and require no authentication. The API exposes 5 endpoints.

Jentic One on Github View OpenAPI Document

Connect the PyPI API to your agent

Capabilities

Use Cases

Start building with PyPI API

Key Endpoints

Why Jentic?

Related APIs

FAQs

PyPI API