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

@corbits/system-one

v0.3.1

Published

Typed-decision evaluation client for System One (Jev-class) models: arktype question/decision schemas, endpoint configuration with gateway override, and timeout/fallback semantics.

Readme

@corbits/system-one

Typed choice, score and yes/no decisions about a JSON state from TypeSafe's Jev model, returned as a validated result or a typed fallback. An inference provider for Corbits and Interchange agents: registers as an @intx/inference adapter, and also works standalone through evaluate().

Why @corbits/system-one?

  1. Typed decisions, not free text. You send questions with ids; you get back one validated decision per id, with probabilities and confidence. No prompt parsing.
  2. Failures are data. A missing key, timeout, HTTP error or bad body returns a FallbackResult with a reason, so a gate can fail closed without a try. Only invalid caller input throws.
  3. One call, many questions. Every question in a list goes out in one POST, bounded by a 1.5 s default timeout.

It evaluates structured state against questions. For open-ended chat completions, use a general inference provider such as @corbits/openai-responses.

Install

bun add @corbits/system-one @intx/inference@^0.4.0 @intx/types@^0.4.0

Runs on Bun >= 1.2 or Node >= 24.

Quickstart

Needs TYPESAFE_API_KEY set.

import { evaluate } from "@corbits/system-one";

const result = await evaluate({
  state: { action: "deploy", env: "production" },
  questions: [
    {
      id: "escalate",
      type: "boolean",
      instructions: "Must this request be escalated for human approval?",
    },
  ],
});

console.log(result.fallback ? result.reason : result.decisions);

On success it prints one decision per question, or the fallback reason on failure:

[{ id: "escalate", type: "noul", noul: 0.91 }];

Boolean questions answer as noul, a probability from 0 to 1 that the answer is yes.

Where it fits

Interchange runs AI agents as principals (accounts that hold their own identity, permissions and credentials). Corbits packages add what an agent product needs around it.

  • Runs in: the agent sidecar (the runtime next to each agent), or any process. evaluate() needs no Interchange runtime.
  • Plugs into: the @intx/inference adapter registry, as the adapter for the corbits-system-one provider id.
  • Pairs with: @corbits/openai-responses and @corbits/ollama-adapter, the other Corbits inference providers.

Reference

| Export | Description | | --------------------------------- | ----------------------------------------------------------------------------------- | | evaluate(input, options?) | Runs one evaluation. Returns EvaluateResult: decisions or a FallbackResult. | | createSystemOneAdapter(config?) | Returns a ProviderAdapter for runInference. config is an EvaluateConfig. | | createSystemOneAdapterFactory | Interchange AdapterFactory for SIDECAR_ADAPTER_MANIFEST; takes offering quirks. | | SYSTEM_ONE_PROVIDER | The "corbits-system-one" provider id. | | DEFAULT_TIMEOUT_MS | 1500, the default timeoutMs. | | SystemOneError | Thrown for invalid input or a custom endpoint without a url. | | SystemOneTelemetryEvent | Schema and type for events passed to onTelemetry. | | EvaluateOptions, EvaluateDeps | Types for options: onTelemetry, and deps: { fetch, scheduler }. |

Question, QuestionList, Decision, EvaluateInput, EvaluateConfig, EndpointConfig, EvaluateResult and FallbackResult are exported as arktype schemas and types.

Questions

| type | Fields | Decision fields | | --------- | ------------------------------------------------------------------------------- | ------------------------------------------------ | | choice | instructions, criteria (option name → description or null, 1–255 options) | choice, probabilities, confidence | | score | instructions, criteria (2–10 descriptions) | score, legend, probabilities, confidence | | boolean | instructions, optional criteria: { true?, false? } | noul | | noul | Same as boolean | noul |

Every question has an id, unique within the list.

Config

input.config for evaluate, or the argument to createSystemOneAdapter:

| Field | Type | Default | Description | | ----------- | ---------------- | ---------------------- | -------------------------------------------------------------------------------- | | endpoint | EndpointConfig | { kind: "official" } | official, gateway, or custom with a url. Each takes an optional model. | | timeoutMs | number | 1500 | Bound for the whole round trip. | | apiKey | string | from the environment | Overrides the environment key. |

Endpoints and keys

| kind | URL | Default model | Key from the environment | | ---------- | ---------------------------------------------------- | ----------------- | ---------------------------------------------- | | official | https://api.typesafe.ai/v1/systemone | jev-latest | TYPESAFE_API_KEY | | gateway | https://ai-gateway.vercel.sh/typesafe/v1/systemone | typesafe-ai/jev | AI_GATEWAY_API_KEY, then VERCEL_OIDC_TOKEN | | custom | url | typesafe-ai/jev | SYSTEM_ONE_API_KEY |

SYSTEM_ONE_API_KEY is also a supported alias on every endpoint, read after the endpoint's own key.

Fallback reasons

| reason | When | | ------------- | ------------------------------------------------------------- | | no-key | No key in apiKey or the environment. No request is sent. | | timeout | The round trip, including the body read, exceeds timeoutMs. | | network | The request fails before a response. | | http-error | Non-2xx response. httpStatus holds the status. | | parse-error | The body is not JSON or fails validation. |

detail carries the underlying message.

Using with Interchange

Register the adapter under SYSTEM_ONE_PROVIDER and pass questions per call in providerOptions.systemOne ({ state?, questions? }). Without state, the adapter sends the transcript text as state. Without questions, it asks one boolean question with id response.

import { createDependencies, runInference } from "@intx/inference";
import {
  createSystemOneAdapter,
  SYSTEM_ONE_PROVIDER,
  type QuestionList,
} from "@corbits/system-one";

const deps = createDependencies({
  has: (provider) => provider === SYSTEM_ONE_PROVIDER,
  resolve: () => createSystemOneAdapter(),
});

const questions = [
  {
    id: "escalate",
    type: "boolean",
    instructions: "Must this request be escalated for human approval?",
  },
] satisfies QuestionList;

let seq = 0;
for await (const event of runInference({
  deps,
  source: {
    id: "system-one",
    provider: SYSTEM_ONE_PROVIDER,
    baseURL: "https://api.typesafe.ai/v1/systemone",
    credentialId: "TYPESAFE_API_KEY",
    model: "jev-latest",
  },
  turns: [
    {
      role: "user",
      timestamp: Date.now(),
      content: [{ type: "text", text: "Deploy to production?" }],
    },
  ],
  inferenceOptions: { providerOptions: { systemOne: { questions } } },
  nextSeq: () => seq++,
  readMaterial: (id) => {
    const secret = process.env[id];
    if (secret === undefined) throw new Error(`${id} is not set`);
    return { secret };
  },
})) {
  if (event.type === "inference.text.delta")
    console.log(JSON.parse(event.data.token));
}

The adapter emits one inference.text.delta per decision, whose token is the decision as JSON, then an inference.usage event. The harness supplies the credential through readMaterial and owns retries. A malformed response body is a ProtocolMismatchError, not a fallback.

Manifest factory

createSystemOneAdapterFactory(source, quirks?) is an Interchange AdapterFactory, so a stock sidecar loads it from SIDECAR_ADAPTER_MANIFEST with no custom code:

[
  {
    "provider": "corbits-system-one",
    "specifier": "@corbits/system-one",
    "export": "createSystemOneAdapterFactory"
  }
]

The hub offering's quirks are validated and all optional:

{
  "endpoint": {
    "kind": "custom",
    "url": "https://opencode.ai/zen/v1/systemone"
  },
  "model": "jev-1.13",
  "questions": [{ "type": "boolean", "id": "gate", "instructions": "Allow?" }],
  "state": {}
}

Without endpoint, the adapter posts to the catalog provider's baseURL + /systemone, the host the offering's credential was issued for. A model quirk (top level or on endpoint) is the model sent on the wire, so one catalog model can be served by providers that name it differently. questions and state are per-call defaults; providerOptions.systemOne on a call wins field by field. Unknown keys throw. The adapter sends the bearer sentinel and the harness injects the offering's credential.

| Provider | Provider baseURL | model quirk | | ----------------- | ------------------------------------------ | ----------------------------- | | TypeSafe | https://api.typesafe.ai/v1 | jev-latest | | Vercel AI Gateway | https://ai-gateway.vercel.sh/typesafe/v1 | typesafe-ai/jev | | OpenRouter | https://openrouter.ai/api/v1 | typesafe/jev-1.13 | | OpenCode Zen | https://opencode.ai/zen/v1 | jev-1.13 or jev-1.13-free |

Upgrading to 0.3.1

  • createSystemOneAdapterFactory without an endpoint quirk now posts to the catalog provider's baseURL + /systemone instead of the official TypeSafe URL. Set the provider baseURL to the API root (for example https://api.typesafe.ai/v1), or keep the old behavior with {"endpoint":{"kind":"official"}}. The harness sends the offering's credential to whatever URL the adapter returns, so only set an explicit endpoint on a host that credential belongs to.
  • A model quirk now overrides the model the harness passes (the catalog canonical name).
  • createSystemOneAdapter and evaluate are unchanged.

Upgrading from 0.1

  • HttpError, NetworkError and TimeoutError are removed. Transport failures return a FallbackResult.
  • A 2xx body that is not JSON is parse-error (was network). A timeout during the body read is timeout.
  • recordTelemetryEvent and drainTelemetryEvents are removed. Pass evaluate(input, { onTelemetry }).
  • Wire helpers, quirks presets, JsonRecord, Confidence and the env-var name constants are no longer exported.
  • A custom endpoint without a model sends typesafe-ai/jev.
  • Peers are @intx/inference and @intx/types ^0.4.0.
  • Environment variables are unchanged, including SYSTEM_ONE_API_KEY.

License

LGPL-2.1-only