Most social discovery apps try to “recommend people” using closed databases and shallow signals.

Intori flips this model.

It turns Farcaster’s open social graph into a live matchmaking layer and that’s exactly why it cannot exist outside Farcaster.

Let’s break it down.

Intori is a Farcaster mini app that helps users discover meaningful connections.

Instead of random follow suggestions, Intori:

• asks users short questions

• turns answers into social signals

• recommends people with aligned interests

• lets users send “gifts” to spark interaction

• triggers native Warpcast notifications

It feels social because it’s built directly inside the social protocol.

Intori does not create accounts.

It uses Farcaster IDs (FIDs) as identity.

That means:

• one identity across all Farcaster apps

• no email logins

• no centralized user database

• instant social context

On Web2, Intori would need:

• account creation

• OAuth integrations

• identity linking

• platform permission approvals

This destroys frictionless onboarding.

Farcaster gives Intori native identity for free.

2) It Needs an Open Social Graph

Intori’s core feature is social matching.

That requires:

• follower relationships

• profile metadata

• engagement signals

• discovery context

Farcaster exposes this data openly at the protocol level.

On traditional platforms:

• follower graphs are locked

• recommendation systems are private

• APIs are restricted or paid

Without Farcaster’s open graph, Intori becomes blind.

Users open Intori directly from Farcaster:

• inside posts

• inside frames

• without leaving the app

This “social-native app distribution” does not exist on normal websites.

• No app store.

• No redirects.

• No installs.

That distribution channel is unique to Farcaster mini apps.

Now here’s the important part:

Farcaster is the protocol.

Neynar is the infrastructure layer that makes building practical.

Without Neynar, Intori’s team would need to build everything manually.

Neynar provides:

• Sign In With Farcaster

• managed signer flows

• secure identity verification

This allows Intori users to authenticate instantly using their Farcaster identity.

• No passwords.

• No email systems.

• No custom auth backend.

Neynar gives Intori easy access to:

• profile data

• follower lists

• cast history

• engagement context

Instead of running Farcaster nodes or indexing hubs, Intori can query everything through Neynar’s APIs.

This reduces:

• infrastructure cost

• development time

• maintenance complexity

When someone sends a gift or gets matched on Intori:

→ Warpcast notifications are triggered.

That’s powerful.

It means Intori doesn’t rely on:

• email campaigns

• push notification SDKs

• third-party messaging tools

Neynar makes protocol-native notifications accessible to mini apps.

To exist inside Farcaster, apps need:

• farcaster.json manifests

• embed metadata

• signature validation

• frame compatibility

Neynar App Studio and tooling handle this layer.

That’s why Intori can focus on product logic instead of protocol plumbing.

Intori is not “just another social app”.

It demonstrates something bigger:

Farcaster turns social networks into infrastructure. Neynar turns that infrastructure into developer-friendly building blocks.

Together they enable:

• composable social apps

• identity-native experiences

• protocol-level discovery

• permissionless innovation

Intori works because:

Farcaster provides identity + social graph + distribution

Neynar provides APIs + authentication + notifications + tooling

Remove either one→ The product breaks.

That’s what makes this stack special.

Most social discovery apps try to “recommend people” using closed databases and shallow signals.

Intori flips this model.

It turns Farcaster’s open social graph into a live matchmaking layer and that’s exactly why it cannot exist outside Farcaster.

Let’s break it down.

Intori is a Farcaster mini app that helps users discover meaningful connections.

Instead of random follow suggestions, Intori:

• asks users short questions

• turns answers into social signals

• recommends people with aligned interests

• lets users send “gifts” to spark interaction

• triggers native Warpcast notifications

It feels social because it’s built directly inside the social protocol.

Intori does not create accounts.

It uses Farcaster IDs (FIDs) as identity.

That means:

• one identity across all Farcaster apps

• no email logins

• no centralized user database

• instant social context

On Web2, Intori would need:

• account creation

• OAuth integrations

• identity linking

• platform permission approvals

This destroys frictionless onboarding.

Farcaster gives Intori native identity for free.

2) It Needs an Open Social Graph

Intori’s core feature is social matching.

That requires:

• follower relationships

• profile metadata

• engagement signals

• discovery context

Farcaster exposes this data openly at the protocol level.

On traditional platforms:

• follower graphs are locked

• recommendation systems are private

• APIs are restricted or paid

Without Farcaster’s open graph, Intori becomes blind.

Users open Intori directly from Farcaster:

• inside posts

• inside frames

• without leaving the app

This “social-native app distribution” does not exist on normal websites.

• No app store.

• No redirects.

• No installs.

That distribution channel is unique to Farcaster mini apps.

Now here’s the important part:

Farcaster is the protocol.

Neynar is the infrastructure layer that makes building practical.

Without Neynar, Intori’s team would need to build everything manually.

Neynar provides:

• Sign In With Farcaster

• managed signer flows

• secure identity verification

This allows Intori users to authenticate instantly using their Farcaster identity.

• No passwords.

• No email systems.

• No custom auth backend.

Neynar gives Intori easy access to:

• profile data

• follower lists

• cast history

• engagement context

Instead of running Farcaster nodes or indexing hubs, Intori can query everything through Neynar’s APIs.

This reduces:

• infrastructure cost

• development time

• maintenance complexity

When someone sends a gift or gets matched on Intori:

→ Warpcast notifications are triggered.

That’s powerful.

It means Intori doesn’t rely on:

• email campaigns

• push notification SDKs

• third-party messaging tools

Neynar makes protocol-native notifications accessible to mini apps.

To exist inside Farcaster, apps need:

• farcaster.json manifests

• embed metadata

• signature validation

• frame compatibility

Neynar App Studio and tooling handle this layer.

That’s why Intori can focus on product logic instead of protocol plumbing.

Intori is not “just another social app”.

It demonstrates something bigger:

Farcaster turns social networks into infrastructure. Neynar turns that infrastructure into developer-friendly building blocks.

Together they enable:

• composable social apps

• identity-native experiences

• protocol-level discovery

• permissionless innovation

Intori works because:

Farcaster provides identity + social graph + distribution

Neynar provides APIs + authentication + notifications + tooling

Remove either one→ The product breaks.

That’s what makes this stack special.