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

See the stack →
Onchain creation for mobile

Create onchain products with APIs or Studio.

Build with FabricBloc APIs across iOS, Android, REST, and MCP, or create visually in Studio for macOS. Wallets, tokens, NFTs, vaults, and agent rails stay under one platform.

iOS · FabricKit Android · FabricKit Python / TypeScript SDK REST · MCP
Base
Polygon
Arbitrum
Optimism
Solana
BNB Chain
One FabricBloc platform
wallets · tokens · NFTs · vaults · agents

Built for teams shipping onchain

  • Fintech teams
  • Gaming apps
  • Marketplaces
  • Loyalty programs
  • Creator platforms
  • AI agents

Build with intent

Each primitive, working as intended.

The animation in every card mirrors what the code does. Embedded wallets create themselves. Agent permissions get granted. Charts stream live.

Wallets-as-a-service

Embedded wallets in three lines.

Non-custodial. iOS + TypeScript SDKs. Created inside your app — no redirects, no seed phrases for users to lose.

Tokens

Issue ERC-20s at scale.

Mint, sponsor gas, enforce transfer policies.

MINT THROUGHPUT

Agent rails

Permissions, scoped.

MCP-native. Claude-ready. Agents read, sign, and orchestrate within your policy.

~/agent.ts
$ run

Analytics

Onchain telemetry, in real time.

Balances, transfers, throughput — streamed to your dashboard.

VOLUME TREND

Networks

One SDK. EVM-native.

Ethereum, Base, and Polygon today. Configure with a single string.

Ethereum
Ethereum
Base
Base
Polygon
Polygon
New · Agentic finance

Give agents scoped onchain capabilities.

MCP server, Claude and Codex integrations, and scoped key permissions let agents read balances, sign transactions, and orchestrate vaults without broad wallet access or secrets pasted into config files.

{
  "fabricbloc": {
    "command": "bun",
    "args": ["x", "@fabricbloc/mcp"]
  }
}

No surprise bills

Pricing for API builders and Studio creators.

Free tier in invite-only beta. Predictable PRO. Enterprise on demand.

Checking subscription service

Loading current tiers...

Pricing comes from the live subscription API, not copied site data.

Launch scenarios

What teams can create with FabricBloc.

Real patterns from API and Studio teams. Named case studies coming as customers approve them.

Consumer fintech

Create wallet-backed accounts without stitching vendors.

Create embedded wallets, sponsor first transactions, and expose balances through one API surface instead of separate wallet, key, token, and RPC contracts.

Prototype path: wallets, gas policy, rewards token

Marketplace app

Turn loyalty points into programmable assets.

Issue rewards, gate redemptions, and let support agents top up or reverse balances with scoped permissions instead of direct wallet access.

Prototype path: tokens, webhooks, agent-safe operations

Mobile game

Launch owned inventory without forcing crypto UX.

Mint items behind familiar account flows, hide seed phrases, and keep collection metadata, wallets, and claim flows under one product contract.

Prototype path: wallets, NFTs, sponsored claims

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

Start creating onchain.

Use an API key for iOS, Android, REST, and MCP, or open Studio for macOS.