# Connect Loyverse to Hermes Agent Prepare a grounded POS sales briefing

> Read receipts with Hermes Agent and Agent200. Prepare a POS sales briefing using the connected user’s own Loyverse account.

- Page: https://www.agent200.com/connectors/loyverse/framework/hermes-agent/
- Connector: [Loyverse](https://www.agent200.com/connectors/loyverse.md)
- Framework: Hermes Agent
- Updated: 2026-11-17

## Instructions for AI agents

Goal: connect Loyverse to Hermes Agent with Agent200, through its MCP server.
Guide: https://www.agent200.com/connectors/loyverse/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 Loyverse 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. The first Loyverse request returns an authorization link if the user has not connected Loyverse yet: show it to them and continue once they have approved access on Loyverse's own page.
5. Check it works with this request: "Read the Loyverse receipt I identify and prepare a POS sales briefing. Name the source and use only receipt, item, customer and amount fields. State access gaps; do not change records."
   What should come back:
   - The selected receipt is identified.
   - Only the returned receipt, item, customer and amount fields are reported.
   - Access gaps and missing context are explicit; no source data is changed.
6. If a tool is missing or a call is refused, check the project's Connectors settings in the dashboard and the access the user granted in Loyverse, then retry.

## Overview

Inspect the Agent200 tools Hermes advertises after connection. Use discovered names and input schemas for the receipt read, not guesses from catalogue labels.

Start with one identified receipt. Preserve returned receipt, item, customer and amount fields; report missing data and keep the workflow read-only.

Provider reference: [Loyverse API](https://developer.loyverse.com/docs/).

- **Connector:** [Loyverse](https://www.agent200.com/connectors/loyverse/)
- **Works with:** Hermes Agent · Agent app, through MCP
- **Authentication:** Managed OAuth, per end user
- **You need:** [An Agent200 API key](https://agent200.com/platform/apikeys/)
- **Tools:** [5 tools](https://www.agent200.com/connectors/loyverse/framework/hermes-agent/#tools)
- **MCP server:** `https://api.agent200.com/mcp/`

## Before you start

- **An Agent200 API key.** Create one on the [API keys page](https://agent200.com/platform/apikeys/) of the dashboard.
- **Loyverse enabled for your project.** In the dashboard's Connectors settings, with the endpoints and scopes your agent needs.
- **An end user with a Loyverse account.** They approve access once, on Loyverse's own page.
- **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 Loyverse to Hermes Agent

### 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 Loyverse and every other connector enabled for your project. Keep it out of chats and source control.

Create an API key: https://agent200.com/platform/apikeys/

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

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

File `~/.hermes/.env`:

```bash
AGENT200_API_KEY=your-agent200-api-key
```

### 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.

File `~/.hermes/config.yaml`:

```text
mcp_servers:
  agent200:
    url: "https://api.agent200.com/mcp/"
    headers:
      Authorization: "Bearer ${AGENT200_API_KEY}"
```

### Step 4: Reload and test

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

File `Terminal`:

```bash
# In a running Hermes session: /reload-mcp
hermes mcp test agent200
hermes mcp list
```

### Step 5: Connect your Loyverse account

The first time you ask Hermes Agent for something in Loyverse, Agent200 returns an authorization link. Open it and approve access on Loyverse's own page. Agent200 stores the connection and keeps it working; your password never reaches Hermes Agent or Agent200.

## Test your connection

Ask: "Read the Loyverse receipt I identify and prepare a POS sales briefing. Name the source and use only receipt, item, customer and amount fields. State access gaps; do not change records."

What should come back:

- The selected receipt is identified.
- Only the returned receipt, item, customer and amount fields are reported.
- Access gaps and missing context are explicit; no source data is changed.

Check the selected receipt ID, account scope, read permission and pagination. Receipt totals and customer records are sensitive. Account for refunds, store scope and pagination; do not treat receipts as settled payouts.

## Loyverse tools Hermes Agent can call

- **List receipts** (`loyverse_list_receipts`, read): Find receipts in a selected store and time window.
- **Read a receipt** (`loyverse_get_receipt`, read): Retrieve one receipt by ID.
- **List items** (`loyverse_list_items`, read): Find catalog items available to the connection.
- **Read an item** (`loyverse_get_item`, read): Retrieve one identified catalog item.
- **List customers** (`loyverse_list_customers`, read): Find customer records in authorized scope.

## How it works

1. **You ask Hermes Agent.** In your own words, for something in Loyverse.
2. **Hermes Agent picks a tool.** It sees the Loyverse tools on the Agent200 MCP server and calls the one the request needs.
3. **Agent200 runs the call.** With your own Loyverse connection, within the tools and scopes your project allows.
4. **Hermes Agent answers.** It gets the result back from the MCP server and uses it in its reply or its next step.

**Each user's own connection.** Connections belong to individual end users. A request for one user never reaches another user's Loyverse account.

**Permissions at every level.** Your project settings decide what the agent may request, the end user decides what they authorize, and Loyverse enforces what its API grants.

## Troubleshooting

### The source cannot be read

Check the selected receipt ID, account scope, read permission and pagination. Receipt totals and customer records are sensitive. Account for refunds, store scope and pagination; do not treat receipts as settled payouts.

## FAQ

### How do I verify this result?

Compare the named receipt and returned receipt, item, customer and amount fields with the source. Treat missing information as missing, not as a fact.

## Use Loyverse with another framework

- [Loyverse + Claude](https://www.agent200.com/connectors/loyverse/framework/claude.md)
- [Loyverse + ChatGPT](https://www.agent200.com/connectors/loyverse/framework/chatgpt.md)
- [Loyverse + Claude Code](https://www.agent200.com/connectors/loyverse/framework/claude-code.md)
- [Loyverse + Muse](https://www.agent200.com/connectors/loyverse/framework/muse.md)
- [Loyverse + Grok Bot](https://www.agent200.com/connectors/loyverse/framework/grok-bot.md)
- [Loyverse + OpenAI Dots](https://www.agent200.com/connectors/loyverse/framework/openai-dots.md)
- [Loyverse + Claude Duet](https://www.agent200.com/connectors/loyverse/framework/claude-duet.md)
- [Loyverse + OpenClaw](https://www.agent200.com/connectors/loyverse/framework/openclaw.md)

---

Agent200: https://www.agent200.com/ · API keys: https://agent200.com/platform/apikeys/ · Docs: https://docs.igpt.ai/
