Skip to main content
LOCAL ENGINE | No required paid service
START WITH ONE CONNECTION

Your first check starts here.

Choose a local example or connect your own staging application. Trace checks only the stores and observation window you review.

01 / EXPLORE

Try the reference lab

Understand a failure and its corrected implementation. No installation or connection needed.

02 / CONNECT

Test my application

Use an existing adapter, bind your app’s functions, or map its staging API routes.

03 / MOVE A TEST

Import a connection

Bring reviewed targets and saved regressions to another machine or CI runner.

Review a bundle ↓
OPTIONAL / TRACE-OWNED SAMPLE

Meet Mem0 without a terminal.

stopped

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.

YOUR APPLICATION / TWO INTEGRATION PATHS

Use the functions you already have.

Python · callbacks or existing Mem0

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 ↓

JavaScript · async callbacks

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 ↓
EXISTING HTTP API / EXPLICIT FIELD MAPPING

Map your API to a repeatable check.

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.

SAME CONTRACT / ANOTHER MACHINE

Take the test with you.

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.

Stop this local engine

Completed evidence and connections stay on this computer. An active check finishes before the process exits. Reopen Trace from your launcher to continue.

AI DATA LIFECYCLE TESTING

Deleted should
mean deleted.

Test what your application forgets.
Keep the evidence. Catch the regression.

i
A real engine. A controlled reference lab.

These deliberately broken and corrected fixtures use actual local stores. They do not assess an external application or prove physical erasure.

View scope ↗
01

Configure a run

SYNTHETIC DATA ONLY
TEST SEQUENCES
Temporary fixtures · No external API calls · Full evidence
02

Inspect the evidence

READY
◎

Proof starts with a run.

Choose a fixture and test sequences.
Results come from observed store contents,
retrieval responses and preserved controls.

PASSFAILINCONCLUSIVE
THE CONTRACT

Precisely scoped.
Honestly reported.

What we verify

API-visible source records, vector records and cached answers after deletion and controlled worker completion. An unrelated record must survive.

What we do not claim

Disk or backup erasure, model unlearning, historical chat deletion, production coverage, or independently reproduced upstream vulnerabilities.