Culqi
Culqi is a Peruvian online payments platform and a Grupo Credicorp / Krealo company. Its REST API v2 lets businesses accept card, Yape, PagoEfectivo, mobile wallet and Cuotealo (installment) payments in PEN and USD, with card data tokenized client-side against a PCI-scoped secure host and all money movement, subscriptions and webhooks driven from a server-side secret key.
Reference-quality API operations across every facet — a rich contract, published governance, transparent operations, and machine-readable commercial terms.
API Evangelist profiles Culqi the way a machine reads it — 47 machine-readable artifacts across 12 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 — Culqi scores 66.6/100 (exemplar), with a separate agent-readiness read of 44/100 (agent ready). 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-08-17 · rubric v0.11.0
Put this on your own site. The badge is drawn live from Culqi's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/culqi/"
title="Culqi on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/culqi.svg"
alt="Culqi Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/culqi/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/culqi/"
title="Culqi on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/culqi/card.svg"
alt="Culqi Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Culqi
Each block below is one kind of artifact we hold for Culqi. 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 12
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.
Culqi 3DS API
3-D Secure charge confirmation on the secure host.
Culqi Cards API
Cards saved against a customer for recurring or one-click charges.
Culqi Charges API
One-time charges (cargos) against a token or saved card.
Culqi Customers API
Stored customer (cliente) profiles.
Culqi Events API
Webhook event objects representing account activity.
Culqi Iins API
Card BIN / IIN metadata lookup.
Culqi Orders API
Payment orders for PagoEfectivo (CIP) and bank-transfer / cash-agent flows.
Culqi Plans API
Recurring-billing plan definitions.
Culqi Refunds API
Full or partial refunds (devoluciones) of a charge.
Culqi Subscriptions API
Subscriptions linking a saved card to a plan.
Culqi Tokens API
Client-side tokenization of card and Yape credentials on the secure host.
Culqi Transfers API
Settlement transfers (abonos) paid out to the merchant.
Scroll within the panel for all 12 ·
Postman Collections 12
A runnable collection turns the contract into something a developer can execute in seconds. We profile them because the fastest way to trust an API is to make a real call against it.
Ready-to-run Postman collections for exercising this provider's APIs.
Culqi API v2 3DS API
POSTMANCulqi API v2 3DS Cards API
POSTMANCulqi API v2 3DS Charges API
POSTMANCulqi API v2 3DS Events API
POSTMANCulqi API v2 3DS Iins API
POSTMANCulqi API v2 3DS Orders API
POSTMANCulqi API v2 3DS Plans API
POSTMANCulqi API v2 3DS Refunds API
POSTMANCulqi API v2 3DS Tokens API
POSTMANScroll within the panel for all 12 ·
Open Collections 13
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONCulqi API v2 3DS API
OPEN COLLECTIONCulqi API v2 3DS Cards API
OPEN COLLECTIONCulqi API v2 3DS Charges API
OPEN COLLECTIONCulqi API v2 3DS Customers API
OPEN COLLECTIONCulqi API v2 3DS Events API
OPEN COLLECTIONCulqi API v2 3DS Iins API
OPEN COLLECTIONCulqi API v2 3DS Orders API
OPEN COLLECTIONCulqi API v2 3DS Plans API
OPEN COLLECTIONCulqi API v2 3DS Refunds API
OPEN COLLECTIONCulqi API v2 3DS Subscriptions API
OPEN COLLECTIONCulqi API v2 3DS Tokens API
OPEN COLLECTIONCulqi API v2 3DS Transfers API
OPEN COLLECTIONScroll within the panel for all 13 ·
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.
culqi-mcp.yml
MCP SERVERPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Culqi Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Culqi Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Culqi Finops
FINOPSEvent 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.
Culqi Events Webhooks
ASYNCAPISecurity Posture 4
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 Culqi — 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 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 7
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 7 ·
Build 6
SDKs, sample code, and the tooling you integrate with
Access & Security 6
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 5
Pricing, plans, and the legal terms of use
Company 3
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/culqi · machine-readable index on apis.io
This is an independent, third-party profile of Culqi, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.