Jobs data · https://api.lever.co
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, a company's open job postings. Show me the price first.
treg call lever.postings.get --query site=spotify --query posting_id=2a55d6c9-c564-443a-be3e-a3851db5a93b
Its tools are free and need no key: there is nothing to connect.
No charge per call and no markup.
A free treg.to account is all it takes: no card, and no account with the provider.
Lever is a public API: no account, no key.
Another provider is a different word in the prompt, not a new integration.
The same token calls Apollo.io, Ashby job boards, Greenhouse Job Board and 3,647 other tools.
lever.eu.postings.getlever.eu.postings.listlever.postings.getlever.postings.listReliability badges come from live traffic through treg.to. Live-verified means a successful provider check; it does not verify every request variant.
No. Lever is a public API with no key: there is nothing to connect.
Nothing. treg.to does not charge for these calls.
Run: claude mcp add --transport http treg https://treg.to/mcp. One MCP server carries Lever 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 relays Lever's real public API: the request is the provider's own, no credential is added, and the answer is relayed verbatim. The official Lever channels are linked above.