# Loyverse for AI agents. Make the right receipt easier to review.

> Read accessible receipts and related records in Loyverse. Prepare a source-grounded POS sales briefing within the selected account.

- Page: https://www.agent200.com/connectors/loyverse/
- Category: CRM and sales
- Authentication: Managed OAuth
- Identifier in code: `loyverse`
- Create an API key: https://agent200.com/platform/apikeys/
- Updated: 2026-11-18

## Instructions for AI agents

Connector: Loyverse, through Agent200. In code: "loyverse".
What it does: Read accessible receipts and related records in Loyverse. Prepare a source-grounded POS sales briefing within the selected account.
Page: https://www.agent200.com/connectors/loyverse/

1. Get an Agent200 API key. If the developer has none, send them to https://agent200.com/platform/apikeys/ and ask them to choose "Create an API key". Read the key from the AGENT200_API_KEY environment variable. Never ask for it in chat, and never write it into code, prompts or logs.
2. Sign-in is managed OAuth. Each end user approves access once, on Loyverse's own page, through the authorization link Agent200 returns. Never ask a user for a Loyverse password or token in chat.
3. Give every request a stable id for the end user. Agent200 uses only that user's own connection.
4. Read tools: loyverse_list_receipts, loyverse_get_receipt, loyverse_list_items, loyverse_get_item, loyverse_list_customers. Name "loyverse" in the tools of a request; the model decides which tool to call.
5. Stay within the project's settings. If a tool is turned off or a call is refused, tell the user. Do not work around it.
6. Before a write, confirm with the user, unless they asked for that exact change.
7. For setup with a specific framework, follow its guide:
   https://www.agent200.com/connectors/loyverse/framework/claude/
   https://www.agent200.com/connectors/loyverse/framework/chatgpt/
   https://www.agent200.com/connectors/loyverse/framework/claude-code/
   https://www.agent200.com/connectors/loyverse/framework/muse/
   https://www.agent200.com/connectors/loyverse/framework/grok-bot/
   https://www.agent200.com/connectors/loyverse/framework/openai-dots/
   https://www.agent200.com/connectors/loyverse/framework/claude-duet/
   https://www.agent200.com/connectors/loyverse/framework/hermes-agent/
   https://www.agent200.com/connectors/loyverse/framework/openclaw/

The code on the connector page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/

## About

With the Loyverse connector, your agent reads point of sale data in each user's own Loyverse account. It can list and read receipts, list and read items, and list customers, using only the tools your project allows.

Loyverse is a point of sale system for retail shops and restaurants.

## Loyverse tools

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

## Limits you can set

**Turn single tools on or off.** Let the agent read receipts and items, and switch off `loyverse_list_customers` if it should not see customer records.

**Restrict what the agent reaches.** Choose the endpoints and scopes a project may use, for example receipts and items but not customers. A call outside them is refused.

## Get started

### Step 1: Set up the SDK

Add the Agent200 SDK to the codebase you already have and authenticate with your API key. The key covers every connector enabled for the project.

File `agent.js`:

```js
// One Agent200 API key covers every connector enabled for the project.
const agent200 = new Agent200({
  apiKey: process.env.AGENT200_API_KEY,
});
```

(Conceptual example of the Agent200 SDK.)

### Step 2: Let your user connect Loyverse

Each end user authorizes their own Loyverse account once. Agent200 runs the OAuth flow, handles the callback, stores the tokens and refreshes them.

File `connect.js`:

```js
// Each end user authorizes their own Loyverse account, once.
const connection = await agent200
  .user("user_123")
  .connect("loyverse");

if (connection.authorizationUrl) {
  // Show this link to your user; Agent200 handles the rest.
  console.log(connection.authorizationUrl);
}
```

(Conceptual example of the Agent200 SDK.)

### Step 3: Run with the Loyverse tools

Name the user, the model and the tools. The model decides which Loyverse tools to call, and Agent200 executes them with that user's connection.

File `run.js`:

```js
const result = await agent200
  .user("user_123")
  .run({
    model: "openai/gpt-5.6-sol",
    input: "What were yesterday's sales",
    tools: ["loyverse"],
  });

console.log(result.output);
```

(Conceptual example of the Agent200 SDK.)

## Sign-in and permissions

**Connect the intended account.** Use the documented Loyverse authorization route. Confirm the organization, team or workspace before reading records.

**Match access to the request.** Authorize the intended Loyverse account through OAuth with the required read permissions. Select the relevant store before a sales review.

**Preserve the application user.** Keep the same stable application user identity for connection and later requests. Store the Agent200 key outside prompts and code.

## Example requests

- "What were yesterday's sales"
- "Which items sold the most this week"
- "Show the latest receipts from the downtown store"

## Guides: Loyverse with your AI framework

- [Loyverse + Claude](https://www.agent200.com/connectors/loyverse/framework/claude.md): Read receipts with Claude and Agent200. Prepare a POS sales briefing using the connected user’s own Loyverse account.
- [Loyverse + ChatGPT](https://www.agent200.com/connectors/loyverse/framework/chatgpt.md): Use ChatGPT to build a separate read-only Loyverse assistant with Agent200. Ground the POS sales briefing in returned source data.
- [Loyverse + Claude Code](https://www.agent200.com/connectors/loyverse/framework/claude-code.md): Use Claude Code to build a separate read-only Loyverse assistant with Agent200. Ground the POS sales briefing in returned source data.
- [Loyverse + Muse](https://www.agent200.com/connectors/loyverse/framework/muse.md): Read receipts with Muse and Agent200. Prepare a POS sales briefing using the connected user’s own Loyverse account.
- [Loyverse + Grok Bot](https://www.agent200.com/connectors/loyverse/framework/grok-bot.md): Read receipts with Grok Bot and Agent200. Prepare a POS sales briefing using the connected user’s own Loyverse account.
- [Loyverse + OpenAI Dots](https://www.agent200.com/connectors/loyverse/framework/openai-dots.md): Use OpenAI Dots to build a separate read-only Loyverse assistant with Agent200. Ground the POS sales briefing in returned source data.
- [Loyverse + Claude Duet](https://www.agent200.com/connectors/loyverse/framework/claude-duet.md): Read receipts with Claude Duet and Agent200. Prepare a POS sales briefing using the connected user’s own Loyverse account.
- [Loyverse + Hermes Agent](https://www.agent200.com/connectors/loyverse/framework/hermes-agent.md): Read receipts with Hermes Agent and Agent200. Prepare a POS sales briefing using the connected user’s own Loyverse account.
- [Loyverse + OpenClaw](https://www.agent200.com/connectors/loyverse/framework/openclaw.md): Read receipts with OpenClaw and Agent200. Prepare a POS sales briefing using the connected user’s own Loyverse account.

## FAQ

### What access does Loyverse need?

Authorize the intended Loyverse account through OAuth with the required read permissions. Select the relevant store before a sales review. [Provider documentation](https://developer.loyverse.com/docs/).

### Does a list include every record?

Receipt totals and customer records are sensitive. Account for refunds, store scope and pagination; do not treat receipts as settled payouts.

### Can this workflow make changes?

The listed Loyverse operations are read-only. A proposed change in the agent answer does not edit the source.

### How should I verify the answer?

Identify the selected receipt and compare the answer with receipt, item, customer and amount fields. Disclose missing or inaccessible fields.

### Are these exact runtime tool schemas?

The listed identifiers describe catalogue capabilities. Discover the actual runtime tool names and input schemas before executing a request.

## Related connectors

- [HubSpot](https://www.agent200.com/connectors/hubspot.md): Look up and update contacts, companies and deals in your users' HubSpot CRM.
- [Salesforce](https://www.agent200.com/connectors/salesforce.md): Query and update accounts, contacts and opportunities in Salesforce.
- [LinkedIn](https://www.agent200.com/connectors/linkedin.md): Share posts and read profile details on LinkedIn on behalf of each of your users, where the relevant API permissions are available.
- [Zendesk](https://www.agent200.com/connectors/zendesk.md): Search, read, create and update Zendesk tickets, and reply to customers, on behalf of each of your users.

---

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