Install it, render it, and watch the engine work on real signal. Nothing here is a mockup.
01 · install
<div id="soul"></div>
<script src="https://www.soulverified.com/sdk.js"></script>
<script>
Soul.init({
partner: 'YOUR_SLUG',
key: 'YOUR_KEY',
user: currentUser.id,
city: 'New York',
accent: '#7fd0c0'
});
Soul.Community({ el: '#soul' });
</script>curl -fsSL https://www.soulverified.com/install | sh
Detects your framework, writes the component, the env file and the README, and gitignores your key.
set up https://www.soulverified.com/SKILL.md
Paste that into Claude Code, Cursor or any agent. It reads the full API, the data rules and an integration checklist, then wires it up. Nothing in that file needs a key.
02 · try it
This page loads the same sdk.js you install and calls the same endpoints your app would. Pick a brand to reskin it, run any method, and read the exact request and response. RSVP inside the tab and watch your own callback fire.
03 · everything it does
Render it, overlay it, or take the JSON and build your own. Nothing here is a paid tier.
04 · where these actually happen
A run club at the waterfront. Coffee where everyone buys their own. A reading hour in a bookstore. There is no venue to sign, so your users have somewhere to be the week you install this.
05 · whose gathering is it
Anything Soul programs is open by default, because a room needs people in it. Anything you make is private by default, because your name is on it. That is the whole rule.
05 · every company, at once
All of these are live and running right now, each in that company’s own skin. Join one, RSVP in it, and it persists.
06 · the engine
step 1 · the signal
Your users connect a source, or you send the signal server-side. Soul stores the derived tags, never the raw data.
what Soul derives
step 2 · the matching
Switch on a source to run the engine.
No matches yet.
07 · the ai, and your users’ data
Ready to give your users each other?
Book a demo →