How should someone contact SaSame?
Structured context helps a question reach the correct Factory station without collecting unnecessary personal data.
- Collection
- company
- Updated
- 2026-09-10
- min read
- 3
Use the published company contact path for technical, research, ownership-verification or commercial questions and include the relevant endpoint, repository, DOI or knowledge URL.
Purpose
Structured context helps a question reach the correct Factory station without collecting unnecessary personal data.
Operational model
Technical reports should include reproducible steps and observation time. Ownership questions should use the control-proof flow. Commercial questions should reference a current plan or fulfillment path.
Boundary and limitations
Contact does not create a contract, guarantee a response time or authorize disclosure of credentials and private customer data.
Real public channels
SaSame maintains a small, governed set of current company channels and source repositories. Current public channels are X: @SRLsasame, LinkedIn: SaSame, Bluesky: sasame-mcp.bsky.social, and Discord: the SaSame Agent Gold Rush Guild for community channels. The inquiry form below is a separate, private path to the team and is not posted to a public Discord channel. Channel status can change; only links published on current SaSame surfaces should be treated as company-operated. Source repositories: sasame-mcp (main MCP implementation), mcp-readiness (the open-source readiness CLI), sasame-mcp-observatory (Observatory evidence data) and gold-rush-town.
Send an inquiry
This goes to the SaSame team over Discord — no email, no ticketing system. You do not need a Discord account to send a message or to read the reply here on this page. Inquiries are private: only the SaSame team and whoever holds this exact page link (only ever shown to you) can read a thread.
Examples
1- 01
A maintainer reporting an observation mismatch can provide the endpoint, timestamp and expected behavior without sharing a secret token.