# Square for AI agents. Managed auth, ready-made tools.

> Look up Square payments, orders and customers, and create invoices and payment links, on behalf of each of your users.

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

## Instructions for AI agents

Connector: Square, through Agent200. In code: "square".
What it does: Look up Square payments, orders and customers, and create invoices and payment links, on behalf of each of your users.
Page: https://www.agent200.com/tools/square/

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 Square's own page, through the authorization link Agent200 returns. Never ask a user for a Square 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: square_list_payments, square_search_orders, square_search_customers, square_search_catalog, square_get_inventory, square_list_locations. Write tools: square_create_customer, square_create_payment_link, square_create_invoice, square_publish_invoice. Name "square" 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/tools/square/framework/claude/
   https://www.agent200.com/tools/square/framework/chatgpt/
   https://www.agent200.com/tools/square/framework/claude-code/
   https://www.agent200.com/tools/square/framework/muse/
   https://www.agent200.com/tools/square/framework/grok-bot/
   https://www.agent200.com/tools/square/framework/openai-dots/
   https://www.agent200.com/tools/square/framework/claude-duet/
   https://www.agent200.com/tools/square/framework/hermes-agent/
   https://www.agent200.com/tools/square/framework/openclaw/

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

## About

With the Square connector, your agent works with each seller's Square account: it looks up payments, orders and customers, reads the item catalog and stock counts, and creates customers, invoices and payment links. Each user connects their own Square account through managed OAuth, and your agent stays within the permissions they approve and the operations your project allows.

Square is a commerce platform that sellers use to take payments in person and online and to run their business.

## Square tools

- **List payments** (`square_list_payments`, read): List payments for a date range, with amount and status.
- **Search orders** (`square_search_orders`, read): Find orders by location, date, state or customer.
- **Search customers** (`square_search_customers`, read): Find customers by name, email or phone number.
- **Create a customer** (`square_create_customer`, write): Add a customer to the seller's directory.
- **Search the catalog** (`square_search_catalog`, read): Find items and their prices in the seller's catalog.
- **Get inventory** (`square_get_inventory`, read): Read stock counts for catalog items at each location.
- **Create a payment link** (`square_create_payment_link`, write): Create a checkout link a customer can pay through.
- **Create an invoice** (`square_create_invoice`, write): Create a draft invoice for an order.
- **Publish an invoice** (`square_publish_invoice`, write): Send a draft invoice to the customer.
- **List locations** (`square_list_locations`, read): List the seller's business locations.

## Limits you can set

**Turn single tools on or off.** Keep the read tools on, and switch off `square_publish_invoice` and `square_create_payment_link` if your agent should only report on sales.

**Restrict what the agent reaches.** Choose the endpoints and scopes a project may use. 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 Square

Each end user authorizes their own Square 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 Square account, once.
const connection = await agent200
  .user("user_123")
  .connect("square");

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 Square tools

Name the user, the model and the tools. The model decides which Square 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 today's sales at the downtown location",
    tools: ["square"],
  });

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

(Conceptual example of the Agent200 SDK.)

## Sign-in and permissions

**Who signs in.** Each of your users, once, on Square's own page, as the seller whose account they connect. You never see or store their Square password.

**What access is requested.** The permissions Square lists before the seller agrees, such as reading payments and orders or writing customers and invoices.

## Example requests

- "What were today's sales at the downtown location"
- "Which items are running low"
- "Send Jane Smith an invoice for the catering order"
- "Create a payment link for a 50 dollar gift card"

## Guides: Square with your AI framework

- [Square + Claude](https://www.agent200.com/tools/square/framework/claude.md): Connect Square to Claude through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
- [Square + ChatGPT](https://www.agent200.com/tools/square/framework/chatgpt.md): ChatGPT cannot send an API key to a custom MCP server, so this guide builds Square into your own agent with OpenAI's models and the Agent200 SDK.
- [Square + Claude Code](https://www.agent200.com/tools/square/framework/claude-code.md): Have Claude Code build a Square agent with the Agent200 SDK: managed OAuth, ready-made tools and one API key.
- [Square + Muse](https://www.agent200.com/tools/square/framework/muse.md): Connect Square to Muse through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
- [Square + Grok Bot](https://www.agent200.com/tools/square/framework/grok-bot.md): Connect Square to Grok Bot through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
- [Square + OpenAI Dots](https://www.agent200.com/tools/square/framework/openai-dots.md): Dots cannot send an API key to a custom MCP server, so this guide builds an always-on Square agent with OpenAI's models and the Agent200 SDK.
- [Square + Claude Duet](https://www.agent200.com/tools/square/framework/claude-duet.md): Connect Square to Claude Duet through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
- [Square + Hermes Agent](https://www.agent200.com/tools/square/framework/hermes-agent.md): Connect Square to Hermes Agent through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
- [Square + OpenClaw](https://www.agent200.com/tools/square/framework/openclaw.md): Connect Square to OpenClaw through Agent200's MCP server: managed OAuth, ready-made tools and one API key.

## FAQ

### Who handles the Square OAuth flow and the tokens?

Agent200. It runs the authorization, handles the callback on its own domain, stores the tokens and refreshes them. You do not build or maintain an OAuth integration for Square.

### Does my agent act as the end user?

Within what that user authorized, yes. Every request names an end user, and Agent200 uses only that user's Square connection, never another user's. It cannot reach anything the user or Square has not authorized.

### Can I limit what my agent can do in Square?

Yes. You choose which services, endpoints and authorization scopes are allowed in your Agent200 configuration, and the agent works only within them.

## Related connectors

- [HubSpot](https://www.agent200.com/tools/hubspot.md): Look up and update contacts, companies and deals in your users' HubSpot CRM.
- [Salesforce](https://www.agent200.com/tools/salesforce.md): Query and update accounts, contacts and opportunities in Salesforce.
- [LinkedIn](https://www.agent200.com/tools/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/tools/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/
