Buildkite Test Engine (BYOK)
Read your Buildkite Test Engine suites, test runs and failed test executions with your own API access token (read_suites scope)
Search ReliefWeb humanitarian reports, disasters, countries, jobs, training and sources through the ReliefWeb API with your own approved appname
Unify Dynamics LLC
Real questions, and the tools your agent calls to answer them.
search_reportsget_reportsearch_disasterslist_countriessearch_jobssearch_trainingReliefWeb (BYOK) lets an AI assistant read your own ReliefWeb data through the ReliefWeb API with a key you supply (pre-approved ReliefWeb appname). Read-only: 7 tools (search_reports, get_report, search_disasters, list_countries, search_jobs, search_training, search_sources). 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.reliefweb.int. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by ReliefWeb. ReliefWeb and its logos are trademarks of their owners and are used only to say which service the connector works with.
Sources: Live from the ReliefWeb API (api.reliefweb.int) with a BYOK key; documentation: https://apidoc.reliefweb.int/. 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.
7 tools, grouped by job. Every one is read-only or compute-only.
https://byok-reliefweb.connectorbay.com/mcpThree ways in, the same 7 tools.
https://byok-reliefweb.connectorbay.com/mcpPOST https://byok-reliefweb.connectorbay.com/v1/tools/<tool>https://connectorbay.com/openai/byok-reliefweb.jsonhttps://connectorbay.com/v1/chat/completions · how it worksX-Upstream-Key header (get one at apidoc.reliefweb.int).ReliefWeb (BYOK) lets an AI assistant read your own ReliefWeb data through the ReliefWeb API with a key you supply (pre-approved ReliefWeb appname). It is a hosted MCP server with 7 tools such as Search reports, Get report, Search disasters, List countries, Search jobs, Search training, published by Unify Dynamics LLC. It is independent and not affiliated with ReliefWeb.
Add the MCP endpoint https://byok-reliefweb.connectorbay.com/mcp to your client's MCP, connector or integration settings (streamable HTTP, no OAuth). For REST, POST JSON to https://byok-reliefweb.connectorbay.com/v1/tools/<tool>; the OpenAPI description is at /openapi.json. For OpenAI function calling, load https://connectorbay.com/openai/byok-reliefweb.json.
Yes: this is a bring-your-own-key connector. Create a pre-approved ReliefWeb appname at https://apidoc.reliefweb.int/ 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 Buildkite Test Engine suites, test runs and failed test executions with your own API access token (read_suites scope)
Read your Bump.sh API documentation hubs, branches, deployed versions and API change diffs with your own token
Search German Bundestag proceedings, printed papers, plenary protocols, parliamentary activities and members through the DIP API with your own key
Read your bunny.net pull zones, storage zones, DNS zones and records, video libraries, statistics and billing summary with BYOK
Read your Bytescale folder structure, file details and recent file-processing jobs with your own secret API key
Browse Canadian court and tribunal decisions, citations and legislation metadata on CanLII with your own API key
https://byok-reliefweb.connectorbay.com/mcpPOST https://byok-reliefweb.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-reliefweb.connectorbay.com/openapi.jsonX-Upstream-Key header of every request (never stored, logged or cached)https://byok-reliefweb.connectorbay.com/health · Tool schemas: https://byok-reliefweb.connectorbay.com/tools.jsonReliefWeb (BYOK) lets an AI assistant read your own ReliefWeb data through the ReliefWeb API with a key you supply (pre-approved ReliefWeb appname). Read-only: 7 tools (search_reports, get_report, search_disasters, list_countries, search_jobs, search_training, search_sources). 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.reliefweb.int. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by ReliefWeb. ReliefWeb 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:
search_reports: Search ReliefWeb reports (situation updates, analysis, maps) by text and one filter, newest first by default.get_report: Get one ReliefWeb report by its numeric id; use profile=full to read the full text, sources, countries and files.search_disasters: Search ReliefWeb disasters (events with GLIDE number, type, countries and status) by text and one filter.list_countries: List ReliefWeb's country records (name, ISO3 code, status and description), optionally by text.search_jobs: Search humanitarian job postings on ReliefWeb by text and one filter (country, career category, experience, source).search_training: Search training opportunities and courses listed on ReliefWeb by text and one filter.search_sources: Search the organizations (sources) that publish on ReliefWeb, with type, homepage and country.You bring your own ReliefWeb pre-approved ReliefWeb appname (https://apidoc.reliefweb.int/). 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.reliefweb.int 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 ReliefWeb API (api.reliefweb.int) with a BYOK key; documentation: https://apidoc.reliefweb.int/. Endpoints checked against that documentation on 2026-10-16.
Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by ReliefWeb. ReliefWeb 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 ReliefWeb account.
Built for: Worldwide. Languages: English.
Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.
What ReliefWeb (BYOK) is. ReliefWeb (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own ReliefWeb data: Search ReliefWeb humanitarian reports, disasters, countries, jobs, training and sources through the ReliefWeb API with your own approved appname. You bring your own ReliefWeb pre-approved ReliefWeb appname; the assistant sends it to us with each request.
BYOK key. The key you supply is used to make the one ReliefWeb 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.reliefweb.int, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If ReliefWeb 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 ReliefWeb receives. The request we make on your behalf, including the key and the arguments, under ReliefWeb's own terms and privacy policy. ReliefWeb acts at your direction and is the only recipient of the data of your request besides our hosting provider.
What we return. The answer ReliefWeb 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 ReliefWeb 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. ReliefWeb (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 ReliefWeb at any time to end all access.
Children. ReliefWeb (BYOK) is a general-audience service operated by the adult using the assistant, under ReliefWeb'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 ReliefWeb (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").
Email agent@connectorbay.com. We answer within two business days.
https://byok-reliefweb.connectorbay.com/mcphttps://byok-reliefweb.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. ReliefWeb (BYOK) never asks for them.