Skip to main content

TypeSafe Unofficial CLI

python PyPI license

Unofficial. This project is not affiliated with, endorsed by, or supported by TypeSafe AI or OpenRouter. "TypeSafe", "Jev" and "OpenRouter" belong to their owners.

Unofficial command-line interface for TypeSafe AI System One models, on TypeSafe or OpenRouter, built on typesafe-sdk.

Install

uv tool install typesafe-unofficial-cli

It needs Python 3.14 or newer. To work on the CLI from a checkout, run make install.

Usage

Log in once per provider profile. The key is read from a hidden prompt:

typesafe auth login
typesafe -p openrouter auth login --provider openrouter

Ask questions about some text. Each question is noul, choice or score:

echo '{"billing": {"type": "noul", "instructions": "Is this billing?"}}' \
  > questions.json
typesafe ask --state "I was charged twice." --questions-file questions.json

Ask the same questions about many states, one JSON value per line, with several requests in flight (see batch ask):

typesafe ask --states-file states.jsonl --questions-file questions.json \
  --concurrency 8

ask and models list accept --timeout, --max-retries and repeatable --header 'Name: value'; ask also takes --extra-body FILE with extra top-level request fields. The request id of each response is printed on stderr and is a request_id field in the records.

Profile settings are managed with config set|get|unset (provider, base_url, model, timeout, max_retries and the global output):

typesafe config set model jev-latest

Other commands: models list (TypeSafe only), auth status|logout|token and config path|list|use.

For automation set TYPESAFE_API_KEY or OPENROUTER_API_KEY; each provider reads only its own variable. Global options go before the command: -p/--profile, -o/--output (table, json, jsonl, csv, id) and -v/--verbose.

Roadmap

  • 0.1.0: scaffold, auth, profiles, ask, models list
  • 0.2.0: request options, config set|get|unset, batch ask, request ids
  • 1.0.0: every SDK capability covered, contracts frozen

Security

Report a vulnerability privately through GitHub's advisory form, not a public issue.

Contributing

See CONTRIBUTING.md.

License

See LICENSE.

Metadata

Release files for typesafe-unofficial-cli 1.0.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for typesafe-unofficial-cli 1.0.1
File Size Uploaded
typesafe_unofficial_cli-1.0.1.tar.gz 119.9 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for typesafe-unofficial-cli 1.0.1
File Interpreter ABI Platform
typesafe_unofficial_cli-1.0.1-py3-none-any.whl Python 3 none any Details

Total release size: 156.3 kB

Release files / typesafe_unofficial_cli-1.0.1.tar.gz

Download URL typesafe_unofficial_cli-1.0.1.tar.gz
Size 119.9 kB
Tags Source
SHA-256 checksum
How to use checksums
d97a6fb84893fa8a82ec45b64999e4593b3646c85ddad9e2c42e9066544c863f
BLAKE2b-256 checksum
How to use checksums
b27a1fb8946679ac59083f3c9bde9b8674d6ca794fac3922a2d3380e4851bc5d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 2, 2026.

Transparency log

Release files / typesafe_unofficial_cli-1.0.1-py3-none-any.whl

Download URL typesafe_unofficial_cli-1.0.1-py3-none-any.whl
Size 36.3 kB
Tags Python 3
SHA-256 checksum
How to use checksums
f0288c7091024f669469b263b1e865751c8e9e90eaed4b60c713afaab5e0afd2
BLAKE2b-256 checksum
How to use checksums
7d5f7849b5c34f6ae68f94e7b4718c9a1e06c6f7f0d930c8397ec671bf25a58f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 2, 2026.

Transparency log

Release history Release notifications | RSS feed

1.1.0

2 release files

This release

1.0.1 This release

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page