MCP quotas and credits

Understand how StoreInspect MCP uses request quotas, search-row quotas, and shared contact credits.

StoreInspect MCP uses the same account access model as the StoreInspect API. Tool calls are tied to the StoreInspect account you approve during OAuth.

Check current usage

Ask your client:

Use StoreInspect to show my current usage.

The client should call get_usage and return plan, API access, request quota, search-row usage, and shared contact credits. Trial users also see the current 250-credit trial cap and the paid-plan credit total.

Request and search-row quotas

Store and contact search tools use quota because they return rows from the StoreInspect index.

Tool	Quota behavior
get_billing_status	Exempt from normal API request quota; limited to 60 checks per hour.
create_subscription_link	Exempt from normal API request quota; limited to five billing links per hour.
create_billing_portal_link	Exempt from normal API request quota; limited to five billing links per hour.
get_usage	Reads quota and credit state.
list_taxonomy	Reads supported filters.
get_shopify_store	Looks up one store by domain.
search_shopify_stores	Uses request quota and search-row quota.
enrich_shopify_domains	Uses request quota and search-row quota.
search_shopify_contacts	Uses request quota and search-row quota.
reveal_contacts	Can spend shared contact credits.

Before a search or enrichment tool runs, StoreInspect checks that the requested limit fits within your monthly search-row quota. After the tool completes, usage reporting reflects the rows actually returned.

Claude Free preview

Active Free accounts can use StoreInspect data tools through https://mcp.storeinspect.com/claude.

• Store and contact searches return at most 50 records per call.
• Store and contact reads do not consume the unique-store export allowance.
• Contact reveals still require explicit confirmation and spend the account’s normal Free contact credits.
• Request and search-row quotas still apply.

Contact credits

Contact credits are shared across the StoreInspect web app, REST API, and MCP.

• Trial users receive 250 contact credits during the trial. Paid Pro includes 1,000 monthly contact credits.
• Contact search previews do not expose raw emails, phone numbers, or LinkedIn URLs.
• Revealing a contact for the first time spends one shared contact credit.
• Re-revealing a contact already revealed to your account does not spend another credit.
• StoreInspect refuses MCP reveals unless the tool input includes explicit credit-spend confirmation.
• When trial credits are exhausted, reveal_contacts returns a billing action that points to the billing page for unlocking paid Pro credits immediately.

Reveal confirmation

The reveal_contacts tool requires:

{
  "contact_ids": ["ct_AbCdEf_GhIjKlMnOpQrStUv"],
  "confirm_spend_credits": true
}

If confirm_spend_credits is missing or false, StoreInspect refuses the reveal.

The contact_ids values must be the ct_... IDs returned by contact preview results. Names, roles, and store domains cannot be used as reveal IDs.

Cost-control prompts

Use preview-first prompts:

Search for ecommerce decision-maker contacts at these stores. Do not reveal contact channels yet.

Then ask for a shortlist:

Rank the best 10 contacts to reveal and show the contact IDs. Do not spend credits.

Reveal only after review:

Reveal these three ct_... contact IDs and confirm spending contact credits.

Focus searches

Search endpoints are intended for focused ICP workflows. Use filters such as country, category, traffic tier, app usage, missing app, pixel, theme, Shopify Plus, Meta ads, contact role, or revealable-contact availability.

Do not use MCP tools to crawl, resell, or reconstruct the StoreInspect dataset.