WorldFirst
WorldFirst is a United Kingdom-founded cross-border payments and money-movement company, headquartered in London and owned by Ant Group (Alipay) since 2019. It gives online sellers, marketplaces, and SMEs a multi-currency World Account to collect, hold, convert, and send money across borders, alongside a World Card for multi-currency spending and marketplace/supplier payouts. Its home market is the United Kingdom, but its book is global e-commerce and cross-border trade, serving merchants selling on Amazon and other marketplaces. WorldFirst ships a genuine, API-native developer platform at developers.worldfirst.com built on Ant Group's Antom-style gateway (open-sea/open-eu/open-na hosts, /amsin/api/v1 paths): a RESTful, JSON, HTTPS-only interface segmented into an Enterprise Solution (account, beneficiary, FX, transfer, payout, invoicing, virtual-card credit), a Pay Solution (Cashier Payment / online checkout acceptance for merchants), and a WorldTrade Solution (cross-border trade orders). Requests are secured with RSA256/ECC224 digital signatures plus OAuth 2.0 access tokens; asynchronous notifications (webhooks) return payment and trade-order results. The public reference is documentation-and-console only — the underlying OpenAPI/Swagger is not offered as a downloadable spec (the gateway blocks anonymous spec fetches), so integration is gated behind partner onboarding and the console's iMock/iTest tooling.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles WorldFirst the way a machine reads it — 6 machine-readable artifacts across 3 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 — WorldFirst scores 39.9/100 (thin), with a separate agent-readiness read of 23/100 (agent aware). 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.
How we profile WorldFirst
Each block below is one kind of artifact we hold for WorldFirst. 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 3
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.
WorldFirst Enterprise Solution API
The WorldFirst Enterprise Solution (World Account) API — a RESTful, JSON, signed-request interface covering customer onboarding, account and beneficiary management, statements, ...
WorldFirst Pay Solution API
The WorldFirst Pay Solution (Cashier Payment) API lets overseas e-commerce merchants accept payments through a hosted checkout: create a payment order, let the customer complete...
WorldFirst WorldTrade Solution API
The WorldTrade Solution API supports cross-border trade transactions between partners and the WorldFirst platform — e.g. inquiryQuotes (FX quote lookup at /amsin/api/v1/payments...
Event Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Worldfirst Webhooks
ASYNCAPISecurity 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.
Resources
Every other property we hold for WorldFirst — 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 5
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Access & Security 2
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/worldfirst · machine-readable index on apis.io