Stables primary sources — 2026-04-30

Project status in this pass

• No canonical standalone whitepaper or litepaper surfaced.
• The clearest current source of truth is the official docs corpus, llms surfaces, and the first-party MCP server repository.
• Several direct docs-page fetches returned a Cloudflare block during this pass, so the accessible llms.txt / llms-full.txt surfaces were especially important.

Primary-source snapshots

1) Docs index / llms.txt

• URL: https://docs.stables.money/llms.txt
• Key excerpt:
  • Enumerates first-party surfaces across customer types, identity verification, entitlements, compliance, country restrictions, transfers, virtual accounts, limits, fees, API keys, and webhooks.
  • This was the fastest way to confirm Stables is exposing a broad payment-and-compliance platform rather than a single transfer endpoint.

2) Docs corpus / llms-full.txt

• URL: https://docs.stables.money/llms-full.txt
• Key excerpt:
  • Opens with “Build compliant stablecoin payments infrastructure” and says Stables provides “APIs and tools for developers and agents to move money globally - securely and at scale.”
  • Describes Stables as “the infrastructure layer for stablecoin-powered payments.”
  • Says developers can build send/receive flows and instantly issue USD, EUR, and AUD virtual accounts with local bank details.

3) Customer onboarding quickstart (captured through llms-full.txt)

• URL: https://docs.stables.money/
• Key excerpt:
  • Says a Stables customer is an end user of the business and that every action is tied to the customer.
  • Explains that customer creation is the first step before value can move.
  • Says entitlements plus KYC/KYB data are required before customers can transact.

4) Payment / transfer quickstart (captured through llms-full.txt)

• URL: https://docs.stables.money/
• Key excerpt:
  • Describes the Transfer API as enabling conversion between supported fiat and cryptocurrency currencies.
  • Explicitly says the currently documented transfer flow is crypto → fiat (off-ramp), with other transfer types “coming soon.”
  • Directs developers who need stablecoin receipt and payout today toward Virtual Accounts.

5) Webhooks quickstart (captured through llms-full.txt)

• URL: https://docs.stables.money/
• Key excerpt:
  • Documents webhook subscription creation, event-type registration, and realtime notifications for customer, KYC, and payment events.
  • Recommends signature verification using HMAC-SHA256 and idempotency keyed by eventId.
  • Shows that operational event handling is part of the core platform surface.

6) Sandbox guide (captured through llms-full.txt)

• URL: https://docs.stables.money/
• Key excerpt:
  • Says the sandbox base URL is https://api.sandbox.stables.money.
  • Notes that the sandbox is functional for customer creation and KYC testing.
  • Reinforces that Stables is already packaging a developer-testing environment, not just production APIs.

7) MCP server README

• URL: https://raw.githubusercontent.com/stables-money/mcp-server/main/README.md
• Key excerpt:
  • Describes the project as an MCP server exposing the Stables fiat-to-crypto API to AI agents.
  • Says AI assistants can manage customers, create quotes, execute transfers, and handle virtual accounts programmatically.
  • Lists 25 tools across customer management, quotes, transfers, virtual accounts, API keys, webhooks, and notifications.

8) MCP server package metadata

• URL: https://raw.githubusercontent.com/stables-money/mcp-server/main/package.json
• Key excerpt:
  • Publishes the package as stables-mcp-server with homepage https://docs.stables.money.
  • Describes it as an MCP server for the Stables fiat-to-crypto API enabling AI agents to manage customers, quotes, and transfers.
  • Reinforces that agent-facing access is a first-party maintained surface rather than a third-party community wrapper.

Working conclusion

Stables is best cataloged as a compliance-heavy stablecoin payments and virtual-account control plane. In this pass, the most revealing primary sources were the docs llms corpus and the first-party MCP repository, which together exposed customer/compliance onboarding, off-ramp transfer flows, virtual-account issuance, webhooks, sandbox support, and agent-facing tooling.