Skip to main content
Track customer-facing REST API and MCP changes here, including endpoints, tools, authentication, scopes, schemas, limits, quotas, billing behavior, and changes that may require integration updates.

​
2026-08-02

Machine-readable discovery for StoreInspect MCP is now available.
  • Added /.well-known/mcp.json with the hosted MCP endpoints, OAuth configuration, tool categories, and client setup details.
  • Added /.well-known/mcp/server-card.json with the public tool schemas and limits. The server card reports MCP contract version 1.0.1.
  • Added /.well-known/agent-skills/index.json so compatible agents can discover the public StoreInspect skill.

​
2026-07-26

Approved StoreInspect integrations can now authenticate to API V1 with OAuth.
  • OAuth access tokens use the same Bearer header, endpoint scopes, paid-plan checks, quotas, and contact-credit ledger as API keys.
  • The API OAuth resource is https://storeinspect.com/api/v1.
  • OAuth client registration is managed by StoreInspect. Independent server-side integrations should continue to use dashboard-created API keys unless their OAuth client has been approved.

​
2026-07-23

ChatGPT now uses a dedicated MCP endpoint with focused tool contracts.
  • Added the data-only ChatGPT endpoint: https://mcp.storeinspect.com/openai.
  • Billing tools remain available through https://mcp.storeinspect.com/mcp but are not exposed through the ChatGPT endpoint.
  • MCP search tools return at most 25 records per call.
  • MCP filter arrays and domain enrichment accept at most 10 values.
  • Domain enrichment returns store and technology data only. Contact previews are available through search_shopify_contacts.
  • reveal_contacts now requires the literal value confirm_spend_credits: true.
  • MCP responses no longer return request IDs or API-key identity. REST API responses are unchanged.

​
2026-07-21

Subscription links created through the REST API or MCP now use paid Checkout.
  • API- and MCP-created Checkout sessions do not include a free trial.
  • Creating a subscription link does not subscribe, upgrade, or charge the account. A human must still open the Stripe-hosted page and confirm the change.

​
2026-07-20

Secure Stripe-hosted billing links are now available through the REST API and MCP.
  • Added billing status, subscription-link, and billing-portal endpoints to API V1.
  • Added get_billing_status, create_subscription_link, and create_billing_portal_link MCP tools.
  • Added billing:read and billing:manage scopes.
  • Free MCP users can connect and use billing tools; Store and contact tools still require an active paid plan.
  • Existing API keys can use billing recovery after paid access lapses, but new API keys and all data endpoints remain paid-only.
  • Billing tools create Stripe-hosted links only. They never directly change or charge a subscription, and a human must confirm in Stripe.

​
2026-07-07

Usage, contact-credit recovery, and revenue-tier coverage have been improved.
  • GET /usage and the MCP get_usage tool now report trial state and the paid-plan contact-credit total.
  • Trial users who exhaust their contact credits receive an end_trial_to_unlock_pro_credits billing action from contact reveal requests when ending the trial would unlock paid credits.
  • Revenue tiers are now derived from available revenue estimates when a stored tier is missing, improving lookup, enrichment, store search, and contact search consistency.

​
2026-07-04

Store and contact search now support more focused filters across the REST API and MCP.
  • Store search supports app and pixel any, all, and none filters.
  • Added theme-type, active Meta Ads, contact-availability, and contact-role filters for stores.
  • Contact search supports role, seniority, verified-email, phone, and LinkedIn availability filters together with store filters.
  • MCP tool schemas expose the supported filter shapes directly to compatible clients.

​
2026-07-03

Hosted MCP support is now available for AI clients.
  • Added a dedicated MCP docs section with setup, client connection guides, example workflows, tool reference, quotas, connection management, troubleshooting, and security guidance.
  • Added the hosted MCP endpoint: https://mcp.storeinspect.com/mcp.
  • Added OAuth setup instructions for ChatGPT, Claude, Claude Code, Codex CLI, Cursor, VS Code, and other remote MCP clients.
  • Added MCP tools for checking usage, listing taxonomy, looking up stores, searching Shopify stores, enriching domains, searching contacts, and revealing contacts.
  • Documented MCP scopes, OAuth authorization, token audience validation, connected-client revocation, and contact reveal confirmation.
  • Added MCP connection management in the StoreInspect dashboard.

​
2026-06-30

StoreInspect API documentation is now available.
  • Added Developer Docs and API Reference for StoreInspect API V1.
  • Added endpoint reference for GET /usage, GET /taxonomy, store lookup/search/enrichment, contact search, and contact reveal.
  • Added guides for authentication, pagination, rate limits, errors, credits and reveals, taxonomy, search guardrails, and data models.
  • Clarified V1 data coverage, request quotas, search-row quotas, and shared contact credits.

​
Policy

V1 uses /api/v1 in the URL for breaking-version boundaries. Within V1, StoreInspect may add fields, enum values, filters, response metadata, and other non-breaking behavior. Breaking REST API changes go into a future /api/v2 unless a security or abuse issue requires immediate action. Documentation corrections, navigation changes, and visual updates are not listed unless they change how customers integrate with the REST API or MCP. MCP changes that require client updates are called out explicitly.