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

browsy-ai

v0.1.2

Published

Zero-render browser SDK for AI agents — core client + LangChain, OpenAI, and Vercel AI integrations

Readme

browsy-ai

Zero-render browser SDK for AI agents. Browse, interact with, and extract data from web pages without launching a browser.

browsy converts HTML into a Spatial DOM — a flat list of interactive elements with bounding boxes, roles, and states — at a fraction of the cost and latency of screenshot-based automation.

| | Screenshot-based | browsy | |---|---|---| | Runtime | Chromium process | None (Rust library) | | Memory | ~300MB/page | ~5MB/page | | Latency | 2-5s | <100ms | | Token cost | ~10k+ | ~200-800 |

Install

npm install browsy-ai

Framework dependencies are optional — install only what you use:

npm install browsy-ai @langchain/core    # + LangChain.js
npm install browsy-ai openai             # + OpenAI
npm install browsy-ai ai                 # + Vercel AI SDK

Requires Node.js 22+ and the browsy CLI for the REST server:

cargo install browsy

Quick Start

Core SDK

import { BrowsyContext } from "browsy-ai";

const ctx = new BrowsyContext({ port: 3847 });

const page = await ctx.executeToolCall("browse", { url: "https://example.com" });
console.log(page);

const info = await ctx.executeToolCall("pageInfo", {});
console.log(info);

LangChain.js

import { getTools } from "browsy-ai/langchain";
import { ChatOpenAI } from "@langchain/openai";
import { createReactAgent } from "@langchain/langgraph/prebuilt";

const tools = getTools();  // 14 LangChain tool instances
const llm = new ChatOpenAI({ model: "gpt-4o" });
const agent = createReactAgent({ llm, tools });

const result = await agent.invoke({
  messages: [{ role: "user", content: "Go to news.ycombinator.com and list the top 5 stories" }],
});

OpenAI Function Calling

import { getToolDefinitions, handleToolCall } from "browsy-ai/openai";

const tools = getToolDefinitions();
const result = await handleToolCall("browsy_browse", { url: "https://example.com" });

Vercel AI SDK

import { browsyTools } from "browsy-ai/vercel-ai";
import { generateText } from "ai";
import { openai } from "@ai-sdk/openai";

const result = await generateText({
  model: openai("gpt-4o"),
  tools: browsyTools(),
  prompt: "Go to example.com and summarize it",
  maxSteps: 10,
});

Available Tools

All integrations expose these 14 browsy tools:

| Tool | Parameters | Description | |------|-----------|-------------| | browsy_browse | url, format?, scope? | Navigate to a URL | | browsy_click | id | Click an element by ID | | browsy_type_text | id, text | Type into an input field | | browsy_check | id | Check a checkbox/radio | | browsy_uncheck | id | Uncheck a checkbox/radio | | browsy_select | id, value | Select a dropdown option | | browsy_search | query, engine? | Web search | | browsy_login | username, password | Log in using detected form | | browsy_enter_code | code | Enter 2FA/verification code | | browsy_find | text?, role? | Find elements by text or role | | browsy_get_page | format?, scope? | Get current page with form state | | browsy_page_info | — | Page metadata and suggested actions | | browsy_tables | — | Extract structured table data | | browsy_back | — | Go back in history |

Session Isolation

Each agent gets its own browsing session with independent cookies, history, and form state:

const ctx = new BrowsyContext();

const page1 = await ctx.executeToolCall("browse", { url: "https://a.com" }, "agent-1");
const page2 = await ctx.executeToolCall("browse", { url: "https://b.com" }, "agent-2");

Configuration

const ctx = new BrowsyContext({
  port: 3847,                  // REST server port (default: 3847)
  autoStart: true,             // Auto-start browsy serve (default: true)
  allowPrivateNetwork: false,  // Allow private network URLs (default: false)
  serverTimeout: 10_000,       // Startup timeout in ms (default: 10000)
});

Zod Schemas

All tool parameter schemas are exported as Zod objects for custom integrations:

import { BrowseParams, ClickParams, TOOL_DESCRIPTIONS, TOOL_SCHEMAS } from "browsy-ai";

const parsed = BrowseParams.parse({ url: "https://example.com" });

for (const { name, method, schema } of TOOL_SCHEMAS) {
  console.log(name, TOOL_DESCRIPTIONS[name]);
}

Documentation

Full documentation at browsy.dev

License

MIT