Enrichment · https://api.corpoapi.com
set up treg — https://treg.to/llms.txt
claude mcp add --transport http treg https://treg.to/mcp
Settings → Connectors → add https://treg.to/mcp as a custom connector.
Add https://treg.to/mcp as a remote MCP connector in its tool settings.
Settings → Connectors → Add custom connector → https://treg.to/mcp.
Point it at https://treg.to/mcp (HTTP transport).
curl -fsSL https://treg.to/install.sh | sh
LangChain, CrewAI or any code: /call/<tool-id> + X-Treg-Token: <token>. No SDK.
Using treg, find a company in an official business register by name or registration number. Show me the price first.
treg call corpoapi.companies.owners --query jurisdiction=gb --query company_number=00519500
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 every provider in the catalog and 3,606 other tools.
corpoapi.companies.filingscorpoapi.companies.financialscorpoapi.companies.officerscorpoapi.companies.ownerscorpoapi.companies.ownership.graphcorpoapi.companies.registry.coveragecorpoapi.companies.registry.profilecorpoapi.companies.registry.searchcorpoapi.companies.vat.verifycorpoapi.companies.verifyReliability 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 Corpo API 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.to/mcp. One MCP server carries Corpo API 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 Corpo API'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 Corpo API channels are linked above.