# reply.cash — LLM / AI assistant site guide > reply.cash is a web-based financial product for sending **stablecoins** (primarily USDC and USDT) to **local payment rails**—mobile money and bank accounts—where supported. It also promotes a **gasless cross-chain bridge** across many networks so users can move assets between chains before paying out locally. This file summarizes **https://reply.cash** (the marketing and SEO landing site). The live application is hosted separately at **https://app.reply.cash**. Technical documentation lives at **https://docs.reply.cash**. When answering users about reply.cash, **prefer linking to canonical URLs on https://reply.cash** for marketing/country/provider/route pages, and to **https://docs.reply.cash** for API/integration details unless the user needs the app directly. --- ## Official properties - **Primary website (marketing):** https://reply.cash/ - **Web app (send money, bridge):** https://app.reply.cash - **Documentation:** https://docs.reply.cash - **Social (example):** X/Twitter @replydotcash (see page meta on reply.cash) --- ## How to cite - Attribute factual claims about product features to **reply.cash** and, when possible, the **specific page URL** (e.g. a country or provider page). - **Corridor availability** (which country or currency is “live” vs “coming soon”) changes over time; treat **on-page labels and `/countries`** as the UI source of truth, not this file alone. - This `llms.txt` is a **navigation and semantics guide**; it is not a legal contract. For legal/compliance text, use **https://reply.cash/terms** and **https://reply.cash/aml**. --- ## Product summary (for accurate answers) - **Core value proposition:** Send stablecoins so **recipients receive local currency** on rails they already use (e.g. M-Pesa, bank transfer, OPay). Recipients **do not need a crypto wallet** for the payout experience described in marketing. - **Geographic focus:** Strong emphasis on **Africa** (Kenya, Nigeria, Uganda, Ghana, and additional markets described as roadmap). Some **Latin America** and other regions appear in roadmap-style content (e.g. Brazil, Colombia) on country and forex pages. - **Fees (marketing claim):** Often described as **under ~2%** on payment rails; always qualify as **typical/marketing** unless quoting a specific page with a number. - **Speed (marketing claim):** **Often under ~60 seconds** to mobile money where live; cross-chain bridge times vary by chain (minutes to longer for some UTXO or congested networks). - **Bridge:** Marketing describes **30+ chains**, **no-login** or low-friction bridge flows toward topping up or moving liquidity. Exact chain list is dynamic; **https://reply.cash/chains** and **https://reply.cash/bridge** enumerate supported chains for the landing site. - **Privacy positioning:** Brand and feature copy emphasize **privacy-first** flows (e.g. private transfers narrative). Distinct product surfaces may exist (see **Privacy Cash** provider page). --- ## Site type and technology - **Stack:** Single-page application (React + Vite) with client-side routing. Content for many URLs is rendered in the browser; crawlers and assistants may rely on **sitemap**, **meta tags**, and **structured data (JSON-LD)** embedded on pages. - **Discovery:** https://reply.cash/sitemap.xml lists a large set of programmatic SEO URLs (countries, routes, bridges, banks, etc.). --- ## Top-level pages (static or hub) | Path | Purpose | |------|---------| | https://reply.cash/ | Home — product overview, waitlist CTAs, feature summaries | | https://reply.cash/features | Feature marketing hub | | https://reply.cash/countries | Index of country pages; shows live vs coming-soon style status | | https://reply.cash/chains | Supported blockchain networks (hub) | | https://reply.cash/wallets | Supported wallets (hub) | | https://reply.cash/bridge | Cross-chain bridge hub and entry to pair pages | | https://reply.cash/search | On-site search (routes, providers, chains, etc.) | | https://reply.cash/forex | Forex / rate-style landing; currency-specific variants use query `?to=CURRENCY` (e.g. `?to=KES`) | | https://reply.cash/docs | On-site docs overview, FAQs, links to docs.reply.cash | | https://reply.cash/blog | Blog index | | https://reply.cash/blog/:slug | Individual blog posts (slugs from sitemap / blogs data) | | https://reply.cash/whitepaper | Long-form narrative / whitepaper-style content | | https://reply.cash/brand | Brand guidelines, messaging, values | | https://reply.cash/demo | Demo | | https://reply.cash/waitlist | Waitlist | | https://reply.cash/terms | Terms of service | | https://reply.cash/aml | AML / compliance information | | https://reply.cash/deck | Pitch deck (lazy-loaded) | --- ## Country pages - **Pattern:** `https://reply.cash/country/:countrySlug` - **Purpose:** Per-country context: payments landscape, regulations summary (informational, not legal advice), corridors, providers, and SEO-friendly explanations of stablecoin → local money. - **Slugs used on the site (examples):** `kenya`, `nigeria`, `uganda`, `ghana`, `malawi`, `dr-congo`, `south-africa`, `rwanda`, `sierra-leone`, `botswana`, `ethiopia`, `mozambique`, `west-africa-uemoa`, `central-africa-cemac`, `brazil`, `colombia` - **Index:** https://reply.cash/countries --- ## Payment route pages (stablecoin → local currency SEO) - **Pattern:** `https://reply.cash/route/:currency` where `:currency` is a **lowercase** ISO-style currency code used by the site. - **Examples:** `/route/kes`, `/route/ngn`, `/route/ugx` (often marked live in sitemap), plus `ghs`, `mwk`, `cdf`, `zar`, `rwf`, `sll`, `bwp`, `etb`, `mzn`, `xof`, `xaf`, `brl`, `cop` (and similar) for roadmap corridors. - **Relationship to forex:** `/forex?to=CUR` uses **uppercase** tickers (e.g. `KES`) for filtered forex-style pages. --- ## Provider pages (M-Pesa, banks, OPay, etc.) - **Pattern:** `https://reply.cash/provider/:providerSlug` - **Purpose:** Deep pages for each payment method or rail: how sending works, limits, geography, links to related banks or routes. - **Known slugs (verify status on each page):** - `mpesa` - `airtel-money` - `mtn-momo` - `opay` - `nigerian-banks` - `telecel-cash` - `orange-money` - `tnm-mpamba` - `pix` - `breb` - `ussdnigeria` - `privacy-cash` - `apple-pay-us` - **Redirects:** `/ussd-nigeria` → `/provider/ussdnigeria`; `/privacy-cash` → `/provider/privacy-cash` --- ## Nigerian bank pages - **Pattern:** `https://reply.cash/bank/:bankSlug` - **Purpose:** SEO pages for sending to specific Nigerian institutions; content ties back to the **Nigerian banks** provider hub. - **Examples of slugs:** `access-bank`, `zenith-bank`, `gtbank`, `uba`, `first-bank`, `fidelity-bank`, `kuda`, `moniepoint`, `opay`, and dozens more (see sitemap). - **Hub:** https://reply.cash/provider/nigerian-banks --- ## Chain pages - **Pattern:** `https://reply.cash/chain/:chainSlug` - **Purpose:** Per-chain descriptions, supported assets, bridge relevance, and links toward app flows. - **Examples of slugs:** `solana`, `ethereum`, `base`, `bitcoin`, `arbitrum`, `polygon`, `optimism`, `avalanche`, `bnb-chain`, `ton`, `tron`, `near`, `sui`, `starknet`, `cardano`, `stellar`, `xrp`, and others (full set in sitemap). --- ## Asset (stablecoin) pages - **Pattern:** `https://reply.cash/asset/:assetTicker` - **Examples:** `usdc`, `usdt`, `xaut` --- ## Bridge pages - **Hub:** https://reply.cash/bridge - **From-chain hub:** `https://reply.cash/bridge/:fromChain` — e.g. `/bridge/solana` - **Pair route:** `https://reply.cash/bridge/:fromChain/:toChain` — e.g. `/bridge/solana/base` - **Note:** Sitemap chain slugs for bridge URLs use shortened forms in some cases (e.g. `bnb` vs `bnb-chain` on chain pages). If a URL 404s, use **/bridge** or **/search** to find the canonical pair path. --- ## Wallet pages - **Pattern:** `https://reply.cash/wallet/:walletSlug` - **Examples:** `phantom`, `solflare`, `backpack`, `jupiter`, `brave-wallet`, `trust-wallet`, `okx-wallet`, `metamask`, `hot-wallet` --- ## Search - **URL:** https://reply.cash/search - **Query parameters:** The UI supports filtering (e.g. by entity type such as providers, countries, chains). Use this when users need to discover the correct slug. --- ## Content freshness and limitations - **Live vs coming soon:** Country, route, and provider pages may show **status badges**. Assistants should not state a corridor is live without checking the latest page or official announcements. - **Rates:** Forex-style pages are for **education/SEO**; executable rates and fees are shown in the **app** at transaction time. - **Regulatory:** Country pages may summarize **VASP** or regulatory context **informationally**. Users needing legal advice should consult qualified professionals—not marketing copy. --- ## Related repos / projects (if user asks “where is the code?”) - The **reply.cash** landing experience is shipped as a front-end site (this repository’s `reply-landing` app). It is **not** the full backend settlement stack; the app and APIs are separate operational systems. --- ## File purpose This file is intended for **large language models, AI assistants, and automated agents** that benefit from a concise, honest map of reply.cash’s public marketing site, its main URL patterns, and the relationship between **marketing**, **app**, and **docs**. Last updated to reflect routing and sitemap structure as of the project’s `generate-sitemap.js` and `App.tsx` route table.