Humaans (BYOK)

Humaans (BYOK) — connector documentation

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

What Humaans (BYOK) is for

Humaans (BYOK) lets an AI assistant read your own Humaans data through the Humaans API with a key you supply (Humaans API access token (public:read or private:read scope)). Read-only: 12 tools (get_token_info, list_companies, list_people, get_person, list_job_roles, list_locations, list_org_units, list_time_away, list_time_away_periods, list_time_away_types, list_public_holiday_calendars, list_public_holidays). 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 app.humaans.io. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Humaans. Humaans 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 scopes does my Humaans token have and when does it expire?"
• "Which Humaans company is this token for?"
• "Who joined the company this year?"
• "Show the profile of person abc123"
• "What is everyone's job title as of today?"
• "Where are our offices?"

What it does

• get_token_info: Show the scopes the token has and when it expires.
• list_companies: List the company the token belongs to with name, status, payment status and dates.
• list_people: List people with name, work email, status, job role, location, contract type, start and end dates, teams and holiday calendar; active people by default, filter by status, work email or start date range. Home address, birthday and tax fields are left out.
• get_person: Get one person by id with name, work email, status, job role, location, contract type, start and end dates, teams and holiday calendar. Home address, birthday and tax fields are left out.
• list_job_roles: List job roles (job title, department, effective dates, who they report to); use as_of to get the role in effect on a date for each person.
• list_locations: List company locations with label, code, city, country, timezone and the time away policy and working pattern in use.
• list_org_units: List org units (departments, teams, legal entities) with name, code, parent, hierarchy and reporting leader.
• list_time_away: List time away records (leave, remote work, training) with person, dates, half-day periods, type, days, request status and reviewer; filter by person, type, status or date range.
• list_time_away_periods: List leave balance periods with allowance, carried over, used, pending, upcoming, current balance and end-of-year balance; defaults to the pto type.
• list_time_away_types: List time away types (pto, sick, parental and company-specific ones) with name, category and base type.
• list_public_holiday_calendars: List public holiday calendars with name, country, region and number of days.
• list_public_holidays: List the public holidays of one calendar between two dates.

BYOK key

You bring your own Humaans Humaans API access token (public:read or private:read scope) (https://app.humaans.io/settings/api). 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 app.humaans.io 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://docs.humaans.io/api/ (the API this connector calls, with a BYOK key)

Live from the Humaans API (app.humaans.io) with a BYOK key; documentation: https://docs.humaans.io/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 Humaans. Humaans 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 Humaans account.

Built for: Worldwide. Languages: English.

Humaans (BYOK) — Privacy Policy

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

What Humaans (BYOK) is. Humaans (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Humaans data: Read your Humaans people, job roles, locations, org units, time away, leave balances and public holidays with your own API access token. You bring your own Humaans Humaans API access token (public:read or private:read scope); the assistant sends it to us with each request.

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

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

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

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

Humaans (BYOK) — Terms of Service

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

1. The Service. Humaans (BYOK) provides: Read your Humaans people, job roles, locations, org units, time away, leave balances and public holidays with your own API access token. 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 Humaans credentials and only access data you are allowed to access. Humaans's terms apply to your use of Humaans; 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 Humaans. Humaans 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 Humaans returns, lightly trimmed; it may be incomplete, delayed or changed by Humaans. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Humaans 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 Humaans'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; Humaans 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 Humaans 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 Humaans 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-humaans

Humaans (BYOK) support

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

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