Bitpagos

Bitpagos is a payment gateway based in Buenos Aires, Argentina, focused on merchants in Latin America. It processes credit cards and Bitcoin, aiming to reduce international transaction fees for small and medium businesses. Founded as Ripio, the company rebranded to Bitpagos and offers APIs for payment processing, refunds, and transaction reporting, targeting fintech integrations across the region.

Bitpagos is listed with 8 APIs on the APIs.io network, including Bitpagos API, Customers API, Offramp API, and 5 more. Tagged areas include Payments, Fintech, Latin America, Bitcoin, and Credit Cards.

The Bitpagos catalog on APIs.io includes 1 event-driven AsyncAPI specification, 1 JSON-LD context, and 1 Spectral governance ruleset.

Bitpagos’ developer surface includes sandbox, authentication, support, engineering blog, documentation, API reference, and 18 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

35.5/100 thin ▬ flat Agent 29/100 agent aware Full breakdown ↓
scored 2026-11-13 · rubric v0.28.0 · Show this score on your site →

8 APIs

Payments Fintech Latin America Bitcoin Credit Cards

Kin Score

Kin Score How this is scored →
scored 2026-11-13 · rubric v0.28.0

Composite quality — 35.5/100 · thin

Contract Quality 6.3 / 19

Developer Ergonomics 7.5 / 15

Access Clarity 1.3 / 15

Operational Transparency 3.5 / 10

Contract Governance 2.0 / 9

Discoverability 6.7 / 8

Regulatory Posture 2.8 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 29/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 6 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 6 / 6

Agent Skills 0 / 5

Well-Known Catalog 4 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Payments regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/bitpagos/"><img src="https://apis.io/badge/bitpagos/card.svg" alt="Bitpagos on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship Ask about this →
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author Ask about this →
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented) Ask about this →
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes Ask about this →
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0 Ask about this →
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented) Ask about this →

7 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Access Clarity scores 8.5 — up to +18.3 composite points Ask about this →
Contract Quality scores 33.7 — up to +16.6 composite points Ask about this →
Developer Ergonomics scores 50.0 — up to +10.0 composite points Ask about this →

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Not sure how this applies to your stack? Ask about any one item. Kin Lane reads every question, looks at your profile and your situation, and replies with what a fix would take — scoped to that one area, priced up front, yours whether you ship it or not. Ask a question →

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/bitpagos/apis.yml: open an issue on github.com/api-evangelist/bitpagos to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

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.

OpenAPI

measured — observed by APIs.io (published)

APIs 8

Individual APIs this provider publishes, each with its own machine-readable definition.

Bitpagos API

Payment processing API for merchants, supporting credit cards and Bitcoin.

Bitpagos Bitpagos API

The Bitpagos API API from Bitpagos — 1 operation(s) for bitpagos api.

Bitpagos Customers API

The Customers API from Bitpagos — 10 operation(s) for customers.

Bitpagos Offramp API

The Offramp API from Bitpagos — 1 operation(s) for offramp.

Bitpagos Quotes API

The Quotes API from Bitpagos — 1 operation(s) for quotes.

Bitpagos Rates API

The Rates API from Bitpagos — 1 operation(s) for rates.

Bitpagos Resources API

The Resources API from Bitpagos — 1 operation(s) for resources.

Bitpagos Trade API

The Trade API from Bitpagos — 1 operation(s) for trade.

Scroll for all 8

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Bitpagos Webhooks

ASYNCAPI

Semantic Vocabularies 1

JSON-LD contexts and semantic vocabularies used across these APIs.

Bitpagos Context

19 classes · 36 properties

JSON-LD

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs. Counts are the severity each rule declares, not results of running them.

Bitpagos API Rules

10 rules · 8 error-severity 1 warn-severity 1 info-severity

SPECTRAL

2 properties

JSON SCHEMA

PostResourcesAccesstokensSharetokenResponse

1 properties

JSON SCHEMA

Scroll for all 11

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Bitpagos Authentication

4 schemes

SECURITY

Bitpagos Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Resources

Get Started 1

Portal, sign-up, and the first successful call

Sandbox

Sandbox

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

WellKnown

WellKnown

Design & Contract 6

Pagination, idempotency, versioning, errors, and events

Spectral

JSONLD

Vocabulary

Webhooks

DataModel

Conformance

Build 3

SDKs, sample code, and the tooling you integrate with

SDKs

SDKs

Packages

Packages

GitHubOrganization

GitHubOrganization

Access & Security 3

Authentication, authorization, and security posture

SecurityTxt

SecurityTxt

Authentication

Authentication

DomainSecurity

DomainSecurity

Operate 2

Status, limits, changes, and where to get help

Support

Support

StatusPage

StatusPage

Commercial 1

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

Company 2

The organization behind the API

Blog

Blog

Website

Website

Other 2

Properties that don't map to a standard resource type

Hosts

Hosts

Vendors

Vendors

Source (apis.yml)

aid: bitpagos
name: Bitpagos
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  probe_state: unreadable
  source:
  - authentication
  - security
  - sandbox
  generated: '2026-11-13'
  method: derived
image: https://cdn.prod.website-files.com/5f17344acf2c6d3c3a1d6238/680a5d403b378088d8ccb8a3_Contenido_banner-marca_fb_1200x628_0525.png
description: Bitpagos is a payment gateway based in Buenos Aires, Argentina, focused on merchants in Latin America. It processes
  credit cards and Bitcoin, aiming to reduce international transaction fees for small and medium businesses. Founded as Ripio,
  the company rebranded to Bitpagos and offers APIs for payment processing, refunds, and transaction reporting, targeting
  fintech integrations across the region.
url: https://raw.githubusercontent.com/api-evangelist/bitpagos/refs/heads/main/apis.yml
x-type: company
x-source: harvest:secondary-market
x-tier: profiled
x-tier-reason: enrichment pass 2026-09-28 (modular-v1; was harvest)
specificationVersion: '0.20'
created: '2026-09-28'
modified: '2026-09-28'
x-docs-platform: mintlify
x-docs-platform-confidence: medium
x-docs-platform-checked: 2026-10-04
tags:
- Payments
- Fintech
- Latin America
- Bitcoin
- Credit Cards
tags_raw:
- Payments
- Fintech
- Latin America
- Bitcoin
- CreditCards
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: SecurityTxt
  url: well-known/bitpagos-status-security.txt
- type: Spectral
  url: rules/bitpagos-rules.yml
- type: JSONLD
  url: json-ld/bitpagos-context.jsonld
- type: Vocabulary
  url: vocabulary/bitpagos-vocabulary.yml
- type: Webhooks
  url: asyncapi/bitpagos-webhooks.yml
- type: DataModel
  url: data-model/bitpagos-data-model.yml
- type: Sandbox
  url: sandbox/bitpagos-sandbox.yml
- type: Authentication
  url: authentication/bitpagos-authentication.yml
- type: Conformance
  url: conformance/bitpagos-conformance.yml
- type: LLMsTxt
  url: llms/bitpagos-llms.txt
- type: WellKnown
  url: well-known/bitpagos-well-known.yml
- type: Hosts
  url: hosts/bitpagos-hosts.yml
- type: Vendors
  url: vendors/bitpagos-vendors.yml
- type: SDKs
  url: packages/bitpagos-packages.yml
- type: Packages
  url: packages/bitpagos-packages.yml
- type: TermsOfService
  url: http://terms.ripio.com/
- type: Support
  url: https://help.ripio.com/
- type: StatusPage
  url: https://status.ripio.com/
- type: Blog
  url: https://launchpad.ripio.com/blog
- type: Documentation
  url: https://apidocs.ripio.com/
- type: APIReference
  url: https://docs.ripio.com/llms.txt
- type: GitHubOrganization
  url: https://github.com/ripio
- type: DomainSecurity
  url: security/bitpagos-domain-security.yml
- type: Website
  url: https://www.ripio.com
apis:
- name: Bitpagos API
  description: Payment processing API for merchants, supporting credit cards and Bitcoin.
  humanURL: https://docs.ripio.com/crypto-as-a-service/overview/introduction
  baseURL: https://b2b-api.ripio.com/
  aid: bitpagos:bitpagos-api-2
- aid: bitpagos:bitpagos-bitpagos-api-api
  name: Bitpagos Bitpagos API
  description: The Bitpagos API API from Bitpagos — 1 operation(s) for bitpagos api.
  humanURL: https://docs.ripio.com/crypto-as-a-service/overview/introduction
  baseURL: https://b2b-api.ripio.com/
  tags:
  - Bitpagos API
  properties:
  - type: OpenAPI
    url: openapi/bitpagos-bitpagos-api-api-openapi.yml
  - type: JSONSchema
    url: json-schema/bitpagos-get-api-v1-v1-id-response-schema.json
- aid: bitpagos:bitpagos-customers-api
  name: Bitpagos Customers API
  description: The Customers API from Bitpagos — 10 operation(s) for customers.
  humanURL: https://docs.ripio.com/crypto-as-a-service/overview/introduction
  baseURL: https://b2b-api.ripio.com/
  tags:
  - Customers
  properties:
  - type: OpenAPI
    url: openapi/bitpagos-customers-api-openapi.yml
  - type: JSONSchema
    url: json-schema/bitpagos-post-api-v1-customers-response-schema.json
  - type: JSONSchema
    url: json-schema/bitpagos-post-api-v1-customers-request-schema.json
  - type: JSONSchema
    url: json-schema/bitpagos-post-api-v1-customers-customerid-kyc-otp-validate-response-schema.json
  - type: JSONSchema
    url: json-schema/bitpagos-post-api-v1-customers-customerid-kyc-start-response-schema.json
- aid: bitpagos:bitpagos-offramp-api
  name: Bitpagos Offramp API
  description: The Offramp API from Bitpagos — 1 operation(s) for offramp.
  humanURL: https://docs.ripio.com/crypto-as-a-service/overview/introduction
  baseURL: https://b2b-api.ripio.com/
  tags:
  - Off-Ramp
  tags_raw:
  - Offramp
  properties:
  - type: OpenAPI
    url: openapi/bitpagos-offramp-api-openapi.yml
- aid: bitpagos:bitpagos-quotes-api
  name: Bitpagos Quotes API
  description: The Quotes API from Bitpagos — 1 operation(s) for quotes.
  humanURL: https://docs.ripio.com/crypto-as-a-service/overview/introduction
  baseURL: https://b2b-api.ripio.com/
  tags:
  - Quotes
  properties:
  - type: OpenAPI
    url: openapi/bitpagos-quotes-api-openapi.yml
  - type: JSONSchema
    url: json-schema/bitpagos-post-api-v1-quotes-response-schema.json
  - type: JSONSchema
    url: json-schema/bitpagos-post-api-v1-quotes-request-schema.json
- aid: bitpagos:bitpagos-rates-api
  name: Bitpagos Rates API
  description: The Rates API from Bitpagos — 1 operation(s) for rates.
  humanURL: https://docs.ripio.com/crypto-as-a-service/overview/introduction
  baseURL: https://b2b-api.ripio.com/
  tags:
  - Rates
  properties:
  - type: OpenAPI
    url: openapi/bitpagos-rates-api-openapi.yml
  - type: JSONSchema
    url: json-schema/bitpagos-get-api-v1-rates-response-schema.json
- aid: bitpagos:bitpagos-resources-api
  name: Bitpagos Resources API
  description: The Resources API from Bitpagos — 1 operation(s) for resources.
  humanURL: https://docs.ripio.com/crypto-as-a-service/overview/introduction
  baseURL: https://b2b-api.ripio.com/
  tags:
  - Resources
  properties:
  - type: OpenAPI
    url: openapi/bitpagos-resources-api-openapi.yml
  - type: JSONSchema
    url: json-schema/bitpagos-post-resources-accesstokens-sharetoken-request-schema.json
  - type: JSONSchema
    url: json-schema/bitpagos-post-resources-accesstokens-sharetoken-response-schema.json
- aid: bitpagos:bitpagos-trade-api
  name: Bitpagos Trade API
  description: The Trade API from Bitpagos — 1 operation(s) for trade.
  humanURL: https://docs.ripio.com/crypto-as-a-service/overview/introduction
  baseURL: https://b2b-api.ripio.com/
  tags:
  - Trade
  properties:
  - type: OpenAPI
    url: openapi/bitpagos-trade-api-openapi.yml
  - type: JSONSchema
    url: json-schema/bitpagos-get-trade-public-server-time-response-schema.json
x-coverage:
  state: unreadable
  reason: no-machine-readable-spec
  detail: The provider's documentation links to OpenAPI specs hosted on docs.ripio.com, which belong to Ripio, not Bitpagos.
  evidence:
  - url: https://docs.ripio.com/crypto-as-a-service/openapi.json
    status: 200
  checked: '2026-09-28'
x-enrichment:
  date: '2026-09-28'
  status: enriched
  artifacts_added: 25
  pass: modular-v1
  engine: identity=local,contract=local,surfaces=local,docs=local,regulatory=local

Bitpagos API — frequently asked questions

Does Bitpagos have an API?

Yes. APIs.io lists 8 APIs from Bitpagos, including Bitpagos API, Bitpagos Bitpagos API and Bitpagos Customers API, and 5 more.

Is there an OpenAPI specification for the Bitpagos API?

Yes. APIs.io indexes 7 OpenAPI specifications for Bitpagos, each linked for download from this page.

How do I authenticate with the Bitpagos API?

Bitpagos uses bearer-token authentication (4 schemes). The details are profiled on APIs.io as Bitpagos Authentication.

Is the Bitpagos API ready for AI agents?

Bitpagos has a Kin Score of 35.5 out of 100 (thin) and an Agent Readiness score of 28.5 (agent-aware), scored by API Evangelist on 2026-11-13.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/bitpagos"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/bitpagos/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/bitpagos/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.