A shared API request library for your team
Every team has the same ritual: someone needs to hit the staging API, can't remember the auth header, and excavates Slack for the curl someone pasted in March. A shared request library ends it. In The-Snip, each saved API call stores method, URL, headers and body as a first-class item — searchable next to the snippets and runbooks that use it, one click from a ready-made curl. Docs link to requests with [[wikilinks]], review keeps stale endpoints from masquerading as current, and your agents can fetch the same requests over REST and MCP instead of hallucinating endpoint shapes. It's Postman-collection convenience without another silo, inside the base your team already searches.
How it works
- Save each API call with its method, URL, headers and body — one item per endpoint-and-purpose, titled the way people search ("staging: refresh auth token").
- Copy any request as a ready-made curl straight from the card when you need to replay it.
- Organize with collections per service and tags per environment, then find anything with weighted workspace search.
- Link requests from runbooks with [[wikilinks]] — the incident doc points at the exact calls it tells you to run.
- Let agents use the library too: over REST or MCP they read canonical requests — reads are free on every plan — and propose new ones (agent writes need Pro & Team), with review gating every write.
Questions, answered.
Can I replay a saved request?
Copy any saved API call as a complete curl command — method, URL, headers, body — and run it in your terminal. No proprietary runner, nothing to install.
Should we store live tokens in saved requests?
No — save placeholder values (Bearer <token>) and inject real secrets at run time from your environment. The library is for the shape of requests; your secret manager stays the home for secrets.
How is this better than a Postman collection?
It lives with the rest of the knowledge: the snippet that parses the response and the runbook that explains when to call it are one [[wikilink]] away, all under the same search and review gate — and agents reach it over MCP, which a collection export can't do.
What keeps stale requests out?
Review. Endpoint changed? Update the item and the correction goes through the same approval flow, so the base's answer is the current one. A last-reviewed trail beats tribal memory of which curl still works.
What does it cost?
Free for 25 items — enough for a real trial library, and agent reads over REST and MCP are free on every plan. The Pro & Team plan ($8/user/month, $80/user/year) adds unlimited items, export, agent writes (create and update), workspaces and review.
Can we keep a request's expected response too?
Yes — pair the saved call with a snippet holding the sample response, or note it in a linked doc. When an endpoint misbehaves, comparing against the recorded good response is the fastest sanity check on call.
Start your base — free.
Free: 25 items, no card. Pro & Team: $8/user/mo — unlimited items, REST API, review workflow, and the hosted MCP server.