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

@usegraft/content-api

v1.0.0-beta.9

Published

A versioned read-only HTTP transport for Graft's authored content index.

Readme

@usegraft/content-api

A versioned, read-only HTTP transport for Graft's authored content index.

Part of Graft, a CMS built so an AI agent is the primary operator.

Install

npm i @usegraft/content-api

Serve authored content

graft serve mounts this handler at /api/content/v1. You can also mount it in any runtime that accepts Web Request and Response objects.

import { createContentApiHandler } from "@usegraft/content-api";
import { createDb, createDbIndexReader } from "@usegraft/db";
import { collections } from "./graft.config";

const database = createDb(process.env.DATABASE_URL!);

export const GET = createContentApiHandler({
  collections: Object.keys(collections),
  branch: "main",
  index: createDbIndexReader(database.db),
});

The handler serves:

  • GET /api/content/v1/documents?collection=pages
  • GET /api/content/v1/documents?collection=pages&slug=home
  • GET /api/content/v1/search?collection=pages&query=pricing

An endpoint represents one branch. It does not accept a branch query parameter, so a caller cannot switch a production endpoint to preview content.

The handler does not authenticate callers. Put a proxy or check Authorization before invoking it if the index is not public. The handler does not close its reader or database. The application that created those handles owns their lifecycle.

Use the existing typed SDK

The remote reader implements ContentIndexReader, so the framework-agnostic client and framework adapters need no HTTP-specific API.

import { createContentApiReader } from "@usegraft/content-api";
import { createClient } from "@usegraft/sdk-core";
import { collections } from "./graft.config";

const graft = createClient({
  index: createContentApiReader({
    endpoint: "https://cms.example.com/api/content/v1",
    headers: { authorization: `Bearer ${process.env.GRAFT_CONTENT_TOKEN}` },
  }),
  collections,
});

const page = await graft.getDocument("pages", "home");
const hits = await graft.searchDocuments("pages", "pricing");

Pass fetch to createContentApiReader when the runtime needs a custom implementation. headers are static and sent on every request, which suits an auth token or proxy header.


MIT. Repository