Carry1st
Carry1st is Africa's leading mobile games publisher and digital commerce platform, headquartered in South Africa and operating across high-growth African markets including Nigeria, South Africa, Kenya, Ghana, Egypt, and Morocco. Beyond publishing and distributing mobile games from partners such as Riot Games, Activision, and Supercell, Carry1st operates Pay1st, a payment gateway that lets digital-content and game developers accept payments through 120+ local payment methods across six African geographies. Pay1st offers a single unified API, acts as Merchant of Record (handling compliance, taxation, FX, and risk so businesses collect in USD), and supports hosted-payment, game-client, and Carry1st Shop marketplace integration styles. Carry1st is backed by a16z. This profile was enriched by the API Evangelist pipeline from the public Pay1st developer documentation.
Carry1st publishes 4 API contracts indexed on the APIs.io network, including Authentication API, Payment Methods API, Payments API, and 1 more. Tagged areas include Company, Payments, Payment Gateway, Fintech, and Gaming.
The Carry1st catalog on APIs.io includes 1 event-driven AsyncAPI specification.
Carry1st’s developer surface includes documentation, API reference, getting-started guide, engineering blog, support, changelog, authentication, and 22 more developer resources.
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 |
|---|---|---|---|---|
| African Payments (Nigeria, Kenya, South Africa, Ghana, WAEMU) | standard | 17.2 (thin) | - | - |
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.
APIs 4
Individual APIs this provider publishes, each with its own machine-readable definition.
Carry1st Authentication API
Obtain and refresh access tokens for Gateway API requests.
Carry1st Payment Methods API
Discover the local payment methods available per country.
Carry1st Payments API
Create payment requests and query their status.
Carry1st Refunds API
Request refunds against processed transactions.
Open Collections 4
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Pay1st Gateway Authentication API
OPEN COLLECTIONPay1st Gateway Authentication Payment Methods API
OPEN COLLECTIONPay1st Gateway Authentication Payments API
OPEN COLLECTIONPay1st Gateway Authentication Refunds API
OPEN COLLECTIONArazzo Workflows 1
Multi-step API workflows described with the Arazzo specification.
Pay1st - collect a payment
Authenticate, create a signed payment request, and confirm the payment status.
ARAZZOAgent Skills 2
Packaged agent skills for driving this provider's APIs from an AI assistant.
Collect a payment with Pay1st
AGENT SKILLRefund a Pay1st transaction
AGENT SKILLEvent Specifications 1
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Carry1St Pay1St 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.
Carry1St Pay1St Gateway Overlay
DERIVEDSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
Recommended x-agentic-access execution contracts for AI agents.
Resources
Get Started 3
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 8
Pagination, idempotency, versioning, errors, and events
Scroll for all 8
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 1
Properties that don't map to a standard resource type
Source (apis.yml)
Carry1st API — frequently asked questions
Does Carry1st have an API?
Yes. APIs.io lists 4 APIs from Carry1st, including Carry1st Authentication API, Carry1st Payment Methods API and Carry1st Payments API, and 1 more.
Is there an OpenAPI specification for the Carry1st API?
Yes. APIs.io indexes 4 OpenAPI specifications for Carry1st, each linked for download from this page.
How do I authenticate with the Carry1st API?
Carry1st uses bearer-token authentication (apiKey/http · 2 schemes). The details are profiled on APIs.io as Carry1St Authentication.
Is the Carry1st API ready for AI agents?
Carry1st has a Kin Score of 34.8 out of 100 (thin) and an Agent Readiness score of 33.8 (agent-ready), scored by API Evangelist on 2026-10-31.
Work with this as data
Every provider here is available over the APIs.io API and to AI agents over MCP.