# Strata API

Composable trading-card identity and pricing for agents: raw cards, sealed products and graded slabs. Start with the [complete setup journey](https://stratatcg.com/connector/docs/get-started.md); reuse the user’s existing Strata account when available. Read `/api/billing/status` for current limits, payment availability and transition date.

For MCP-capable agents, first read the [portable installation guide](https://stratatcg.com/connector/docs/mcp.md). Use the remote endpoint `https://stratatcg.com/connector/mcp` with OAuth and host-managed token storage when enabled. Verify the actual host supports installation; a prompt alone cannot publish a native plugin. Muse native, dots, and Grok Bot availability depend on their platform installation controls.

For registered OAuth clients, prefer the [account connection flow](https://stratatcg.com/connector/docs/oauth.md). It creates or reuses the user's Strata identity and grants selected scopes without manual API keys. Read-only permissions are available. Sandbox uses a separate registration and approved tester access. Native Muse installation remains subject to platform review.

For clients without a working MCP or registered OAuth integration:
1. Help the user sign in to their existing account or create one at https://stratatcg.com/connector/dashboard?from=agent.
2. Ask them to create a lookup-only API key and store it in the agent's secure credential setting. Never request a password, browser session, card details or API key in chat.
3. Send `Authorization: Bearer <key>` and `Content-Type: application/json` to the base URL `https://stratatcg.com/connector`.
4. Read the [agent skill](https://stratatcg.com/connector/docs/skills/tcg-identify/SKILL.md) and [OpenAPI schema](https://stratatcg.com/connector/openapi.json) for the exact input and response shape.

The official Strata registry/API is the source of truth for shared identities
and cross-market mappings. Do not use personal CSV exports, spreadsheets,
Discord threads, or copied registry snapshots as a lookup source or update
target. Send corrections through `/api/v1/feedback`; pending feedback does not
become an active mapping until reviewed. Only a verified API-returned link
supports cross-market pricing.

## Useful answers by default

For ordinary lookups, identify and price together unless the user asks for identity only/no pricing: explicitly set `enrich:true` on identify or slab identification. Known confirmed products go directly to pricing; reuse an existing quote instead of charging twice. Resolve identity/printing ambiguity before quoting and respect current credit limits. The setup identity-only check is an explicit exception.

Present exact identity, selected price with currency/condition/basis and source/time, a clickable TCGplayer product link whenever that product is established, and returned product images when supported. Use `match.url` / `market.url` / enrich `url`, and `match.imageLarge` or `match.image`. A slab's TCGplayer link needs a verified raw mapping and a raw-reference label. Show images for small groups (normally up to four distinct products); use a compact linked table for larger batches. Never invent URLs, images or missing prices. Full presentation rules are in the [agent operating guide](https://stratatcg.com/connector/docs/agent-workflows.md).

## Choose the API flow

- **Raw or sealed description / agent-read photo:** `POST /api/v1/identify`. The agent reads the image; Strata receives text only. Check each result's `ok`, `confident`, candidates, and `kind` before pricing.
- **Candidate list without identity resolution:** `GET /api/v1/suggest?q=...&kind=all`. Suggestions are not identity decisions and are not billable. See [suggest and confirm](https://stratatcg.com/connector/docs/suggest.md).
- **Known TCGplayer product:** `POST /api/v1/enrich` with its printing, language, condition or sealed selectors. Identification is unnecessary when the caller already knows the product.
- **Graded slab:** `POST /api/v1/slabs/identify` with one cert, barcode or readable label text. ALT identity and graded price are independent of TCGplayer coverage. TAG cert-only identification is unsupported.
- **Another graded market/grade:** `POST /api/v1/graded/prices` using an ALT `identityRef` or `strataProductId` and explicit grader, grade and tier.
- **Cross-market comparison:** use a verified registry link and its exact printing/language selectors. Then call raw and graded pricing concurrently. A proposed/unmapped link never supplies a price.
- **Product capabilities or registry progress:** `GET /api/v1/products/{strataProductId}`. It distinguishes supported, unmapped, unsupported and unavailable capabilities. Do not poll continuously.
- **Correction or mapping concern:** retain the identify result's `resultRef` and optionally call `POST /api/v1/feedback` once with an idempotency key. Acknowledgement means pending review, not that a shared mapping changed.

Never treat a raw quote as a graded slab price or infer raw condition from slab grade. A raw Near Mint comparison is only a reference market. A CardLadder URL is an outbound link; Strata does not scrape CardLadder.

## Usage and reliability

Each successful confident identity costs one monthly credit. Each usable selected-market price costs one. Slab identity and each graded market selection follow the same per-operation rule. `identify` with `enrich:true` reserves at most two per item, then returns unused reservations. Beta quota policy is attempt-based until the monthly transition: each account has 1,000 lookups per rolling 24 hours. On beta `account_quota_exceeded`, stop until `retryAt` or `Retry-After`; the beta billing-status response does not include live remaining account usage. `daily_limit` is the separate service-wide safety ceiling; `rate_limited` is a short-term limit. Product reads, feedback, and internal registry discovery do not use customer lookup credits.

Use one stable `Idempotency-Key` for a logical request and identical network retries. Respect `Retry-After` on 429; do not split batches or create accounts to evade limits. On ambiguous identity, ask for the distinguishing printed detail before quoting. A source outage is not evidence of no match. Return the request ID for support.

Read `/api/billing/status` (or OAuth gateway `billing_status`) before discussing an upgrade. Current advertised monthly plans are Free 1,000 credits, Pro 10,000 for $10, and Scale 50,000 for $50; activation and checkout availability come from the endpoint. No automatic overages/top-ups. Upgrades take effect after payment with a reviewed prorated charge and proportional added credits; downgrades take effect at renewal. OAuth agents may prepare an immutable billing action for the owner's separate approval, then check its authoritative status and resume the original task. Never collect payment credentials or claim that a redirect proves payment. See [OAuth and billing actions](https://stratatcg.com/connector/docs/oauth.md) and [sandbox testing](https://stratatcg.com/connector/docs/agent-sandbox.md).

## Complete documentation

- [Documentation home](https://stratatcg.com/connector/docs/reference.html)
- [Complete agent bundle](https://stratatcg.com/connector/llms-full.txt): all customer guides, generated together; OpenAPI remains the schema authority.
- [Agent operating guide](https://stratatcg.com/connector/docs/agent-workflows.md)
- [Products and mappings](https://stratatcg.com/connector/docs/products.md)
- [Billing lifecycle](https://stratatcg.com/connector/docs/billing.md)
- [Console](https://stratatcg.com/connector/docs/console.md)
- [Suggest and confirm](https://stratatcg.com/connector/docs/suggest.md)
- [OAuth lifecycle](https://stratatcg.com/connector/docs/oauth.md)
- [Sandbox walkthrough](https://stratatcg.com/connector/docs/agent-sandbox.md)

The OAuth gateway currently dispatches identify, enrich, slabs, graded and product lookups only. Suggestions, confirmations and feedback require personal-key routes; do not send OAuth tokens there. Never assume all operations in the public schema are gateway operation names.

## Guides

- [Introduction](https://stratatcg.com/connector/docs/introduction.md)
- [Quickstart](https://stratatcg.com/connector/docs/quickstart.md)
- [Identification](https://stratatcg.com/connector/docs/identify.md)
- [Registry feedback and review](https://stratatcg.com/connector/docs/registry-feedback.md)
- [Raw and sealed pricing](https://stratatcg.com/connector/docs/enrich.md)
- [Coverage](https://stratatcg.com/connector/docs/coverage.md)
- [Slab and cross-market recipes](https://stratatcg.com/connector/docs/recipes.md)
- [Slab identification](https://stratatcg.com/connector/docs/slabs.md)
- [Graded prices](https://stratatcg.com/connector/docs/graded-prices.md)
- [Errors and retries](https://stratatcg.com/connector/docs/errors-retries.md)
- [Errors and pitfalls](https://stratatcg.com/connector/docs/pitfalls.md)
- [Monthly plans](https://stratatcg.com/connector/docs/monthly-plans.md)
- [Migration](https://stratatcg.com/connector/docs/migration.md)
- [OpenAPI](https://stratatcg.com/connector/openapi.json)
- [Privacy](https://stratatcg.com/connector/privacy) · [Terms](https://stratatcg.com/connector/terms) · [Support](https://stratatcg.com/support)

The native Muse connector submission is separate from these public HTTP APIs. Do not claim that a submission is approved or that a native Muse connector is available. The remote MCP endpoint is available independently of directory approval; consult the MCP guide for tested hosts and current application status.