LeakIX (BYOK)
Read LeakIX internet scan results: exposed services, leaks and misconfigurations, subdomains and detection plugins, with your own API key
Read your Requesty LLM router organization balance, API keys with spend and limits, groups and usage statistics with your own management API key
Unify Dynamics LLC
Real questions, and the tools your agent calls to answer them.
get_organizationget_organization_usagelist_api_keysget_api_keylist_groupsget_groupRequesty (BYOK) lets an AI assistant read your own Requesty data through the Requesty API with a key you supply (Requesty API key with manage read permission). Read-only: 6 tools (get_organization, get_organization_usage, list_api_keys, get_api_key, list_groups, get_group). 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-v2.requesty.ai. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Requesty. Requesty and its logos are trademarks of their owners and are used only to say which service the connector works with.
Sources: Live from the Requesty API (api-v2.requesty.ai) with a BYOK key; documentation: https://docs.requesty.ai/api-reference/management-apis. 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.
6 tools, grouped by job. Every one is read-only or compute-only.
https://byok-requesty.connectorbay.com/mcpThree ways in, the same 6 tools.
https://byok-requesty.connectorbay.com/mcpPOST https://byok-requesty.connectorbay.com/v1/tools/<tool>https://connectorbay.com/openai/byok-requesty.jsonhttps://connectorbay.com/v1/chat/completions · how it worksX-Upstream-Key header (get one at app.requesty.ai).Requesty (BYOK) lets an AI assistant read your own Requesty data through the Requesty API with a key you supply (Requesty API key with manage read… It is a hosted MCP server with 6 tools such as Get organization, Get organization usage, List api keys, Get api key, List groups, Get group, published by Unify Dynamics LLC. It is independent and not affiliated with Requesty.
Add the MCP endpoint https://byok-requesty.connectorbay.com/mcp to your client's MCP, connector or integration settings (streamable HTTP, no OAuth). For REST, POST JSON to https://byok-requesty.connectorbay.com/v1/tools/<tool>; the OpenAPI description is at /openapi.json. For OpenAI function calling, load https://connectorbay.com/openai/byok-requesty.json.
Yes: this is a bring-your-own-key connector. Create a Requesty API key with manage read permission at https://app.requesty.ai/ 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 LeakIX internet scan results: exposed services, leaks and misconfigurations, subdomains and detection plugins, with your own API key
Read your Leaseweb dedicated servers, public cloud instances, load balancers, IP addresses and object storage with your own API key
Read your Letta agents, their messages, memory blocks, tools, runs, steps, folders and models with your own API key
Read your Level remote monitoring and management fleet: devices, groups, tags, alerts, patch updates, automations and the activity log with your own API key
Look up open-source packages across package managers, their dependents, contributors and SourceRank, and your subscriptions, with your own Libraries.io API key
Read your LIFX lights and scenes and change light power, brightness, color and effects through the LIFX HTTP API with your own access token
https://byok-requesty.connectorbay.com/mcpPOST https://byok-requesty.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-requesty.connectorbay.com/openapi.jsonX-Upstream-Key header of every request (never stored, logged or cached)https://byok-requesty.connectorbay.com/health · Tool schemas: https://byok-requesty.connectorbay.com/tools.jsonRequesty (BYOK) lets an AI assistant read your own Requesty data through the Requesty API with a key you supply (Requesty API key with manage read permission). Read-only: 6 tools (get_organization, get_organization_usage, list_api_keys, get_api_key, list_groups, get_group). 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-v2.requesty.ai. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Requesty. Requesty 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:
get_organization: Show the organization's name and prepaid balance.get_organization_usage: Get aggregated usage for the whole organization over a date range (at most 100 days), by hour, day or month, optionally grouped by model, API key, provider and more.list_api_keys: List the organization's API keys with monthly limit, month-to-date spend, permissions, labels and group.get_api_key: Get one API key's spend, limit, permissions and group; use 'self' for the calling key.list_groups: List groups with member counts, month-to-date spend and monthly limits.get_group: Get one group's name and monthly limit (member details are not returned).You bring your own Requesty Requesty API key with manage read permission (https://app.requesty.ai/). 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-v2.requesty.ai 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 Requesty API (api-v2.requesty.ai) with a BYOK key; documentation: https://docs.requesty.ai/api-reference/management-apis. Endpoints checked against that documentation on 2026-10-16.
Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Requesty. Requesty 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 Requesty account.
Built for: Worldwide. Languages: English.
Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.
What Requesty (BYOK) is. Requesty (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Requesty data: Read your Requesty LLM router organization balance, API keys with spend and limits, groups and usage statistics with your own management API key. You bring your own Requesty Requesty API key with manage read permission; the assistant sends it to us with each request.
BYOK key. The key you supply is used to make the one Requesty 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-v2.requesty.ai, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Requesty 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 Requesty receives. The request we make on your behalf, including the key and the arguments, under Requesty's own terms and privacy policy. Requesty acts at your direction and is the only recipient of the data of your request besides our hosting provider.
What we return. The answer Requesty 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 Requesty 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. Requesty (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 Requesty at any time to end all access.
Children. Requesty (BYOK) is a general-audience service operated by the adult using the assistant, under Requesty'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 Requesty (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").
Email agent@connectorbay.com. We answer within two business days.
https://byok-requesty.connectorbay.com/mcphttps://byok-requesty.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. Requesty (BYOK) never asks for them.