Zoth

• Name: Zoth
• URL: https://zoth.io/
• Category: stablecoin neobank product family / yield-payments-spend stack / agentic-finance and tokenization surface
• Summary: Zoth at the project layer is the product family inside a broader Zoth company shell. The current docs still make the product side analytically useful: a privacy-first stablecoin neobank stack with application-layer Earn, Send, and Spend modules, agentic-finance tooling, tokenization / issuance packaging, and branded financial workflow components. The broader operator boundary now lives in zoth, which is the cleaner place to reason about licensing posture, compliance embedding, payment orchestration, onboarding, and the regulated-distribution shell above the products.
• What it does:
  • Packages a stablecoin-neobank application layer around Earn, Send, and Spend flows rather than around a single asset or wallet
  • Uses zVaults and curated partner products for yield-oriented treasury and savings workflow
  • Exposes privacy-preserving cross-border payment and remittance workflow with integrated on-ramp and off-ramp positioning
  • Extends balances into real-world spend through Zoth Cards and Zoth Corporate Cards, which the docs still place in the application layer even if some pieces are marked coming soon
  • Adds an Agentic Economy Solutions layer centered on Zocta plus tools for businesses and developers to build and deploy custom agents for payments, treasury operations, and capital coordination
  • Markets a broader financial-product bundle that includes stablecoin-launch and tokenization surfaces such as Stablecoin Studio, ZeUSD, PayX7, and FAAST in the Why Zoth framing
• Key claims:
  • The ecosystem docs describe five core offerings: Earn, Send, Spend, Agentic, and Zocta Points
  • The Why a Stablecoin Neobank page describes Zoth as a unified stack for a liquid yield asset, tokenization infrastructure, instant global payments, enterprise spend access, automated treasury/liquidity routing, embedded KYC / AML / KYB frameworks, and machine-native financial interfaces
  • The five-layer architecture says Layer 1 is the application layer, built around zVaults and curated partner products for yield, privacy-preserving cross-border payments, and card-based spend access
  • Layer 2 says Zocta is Zoth’s built-in AI agent and that the platform also offers tooling for custom agents, making the product family explicitly machine-facing as well as enterprise-facing
  • The Why Zoth page still markets a branded product cluster rather than one monolith, naming Stablecoin Studio, ZeUSD, PayX7, and FAAST as distinct parts of the stack
  • Taken together, the useful project-layer read is not one stablecoin but a bundled financial product family spanning yield, settlement, spend, tokenization, and agentic workflow
• Whitepaper: No canonical standalone whitepaper is the key artifact here. The strongest current sources are the homepage and docs corpus, with earlier source capture preserved in ../whitepapers/zoth-primary-sources-2026-05-07.md.
• Sources:
  • https://zoth.io/
  • https://docs.zoth.io/zoth/getting-started/the-zoth-ecosystem.md
  • https://docs.zoth.io/zoth/getting-started-1/why-zoth.md
  • https://docs.zoth.io/zoth/getting-started/why-a-stablecoin-neobank.md
  • https://docs.zoth.io/zoth/the-hierarchical-architecture/a-five-layered-integrated-financial-stack.md
  • https://docs.zoth.io/zoth/the-hierarchical-architecture/a-five-layered-integrated-financial-stack/layer-1-stablecoin-neobank-applications.md
  • https://docs.zoth.io/zoth/the-hierarchical-architecture/a-five-layered-integrated-financial-stack/layer-2-agentic-economy-solutions.md
  • ../whitepapers/zoth-primary-sources-2026-05-07.md

Internal linkages

• Company boundary for licensing posture, onboarding, compliance embedding, and payment-orchestration control: zoth.
• Useful product-side contrasts: m0, agora, plasma, and stable.

Protocol / company boundary

• Keep this note on the product family: neobank application modules, yield and payments workflow, card/spend surfaces, agentic-finance tooling, and tokenization or stablecoin-launch components builders or customers interact with directly.
• Use zoth when the useful question is who controls customer admission, the regulatory shell, supported jurisdictions, payment orchestration, compliance workflow, or the default commercialization path around those products.
• That split matters because what does the Zoth product stack expose? and which named operator governs access, policy, and regulated packaging around it? are related but not identical questions.

Control surface

• At the product layer, practical authority sits in how Zoth bundles yield products, payment workflow, spend access, agentic tooling, and tokenization modules into one financial stack.

• The wider admissions, licensing, compliance, routing, and commercialization shell now points upward to zoth.

• Read this note as the product family, not as the full operator story.

• Last reviewed: 2026-08-13 UTC