Packagist Private Packagist API
Official vendor OpenAPI document · agent-readyE CommerceShipping LogisticsapiKey32 EndpointsREST
For Agents
Private Packagist REST API for managing packages, teams, customers, and credentials in your organization's private Composer repository.
Use for: I need to access Private Packagist API, How do I use the packagist.com API?, Get data from packagist.com
Not supported: Provides access to Private Packagist API functionality as defined in the OpenAPI specification.
Private Packagist REST API for managing packages, teams, customers, and credentials in your organization's private Composer repository.
Install Jentic One Beta
Connect the Private Packagist API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Private Packagist 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.
1
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%2Fpackagist.com%2Fpackagist" | sh2
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%2Fpackagist.com%2Fpackagist" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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 Private Packagist API.
List all packages
Create a new package
Get a specific package
Update a package
Delete a package
List customers with access to a package
List security issues for a package
Use Cases
Patterns agents use Private Packagist API for, with concrete tasks.
★ Basic Private Packagist API Integration
Integrate Private Packagist API into your application to access its core functionality.
Use the Private Packagist API API to access vendor services and data.
Key Endpoints
32 endpoints — private packagist rest api for managing packages, teams, customers, and credentials in your organization's private composer repository.
METHOD
PATH
DESCRIPTION
GET
/packages/
List all packages
POST
/packages/
Create a new package
GET
/packages/{packageId}
Get a specific package
PUT
/packages/{packageId}
Update a package
DELETE
/packages/{packageId}
Delete a package
GET
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Private Packagist by hand means choosing between its HMAC-SHA256 signed requests and token auth, then building the correct Authorization header for every package call. Through Jentic you install once, import the Private Packagist API from the API Directory, store the credentials once, and your agent calls it.
Permission scoping
Private Packagist puts the package id in the URL path (/packages/{packageId}), so a rule can pin your agent to one package for reads like its customers and security issues. You choose the operations it may call, so destructive ones like deleting or updating a package are not included unless you add them.
Credential isolation
Your Private Packagist credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'list packages' or 'check a package's security issues', and Jentic returns the matching Private Packagist operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
FAQs
Specific to using Private Packagist API through Jentic.
What authentication does the Private Packagist API use?
The Private Packagist API uses apiKey authentication.
How many endpoints does the Private Packagist API have?
The Private Packagist API has 32 endpoints available.
Can I limit what my agent is allowed to do with the Private Packagist API?
Yes. Jentic One runs self-hosted on your own infrastructure, so your rules decide which Private Packagist operations and credentials your agent may use. Because the package id sits in the URL path (/packages/{packageId}), you can pin the agent to a single package and allow only read operations such as listing its customers or security issues. You choose which operations are exposed, so destructive calls like deleting or updating a package stay out of reach unless you explicitly add them.
GET STARTED