HDX Humanitarian API (BYOK)

HDX Humanitarian API (BYOK) — connector documentation

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

What HDX Humanitarian API (BYOK) is for

HDX Humanitarian API (BYOK) lets an AI assistant read your own HDX Humanitarian API data through the HDX Humanitarian API API with a key you supply (HDX HAPI app identifier). Read-only: 6 tools (get_operational_presence, get_operational_presence_by_sector, get_population, get_population_by_age_and_gender, list_sectors, get_resource_metadata). 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 hapi.humdata.org. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by HDX Humanitarian API. HDX Humanitarian API 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:

• "Which humanitarian organizations operate in Mali?"
• "Which organizations do water and sanitation work in Yobe, Nigeria?"
• "What is the population of Afghanistan by province?"
• "How many boys under five live in each Afghan province?"
• "Which humanitarian sectors does HAPI know?"
• "Where does HAPI resource b28928be-1847-408f-b3cd-9b87b596c710 come from?"

What it does

• get_operational_presence: List which humanitarian organizations work in which sectors and administrative areas (the 3W operational presence data) for a country.
• get_operational_presence_by_sector: List operational presence rows of one humanitarian sector (for example Nutrition or Water Sanitation Hygiene) in a country, optionally for one organization.
• get_population: Get baseline population figures for a country by subnational area, with gender and age-range breakdowns. Set admin_level to choose national (0), first (1) or second (2) level.
• get_population_by_age_and_gender: Get baseline population for one age range and gender in a country, for example males aged 0-4 at province level.
• list_sectors: List the humanitarian sectors (code and name) used by the operational presence data, to use as sector filters.
• get_resource_metadata: Get the source resource record behind HAPI rows: file name, format, update date, download link and the HDX dataset and provider it comes from.

BYOK key

You bring your own HDX Humanitarian API HDX HAPI app identifier (https://hdx-hapi.readthedocs.io/en/latest/getting-started/). 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 hapi.humdata.org 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://hdx-hapi.readthedocs.io/en/latest/getting-started/ (the API this connector calls, with a BYOK key)

Live from the HDX Humanitarian API API (hapi.humdata.org) with a BYOK key; documentation: https://hdx-hapi.readthedocs.io/en/latest/getting-started/. 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 HDX Humanitarian API. HDX Humanitarian API 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 HDX Humanitarian API account.

Built for: Worldwide. Languages: English.

HDX Humanitarian API (BYOK) — Privacy Policy

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

What HDX Humanitarian API (BYOK) is. HDX Humanitarian API (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own HDX Humanitarian API data: Read standardised humanitarian indicators (who works where, subnational population) from the OCHA Humanitarian Data Exchange with your own app identifier. You bring your own HDX Humanitarian API HDX HAPI app identifier; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one HDX Humanitarian API 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 hapi.humdata.org, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If HDX Humanitarian API 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 HDX Humanitarian API receives. The request we make on your behalf, including the key and the arguments, under HDX Humanitarian API's own terms and privacy policy. HDX Humanitarian API acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer HDX Humanitarian API 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 HDX Humanitarian API 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. HDX Humanitarian API (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 HDX Humanitarian API at any time to end all access.

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

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

HDX Humanitarian API (BYOK) — Terms of Service

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

1. The Service. HDX Humanitarian API (BYOK) provides: Read standardised humanitarian indicators (who works where, subnational population) from the OCHA Humanitarian Data Exchange with your own app identifier. 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 HDX Humanitarian API credentials and only access data you are allowed to access. HDX Humanitarian API's terms apply to your use of HDX Humanitarian API; 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 HDX Humanitarian API. HDX Humanitarian API 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 HDX Humanitarian API returns, lightly trimmed; it may be incomplete, delayed or changed by HDX Humanitarian API. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your HDX Humanitarian API 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 HDX Humanitarian API'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; HDX Humanitarian API 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 HDX Humanitarian API 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 HDX Humanitarian API 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-hdx-hapi

HDX Humanitarian API (BYOK) support

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

• MCP endpoint: https://byok-hdx-hapi.connectorbay.com/mcp
• REST API: https://byok-hdx-hapi.connectorbay.com/openapi.json
• Live status: https://byok-hdx-hapi.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. HDX Humanitarian API (BYOK) never asks for them.