NewWallets, tokens, NFTs, and vaults are live. RPC nodes coming soon.

See the stack →

Use cases

Who builds on FabricBloc.

We launched in 2025. Case studies land when customers do. Until then, here's the stack — judge the docs.

Use cases

Built for teams who ship.

We launched in 2025 — case studies land when customers do. Until then, worked examples of what ships on the stack today: wallets, tokens, NFTs, vaults, and agents.

  • Ship embedded wallets behind your existing login. Users get non-custodial accounts — no seed-phrase screens, keys stay with the user.

    Fintech teams Embedded wallets
  • Lazy-mint loot as NFTs with sponsored gas. Players claim without a wallet prompt or a gas fee.

    Gaming apps NFTs + gas sponsorship
  • Charge recurring on-chain USDC subscriptions instead of bolting a card processor onto a crypto product.

    Fintech teams USDC subscriptions
  • Native account abstraction means signup looks like signup. The wallet is created under the hood on first use.

    Mobile-first products Account abstraction
  • FabricBloc is EVM-only today. We would rather say that here than have you find it in a migration ticket.

    Honest limits EVM
  • FabricKit on iOS and the TypeScript SDK share one API shape, so mobile and backend teams stop translating between vendors.

    Mobile-first products iOS + TypeScript SDKs
  • Issue a points token with transfer rules from one API. Balances, transfers, and history come from the same SDK.

    Loyalty programs Tokens
  • Mint and manage tokens from Studio for macOS — routine asset operations without an engineering ticket.

    Business owners Studio
  • Support staff debug user wallets with read-only scoped keys that cannot touch funds.

    Enterprise pilots Scoped keys
  • npm i @fabricbloc/sdk, then the quickstart takes you from signup to a first signed transaction. The docs are the proof — start there.

    Every team Quickstart
  • Point a Claude agent at the MCP server. It reads balances and signs within policy through scoped keys — no key material in your code.

    AI-agent developers MCP server
  • Route creator payouts through vaults and tokens. Deposit, withdraw, audit — via API, with no Solidity contract to write.

    Creator platforms Vaults
  • Give each agent exactly the permissions it needs. Spend limits are enforced at the key level, not in your application code.

    AI-agent developers Scoped keys
  • NFT drops, royalties, and payouts on platform primitives — one SDK instead of stitching three vendors together.

    Marketplaces NFTs + vaults
  • Prototype on the free tier, then upgrade without changing a line — free and paid run the exact same API.

    Founders Free tier

See it for yourself.

Request access to the beta. We onboard teams in waves.