Tinspec documentation

A request workbench for backend developers. Point it at your OpenAPI document — or a gRPC server, or a GraphQL endpoint — and the endpoints are just there. Live-bound, not imported once and left to rot.

Start here Download Tinspec

What these docs cover

Everything here describes Tinspec v0.1.0-preview.10, released 2026-09-13 — the build you get today from tinspec.dev/download. Nothing on these pages is a plan or a preview of unreleased work. If a feature is not in that build, it is not documented here.

That build is macOS only. Linux and Windows have no preview.10 file; an existing install on either is never offered the update and keeps working. Install has the detail. The tinspec CLI ships separately, at v0.1.1.

Start here

Install, open your first project, bind a spec, and send a request.

Concepts

The seven words the rest of the docs lean on — request, spec source, environment, chain, auth provider, sender, project.

Guides

One job per page: automate auth, build a chain, call gRPC, route through a gateway, run a suite in CI, let an agent drive.

Reference

The collection file format you commit, the project layout, the MCP tools, and every keyboard shortcut.

Why it is a desktop app

Requests are sent by a Rust engine running inside the app, not by a browser tab. That is the whole reason Tinspec is native: a browser cannot reach localhost, cannot speak native gRPC, and is stopped by CORS. A local process makes all three ordinary.

The desktop app is free and works fully offline with no account, and nothing you send is proxied through a Tinspec server. The source is not public — Local & cloud covers where that stands, and what the separate paid tier (cloud sync, teams, tunnels) adds.