CRM and sales
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.
About Square
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.
Tools
What your agent can do in Square.
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 Square connection.
-
List payments
Readsquare_list_paymentsList payments for a date range, with amount and status.
-
Search orders
Readsquare_search_ordersFind orders by location, date, state or customer.
-
Search customers
Readsquare_search_customersFind customers by name, email or phone number.
-
Create a customer
Writesquare_create_customerAdd a customer to the seller's directory.
-
Search the catalog
Readsquare_search_catalogFind items and their prices in the seller's catalog.
-
Get inventory
Readsquare_get_inventoryRead stock counts for catalog items at each location.
-
Create a payment link
Writesquare_create_payment_linkCreate a checkout link a customer can pay through.
-
Create an invoice
Writesquare_create_invoiceCreate a draft invoice for an order.
-
Publish an invoice
Writesquare_publish_invoiceSend a draft invoice to the customer.
-
List locations
Readsquare_list_locationsList the seller's business locations.
No tool matches that search.
Control
Limits you can set.
You decide what your agent may do in Square, and Agent200 runs every call within those limits.
-
Turn single tools on or off
Keep the read tools on, and switch off
square_publish_invoiceandsquare_create_payment_linkif 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
Connect Square
in three steps.
-
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.jsConceptual exampleSet 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
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.
connect.jsConceptual exampleLet an end user connect their account (managed OAuth) // 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); } -
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.
run.jsConceptual exampleRun a request with the connector's tools 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);
Access
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.
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 Square connector and how to use it.
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/
This page is also available as Markdown, for agents and LLMs: /tools/square.md
Guides
Use Square with the AI you build on.
Step-by-step setup for Square with a specific model, assistant or agent framework.
-
Square + Claude
How to connect Square to Claude
-
Square + ChatGPT
How to connect Square to ChatGPT
-
Square + Claude Code
How to connect Square to Claude Code
-
Square + Muse
How to connect Square to Muse
-
Square + Grok Bot
How to connect Square to Grok Bot
-
Square + OpenAI Dots
How to connect Square to OpenAI Dots
-
Square + Claude Duet
How to connect Square to Claude Duet
-
Square + Hermes Agent
How to connect Square to Hermes Agent
-
Square + OpenClaw
How to connect Square to OpenClaw
FAQ
Square and Agent200, answered.
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.