# Connect Strata to your agent

Start at https://stratatcg.com/connector and choose **Copy setup for my agent**. Paste those public instructions into your agent. They contain no credentials. Your agent must support a remote MCP connection with OAuth, HTTP API calls with secure credential storage, or a registered Strata OAuth integration. A chat-only assistant cannot install an integration simply by reading a prompt; use the [console](https://stratatcg.com/connector/console) in that case.

For an MCP-capable host, use the [remote MCP installation guide](./mcp.md) first. It supports automatic OAuth client registration and host-managed credentials when enabled. The native Muse application retains its existing submitted flow; it is not replaced by the portable connection.

## 1. Create or reuse your account

Use [Strata sign-in](https://stratatcg.com/connector/dashboard). Existing app customers should use the same sign-in method they already use. New customers can create an account and verify their email if prompted. No payment card is required to create an account or use the free allowance. Do not create a second account to obtain another allowance. Different sign-in identities are not automatically merged by matching email; contact support if you connected the wrong identity.

## 2. Connect securely

**Remote MCP host:** add `https://stratatcg.com/connector/mcp` through the host’s supported MCP controls, sign in on Strata, review permissions, and let the host store tokens. Discover the tools and read `strata_account` before the first lookup. See the [host-specific instructions](./mcp.md).

**Registered OAuth integration:** start from the agent’s Strata connection control. Sign in on Strata, check the displayed account and agent, choose the requested permissions and approve. The agent handles credentials. Read-only access is available. Connecting does not subscribe you or authorize purchases. See [OAuth](./oauth.md). OAuth requires an actual registered client and exact callback. The MCP endpoint can perform standards-based automatic registration through a compatible host; the existing JSON gateway continues using its separately registered clients. Muse’s native listing remains subject to platform approval.

**Other API-capable agents or scripts:** in the dashboard, create a personal key named for your agent. Copy the key directly into the agent’s private secret/credential setting as `STRATA_API_KEY`. Do not paste it into chat, source control or a shared document. The key appears only once. If lost, revoke it and create a replacement. Keys expire after 90 days; replace them before expiry. Each agent should have its own key so it can be revoked separately.

Use base URL `https://stratatcg.com/connector`, header `Authorization: Bearer <key>`, and `Content-Type: application/json`. API keys are lookup credentials; account billing stays in the authenticated browser. MCP OAuth tokens stay on the MCP endpoint. Separately registered gateway tokens use the scoped agent gateway documented in the OAuth guide. Neither token belongs on personal-key routes.

If an agent cannot securely store credentials, stop credential setup and open the authenticated console instead. Never improvise a public callback URL, store browser session cookies, or ask for payment-card details.

## 3. Verify one lookup

Read the deployed [OpenAPI schema](https://stratatcg.com/connector/openapi.json). For a personal key, call `POST /api/v1/identify` with:

```json
{"text":"Charizard ex 199/165 151","hints":{"game":"Pokemon"},"enrich":false}
```

Use one new `Idempotency-Key` for this logical operation; preserve the exact body and key if the network fails. Verify a successful, confident match for Charizard ex 199/165, SV: Scarlet & Violet 151 (TCGplayer 517045). Do not call identification repeatedly just to test connectivity. Under monthly billing this successful identity uses one credit. A schema/authentication error is not a successful setup; follow its response before proceeding.

This setup check is deliberately identity-only. Subsequent ordinary lookups identify and price together unless the user asks otherwise; include product links and returned images following the [agent operating guide](./agent-workflows.md).

Once this works, the agent asks which card, slab, sealed product or collection to look up. It reads photos with its own image tools and sends relevant text. Strata does not accept photo uploads. For slabs use the dedicated slab route; a missing raw mapping never invalidates a graded result. See [recipes](./recipes.md).

## 4. Use and manage billing

The [dashboard](https://stratatcg.com/connector/dashboard#billing) shows your account’s available credits, plan and reset date. `GET /api/billing/status` without credentials shows public prices and checkout availability. With your personal API key, it returns your monthly account balance and reset date. MCP clients use `strata_account`; registered gateway clients use `account` or `billing_status`.

Choose a plan in the dashboard when needed. Review the price and renewal terms, then enter payment details only in Stripe’s hosted checkout. After returning, refresh your account until confirmed credits appear. A successful redirect alone is not proof of payment. If payment is still processing, preserve the original task and check its status; do not create duplicate subscriptions.

Paid upgrades are immediate after verified payment, with the prorated charge and proportional added credits shown before approval. Downgrades take effect at renewal. The current paid period and used credits are preserved. There are no automatic overages, top-ups or credit rollover. Registered OAuth agents can prepare a billing action and send you to its review page; they cannot silently approve it.

Use **Manage billing** for invoices, payment methods and cancellation. Cancellation takes effect at the period end shown by Stripe; paid access remains until then. If a payment fails, update the method and verify the invoice/payment status before expecting a new allowance. Failed payment does not grant credits.

On an allowance limit, use the actual reset or eligible plan options. On a short-term rate limit, honor `Retry-After`. A provider outage or global capacity limit is not fixed by buying a larger plan. Preserve completed work and retry only unfinished items. Shared account usage includes every key and connected agent.

## 5. Disconnect, recover or get help

Revoke a key or OAuth connection in the dashboard to stop that agent’s access. **Revocation and signing out do not cancel a subscription.** Cancel billing separately if you want renewal to stop. Do not delete an account as a way to cancel charges.

For missing credits, refunds, duplicate accounts, access or deletion requests, use [support](https://stratatcg.com/support). Include the request ID, action reference or invoice reference when available, never passwords, API keys, OAuth tokens or card details. Support verifies account ownership before changes. Refund eligibility and retained financial records require review; no automatic refund or immediate universal erasure is promised.

If you lose account access, use **Forgot password?** or the original social sign-in. Do not create replacement subscriptions while ownership is unresolved. The agent should retain the task context and resume only after account recovery or confirmed billing status.