tryfetchLocal-first API client
Collections and requests are plain files next to your code. Environments, secrets in your OS keychain, JavaScript pre and post scripts, history, and a CLI and MCP server that ask before an agent acts.
Try it free for 7 days, no card required.
Plain files
Add a directory and Tryfetch keeps everything in a .tryfetch folder inside it: one readable TOML file per request, folders for collections, a file per environment. Commit it, branch it, review it. History stays on your machine and out of git.
.tryfetch/collections/Users/Create user.toml
method = "POST"
url = "{{baseUrl}}/users"
[auth]
type = "bearer"
token = "{{token}}"
[body]
type = "json"
content = '''
{ "name": "Ada Lovelace" }
'''Environments and secrets
Switch between local, staging and production per project. Mark a variable secret and only its name is written to the file; the value lives in the macOS Keychain, Windows Credential Manager or Secret Service. Values that are fine to share, like a localhost password, can stay in the file.
.tryfetch/environments/staging.toml
[[vars]]
name = "baseUrl"
value = "https://staging.example.com"
[[vars]]
name = "token"
secret = true # the value is in your keychainAgents, with a leash
Install the skill or add the MCP server and your coding agent can run saved requests with your environments. Set a policy per HTTP method. On "ask", a native popup shows the exact request first. Secret values are masked in everything the agent gets back.
tryfetch · approval needed
Claude Code wants to send a DELETE
https://staging.example.com/users/usr_8f2k1
shop-api · staging · Users/Delete user
Carries your secrets: token
Deny escAllow enter
Mock server
Give a request a mock response, or save a real one as the mock in one click. tryfetch mock answers those routes on localhost, and a db.json gives you json-server style resources next to them.
$ tryfetch mock
Mocking shop-api on http://localhost:4010
POST /login
GET /users/{{id}}
REST /posts
GET /users/42 → 200
POST /posts → 201One license per person, active on one device at a time. Buy several and hand them out from your account.
On your disk. Collections and requests are plain files, so you can keep them in your repo and review changes like any other code. tryfetch.sh only knows your email, your licenses and the device each one is active on.
In your operating system's keychain, not in the collection files.
Tryfetch comes with a CLI, an MCP server and an agent skill. You set a policy per HTTP method: allow, ask or disabled. With "ask", a popup shows the exact request and which of your secrets it carries before anything is sent. Agents never see secret values; they are masked in everything Tryfetch hands back.
Any saved request can carry a mock response. Start the mock server for a project and it answers those methods and paths on localhost, plus json-server style resources from a db.json file. Useful while the real API is still being built.
Yes. Requests run JavaScript before they are sent and after the response comes back: change headers, keep a login token for the next request, and write tests with expect. The editor completes the script API as you type. Scripts are synchronous and cannot make their own network calls.
Yes. €12.90 per license excluding VAT, once. VAT for your country is added at checkout. No subscription, no seat renewal.
Each license is active on one computer at a time. Moving machines? Deactivate the old one in Tryfetch or from your account on tryfetch.sh, then activate the new one.
Yes. Pick a quantity at checkout, then assign each license to a teammate by email from your account. Reassign any time; the old device is signed out.
Polar is our merchant of record: they handle checkout, VAT and invoices. Licenses, seats and devices live in your tryfetch.sh account.