KOMOJU (BYOK)

KOMOJU (BYOK) — connector documentation

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

What KOMOJU (BYOK) is for

KOMOJU (BYOK) lets an AI assistant read your own KOMOJU data through the KOMOJU API with a key you supply (secret API key). Read-only: 12 tools (list_payments, get_payment, get_session, list_customers, list_subscriptions, list_chargebacks, get_chargeback, list_events, get_balance, list_balance_transactions, list_settlements, get_settlement). 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 komoju.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by KOMOJU. KOMOJU 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 KOMOJU payments were captured this week?"
• "What is the status of KOMOJU payment pay3fj6nnhvws08idzacf6et8?"
• "Did KOMOJU session 4k2x9ap7qrz0m3tsgd1wbyvc6 get paid?"
• "Which customers are saved in KOMOJU?"
• "Which KOMOJU subscriptions are active and when do they renew?"
• "Are there KOMOJU chargebacks I still need to answer?"

What it does

• list_payments: List payments newest first with status, amount, currency, order number and customer; filter by status, currency, your order number and a time range. Card holder details are not returned.
• get_payment: Get one payment by id with status, amounts, refunded amount, payment method type and card brand, capture time and order number.
• get_session: Get one hosted checkout session: status, amount, currency, expiry, completion time, line items and the resulting payment status.
• list_customers: List saved customers (for subscriptions and one-click payments) with id, email, locale and creation time.
• list_subscriptions: List subscriptions with status, amount, billing period and day, retry count, next charge time and start/end times.
• list_chargebacks: List chargeback requests with amount, reason, due date and status; filter by status, payment id and due-date range.
• get_chargeback: Get one chargeback request by id with payment, amount, reason, due date and status.
• list_events: List account events (such as payment captured or refunded) newest first with type, resource and time.
• get_balance: Show the balance in one currency in the smallest unit (total_balance_cents) with the breakdown of payments, refunds, corrections and fees.
• list_balance_transactions: List balance movements in one currency with type, amount in the smallest unit and time; filter by type and time range.
• list_settlements: List settlements with reference, status, cycle, transaction amount, fees, remittance amount and cut-off time (amounts in the smallest unit).
• get_settlement: Get one settlement with its breakdown: captured payments, refunds, corrections, disbursements and fees (amounts in the smallest unit).

BYOK key

You bring your own KOMOJU secret API key (https://docs.komoju.com/en/docs/introduction/authentication.md). 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 komoju.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.

Data sources

• https://docs.komoju.com/en/api-reference/2025-01-28/index.md (the API this connector calls, with a BYOK key)

Live from the KOMOJU API (komoju.com) with a BYOK key; documentation: https://docs.komoju.com/en/api-reference/2025-01-28/index.md. 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 KOMOJU. KOMOJU 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 KOMOJU account.

Built for: Worldwide. Languages: English.

KOMOJU (BYOK) — Privacy Policy

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

What KOMOJU (BYOK) is. KOMOJU (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own KOMOJU data: Read your KOMOJU (Japan) payments, sessions, subscriptions, chargebacks, events, balance and settlements with your own secret API key. You bring your own KOMOJU secret API key; the assistant sends it to us with each request.

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

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

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

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

KOMOJU (BYOK) — Terms of Service

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

1. The Service. KOMOJU (BYOK) provides: Read your KOMOJU (Japan) payments, sessions, subscriptions, chargebacks, events, balance and settlements with your own secret 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 KOMOJU credentials and only access data you are allowed to access. KOMOJU's terms apply to your use of KOMOJU; 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 KOMOJU. KOMOJU 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 KOMOJU returns, lightly trimmed; it may be incomplete, delayed or changed by KOMOJU. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your KOMOJU 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 KOMOJU'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; KOMOJU 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 KOMOJU 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 KOMOJU 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-komoju

KOMOJU (BYOK) support

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

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