SIGNALMESH · SUBMESH

Scan → attach your session to an origin

Paste cookies (Netscape / JSON) and/or headers (KV pairs or JSON) that your browser already carries for a target origin. The submesh stores them scoped to that origin and pipes them through on every POST /api/submesh/call to matching coords. Values live in memory only; never logged, only 8-char hashes retained for provenance. Same trust boundary as an autofilled Submit Payment: user-triggered, local-side, and the credential the target already accepted IS the credential.

1. Auth key

Your submesh API key. Defaults to the free demo tier.

2. Target origin

The service you want the mesh to reach AS YOU. Include scheme.

3. Session material (cookies + / OR headers)

Fastest capture in Chrome/Brave DevTools: Application → Storage → Cookies → your origin, copy the rows you need. Values are never logged.
For header-based auth (GitHub Bearer, HF X-SignalMesh-Key, etc.). Same in-memory scoping.
Session drops from memory after this window.