Xflow
Xflow is a cross-border payments platform for Indian businesses, freelancers, and exporters, enabling them to receive international payments through local collection accounts (ACH in the US, SEPA in the EU) with one-day INR settlement, transparent FX at mid-market rates, and automated FIRA and compliance reporting. The Xflow REST API exposes accounts, receivables, payment links, deposits, payouts, transfers, balances, exchange rates, and webhook endpoints so platforms and payment aggregators can embed compliant India-bound money movement.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Xflow the way a machine reads it — 23 machine-readable artifacts across 18 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Xflow scores 55.5/100 (developing), with a separate agent-readiness read of 71/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Xflow
Each block below is one kind of artifact we hold for Xflow. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 18
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Xflow Accounts API
The Accounts API from Xflow — 4 operation(s) for accounts.
Xflow AccountSettings API
The AccountSettings API from Xflow — 3 operation(s) for accountsettings.
Xflow Addresses API
The Addresses API from Xflow — 2 operation(s) for addresses.
Xflow Balance API
The Balance API from Xflow — 2 operation(s) for balance.
Xflow BalanceTransactions API
The BalanceTransactions API from Xflow — 2 operation(s) for balancetransactions.
Xflow Deposits API
The Deposits API from Xflow — 2 operation(s) for deposits.
Xflow Events API
The Events API from Xflow — 2 operation(s) for events.
Xflow ExchangeRates API
The ExchangeRates API from Xflow — 2 operation(s) for exchangerates.
Xflow FeePlans API
The FeePlans API from Xflow — 2 operation(s) for feeplans.
Xflow Files API
The Files API from Xflow — 3 operation(s) for files.
Xflow PaymentLinks API
The PaymentLinks API from Xflow — 6 operation(s) for paymentlinks.
Xflow Payments API
The Payments API from Xflow — 2 operation(s) for payments.
Xflow Payouts API
The Payouts API from Xflow — 2 operation(s) for payouts.
Xflow Persons API
The Persons API from Xflow — 2 operation(s) for persons.
Xflow Quotes API
The Quotes API from Xflow — 1 operation(s) for quotes.
Xflow Receivables API
The Receivables API from Xflow — 5 operation(s) for receivables.
Xflow Transfers API
The Transfers API from Xflow — 2 operation(s) for transfers.
Xflow WebhookEndpoints API
The WebhookEndpoints API from Xflow — 4 operation(s) for webhookendpoints.
Scroll within the panel for all 18 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
Xflow MCP candidate manifest
MCP SERVEREvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Xflow Webhooks
ASYNCAPISecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Xflow — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 6
Portal, sign-up, and the first successful call
Documentation 3
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 7
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 7 ·
Build 5
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/xflow · machine-readable index on apis.io