Recall AI (BYOK)
Read your Recall.ai meeting bots, recordings, transcripts metadata, calendars and calendar events with your own API key
Read Triage malware sandbox analyses: sample lists, search by hash or family, summaries and overview reports, with your own API key
Unify Dynamics LLC
Real questions, and the tools your agent calls to answer them.
list_samplessearch_samplesget_sampleget_sample_summaryget_overview_reportlist_profilesTriage (BYOK) lets an AI assistant read your own Triage data through the Triage API with a key you supply (Triage API key). Read-only: 8 tools (list_samples, search_samples, get_sample, get_sample_summary, get_overview_report, list_profiles, get_user_stats, get_org_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 tria.ge. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Triage. Triage and its logos are trademarks of their owners and are used only to say which service the connector works with.
Sources: Live from the Triage API (tria.ge) with a BYOK key; documentation: https://tria.ge/docs/. Endpoints checked against that documentation on 2026-10-16.
The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.
8 tools, grouped by job. Every one is read-only or compute-only.
https://byok-triage.connectorbay.com/mcpThree ways in, the same 8 tools.
https://byok-triage.connectorbay.com/mcpPOST https://byok-triage.connectorbay.com/v1/tools/<tool>https://connectorbay.com/openai/byok-triage.jsonhttps://connectorbay.com/v1/chat/completions · how it worksX-Upstream-Key header (get one at tria.ge).Triage (BYOK) lets an AI assistant read your own Triage data through the Triage API with a key you supply (Triage API key). It is a hosted MCP server with 8 tools such as List samples, Search samples, Get sample, Get sample summary, Get overview report, List profiles, published by Unify Dynamics LLC. It is independent and not affiliated with Triage.
Add the MCP endpoint https://byok-triage.connectorbay.com/mcp to your client's MCP, connector or integration settings (streamable HTTP, no OAuth). For REST, POST JSON to https://byok-triage.connectorbay.com/v1/tools/<tool>; the OpenAPI description is at /openapi.json. For OpenAI function calling, load https://connectorbay.com/openai/byok-triage.json.
Yes: this is a bring-your-own-key connector. Create a Triage API key at https://tria.ge/account and send it in the X-Upstream-Key header. ConnectorBay uses it for that one call only and never stores, logs or caches it.
Yes. Every tool reads or computes. Nothing is created, changed, sent, paid or deleted in your account.
Yes. It is free to use within the published rate limits; an optional Pro key raises them. There is no account to create.
Read your Recall.ai meeting bots, recordings, transcripts metadata, calendars and calendar events with your own API key
Read your Recruitee recruiting data (job offers, candidate search, departments, locations, tags, sources, talent pools, requisitions) with BYOK
Read your Recruiterflow jobs, pipelines, departments, locations, campaigns and client companies with your own API key
Read your Refiner surveys, NPS, CSAT and rating reports, survey responses and user segments with your own API key
Read your Remote.com company's identity, departments, custom field definitions, supported countries and country holidays with your own customer API token
Read your Rentman rental projects, contacts, crew, equipment, quotes, invoices and stock locations with your own API token
https://byok-triage.connectorbay.com/mcpPOST https://byok-triage.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-triage.connectorbay.com/openapi.jsonX-Upstream-Key header of every request (never stored, logged or cached)https://byok-triage.connectorbay.com/health · Tool schemas: https://byok-triage.connectorbay.com/tools.jsonTriage (BYOK) lets an AI assistant read your own Triage data through the Triage API with a key you supply (Triage API key). Read-only: 8 tools (list_samples, search_samples, get_sample, get_sample_summary, get_overview_report, list_profiles, get_user_stats, get_org_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 tria.ge. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Triage. Triage 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:
list_samples: List analysed samples: the ones you own (default), your organisation's, or the public ones (public cloud only), newest first, with status, kind, filename and submit time.search_samples: Search analyses with Triage search syntax, for example by hash (sha256:...), family (family:emotet), tag (tag:ransomware), extracted C2 (ip:, domain:, url:) or date range (from:, to:). Operators combine with AND, OR, NOT.get_sample: Get one sample: ID, status, kind (file or url), filename, privacy flag and submit time.get_sample_summary: Get a short summary of a sample and its analysis tasks: overall score (1 to 10), hashes, creation and completion time, and per-task status, tags, score and platform.get_overview_report: Get the one-page overview report of a sample: hashes, overall score, malware families, tags, per-target signatures and indicators (URLs, domains, IPs). Extracted configuration and credential blocks are not returned.list_profiles: List analysis profiles your company has (name, tags, network mode, timeout). Only available to company-managed accounts.get_user_stats: Show how many samples your own account has submitted.get_org_stats: Show how many samples your organisation has submitted in total.You bring your own Triage Triage API key (https://tria.ge/account). 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 tria.ge 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.
Live from the Triage API (tria.ge) with a BYOK key; documentation: https://tria.ge/docs/. Endpoints checked against that documentation on 2026-10-16.
Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Triage. Triage 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 Triage account.
Built for: Worldwide. Languages: English.
Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.
What Triage (BYOK) is. Triage (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Triage data: Read Triage malware sandbox analyses: sample lists, search by hash or family, summaries and overview reports, with your own API key. You bring your own Triage Triage API key; the assistant sends it to us with each request.
BYOK key. The key you supply is used to make the one Triage 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 tria.ge, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Triage 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 Triage receives. The request we make on your behalf, including the key and the arguments, under Triage's own terms and privacy policy. Triage acts at your direction and is the only recipient of the data of your request besides our hosting provider.
What we return. The answer Triage 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 Triage 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. Triage (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 Triage at any time to end all access.
Children. Triage (BYOK) is a general-audience service operated by the adult using the assistant, under Triage's own age rules.
Changes. We will post changes here with a new effective date.
Effective 24 October 2026. These terms govern use of the Triage (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").
Email agent@connectorbay.com. We answer within two business days.
https://byok-triage.connectorbay.com/mcphttps://byok-triage.connectorbay.com/openapi.jsonWhen 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. Triage (BYOK) never asks for them.