Just One API + Hermes Agent

How to connect Just One API to Hermes Agent

Set up Just One API for Hermes Agent with Agent200, then check which tools are available to your agent.

On this page
  1. Overview
  2. Before you start
  3. Setup steps
  4. Test your connection
  5. Instructions for AI agents
  6. Just One API tools
  7. How it works
  8. Troubleshooting

Overview

This guide connects Just One API to Hermes Agent through Agent200's MCP server. When you finish, Hermes Agent can search, read and act in Just One API with the tools Agent200 provides, whenever a request needs them.

You add one MCP server to Hermes Agent with your Agent200 API key. Just One API is reached with that key, so there is no separate Just One API key to manage.

Connector
Just One API
Works with
Hermes Agent ยท Agent app, through MCP
Authentication
Your Agent200 API key
Tools
5 tools
MCP server
https://api.agent200.com/mcp/

Before you start

  • An Agent200 API key. Create one on the API keys page of the dashboard.
  • Just One API enabled for your project. In the dashboard's Connectors settings, with the endpoints and scopes your agent needs.
  • Hermes Agent, with custom MCP servers allowed. Hermes Agent is open source and self-hosted: anyone running it can add MCP servers in its config file.

Connect Just One API to Hermes Agent

  1. 1

    Step 1: Create your Agent200 API key

    Open the API keys page in the Agent200 dashboard and choose Create an API key. You add it to Hermes Agent in the next step, as "Authorization: Bearer <your key>". One key covers Just One API and every other connector enabled for your project. Keep it out of chats and source control.

  2. 2

    Step 2: Store your key in ~/.hermes/.env

    Keep the key out of config.yaml: Hermes reads it from ~/.hermes/.env.

    ~/.hermes/.env
    MCP: Hermes Agent key in ~/.hermes/.env
    AGENT200_API_KEY=your-agent200-api-key
  3. 3

    Step 3: Add the server to ~/.hermes/config.yaml

    Add an entry under mcp_servers with the URL and the Authorization header. Do not set transport: sse: Agent200 serves streamable HTTP.

    ~/.hermes/config.yaml
    MCP: Hermes Agent config.yaml entry
    mcp_servers:
      agent200:
        url: "https://api.agent200.com/mcp/"
        headers:
          Authorization: "Bearer ${AGENT200_API_KEY}"
  4. 4

    Step 4: Reload and test

    In a running session, run /reload-mcp, or restart Hermes. Then check what the server returned from a terminal.

    Terminal
    MCP: Hermes Agent reload and test
    # In a running Hermes session: /reload-mcp
    hermes mcp test agent200
    hermes mcp list

Test your connection

Run one request to check everything is wired up.

Ask

Ask Hermes Agent to list the Agent200 tools available for Just One API, including which are read-only.

What should come back

  • A list of the Just One API tools enabled for this Agent200 project, with their names and descriptions. If no tools appear, check that the connector is available to the project and its tools are enabled.

If no tools appear, check your Agent200 project access for Just One API and make sure its tools are enabled. Tool availability depends on your project setup.

Get your API key

Create a key in the Agent200 dashboard. It reaches Just One API and every other connector enabled for your project.

Read the SDK docs

Instructions for AI agents

Using a coding agent? Paste this brief into it, or give it the address of this page. It lists what to do, in order, to connect Just One API to Hermes Agent.

Agent brief
Goal: connect Just One API to Hermes Agent with Agent200, through its MCP server.
Guide: https://www.agent200.com/connectors/just-one-api/framework/hermes-agent/

1. The user needs an Agent200 API key. If they have none, send them to https://agent200.com/platform/apikeys/ to choose "Create an API key". They paste it into Hermes Agent's settings themselves: never ask for it in chat and never write it into files you share.
2. Make sure Just One API is enabled for their project in the Agent200 dashboard (Connectors), with the tools the task needs.
3. Add Agent200's MCP server to Hermes Agent: URL https://api.agent200.com/mcp/, transport streamable HTTP, header "Authorization: Bearer <the user's Agent200 API key>". Follow the setup steps on the guide page for Hermes Agent's exact menus or commands.
4. Check it works with this request: "Ask Hermes Agent to list the Agent200 tools available for Just One API, including which are read-only."
   What should come back:
   - A list of the Just One API tools enabled for this Agent200 project, with their names and descriptions. If no tools appear, check that the connector is available to the project and its tools are enabled.
5. If a tool is missing or a call is refused, check the project's Connectors settings in the dashboard, then retry.

The whole guide is also available as Markdown, for agents and LLMs: /connectors/just-one-api/framework/hermes-agent.md

Just One API tools Hermes Agent can call

  • Search posts

    Read
    justoneapi_search_posts

    Search public posts on a supported platform by keyword.

  • Get a post

    Read
    justoneapi_get_post

    Get a public post's details and engagement.

  • List comments

    Read
    justoneapi_list_comments

    List the public comments on a post.

  • Get a profile

    Read
    justoneapi_get_profile

    Get a public creator profile and its stats.

  • Get a product

    Read
    justoneapi_get_product

    Get the public details of a product listing.

How it works

  1. 01

    You ask Hermes Agent

    In your own words, for something in Just One API.

  2. 02

    Hermes Agent picks a tool

    It sees the Just One API tools on the Agent200 MCP server and calls the one the request needs.

  3. 03

    Agent200 runs the call

    It reaches Just One API with your Agent200 API key, within the endpoints your project allows.

  4. 04

    Hermes Agent answers

    It gets the result back from the MCP server and uses it in its reply or its next step.

Permissions at every level. Your project settings decide which services and endpoints the agent may use.

Troubleshooting

The connection fails and names a missing variable

Add AGENT200_API_KEY to ~/.hermes/.env and run /reload-mcp.

The server answers 401 or 403

Check the key in ~/.hermes/.env and that the header reads exactly Bearer ${AGENT200_API_KEY}.

The initialize request fails with 400 or 405

That points to an SSE setting. Remove any transport: sse line from the entry and check the URL is exactly the Agent200 MCP server address.

The Just One API tools do not appear

Run hermes mcp test agent200, check the entry is not disabled and no tools filter hides them, then /reload-mcp. Hermes names them mcp_agent200_....

A tool call is refused or returns less than expected

Agent200 runs only what your project allows. Check that Just One API and the tools you need are enabled in the dashboard's Connectors settings.

The API key was pasted into a chat or committed

Create a new key on the API keys page, replace it in Hermes Agent's MCP settings, and stop using the old one. Paste the key only into Hermes Agent's settings, never into a chat.

Use Just One API with another framework

200 OK

Just One API, connected to Hermes Agent.
One SDK. One API key.

Agent200 handles the OAuth, the tokens and every tool call. You keep your agent, your model and your code.

Book a demo.
See it in action.

Tell us who you are, then pick a time for a 1:1 session with an expert from our team.

We use your details only to email you about Agent200. See the Privacy Policy.

Pick a time. We'll take it from there.

A 1:1 session with an expert from our team, about what you are building.

Open in Calendly (opens in a new tab)