Rebilly (BYOK)

Rebilly (BYOK) — connector documentation

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

What Rebilly (BYOK) is for

Rebilly (BYOK) lets an AI assistant read your own Rebilly data through the Rebilly API with a key you supply (Rebilly secret API key). Read-only: 9 tools (list_shipping_rates, list_payment_method_catalog, list_payment_gateway_catalog, list_fees, list_webhooks, list_websites, list_gateway_accounts, list_journal_accounts, get_risk_score_rules). 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.rebilly.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Rebilly. Rebilly 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:

• "What shipping rates are configured in Rebilly?"
• "Which payment methods can Rebilly process and do they support recurring payments?"
• "Which payment gateways does Rebilly integrate with and what do they support?"
• "What gateway fees are configured in Rebilly?"
• "Where does my Rebilly account send webhooks?"
• "Which websites are set up in Rebilly?"

What it does

• list_shipping_rates: List shipping rates with name, price, currency, the filter rule that selects them and active status.
• list_payment_method_catalog: List the payment methods Rebilly supports (cards, wallets, bank transfers and others) with supported countries and currencies, recurring, refund and dispute support.
• list_payment_gateway_catalog: List the payment gateways Rebilly integrates with: supported payment methods, card brands, currencies, merchant countries, reconciliation and dispute support. No credentials.
• list_fees: List fee entries that model gateway or settlement costs: buy or sell side, filter rule, fixed amount or basis points and settlement currency.
• list_webhooks: List webhook endpoints with event filter, status, HTTP method and URL. Custom headers, body templates and credentials are not returned.
• list_websites: List websites (storefronts) of the organization with name, URL and creation time. Contact details are not returned.
• list_gateway_accounts: List gateway accounts (your merchant accounts at payment gateways) with gateway, method, accepted currencies, card schemes, status, 3-D Secure flag and monthly limit. Credentials are not returned.
• list_journal_accounts: List the revenue accounting journal accounts (for example unearned revenue) with name and description.
• get_risk_score_rules: Show the risk scoring rules: points added for proxy, VPN, Tor or hosting traffic, mismatched countries and velocity brackets.

BYOK key

You bring your own Rebilly Rebilly secret API key (https://www.rebilly.com/docs/dev-docs/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.rebilly.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://www.rebilly.com/catalog/all/ (the API this connector calls, with a BYOK key)

Live from the Rebilly API (api.rebilly.com) with a BYOK key; documentation: https://www.rebilly.com/catalog/all/. 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 Rebilly. Rebilly 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 Rebilly account.

Built for: Worldwide. Languages: English.

Rebilly (BYOK) — Privacy Policy

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

What Rebilly (BYOK) is. Rebilly (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Rebilly data: Read the setup of your Rebilly account (shipping rates, payment method and gateway catalogs, fees, webhooks, websites, gateway accounts, journal accounts and risk rules) with your own secret API key. You bring your own Rebilly Rebilly secret API key; the assistant sends it to us with each request.

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

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

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

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

Rebilly (BYOK) — Terms of Service

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

1. The Service. Rebilly (BYOK) provides: Read the setup of your Rebilly account (shipping rates, payment method and gateway catalogs, fees, webhooks, websites, gateway accounts, journal accounts and risk rules) 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 Rebilly credentials and only access data you are allowed to access. Rebilly's terms apply to your use of Rebilly; 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 Rebilly. Rebilly 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 Rebilly returns, lightly trimmed; it may be incomplete, delayed or changed by Rebilly. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Rebilly 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 Rebilly'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; Rebilly 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 Rebilly 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 Rebilly 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-rebilly-config

Rebilly (BYOK) support

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

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