npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@jayteelabs/pi-nous-portal-provider

v0.2.3

Published

Pi provider package for Nous Research Portal inference.

Readme

@jayteelabs/pi-nous-portal-provider

Pi package that registers the nous-portal provider for Nous Research Portal.

Install

pi install npm:@jayteelabs/pi-nous-portal-provider

Usage

# Export NOUS_API_KEY from your shell or secrets manager before running Pi.
pi -p nous-portal -m openai/gpt-5.5
pi -e ./pi-nous-portal-provider --list-models

For Portal OAuth, run Pi and choose the subscription flow:

/login → Use a subscription → Nous Research Portal

For a direct inference key, choose the API-key flow:

/login → Use an API key → Nous Research Portal

Without NOUS_API_KEY or stored Portal OAuth credentials, the provider registers its static fallback catalog under a direct-key provider alias so Pi can discover Nous in the API-key /login flow. After an interactive Portal OAuth login, Pi refreshes its model registry and this extension re-registers the cached Portal catalog. Interactive sessions also refresh the Portal catalog registration on session_start.

Configuration

  • NOUS_API_KEY: direct inference API key.
  • NOUS_PORTAL_BASE_URL: defaults to https://portal.nousresearch.com.
  • NOUS_INFERENCE_BASE_URL: defaults to https://inference-api.nousresearch.com/v1.
  • NOUS_CLIENT_ID: defaults to hermes-cli because it doesn't accept anything else currently.
  • NOUS_MIN_KEY_TTL_SECONDS: defaults to 1800.

Models

Nous Portal /models is the model allowlist. Matching OpenRouter /models entries enrich that allowlist with context, pricing, image input, and reasoning metadata. The static fallback catalog is registered when live discovery is unavailable with usable credentials, and during unauthenticated startup/session registration so Pi's API-key login provider discovery can list Nous. Pi filters custom OAuth provider IDs out of the API-key picker, so this package uses the internal nous-portal-api-key provider ID for the direct-key login entry while displaying it as Nous Research Portal. Expired or invalid OAuth credentials still keep the OAuth provider model list blank. When both stored Portal OAuth credentials and a direct API key exist, the OAuth catalog takes precedence and the direct-key alias is cleared so /model shows one Nous model set. See docs/models.md.

Testing

Run the offline unit tests with npm test. Live provider compatibility checks are isolated behind npm run test:compat and skip unless the required Nous model/API-key environment variables are set. See docs/testing.md.