Jev directory
CommunityJev Agents & MCP
Meety
iMessage networking agent for Luma events that uses Jev as its match classifier, ranking attendees against a user's event goal and answering live should-I-talk-to-this-person questions with probabilities.
- Stars
- 1
- Reading time
- 2 min
- Published by
- Community
- Added
- Oct 2026
Highlights
- iMessage networking agent for Luma events that ranks attendees against a user's event goal.
- Uses Jev as the core match classifier, returning match, probability, reason, and conversation starter.
- Supports live iMessage Q&A such as whether to talk to a specific person at an event.
- Built for JEVATHON, the Jev Hackathon SF at CodeRabbit HQ on September 26, 2026.
- Combines Supabase storage, Photon iMessage messaging, Luma attendee data, and LinkedIn/X signals.
Questions about this entry
Short answers drawn from the linked project or page.
Meety is an iMessage networking agent that combines the attendee's profile, event-specific goal, and other attendees' public/social context to rank who to meet before and during a Luma event.
Jev is the core match classifier. Meety sends it the user's profile summary, event goal, event context, attendee data, and a strict response schema, then uses Jev's output for pre-event ranking and live iMessage Q&A.
The expected JSON includes match as a boolean, probability as a number, a reason, a best_conversation_starter, and confidence such as high; the digest shows an example with match true and probability 0.82.
It collects attendee context including LinkedIn, X, email, about text, and recent posts, and uses Tavily or web research for background enrichment of user and attendee summaries.
Photon provides the iMessage messaging layer for onboarding, reminders, match delivery, and live Q&A; Meety sends top matches over iMessage before the event and answers live questions in the room.
Supabase handles sign-up, user records, session state, and persisted event and match data, according to the workflow and tool stack described in the digest.
Browserbase or browser automation is used for user-authorized Luma access and attendee-list scraping where the event exposes the list, so events without an exposed list are a stated limit.
From the Jev guides
Original write-ups on what this entry is for.
From the Jev AI model community
Posts from builders shipping with Jev right now.