Registry Npmjs npm Registry API

Name: npm Registry API
Brand: npm Registry API
Availability: InStock

✓ Official Vendor SpecDeveloper ToolsSource Controlbearer20 EndpointsREST

For Agents

Programmatically get package metadata (packument), publish a package. Covers 20 operations with bearer authentication.

Install Jentic One Beta

Connect the npm Registry API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the npm Registry 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 npm Registry API.

Get package metadata (packument)

Publish a package

Search packages

Unpublish a package version

GET STARTED

Start building with npm Registry API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use npm Registry API for, with concrete tasks.

★ Developer Tools Operations

Use the npm Registry API to perform developer tools operations programmatically. The API provides 20 endpoints covering core functionality including get package metadata (packument), publish a package, get specific package version.

Call GET /{package} to get package metadata (packument)

Automated Package Management

Automate package operations by combining multiple npm Registry API endpoints. Agents can publish a package and then get specific package version in a single workflow.

Call PUT /{package} to publish a package, then verify the result

AI Agent Integration via Jentic

AI agents discover and call npm Registry 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 bearer tokens manually.

Search Jentic for 'get package metadata (packument)', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

20 endpoints — the npm public registry api.

METHOD

PATH

DESCRIPTION

GET

/{package}

Get package metadata (packument)

PUT

/{package}

Publish a package

GET

/{package}/{version}

Get specific package version

GET

/-/v1/search

Search packages

DELETE

/{package}/-/{tarball}/{revision}

Unpublish a package version

GET

/{package}/-/{tarball}

Download package tarball

POST

/-/npm/v1/user

Update user profile

GET

/-/npm/v1/user

Get user profile

GET

/{package}

Get package metadata (packument)

PUT

/{package}

Publish a package

GET

/{package}/{version}

Get specific package version

GET

/-/v1/search

Search packages

DELETE

/{package}/-/{tarball}/{revision}

Unpublish a package version

Why Jentic?

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

Credential isolation

Your npm Registry API bearer token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'get package metadata' or 'search for packages', and Jentic returns the matching npm Registry API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

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 npm Registry API through Jentic.

What authentication does the npm Registry API use?

The npm Registry API uses a Bearer token in the Authorization header. 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 package metadata (packument) with the npm Registry API?

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

What are the rate limits for the npm Registry 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 package metadata (packument) through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get package metadata (packument)'. Jentic returns the matching npm Registry API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the npm Registry API have?

The npm Registry API exposes 20 endpoints covering package, search, disttags operations.

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

Yes. Jentic One is self-hosted by you, so your own rules decide which npm Registry operations and credentials the agent may use. Because the package name and version sit in the URL path, such as GET /{package} and GET /{package}/{version}, you can pin the agent to a single package so it only reads that package's metadata and versions. You choose the operations it may call, so destructive ones like PUT /{package} to publish a package or DELETE /{package}/-/{tarball}/{revision} to remove a version stay off unless you add them.