Coins.ph
Coins.ph is a BSP-regulated Philippine fintech super app combining a licensed crypto exchange (Coins Pro), an e-wallet for pesos and 170+ cryptocurrencies, and a merchant/partner payments platform. Its public developer platform exposes a Partner Integration / Payment API (QRPH collections, checkout, disbursements, refunds, virtual accounts, reconciliation) and the Coins Pro exchange API (spot trading, wallets, market data, convert, sub-accounts, and a WebSocket user-data stream), plus an on/off ramp API. All requests are authenticated with an API key and HMAC-SHA256 request signing (X-COINS-APIKEY, Timestamp, Signature). Backed by Pantera Capital and Ribbit Capital.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Coins.ph the way a machine reads it — 32 machine-readable artifacts across 26 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 — Coins.ph scores 57.1/100 (developing), with a separate agent-readiness read of 80/100 (agent native). 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 Coins.ph
Each block below is one kind of artifact we hold for Coins.ph. 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 26
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.
Coins.ph Account API
Account management APIs.
Coins.ph Account Validation API
The Account Validation API from Coins.ph — 2 operation(s) for account validation.
Coins.ph Checkout API
Checkout creation and management
Coins.ph Checkout Refund API
Checkout refund operations
Coins.ph Collections - Crypto API
Crypto deposit address
Coins.ph Collections - QRPH API
QRPH code generation and management
Coins.ph Convert API
Convert quote and acceptance operations.
Coins.ph Disbursements API
Cash-out and disbursement operations
Coins.ph General API
General endpoints for connectivity, server time, system status, and user IP.
Coins.ph Listens API
Manage user data stream listenKeys for WebSocket connections. A listenKey is required to establish a private WebSocket connection for receiving real-time account updates (orders...
Coins.ph Markets API
Market data APIs.
Coins.ph ON/OFF Ramp API
Fiat-to-crypto and crypto-to-fiat ramp operations
Coins.ph Order History API
Order history and details
Coins.ph Ramp Callback API
Webhook callbacks sent to the merchant's configured callback URL when order status changes
Coins.ph Reconciliation API
Reconciliation report
Coins.ph Refund API
Refund operations
Coins.ph Scan to Pay API
QR code scan-to-pay payment operations
Coins.ph Spot API
Spot trading operations including order placement, querying, cancellation, and trade history.
Coins.ph Sub Account API
Sub Account deposit, withdrawal, and transfer operations.
Coins.ph Tokenized Checkout API
Password-free (auto-debit) checkout
Coins.ph Trading - Convert API
Convert trading operations
Coins.ph Trading - OTC API
OTC trading for Business Account
Coins.ph Transfers API
The Transfers API from Coins.ph — 2 operation(s) for transfers.
Coins.ph Utility API
Account balance, transfers, and utility endpoints
Coins.ph Virtual Account API
Virtual account creation and management
Coins.ph Wallet API
Convert, Deposit, Withdraw, Transfers, and Sub Account Transfer operations.
Scroll within the panel for all 26 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
coinsph-mcp.yml
MCP SERVEREvent 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.
Coinsph Webhooks
ASYNCAPISecurity Posture 3
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.
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.
Resources
Every other property we hold for Coins.ph — 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 3
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 8
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 8 ·
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Operate 3
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
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/coinsph · machine-readable index on apis.io