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

@nirholas/erc-8004-demo-agent

v1.0.0

Published

a demo agent to showcase 8004 registration best practices

Readme

8004-demo-agent

npm version

ERC-8004 · Registration Guide · Reputation Guide · Agent0 SDK


A demo agent to showcase ERC-8004 registration best practices.

Built using create-8004-agent

Quick Start

1. Install dependencies

npm install

2. Configure environment

Edit .env and add your API keys:

# Already set if wallet was auto-generated
PRIVATE_KEY=your_private_key

# Get from https://pinata.cloud (free tier works)
PINATA_JWT=your_pinata_jwt

# Get from https://platform.openai.com
OPENAI_API_KEY=your_openai_key

3. Fund your wallet

Your agent wallet: 0x66615821b1340A544700c4bfdc8868Bf349C675B

Get testnet ETH from: https://cloud.google.com/application/web3/faucet/ethereum/sepolia

4. Register on-chain

npm run register

This will:

  • Upload your agent metadata to IPFS
  • Register your agent on Ethereum Sepolia
  • Output your agent ID and 8004scan link

5. Start the A2A server

npm run start:a2a

Test locally: http://localhost:3000/.well-known/agent-card.json

6. Start the MCP server

npm run start:mcp

Project Structure

8004-demo-agent/
├── src/
│   ├── register.ts      # Registration script
│   ├── agent.ts         # LLM logic
│   └── a2a-server.ts   # A2A server
│   └── mcp-server.ts   # MCP server
├── .env                 # Environment variables (keep secret!)
└── package.json

OASF Skills & Domains (Optional)

Add capabilities and domain expertise to help others discover your agent.

Edit src/register.ts and uncomment/add before registerIPFS():

// Add skills (what your agent can do)
agent.addSkill('natural_language_processing/natural_language_generation/summarization');
agent.addSkill('analytical_skills/coding_skills/text_to_code');

// Add domains (areas of expertise)  
agent.addDomain('technology/software_engineering');
agent.addDomain('finance_and_business/investment_services');

Browse the full taxonomy: https://schema.oasf.outshift.com/0.8.0

Going Live

By default, your agent is registered with active: false. This is intentional - it lets you test without appearing in explorer listings.

When you're ready for production:

  1. Edit src/register.ts and change agent.setActive(false) to agent.setActive(true)
  2. Re-run npm run register to update your agent's metadata

Next Steps

  1. Update the endpoint URLs in src/register.ts with your production domain
  2. Customize the agent logic in src/agent.ts
  3. Deploy to a cloud provider (Vercel, Railway, etc.)
  4. Re-run npm run register if you change metadata

Resources

License

MIT