Dakota

• Name: Dakota
• URL: https://dakota.xyz/
• Category: stablecoin treasury and money-movement control plane
• Tags: ethereum-ecosystem
• Summary: Dakota is a regulated stablecoin treasury and money-movement stack for fintechs and enterprises that want programmable accounts, ramps, wallets, and payout workflows behind one API. The important point is not a new payment primitive. It is that Dakota bundles onboarding, recipient state, wallet policy, and rail abstraction into one operator surface.
• What it does:
  • Provides APIs for creating customers, onboarding businesses and individuals, and managing compliance-heavy money-movement workflows
  • Supports on-ramp accounts for accepting USD bank transfers and delivering stablecoins, plus off-ramp accounts for converting stablecoins into USD payouts over rails such as ACH and wire
  • Supports swap flows across blockchain networks and exposes supported-network metadata through the platform API
  • Offers non-custodial wallet infrastructure with policy controls alongside recipients, fiat destinations, crypto destinations, and transaction/event monitoring
  • Publishes a stable OpenAPI specification, sandbox and production environments, and official TypeScript and Go SDKs for integration
• Key claims:
  • Dakota’s official docs describe it as a “regulated stablecoin infrastructure platform” that enables fintechs and enterprises to embed programmable global money movement through APIs
  • The docs say Dakota can create stablecoin-backed business accounts, issue and manage wallets, orchestrate on- and off-ramps, move funds globally in real time, and automate money flows behind a unified API
  • The public API reference says Dakota exposes customers, wallets, transactions, and money-movement primitives, with a downloadable OpenAPI 3.0.3 specification and sandbox/production base URLs
  • Dakota’s SDK materials explicitly frame the platform around on-ramp, off-ramp, swap, and wallet flows rather than only simple API payments
  • The docs and SDKs show Dakota abstracting banking partners, custody, and blockchain infrastructure behind the scenes, which is a strong categorization signal that this is a stablecoin money-movement control plane rather than a generic fintech app
• Whitepaper: No classic standalone whitepaper or litepaper was found during this pass. The strongest primary materials were Dakota’s official site, docs portal, llms.txt, API reference, SDK docs, and public GitHub repos; see ../whitepapers/dakota-primary-sources-2026-04-26.md.
• Sources:
  • https://dakota.xyz/
  • https://docs.dakota.xyz/
  • https://docs.dakota.xyz/llms.txt
  • https://docs.dakota.xyz/api-reference/introduction
  • https://docs.dakota.xyz/documentation/sdks
  • https://docs.dakota.xyz/api-reference/info/get-supported-blockchain-networks
  • https://github.com/dakota-xyz
  • https://github.com/dakota-xyz/dakota-ts-sdk
  • https://raw.githubusercontent.com/dakota-xyz/dakota-ts-sdk/main/README.md

Internal linkages

• Best upward reads: bridge-xyz and coinflow.

Control surface

• Practical authority sits in onboarding approval, supported jurisdictions and networks, recipient records, wallet policy, transfer retries or halts, and bank-partner abstraction.

• That makes Dakota a treasury and money-movement control plane, not a canonical settlement layer.

• The sticky layer is the hosted workflow machinery around recipient state, compliance, routing, and payout execution rather than the stablecoin itself.

• Last reviewed: 2026-06-02 UTC