Sandbox walkthrough
Use your actual Strata identity at https://stratatcg.com/connector/console?mode=test. Approved tester accounts share sign-in with production, but test Stripe subscriptions and lookup credits are isolated. A production account is not automatically an approved tester. Live payment availability is independent.
Test OAuth without waiting for a connector client
Open https://stratatcg.com/connector/agent-test and choose Connect sandbox. This browser client uses the same registered OAuth and sandbox gateway an agent uses. Sign in with your usual account, review the scopes, return, then run Read account and credits. Try a query, prepare a subscription or plan change, open its separate review tab, and use Check original action after returning. Retry same request keeps the same payload and operation key. Disconnect this test client revokes only this connection; it does not cancel billing.
Access and refresh tokens stay in page memory. Reloading requires reconnecting; existing connections can be revoked from the account dashboard. A host-only, secure cookie holds the PKCE verification material for at most 30 minutes so email verification can resume in another tab; it is removed when the return is validated. No API key or OAuth token is displayed or copied. This test demonstrates Strata's OAuth behavior, not Muse installation or approval.
Test from Muse
For Muse, first install/connect the registered Strata Sandbox connector if it is available in your account. The submission portal alone does not install it. The operator must supply Muse's exact callback, a sandbox OAuth registration and a dedicated reviewer account; approval/testing access is controlled by Muse. Do not paste your Strata password or API key into a chat.
- Connect, sign in with your usual Strata identity, and verify Sandbox and your account name on consent. Allow account and card access; add billing preparation for this test.
- Ask: “Show my Strata sandbox plan, credits, reset date and payment availability.” It must report sandbox, not production.
- Ask: “Identify Charizard ex 199/165 from Pokémon 151, then price the matched raw Near Mint printing.” Ambiguous identity must be resolved before pricing. Missing data must not display as zero.
- Ask: “Prepare a sandbox Pro subscription and show me the price and terms.” Review the action. In the Stripe Sandbox checkout, use test card
4242 4242 4242 4242, any future expiry, any three-digit CVC and a test postal code. Do not use a real payment card for this test. - Return and ask: “Check the original billing action and show my credits.” A redirect alone must not be described as payment confirmation. Paid Pro should grant the test monthly allowance once.
- Ask: “Quote an immediate upgrade to Scale.” Review the prorated charge, extra credits and original expiry. After confirmation, retry the original action reference: it must not create another charge or grant.
- Ask: “Schedule a downgrade to Pro at renewal.” Scale stays active for this period; status shows the future Pro date.
- Ask: “Cancel renewal.” Review removal of the scheduled change and the access end date. Cancellation must not erase already-paid credits before expiry.
- Ask for invoices or a payment-method update. Stripe opens securely. The agent may report that the portal is ready, but cannot claim you saved a card simply because you returned.
- Revoke this connection under Connected agents in the Strata dashboard. The next gateway request must fail; billing is not canceled by revocation alone.
Also try declining consent, choosing the wrong account, an expired quote, a sandbox token on production, insufficient permissions, duplicate preparation and delayed payment. Expect actionable errors with no duplicated purchase and no production credit change. When reporting a problem, include environment, request/action ID and expected behavior; omit secrets.