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

capgent-sdk

v2.0.0

Published

TypeScript SDK for Capgent — agent verification, reverse CAPTCHA challenges, and API identity.

Readme

Install

npm install capgent-sdk

Migrating from capgent-sdk v1.x

Breaking changes in v2:

  • Types & helpers: CapagentErrorCapgentError, CapagentClientOptionsCapgentClientOptions, withCapagentProofwithCapgentProof.
  • Admin HTTP header: x-capagent-admin-keyx-capgent-admin-key.
  • Environment variables stay CAPAGENT_* / NEXT_PUBLIC_CAPAGENT_API_BASE_URL (unchanged).

Basic usage

import { createClient } from "capgent-sdk";
import { parseCanonicalStepsFromInstructions } from "capgent-sdk/parser/heuristic";
import { solveChallengeFromSteps } from "capgent-sdk/solver";

const client = createClient({
  baseUrl: process.env.CAPAGENT_API_BASE_URL ?? "http://localhost:8787",
  apiKey: process.env.CAPAGENT_API_KEY,
  agentName: "my-agent",
  agentVersion: "1.0.0",
});

// 1) Fetch a challenge
const ch = await client.getChallenge();

// 2) Parse the instruction text into canonical byte-steps
const steps = parseCanonicalStepsFromInstructions(ch.instructions);

// 3) Solve the challenge (answer + HMAC)
const { answer, hmac } = await solveChallengeFromSteps({
  data_b64: ch.data_b64,
  nonce: ch.nonce,
  steps,
});

// 4) Verify to get a proof JWT
const proof = await client.verifyChallenge(ch.challenge_id, answer, hmac);

// 5) (Optional) Call a protected endpoint
await client.protectedPing(proof.token);

OpenRouter-based parser (optional)

If you want to parse instructions with an LLM:

import { parseStepsWithOpenRouter } from "capgent-sdk/parser/llm-openrouter";

const steps = await parseStepsWithOpenRouter(ch.instructions, {
  apiKey: process.env.OPENROUTER_API_KEY,
});

Errors

SDK methods throw CapgentError, with:

  • code: one of challenge_failed, verify_failed, protected_ping_failed, agent_register_failed, identity_token_failed, guestbook_sign_failed
  • status: HTTP status code
  • endpoint: the endpoint that failed