Amplitude (BYOK)
Read your Amplitude active users, sessions, event totals and segmentation, user composition and real-time activity with BYOK and secret key (default US data center)
Read your Buildium lookup lists: task, vendor, file and asset categories and user roles, with your own API key
Unify Dynamics LLC
Real questions, and the tools your agent calls to answer them.
list_task_categorieslist_vendor_categorieslist_file_categorieslist_asset_categorieslist_user_rolesBuildium Catalog (BYOK) lets an AI assistant read your own Buildium Catalog data through the Buildium Catalog API with a key you supply (API key client ID). Read-only: 5 tools (list_task_categories, list_vendor_categories, list_file_categories, list_asset_categories, list_user_roles). 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.buildium.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Buildium Catalog. Buildium Catalog and its logos are trademarks of their owners and are used only to say which service the connector works with.
Sources: Live from the Buildium Catalog API (api.buildium.com) with a BYOK key; documentation: https://developer.buildium.com/. 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.
5 tools, grouped by job. Every one is read-only or compute-only.
https://byok-buildium-catalog.connectorbay.com/mcpThree ways in, the same 5 tools.
https://byok-buildium-catalog.connectorbay.com/mcpPOST https://byok-buildium-catalog.connectorbay.com/v1/tools/<tool>https://connectorbay.com/openai/byok-buildium-catalog.jsonhttps://connectorbay.com/v1/chat/completions · how it worksX-Upstream-Key header (get one at developer.buildium.com).Buildium Catalog (BYOK) lets an AI assistant read your own Buildium Catalog data through the Buildium Catalog API with a key you supply (API key… It is a hosted MCP server with 5 tools such as List task categories, List vendor categories, List file categories, List asset categories, List user roles, published by Unify Dynamics LLC. It is independent and not affiliated with Buildium Catalog.
Add the MCP endpoint https://byok-buildium-catalog.connectorbay.com/mcp to your client's MCP, connector or integration settings (streamable HTTP, no OAuth). For REST, POST JSON to https://byok-buildium-catalog.connectorbay.com/v1/tools/<tool>; the OpenAPI description is at /openapi.json. For OpenAI function calling, load https://connectorbay.com/openai/byok-buildium-catalog.json.
Yes: this is a bring-your-own-key connector. Create a API key client ID at https://developer.buildium.com/#section/Getting-Started/Creating-API-Keys 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 Amplitude active users, sessions, event totals and segmentation, user composition and real-time activity with BYOK and secret key (default US data center)
Read your Amplitude tracking plan: event categories, event types, shared event properties, user properties and group properties, with your own API key and secret key (default US data center)
Read Bible translations, books, chapters, verses and passages and search scripture text across hundreds of versions with your own API.Bible key
Read the contacts, accounts, deals, notes, stages, lists and sequences of your own Apollo workspace with BYOK (credit-free endpoints only)
Read your Apono just-in-time access setup: integrations, connectors, access flows, bundles, spaces, scopes, groups and activity reports with your own API token
Read your Appcues flows, NPS surveys, checklists, banners, pins, launchpads, segments and tags with your own API key and secret
https://byok-buildium-catalog.connectorbay.com/mcpPOST https://byok-buildium-catalog.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-buildium-catalog.connectorbay.com/openapi.jsonX-Upstream-Key header and the API key secret in X-Upstream-Key-2 of every request (never stored, logged or cached)https://byok-buildium-catalog.connectorbay.com/health · Tool schemas: https://byok-buildium-catalog.connectorbay.com/tools.jsonBuildium Catalog (BYOK) lets an AI assistant read your own Buildium Catalog data through the Buildium Catalog API with a key you supply (API key client ID). Read-only: 5 tools (list_task_categories, list_vendor_categories, list_file_categories, list_asset_categories, list_user_roles). 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.buildium.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Buildium Catalog. Buildium Catalog 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_task_categories: List task categories with their sub categories and whether they are built in.list_vendor_categories: List vendor categories with name and whether the category is built in.list_file_categories: List file categories with name and whether they can be edited.list_asset_categories: List the categories used for inventory assets and appliances.list_user_roles: List Buildium user roles with name, description and the number of users in each (no user details).You bring your own Buildium Catalog API key client ID (https://developer.buildium.com/#section/Getting-Started/Creating-API-Keys). 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.buildium.com 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.
Buildium's Open API needs a Premium subscription with the Open API setting turned on and an API key created under Settings > Developer Tools.
Live from the Buildium Catalog API (api.buildium.com) with a BYOK key; documentation: https://developer.buildium.com/. Endpoints checked against that documentation on 2026-10-16.
Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Buildium Catalog. Buildium Catalog 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 Buildium Catalog account.
Built for: Worldwide. Languages: English.
Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.
What Buildium Catalog (BYOK) is. Buildium Catalog (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Buildium Catalog data: Read your Buildium lookup lists: task, vendor, file and asset categories and user roles, with your own API key. You bring your own Buildium Catalog API key client ID; the assistant sends it to us with each request.
BYOK key. The key you supply is used to make the one Buildium Catalog 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.buildium.com, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Buildium Catalog 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 Buildium Catalog receives. The request we make on your behalf, including the key and the arguments, under Buildium Catalog's own terms and privacy policy. Buildium Catalog acts at your direction and is the only recipient of the data of your request besides our hosting provider.
What we return. The answer Buildium Catalog 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 Buildium Catalog 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. Buildium Catalog (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 Buildium Catalog at any time to end all access.
Children. Buildium Catalog (BYOK) is a general-audience service operated by the adult using the assistant, under Buildium Catalog'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 Buildium Catalog (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").
Email agent@connectorbay.com. We answer within two business days.
https://byok-buildium-catalog.connectorbay.com/mcphttps://byok-buildium-catalog.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. Buildium Catalog (BYOK) never asks for them.