Ualá

Ualá is a Latin American fintech founded in Argentina in 2017 by Pierpaolo Barbieri, offering a neobank super-app (prepaid and credit cards, savings, investments, loans, insurance) in Argentina and Mexico, where it operates as Ualá ABC through the acquired ABC Capital bank. Its merchant arm, Ualá Bis, provides payments acceptance — link de pago, POS, e-commerce plugins, and the API Cobros Online v2, a checkout API with hosted payment links, order retrieval and listing, refunds, and webhook status notifications, documented at developers.ualabis.com.ar with official Node.js and PHP SDKs.

Ualá publishes 4 API contracts indexed on the APIs.io network, including Authentication API, Orders API, Refunds API, and 1 more. Tagged areas include Company, Fintech, Payments, Banking, and Neobank.

The Ualá catalog on APIs.io includes 1 event-driven AsyncAPI specification and 1 Spectral governance ruleset.

Ualá’s developer surface includes engineering blog, documentation, API reference, getting-started guide, support, pricing, changelog, and 24 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

38.8/100 thin ▬ flat Agent 36/100 agent ready Front door AI 1/6 silent saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

2 published contracts 2 Agent Skills

Company Fintech Payments Banking Neobank Checkout E-Commerce Argentina Mexico

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 38.8/100 · thin

Contract Quality 4.2 / 19

Developer Ergonomics 10.6 / 15

Access Clarity 5.7 / 15

Operational Transparency 2.6 / 10

Contract Governance 1.6 / 9

Discoverability 5.0 / 8

Regulatory Posture 3.0 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 36/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 6 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 6 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 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 Banking & Open Finance 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/ual/"><img src="https://apis.io/badge/ual/card.svg" alt="Ualá 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
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)
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document
Delegated User Identity +6 pts — a served discovery document listing authorization_code in grant_types_supported (served), else an oauth2 authorizationCode flow or openIdConnect declared in an OpenAPI (documented)

5 more unmet checks in the Agent Readiness table above.

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

Contract Quality scores 22.2 — up to +19.5 composite points
Access Clarity scores 38.2 — up to +12.4 composite points
Contract Governance scores 18.2 — up to +9.8 composite points

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.

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/ual/apis.yml: open an issue on github.com/api-evangelist/ual 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 →

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
Argentine Fintech Registers (BCRA PSP + entities, CNV agents + PSAV, Cámara Fintech)	regulated	47.0	-	-

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.

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 4

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

Ualá Authentication API

The Authentication API from Ualá — 1 operation(s) for authentication.

Ualá Orders API

Payment orders (checkout)

Ualá Refunds API

Refunds of approved orders

Ualá Bis API Cobros Online V2 API

The Ualá Bis API Cobros Online V2 API from Ualá — 0 operation(s) for ualá bis api cobros online v2.

Open Collections 3

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

Ualá Bis API v2 Authentication API

OPEN COLLECTION

Ualá Bis API v2 Authentication Orders API

OPEN COLLECTION

Ualá Bis API v2 Authentication Refunds API

OPEN COLLECTION

Agent Skills 2

Packaged agent skills for driving this provider's APIs from an AI assistant.

Create a Ualá Bis checkout order and track it to approval

AGENT SKILL

Refund a Ualá Bis order and confirm the result

AGENT SKILL

Event Specifications 1

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

Ual Webhooks

ASYNCAPI

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Ualá API Rules

60 rules · 58 errors 1 warnings 1 info

SPECTRAL

OpenAPI Overlays 2

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.

Ual Bis Auth V2 Overlay

2 actions · update · ual-bis-auth-v2-openapi.yml

DERIVED

Ual Bis Cobros Online V2 Overlay

4 actions · update · ual-bis-cobros-online-v2-openapi.yml

DERIVED

Security Posture 2

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

Ual Authentication

http · 1 scheme

SECURITY

Ual Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Ual Agentic Access

5 operations · 3 acting

AGENTIC

Resources

Get Started 4

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

Login

Sandbox

Sandbox

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

AgenticAccess

X-MCPServerCandidate

X-MCPServerCandidate

LLMsTxt

LLMsTxt

AgentSkill

AgentSkill

Design & Contract 7

Pagination, idempotency, versioning, errors, and events

Webhooks

ErrorCatalog

Conventions

Lifecycle

Conformance

DataModel

Components

Scroll for all 7

Build 3

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Packages

Packages

SDKs

SDKs

Access & Security 2

Authentication, authorization, and security posture

Authentication

Authentication

DomainSecurity

DomainSecurity

Operate 2

Status, limits, changes, and where to get help

Support

Support

ChangeLog

ChangeLog

Commercial 3

Pricing, plans, and the legal terms of use

Pricing

Pricing

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 3

The organization behind the API

Blog

Blog

Website

Website

Blog

Blog

Other 1

Properties that don't map to a standard resource type

Overlay

Overlay

Source (apis.yml)

aid: ual
name: Ualá
description: Ualá is a Latin American fintech founded in Argentina in 2017 by Pierpaolo Barbieri, offering a neobank super-app
  (prepaid and credit cards, savings, investments, loans, insurance) in Argentina and Mexico, where it operates as Ualá ABC
  through the acquired ABC Capital bank. Its merchant arm, Ualá Bis, provides payments acceptance — link de pago, POS, e-commerce
  plugins, and the API Cobros Online v2, a checkout API with hosted payment links, order retrieval and listing, refunds, and
  webhook status notifications, documented at developers.ualabis.com.ar with official Node.js and PHP SDKs.
url: https://raw.githubusercontent.com/api-evangelist/ual/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- bessemer-venture-partners
x-tier: enriched
x-docs-platform: nextra
x-docs-platform-confidence: medium
x-docs-platform-checked: 2026-10-17
x-docs-hosting: vercel
x-enrichment:
  date: '2026-07-21'
  status: enriched
  artifacts_added: 23
  pass: local-v1
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - security
  - sandbox
  generated: '2026-11-06'
  method: derived
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-10-06'
tags:
- Company
- Fintech
- Payments
- Banking
- Neobank
- Checkout
- E-Commerce
- Argentina
- Mexico
tags_raw:
- Company
- Fintech
- Payments
- Banking
- Neobank
- Checkout
- Ecommerce
- Argentina
- Mexico
image: https://developers.ualabis.com.ar/logo-large.png
apis:
- aid: ual:ual-authentication-api
  name: Ualá Authentication API
  description: The Authentication API from Ualá — 1 operation(s) for authentication.
  humanURL: https://developers.ualabis.com.ar/v2
  baseURL: https://checkout.developers.ar.ua.la/v2/api
  tags:
  - Authentication
  properties:
  - type: OpenAPI
    url: openapi/ual-authentication-api-openapi.yml
  - type: Documentation
    url: https://developers.ualabis.com.ar/v2
  - type: Documentation
    url: https://developers.ualabis.com.ar/v2/authentication/create
- aid: ual:ual-orders-api
  name: Ualá Orders API
  description: Payment orders (checkout)
  humanURL: https://developers.ualabis.com.ar/v2
  baseURL: https://checkout.developers.ar.ua.la/v2/api
  tags:
  - Order
  tags_raw:
  - Orders
  properties:
  - type: OpenAPI
    url: openapi/ual-orders-api-openapi.yml
  - type: Documentation
    url: https://developers.ualabis.com.ar/v2
  - type: Documentation
    url: https://developers.ualabis.com.ar/v2/authentication/create
- aid: ual:ual-refunds-api
  name: Ualá Refunds API
  description: Refunds of approved orders
  humanURL: https://developers.ualabis.com.ar/v2
  baseURL: https://checkout.developers.ar.ua.la/v2/api
  tags:
  - Refunds
  properties:
  - type: OpenAPI
    url: openapi/ual-refunds-api-openapi.yml
  - type: Documentation
    url: https://developers.ualabis.com.ar/v2
  - type: Documentation
    url: https://developers.ualabis.com.ar/v2/authentication/create
- aid: ual:ual-ual-bis-api-cobros-online-v2-api
  name: Ualá Bis API Cobros Online V2 API
  description: The Ualá Bis API Cobros Online V2 API from Ualá — 0 operation(s) for ualá bis api cobros online v2.
  humanURL: https://developers.ualabis.com.ar/v2
  baseURL: https://checkout.developers.ar.ua.la/v2/api
  tags:
  - Ualá Bis API Cobros Online V2
  properties:
  - type: OpenAPI
    url: openapi/ual-ual-bis-api-cobros-online-v2-api-openapi.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- url: https://www.uala.com.ar/aula-uala/blog
  type: Blog
- type: Overlay
  url: overlays/ual-bis-auth-v2-overlay.yaml
- type: AgenticAccess
  url: agentic-access/ual-agentic-access.yml
- type: Website
  url: https://www.uala.com.ar/
- type: DeveloperPortal
  url: https://developers.ualabis.com.ar/
- type: Documentation
  url: https://developers.ualabis.com.ar/v2
- type: APIReference
  url: https://developers.ualabis.com.ar/v2
- type: GettingStarted
  url: https://developers.ualabis.com.ar/
- type: GitHubOrganization
  url: https://github.com/Uala-Developers
- type: Blog
  url: https://blog.uala.com.ar/
- type: Support
  url: https://www.uala.com.ar/preguntas-frecuentes
- type: Pricing
  url: https://www.uala.com.ar/costos
- type: Login
  url: https://web.ualabis.com.ar/
- type: TermsOfService
  url: https://www.uala.com.ar/cgu
- type: PrivacyPolicy
  url: https://www.uala.com.ar/privacidad
- type: ChangeLog
  url: changelog/ual-changelog.yml
- type: Webhooks
  url: asyncapi/ual-webhooks.yml
- type: ErrorCatalog
  url: errors/ual-problem-types.yml
- type: Conventions
  url: conventions/ual-conventions.yml
- type: Sandbox
  url: sandbox/ual-sandbox.yml
- type: Lifecycle
  url: lifecycle/ual-lifecycle.yml
- type: Conformance
  url: conformance/ual-conformance.yml
- type: Packages
  url: packages/ual-packages.yml
- type: SDKs
  url: packages/ual-packages.yml
- type: X-MCPServerCandidate
  url: mcp/ual-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: LLMsTxt
  url: llms/ual-llms.txt
- type: AgentSkill
  url: skills/_index.yml
- type: DataModel
  url: data-model/ual-data-model.yml
- type: Components
  url: components/ual-components.yml
- type: Authentication
  url: authentication/ual-authentication.yml
- type: DomainSecurity
  url: security/ual-domain-security.yml

Ualá API — frequently asked questions

Does Ualá have an API?

Yes. APIs.io lists 4 APIs from Ualá, including Ualá Authentication API, Ualá Orders API and Ualá Refunds API, and 1 more.

Is there an OpenAPI specification for the Ualá API?

Yes. APIs.io indexes 4 OpenAPI specifications for Ualá, each linked for download from this page.

How do I authenticate with the Ualá API?

Ualá uses bearer-token authentication (http · 1 scheme). The details are profiled on APIs.io as Ual Authentication.

Is the Ualá API ready for AI agents?

Ualá has a Kin Score of 38.8 out of 100 (thin) and an Agent Readiness score of 36.4 (agent-ready), scored by API Evangelist on 2026-11-06.

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/ual"

All providers

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

Every operation they expose

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

How their score was established

curl "https://apis.io/api/v1/providers/ual/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.