Jobs data · https://api.ashbyhq.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, a company's open job postings. Show me the price first.
treg call ashby.companies.jobs --query board=ramp --query includeCompensation=true
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.
Ashby job boards 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, Greenhouse Job Board, Hirebase and 3,650 other tools.
ashby.companies.jobsReliability badges come from live traffic through treg.to. Live-verified means a successful provider check; it does not verify every request variant.
No. Ashby job boards 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 Ashby job boards 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 Ashby job boards's real public API: the request is the provider's own, no credential is added, and the answer is relayed verbatim. The official Ashby job boards channels are linked above.