Soul

The AI community manager

Give your users each other.

Cards that arrive inside your app the way Wrapped does. Each one is one person worth meeting, and one question: yes or no.

New YorkThis week

Coffee, you and Mira1:1Devoción · you both run at dawn Thu 8:00am
Walk, you and Jonas1:1Brooklyn Bridge · both boulder Fri 6:15am
Track nightGroupMcCarren Park · 9 going Fri 7:00pm
Coffee, you and Ivy1:1Sey · both slow mornings Sat 9:00am
No-phone supperGroupFort Greene · 12 going Sat 7:30pm

Proposed by the agent. Both sides accept before either sees a name.

Our approach

Every consumer product now competes for the same attention on the same screen. Engagement is bought back each month, retention decays the moment spend stops, and the relationship a user has is with the feed rather than with anyone in it.

The durable alternative is other people. A product whose users have met each other offline does not churn the same way, because leaving costs a person their friends rather than an app. That is the strongest retention mechanic in consumer software, and almost nobody ships it, because running real gatherings has always been manual work that does not scale.

Soul makes it infrastructure. One embed reads the affinities a user already consented to share, works out which two of your users would actually click, and asks them both, one card at a time, inside the app they were already in. Nobody browses anybody. Nobody is asked to open a second thing. Both sides say yes before either sees a name, and then it is a coffee on a Tuesday. A layer any product can turn on.

How it works

ReadNormalized affinities, from the accounts a user already consented to connect, feed an agent that works out which two of your users would actually click. Not a feed of profiles to browse. One pairing at a time, with a reason behind it.The brain

DeckTheir cards arrive inside your app the way Wrapped does, and sit until they are answered or replaced. No new tab, no second app, nothing for anyone to remember to open. You choose when it appears: one call, Soul.present().The moment

MeetBoth sides accept before either sees a name. Then the card turns over: who they are, where, when, a way to say hello, and the coffee in their calendar. Mostly one to one. Larger gatherings when the room justifies it.Offline

Your ground, your accent, your corner radius. The form of the card is ours, because an introduction to a stranger should look like it came from somewhere.

The AI reads the signal. Never the raw data.

AffinitiesOnly normalized signals, early riser, house music, trail runner, derived from what a user chooses to connect. Never raw health, location or financial data.Not raw data

ConsentUser-consented through OAuth. Data minimization, right to delete, never sold, never posted. A data processing agreement for every partner.GDPR and CCPA

CustodyEncrypted on our infrastructure, or kept partner-side if you own the data. Deletable on request, never shared with third parties.Your choice

Every partner stays compliant. The brain never touches raw data.

One script tag. The whole layer.

See it first

One command, no account, no key. It writes a small app, wires the real SDK into it and opens the deck over it. Answer a card and the answer is a real write you can reload and find again.

curl -fsSL https://www.soulverified.com/sandbox | sh

Paste it

Anywhere you can put HTML. Webflow, Squarespace, Framer, a CMS field.

<script src="https://www.soulverified.com/sdk.js"></script>
<script>Soul.init({ partner: 'you' }); Soul.present();</script>

Or scaffold it

Detects your framework and writes the component, the env file and the README.

curl -fsSL https://www.soulverified.com/install | sh

Or hand it to an agent

Paste the reference into any coding agent. It reads the API and wires it up. No key needed.

https://www.soulverified.com/developers

The sandbox runs the same sdk.js against the same endpoints your app would, on real rows. Nothing here is a mockup, and nothing is trained on your users.

dattanikrishi@gmail.com