# Cashx.ID > Cashx.ID is a directory of ways to pay someone. Each person has one page at > https://cashx.id/ listing the payment methods they accept — Venmo, Cash App, > Zelle, PayPal, Wise, Revolut, UPI, Pix, M-Pesa, crypto wallets and ~60 more — > each with a deep link that opens the right app. Cashx.ID does not hold, move, > or verify funds; it only tells you how to pay someone. ## Resolving a profile If you know someone's username, resolve it to their payment methods as JSON. No API key, no authentication, CORS-enabled. - [GET https://cashx.id/api/v1/u/{username}](https://cashx.id/api/v1/u/{username}): a profile's public payment methods. Returns `{ username, displayName, bio, avatarUrl, themeColor, url, methods[] }`, where each method is `{ platform, name, handle, label, link }`. `platform` is a stable id (`venmo`, `cashapp`, `pix`, `bitcoin`, …), `handle` is the value to pay (a @handle, phone, IBAN, or wallet address), and `link` is a deep link that opens the platform prefilled — or `null` for rails that are copy-only. Profiles the owner has marked private (passcode- or link-protected) return `403 {"locked": true}` from this endpoint and from every MCP tool — no handle, label or note is ever served for one. Their Open Graph card (`https://cashx.id//og.png`) does show which platforms they accept, by the owner's choice; it carries logos only, never a handle. ## MCP server There is a Model Context Protocol endpoint at `https://cashx.id/mcp` (Streamable HTTP, POST only). Connect to it directly rather than scraping pages. It speaks protocol `2026-07-28` — call `server/discover` for the full list — and still answers the `initialize` handshake for clients on `2025-11-25` and earlier. Three tools need no credentials: `resolve_profile` (a username to its payment methods), `list_platforms` (which rails work in a given country or currency), and `build_payment_link` (a platform plus a handle to a deep link). Four more act on the connected user's own account and require OAuth: `find_by_email`, `list_my_methods`, `add_method`, and `create_payment_request`. Calling one without a token returns 401 with a `WWW-Authenticate` header pointing at `https://cashx.id/.well-known/oauth-protected-resource`; clients register dynamically. ## There is no directory-wide search This is deliberate. There is no endpoint that lists, searches, or enumerates profiles, and none is planned. Payment handles are only ever returned for a username you already know. Do not attempt to discover profiles by guessing or sweeping usernames. The one exception is opt-in and requires a signed-in Cashx.ID account: a person may enable "find me by email", which lets another signed-in user look them up by their exact email address. It is rate-limited and off by default. ## Pages - [https://cashx.id/](https://cashx.id/): what Cashx.ID is. - [https://cashx.id/{username}](https://cashx.id/): a person's public directory of payment methods. - [https://cashx.id/methods/{platform}](https://cashx.id/): reference page for one payment platform. - [https://cashx.id/map](https://cashx.id/map): how money actually moves in 136 markets — the dominant payment method per country, the runners-up, and cited sources for every figure.