Enrichment · https://api.leadocean.io
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, fill in a person's profile from a LinkedIn URL or other identifier you already hold — job title, employer, seniority, location. Show me the price first.
LeadOceantreg call leadocean.people.enrich --method POST --data '{"linkedin_url":"https://www.linkedin.com/in/routing-fixture"}'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 AI Ark, Akta by Wokelo, AnyAPI and 3,605 other tools.
leadocean.companies.peopleleadocean.people.email.find.personalleadocean.people.email.find.workleadocean.people.enrichleadocean.people.phone.findleadocean.people.reverseleadocean.people.searchleadocean.people.search.countleadocean.companies.countleadocean.companies.enrichleadocean.companies.searchReliability badges come from live traffic through treg.to. Live-verified means a successful provider check; it does not verify every request variant.
Every provider that does this job, side by side: price per billing unit, measured success rate and speed.
Every provider that does this job, side by side: price per billing unit, measured success rate and speed.
Every provider that does this job, side by side: price per billing unit, measured success rate and speed.
Every provider that does this job, side by side: price per billing unit, measured success rate and speed.
Every provider that does this job, side by side: price per billing unit, measured success rate and speed.
Every provider that does this job, side by side: price per billing unit, measured success rate and speed.
These providers answer some of the same capabilities as LeadOcean. The platform pages show them on one row with rate and coverage; choosing is yours, treg.to does not route between providers automatically.
Yes. This is an own-account connection: you sign in to LeadOcean 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 LeadOcean 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 LeadOcean'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 LeadOcean channels are linked above.