Apicbase Suppliers and Purchase Orders (BYOK)
Read an Apicbase library's suppliers, purchase orders, order approvals, supplier deliveries and incoming orders between outlets with your own API token
Read your Lenco business bank accounts in Zambia and Nigeria: accounts, balances, transactions by id or reference, and the bank list with your own API token
Unify Dynamics LLC
Real questions, and the tools your agent calls to answer them.
list_accountsget_accountget_account_balancelist_transactionsget_transactionget_transaction_by_referenceLenco (BYOK) lets an AI assistant read your own Lenco data through the Lenco API with a key you supply (Lenco API token (the token can also move money; this connector only reads)). Read-only: 7 tools (list_accounts, get_account, get_account_balance, list_transactions, get_transaction, get_transaction_by_reference, list_banks). 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.lenco.co. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Lenco. Lenco and its logos are trademarks of their owners and are used only to say which service the connector works with.
Sources: Live from the Lenco API (api.lenco.co) with a BYOK key; documentation: https://lenco-api.readme.io/reference/introduction. 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.
7 tools, grouped by job. Every one is read-only or compute-only.
https://byok-lenco.connectorbay.com/mcpThree ways in, the same 7 tools.
https://byok-lenco.connectorbay.com/mcpPOST https://byok-lenco.connectorbay.com/v1/tools/<tool>https://connectorbay.com/openai/byok-lenco.jsonhttps://connectorbay.com/v1/chat/completions · how it worksX-Upstream-Key header (get one at lenco-api.readme.io).Lenco (BYOK) lets an AI assistant read your own Lenco data through the Lenco API with a key you supply (Lenco API token (the token can also move… It is a hosted MCP server with 7 tools such as List accounts, Get account, Get account balance, List transactions, Get transaction, Get transaction by reference, published by Unify Dynamics LLC. It is independent and not affiliated with Lenco.
Add the MCP endpoint https://byok-lenco.connectorbay.com/mcp to your client's MCP, connector or integration settings (streamable HTTP, no OAuth). For REST, POST JSON to https://byok-lenco.connectorbay.com/v1/tools/<tool>; the OpenAPI description is at /openapi.json. For OpenAI function calling, load https://connectorbay.com/openai/byok-lenco.json.
Yes: this is a bring-your-own-key connector. Create a Lenco API token (the token can also move money; this connector only reads) at https://lenco-api.readme.io/reference/get-started 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 an Apicbase library's suppliers, purchase orders, order approvals, supplier deliveries and incoming orders between outlets with your own API token
Read your Apphud subscription analytics: chart catalog, time series, column reports and dashboard widgets, with your own S2S key
Read your Asaas charges, customers, subscriptions, balance and statement (read-only) with your own API key
Decode VINs and read vehicle listings, specifications, recalls, photos, interest rates and cost of ownership with your own Auto.dev key
Read your Autumn billing customers, subscriptions, invoices, plans, features, usage events and balances with your own secret key
Read Avalanche C-Chain and L1 blocks, transactions, token balances and transfers from the AvaCloud Data API (formerly Glacier) with your own API key
https://byok-lenco.connectorbay.com/mcpPOST https://byok-lenco.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-lenco.connectorbay.com/openapi.jsonX-Upstream-Key header of every request (never stored, logged or cached)https://byok-lenco.connectorbay.com/health · Tool schemas: https://byok-lenco.connectorbay.com/tools.jsonLenco (BYOK) lets an AI assistant read your own Lenco data through the Lenco API with a key you supply (Lenco API token (the token can also move money; this connector only reads)). Read-only: 7 tools (list_accounts, get_account, get_account_balance, list_transactions, get_transaction, get_transaction_by_reference, list_banks). 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.lenco.co. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Lenco. Lenco 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_accounts: List your Lenco bank accounts with name, type, status, currency, available and current balance. Account numbers are not returned.get_account: Get one Lenco account by id: name, type, status, currency and balances.get_account_balance: Get the available and current balance of one Lenco account.list_transactions: List transactions on your Lenco accounts (credits and debits) with status, amount, fee, narration and times, filtered by status, type, dates or search text. The counterparty details of each transaction are included as returned.get_transaction: Get one Lenco transaction by id: type, status, amount, fee, narration, times, your client reference and failure reason.get_transaction_by_reference: Find a Lenco transaction by the client reference your system supplied when creating it.list_banks: List the banks and financial institutions Lenco supports, with their codes.You bring your own Lenco Lenco API token (the token can also move money; this connector only reads) (https://lenco-api.readme.io/reference/get-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 api.lenco.co 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 Lenco API (api.lenco.co) with a BYOK key; documentation: https://lenco-api.readme.io/reference/introduction. Endpoints checked against that documentation on 2026-10-16.
Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Lenco. Lenco 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 Lenco account.
Built for: Worldwide. Languages: English.
Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.
What Lenco (BYOK) is. Lenco (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Lenco data: Read your Lenco business bank accounts in Zambia and Nigeria: accounts, balances, transactions by id or reference, and the bank list with your own API token. You bring your own Lenco Lenco API token (the token can also move money; this connector only reads); the assistant sends it to us with each request.
BYOK key. The key you supply is used to make the one Lenco 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.lenco.co, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Lenco 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 Lenco receives. The request we make on your behalf, including the key and the arguments, under Lenco's own terms and privacy policy. Lenco acts at your direction and is the only recipient of the data of your request besides our hosting provider.
What we return. The answer Lenco 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 Lenco 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. Lenco (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 Lenco at any time to end all access.
Children. Lenco (BYOK) is a general-audience service operated by the adult using the assistant, under Lenco'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 Lenco (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").
Email agent@connectorbay.com. We answer within two business days.
https://byok-lenco.connectorbay.com/mcphttps://byok-lenco.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. Lenco (BYOK) never asks for them.