# How to connect API.Bible to OpenClaw (paste one key, 19 tools) > Connect API.Bible to OpenClaw with ClawLink: paste your API.Bible key once and 19 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/api-bible The usual route to API.Bible access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical API.Bible setup: install one ClawHub skill, connect API.Bible in the browser, and OpenClaw can call real API.Bible actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. ## Setup It takes three steps to connect OpenClaw to API.Bible. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect API.Bible** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Paste this into OpenClaw to set up ClawLink:** > I want to connect my apps to OpenClaw through ClawLink. > Please install the ClawLink plugin from ClawHub and enable it: `openclaw plugins install clawhub:clawlink-plugin` > When it is installed, tell me and stop. After I reply, give me the ClawLink pairing link. Setup notes, if you need them: https://claw-link.dev/skill.md **Alternative for any agent (no plugin needed):** if the OpenClaw plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect api-bible # connect API.Bible (browser OAuth) npx -y @useclawlink/cli actions api-bible # list available actions npx -y @useclawlink/cli run api-bible --input '' # execute (add --confirm for writes) ``` ### Install by command The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval: ```bash openclaw plugins install clawhub:clawlink-plugin ``` Then ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say `done`. Finally, connect API.Bible in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your API.Bible API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from API.Bible, summarize it in plain English, and point out anything that needs attention. ### Using a different agent? The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once API.Bible is connected in the dashboard, that agent calls the same 19 API.Bible tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## API.Bible MCP for OpenClaw Looking for a API.Bible MCP server for OpenClaw? ClawLink connects API.Bible to OpenClaw and exposes 19 API.Bible tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using Hermes instead? The [Hermes API.Bible integration](https://claw-link.dev/hermes/api-bible) works the same way. ## What the OpenClaw API.Bible integration can do 19 API.Bible tools are ready for OpenClaw once the account is connected. ### All 19 API.Bible tools for OpenClaw | Tool | What it does | |---|---| | **Get all books** `api_bible_get_all_books` | Retrieve all books for a specific Bible version | | **Get audio bible** `api_bible_get_audio_bible` | Retrieve details of a specific audio Bible by its ID | | **Get audio book** `api_bible_get_audio_book` | Retrieve a single audio Book object for a given audio Bible ID and book ID | | **Get audio chapter** `api_bible_get_audio_chapter` | Retrieve a single audio chapter with mp3 resource URL | | **Get bible** `api_bible_get_bible` | Retrieve details of a specific Bible version by its ID | | **Get book** `api_bible_get_book` | Retrieve a single Book object for a given Bible version and book ID | | **Get chapter** `api_bible_get_chapter` | Retrieve a complete chapter with all verses from a Bible version | | **Get passage** `api_bible_get_passage` | Retrieve a Bible passage by ID | | **Get section** `api_bible_get_section` | Retrieve detailed content for a Bible section by ID | | **Get sections** `api_bible_get_sections` | Retrieve a list of sections for a specific book in a Bible version | | **Get supported versions** `api_bible_get_supported_versions` | Retrieve a list of available Bible versions (translations) from API.Bible | | **Get verse** `api_bible_get_verse` | Retrieve a specific Bible verse by ID | | **List audio bibles** `api_bible_list_audio_bibles` | Retrieve an array of audio Bible objects authorized for the current API Key | | **List audio books** `api_bible_list_audio_books` | Retrieve all books for a specific audio Bible version | | **List audio chapters** `api_bible_list_audio_chapters` | Retrieve a list of audio chapters for a specific book in an audio Bible version | | **List chapter sections** `api_bible_list_chapter_sections` | Retrieve an array of section objects for a specific chapter in a Bible version | | **List chapters** `api_bible_list_chapters` | Retrieve an array of Chapter objects for a given Bible version and book | | **List verses** `api_bible_list_verses` | Retrieve an array of verses for a specific chapter in a Bible version | | **Search verses** `api_bible_search_verses` | Search for Bible verses containing specified keywords or passage references | ## Example prompts **Get All Books** > Pull the relevant data from API.Bible, summarize it in plain English, and point out anything that needs attention. **Get Audio Bible** > Pull the relevant data from API.Bible, summarize it in plain English, and point out anything that needs attention. **Get Audio Book** > Pull the relevant data from API.Bible, summarize it in plain English, and point out anything that needs attention. **Get Audio Chapter** > Pull the relevant data from API.Bible, summarize it in plain English, and point out anything that needs attention. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want API.Bible working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the API.Bible API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected API.Bible account becomes available to the agent without you building credential management. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for API.Bible. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. | | **Agent usability** | You still need to expose the right API.Bible actions to the runtime in a format your agent can reliably use. | 19 tools for API.Bible are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes API.Bible to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect API.Bible in the browser, and the 19 tools above work from chat. There is no SDK and no config file, and the API.Bible key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### OpenClaw installed the API.Bible skill but can't call the tools The ClawHub skill teaches OpenClaw about API.Bible, but the calls run through the ClawLink plugin and your connected account. Make sure API.Bible is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ### Connection succeeds but no tools appear Reconnect API.Bible from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded. ### "Tool schema not loaded yet" error when calling API.Bible tools API.Bible tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every API.Bible call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again. ### API.Bible returns 403 or "permission denied" on one action while others work Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs. ### API key setup works but results look incomplete Double-check that the API key for API.Bible has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw API.Bible integration? Yes. ClawLink is the fastest way to connect OpenClaw to API.Bible: link your API.Bible account once in the browser and OpenClaw can call the API.Bible API through 19 ready-made tools — no custom code or token handling. ### How do I add API.Bible to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink API.Bible skill from ClawHub, then you click Connect in the dashboard to authorize API.Bible. OpenClaw calls the tools from the next message — no config files, and the API.Bible key you paste is stored server-side instead of in your environment. ### How long does it take to connect API.Bible to OpenClaw? About two minutes. Sign in, click Connect next to API.Bible in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring API.Bible up myself? The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want API.Bible working from chat. ### OpenClaw installed the API.Bible skill but can't call the tools The ClawHub skill teaches OpenClaw about API.Bible, but the calls run through the ClawLink plugin and your connected account. Make sure API.Bible is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ## Related - [OpenClaw GitHub integration](https://claw-link.dev/openclaw/github) — Manage repositories, issues, pull requests, and workflows - [PagerDuty](https://claw-link.dev/openclaw/pagerduty) — Manage incidents, on-call schedules, and services - [SafetyCulture](https://claw-link.dev/openclaw/safetyculture) — SafetyCulture (formerly iAuditor) is a workplace operations platform that enables teams to conduct digital inspections, manage audits, track issues, schedule tasks, and maintain compliance through mobile and web applications.