Kevin Guide

Kevin is a free, text-only public network you use from inside ChatGPT, with a read-only website alongside it.

Kevin is a small public network made of text. You use it by talking to ChatGPT: you ask for a room, a profile or the News and Kevin answers, and you write by telling Kevin what to post. The website kevinchat.com is the paper copy — it reads along, it never writes. Four things describe the whole product: you talk with people in public rooms, you keep a small public profile, you publish projects and events that stay findable, and you ask Kevin what is going on. Kevin is text-only on purpose: no images, no profile pictures, no uploads, no downloads and no file storage anywhere.

• —Everything you write in a room or publish on your profile is public.
• —Kevin has no direct messages and no private rooms.
• —Writing always happens in ChatGPT; the website is read-only.

One global public room plus one public room per profile. Every message is physically deleted 30 minutes after it was posted.

There is exactly one global room where everybody can write, and every profile has its own public room. Both are public: anybody can read them, in ChatGPT or on the website. Every message is physically deleted 30 minutes after it was posted — not hidden, not archived, removed by a scheduled job — so a conversation is something you take part in, not something you scroll back through. You can reply to a message and you can mention someone with @handle; both are what makes a conversation hang together when the room is busy. A room shows a bounded number of recent messages, and when a room is busy Kevin puts people into small stable conversation groups so the room stays readable instead of turning into noise. You can delete your own message at any time, and inside your own profile room you can delete any message or clear the whole room.

• —A deleted message cannot be recovered — not by you and not by Kevin.
• —Kevin stores the text you wrote, never a translation of it.
• —Nothing you write in a room is private.

A small public profile with a unique handle, plus follows, one like per profile, blocking and a pull-based activity inbox.

Your profile is deliberately small: a name, one unique handle, a short bio, a language and a handful of public links. It is free, and it is the thing other people and other assistants read. You can follow a profile to see its activity, and you can like a profile exactly once — there is no like count race, no score and no ranking of people. Blocking is a personal control that takes effect immediately: it removes follows and likes in both directions and hides you and the other profile from each other. Activity is pull-based: it exists when you ask for it. Kevin sends no background push notification and shows no badge chasing you. Profile views are counted anonymously as a total only — Kevin never records who visited a profile or when.

• —Profile views are a total counter only: no visitor identities, no timeline.
• —Blocking is separate from reporting and only affects you and the blocked profile.
• —Your profile, links, follows and likes stay free forever.

Structured entries you publish on your profile. Creating, editing, publishing, sorting, hiding, exporting and deleting are all free.

An entry is a structured thing you show: a project, an artwork, an event or a custom entry. It has a title, a description, tags, its own links and, for an event, a date. Entries are informational presentations, not shop listings: there are no prices, no cart, no orders, no ticketing and no payment between people anywhere in Kevin. The lifecycle is simple. You create an entry, it starts hidden, you edit it until it is right, and then you publish it. A published entry appears on your public profile, in Discover and in the public indexes; unpublishing takes it straight back out of public view without touching its content. Creating, editing, publishing, sorting, hiding, exporting and deleting your entries are all free, so nothing ever locks you out of your own work.

• —Entries carry no price, offer, booking or checkout field of any kind.
• —A new entry starts as a private draft; only publishing makes it public.
• —Unpublishing, exporting and deleting are always available.

The public list of people and the work they published, ordered by what is recent — never by popularity.

Discover shows people who published something and the projects and events they published. The ordering is deliberately boring: recent first. There is no popularity ranking, no trending score, no engagement weighting and no promoted position mixed into it. Discover reads only published, public data, so anything you can see there is something somebody chose to publish. Unpublishing an entry takes it out of the public indexes immediately; nothing about it is deleted.

• —Loudness is not relevance: Kevin does not rank people against each other in public.
• —Discover never contains room messages — those are gone after 30 minutes.

An aggregated picture of what the network is talking about, derived only from Kevin's own public activity.

News answers the question 'what is going on here right now'. It is built from Kevin's own public activity: the topics people are writing about, the projects and events they published, and how busy the network is. It is always aggregated and never about one named person, and every topic links back to the public profiles, projects and events it came from. News has no editorial staff, no outside world coverage and no opinion. When the network is quiet, News says it is quiet — it never invents activity, trends or numbers to look busy.

• —News never reports on an individual person.
• —Nothing appears in News that cannot be traced to public, published data.
• —Kevin does not fetch outside news, weather or web results.

Every public text is checked before it is stored, reports are private, and you can always export or permanently delete everything you have.

All public text — messages, your name, your bio, your links and every entry field — is checked before Kevin stores it. Kevin applies structural rules (Unicode abuse, repetition, link limits, https-only links, phishing patterns, handing out private contact details) and then a moderation service. The check is fail-closed: if it cannot complete, the write is refused, and rejected text is never stored anywhere. You can report a room message, a profile or a published entry. Reports are private: they are never shown publicly, never appear in News, Discover or any public number, and no IP address or device data is collected. A single report never deletes content or an account automatically. Blocking is the immediate personal control and is separate from reporting. Independently of all of this, you can export your whole portfolio and permanently delete individual entries or your entire account, at any time, for free.

• —Moderation is automated and imperfect; Kevin is not an emergency service.
• —Because messages are deleted after 30 minutes, Kevin usually has no message text left at all.
• —Deletion is permanent. Export first if you want a copy.

Private, mutual suggestions of people whose published work fits yours.

Kevin can quietly suggest a few people whose published projects overlap with yours. It reads published content only: profile text, published entries and their tags. It never reads room messages, follows, likes, profile-view history or anything private. A suggestion is private and mutual — it exists for the two people involved, carries one short factual reason, and never shows a score, a percentage, a rank or how many people were compared. Kevin never acts for you: it does not follow anybody and does not send anybody a message. Dismissing a suggestion removes it for both sides anonymously; blocking or opting out retracts every open suggestion. The feature is free and switched on; a published bio alone is enough to take part, and you still decide individually whether you take part.

• —No score, no percentage, no rank and no comparison count is ever shown.
• —Suggestions never become public and never appear in Discover or News.
• —This guide explains the rule, never your own numbers. Balances, campaign state, trial days and plan status always come from your own authenticated request.

Kevin makes private, mutual suggestions of people, using one shared resonance engine.

Kevin matches in exactly one place: suggested people. The engine reads published text only and turns it into six qualitative signals — thematic overlap, need, complement, timeliness, context and language, and intent — described in words. Suggested people is opt-in, private and mutual. A published bio alone is enough to take part; published entries only make the signal denser. Order is led by thematic overlap, need, complement and timeliness, then context and intent. A suggestion exists only for the two people involved, carries one short factual reason and can be dismissed anonymously. Kevin's server is deterministic and makes no model call: it prepares the published facts and the cues, and the connected assistant reads them and decides what is genuinely relevant — including the answer that nothing fits. Room messages, private text, follows, likes, profile-view history, click history, IP address, device and demographics are never used, and no match is ever expressed as a score, percentage or ranking.

• —One match type: suggested people, opt-in, private and mutual.
• —One shared resonance engine reads published text only.
• —'No match' is always an allowed answer, and matching never shows a score or percentage.

One shared resonance engine reads published text and decides suggested people.

Kevin reads two profiles using only what both sides published: profile text, published entries, their tags, topic words, language and place. From that it derives six qualitative signals — thematic overlap, need, complement, timeliness, context and language, and intent — plus short neutral cues such as recurring motifs, shared direction, rhythm and tension. Everything is described in words: there is no compatibility score, no percentage, no rank and no ordering of people. A published bio alone is enough to take part; published entries only make the signal denser. Suggested people is opt-in, private and mutual: a suggestion exists only for the two people involved. The server side is deterministic and makes no model call — the same published facts always give the same cues — while the connected assistant reads those public facts and may always say that nothing fits. Resonance never uses room messages, private text, follows, likes, profile views, click history, IP address, device or demographics.

• —Six qualitative signals: thematic, need, complementary, timeliness, context and language, intent.
• —Resonance cues are described in words only — never a score, percentage or rank.
• —Only published text is read; messages, follows, likes and view history never are.
• —A published bio is enough — entries only add signal density.

Reads material you hand over from your own accounts and proposes profile and entry drafts you review yourself.

Social Media Profile Builder is available: you hand over your own material, Kevin normalises it and proposes drafts you approve yourself. Connecting an account, importing and generating drafts need active Kevin Pro. Looking at what you already imported, deleting it, deleting drafts and disconnecting a provider stay free, also after Pro lapses. Kevin never logs into a provider and never fetches a website. You hand over your own material yourself: the text of your own profile, or an export file you downloaded from the provider. Kevin never asks for a social password and never scrapes anything. Nothing publishes itself. A draft becomes part of Kevin only when you accept it, and it becomes public only when the publish step afterwards succeeds. Imported data and drafts are private to you. They never reach other people, other profiles, rooms, News, suggestions or sponsors. Disconnecting a provider revokes Kevin's access and removes the connection. Deleting your imported data removes the raw copies and the drafts built from them. Neither touches the profile or entries you already saved. Kevin Love and people matching are unchanged by this feature. They keep reading only the profile and entries you explicitly saved and published yourself. How it runs: get_profile_builder_status: see your sources, any waiting drafts and how long imported material is kept. Hand over your own material as text, one entry per source: your own profile text or your own provider export. start_profile_builder: Kevin normalises that material and proposes private profile and entry drafts. get_profile_builder_draft: review the proposals and edit or reject each one. apply_profile_builder_changes: save only what you accepted into your Kevin profile and entries.

• —Works today: you hand over your own text or export from GitHub, LinkedIn, X or Instagram, and Kevin keeps that raw material for at most 24 hours.
• —A draft is private; only a save and then a publish makes anything visible.

A warm paper sheet with dark-blue ballpoint ink, a few hand-drawn marks and Kevin's own handwriting for short asides.

Kevin's website looks like a sheet of paper somebody wrote on: a warm paper background, dark-blue ballpoint ink for text, and a few loose hand-drawn marks in the margins. Kevin's handwriting is used only for Kevin's own short asides and for headings; everything you actually have to read is set in a plain, highly readable typeface. The marks are decoration and carry no information — nothing is ever explained by a doodle alone. Text that people wrote themselves is never restyled, decorated or corrected: your bio stays your bio. Some surfaces are always plainly written and exact, never playful: billing, privacy, terms, safety, data-deletion, support, install, oauth, consent, recovery, checkout, errors, server-status, moderation, retention. There is a day and a night version and a toggle in the site header. The look changed, the rules did not: Kevin is still text-only and messages still disappear after 30 minutes.

• —Decorative marks are hidden from screen readers and never carry meaning.
• —Kevin's informal voice is never applied to your own text or to precise pages.

The paper look adapts: reduced motion, higher contrast and forced colours are all respected, and nothing depends on colour alone.

The hand-drawn look is decoration layered on top of ordinary, semantic text, so it can be taken away without losing anything. If your system asks for reduced motion, every ink animation stops. If it asks for more contrast, the paper and ink move further apart and the soft margin notes become solid. In forced-colours mode the decorative marks step out of the way entirely and your own colour choices win. Decorative marks are hidden from screen readers, headings and landmarks are real, every interactive element has a visible focus ring, and no piece of information is carried by colour or by a doodle alone. Body text never uses the handwriting face.

• —Reduced motion, increased contrast and forced colours are honoured automatically.
• —Nothing in Kevin is communicated by colour or decoration alone.

A small read-only card ChatGPT can show next to Kevin's answer. It does nothing except display what the answer already contains.

When you ask Kevin for a room, a profile or your activity, ChatGPT can render a compact card in the same paper-and-ink style. There is one card per kind of result — Kevin room card, Kevin profile card, Kevin activity card — so a profile never inherits a room's heading. Every card is read-only and inert: it has no buttons, no forms, no cookies and no storage, it loads no images, it makes no network request of any kind, and it shows only what the tool answer already contained. It cannot post, follow, delete or send anything, and it cannot translate — any translation you see is ChatGPT's own reply text. If the card does not appear, nothing is lost: the same information is in the answer.

• —The card never writes, never stores anything and never connects anywhere.
• —Anything you can see in a card is public information that the answer already contained.

kevinchat.com is the read-only paper copy of Kevin: rooms, discover, News, your account overview, the status page and this guide.

Every page on kevinchat.com reads along and none of them writes. The home page explains how to connect Kevin inside any MCP-capable AI assistant, /discover shows public profiles and published entries, /news shows what Kevin noticed lately, /docs is this guide. /account is your own signed-in overview: your profiles and handles and your published entries, all read-only. /stats shows anonymous platform numbers and how the service itself is doing. Creating, editing, publishing and deleting always happen by talking to Kevin in your assistant, never on the website.

• —The website never writes: no posting, no editing, no deleting.
• —/account only ever shows your own data and only while you are signed in.
• —/stats shows aggregate, anonymous numbers — never individual people.

Anonymous, aggregate platform numbers — activity, profiles, entries, ChatGPT connections and website visits. Ask Kevin for them in chat or read them on /stats.

Kevin publishes one set of numbers and both the website and ChatGPT read the same source. You get: people active now, in the last 24 hours and in the last 7 days; messages and active rooms in the last 30 minutes; how many public profiles and published entries exist; how many profiles and entries were added in the last 24 hours; how many accounts have connected Kevin from ChatGPT (total, 24 hours, 7 days); and anonymous website visit counts for 24 hours, 7 days and in total. Ask Kevin in chat and it calls get_network_status and reads out exactly those numbers — it never estimates, extrapolates or invents a figure. Because room messages expire after 30 minutes, the message and room counts describe what exists right this moment, not a history. The same figures are public on kevinchat.com/stats.

• —Counts only: no handle, no message text and no visitor identity is ever part of the numbers.
• —Website visits are daily counters per coarse page group, with no session or visit timeline.
• —Internal operations telemetry stays on the server and is never reported in chat.

Kevin is built so verified AI crawlers and MCP-capable assistants can read published profiles and entries the same way a person reads the website.

Kevin serves every published profile and every published project, artwork, event, product, service or custom entry in both human HTML and machine-readable formats. Stable URLs such as /u/handle, /u/handle.json, /u/handle.jsonld, /p/slug, /e/slug, /llms.txt and /llms-full.txt let search crawlers and MCP clients read public text without guessing. Only published content is exposed: hidden, draft, review or deleted entries and unpublished profiles are never included. Room messages, private account data, visitor identities, follow lists and individual analytics are never published or shared with other AIs. If you want to be found by AI assistants, publish a profile and publish entries; hiding or deleting removes them from those formats. You can see anonymous aggregate read counts for your own published items with the get_ai_read_analytics tool.

• —Machine-readable formats contain the same public text as the HTML pages, nothing more.
• —No reader identity, session, address or timeline is stored for AI read analytics.

Kevin's dated changelog: every product change, newest first.

Kevin keeps one authored changelog and reads it everywhere: on the website and in chat. Each entry has a date, a title and a plain summary. If a change is built but not switched on, the entry says so instead of implying you can use it. Ask Kevin what is new and it reads out the most recent entries.

• —The changelog is authored, dated and identical on the website and in chat.