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

@semiont/api-client

v0.4.19

Published

Semiont API SDK - types, client, and utilities

Readme

@semiont/api-client

Tests codecov npm version npm downloads License

TypeScript SDK for Semiont — a knowledge management system for semantic annotations, AI-powered analysis, and collaborative document understanding.

The api-client is a transparent proxy to @semiont/make-meaning. The browser writes code as though it has direct access to the knowledge system. HTTP, auth, SSE, and caching are internal concerns.

The 7 Verbs

The API is organized by the domain's verbs — the same verbs that organize the EventBus protocol, the documentation, and the backend actors:

import { SemiontApiClient } from '@semiont/api-client';

const semiont = new SemiontApiClient({ baseUrl, eventBus, getToken });

// Browse — reads from materialized views
const resource = semiont.browse.resource(resourceId);       // Observable
const annotations = semiont.browse.annotations(resourceId); // Observable
const content = await semiont.browse.resourceContent(rid);   // Promise

// Mark — annotation CRUD + AI assist
await semiont.mark.annotation(resourceId, input);
await semiont.mark.delete(resourceId, annotationId);
semiont.mark.assist(resourceId, 'linking', options);         // Observable (progress)

// Bind — reference linking
await semiont.bind.body(resourceId, annotationId, operations);

// Gather — LLM context assembly
semiont.gather.annotation(annotationId, resourceId);         // Observable (progress → context)

// Match — semantic search
semiont.match.search(resourceId, referenceId, context);      // Observable (results)

// Yield — resource creation + AI generation
await semiont.yield.resource(data);
semiont.yield.fromAnnotation(resourceId, annotationId, opts); // Observable (progress)

// Beckon — attention coordination
semiont.beckon.attention(annotationId, resourceId);           // void (ephemeral)

// + Job, Auth, Admin namespaces

Return Type Conventions

  • Browse live queriesObservable (events-stream driven, cached in BehaviorSubject)
  • Browse one-shot readsPromise (fetch once, no cache)
  • Commands (mark, bind, yield.resource) → Promise (fire-and-forget)
  • Long-running ops (gather, match, yield.fromAnnotation, mark.assist) → Observable (progress + result)
  • Ephemeral signals (beckon) → void

Auth is Internal

The client takes a getToken function at construction. No per-call auth:

const semiont = new SemiontApiClient({
  baseUrl: baseUrl('http://localhost:4000'),
  eventBus: new EventBus(),
  getToken: () => accessToken(token),
});

// No auth on individual calls
const annotations = semiont.browse.annotations(resourceId);
await semiont.mark.annotation(resourceId, input);
await semiont.bind.body(resourceId, annotationId, operations);

Update the token getter at any time via semiont.setTokenGetter(getter).

Installation

npm install @semiont/api-client

Prerequisites: Semiont backend running. See Running the Backend.

Documentation

Key Features

  • Verb-oriented — 7 domain namespaces mirror @semiont/make-meaning's actor model
  • Type-safe — OpenAPI types from @semiont/core, branded identifiers
  • Observable reads — live-updating views via EventBus + events-stream SSE
  • Framework-agnostic — pure TypeScript + RxJS, no React dependency

License

Apache-2.0