TestingBot (BYOK)

TestingBot (BYOK) — connector documentation

• MCP endpoint: https://byok-testingbot.connectorbay.com/mcp
• REST API: POST https://byok-testingbot.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-testingbot.connectorbay.com/openapi.json
• Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
• Authentication: your own TestingBot TestingBot API key, sent in the X-Upstream-Key header and the TestingBot API secret in X-Upstream-Key-2 of every request (never stored, logged or cached)
• Health: https://byok-testingbot.connectorbay.com/health · Tool schemas: https://byok-testingbot.connectorbay.com/tools.json
• Publisher: Unify Dynamics LLC · connectorbay.com/byok-testingbot · agent@connectorbay.com

What TestingBot (BYOK) is for

TestingBot (BYOK) lets an AI assistant read your own TestingBot data through the TestingBot API with a key you supply (TestingBot API key). Read-only: 9 tools (get_user, list_tests, get_test, list_builds, list_build_tests, get_test_summary, get_test_trends, list_top_failures, list_test_case_stats). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.testingbot.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by TestingBot. TestingBot and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

• "How many test minutes do I have left on TestingBot?"
• "Which of my recent TestingBot tests failed?"
• "Why did TestingBot test 3 fail?"
• "Which TestingBot builds do I have?"
• "Which tests in TestingBot build first-build failed?"
• "What was my TestingBot pass rate over the last 7 days?"

What it does

• get_user: Show the TestingBot account the key belongs to: name, plan, remaining test seconds, concurrency limits and current concurrent sessions.
• list_tests: List your TestingBot test sessions, newest first, with pass/fail, browser, OS, duration and build. Filter by build, group, browser ID or update time.
• get_test: Get one test session by numeric ID or WebDriver session ID: state, result, failure message, browser, OS or device, build, groups, duration and type.
• list_builds: List your TestingBot builds (groups of tests sharing a build identifier), optionally by tag.
• list_build_tests: List the test sessions of one build, by numeric build ID or build identifier, with result, browser, OS and duration.
• get_test_summary: Show headline totals for a period: tests run, passed, failed, unknown, pass rate and failure rate.
• get_test_trends: Show pass, fail and unknown counts per day (or per browser, or rolled up by status) for a period, newest first.
• list_top_failures: List the most common failure messages of failed tests in a period with occurrence counts.
• list_test_case_stats: List per-test-name statistics for a period: runs, passes, failures, pass rate, flaky flag and average duration.

BYOK key

You bring your own TestingBot TestingBot API key (https://testingbot.com/support/api#authentication). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.testingbot.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

• https://testingbot.com/support/api (the API this connector calls, with a BYOK key)

Live from the TestingBot API (api.testingbot.com) with a BYOK key; documentation: https://testingbot.com/support/api. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by TestingBot. TestingBot and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your TestingBot account.

Built for: Worldwide. Languages: English.

TestingBot (BYOK) — Privacy Policy

Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What TestingBot (BYOK) is. TestingBot (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own TestingBot data: Read your TestingBot cross-browser test sessions, builds and pass/fail analytics with your own API key and secret. You bring your own TestingBot TestingBot API key; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one TestingBot call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to api.testingbot.com, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If TestingBot rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What TestingBot receives. The request we make on your behalf, including the key and the arguments, under TestingBot's own terms and privacy policy. TestingBot acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer TestingBot gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your TestingBot data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. TestingBot (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at TestingBot at any time to end all access.

Children. TestingBot (BYOK) is a general-audience service operated by the adult using the assistant, under TestingBot's own age rules.

Changes. We will post changes here with a new effective date.

TestingBot (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the TestingBot (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

1. The Service. TestingBot (BYOK) provides: Read your TestingBot cross-browser test sessions, builds and pass/fail analytics with your own API key and secret. It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
2. Your own key, your own account. You must use your own TestingBot credentials and only access data you are allowed to access. TestingBot's terms apply to your use of TestingBot; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by TestingBot. TestingBot and its logos are trademarks of their owners and are used only to say which service the connector works with.
4. No advice, no guarantees. Output is the data TestingBot returns, lightly trimmed; it may be incomplete, delayed or changed by TestingBot. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your TestingBot account.
6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent TestingBot's controls, or to attack any system.
7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; TestingBot may change or end its API at any time.
8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your TestingBot key.
10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action TestingBot takes on your account. Our total liability is limited to US $100.
11. Governing law. California law; venue in San Mateo County, California.
12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-testingbot

TestingBot (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

• MCP endpoint: https://byok-testingbot.connectorbay.com/mcp
• REST API: https://byok-testingbot.connectorbay.com/openapi.json
• Live status: https://byok-testingbot.connectorbay.com/health

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. TestingBot (BYOK) never asks for them.