Explore the request format, source outcomes and credit budgets behind TrueFetch. Use the Markdown reference with your coding assistant, or inspect the JSON catalog to understand the product roadmap.
- Read the Job Search reference as Markdown
- Open the machine-readable API catalog
- Find the documentation index in llms.txt
- Download a sample response
MCP connections are in development. Installation instructions and a verified server address will appear here when the service opens. Check release status.
Jev data workflows
Use TypeSafe Jev to classify job listings and route uncertain results for review. Download the Python workflow or a TypeScript API example, with source links and explicit routing rules.
Explore the Jev workflow · Read the implementation guide
One task contract
REST and MCP are designed to expose the same operations, source restrictions, outcomes and billing rules. A model choosing a tool does not grant unlimited spending permission. Requests must stay within authorized scope and budget, and incomplete source coverage must remain visible in the result.
Long-running operations return a task handle. The client should follow that handle instead of repeatedly creating work. Retrieved web content is untrusted data, not instructions that can authorize other tools or change an account’s permissions.
Custom connections and directories
Custom server connections and a host’s official directory are separate routes. Instructions will identify the exact host, supported version, authentication flow and tested tasks before a connection is labeled verified. Directory submission and approval will be reported separately.
No MCP client currently has a verified TrueFetch connection or installation guide. We will publish only steps supported by an operating integration, including authorization scopes, limits, revocation and known restrictions.
Billing and control
MCP is planned to use the same credit balance, operation rates and spending ceiling as REST. The design reserves the authorized upper bound before execution, settles eligible delivery and releases the unused amount. This is a future execution contract, not a working connection. Account sign-in and API key management are available separately; creating a key does not enable MCP. See the account quickstart and billing design.
Read the MCP technical plan and integration verification requirements, or tell us which client and task you need.