Stone Co
Stone Co. (NASDAQ: STNE) is a Brazilian financial services and payment technology company headquartered in São Paulo. Stone provides card acquiring (POS), digital banking, business management software, and credit products to entrepreneurs and small-to-medium businesses across more than 5,500 Brazilian cities, and is the fourth-largest acquirer in Brazil following its acquisition of Elavon's Brazilian operations. Stone operates several developer-facing platforms: Connect Stone (a POS integration API for in-store payment automation and "infinite shelf" omnichannel inventory), Stone Open Banking (a RESTful banking API for account, balance, TED, PIX, and payment-link operations against Stone accounts and consented third-party accounts), the Stone SDK Android (for embedding card-present payments into Android apps and Pinpad/POS devices), AutoTEF (PIN-pad-based self-service TEF integration), the Conciliação Stone XML reconciliation feed, and Pagar.me (Stone's online/PSP gateway covering orders, charges, customers, subscriptions, split payments, recurring billing, tokenization, and 3DS). Authentication is OAuth2 / PEM-keyed JWT for Open Banking and API-key / credential-based for the other surfaces. Onboarding for Open Banking and Connect Stone partners is gated through Stone's partnerships team; Pagar.me and the Android SDK are self-service. Documentation is primarily in Portuguese and concentrated at docs.stone.com.br, docs.openbank.stone.com.br, connect-stone.stone.com.br, conciliacao.stone.com.br, and docs.pagar.me.
Index entry only — little beyond a description and a link, and nothing machine-readable enough for an agent to act on without a human reading the site first.
API Evangelist profiles Stone Co the way a machine reads it — 1 machine-readable artifact, 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 — Stone Co scores 14.2/100 (minimal), with a separate agent-readiness read of 0/100 (human only). 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
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Stone Co
Each block below is one kind of artifact we hold for Stone Co. 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.
Security Posture 1
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.
Resources
Every other property we hold for Stone Co — 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 7
Reference material describing how the API behaves
Scroll within the panel for all 7 ·
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Company 6
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/stone-co · machine-readable index on apis.io