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

@conciergeprotocol/client

v0.2.0

Published

Call any Concierge Agent Protocol front door.

Readme

@conciergeprotocol/client

Call a Concierge Agent Protocol front door from JavaScript. Give it a domain. It reads agent.txt, posts one message, and waits for the company's reply.

The protocol is at conciergeprotocol.org. Source is at github.com/conciergeprotocol/js.

Install

npm install @conciergeprotocol/client

Node.js 18 or newer.

Ask

import { createClient } from '@conciergeprotocol/client'

const cap = createClient({ from: 'agent:my-assistant' })

const answer = await cap.ask('example.com', 'Do you have a free plan?')
console.log(answer.reply)

from is agent: plus 1 to 64 letters, numbers, dots, underscores, or hyphens. It tells the company who is calling.

A follow-up sends only the new question. The company keeps the earlier turns.

const thread = cap.thread('example.com')
await thread.ask('What do you sell?')
const price = await thread.ask('How much is the cheapest paid plan?')

When there is no front door

discover returns null. ask throws NoDoorError. That is the signal to browse the site instead.

discover reads https://{domain}/agent.txt. A redirect may go to any https URL. When that file is missing, an HTML page, or has no CAP line, it reads the homepage and follows Link: <url>; rel="agent" or <link rel="agent" href="url"> in the head. door.origin stays the company's domain. door.source is redirect, link-header, or link-tag when the file was not at the root.

import { createClient, NoDoorError } from '@conciergeprotocol/client'

const cap = createClient({ from: 'agent:my-assistant' })

try {
  const answer = await cap.ask('example.com', 'What are your hours?')
  console.log(answer.reply)
} catch (error) {
  if (error instanceof NoDoorError) {
    // Browse the site.
  }
}

Still working

ask waits up to two minutes. If the company is still answering, the message comes back with status: 'working' and no reply. Read it again with get. Do not write a reply while the status is working.

const message = await cap.ask('example.com', 'What are your hours?')
if (message.status === 'working') {
  const later = await cap.get('example.com', message.id)
}

A failed message is a result, including login_required. It is not thrown.

Account questions

login opens the company's page. finishLogin stores the token for that door, and the next ask sends it. Pass your own token store to createClient when the token should outlive the process.

const cap = createClient({
  from: 'agent:my-assistant',
  tokens: {
    async get(origin) {},
    async set(origin, token) {},
    async delete(origin) {}
  }
})

await cap.login('example.com')
await cap.finishLogin(callbackUrl)

License

Apache 2.0