CloudWalk
CloudWalk, Inc. is a Sunnyvale- and São Paulo-based payments and financial-infrastructure company that builds an AI-native transaction layer for small businesses. It operates three consumer-facing brands: InfinitePay, its Brazilian acquirer and digital-banking platform (card machines, Tap to Pay, hosted checkout, payment links, Pix, PJ accounts, credit and CDB); JIM, a phone-as-POS operating system for self-employed workers in the United States; and Pierre, a personal-finance intelligence product built on Brazilian Open Finance. Its public developer surface is deliberately small and integration-shaped rather than platform-shaped: an Integrated Checkout REST API on api.checkout.infinitepay.io that creates hosted payment links and checks their status, an approved-payment webhook, and an InfiniteTap deeplink contract that hands a Tap-to-Pay transaction from a third-party POS app to the InfinitePay mobile app and back. CloudWalk publishes no OpenAPI, no machine-readable discovery documents and no MCP or agent surface. The legal entity behind InfinitePay is CLOUDWALK INSTITUIÇÃO DE PAGAMENTO E SERVIÇOS LTDA (CNPJ 18.189.547/0001-42), a Brazilian payment institution supervised by the Banco Central do Brasil.
CloudWalk publishes 3 API contracts indexed on the APIs.io network: Checkout Links API, InfinitePay Checkout API, and Payments API. Tagged areas include Company, Payments, Financial Services, Fintech, and Checkout.
The CloudWalk catalog on APIs.io includes 1 event-driven AsyncAPI specification.
CloudWalk’s developer surface includes documentation, API reference, getting-started guide, support, engineering blog, pricing, signup flow, and 30 more developer resources.
What this lets a business do 1
Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →
Kin Score
Markets this provider is in provisional
The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.
| Market | Position | Depth | Registered MCP server | Declares compatibility |
|---|---|---|---|---|
| Latin American Open Finance (Brazil OFB + Pix) | undeclared | - | - | - |
| EMV Card Terminals (card acceptance hardware and kernels) | undeclared | - | - | - |
| Brazil BCB Authorized Institutions (Banco Central do Brasil register beyond Pix) | undeclared | - | - | - |
Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.
Standards implemented 1
Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.
APIs 3
Individual APIs this provider publishes, each with its own machine-readable definition.
CloudWalk Checkout Links API
Create InfinitePay-hosted checkout payment links.
CloudWalk InfinitePay Checkout API
The InfinitePay Checkout API API from CloudWalk — 0 operation(s) for infinitepay checkout api.
CloudWalk Payments API
Query the payment status of a checkout link.
Open Collections 1
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
InfinitePay Checkout API
OPEN COLLECTIONPricing Plans 1
Published pricing tiers and plan structures.
Event Specifications 1
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Cloudwalk Infinitepay Webhooks
ASYNCAPIOpenAPI Overlays 1
Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.
Security Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
Recommended x-agentic-access execution contracts for AI agents.
Resources
Get Started 4
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 7
Pagination, idempotency, versioning, errors, and events
Scroll for all 7
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 5
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 4
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 2
Properties that don't map to a standard resource type
Source (apis.yml)
Work with this as data
Every provider here is available over the APIs.io API and to AI agents over MCP.