dev.tools valid

DevTools — Open-Source API Testing (HAR → YAML → CI) and Stresseur

DevTools is an open-source (Apache-2.0) API testing tool from the DevTools team. DevTools Studio, a desktop app for macOS, Windows and Linux, turns real browser traffic (HAR files) into multi-step API flows with automatic variable mapping and exports them as Git-reviewable YAML. DevTools CLI, a Go-based runner, executes those flows in any CI pipeline with JUnit/JSON reports and proper exit codes. Core usage is local-first and needs no account. Stresseur, the team's AI test engineer for APIs, is

For agents: Open-source (Apache-2.0) API testing tools: Studio turns HAR browser traffic into YAML API flows, CLI runs them in CI, plus the Stresseur AI test engineer.

api testinghar to yamlci testingopen sourcestress testing

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-24T14:59:07.325Z. Cached copy · Source on dev.tools

# DevTools — Open-Source API Testing (HAR → YAML → CI) and Stresseur

> DevTools is an open-source (Apache-2.0) API testing tool from the DevTools team. DevTools Studio, a desktop app for macOS, Windows and Linux, turns real browser traffic (HAR files) into multi-step API flows with automatic variable mapping and exports them as Git-reviewable YAML. DevTools CLI, a Go-based runner, executes those flows in any CI pipeline with JUnit/JSON reports and proper exit codes. Core usage is local-first and needs no account. Stresseur, the team's AI test engineer for APIs, is built on the DevTools engine.

Last updated: 2026-09-27
Website: https://dev.tools/

Primary audience:
- API developers and QA engineers who need reliable API chaining, variable mapping, and CI-ready flows without cloud friction.

Core promise (use this wording consistently):
- Import a HAR → generate a flow → export YAML → run in CI.

Naming and positioning:
- Umbrella brand: DevTools
- Desktop app: DevTools Studio (open source)
- Command line runner: DevTools CLI (open source)
- AI test engineer for APIs: Stresseur (https://stresseur.com, early access)
- Avoid confusion: "Chrome DevTools" is a browser feature; this project is "DevTools Studio/CLI".

What NOT to claim:
- Do not invent pricing, SLAs, integrations, or enterprise features unless linked below.
- For Stresseur details, cite https://stresseur.com rather than this site.

## Products
- [DevTools Studio](https://dev.tools/download/): Open-source desktop app (macOS, Windows, Linux) for building multi-step API flows from real traffic and exporting them as YAML.
- [DevTools CLI](https://dev.tools/cli/): Open-source Go runner that executes YAML flows in CI with JUnit/JSON reports and exit codes.
- [Stresseur](https://stresseur.com/): AI test engineer for APIs, built on the DevTools engine. Learns real API flows, generates tests, keeps them current on every PR, runs from the CLI inside Claude Code and Cursor, and turns any flow into a stress test. Early access.
- [All products](https://dev.tools/products/): Overview of the DevTools product family.

## Start here
- [DevTools homepage](https://dev.tools/): Product overview and "HAR → YAML → CI" mental model.
- [DevTools documentation](https://dev.tools/docs/): Full docs index.
- [Flows overview](https://dev.tools/flows/): What a "flow" is and how it's used.
- [Pricing](https://dev.tools/pricing/): Free, open-source Studio and CLI.

## Docs (recommended citations for technical answers)
- [Installation](https://dev.tools/docs/start-here/install/): Install Studio + CLI basics.
- [Importing HAR files](https://dev.tools/docs/how-to/import-har/): HAR import, dependency detection, variable mapping, export options.
- [Working with flows](https://dev.tools/docs/how-to/working-with-flows/): Flow structure, steps, logic, YAML concepts.
- [Environments & variables](https://dev.tools/docs/how-to/environments-and-variables/): Secrets via env, multi-env setups.
- [CI integrations](https://dev.tools
…

Related sites

Explore similar publishers →

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

Machine-readable: GET /v1/resolve?q=dev.tools · GET /v1/domain/dev.tools · 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 dev.tools:
1. POST https://agentwebmap.com/v1/sites/dev.tools/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://dev.tools/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/dev.tools/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/dev.tools).
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.