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

@spheredata/sdk

v0.0.1

Published

SPHERE client SDK — talks to the SPHERE backend (auth, metered agent, account).

Downloads

44

Readme

@spheredata/sdk

The SPHERE client SDK — the single integration surface for the SPHERE metered AI backend. One client for the web portal, the Electron desktop app, and the CLI; surfaces differ only in where the token is stored and which tools run locally.

The product/brand is SPHERE — this package is published under the @spheredata npm scope.

Install

npm i @spheredata/sdk

Quick start

import { createSphere } from "@spheredata/sdk";

const sphere = createSphere({ portal: "adrc" }); // web: sessionStorage by default

await sphere.signIn({ email, password });
const res = await sphere.streamAgent({ messages, tools }); // SSE Response, one turn/call
const balance = await sphere.getBalance();

The portal slug is sent as ?portal=<slug> on every metered request so the backend applies that client's config (model, margin) and tags usage.

createSphere(options)

| Option | Default | Purpose | | --- | --- | --- | | portal | "adrc" | Attribution slug; sets server-side config + usage tag. | | tokenStore | sessionStorage (else in-memory) | Sync string KV { get, set, clear }. Inject safeStorage (desktop) or a file store (CLI). | | onAuthInvalid | no-op | Called on any hard auth failure (store is cleared) — drop to a login screen. | | fetch | globalThis.fetch | Override the fetch implementation. | | apiBase, appId | SPHERE defaults | Point at a different backend / app. |

Token store contract: operations must be synchronous and atomic — single-flight refresh relies on the rotated bundle being persisted before the next read. The SDK refreshes transparently (proactive near-expiry, retry-once-on-401).

Client methods

createSphere() returns:

  • Auth: signUp, signIn, signOut, oauthUrl, isSignedIn()
  • Agent: ask, streamAgent(payload, signal) → Response (SSE, one model turn per call)
  • Account / wallet: getAccount, getBalance, listCredits, buyCredits, redeem
  • Metering: charge({ bytes, op, tag })pre-charge before a data op; returns { ok:false, insufficient:true, ... } on a 402 (an expected business outcome, not thrown). When charging is gated off server-side, returns { ok:true, charged:false, cost_usd:0 }.
  • Identity: portal, appId, apiBase

A ready-made default instance for the ADRC portal is also exported:

import { sphere } from "@spheredata/sdk";

Pairs with

@spheredata/embed — the <sphere-agent> web component. Pass the client in via el.sphere = sphere.

License

MIT