What problem does it solve? A successful API response only proves credentials work for some account, not the correct one. This Skill prevents false verification when multiple accounts, environments, or tenants exist (old vs. new, staging vs. production), stopping integrations from silently targeting the wrong destination. ## Core Features & Use Cases - Independent Identity Confirmation: Asks the user for an identifying fact (account email, product count in a category) and queries the API for the same field to compare. - Mismatch Handling: Treats credentials as wrong until proven otherwise when the compared values do not match, rather than proceeding as if verified. - Fallback Verification: When no distinguishing field is available via the API, directs the user to confirm identity from their own logged-in dashboard instead of re-running calls against possibly-wrong credentials. - Use Case: Before declaring a new OpenCart or payment API integration verified, confirm the store name or product count returned by the API matches the account the user actually intends to connect. ## Quick Start Before marking these API credentials as verified, confirm the account identity by comparing an identifying field from the API with what the user reports.
