Enrichment · https://api.context.dev/v1
set up treg — https://treg.sciatafrica.com/llms.txt
claude mcp add --transport http treg https://treg.sciatafrica.com/mcp
Settings → Connectors → add https://treg.sciatafrica.com/mcp as a custom connector.
Add https://treg.sciatafrica.com/mcp as a remote MCP connector in its tool settings.
Settings → Connectors → Add custom connector → https://treg.sciatafrica.com/mcp.
Point it at https://treg.sciatafrica.com/mcp (HTTP transport).
curl -fsSL https://treg.sciatafrica.com/install.sh | sh
LangChain, CrewAI or any code: /call/<tool-id> + X-Treg-Token: <token>. No SDK.
Using treg, enrich a company from its domain or name. Show me the price first.
treg call branddev.web.map --query domain=docs.context.dev --query maxLinks=10
Connect once; treg.to keeps the credential server-side and injects it per call. No key on any machine.
The provider's own rate, $0.000 markup. How billing works.
Calls through your own connection are not metered by treg.
Register it and those calls are never metered. Your key always wins.
Another provider is a different word in the prompt, not a new integration.
The same token calls Akta by Wokelo, AnyAPI, Apollo.io and 3,599 other tools.
branddev.brand.ai.productsbranddev.brand.ai.querybranddev.brand.fontsbranddev.brand.naicsbranddev.brand.retrievebranddev.brand.retrieve-by-emailbranddev.brand.retrieve-by-isinbranddev.brand.retrieve-by-namebranddev.brand.retrieve-by-tickerbranddev.brand.retrieve-simplifiedbranddev.brand.screenshotbranddev.brand.styleguidebranddev.brand.transaction-identifierbranddev.web.crawlbranddev.web.mapbranddev.web.scrapebranddev.web.searchReliability badges come from live traffic through treg.to. Live-verified means a successful provider check; it does not verify every request variant.
Yes. This is an own-account connection: you sign in to Context.dev once and your agent uses that connection through your treg.to token. Calls on it are never metered.
Run: claude mcp add --transport http treg https://treg.sciatafrica.com/mcp. One MCP server carries Context.dev and the rest of the catalog.
Anything that speaks MCP (Claude Code, Claude Desktop, ChatGPT, Codex, Cursor, Grok) and anything that can make an HTTP request (LangChain, CrewAI, LlamaIndex, plain code).
No. treg.to serves Context.dev's real API through its own metered proxy: the request is the provider's own, the credential is injected server-side, and the answer is relayed verbatim. The official Context.dev channels are linked above.