Zuper (BYOK)
Read your Zuper field service data: jobs, projects, customers (names only), assets, organizations and job categories with your own API key
Read Bible translations, books, chapters, verses and passages and search scripture text across hundreds of versions with your own API.Bible key
Unify Dynamics LLC
Real questions, and the tools your agent calls to answer them.
list_biblesget_biblelist_booksget_booklist_chaptersget_chapterAPI Bible (BYOK) lets an AI assistant read your own API Bible data through the API Bible API with a key you supply (API.Bible API key). Read-only: 10 tools (list_bibles, get_bible, list_books, get_book, list_chapters, get_chapter, list_verses, get_verse, get_passage, search_bible). 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 rest.api.bible. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by API Bible. API Bible and its logos are trademarks of their owners and are used only to say which service the connector works with.
Sources: Live from the API Bible API (rest.api.bible) with a BYOK key; documentation: https://docs.api.bible/. 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.
10 tools, grouped by job. Every one is read-only or compute-only.
https://byok-apibible.connectorbay.com/mcpThree ways in, the same 10 tools.
https://byok-apibible.connectorbay.com/mcpPOST https://byok-apibible.connectorbay.com/v1/tools/<tool>https://connectorbay.com/openai/byok-apibible.jsonhttps://connectorbay.com/v1/chat/completions · how it worksX-Upstream-Key header (get one at docs.api.bible).API Bible (BYOK) lets an AI assistant read your own API Bible data through the API Bible API with a key you supply (API.Bible API key). It is a hosted MCP server with 10 tools such as List bibles, Get bible, List books, Get book, List chapters, Get chapter, published by Unify Dynamics LLC. It is independent and not affiliated with API Bible.
Add the MCP endpoint https://byok-apibible.connectorbay.com/mcp to your client's MCP, connector or integration settings (streamable HTTP, no OAuth). For REST, POST JSON to https://byok-apibible.connectorbay.com/v1/tools/<tool>; the OpenAPI description is at /openapi.json. For OpenAI function calling, load https://connectorbay.com/openai/byok-apibible.json.
Yes: this is a bring-your-own-key connector. Create a API.Bible API key at https://docs.api.bible/quick-start/authentication 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 Zuper field service data: jobs, projects, customers (names only), assets, organizations and job categories with your own API key
Read your Zuper appointments, recurring jobs, service tasks, job photo folders and measurements (no customer or staff details) with your own API key
Read your Zuper service setup: service territories, teams, request statuses and workflow automation rules with your own API key
Check IP addresses for abuse reports, read report details, network blocks and the blacklist with BYOK
Read your Accelevents virtual and hybrid event data: attendees, ticket sales, sessions and speakers with your own organizer API key
Read your AccuLynx roofing and construction jobs, milestones, invoices, payments, appointments, users and company settings with your own API key
https://byok-apibible.connectorbay.com/mcpPOST https://byok-apibible.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-apibible.connectorbay.com/openapi.jsonX-Upstream-Key header of every request (never stored, logged or cached)https://byok-apibible.connectorbay.com/health · Tool schemas: https://byok-apibible.connectorbay.com/tools.jsonAPI Bible (BYOK) lets an AI assistant read your own API Bible data through the API Bible API with a key you supply (API.Bible API key). Read-only: 10 tools (list_bibles, get_bible, list_books, get_book, list_chapters, get_chapter, list_verses, get_verse, get_passage, search_bible). 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 rest.api.bible. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by API Bible. API Bible 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_bibles: List the Bible versions your key can read (public-domain and Creative Commons ones, plus any licensed to your plan), with language and abbreviation.get_bible: Get one Bible version: names, language, countries, description and copyright.list_books: List the books of a Bible version with their ids (for example GEN, JHN), optionally with chapter ids.get_book: Get one book of a Bible version by book id such as 'GEN' or 'JHN'.list_chapters: List the chapters of one book with their ids (for example JHN.3).get_chapter: Read a whole chapter's text by chapter id such as 'JHN.3'.list_verses: List the verse ids and references of one chapter (no text; use get_verse or get_passage for text).get_verse: Read one verse by verse id such as 'JHN.3.16'.get_passage: Read a range of verses (up to 200) by passage id: two verse ids joined by a hyphen, for example 'JHN.3.1-JHN.3.16'.search_bible: Search one Bible version for verses containing all given keywords (wildcards * and ? allowed) or matching a reference.You bring your own API Bible API.Bible API key (https://docs.api.bible/quick-start/authentication). 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 rest.api.bible 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 API Bible API (rest.api.bible) with a BYOK key; documentation: https://docs.api.bible/. Endpoints checked against that documentation on 2026-10-16.
Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by API Bible. API Bible 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 API Bible account.
Built for: Worldwide. Languages: English.
Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.
What API Bible (BYOK) is. API Bible (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own API Bible data: Read Bible translations, books, chapters, verses and passages and search scripture text across hundreds of versions with your own API.Bible key. You bring your own API Bible API.Bible API key; the assistant sends it to us with each request.
BYOK key. The key you supply is used to make the one API Bible 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 rest.api.bible, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If API Bible 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 API Bible receives. The request we make on your behalf, including the key and the arguments, under API Bible's own terms and privacy policy. API Bible acts at your direction and is the only recipient of the data of your request besides our hosting provider.
What we return. The answer API Bible 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 API Bible 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. API Bible (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 API Bible at any time to end all access.
Children. API Bible (BYOK) is a general-audience service operated by the adult using the assistant, under API Bible'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 API Bible (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").
Email agent@connectorbay.com. We answer within two business days.
https://byok-apibible.connectorbay.com/mcphttps://byok-apibible.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. API Bible (BYOK) never asks for them.