Turn search infrastructure into a production-ready workspace

MySearch unifies Tavily, Exa, Firecrawl, and Social / X into a search gateway that Codex, Claude Code, and team agents can call directly. Users do not need to maintain separate providers, compatible gateways, or result schemas, and they do not have to decide manually each time whether to use web search, content extraction, or social intelligence.

Unified Gateway Web discovery, content extraction, and social intelligence all use the same wiring.

Exa Workspace Exa is split into its own section for issuing tokens, managing keys, and making direct proxy calls.

Unified Operations Key pools, tokens, quota sync, and team sharing live in one console.

Unified Compatibility Connect official APIs and custom compatible aggregators without locking into one backend.

Router Tavily for Discovery

Best for news, quick answers, and web lead collection in MySearch's first routing layer.

Search Exa for Web Discovery

Adds a web search option alongside Tavily, with its own key pool, token pool, and proxy endpoint.

Depth Firecrawl for Extraction

Documentation sites, GitHub, PDFs, pricing pages, and changelogs are more reliable through Firecrawl.

Social Social / X for Intelligence

Works with grok2api and xAI-compatible search, normalizing X results into a structure MySearch can consume directly.

This capability is wired through grok2api's compatible API and backend token state. MySearch's Social / X route credits the grok2api project here and keeps it as the default compatible implementation source.

github.com/chenyme/grok2api

Current Use

X Search Compatible

Credits

grok2api

Workspace Switcher

Switch search engine workspaces from one screen

Choose a workspace to expand its keys, tokens, quotas, and integration settings below.

Your last opened workspace is remembered

Search Infrastructure Console

Switch search engine workspaces from one screen