Amberflo (BYOK)

Amberflo (BYOK) — connector documentation

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

What Amberflo (BYOK) is for

Amberflo (BYOK) lets an AI assistant read your own Amberflo data through the Amberflo API with a key you supply (Amberflo API key). Read-only: 8 tools (list_customers, list_meters, list_product_items, list_promotions, list_business_units, list_budgets, list_chargeback_invoices, list_cost_ingestion_configs). 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.amberflo.io. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Amberflo. Amberflo 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 Amberflo customers are enabled and what lifecycle stage are they in?"
• "Which usage meters are defined in Amberflo and which are used in billing?"
• "Which product items can Amberflo bill for?"
• "Which discounts and promotions exist in Amberflo?"
• "Which business units do we allocate cloud costs to in Amberflo?"
• "Which cloud cost budgets are set in Amberflo and what are their limits?"

What it does

• list_customers: Page through billing customers with ID, name, lifecycle stage, enabled and test flags and created and updated times, with search, sort and status filters. Email and address are left out.
• list_meters: List usage meter definitions with API name, label, meter type, aggregation, event type, dimensions, billing use and enabled flag.
• list_product_items: List the billable product items of the account with product ID, meter API name, item name and description.
• list_promotions: List account promotions (discounts) with ID, type, name, description, hidden flag and last update.
• list_business_units: Page through business units used for cost allocation and chargeback with name, description and timestamps, with search and sort.
• list_budgets: Page through cost budgets with code, label, limit, active window and usage item, optionally only those active at a point in time.
• list_chargeback_invoices: Page through business unit chargeback invoices (summary only) with period, status and chargeback amount.
• list_cost_ingestion_configs: List cloud cost (FOCUS) ingestion configurations with provider, data type, label, bucket, enabled flag and last scan time. Credentials are left out.

BYOK key

You bring your own Amberflo Amberflo API key (https://docs.amberflo.io/reference/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 app.amberflo.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.amberflo.io/reference/getting-started (the API this connector calls, with a BYOK key)

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

Built for: Worldwide. Languages: English.

Amberflo (BYOK) — Privacy Policy

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

What Amberflo (BYOK) is. Amberflo (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Amberflo data: Read your Amberflo usage metering and billing setup: customers, meters, product items, promotions, business units, budgets, chargeback invoices and cost ingestion configs with your own API key. You bring your own Amberflo Amberflo API key; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Amberflo 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.amberflo.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 Amberflo 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 Amberflo receives. The request we make on your behalf, including the key and the arguments, under Amberflo's own terms and privacy policy. Amberflo acts at your direction and is the only recipient of the data of your request besides our hosting provider.

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

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

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

Amberflo (BYOK) — Terms of Service

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

1. The Service. Amberflo (BYOK) provides: Read your Amberflo usage metering and billing setup: customers, meters, product items, promotions, business units, budgets, chargeback invoices and cost ingestion configs with your own API key. 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 Amberflo credentials and only access data you are allowed to access. Amberflo's terms apply to your use of Amberflo; 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 Amberflo. Amberflo 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 Amberflo returns, lightly trimmed; it may be incomplete, delayed or changed by Amberflo. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Amberflo 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 Amberflo'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; Amberflo 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 Amberflo 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 Amberflo 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-amberflo

Amberflo (BYOK) support

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

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