Betsy Enterprise Co-Pilot
Bring live 2A demand into any MCP-compatible AI assistant.
Brand teams already live in AI assistants. Enterprise Co-Pilot connects Demand Intelligence to those tools via the Model Context Protocol — authenticated demand summaries your brand team already trusts.
- Read-only tools
- ek_live_ API key
- Open protocol
What it is
- Remote MCP for Demand Intelligence keys
- Same anonymized data as the REST API
- Platform warehouse inventory when feed is synced
- Plan lookback and rate limits enforced
- Works with Claude, Cursor, and MCP clients
What it is not
- Not free public market data
- Not shopper chat or dealer-agent install
- Not key minting or signup inside MCP
- Not full session dumps (use REST / portal)
Tools
Small, read-only surfaces designed for assistant context — not a raw warehouse dump.
get_startedMeet Betsy — welcome card, plan, and example asks (first turn).
get_meConfirm account, plan, lookback limits, brand pins, and portal path.
get_healthAuthenticated liveness — service ok and scope ready for reads.
get_today_at_a_glanceCompact demand summary: tops, unmet, rising, map pulse (prior day or live).
get_unmet_demandZero-hit demand signals within your plan lookback.
get_rising_calibersRising caliber heat from durable rollups.
get_nics_check_volumePublic FBI NICS check counts by month/state (macro only — not sales, not live NICS).
search_inventoryPlatform + warehouse feed: search on-hand stock (how much X do we have?).
lookup_upcPlatform + warehouse feed: look up a UPC in internal warehouse stock.
get_session_contributorsPlatform: who drove sessions/signals (funny aliases only — never legal store names).
How to connect
Fastest path: mint and test inside the Demand Intelligence portal, then paste a host-ready install. Details below if you are configuring by hand.
- 1Demand Intelligence accessHold an active Demand Intelligence plan. Co-Pilot is positioned for Platform; ask Coriolis if you need access.
- 2Mint a Co-Pilot key in the portalSign in to your portal → Keys · Co-Pilot → Create Co-Pilot key. The full secret is shown once. Use Test connection on that screen before you leave.
- 3Install in your AI assistantPick Grok web, Claude Desktop, Cursor, VS Code, or another host and copy the connect string (or hand-off pack).
- 4Test, then askUse Test connection in the portal, then send: "Hi Betsy" and "What's hot today?"
Things people actually ask
- “What's hot today?”
- “What calibers are heating up?”
- “How much 300 BLK do we have?”
Install by assistant
https://www.gunsearchengine.com/api/mcp/enterprise/mcp
Placeholder configs use ek_live_YOUR_KEY. In the portal, the same tabs fill in your real secret after you mint a key.
Best for sales managers — browser chat, no IDE
- Open Grok in the browser and open MCP / connectors settings.
- Paste the URL and Authorization values from the block below (or the whole pack).
- Save / enable betsy-enterprise.
- Start a chat and send: "Hi Betsy"
Grok web · connect string
Betsy Enterprise Co-Pilot URL: https://www.gunsearchengine.com/api/mcp/enterprise/mcp Authorization: Bearer ek_live_YOUR_KEY After connecting, start a chat and send exactly: Hi Betsy Then try: What's hot today?
The server URL and Authorization: Bearer ek_live_… header are what matter. Stdio-only clients need a remote bridge such as mcp-remote.
Security & data
Same multi-tenant rules as Demand Intelligence and Active Defense: anonymized aggregates, no shopper emails in partner payloads, plan lookback and rate limits on every tool. Keys never leave your MCP client config — rotate them in the portal if exposed.
FAQ
- What is MCP?
- Model Context Protocol is an open standard for connecting AI assistants to external tools. Betsy Enterprise Co-Pilot is a remote MCP server that exposes Demand Intelligence demand tools to any compatible client.
- Do I need Demand Intelligence?
- Yes. The Co-Pilot authenticates with a Demand Intelligence API key (ek_live_…). It is not a free public data feed and not a GunSearchAgent dealer tool.
- Where do I get the key?
- In the Demand Intelligence portal, open Keys · Co-Pilot (client admin), click Create Co-Pilot key, and copy the secret immediately — it is shown once. You can also Test connection from that screen before installing in an assistant.
- Which AI apps can use it?
- Copy the install for Grok, Claude, Cursor, or VS Code. Configs are filled with your key in the portal.
- Is a portal cookie enough?
- No. MCP uses API keys only. Mint a key under Keys · Co-Pilot or ask Coriolis during onboarding. Never put portal session cookies in an MCP client.
- Does it include sessions export or full intel dumps?
- Not in v1. Co-Pilot demand tools stay small and read-only: account, health, glance, unmet, and rising. Full session packages and bulk export remain on the REST Enterprise API and portal.
- Can Co-Pilot search our inventory?
- Yes on Platform when your internal warehouse feed is connected and synced (portal Keys · Co-Pilot checklist: Warehouse feed). Ask things like “how much 300 BLK do we have?” — on-hand warehouse stock, not the public/stream catalog FFLs use for dropship, and not shopper multi-dealer chat.
- How is this different from the REST API?
- Same data, same entitlements and rate limits. REST is for apps and integrations; MCP is for AI assistants that speak the protocol. OpenAPI remains the contract source of truth for HTTP.
Ready for Demand Intelligence
Co-Pilot is included for authenticated Demand Intelligence clients — no separate MCP product to buy. Request a demo, then open Keys · Co-Pilot in the portal, mint a key, and connect your assistant.