How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
MONI (Ex-Monisnap) website screenshot

MONI (Ex-Monisnap)

MONI, formerly Monisnap, is a Paris-based remittance fintech founded in 2017 by Raphaël Rivière, Jean-Baptiste Bouvier and Jonathan Brossard. It lets diaspora customers in France, Spain and the United Kingdom send money to roughly 150 countries — as cash pickup across a partner network of some 350,000 payout points, as a transfer into a mobile money wallet, as mobile airtime top-up with more than 800 operators, or as a prepaid card recharge — through a consumer app and the monisnap.com and allo.monisnap.com storefronts. Alongside the consumer product MONI runs a B2B "Moni-as-a-Service" remittance-as-a-service platform that banks and neobanks such as Nickel and Bnext embed white-label in their own applications. MONISNAP SAS is registered with the French ACPR as a payment services agent of MPS SAS, an authorised payment institution (CIB 17738). MONI publishes no public API: there is no developer portal, no API reference and no machine-readable contract on any MONI host — the partner platform is reached through a sales conversation.

human only

More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.

Kin Score

API Evangelist profiles MONI (Ex-Monisnap) the way a machine reads it — 3 machine-readable artifacts, 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 — MONI (Ex-Monisnap) scores 13.3/100 (emerging), with a separate agent-readiness read of 3/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.

Behind a wall

Why this profile is thin

MONI markets a B2B "Moni-as-a-Service" remittance-as-a-service platform that Nickel and Bnext already embed, but ships it entirely through direct sales — there is no developer portal to gate: api., docs., developer., developers. and sandbox.monisnap.com all NXDOMAIN, and every /.well-known/ discovery path on the two live hosts 404s.

An API exists — we simply could not reach the contract without credentials or a sales conversation. This one is MONI (Ex-Monisnap)'s to change: publishing the reference and a machine-readable spec at a public URL, while keeping key issuance behind whatever gate they like, would let an integrator evaluate the API before committing to a call.

What we probed
  • https://developer.monisnap.com/ → HTTP 0
  • https://www.monisnap.com/.well-known/api-catalog → HTTP 404
  • https://allo.monisnap.com/.well-known/agent-card.json → HTTP 404
  • https://www.monisnap.com/llms.txt → HTTP 404
  • https://www.monisnap.com/gb/ → HTTP 403

Checked 2026-08-17. If this is out of date, tell us on the provider's repo and we will re-run the profile.

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. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.

Kin Score Kin Score How this is scored →
scored 2026-10-03 · rubric v0.23.0
MONI (Ex-Monisnap) Kin Score — API readiness rating by API Evangelist

Put this on your own site. The badge is drawn live from MONI (Ex-Monisnap)'s current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.

<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/monisnap/"
   title="MONI (Ex-Monisnap) on API Evangelist — API profile and Kin Score">
  <img src="https://apis.io/badge/monisnap.svg"
       alt="MONI (Ex-Monisnap) Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>

More shapes, themes and sizes → · Score as JSON · How badges work

How we profile MONI (Ex-Monisnap)

Each block below is one kind of artifact we hold for MONI (Ex-Monisnap). 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.

Pricing Plans 1

Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.

Published pricing tiers and plan structures.

Rate Limits 1

Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.

Documented rate limits and quota policies.

Monisnap Rate Limits

0 limits

RATE LIMITS

Security Posture 1

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.

Monisnap Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Resources

Every other property we hold for MONI (Ex-Monisnap) — 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.

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 1

Pagination, idempotency, versioning, errors, and events

Build 1

SDKs, sample code, and the tooling you integrate with

Access & Security 1

Authentication, authorization, and security posture

Operate 2

Status, limits, changes, and where to get help

Commercial 3

Pricing, plans, and the legal terms of use

← All providers · Data indexed from github.com/api-evangelist/monisnap · machine-readable index on apis.io

Where this information came from

This is an independent, third-party profile of MONI (Ex-Monisnap), published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.