Flexa

Flexa is a digital-currency payments network that lets businesses accept crypto and other digital assets from customers anywhere, with instant authorization, fraud-resistant settlement, and automatic conversion into a preferred payout currency so merchants avoid price volatility. The Flexa Payments API is built around the "commerce intent" resource, which represents any attempt to collect a digital-currency payment and tracks requested debits against actual credits; supporting resources include assets, refunds, events, links, brands, and flexcodes. Flexa ships prebuilt mobile UI Components for iOS, Android, and React Native, plus in-person (Point of Sale) and online acceptance options, and a production-grade test mode that uses a valueless ERC-20 "Credit" (CR) token. Flexa is backed by Pantera Capital and supports 99+ digital assets across Ethereum, Bitcoin, Lightning, Solana, and more.

Flexa publishes 4 API contracts indexed on the APIs.io network, including Assets API, Commerce Intents API, Events API, and 1 more. Tagged areas include Company, Cryptocurrency, Payments, Digital Currency, and Fintech.

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

Flexa’s developer surface includes engineering blog, documentation, API reference, getting-started guide, support, authentication, sandbox, and 24 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

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

1 published contract 2 Agent Skills

Company Cryptocurrency Payments Digital Currency Fintech Blockchain Merchant Payments Web3

What this lets a business do 1

Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →

Consumer Commerce

AE-140

Commerce Intents

Kin Score

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

Composite quality — 46.7/100 · developing

Contract Quality 11.3 / 19

Developer Ergonomics 11.0 / 15

Access Clarity 3.2 / 15

Operational Transparency 2.1 / 10

Contract Governance 1.6 / 9

Discoverability 5.5 / 8

Regulatory Posture 4.2 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 31/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 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/flexa/"><img src="https://apis.io/badge/flexa/card.svg" alt="Flexa 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):

Access Clarity scores 21.1 — up to +15.8 composite points
Operational Transparency scores 21.1 — up to +10.3 composite points
Contract Quality scores 60.4 — up to +9.9 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/flexa/apis.yml: open an issue on github.com/api-evangelist/flexa 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 4

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

Flexa Assets API

Assets encompass all the value that flows through the Flexa platform. In the Flexa API, both national currencies (“fiat“) and digital currencies (“crypto“ or “digital assets“) a...

Flexa Commerce Intents API

Commerce intents offer a versatile way to process digital asset payments from your customers using any sales channel.

Flexa Events API

Events are created when any of the core resources on the Flexa platform change in a meaningful way, such as when a commerce intent succeeds or a digital asset transaction is req...

Flexa Refunds API

Refunds are the only way by which a Flexa payment can be reversed. Refunds are always initiated by the recipient, and can be made for either a partial amount or the full value o...

Open Collections 4

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

Flexa Assets API

OPEN COLLECTION

Flexa Assets Commerce Intents API

OPEN COLLECTION

Flexa Assets Events API

OPEN COLLECTION

Flexa Assets Refunds API

OPEN COLLECTION

Agent Skills 2

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

Collect a digital-currency payment

AGENT SKILL

Refund a completed payment

AGENT SKILL

Event Specifications 1

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

Flexa Events Webhooks

ASYNCAPI

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Flexa API Rules

60 rules · 58 errors 1 warnings 1 info

SPECTRAL

OpenAPI Overlays 1

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.

Flexa Openapi Overlay

4 actions · update · flexa-openapi.json

DERIVED

Security Posture 3

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

Flexa Authentication

http · 1 scheme

SECURITY

Flexa Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Flexa Vulnerability Disclosure

contact published

SECURITY

Agentic Access 1

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

Flexa Agentic Access

8 operations · 3 acting

AGENTIC

Resources

Get Started 3

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

Sandbox

Sandbox

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 5

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

AgenticAccess

LLMsTxt

LLMsTxt

WellKnown

WellKnown

X-MCPServerCandidate

X-MCPServerCandidate

AgentSkill

AgentSkill

Design & Contract 7

Pagination, idempotency, versioning, errors, and events

ErrorCatalog

Conventions

Lifecycle

Conformance

DataModel

Webhooks

Components

Scroll for all 7

Build 3

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Packages

Packages

SDKs

SDKs

Access & Security 4

Authentication, authorization, and security posture

Authentication

Authentication

DomainSecurity

DomainSecurity

VulnerabilityDisclosure

VulnerabilityDisclosure

Security

Security

Operate 1

Status, limits, changes, and where to get help

Support

Support

Commercial 2

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 2

The organization behind the API

Blog

Blog

Website

Website

Other 2

Properties that don't map to a standard resource type

CapabilityMap

CapabilityMap

Overlay

Overlay

Source (apis.yml)

aid: flexa
name: Flexa
description: Flexa is a digital-currency payments network that lets businesses accept crypto and other digital assets from
  customers anywhere, with instant authorization, fraud-resistant settlement, and automatic conversion into a preferred payout
  currency so merchants avoid price volatility. The Flexa Payments API is built around the "commerce intent" resource, which
  represents any attempt to collect a digital-currency payment and tracks requested debits against actual credits; supporting
  resources include assets, refunds, events, links, brands, and flexcodes. Flexa ships prebuilt mobile UI Components for iOS,
  Android, and React Native, plus in-person (Point of Sale) and online acceptance options, and a production-grade test mode
  that uses a valueless ERC-20 "Credit" (CR) token. Flexa is backed by Pantera Capital and supports 99+ digital assets across
  Ethereum, Bitcoin, Lightning, Solana, and more.
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
image: https://framerusercontent.com/assets/GHzfAvG7SahlNocEC2Agsubvp0.png
url: https://raw.githubusercontent.com/api-evangelist/flexa/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- pantera-capital
x-tier: stub
x-tier-reason: portfolio-lead
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-10-06'
x-docs-platform: mintlify
x-docs-platform-confidence: medium
x-docs-platform-checked: 2026-10-03
tags:
- Company
- Cryptocurrency
- Payments
- Digital Currency
- Fintech
- Blockchain
- Merchant Payments
- Web3
tags_raw:
- Company
- Crypto
- Payments
- Digital Currency
- Cryptocurrency
- Fintech
- Blockchain
- Merchant Payments
- Web3
apis:
- aid: flexa:flexa-assets-api
  name: Flexa Assets API
  description: 'Assets encompass all the value that flows through the Flexa platform. In the Flexa API, both national currencies
    (“fiat“) and digital currencies (“crypto“ or “digital assets“) are returned together in one collection.


    The Flexa API uses [CAIP](https://chainagnostic.org/CAIPs/caip-19)-style IDs for all assets. National currency asset IDs
    are all prefixed with “iso4217/” and use [ISO 4217](https://en.wikipedia.org/wiki/ISO_4217) 3-digit alphabetic codes.
    For example, ether on Ethereum mainnet is `eip155:1/slip44:60`, and the Canadian dollar is `iso4217/CAD`.'
  humanURL: https://docs.flexa.co/introduction
  baseURL: https://api.flexa.co
  tags:
  - Assets
  properties:
  - type: OpenAPI
    url: openapi/flexa-assets-api-openapi.yml
  - type: Documentation
    url: https://docs.flexa.co/introduction
  - type: APIReference
    url: https://docs.flexa.co/api-reference/introduction
  - type: GettingStarted
    url: https://docs.flexa.co/payments/getting-started
  - type: Authentication
    url: authentication/flexa-authentication.yml
  - type: Sandbox
    url: sandbox/flexa-sandbox.yml
  - type: ErrorCatalog
    url: errors/flexa-problem-types.yml
  - type: Conventions
    url: conventions/flexa-conventions.yml
  - type: DataModel
    url: data-model/flexa-data-model.yml
  - type: Webhooks
    url: asyncapi/flexa-events-webhooks.yml
  - type: Conformance
    url: conformance/flexa-conformance.yml
- aid: flexa:flexa-commerce-intents-api
  name: Flexa Commerce Intents API
  description: Commerce intents offer a versatile way to process digital asset payments from your customers using any sales
    channel.
  humanURL: https://docs.flexa.co/introduction
  baseURL: https://api.flexa.co
  tags:
  - Commerce Intents
  properties:
  - type: OpenAPI
    url: openapi/flexa-commerce-intents-api-openapi.yml
  - type: Documentation
    url: https://docs.flexa.co/introduction
  - type: APIReference
    url: https://docs.flexa.co/api-reference/introduction
  - type: GettingStarted
    url: https://docs.flexa.co/payments/getting-started
  - type: Authentication
    url: authentication/flexa-authentication.yml
  - type: Sandbox
    url: sandbox/flexa-sandbox.yml
  - type: ErrorCatalog
    url: errors/flexa-problem-types.yml
  - type: Conventions
    url: conventions/flexa-conventions.yml
  - type: DataModel
    url: data-model/flexa-data-model.yml
  - type: Webhooks
    url: asyncapi/flexa-events-webhooks.yml
  - type: Conformance
    url: conformance/flexa-conformance.yml
- aid: flexa:flexa-events-api
  name: Flexa Events API
  description: Events are created when any of the core resources on the Flexa platform change in a meaningful way, such as
    when a commerce intent succeeds or a digital asset transaction is requested. Clients subscribe to a stream that is provided
    over [Server-Sent Events (SSE)](https://en.wikipedia.org/wiki/Server-sent_events).
  humanURL: https://docs.flexa.co/introduction
  baseURL: https://api.flexa.co
  tags:
  - Event
  tags_raw:
  - Events
  properties:
  - type: OpenAPI
    url: openapi/flexa-events-api-openapi.yml
  - type: Documentation
    url: https://docs.flexa.co/introduction
  - type: APIReference
    url: https://docs.flexa.co/api-reference/introduction
  - type: GettingStarted
    url: https://docs.flexa.co/payments/getting-started
  - type: Authentication
    url: authentication/flexa-authentication.yml
  - type: Sandbox
    url: sandbox/flexa-sandbox.yml
  - type: ErrorCatalog
    url: errors/flexa-problem-types.yml
  - type: Conventions
    url: conventions/flexa-conventions.yml
  - type: DataModel
    url: data-model/flexa-data-model.yml
  - type: Webhooks
    url: asyncapi/flexa-events-webhooks.yml
  - type: Conformance
    url: conformance/flexa-conformance.yml
- aid: flexa:flexa-refunds-api
  name: Flexa Refunds API
  description: 'Refunds are the only way by which a Flexa payment can be reversed. Refunds are always initiated by the recipient,
    and can be made for either a partial amount or the full value of the original payment.


    Because Flexa supports payments using a wide variety of assets, including some that are highly price-volatile, refunds
    are always processed using current exchange rates. For example, if a customer makes a payment using bitcoin, and the commerce
    intent wasn’t denominated in bitcoin, the customer may not receive a refund for the exact same amount of bitcoin that
    they originally paid. Instead, the payment amount will be converted back into bitcoin using the market exchange rate before
    it’s refunded.'
  humanURL: https://docs.flexa.co/introduction
  baseURL: https://api.flexa.co
  tags:
  - Refunds
  properties:
  - type: OpenAPI
    url: openapi/flexa-refunds-api-openapi.yml
  - type: Documentation
    url: https://docs.flexa.co/introduction
  - type: APIReference
    url: https://docs.flexa.co/api-reference/introduction
  - type: GettingStarted
    url: https://docs.flexa.co/payments/getting-started
  - type: Authentication
    url: authentication/flexa-authentication.yml
  - type: Sandbox
    url: sandbox/flexa-sandbox.yml
  - type: ErrorCatalog
    url: errors/flexa-problem-types.yml
  - type: Conventions
    url: conventions/flexa-conventions.yml
  - type: DataModel
    url: data-model/flexa-data-model.yml
  - type: Webhooks
    url: asyncapi/flexa-events-webhooks.yml
  - type: Conformance
    url: conformance/flexa-conformance.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: CapabilityMap
  url: capabilities/flexa-capability-edges.yml
  name: Flexa Business Capability Map
- url: https://flexa.co/newsroom
  type: Blog
- type: AgenticAccess
  url: agentic-access/flexa-agentic-access.yml
- type: Website
  url: https://flexa.co/
- type: DeveloperPortal
  url: https://docs.flexa.co/introduction
- type: Documentation
  url: https://docs.flexa.co/introduction
- type: APIReference
  url: https://docs.flexa.co/api-reference/introduction
- type: GettingStarted
  url: https://docs.flexa.co/payments/getting-started
- type: Support
  url: https://support.flexa.co/en/
- type: TermsOfService
  url: https://flexa.co/legal/terms
- type: PrivacyPolicy
  url: https://flexa.co/legal/privacy
- type: GitHubOrganization
  url: https://github.com/flexa
- type: LLMsTxt
  url: llms/flexa-llms.txt
- type: Packages
  url: packages/flexa-packages.yml
- type: SDKs
  url: packages/flexa-packages.yml
- type: Authentication
  url: authentication/flexa-authentication.yml
- type: Sandbox
  url: sandbox/flexa-sandbox.yml
- type: WellKnown
  url: well-known/flexa-well-known.yml
- type: DomainSecurity
  url: security/flexa-domain-security.yml
- type: VulnerabilityDisclosure
  url: security/flexa-vulnerability-disclosure.yml
- type: Security
  url: https://flexa.co/security/bug-bounty-program
- type: ErrorCatalog
  url: errors/flexa-problem-types.yml
- type: Conventions
  url: conventions/flexa-conventions.yml
- type: Lifecycle
  url: lifecycle/flexa-lifecycle.yml
- type: Conformance
  url: conformance/flexa-conformance.yml
- type: DataModel
  url: data-model/flexa-data-model.yml
- type: Overlay
  url: overlays/flexa-openapi-overlay.yaml
- type: X-MCPServerCandidate
  url: mcp/flexa-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: Webhooks
  url: asyncapi/flexa-events-webhooks.yml
- type: Components
  url: components/flexa-components.yml
- type: AgentSkill
  url: skills/_index.yml
x-enrichment:
  date: '2026-07-19'
  status: backfilled
  pass: local-v1
  note: backfilled from .gitignore signal + verified work evidence

Flexa API — frequently asked questions

Does Flexa have an API?

Yes. APIs.io lists 4 APIs from Flexa, including Flexa Assets API, Flexa Commerce Intents API and Flexa Events API, and 1 more.

Is there an OpenAPI specification for the Flexa API?

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

How do I authenticate with the Flexa API?

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

Is the Flexa API ready for AI agents?

Flexa has a Kin Score of 46.7 out of 100 (developing) and an Agent Readiness score of 31.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/flexa"

All providers

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

Every operation they expose

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

How their score was established

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