Introducing FabricBloc: The Onchain Stack for Developers and AI Agents

Shipping anything onchain today means stitching together five vendors: a wallet SDK, a bundler, an NFT API, an auth provider, and a paymaster. Each has its own keys, its own dashboard, its own bill, and its own way of breaking. The integration tax is real, and it is paid in weeks of engineering time before you write a single line of product code.

We have spent years building blockchain systems for enterprises and startups at BlocLabs, solving that same plumbing over and over. FabricBloc is what we built so no one has to solve it again.

What FabricBloc is

FabricBloc is the onchain stack: wallets, payments, NFTs, identity, and agents — five onchain capabilities behind one SDK and one bill. It is non-custodial by architecture and EVM-native.

Don’t pick five vendors. Pick the stack.

Instead of integrating and reconciling a fragmented toolchain, you get one platform that exposes the primitives every onchain app actually needs:

• Wallets — create and manage non-custodial wallets.
• Payments — move value onchain, including gas abstraction so your users don’t need to think about it.
• NFTs — mint, manage, and distribute tokens and digital assets.
• Identity — verifiable, portable onchain identity.
• Agents — the same capabilities, exposed to AI agents (more on that below).

Non-custodial by architecture

This is the part we refuse to compromise on. Keys, contracts, and assets belong to your customers and theirs — never to us. FabricBloc coordinates and validates; Ethereum settles. If FabricBloc disappeared tomorrow, what you built keeps working, because ownership never lived with us in the first place.

That is a deliberate architectural choice, not a feature flag. It is what lets enterprises build on a managed platform without handing over custody of their users’ assets.

What AI agents can expect

Here is what makes FabricBloc different from a normal Web3 SDK: the same APIs that power human developers also power AI agents.

Developers reach FabricBloc through native SDKs (TypeScript for web, React Native, and Node; Swift for iOS and macOS; Python for the backend). AI agents reach the exact same primitives over MCP (the Model Context Protocol) — the standard that lets assistants like Claude call tools directly.

In practice, that means an agent can:

• spin up and operate a non-custodial wallet,
• initiate and verify a payment,
• mint or transfer an NFT,
• check an onchain identity,

…all through one consistent interface, with the human still in control of their keys. As more software becomes agent-driven, the onchain layer — verification, signature, identity, ownership — is exactly the part that needs proof rather than guesswork. FabricBloc is the substrate those agent actions flow through.

What we’re rolling out

We are opening early access to FabricBloc:

• the SDKs and APIs across all five primitives,
• an MCP server so AI agents can call those primitives directly,
• and a console to configure, orchestrate, and monitor it all.

We’re onboarding early teams deliberately so we can build alongside real use cases — enterprise payments, agent-driven apps, NFT and identity products, and the long tail of “we just need onchain to work” projects. If you’ve read this far, you’re probably one of them.

Get early access

If you’re building an onchain product — or an AI agent that needs to act onchain — and you’d rather ship features than integrate five vendors, we’d like to talk.

Request early access to FabricBloc →

Tell us what you’re building and we’ll get you set up. You can also explore our blockchain API services and see the work we’ve delivered for clients across DeFi, NFTs, DAOs, and enterprise infrastructure.

FabricBloc is built and operated by BlocLabs. Learn more at fabricbloc.com.