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

@proof.com/x401-agent

v0.1.0

Published

x401 agent client for Proof: answers PROOF-REQUEST challenges with a user's Proof credential.

Readme

x401-agent

x401-agent lets your agent call endpoints that require proof of identity.

When an endpoint answers with an x401 proof request, the user presents their credential from their Proof Cloud Wallet, and the agent retries the request with the presented credential.

From a shell, use x401-cli instead.

Installation

npm install @proof.com/x401-agent

Quickstart

Get a Proof access token and export it in the agent's environment:

export PROOF_ACCESS_TOKEN=$(npx @proof.com/x401-cli token --sandbox)

Request the sandbox test endpoint through withX401Fetch:

import { proofWallet, withX401Fetch } from "@proof.com/x401-agent";

const wallet = proofWallet({
  environment: "sandbox",
  accessToken: process.env.PROOF_ACCESS_TOKEN,
});

const fetchWithProof = withX401Fetch(fetch, wallet);
const response = await fetchWithProof(
  "https://try.proof.com/x401/protected?env=fairfax",
);
console.log(response.status);
// => 200

Proof emails the user an approval link. fetchWithProof waits for the approval, retries the request with the proof, and the endpoint answers 200.

Usage

Show the approval link

onApproval receives the pending request. notification.channel indicates where Proof sent the approval link to the user; when it is none, show approval_uri to the user.

import { proofWallet, withX401Fetch } from "@proof.com/x401-agent";

const wallet = proofWallet({
  environment: "sandbox",
  accessToken: process.env.PROOF_ACCESS_TOKEN,
  onApproval: ({ approval_uri, notification }) => {
    if (notification.channel === "none") {
      console.log(`Approve the request: ${approval_uri}`);
    } else {
      console.log(`Proof sent an approval link by ${notification.channel}`);
    }
  },
});

await withX401Fetch(
  fetch,
  wallet,
)("https://try.proof.com/x401/protected?env=fairfax");

Resume a pending request

Keep pending.id to pick the request up with getPresentation.

import {
  awaitPresentation,
  createPresentation,
  getPresentation,
  requirementOf,
  retryWithProofResponse,
} from "@proof.com/x401-agent";

const options = {
  environment: "sandbox",
  accessToken: process.env.PROOF_ACCESS_TOKEN,
};
const url = "https://try.proof.com/x401/protected?env=fairfax";

const challenge = await fetch(url);
const pending = await createPresentation(
  options,
  requirementOf(challenge.headers.get("PROOF-REQUEST")),
);

const presentation = await getPresentation(options, pending.id);
const result = await awaitPresentation(options, presentation);
const response = await retryWithProofResponse(fetch, new Request(url), result);
console.log(response.status);
// => 200

Handle errors

import {
  proofWallet,
  withX401Fetch,
  X401AgentError,
} from "@proof.com/x401-agent";

const fetchWithProof = withX401Fetch(
  fetch,
  proofWallet({
    environment: "sandbox",
    accessToken: process.env.PROOF_ACCESS_TOKEN,
  }),
);

try {
  await fetchWithProof("https://try.proof.com/x401/protected?env=fairfax");
} catch (error) {
  if (error instanceof X401AgentError && error.code === "proof_rejected") {
    console.log("The endpoint rejected the proof:", error.result);
  } else {
    throw error;
  }
}

Configuration

environment is "sandbox" or "production".

proofWallet({
  environment: "production",
  accessToken: process.env.PROOF_ACCESS_TOKEN,
});

fetch replaces the global fetch for calls to Proof.

proofWallet({
  environment: "sandbox",
  accessToken: process.env.PROOF_ACCESS_TOKEN,
  fetch: myFetch,
});

Errors

| code | Meaning | What to do | | ----------------------- | ---------------------------------------------------------------- | ------------------------------------- | | invalid_proof_request | The endpoint's PROOF-REQUEST is not a single valid request | Report it to the endpoint's owner | | proof_rejected | The endpoint rejected the proof; error.result holds its reason | Start again with a new request | | unauthorized | Proof refused the access token | Refresh the token or sign the user in | | rate_limited | Too many requests; error.retryAfter, when set, is in seconds | Wait before retrying | | presentation_failed | Proof answered with an error status or an unexpected body | Check error.message, then retry |

Links

License

Apache-2.0