The Tapestry Identities API is the Engine Behind Better Products

Resolve Wallets into People: How the Tapestry Identities API Powers Smarter, More Social Web3 Apps

Sydney Iadarola
May 12, 2025

In the fragmented world of web3, identity isn’t just a profile, it’s the connective tissue that makes experiences coherent, portable, and personal. A wallet address alone says nothing about the human behind it. That’s where the Tapestry Identities API comes in.

As more products strive to become intelligent, social, and user-aware, resolving identity across wallets and namespaces is a prerequisite. The Identities API is helping teams transform raw, anonymous interactions into real, meaningful user experiences.

From prediction markets to dashboards, from social explorers to investment apps, teams are tapping into this API not just to look users up, but to build smarter, more social, and more personalized products.

This post introduces how the Identities API works and outlines the kinds of value it unlocks through examples from early adopters. Over time we’ll dive deeper into each use case with focused stories on how Jestr, SSE, Lore, and Opinions.fun implemented identity into their product logic.

The API

The Identities API is about resolution: turning inputs like a wallet address, phone number, or email into a richer understanding of who someone is and how they’re connected across platforms.

These endpoints return:

• All wallets and contact info linked to a user
• Profiles from 15+ (and growing!) apps in the Tapestry ecosystem including Lore, Jestr, and Opinions.fun
• User details like bios, usernames, and profile pictures
• A connected identity graph that helps you personalize and recommend smarter

By querying with a single identifier, developers can retrieve both a user's presence and their social context, enabling experiences that are more connected, trusted, and user-friendly.

Turning Data into Experience

The more your app understands who the user is, what they’ve done, and who they’re connected to, the more value it can deliver. Identity doesn’t just enrich, it unlocks.

Across the board, we’re seeing builders use the Identities API as a multiplier for:

• Social Layers for Data-Heavy Apps
  Products that benefit: Dashboards, explorers, aggregators, token-gated communities
  Example: Solana Social Explorer
• Reputational Signals for Trust-Building Apps
  Products that benefit: Prediction markets, investment platforms, lending protocols, P2P marketplaces.
  Example: Lore & Opinions.fun
• Multi-Platform Identity Linking
  Products that benefit: Wallet managers, composable profile layers, onboarding flows, "super apps"
  Example: Jestr
• Personalization Engines
  Products that benefit: Feed-based apps, messaging tools, content aggregators, recommender systems.
  Example: While not implemented yet in its full form, products like Opinions.fun and SSE lay the groundwork for socially-aware content surfacing.

Why Partners Are Reaching for the Identities API

Because it does one thing well: It turns users into people. With just a wallet address or a contact identifier, developers can resolve:

• Full user profiles (Farcaster, Twitter, email, phone)
• Connected wallets and contacts
• Social metadata like bios, usernames, images
• Cross-namespace identity graphs

And it works both ways—letting products start from any identifier (wallet, phone, email) and build up a picture of the person behind it.

• This is what Jestr needed to build social leaderboards.
• What SSE needed to make wallets browsable.
• What Lore needed to show trusted investors.
• What Opinions.fun needed to build social markets.

Build With People in Mind

Whether you’re building a wallet, game, network, or protocol, you’re going to need to answer this question: Who’s using it?

• The Identities API is how you turn that question into a feature—not a friction point. It helps your product understand your users better, and in turn, helps your users get more out of your product.

• If you want to build social-native, trust-aware, multi-platform experiences—this is the primitive you’ll want in your stack.

Check out the API Reference, or reach out to us directly to explore what identity-aware infrastructure can unlock for you!

Identities API Reference