hitspec.dev valid

hitspec

hitspec is a file-based HTTP API testing tool. Write API tests as plain-text .http files, run them with 26 assertion operators, capture and chain requests, stress-test, mock, and verify database state — no SDK, no GUI, no JavaScript.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-27T09:54:13.729Z. Cached copy · Source on hitspec.dev

# hitspec

> hitspec is a file-based HTTP API testing tool. Write API tests as plain-text .http files, run them with 26 assertion operators, capture and chain requests, stress-test, mock, and verify database state — no SDK, no GUI, no JavaScript.

- [hitspec — Plain text API tests. No magic.](https://hitspec.dev/introduction.md): hitspec is a file-based HTTP API testing tool — write .http tests that look like real HTTP requests, assert, capture, chain, and load-test. No SDK, no GUI.
- [Install hitspec — Homebrew, Go, and binary](https://hitspec.dev/installation.md): Install hitspec on macOS, Linux, or Windows via Homebrew, go install, a pre-built binary, or build from source. Get the hitspec CLI running in minutes.
- [Write and run your first API test in under a minute](https://hitspec.dev/quickstart.md): Write a plain-text .http file with requests, assertions, and captures, then run it with hitspec. A fast first API test you can read, diff, and commit.
- [hitspec studio — a keyboard-first terminal API client](https://hitspec.dev/studio.md): hitspec studio is a keyboard-first terminal UI for .http files — edit, run, and inspect requests with a tabbed viewer, plus stress, mock, record, and history.
- [hitspec Studio desktop — a native GUI for .http files](https://hitspec.dev/desktop.md): hitspec Studio is the Electron desktop client for hitspec: file tree, source editor, tabbed response viewer, history, stress, mock, record and imports over your existing .http files.
- [Editor Setup](https://hitspec.dev/editor-setup.md): Configure syntax highlighting, snippets, and shell completions for hitspec.
- [The .http file format for API tests](https://hitspec.dev/concepts/file-format.md): Anatomy of a hitspec .http file: requests, headers, bodies, variables, assertions, captures, dependencies, and directives — plain text you can diff and commit.
- [Variables](https://hitspec.dev/concepts/variables.md): Define variables, use built-in functions, reference environment values, and interpolate captured data.
- [Variable Interpolation](https://hitspec.dev/concepts/variable-interpolation.md): Deep-dive into hitspec's {{var}} syntax, $env() references, capture chains, and resolution order.
- [Assertions](https://hitspec.dev/concepts/assertions.md): Validate HTTP responses with 26 assertion operators covering equality, strings, types, arrays, schemas, and snapshots.
- [Captures](https://hitspec.dev/concepts/captures.md): Extract values from HTTP responses and use them in subsequent requests.
- [Dependencies](https://hitspec.dev/concepts/dependencies.md): Control execution order with @depends, topological sorting, and request chaining.
- [Environments](https://hitspec.dev/concepts/environments.md): Configure variables for dev, staging, and production with hitspec.yaml, .env files, and system variables.
- [Authentication for API tests (@auth)](https://hitspec.dev/features/authentication.md): Configure authentication for API requests with the @auth directive. hitspec
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=hitspec.dev · GET /v1/domain/hitspec.dev · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for hitspec.dev:
1. POST https://agentwebmap.com/v1/sites/hitspec.dev/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://hitspec.dev/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/hitspec.dev/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/hitspec.dev).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.