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

@antseed/cli

v0.1.42

Published

Antseed Network CLI and Web Dashboard

Downloads

3,782

Readme

Antseed CLI + Dashboard

Command-line interface and web dashboard for the AntSeed Network — a P2P network for AI services.

Important: AntSeed is designed for providers who build differentiated services on top of AI APIs — such as TEE-secured inference, domain-specific skills and agents, fine-tuned models, or managed product experiences. Simply reselling raw API access or subscription credentials is not the intended use and may violate your upstream provider's terms of service. Subscription-based plugins (provider-claude-code, provider-claude-oauth) are for testing and development only.

Commands

| Command | Description | |---------|-------------| | antseed init | Install trusted provider and router plugins | | antseed seed | Start providing AI services on the P2P network | | antseed connect | Start the buyer proxy and connect to sellers | | antseed connection get | Show current session state (pinned service, peer) | | antseed connection set | Update service/peer overrides on a running proxy | | antseed connection clear | Clear service/peer overrides on a running proxy | | antseed plugin add <pkg> | Install a provider or router plugin from npm | | antseed plugin remove <name> | Remove an installed plugin | | antseed plugin list | List installed plugins | | antseed status | Show current node status | | antseed config | Manage configuration (show, set, seller show/set, buyer show/set, init) | | antseed dashboard | Start the web dashboard for monitoring and configuration | | antseed dev | Run seller + buyer locally for development and testing | | antseed browse | Browse available services, prices, and reputation on the network |

Plugins

Antseed uses an open plugin ecosystem. Plugins are installed into ~/.antseed/plugins/ via npm.

Providers connect your node to an upstream AI API (seeder mode):

antseed plugin add @antseed/provider-anthropic    # API key auth
antseed plugin add @antseed/provider-claude-code   # Claude Code keychain auth
antseed seed --provider anthropic

Routers select peers and proxy requests (consumer mode):

antseed plugin add @antseed/router-local
antseed connect --router local

Run antseed init to install all trusted plugins interactively.

Configuration

Configuration is stored at ~/.antseed/config.json by default. Use -c / --config to specify an alternative path.

Runtime env variables are loaded via dotenv from .env.local and .env in the current working directory. See .env.example for supported keys.

Enable debug logs with either:

antseed -v <command>

or:

ANTSEED_DEBUG=1 antseed <command>

For dashboard frontend debug logging, set:

VITE_ANTSEED_DEBUG=1

Initialize a new config:

antseed config init

Pricing is configured in USD per 1M tokens with role-specific defaults and optional provider/service overrides. You can also set node displayName, an optional seller publicAddress, and per-service category tags announced in discovery metadata:

{
  "identity": {
    "displayName": "Acme Inference - us-east-1"
  },
  "seller": {
    "publicAddress": "peer.example.com:6882",
    "pricing": {
      "defaults": {
        "inputUsdPerMillion": 10,
        "outputUsdPerMillion": 10
      },
      "providers": {
        "anthropic": {
          "services": {
            "claude-sonnet-4-5-20250929": {
              "inputUsdPerMillion": 12,
              "outputUsdPerMillion": 18
            }
          }
        }
      }
    },
    "serviceCategories": {
      "anthropic": {
        "claude-sonnet-4-5-20250929": ["coding", "privacy"]
      }
    }
  },
  "buyer": {
    "maxPricing": {
      "defaults": {
        "inputUsdPerMillion": 100,
        "outputUsdPerMillion": 100
      }
    }
  }
}

Service categories are normalized to lowercase tags. Recommended tags include: privacy, legal, uncensored, coding, finance, tee (custom tags are also allowed).

Bound Agent

Providers can wrap their service with a bound agent — a read-only, knowledge-augmented AI service that injects a persona, guardrails, and on-demand loaded knowledge into buyer requests.

{
  "seller": {
    "agentDir": "./my-agent"
  }
}

The agent directory contains an agent.json manifest that defines the agent's persona, guardrails, and knowledge modules. Knowledge modules are loaded on demand via the antseed_load_knowledge tool — the LLM decides which modules to load during the conversation and only relevant knowledge is brought into context. Buyers only see the LLM's natural response, never the injected content or internal tool calls.

See the @antseed/bound-agent README for the full manifest reference and directory structure.

Role-first config examples:

# Identity / metadata display name
antseed config set identity.displayName "Acme Inference - us-east-1"

# Seller defaults
antseed config seller set pricing.defaults.inputUsdPerMillion 12
antseed config seller set pricing.defaults.outputUsdPerMillion 36

# Seller per-service override for a provider
antseed config seller set pricing.providers.anthropic.services '{"claude-sonnet-4-5-20250929":{"inputUsdPerMillion":14,"outputUsdPerMillion":42}}'

# Seller per-service category tags announced in metadata
antseed config seller set serviceCategories.anthropic.claude-sonnet-4-5-20250929 '["coding","legal"]'

# Seller public address override for load-balanced deployments
antseed config seller set publicAddress "peer.example.com:6882"

# Buyer max pricing
antseed config buyer set maxPricing.defaults.inputUsdPerMillion 25
antseed config buyer set maxPricing.defaults.outputUsdPerMillion 75

Runtime-only overrides (do not write your config file):

antseed seed --provider anthropic --input-usd-per-million 10 --output-usd-per-million 30
antseed connect --router local --max-input-usd-per-million 20 --max-output-usd-per-million 60

Session overrides (live, while proxy is running)

After antseed connect is running, you can override the service or peer for all subsequent requests without restarting:

# Pin all requests to a specific service (overrides whatever the tool sends)
antseed connection set --service claude-opus-4-6

# Pin all requests to a specific peer (bypasses router for peer selection)
antseed connection set --peer <64-char-hex-peer-id>

# Combine both in one command
antseed connection set --service claude-sonnet-4-6 --peer <peer-id>

# Check current session state
antseed connection get

# Clear individual overrides
antseed connection clear --service
antseed connection clear --peer

# Clear all overrides at once
antseed connection clear

Session overrides are stored in ~/.antseed/buyer.state.json and picked up by the running proxy immediately via file-watching. The desktop app reads and writes the same file to expose service/peer selection in its UI.

The service override rewrites the model field in the request body before routing, so peer selection, pricing, and the forwarded request all reflect the overridden service — regardless of what the tool (e.g. Claude Code) originally requested.

Settlement Runtime (Seeder)

antseed seed can enable automatic session settlement when payment config is present. antseed connect can also enable buyer-side escrow/session locking with the same payment config.

Common runtime env controls:

  • ANTSEED_ENABLE_SETTLEMENT=true|false
  • ANTSEED_SETTLEMENT_IDLE_MS=30000
  • ANTSEED_DEFAULT_ESCROW_USDC=1
  • ANTSEED_AUTO_FUND_ESCROW=true|false
  • ANTSEED_SELLER_WALLET_ADDRESS=0x...

Crypto settlement also requires config.payments.crypto values in your config file:

  • chainId (base or arbitrum)
  • rpcUrl
  • escrowContractAddress
  • usdcContractAddress

If ANTSEED_ENABLE_SETTLEMENT is not explicitly set and the RPC endpoint is unreachable, the CLI now auto-disables settlement for that run and logs a warning instead of looping RPC network-detection errors. Set ANTSEED_ENABLE_SETTLEMENT=true to force-enable settlement checks.

Runtime behavior:

  • session opens -> optional escrow deposit
  • session finalizes -> exact on-chain split settlement (seller payout + platform fee + buyer refund remainder)
  • no receipts -> escrow refund path

Provider-specific options are configured via each plugin's config schema (see antseed plugin add --help).

Development

npm install
npm run build
npm run dev

Links

  • Node SDK: @antseed/node (../node)