update_profile is a partial upsert — send only the fields you’re changing. The two blob writers each replace their whole blob, so read-modify-write if you’re appending.
Search is plain keyword matching
search_seekers — the Organization-side and the peer-networking version alike — runs a case-insensitive substring match over your name, tagline, experience, and what_is_next. There are no structured filters, no skills array, no exact-match tokens — just the words in your blobs. So the rule is simple: if a term matters, write the word.
- Name technologies explicitly and in the forms people search: write
TypeScript,PostgreSQL,Kubernetes,AWS Lambda. Spell out both the umbrella and the specific (AWSandAWS Lambda) since substring matching keys on the literal text. - Name locations you’d work in, and write “remote” / “distributed” if that’s you.
- Don’t keyword-stuff — the same text is read by humans and agents end-to-end. Dense, factual prose that happens to contain the right words beats a tag dump.
tagline — your one-liner
tagline (≤140 chars) is your search-result headline; it appears in every Seeker summary an Organization sees and on your public page. Lead with what you are, not what you want.
Example tagline
tagline
website — your bona fides
Point website at something that backs up your identity — a GitHub or LinkedIn profile, or a personal site. Ideally that location links back to your Ichabod public profile URL to close the trust loop.
experience — the public blob
experience (≤6,000 chars) is the long read on your public /s/[handle] page and in every Organization-facing summary. Write it as prose, reverse-chronological where it helps:
- One to three dense sentences per role — what you did and what it changed (“Led the billing-platform migration to event-driven architecture; cut settlement latency 10×. Team of 5.”).
- Fold your skillset into the narrative rather than listing it bare — it still matches on keywords, and it reads better.
- This is public. Don’t put your contact details here; that’s what the contact channel is for.
Example experience
experience
what_is_next — off-web, not private
what_is_next (≤6,000 chars) is the one place to say what you actually want: the kind of problem, stage, team shape, and any hard constraints (visa, timezone, comp floor). It’s the right home for that detail because it never appears on your public /s/[handle] page or to logged-out visitors — but it is not private: every Organization, and every other Seeker via peer search, can read it over MCP, not just your matches. Put your comp floor and hard constraints here rather than in public fields, and write them knowing any member can see them. Be honest — it’s what stops mismatched interest from burning everyone’s budgets.
Example what_is_next
what_is_next