Try the reference lab
Understand a failure and its corrected implementation. No installation or connection needed.
Choose a local example or connect your own staging application. Trace checks only the stores and observation window you review.
Understand a failure and its corrected implementation. No installation or connection needed.
Use an existing adapter, bind your app’s functions, or map its staging API routes.
Bring reviewed targets and saved regressions to another machine or CI runner.
Review a bundle ↓This starts an isolated local Mem0 2.2.1 sample. To check your existing Mem0 application, use the Python connector below. This sample is not a connection to your account.
First setup downloads Mem0 and Qdrant client dependencies into a dedicated environment. It needs internet and Python 3.11–3.13; later starts reuse the environment. No paid API key or model inference is used.
Checking local sample status…
Active memories and vectors share one store. Audit history is excluded; no answer cache exists. Trace owns this process and stops it when the engine shuts down.
Bind create, search, inventory and delete functions. Or pass your existing Mem0 Memory instance to the connector.
from synapsoul_trace.sdk import serve_adapter from synapsoul_trace.integrations.mem0 import mem0_adapter # memory is your existing staging Mem0 instance serve_adapter(mem0_adapter(memory), port=8879)
Mem0 connector: tested with Mem0 2.2.1 / Qdrant client 1.18.0. It checks active memories and vector points; it excludes audit history, graph memory and any separate answer cache.
Download Python starter ↓Use the small Node HTTP adapter package with your existing application functions. No runtime dependencies.
import {createTraceServer} from '@synapsoul/trace-adapter';
const server = createTraceServer({
ingest, query, inventory, delete: remove
});
server.listen(8879, '127.0.0.1');Node 20+. Each callback receives the synthetic namespace. Inventory must enumerate the declared stores fully; missing observations are not zero.
Download JavaScript starter ↓Import OpenAPI 3 JSON to choose routes, then review the request and response fields. Trace does not infer what an endpoint deletes or whether an inventory is complete.
Use $namespace in every operation; $id/$text for ingest, $query for query, $ids for delete. Responses use dotted field paths. Inventory needs complete, source_records, vector_records and cache_records. Only an absent, explicitly excluded cache may use {"literal":0}.
trace adapter-serve --mapping trace.mapping.json --port 8879
Start this bridge locally, then connect http://127.0.0.1:8879/trace/v1 in My staging app. Review coverage and test connectivity before running. Supported: static route paths, JSON bodies, scalar GET query parameters, HTTP 200 JSON responses. Path parameters and streaming APIs need an SDK adapter.
Export saved connections and regressions without copying Trace’s evidence database. Bundles contain endpoint URLs, coverage and environment-variable names, never token values. Review their URLs before sharing.
Choose a file to review its destinations. No network calls are made by import.
Existing connections cannot be silently overwritten. Digests detect edits; they are not signatures or proof that a sender is trusted. Import creates no test records. Run and regression replay can create and delete synthetic records.
Completed evidence and connections stay on this computer. An active check finishes before the process exits. Reopen Trace from your launcher to continue.