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

@relaycore/cli

v0.1.4

Published

RelayCore CLI - Production-grade agent platform

Readme

RelayCore CLI

The official command-line interface for RelayCore, the agentic finance infrastructure on Cronos. This tool scaffolds projects, manages identities, and spins up local development environments for autonomous agents.

📚 Full Documentation: docs.relaycore.xyz/cli

Features

  • 🚀 Scaffold Projects: Generate production-ready Agent, Service, or Full-Stack templates.
  • 🔐 Identity Management: Register agents and services on-chain (Cronos).
  • 🛠️ Local Development: Run a full local stack with MCP server, Next.js dashboard, and hot-reloading.
  • 🤖 MCP Integration: Built-in support for Model Context Protocol servers.

Installation

npm install -g @relaycore/cli

# or via pnpm
pnpm add -g @relaycore/cli

Quick Start

1. Initialize a Project

Create a new agent project with a standard directory structure:

relaycore init my-agent
# Select template: Agent (MCP), Service (Express), or Full Stack
cd my-agent

2. Login & Authenticate

Authenticate your machine to interact with the RelayCore network:

relaycore auth login
# Opens browser to authenticate and saves session

3. Register Identity

Before you can transact, your agent needs an on-chain identity (Relay ID):

# Register an Agent (Consumer)
relaycore agent register
# Prompts for: Name, Description, Capabilities

# Register a Service (Provider)
relaycore service register
# Prompts for: Service Category, Input/Output Schemas, Price

4. Start Development Environment

Run your agent locally with the RelayCore harness:

relaycore dev

This command:

  • Starts your MCP Server (port 3001)
  • Luanches the Relay Dashboard (port 3000)
  • Connects to Cronos Testnet via your local wallet configuration
  • Watches for file changes

Commands Reference

init

relaycore init <project-name>

Scaffolds a new project. You will be prompted to choose a template:

  • Agent: Minimal MCP server template.
  • Service: Express.js service provider template.
  • Full: Monorepo with both + Next.js frontend.

auth

relaycore auth login   # Login via web
relaycore auth logout  # clear local session
relaycore auth whoami  # Show current user details

agent

relaycore agent register    # Interactively register new agent
relaycore agent list        # List agents owned by you
relaycore agent update      # Update metadata for existing agent

service

relaycore service register  # Register new service
relaycore service list      # List your services

route

Create x402-protected proxy routes for any API endpoint.

relaycore route add         # Create a new paid proxy route
relaycore route list        # List your routes with earnings
relaycore route remove <id> # Remove a route
relaycore route test <id>   # Test a route (shows 402 requirements)

Example: Make any API paid

relaycore route add \
  --url https://api.example.com/data \
  --price 0.01 \
  --name "Data API"

# Output:
#   Route Created Successfully
#   Proxy URL: https://api.relaycore.xyz/proxy/abc123

Requests to the proxy URL require x402 payment before being forwarded to the upstream API.

dev

relaycore dev

Starts the development studio. Requires a valid relaycore.config.ts in the project root.

Configuration

The CLI looks for a .env file in your project root for local overrides:

RELAY_API_URL=https://api.relaycore.xyz  # Default
RELAY_ENV=testnet                        # default: testnet
PRIVATE_KEY=...                          # Optional: For script deploy

License

MIT