SLAB
In this section

DOCS

Slab is a developer- and AI-friendly card-data platform. The API is the product.

Slab is an HTTP API for trading-card data. This portal is not the product. It exists to do two things: mint the API keys that get you in, and host these docs. There is no collection UI here. Everything on tap is reached through the API — by the tools already built on it, or by the one you write next. Everything you can see, you can pull, script, and remix.

There is already an ecosystem around those endpoints: the hosted collection app (the flagship web client — search, portfolio, pricing, chase sets, no code required), the slab CLI, and the open-source tools collected in slab-community on GitHub. None of them have access you don't — they are all just clients of the same API, and what you build can join them. The collection app is the proof: everything it renders comes from the endpoints documented here, so a version of it is something you could build yourself.

Start here: three steps

1 · Get a key (right here in the portal)

Head to Account and mint one. The raw key shows once, so copy it. That key is your entire identity to the API — no other portal setup needed.

📋No code, no key: the hosted collection app renders your collection in the browser, and your portal sign-in already works there. We originally imagined everyone building their own collection UI — the app exists so nobody has to, but it holds no special access, and building your own remains the point of everything below.

2 · Drive it with the pre-built CLI

Don't write code yet. The slabCLI is a ready-made client for the whole API — search the catalog, add the copies you own, and value your collection, all from the terminal. It's the fastest way to learn what the platform can do.

💡The First Run guide walks you from install to your first command. The CLI reference goes deeper — and the CLI documents itself (slab lists every command).

3 · Build your own thing

Once the CLI feels familiar and you know what data is on tap, point your own project at the same endpoints — a portfolio dashboard, a break tracker, a Discord bot, an AI agent that appraises your rips, or your own take on the collection app itself. The CLI and the collection app are built on nothing you can't use: import slab-schemas for typed Python request/response models, or hit the raw HTTP API from any language. To see what that looks like in practice, read one — slab-community holds working apps against these same endpoints. Fork one, or add yours.