# How to connect Just One API to Hermes Agent (paste one key, 279 tools) > Connect Just One API to Hermes with ClawLink: paste your Just One API key once and 279 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/just-one-api Most guides for giving Hermes Agent Just One API access start with registering your own OAuth app or pasting API keys into env files, then leave the token refresh and tool wiring to you. ClawLink gives Hermes a more practical Just One API setup: pair once in the browser and your always-on Hermes agent can act on Just One API for you, reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself. ## Setup It takes three steps to connect Hermes to Just One API. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Just One API** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask Hermes Agent in plain English. **Paste this into Hermes to set up ClawLink:** > Set up ClawLink for Hermes and tell me when it's ready. > 1. Install the plugin: `hermes plugins install ClawLink-HQ/hermes-plugin --enable` > 2. Start pairing with `hermes clawlink begin`. It prints an approval link, so show me the link and stop, don't wait. > 3. I'll approve it in my browser, then reply "approved". > 4. When I say approved, finish setup: `hermes clawlink finish` > 5. Then run `hermes clawlink test` and tell me whether ClawLink is ready. **Alternative for any agent (no plugin needed):** if the Hermes Agent 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 just-one-api # connect Just One API (browser OAuth) npx -y @useclawlink/cli actions just-one-api # list available actions npx -y @useclawlink/cli run just-one-api --input '' # execute (add --confirm for writes) ``` ### Install by command The prompt above walks Hermes through this. By hand, it is four commands and a browser approval: ```bash hermes plugins install ClawLink-HQ/hermes-plugin --enable hermes clawlink begin # prints an approval link — open it and approve hermes clawlink finish # after approving in the browser hermes clawlink test ``` Then connect Just One API in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Just One API API key once. Verify the connection by asking Hermes: > Use Just One API to 1688 get item detail and walk me through the result in plain English. ### Using a different agent? The Hermes 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 Just One API is connected in the dashboard, that agent calls the same 279 Just One API 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). ## Just One API MCP for Hermes Looking for a Just One API MCP server for Hermes Agent? ClawLink connects Just One API to Hermes Agent and exposes 279 Just One API 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 OpenClaw instead? The [OpenClaw Just One API integration](https://claw-link.dev/openclaw/just-one-api) works the same way. ## What the Hermes Agent Just One API integration can do 279 Just One API tools are ready for Hermes Agent once the account is connected. The 30 below are the ones people reach for most; your agent can call all 279. ### 30 of 279 Just One API tools for Hermes | Tool | What it does | |---|---| | **1688 get item detail** `just_one_api_1688_get_item_detail` | Retrieves the public product detail for a 1688 wholesale listing by item ID | | **1688 search item list** `just_one_api_1688_search_item_list` | Searches 1688 wholesale product listings by keyword | | **Aliexpress get product detail** `just_one_api_aliexpress_get_product_detail` | Retrieves an AliExpress product by item ID with optional currency, region, and locale controls | | **Aliexpress search products** `just_one_api_aliexpress_search_products` | Searches AliExpress products with optional query, page, sort, category, brand, location | | **Amazon get best sellers** `just_one_api_amazon_get_best_sellers` | Retrieves paginated Amazon Best Sellers for a category path in a selected country marketplace | | **Amazon get category products** `just_one_api_amazon_get_category_products` | Retrieves paginated Amazon products for a numeric category node in a selected country | | **Amazon get product detail** `just_one_api_amazon_get_product_detail` | Retrieves details for an Amazon product identified by ASIN in a selected country marketplace | | **Amazon get product top reviews** `just_one_api_amazon_get_product_top_reviews` | Retrieves the top reviews for an Amazon product identified by ASIN in a selected country | | **Amazon search products** `just_one_api_amazon_search_products` | Searches Amazon marketplace products by keyword or ASIN with country, sort, condition | | **Bilibili get user detail** `just_one_api_bilibili_get_user_detail` | Retrieves a Bilibili user profile identified by UID | | **Bilibili get user relation stat** `just_one_api_bilibili_get_user_relation_stat` | Retrieves relation statistics for a Bilibili user identified by WMID | | **Bilibili get user video list** `just_one_api_bilibili_get_user_video_list` | Retrieves videos published by a Bilibili user identified by UID, with an optional continuation | | **Bilibili get video caption** `just_one_api_bilibili_get_video_caption` | Retrieves caption data for a Bilibili video segment identified by BVID, AID, and CID | | **Bilibili get video comment** `just_one_api_bilibili_get_video_comment` | Retrieves comments for a Bilibili video identified by AID, with optional cursor pagination | | **Bilibili get video danmu** `just_one_api_bilibili_get_video_danmu` | Retrieves one page of danmaku comments for a Bilibili video segment identified by AID and CID | | **Bilibili get video detail** `just_one_api_bilibili_get_video_detail` | Retrieves details for a Bilibili video identified by its BVID | | **Bilibili search video** `just_one_api_bilibili_search_video` | Searches Bilibili videos by keyword with page-based pagination and sorting by general ranking | | **Bilibili share URL transfer** `just_one_api_bilibili_share_url_transfer` | Resolve a supported Bilibili short share link that targets a video and return its public | | **Cross platform search** `just_one_api_cross_platform_search` | Searches cached recent content across news, Weibo, WeChat, Zhihu, Douyin, Xiaohongshu | | **Douban get movie comments** `just_one_api_douban_get_movie_comments` | Retrieves paginated Douban short comments for a movie or TV subject, ordered by time or newest | | **Douban get movie review detail** `just_one_api_douban_get_movie_review_detail` | Retrieves a single Douban long-form review by its review ID | | **Douban get movie reviews** `just_one_api_douban_get_movie_reviews` | Retrieves paginated Douban long-form reviews for a movie or TV subject, ordered by time or | | **Douban get recent hot movie** `just_one_api_douban_get_recent_hot_movie` | Retrieves a paginated list of movies currently featured in Douban's recent-hot collection | | **Douban get recent hot tv** `just_one_api_douban_get_recent_hot_tv` | Retrieves a paginated list of TV titles currently featured in Douban's recent-hot collection | | **Douban get subject detail** `just_one_api_douban_get_subject_detail` | Retrieves the public detail page data for a Douban movie or TV subject by subject ID | | **Douyin ec get item comments** `just_one_api_douyin_ec_get_item_comments` | Retrieves paginated customer comments for a Douyin E-commerce product by item ID | | **Douyin ec get item detail** `just_one_api_douyin_ec_get_item_detail` | Retrieves Douyin E-commerce product details, including sales data, by item ID | | **Douyin ec get item sku info** `just_one_api_douyin_ec_get_item_sku_info` | Retrieves SKU information for a Douyin E-commerce product by item ID | | **Douyin ec get shop item list** `just_one_api_douyin_ec_get_shop_item_list` | Retrieves a paginated product list for a Douyin E-commerce shop by shop ID | | **Douyin ec search item list** `just_one_api_douyin_ec_search_item_list` | Searches Douyin E-commerce products by keyword with page and search-ID pagination | ## Example prompts **1688 Get Item Detail** > Use Just One API to 1688 get item detail and walk me through the result in plain English. **1688 Search Item List** > Search Just One API for what I need, summarize the results, and tell me the next best action. **Aliexpress Get Product Detail** > Use Just One API to aliexpress get product detail and walk me through the result in plain English. **Aliexpress Search Products** > Search Just One API for what I need, summarize the results, and tell me the next best action. ## 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 Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want Just One API working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Just One API API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Just One API 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 Just One API. | 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 Just One API actions to the runtime in a format your agent can reliably use. | 279 tools for Just One API are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Just One API 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 Hermes Agent users instead. You install the plugin once, connect Just One API in the browser, and the 279 tools above work from chat. There is no SDK and no config file, and the Just One API 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. ### Hermes paired but still can't use Just One API Pairing is a two-step handshake: run `hermes clawlink begin`, approve the link in your browser, then run `hermes clawlink finish`. If you ran finish before approving, or the approval link expired, run `hermes clawlink begin` again to get a fresh link. Confirm the plugin was installed with `--enable`, then verify with `hermes clawlink test`. ### Connection succeeds but no tools appear Reconnect Just One API 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 Just One API tools Just One API 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 Just One API 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. ### Just One API 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 Just One API has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a Hermes Agent Just One API integration? Yes. ClawLink is the fastest way to connect Hermes to Just One API: link your Just One API account once in the browser and Hermes Agent can call the Just One API API through 279 ready-made tools — no custom code or token handling. ### How do I connect Just One API to Hermes with ClawLink? Install the plugin with `hermes plugins install ClawLink-HQ/hermes-plugin --enable`, then pair once: run `hermes clawlink begin`, approve the link in your browser, and run `hermes clawlink finish`. Connect Just One API in the dashboard and Hermes can use it from the next message — no config files, and the Just One API key you paste is stored server-side instead of in your environment. ### How long does it take to connect Just One API to Hermes Agent? About two minutes. Sign in, click Connect next to Just One API in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring Just One API up myself? The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want Just One API working from chat. ### Hermes paired but still can't use Just One API Pairing is a two-step handshake: run `hermes clawlink begin`, approve the link in your browser, then run `hermes clawlink finish`. If you ran finish before approving, or the approval link expired, run `hermes clawlink begin` again to get a fresh link. Confirm the plugin was installed with `--enable`, then verify with `hermes clawlink test`. ## Related - [DataRobot tools](https://claw-link.dev/hermes/datarobot) — DataRobot is a machine learning platform that automates model building, deployment, and monitoring, enabling organizations to derive predictive insights from large datasets. - [Chatbotkit](https://claw-link.dev/hermes/chatbotkit) — ChatBotKit is a platform that enables developers to build and manage AI-powered chatbots, offering comprehensive APIs and SDKs for seamless integration into applications. - [Connect OpenWeb Ninja](https://claw-link.dev/hermes/openweb-ninja) — OpenWeb Ninja provides native APIs for web search, AI answers, e-commerce, finance, jobs, maps, news, real estate, contact enrichment, traffic, and web scraping.