Why xmark exists
The native X bookmarks UI is a reverse-chronological list. It works fine for a few dozen saves and breaks at a few hundred. Past 500, you have a research library you can't read.
xmark fixes the recall side of the equation. We sync your bookmarks via the X API, embed them with OpenAI for semantic search, and let you chat with the corpus through Claude, with every answer citing the original tweets.
Who's behind it
xmark is built by jclvsh (Josh Choi). A small-team product, shipped against the X API directly and Claude as the reasoning layer. We don't take outside funding. The product is paid because the compute is paid.
What xmark is for
- Researchers who use X as a working library.
- Writers who quote what they've read and need fast recall.
- Builders who save technique posts and need to find them later.
- Anyone whose bookmark pile crossed the “unreadable” line.
What it's not for
- Bookmark management: xmark is read-only. Remove a bookmark and it removes on X too.
- Public search: every user's corpus is private, row-level-security-gated.
- Real-time monitoring: bookmarks sync on demand, not on push.
Contact
Bug reports, feature requests, integration questions, partnerships: write the desk at josh@jclvsh.art.