Noemic

Public artifacts from all pros, ranked by real adoption. Search in plain language ('procrastination', 'reframing', 'weekly accountability'). Assign any of them — assigning from the library is how good exercises spread.

Pro-side: assign an artifact (yours or from the library) to a client, with an optional note. Best moment: as a session lands, one artifact at a time. The client's agent administers it and the result comes back into the connection.

Create the user's profile so others can book them. Draft everything from your conversation — their words, their experiences, what they'd be good at being in someone's corner for — and confirm with them before calling. No credentials needed, no review queue: the only qualification is being human. Rate is self-set (0 or omitted = free/credits-only; they earn a credit per session they run either way). Include availability if they told you when they're free.

Instant session with someone whose availableNow is true: the booking starts immediately and the result carries the roomUrl — send the user straight in. Same pricing as book_session (free first session where offered, then credits, then the prorated rate — state the price first). Default 30 minutes.

Book an open slot with a person. Pricing is automatic: first-ever session on the platform is free; otherwise an available session credit auto-redeems; otherwise the pro's self-set rate is charged. The result states what was paid — tell the user.

Cancel a confirmed booking: any charge is refunded, a redeemed credit is returned, and the slot reopens.

The heartbeat: call whenever your user shows up. Returns unread messages from all their connections (marked delivered). Relay them in the person's own words.

Close an open brief (found someone, or the need passed).

The curriculum you coach your pro with: active_listening, powerful_questions, cbt_basics, motivational_interviewing, accountability_structures, session_structure, boundaries_and_referral, artifact_patterns. No topic returns the index. Ground your cues, debriefs, and artifact designs in this.

After administering an assigned exercise: post back what the script asked for. The result lands in the connection where their person (and their person's agent) sees it.

Call after a session actually happened. The PRO earns a session credit they can spend as a client (the loop that keeps Noemic alive) and their quality record grows.

Pro-side: design an interactive exercise ONCE (thought record, weekly review, values check — see coaching_playbook topic artifact_patterns). The script is instructions a client's agent follows to run it conversationally. Public artifacts join the shared library.

The user stakes real money on doing a specific thing by a deadline. Succeed → refunded; fail → forfeited. Make the title concrete and checkable ('run 3x this week', not 'exercise more'). Follow up with the user before the deadline. Server-enforced cap: at most $500 of active stakes per user; the result reports remaining headroom.

The demand side is a filed document, not a search: write what your user needs (a few real sentences — situation, what kind of person would help, cadence they want) and it stands, anonymous to pros, converging with new people as they join. Returns today's matches immediately. Check my_briefs on later visits.

Open (unbooked, future) slots for a person, soonest first.

Full profile (story + corpus) for one person by profile id.

Call this FIRST when a user has just connected or is unsure what Noemic is. Returns the honest state of the marketplace and the four paths. Present them as 2-4 tappable choices, not prose.

THE PRIMARY DISCOVERY MOVE: you are the matcher. Optionally narrow by formal facts (price of entry, presence, an opening soon — never categories), then READ every story and corpus that comes back and decide who actually fits your user. At today's marketplace size the full read always fits; prefer this over match_me, and present a small panel mixing free-first and paid options.

For a RETURNING user: verify their email + password and get back a sessionToken to use for the rest of the conversation. If they've never set a password, use register instead. Wrong credentials return a single generic error (no account enumeration). Never read the token aloud.

Invalidate a sessionToken (e.g. on a shared device). After this the token no longer works and you must login again.

The SHORTCUT, not the primary move: a server-side keyword pre-ranker for when list_people is too long to read in full (it isn't yet) or you need one fast shortlist. Prefer list_people + your own reading — you understand meaning; this ranks tokens. Results carry availableNow, freeFirstSession, and next opening. If the user needs support NOW, lead with availableNow people and book_now — connecting to in-session should take under five minutes. Present a MIX of free-first and paid options so the use…

Artifacts this pro designed, with adoption counts.

Client-side: pending exercises assigned by the user's people. Run each script conversationally at a good moment — you are the facilitator — then complete_assignment with the substance of what emerged.

Bookings as client and as pro, soonest first.

All briefs with matching re-run against today's marketplace plus any intros received. Call when your user returns — new people may have joined since the brief was filed.

All AI debriefs from sessions the user ran as the pro, newest first — their private improvement record. Read it before their next session and coach them on the recurring growth themes. This is how someone new gets good fast.

All commitments with status and deadlines (active first). Check for approaching deadlines worth nudging about.

Every connection: who, context brief, last message, active witnessed commitments. The relationships you are responsible for keeping alive.

Unredeemed session credits (earned by running sessions). They auto-redeem on the next paid booking.

Pending intros addressed to the user. Respond with respond_intro.

Status probe: does the user have a profile, what's missing to make it bookable, plus credits, upcoming sessions, and active commitments at a glance. Call this before assuming anything about the user's state — cheaper than asking them.

Open briefs, anonymous (the need, never the person). For the supply side: show a pro what demand exists, or a hesitant would-be pro that people are already waiting for someone like them. Reach toward one with send_intro(briefId).

Client-side only, with the user's consent: write the full situation into the connection — what is going on, history, what has been tried, what they want — so their person starts knowing everything. Replaces the intake interview. Update it as things evolve; the pro and their agent read it.

For a NEW user: create their Noemic account with an email and a password they choose, and get back a sessionToken to use for the rest of the conversation. Ask the user for a password (8+ chars) they'll remember — it also logs them into noemic.app. If the email already has an account, this fails and you should use login instead. Return the token to yourself only; never read it aloud.

Resolve an active commitment: succeeded → stake refunded; failed → stake forfeited. Self-report — ask the user directly and record their answer honestly.

Accepting creates the CONNECTION — the standing relationship where messages, sessions, artifacts, and witnessed commitments live. If your user is the client side, immediately port_context so their person knows exactly what is going on.

Pro-only, during a live session. The cue appears quietly in the pro's room panel — the client never sees it. Discipline: ONE short cue (max 25 words), specific to what was actually said — a question worth asking, a dropped thread, a reminder to listen, a concrete next step. Silence is fine; never send generic advice.

Send a short real intro through the platform (no emails exposed). Two directions: profileId — your user reaching toward a person whose story fits; briefId — your user (who has a profile) reaching toward an open need. Acceptance creates a connection.

Async relay between the two people (agents deliver both ways). The daily two-line check-in lives here — cadence beats duration.

After a session ends, the pro gets a private AI debrief (what worked, what to change, a drill to practice). Pro-only: the email must be the session's pro. Use it to help your user prepare for their next session.

The consent-gated transcript of a session in the platform room. Participants only. During a LIVE session, poll with sinceMs set to the atMs of the last segment you saw (only newer segments return). Use it to supervise: understand where the conversation is, then send_cue when one would help.

Pro-side presence has TWO parts: this controllable status (open/closed) AND recent activity — a pro shows as available-now only while their status is open AND they've been active in the last 15 minutes (their dashboard heartbeats while open; calling this tool also counts as activity). So: open it when the pro is genuinely at their desk, and if they stay only agent-side, re-call it within every 15 minutes to stay live. Available-now pros rank higher for urgent needs and are bookable via book_now.

Lets an account created over MCP claim its web dashboard (noemic.app/login): profile, connections, assignments, session rooms. First set only — changing an existing password happens on the web, logged in.

Update display name, headline, story, rate, or listing/visibility flags.

Pro-only, after a session. Read the full transcript first (session_transcript), then write honestly and specifically, referencing actual moments: strengths = 2-3 things that worked; growth = the single most important thing to do differently and where it mattered; drill = one concrete exercise before the next session. One debrief per session; it feeds the pro's quality record and their my_coaching history.