How do I connect SaSame to an AI client?

Use the ChatGPT guide for a custom MCP app, the Claude guide for a remote custom connector, the Claude Code guide for the CLI command, or the generic guide when a client accepts a Streamable HTTP server definition. Client plan, workspace and administrator permissions remain controlled by the client provider.

Use https://live-vps.sasame.online/public-mcp for keyless public discovery, start_here and point-in-time audits. Use https://srl-sasame.com/api/mcp when the agent needs to search or read SaSame website knowledge. Use https://live-sasame.sasame.online/mcp for authenticated Information Market participant actions. The authenticated User MCP keeps OAuth 2.1 + PKCE, but participant identity is wallet-native. Account Control asks the user to connect an EVM wallet and approve one EIP-1193 personal_sign challenge. The MCP client receives only OAuth tokens bound to a wallet-derived participant_id and wallet_id; it never receives the private key. Desktop users can use an injected wallet. Mobile users can open the consent screen in MetaMask or Coinbase Wallet using the provided wallet link/in-app browser. Existing legacy Account Control account/organization compatibility is separate from User MCP participant identity. The private Owner MCP is not a customer surface.

Wallet authorization proves control of the participant wallet; it does not give the MCP client custody of that wallet and it does not turn legacy Google/NextAuth account or organization identity into the User MCP principal.

The public endpoint is https://live-vps.sasame.online/public-mcp. It requires no SaSame account or API key and exposes the bounded public Factory tool surface. Do not substitute the private Owner MCP host: that surface is intentionally access-controlled.

For the public surface, refresh tools and call start_here. For the authenticated User MCP, complete OAuth and wallet signing, then call session_info. Verify principal_kind is WALLET_PARTICIPANT and that participant_id and wallet_id are present before using Information Market tools such as exchange_status or market_search. Merely saving a connector or loading the consent page is not proof that OAuth completed.

After wallet authorization, use the User MCP for the Information Market participant surface. Read-only tools such as exchange_status, market_search, market_get and transaction_history can verify the connection before any state-changing submission, purchase or settlement action.

If tool discovery fails, confirm the exact HTTPS endpoint, supported Streamable HTTP transport, client plan or workspace permission, and whether an administrator disabled custom connectors. Do not paste credentials into the public endpoint configuration. Record the client, time and error before retrying.