Loyverse

CRM and sales

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.

About Loyverse

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.

Tools

What your agent can do in Loyverse.

Each tool is a capability the model can call. You decide which ones a project allows, and every call runs with the end user's own Loyverse connection.

  • List receipts

    Read
    loyverse_list_receipts

    Find receipts in a selected store and time window.

  • Read a receipt

    Read
    loyverse_get_receipt

    Retrieve one receipt by ID.

  • List items

    Read
    loyverse_list_items

    Find catalog items available to the connection.

  • Read an item

    Read
    loyverse_get_item

    Retrieve one identified catalog item.

  • List customers

    Read
    loyverse_list_customers

    Find customer records in authorized scope.

Control

Limits you can set.

You decide what your agent may do in Loyverse, and Agent200 runs every call within those limits.

  • 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

Connect Loyverse
in three steps.

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

    agent.js
    Conceptual example
    Set up the SDK with the Agent200 API key
    // One Agent200 API key covers every connector enabled for the project.
    const agent200 = new Agent200({
      apiKey: process.env.AGENT200_API_KEY,
    });
  2. 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.

    connect.js
    Conceptual example
    Let an end user connect their account (managed OAuth)
    // 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);
    }
  3. 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.

    run.js
    Conceptual example
    Run a request with the connector's tools
    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);

Access

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.

For agents

Instructions for AI agents.

Using a coding agent? Paste this brief into it, or give it the address of this page. It describes the Loyverse connector and how to use it.

Agent brief
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/

This page is also available as Markdown, for agents and LLMs: /connectors/loyverse.md

Guides

Use Loyverse with the AI you build on.

Step-by-step setup for Loyverse with a specific model, assistant or agent framework.

FAQ

Loyverse and Agent200, answered.

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.

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.

  • HubSpot

    HubSpot

    Look up and update contacts, companies and deals in your users' HubSpot CRM.

    Managed OAuth CRM and sales
  • Salesforce

    Salesforce

    Query and update accounts, contacts and opportunities in Salesforce.

    Managed OAuth CRM and sales
  • LinkedIn

    LinkedIn

    Share posts and read profile details on LinkedIn on behalf of each of your users, where the relevant API permissions are available.

    Managed OAuth CRM and sales
  • Zendesk

    Zendesk

    Search, read, create and update Zendesk tickets, and reply to customers, on behalf of each of your users.

    Managed OAuth CRM and sales
200 OK

Start with Loyverse.
Your agent does the rest.

Your users connect their own Loyverse accounts. Agent200 handles the OAuth, the tokens and every tool call.

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)