Jentic OSThe workplace. An in-house AI platform for every employeeJentic OneSafe access. Agents reach your systems without holding keysJentic AIRThe foundation. Gets your existing platforms ready for AI
Pricing

GET STARTED

API DirectoryBrowse 10,000+ APIs ready for AI agent integrationDocumentationGuides and API reference

TOOLS

API ScoringCheck your AI readiness using our scorecardArazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually

COMMUNITY

GitHubOpen source projects and examplesOpen StandardsBuilt on open specs. Never locked in.
All ResourcesEverything in one placeBlogLatest articles and insightsTech Talk NewsletterAPIs, AI agents, architecture and strategyWebinarsLive sessions and on-demand recordingsReports & WhitepapersOriginal research on enterprise AI
About UsOur mission and teamCareersJoin our teamContactGet in touch
Try it now
Jentic OSJentic OneJentic AIR
Pricing
API DirectoryDocumentationAPI ScoringArazzo UIArazzo EditorGitHubOpen Standards
All ResourcesBlogTech Talk NewsletterWebinarsReports & Whitepapers
About UsCareersContact
Try it now
JenticJentic
Products
  • Jentic OS
  • Jentic One
  • Jentic AIR
For Developers
  • API Directory
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
  • Trust Centre
ISO/IEC 27001:2022 certification badge issued by Prescient SecurityISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

AICPA SOC for Service Organizations logoAICPA SOC for Service Organizations logo

SOC 2® Type 1 report

Audited by Prescient Assurance

Terms & Conditions•Privacy Policy•
© 2026 Jentic Technology Ltd. All rights reserved.
2 Grattan Court East, Dublin, D02 VX86, Ireland
Switch to light modeSwitch to dark mode
APIs / Developer Tools / npm Registry API
npm Registry API logo

Registry Npmjs npm Registry API

69
AI ReadinessAI-Aware (B+)69/100
See full scorecard
Official vendor OpenAPI document · agent-readyDeveloper ToolsSource Controlbearer20 EndpointsREST

For Agents

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

Use for: I need to package metadata (packument), I want to publish a package, Search for specific package version, Find all packages

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

The npm public registry API. Provides endpoints for package publishing, retrieval, searching, user management, organization management, token management, and dist-tag operations. The API exposes 20 endpoints secured with bearer authentication.

Jentic One on GithubView OpenAPI Document

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.

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%2Fregistry.npmjs.org%2Fregistry-npmjs" | sh
2

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%2Fregistry.npmjs.org%2Fregistry-npmjs" | 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

Download package tarball

Update user profile

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

GET

/{package}/-/{tarball}

Download package tarball

POST

/-/npm/v1/user

Update user profile

GET

/-/npm/v1/user

Get user profile

Jentic AI Readiness Score

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

N

npm Registry API

- AI-Aware (B+)
69/100
93
Foundational Compliance
63
Developer Experience & Jentic Compatibility
52
AI-Readiness & Agent Experience
94
Agent Usability
60
Security
79
AI Discoverability
Powered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
93

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4
98%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

75%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

63

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4
0%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

52

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: C-Signals: 4
60%

Description Coverage

Coverage of descriptions across API elements.

0%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

90%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

59%

Summary Coverage

Coverage of summaries across operations/tags/info.

94

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1
94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

60

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1
60%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

79

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A-Signals: 1
79%

Descriptive Richness

Clarity and depth of descriptions across API elements.

View full reportHow the score is calculatedMore about the dimensions

Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

Score your own APIScoring CLI agent skill
npx @jentic/api-scorecard-cli score <openapi-url>

Why Jentic?

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

Setup

Wiring the npm Registry API by hand means setting its bearer token on every call and building your own retry handling against the registry.npmjs.org host. Through Jentic you install once, import the npm Registry API from the API Directory, store the token once, and your agent calls it.

Permission scoping

The npm Registry API puts the package name and version in the URL path (/{package}/{version} and /{package}/-/{tarball}), so a rule can pin your agent to one package: it can read that package's metadata and versions and nothing else. You choose the operations it may call, so destructive ones like publishing a package or deleting a tarball revision are not included unless you add them.

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.

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.

GET STARTED

Start building with npm Registry API

Explore with Jentic One
View OpenAPI Document