Redotpay website screenshot

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 publishes 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.

19.2/100 emerging ▬ flat Agent 13/100 agent aware saas Full breakdown ↓
scored 2026-09-08 · rubric v0.20.0
AccessSelf serve
1 APIs 1 MCP Servers
CompanyPaymentsFintechStablecoinsCryptocurrencyWalletsAgentic PaymentsMachine Payments Protocolx402Authentication

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0
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/.
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 github.com/api-evangelist/redotpay: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

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

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

OAuth 2.0 · no documented scopes

0 scopes

SCOPES

Resources

Get Started 1

Portal, sign-up, and the first successful call

Documentation 1

Reference material describing how the API behaves

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 4

Pagination, idempotency, versioning, errors, and events

Build 3

SDKs, sample code, and the tooling you integrate with

Access & Security 3

Authentication, authorization, and security posture

Operate 2

Status, limits, changes, and where to get help

Company 2

The organization behind the API

Source (apis.yml)

apis.yml Raw ↑
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: self-serve
  trial: false
  try_now: false
  public: false
  label: Self-serve signup
  confidence: medium
  source:
  - authentication
  generated: '2026-07-22'
  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
- Authentication
tags_raw:
- Company
- Payments
- Fintech
- Stablecoin
- Cryptocurrency
- Wallet
- Agentic Payments
- Machine Payments Protocol
- x402
- OAuth
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
  - Authentication
  tags_raw:
  - Payments
  - Agentic Payments
  - MPP
  - x402
  - OAuth
  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

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"

Discovery needs no key. Ratings and market analysis are Pro.

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.

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