slab-cli
A terminal client for the slab trading-card API — browse the catalog, price cards against real sales comps, and track your own collection from the command line.
pip install slab-cli
This installs the slab command.
Setup
The CLI talks to the hosted slab API. You need an API key — mint one from the slab portal (sign in → API Keys → create). Then:
export SLAB_API_KEY=sk_live_... # your key (required)
# optional:
export SLAB_API_URL=https://api.slab.dev-jeb.com # default; override for a self-hosted API
export SLAB_COLLECTOR=<collector-uuid> # your active collector, reused across commands
Quickstart
# Catalog + pricing (no collector needed)
slab card search --subject "Connor Bedard" # find cards
slab card price <card-uuid> # fair-market value from sales comps
slab card comps <card-uuid> # the underlying recent sales
slab set "OPC Platinum" # a set's sealed FMV + top cards
# Your collection
slab collector create # one-time: create your collector profile
slab collection add # add an owned copy (grade, cost, acquisition)
slab collection cost # log grading/shipping costs on a copy
slab break new # record a box/case break
slab collection dashboard # portfolio value, cost basis, P&L
slab collection search # search + filter your copies
Run slab with no arguments for the full command list, or slab <group> (e.g. slab collection)
to see a group's verbs.
Configuration reference
| Env var | Purpose | Default |
|---|---|---|
SLAB_API_KEY |
API key for authentication (required) | — |
SLAB_API_URL |
Base URL of the slab API | https://api.slab.dev-jeb.com |
SLAB_COLLECTOR |
Active collector UUID, reused per command | — |
SLAB_NO_UPDATE_CHECK |
Set to 1 to silence update checks |
— |
Staying up to date
Nothing updates itself. At most once a day the CLI asks PyPI (in the background, while your command runs) whether there's a newer release, and if so prints one line after the output:
▍ slab-cli 0.7.0 is available — you have 0.6.0
Update when you like: slab update
slab --version # what you have
slab update check # ask PyPI right now; installs nothing
slab update # upgrade, after showing the command and asking
slab update runs the upgrade that matches how you installed slab — pipx upgrade,
uv tool upgrade, or pip install --upgrade — and prints it first, so you can decline and run it
yourself. To turn the whole thing off: export SLAB_NO_UPDATE_CHECK=1.
What it depends on
Requests and responses are typed against slab-schemas —
the same pydantic wire contract the API itself uses — so the CLI and API can never drift.
Requires Python 3.13+.
Release files for slab-cli 0.12.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| slab_cli-0.12.0.tar.gz | 80.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| slab_cli-0.12.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 176.2 kB
Release files / slab_cli-0.12.0.tar.gz
| Download URL | slab_cli-0.12.0.tar.gz |
|---|---|
| Size | 80.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
05c5e6a474ced644d6cf27ef892ca744a053c4ae7e49a10bc2b540b20edb9985
|
|
BLAKE2b-256 checksum How to use checksums |
93e3187da546087d77bebc6ba53ec8eecd6be27f96fdfdf5b702ae47faad428c
|
| 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 Aug 13, 2026.
Transparency logRelease files / slab_cli-0.12.0-py3-none-any.whl
| Download URL | slab_cli-0.12.0-py3-none-any.whl |
|---|---|
| Size | 95.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
49af9505b4e358dd813f678008144078316c0a3ef000ed9f22356b7d58ff4e4f
|
|
BLAKE2b-256 checksum How to use checksums |
10cfb132cd4130e381f31e7b6b15391e8a402fa1921d3cdb0f5082ad17d092f8
|
| 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 Aug 13, 2026.
Transparency log