Packagist Private Packagist API

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.