qa.tech valid

QA.tech

QA.tech is an AI testing platform for web and mobile applications. Autonomous QA agents explore your product the way a user does, then run regression, exploratory and end-to-end tests on every pull request and release, without hand-written selectors or test scripts to maintain.

For agents: AI testing platform with autonomous QA agents for web and mobile apps; docs cover API reference, OpenAPI spec, auth, MCP server and webhooks.

ai testingend-to-end testingregression testingmcp serverqa automation

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-21T02:36:29.561Z. Cached copy · Source on qa.tech

# QA.tech

> QA.tech is an AI testing platform for web and mobile applications. Autonomous QA agents explore your product the way a user does, then run regression, exploratory and end-to-end tests on every pull request and release, without hand-written selectors or test scripts to maintain.

Vision-based agents interact with the real UI, so tests survive markup and layout changes. Tests are described in plain English; the agent works out the steps and reports what broke. Runs happen on every pull request and on a schedule, posting results into GitHub, GitLab, Slack and Jira. Coverage spans web apps, mobile apps on iOS and Android, and API-backed flows including authenticated journeys. Teams using QA.tech include Pricer, Upsales, Strise, Virtusize, 4C Strategies and Airpelago.

Every indexable page has a markdown twin. Append `.md` to any path (for example https://qa.tech/blog/what-is-agentic-testing.md), or request the normal URL with an `Accept: text/markdown` header and the markdown version is returned. Each HTML page also advertises its twin via `<link rel="alternate" type="text/markdown">`.

The REST API and the MCP server share the same tokens and the same base host, https://api.qa.tech. Error responses from QA.tech endpoints are JSON with a stable `code`, a human `message`, a resolution `hint` and a `docs` link.

## Start here

- [Product documentation](https://docs.qa.tech): how the product works, setup guides, API reference.
- [Sitemap](https://qa.tech/sitemap.xml): every indexable page on qa.tech.
- [App login](https://app.qa.tech): the QA.tech application.
- [Crawler policy and content signals](https://qa.tech/robots.txt): robots directives for this site.

## Developer resources (API, MCP, auth, webhooks)

- [QA.tech developer hub](https://qa.tech/developers): one page listing the API docs, OpenAPI spec, auth, MCP server, webhooks and CLI by name.
- [QA.tech API documentation](https://docs.qa.tech/api-reference/introduction): REST API reference – runs, test cases, issues, applications, mobile builds and tunnels.
- [QA.tech OpenAPI specification](https://docs.qa.tech/api-reference/api.json): machine-readable OpenAPI 3 document, including security schemes and server base URL.
- [QA.tech API authentication](https://docs.qa.tech/api-reference/introduction#authentication): bearer API keys (org- or project-scoped, read or write) and OAuth sign-in for interactive clients.
- [QA.tech MCP server](https://qa.tech/product/mcp): endpoint https://api.qa.tech/v1/mcp, streamable HTTP, OAuth sign-in or bearer API key.
- [QA.tech MCP setup guide](https://docs.qa.tech/integrations/mcp): client configuration for Cursor, Claude Code, Claude Desktop, Codex and Continue.
- [QA.tech MCP server card](https://qa.tech/.well-known/mcp/server-card.json): machine-readable MCP descriptor (endpoint, transport, auth methods, tools).
- [QA.tech API authentication doc](https://qa.tech/.well-known/auth.md): markdown summary of bearer keys, OAuth sign-in and the JSON erro
…

Related sites

Other listed sites in Developer tools. See the whole category →

Machine-readable: GET /v1/resolve?q=qa.tech · GET /v1/domain/qa.tech · 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 qa.tech:
1. POST https://agentwebmap.com/v1/sites/qa.tech/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://qa.tech/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/qa.tech/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/qa.tech).
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.