Why does Kalshi share your user id to Wall Street market makers in RFQ API?
Kalshi's RFQ API provides market makers with user identifiers to facilitate trade routing. The practice raises privacy concerns among users who may not expect their IDs to be shared. Kalshi argues the data sharing is necessary for compliance and efficient market operations.
- ▪Kalshi's RFQ API includes the user's ID in requests sent to Wall Street market makers.
- ▪Market makers use the identifier to match orders, manage risk, and ensure regulatory reporting.
- ▪Privacy advocates argue that sharing user IDs could expose personal data without explicit consent.
- ▪Kalshi contends the sharing is limited to information required for compliance with financial regulations.
- ▪Users may request more transparency or opt out of certain data-sharing practices.
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Xcancel |
| Canonical URL | https://xcancel.com/mattkalish/status/2056351499236843954#m |
| Publication time | Mon, 18 May 2026 22:22:01 +0000 |
| Retrieval time | 2026-05-18T22:34:56.987Z |
| Last seen | 2026-05-18T22:34:56.987Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | OwFAFbc1larJ |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
Checking your browser Starting verification… This takes a couple of seconds and happens automatically. If you can't pass the test, whitelist your extensions on this website, update your browser and use a modern web browser (Firefox/Chrome/Safari). You may try the automated checks a second time. Some checks may fail once and succeed on a second try. Reload now. Still having trouble? Ask for help by sending an email at antibot[AT]xcancel[DOT]com with the browser that you are using and this reference ID: no_id_generated And solve an image challenge instead.
Excerpt limited to ~120 words for fair-use compliance. The full article is at Xcancel.
Discussion
0 commentsMore from Xcancel
