Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Block website screenshot

Block

Block, Inc. is a global technology company building economic empowerment tools through a family of products including Square (commerce and payments), Cash App (personal finance and investing), Afterpay (buy now pay later), TIDAL (music streaming), and Spiral (open-source Bitcoin development). The Square API enables developers to build commerce applications with payment processing, order management, catalog, customer engagement, and business operations capabilities.

agent ready

Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.

Kin Score

API Evangelist profiles Block the way a machine reads it — 57 machine-readable artifacts across 5 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.

Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Block scores 69.5/100 (strong), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.

Kin Score

This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.

Kin Score Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 69.5/100 · strong
Contract Quality 16.4 / 25
Developer Ergonomics 9.1 / 20
Commercial Clarity 16.8 / 20
Operational Transparency 6.8 / 13
Governance 10.4 / 12
Discoverability 8.8 / 10
Regulatory · Payments 11.4 / 15
Agent readiness — 48/100 · agent ready
Machine-Readable Contract 18 / 18
Agentic Access Contract 15 / 15
MCP Server 0 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 7 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3

How we profile Block

Each block below is one kind of artifact we hold for Block. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.

APIs 5

Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.

Individual APIs this provider publishes, each with its own machine-readable definition.

Block Catalog API

Manage product catalog

Block Customers API

Customer management and engagement

Block Merchants API

Merchant and location data

Block Orders API

Create and manage orders

Block Payments API

Process and manage payments

Postman Collections 1

A runnable collection turns the contract into something a developer can execute in seconds. We profile them because the fastest way to trust an API is to make a real call against it.

Ready-to-run Postman collections for exercising this provider's APIs.

Square API

POSTMAN

Arazzo Workflows 13

Real integrations are rarely a single call. Arazzo describes the multi-step sequences — auth, then create, then confirm — so both a human and an agent can follow the choreography, not just the endpoints.

Multi-step API workflows described with the Arazzo specification.

Block Square Catalog Browse And Order Verify

Browse catalog items, open an order, and branch on whether the order is OPEN.

ARAZZO

Block Square Catalog Driven Order

Browse the catalog, build an order from a selected item, and capture payment.

ARAZZO

Block Square Catalog To Customer Order

Browse the catalog, create a customer, and open an order for them.

ARAZZO

Block Square Customer Order Then Pay

Create an order, branch on its state, and only take payment when it is OPEN.

ARAZZO

Block Square Customer Payment Audit

Pull a customer roster, list payments for a location, and detail the latest one.

ARAZZO

Block Square Full Commerce Flow

Resolve a location, create a customer, place an order, take payment, and verify it.

ARAZZO

Block Square Location First Sale

Resolve the active seller location, open an order there, and take payment.

ARAZZO

Block Square Location Payment Reconciliation

Resolve a location, list its recent payments, and detail the most recent one.

ARAZZO

Block Square New Customer Checkout

Create a customer, place an order for them, then capture payment for that order.

ARAZZO

Block Square Onboard Customer And Charge

Resolve a location, create a customer, and charge a direct payment to them.

ARAZZO

Block Square Reconcile Payment

List recent payments for a location and pull full detail on the most recent one.

ARAZZO

Block Square Returning Customer Checkout

Find an existing customer or create one, then place and pay for their order.

ARAZZO

Block Square Take Payment And Verify

Take a card payment and immediately re-read it to confirm the final status.

ARAZZO

Scroll within the panel for all 13 ·

Pricing Plans 1

Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.

Published pricing tiers and plan structures.

Block Plans Pricing

3 plans

PLANS

Rate Limits 1

Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.

Documented rate limits and quota policies.

Block Rate Limits

5 limits

RATE LIMITS

FinOps 1

Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.

Cost, billing, and metering signals for API financial operations.

Block Finops

FINOPS

Features 7

The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.

Notable capabilities this provider offers.

Payment Processing

Accept card-present and card-not-present payments using Square hardware, web, or mobile SDKs with OAuth 2.0 or access token authentication.

Order Management

Create, update, and fulfill orders with line items, discounts, taxes, and service charges across online and in-person channels.

Catalog Management

Manage a unified product catalog with items, variations, modifiers, categories, taxes, and discounts synchronized across all locations.

Customer Engagement

Build customer profiles, loyalty programs, gift cards, and marketing campaigns to drive repeat business and customer retention.

Multi-Location Support

Manage multiple business locations with location-specific inventory, pricing, staff permissions, and reporting.

Webhook Events

Subscribe to real-time webhook events for payments, orders, inventory changes, customer activity, and subscription lifecycle events.

Sandbox Environment

Full sandbox environment with test card numbers, merchant accounts, and simulated hardware for development and testing.

Scroll within the panel for all 7 ·

Semantic Vocabularies 1

JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.

JSON-LD contexts and semantic vocabularies used across these APIs.

Block Context

35 classes · 0 properties

JSON-LD

Spectral Rules 2

Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.

Block API Rules

5 rules · 4 warnings

SPECTRAL

Block API Rules

34 rules · 11 errors · 20 warnings

SPECTRAL

JSON Schema 4

Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.

Standalone JSON Schema definitions for this provider's data models.

CatalogObject

4 properties

JSON SCHEMA

Customer

7 properties

JSON SCHEMA

Order

7 properties

JSON SCHEMA

Payment

8 properties

JSON SCHEMA

JSON Structure 4

JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.

JSON Structure definitions describing this provider's data shapes.

Block Catalog Object Structure

0 properties

JSON STRUCTURE

Block Customer Structure

0 properties

JSON STRUCTURE

Block Order Structure

0 properties

JSON STRUCTURE

Block Payment Structure

0 properties

JSON STRUCTURE

Examples 4

Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.

Example request and response payloads for these APIs.

Block Customer Example

13 fields

EXAMPLE

Block Order Example

12 fields

EXAMPLE

Block Payment Example

14 fields

EXAMPLE

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Block Authentication

http/oauth2 · 2 schemes

SECURITY

Block Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Scopes 1

OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.

OAuth scopes governing access to this provider's APIs.

Block Scopes

6 scopes · authorizationCode

6 scopes

SCOPES

Agentic Access 1

An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.

Recommended x-agentic-access execution contracts for AI agents.

Block Agentic Access

8 operations · 3 acting

8 operations · 3 acting

AGENTIC

Use Cases 5

What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.

What developers build with this provider.

Point of Sale Integration

Retailers and restaurants build custom POS applications using Square's payment, catalog, and order APIs.

eCommerce Checkout

Online stores integrate Square's Web Payments SDK and Orders API to accept payments and manage fulfillment.

Marketplace Payments

Multi-seller marketplaces use Square Connect to route payments to sellers and manage fees through the Payouts API.

Subscription Billing

SaaS and service businesses use Square Subscriptions API for automated recurring billing and invoice management.

Loyalty and Rewards

Businesses implement custom loyalty programs using the Loyalty API to track points, tiers, and reward redemptions.

Integrations 4

Pre-built integrations with other platforms tell you where this provider already fits in a stack.

Pre-built integrations with other platforms and tools.

WooCommerce

Official Square extension for WooCommerce synchronizes inventory, products, and payments between WordPress stores and Square.

BigCommerce

Square integration for BigCommerce enables omnichannel selling with synchronized catalog and unified payment processing.

Xero

Square-Xero integration automatically syncs sales transactions and payments to Xero accounting for reconciliation.

QuickBooks

Square connector for QuickBooks Online syncs sales, refunds, and fees to QuickBooks for financial reporting.

Resources

Every other property we hold for Block — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.

Get Started 2

Portal, sign-up, and the first successful call

Documentation 1

Reference material describing how the API behaves

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

Access & Security 3

Authentication, authorization, and security posture

Operate 2

Status, limits, changes, and where to get help

Commercial 3

Pricing, plans, and the legal terms of use

Company 2

The organization behind the API

← All providers · Data indexed from github.com/api-evangelist/block · machine-readable index on apis.io