# The Studio (web app)

The Studio is the API with a photo drop zone, for people who'd rather not write code. Sign in, open **Identify a card**, **Binder page**, **Grade condition** or **Check for fakes** in the sidebar, drop a photo (or paste one, or click to choose), and press **Run**.

- **Identify a card:** add a second photo tilted under a light to tell holo from reverse holo. See [Identify a card from a photo](/docs/identify).
- **Binder page:** one photo of a spread or a 9-pocket page; every card comes back in its place on a grid. If the cards touch, choose the grid (e.g. 3 × 3). Each card counts as one photo check. Binder results can't be shared.
- **Grade condition:** add a photo of the back for a narrower range. See [Card condition from photos](/docs/condition).
- **Check for fakes:** add the back; many fakes give themselves away there. See [Fake check](/docs/authenticity).

## The same as the API

- **Same query:** each run sends the same GraphQL query the CLI and MCP tools send, as your account, so the results, errors and limits are identical.
- **Same quota:** a run counts as one request and one photo check against your account's daily quota (see [Authentication and limits](/docs/authentication)).

## Your runs

- **History:** runs are listed newest first, grouped by day. A running job updates by itself; a finished one opens to the full result.
- **Private by default:** only you can see your photos and results.
- **Share:** creates a link anyone can open, and the result appears on Explore's **Community** tab. Shared pages are never indexed by search engines. **Stop sharing** turns the link off.
- **Is this wrong?:** under a result, tell us what the card really was (or which pockets are wrong, or the real grade). If you tick **Let RarityDB keep this photo**, here or when you upload, we keep it with your correction to test and improve accuracy. Otherwise it stays only in your history.
- **Delete:** removes the run and its photos.

## Why the API doesn't keep a history

API, CLI and MCP calls are stateless: the photo is analysed and not stored. Run history and sharing only exist in the Studio, so photos you send through the API never sit on our servers.