Redotpay

RedotPay is a global stablecoin-based payment fintech that integrates blockchain solutions with traditional banking and finance infrastructures. The platform lets millions of people spend and send digital assets through a crypto-backed Visa card, a multi-currency wallet, P2P trading, international transfers, and stablecoin earning. Its developer-facing surface is agentic: a first-party Rust CLI (redotpay) and a local MCP server / Agent Skill (redotpay-payment) that let AI agents settle HTTP 402 "Payment Required" challenges over the Machine Payments Protocol (MPP), using OAuth2 device-flow login and per-payment idempotency against the production RedotPay API.

Redotpay is listed with 1 API on the APIs.io network. Tagged areas include Company, Payments, Fintech, Stablecoins, and Cryptocurrency.

Redotpay’s developer surface includes documentation, support, engineering blog, signup flow, CLI, authentication, and 14 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

18.4/100 emerging ▬ flat Agent 13/100 agent aware Heartbeat 70/100 alive saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

1 API 1 MCP Servers 1 Agent Skills

Company Payments Fintech Stablecoins Cryptocurrency Wallets Agentic PaymentsMachine Payments Protocolx402 OAuth Authentication

Kin Score

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

Composite quality — 18.4/100 · emerging

Contract Quality 0.0 / 21

Developer Ergonomics 5.7 / 17

Access Clarity 2.2 / 17

Operational Transparency 0.3 / 11

Contract Governance 0.5 / 10

Discoverability 6.4 / 9

Regulatory Posture 3.6 / 15

Agent readiness — 13/100 · agent aware

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 12 / 12

Machine-Readable Auth 10 / 10

Idempotency 9 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 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 could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% 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/redotpay/"><img src="https://apis.io/badge/redotpay/card.svg" alt="Redotpay 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):

Machine-Readable Contract +18 pts — api_specs includes an OpenAPI document
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes
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)
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link

9 more unmet checks in the Agent Readiness table above.

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

Contract Quality scores 0.0 — up to +25.0 composite points
Access Clarity scores 13.2 — up to +17.4 composite points
Developer Ergonomics scores 33.3 — up to +13.3 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/redotpay/apis.yml: open an issue on github.com/api-evangelist/redotpay 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
Agent Skills (SKILL.md packages)	undeclared	-	-	1
Stablecoins and Tokenization (stablecoin issuers, tokenized assets)	undeclared	-	-	1
x402 Micropayments & Agentic Pay-per-Call	undeclared	-	-	1

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 4

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.

OAuth

tagged — the provider's own APIs.json carries the standard as a tag; implementation not verified

x402

tagged — the provider's own APIs.json carries the standard as a tag; implementation not verified

Model Context Protocol (MCP)

measured — observed by APIs.io (documented)

Agent Skills

measured — observed by APIs.io (published)

APIs 1

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

RedotPay Agentic Payments API

Production RedotPay HTTP API surface behind the redotpay CLI and the redotpay-payment MCP server. Provides OAuth2 device-flow authentication and the agentic Machine Payments Pro...

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

Redotpay MCP Server

First-party local MCP server (redotpay-payment) that lets AI agents settle MPP HTTP 402 payments on the user's behalf. Installed via the redotpay-payment-skill install.sh, which...

MCP SERVER

Agent Skills 1

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

redotpay-payment

AGENT SKILL

Security Posture 2

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

Redotpay Authentication

2 schemes

SECURITY

Redotpay Domain Security

TLSv1.3 · DNSSEC · DMARC

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Redotpay Scopes

1 scope

1 scopes

SCOPES

Resources

Get Started 1

Portal, sign-up, and the first successful call

SignUp

SignUp

Documentation 1

Reference material describing how the API behaves

Documentation

Documentation

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

MCPServer

AgentSkill

LLMsTxt

WellKnown

Design & Contract 4

Pagination, idempotency, versioning, errors, and events

Conventions

Idempotency

Conformance

Lifecycle

Build 3

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Packages

Packages

CLI

CLI

Access & Security 3

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Authentication

Authentication

OAuthScopes

OAuthScopes

Operate 2

Status, limits, changes, and where to get help

HelpCenter

HelpCenter

Support

Support

Company 2

The organization behind the API

Website

Website

Blog

Blog

Source (apis.yml)

aid: redotpay
name: Redotpay
description: 'RedotPay is a global stablecoin-based payment fintech that integrates blockchain solutions with traditional
  banking and finance infrastructures. The platform lets millions of people spend and send digital assets through a crypto-backed
  Visa card, a multi-currency wallet, P2P trading, international transfers, and stablecoin earning. Its developer-facing surface
  is agentic: a first-party Rust CLI (redotpay) and a local MCP server / Agent Skill (redotpay-payment) that let AI agents
  settle HTTP 402 "Payment Required" challenges over the Machine Payments Protocol (MPP), using OAuth2 device-flow login and
  per-payment idempotency against the production RedotPay API.'
url: https://raw.githubusercontent.com/api-evangelist/redotpay/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- lightspeed-venture-partners
x-tier: stub
x-tier-reason: portfolio-lead
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - 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
  - scopes
  - security
  generated: '2026-11-06'
  method: derived
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-21'
image: https://www.redotpay.com/logo.svg
tags:
- Company
- Payments
- Fintech
- Stablecoins
- Cryptocurrency
- Wallets
- Agentic Payments
- Machine Payments Protocol
- x402
- OAuth
- Authentication
tags_raw:
- Company
- Payments
- Fintech
- Stablecoin
- Cryptocurrency
- Wallet
- Agentic Payments
- Machine Payments Protocol
- x402
- OAuth
- Authentication
apis:
- name: RedotPay Agentic Payments API
  description: Production RedotPay HTTP API surface behind the redotpay CLI and the redotpay-payment MCP server. Provides
    OAuth2 device-flow authentication and the agentic Machine Payments Protocol (MPP) endpoint that resolves HTTP 402 / x402
    payment challenges and settles them with a payment credential, then retries the original request.
  humanURL: https://github.com/redotpay/redotpay-cli
  baseURL: https://apiv2.redotpay.com
  tags:
  - Payments
  - Agentic Payments
  - MPP
  - x402
  - OAuth
  - Authentication
  tags_raw:
  - Payments
  - Agentic Payments
  - MPP
  - x402
  - OAuth
  - Authentication
  properties:
  - type: Authentication
    url: authentication/redotpay-authentication.yml
  - type: OAuthScopes
    url: scopes/redotpay-scopes.yml
  - type: Conventions
    url: conventions/redotpay-conventions.yml
  - type: Idempotency
    url: conventions/redotpay-conventions.yml
  - type: Conformance
    url: conformance/redotpay-conformance.yml
  - type: Lifecycle
    url: lifecycle/redotpay-lifecycle.yml
  - type: MCPServer
    url: mcp/redotpay-mcp.yml
  - type: CLI
    url: cli/redotpay-cli.yml
  - type: AgentSkill
    url: skills/redotpay-payment.md
common:
- type: DomainSecurity
  url: security/redotpay-domain-security.yml
- type: Website
  url: https://www.redotpay.com
- type: Documentation
  url: https://github.com/redotpay/redotpay-cli
- type: HelpCenter
  url: https://helpcenter.redotpay.com
- type: Support
  url: https://helpcenter.redotpay.com
- type: Blog
  url: https://blog.redotpay.com
- type: GitHubOrganization
  url: https://github.com/redotpay
- type: SignUp
  url: https://www.redotpay.com
- type: Packages
  url: packages/redotpay-packages.yml
- type: CLI
  url: cli/redotpay-cli.yml
- type: MCPServer
  url: mcp/redotpay-mcp.yml
- type: AgentSkill
  url: skills/_index.yml
- type: Authentication
  url: authentication/redotpay-authentication.yml
- type: OAuthScopes
  url: scopes/redotpay-scopes.yml
- type: Conventions
  url: conventions/redotpay-conventions.yml
- type: Idempotency
  url: conventions/redotpay-conventions.yml
- type: Conformance
  url: conformance/redotpay-conformance.yml
- type: Lifecycle
  url: lifecycle/redotpay-lifecycle.yml
- type: LLMsTxt
  url: llms/redotpay-llms.txt
- type: WellKnown
  url: well-known/redotpay-well-known.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
x-enrichment:
  date: '2026-07-21'
  status: enriched
  artifacts_added: 13
  pass: local-v1

Redotpay API — frequently asked questions

Does Redotpay have an API?

Yes. APIs.io lists 1 API from Redotpay, including RedotPay Agentic Payments API.

How do I authenticate with the Redotpay API?

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

Does Redotpay have an MCP server?

Yes. APIs.io lists 1 MCP server for Redotpay: First-party local MCP server (redotpay-payment) that lets AI agents settle MPP HTTP 402 payments on the user's behalf. Installed via the redotpay-payment-skill install.sh, which registers the MCP serv

Is the Redotpay API ready for AI agents?

Redotpay has a Kin Score of 18.4 out of 100 (emerging) and an Agent Readiness score of 12.8 (agent-aware), 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/redotpay"

All providers

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

Every operation they expose

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

How their score was established

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