Developers

QA.tech developer resources

Everything a human or an agent needs to drive QA.tech programmatically: the REST API, the MCP server, authentication, webhooks and the CLI. The API and the MCP server share the same host, https://api.qa.tech, and the same tokens.

Named resources

6 items

QA.tech API documentationREST reference for test runs, test cases, issues, applications, mobile builds and tunnels.https://api.qa.tech/v1Open
QA.tech OpenAPI specificationMachine-readable OpenAPI 3 document, including the server base URL and security schemes.application/vnd.oai.openapi+jsonOpen
QA.tech API authenticationBearer API keys for servers and CI, OAuth sign-in for interactive clients. Same tokens for REST and MCP.Authorization: BearerOpen
QA.tech MCP serverConnect coding agents and IDEs over the Model Context Protocol – list applications, start runs, read issues.https://api.qa.tech/v1/mcpOpen
QA.tech webhooksRun-completed and issue events delivered to your endpoint, plus GitHub, GitLab, Slack and Jira integrations.POST to your endpointOpen
QA.tech CLIWire the MCP server into supported clients and trigger runs from your terminal or pipeline.npx @qadottech/cliOpen

Machine discovery

Well-known documents for agents

Every indexable page on this site also has a markdown twin – append .md to the path, or send Accept: text/markdown. Errors from QA.tech endpoints are JSON with a stable code, message, hint and docs field.

/.well-known/api-catalog
RFC 9727 linkset – OpenAPI document and API docs.
/.well-known/mcp/server-card.json
MCP endpoint, transport, auth methods and tool names.
/.well-known/agent-skills.json
What agents can do on qa.tech and via the API.
/.well-known/auth.md
Authentication summary in markdown.
/llms.txt
Markdown index of every page on this site.
/sitemap.xml
Canonical URL list.

Your team moves fast. Can your testing keep up?

QA.tech agents test your product autonomously, so moving fast never means shipping broken. See how it works in a 30-minute demo.

Get a demo