Skip to content

Connecting your systems

Can Claude answer questions from Square?

A simple, owner-level walkthrough for businesses that run on Square: what Claude can answer, how the connection works, and how to check an answer before you rely on it.

Supported capabilityApplies to Square POS and payments · Claude

Short answer

Yes. Square, the cloud POS and payments platform, publishes a developer API, so Claude connects to it directly, with no export to schedule. We put that connection behind a secure gateway, with read-only access and per-person permissions. You ask about sales, customers, and what is in the catalog, and Claude answers from your Square account. Read-only as we run it today: nothing writes back to Square unless you deliberately turn that on.

An owner who runs the store on Square, already pays for Claude, and wants to ask plain questions about sales, stock, and customers without building reports or exporting spreadsheets.

  • A Square account for your store, with an owner who can authorize access.
  • Confirmation of which Square data and permissions the connection should cover.
  • A Claude account for each person who will ask questions.
  • The access you want each role to have, decided up front.

This is a real setup-and-verify procedure. Follow it, and check the answer yourself before you rely on it.

  1. You authorize the access. Square uses its own authorization to grant access to your account. You authorize it with your own identity, and your credentials stay out of public examples.
  2. SkyNexus sets up the connection. We build a connector against Square’s API and put it behind a secure MCP gateway, with read-only access and per-person permissions. Because Square is in the cloud, there is no export and no separate copy; the data stays in Square.
  3. Add the connector in Claude. Using the endpoint and instructions SkyNexus supplies, add the custom connector in Claude, authenticate with your provisioned access, and confirm the tools you expect are present. Then start a test conversation.
  4. Run one bounded question, and specify it fully. Ask a closed-period figure, and state exactly what you mean: the period and its date semantics, the metric definition (gross or net), how returns and tax are treated, the filters, and the timezone. Square answers in the moment, so also confirm you are asking about the window you intend.
  5. Reconcile against your Square reports, and investigate any gap. Run the same period in Square’s own reporting and compare. A closed period does not by itself guarantee a correct answer: gross versus net, returns, tax, date semantics, filters, and later corrections can all move a figure. If the numbers do not match, investigate the difference before you rely on the answer.
  6. When something is off. An authentication failure is not the same as a tool your role does not have. If Claude asks you to reconnect, follow the supplied sign-in steps and retry. If authentication still fails, contact SkyNexus. If an expected tool is missing, ask us to check your provisioned role and the available tools. To stop future calls, remove the connector from your Claude: that ends new requests through that connector. It does not delete data already retrieved or revoke other people’s connectors, and immediate revocation holds only where we have tested it.

It can

  • Answer in the moment across sales, catalog, and customers, as far as your Square permissions allow.
  • Let you check a figure yourself: reconcile it against your own Square reports before you rely on it.
  • Run from the Claude a person already uses, by adding one connector.

It cannot (as we run it today)

  • Write to or change anything in Square. The connection we run is read-only; any write is a separate, deliberate setup you turn on.
  • See what Square's API does not expose, or what a person's permissions exclude.
  • Reach anything outside Square. This connection is to Square, and only Square.

Not as we run it today. The connection we operate is read-only. Any write, changing an order, a customer, or the catalog, is a separate, deliberate setup you turn on, never something the AI does on its own or that a reworded question unlocks.

Square is a live cloud system, so the connection reads it in the moment rather than from a nightly copy. That means an answer can reflect today’s sales and current stock. It is still bounded by what Square’s API exposes and by a person’s permissions, and a figure is only as sound as the query behind it, so specify the period, metric definition, and filters, and reconcile against your Square reports before relying on it.

The gateway is built on MCP, an open protocol that ChatGPT also supports, so MCP is a potential path to the same gateway. Whether a given ChatGPT account can add the connector, authenticate, and see the expected tools still has to be validated; protocol support alone is not a working pairing. If you later change assistants, the connection setup stays in place: see switching AI assistants without rebuilding the connection.

EvidenceSupported capability under gate

This is the connection we build for Square, offered as a supported capability rather than a named-store deployment. The pattern behind it, a secure gateway with read-only access and per-person permissions, runs in production on The Edge, which we last verified running on August 27, 2026. Square exposes sales, catalog, and customer data through its public API, and we connect it the same way, through the API rather than an export.