PayBito infrastructure knowledge helper for AI agents — injects PayBito API expertise (Resources + Prompts, no live actions) into any MCP-capable AI platform.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"paybito-mcp-2","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# PayBito MCP — AI Integration Knowledge Helper A **knowledge helper** that injects PayBito infrastructure expertise into any AI coding agent, so a developer can implement PayBito integrations (websites, exchanges, payment flows, trading apps) in natural language. > It is **not** an action executor. It never calls PayBito's live API, never moves funds, > never reads balances. It serves *documentation and code guidance* so the AI writes the > correct integration code for you — the same way the `frontend-design` skill makes an AI > produce great UIs without "running" anything. Built from **all 6 of PayBito's published OpenAPI specs** (1,344 endpoints → **1,058 unique operations** across 28 domains and 6 hosts), normalized into one clean model. ## What it exposes | Surface | Contents | For | |---|---|---| | **Resources** | `paybito://overview`, `paybito://modules`, `paybito://auth`, `paybito://domains`, `paybito://domain/{slug}`, `paybito://operation/{id}`, `paybito://playbook/{name}` | Clients that read MCP resources (Claude) | | **Tools** (read-only) | `paybito_overview`, `paybito_modules`, `paybito_search` (accepts a `module` filter), `paybito_get_operation`, `paybito_get_domain`, `paybito_get_auth`, `paybito_list_playbooks`, `paybito_get_playbook` | Clients that only invoke tools (ChatGPT, Cursor, Gemini, …). These return **documentation only**. | | **Prompts** | `integrate_paybito`, `add_payment_button`, `spot_trading_code` | Guided workflows | ### Product modules (so a prompt hits the right API) **STEP 0 — the AI asks the developer one question first.** PayBito serves several audiences with overlapping endpoints, so the most reliable router is the developer's own answer: *"What are you building?"* — - **(a)** an app for the **PayBito App Store / dev console** → PayBito host; - **(b)** **crypto payments** into your own existing site/product (a **merchant**) → your own domain; - **(c)** your **own branded white-label platform — exchange and/or payments** (a…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.