Campfire (BYOK)
Read your Campfire accounting data: invoices, bills, vendors and customers, chart of accounts, budgets, fixed assets, contracts and the trial balance with your own API key
Read your Midtrans (Indonesia) transaction status, subscriptions, invoices and balance mutations with your own server key
Unify Dynamics LLC
Real questions, and the tools your agent calls to answer them.
get_transaction_statusget_balance_mutationget_subscriptionget_invoiceget_card_bin_infoMidtrans (BYOK) lets an AI assistant read your own Midtrans data through the Midtrans API with a key you supply (server key (production)). Read-only: 5 tools (get_transaction_status, get_balance_mutation, get_subscription, get_invoice, get_card_bin_info). 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.midtrans.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Midtrans. Midtrans and its logos are trademarks of their owners and are used only to say which service the connector works with.
Sources: Live from the Midtrans API (api.midtrans.com) with a BYOK key; documentation: https://docs.midtrans.com/reference/get-transaction-status. 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-midtrans.connectorbay.com/mcpThree ways in, the same 5 tools.
https://byok-midtrans.connectorbay.com/mcpPOST https://byok-midtrans.connectorbay.com/v1/tools/<tool>https://connectorbay.com/openai/byok-midtrans.jsonhttps://connectorbay.com/v1/chat/completions · how it worksX-Upstream-Key header (get one at docs.midtrans.com).Midtrans (BYOK) lets an AI assistant read your own Midtrans data through the Midtrans API with a key you supply (server key (production)). It is a hosted MCP server with 5 tools such as Get transaction status, Get balance mutation, Get subscription, Get invoice, Get card bin info, published by Unify Dynamics LLC. It is independent and not affiliated with Midtrans.
Add the MCP endpoint https://byok-midtrans.connectorbay.com/mcp to your client's MCP, connector or integration settings (streamable HTTP, no OAuth). For REST, POST JSON to https://byok-midtrans.connectorbay.com/v1/tools/<tool>; the OpenAPI description is at /openapi.json. For OpenAI function calling, load https://connectorbay.com/openai/byok-midtrans.json.
Yes: this is a bring-your-own-key connector. Create a server key (production) at https://docs.midtrans.com/docs/api-authorization-headers 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 Campfire accounting data: invoices, bills, vendors and customers, chart of accounts, budgets, fixed assets, contracts and the trial balance with your own API key
Look up US nonprofits, IRS charity checks, grants and sector news with your own Candid API subscription key
Discover carbon credit projects by country, vintage, methodology category or text, with registry, supply and price, using your own Carbonmark API key
Read your Cashfree payment gateway orders, payments, refunds, disputes, settlements and reconciliation reports with your own app ID and secret
Read multi-chain blockchain data from Chainbase (blocks, transactions, balances, token prices, holders, ENS) with your own API key
Read your Chapa account in Ethiopia: payment and transfer status, transaction timelines, balances, supported banks and exchange rates with your own secret key
https://byok-midtrans.connectorbay.com/mcpPOST https://byok-midtrans.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-midtrans.connectorbay.com/openapi.jsonX-Upstream-Key header of every request (never stored, logged or cached)https://byok-midtrans.connectorbay.com/health · Tool schemas: https://byok-midtrans.connectorbay.com/tools.jsonMidtrans (BYOK) lets an AI assistant read your own Midtrans data through the Midtrans API with a key you supply (server key (production)). Read-only: 5 tools (get_transaction_status, get_balance_mutation, get_subscription, get_invoice, get_card_bin_info). 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.midtrans.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Midtrans. Midtrans 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:
get_transaction_status: Get the status of one transaction by merchant order id or Midtrans transaction id: payment type, status, fraud status, gross amount, bank and refunds. The masked card and signature are not returned.get_balance_mutation: Get balance mutations for a currency over a time window: opening and closing effective, pending and overall balance, per wallet source. Useful for reconciliation.get_subscription: Get one recurring-payment subscription by id: name, amount, currency, status, schedule and payment type. Customer details and the card token are not returned.get_invoice: Get one Midtrans invoice or quotation by invoice id: number, status, dates, amount, items and taxes. Customer contact details are not returned.get_card_bin_info: Look up what a card BIN (the first 6 or 8 digits only) is: issuing country, card network, credit or debit, class and bank. Never pass a full card number.You bring your own Midtrans server key (production) (https://docs.midtrans.com/docs/api-authorization-headers). 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.midtrans.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.
Live from the Midtrans API (api.midtrans.com) with a BYOK key; documentation: https://docs.midtrans.com/reference/get-transaction-status. Endpoints checked against that documentation on 2026-10-16.
Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Midtrans. Midtrans 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 Midtrans account.
Built for: Worldwide. Languages: English.
Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.
What Midtrans (BYOK) is. Midtrans (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Midtrans data: Read your Midtrans (Indonesia) transaction status, subscriptions, invoices and balance mutations with your own server key. You bring your own Midtrans server key (production); the assistant sends it to us with each request.
BYOK key. The key you supply is used to make the one Midtrans 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.midtrans.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 Midtrans 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 Midtrans receives. The request we make on your behalf, including the key and the arguments, under Midtrans's own terms and privacy policy. Midtrans acts at your direction and is the only recipient of the data of your request besides our hosting provider.
What we return. The answer Midtrans 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 Midtrans 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. Midtrans (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 Midtrans at any time to end all access.
Children. Midtrans (BYOK) is a general-audience service operated by the adult using the assistant, under Midtrans'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 Midtrans (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").
Email agent@connectorbay.com. We answer within two business days.
https://byok-midtrans.connectorbay.com/mcphttps://byok-midtrans.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. Midtrans (BYOK) never asks for them.