Frequently asked

Contexta is the intelligent memory layer that gives AI agents the ability to notice things — connections, changes, contradictions — and act on them with full provenance. Memory plus reactivity plus citations, behind one API.

A vector DB returns nearest neighbours. Contexta returns a Context Packet: entities, relationships, citations, and reactive triggers — over a graph that resolves entities and tracks bi-temporal provenance on every edge.

Open-core. The SDK, CX parser, store adapters (ArangoDB and Neo4j), query orchestration, Reflex DSL, CLI, and framework plugins are open-source. The reactive engine, provenance pipeline, and Context Packet assembler stay proprietary — like Stripe.js versus the Stripe payment engine.

Minutes. Connect via REST or MCP, ingest your first thread, watch a Context Packet land. Framework plugins for LangChain and CrewAI plug in with one import.

Our internal benchmarks show 60–80% hallucination reduction versus naive RAG approaches on the same agent task — driven by provenance-weighted scoring, temporal filtering, and graph-anchored expansion.

Five tiers — Working (Redis, 1 h), Episodic (90 d on ArangoDB), Semantic (graph + vector, permanent), Procedural (triggers, permanent), Archival (S3, per policy). Retention and latency follow access pattern.

Embeddings above a 0.85 cosine threshold merge into the existing node. No duplicate "Acme Inc" / "Acme Corp" / "acme" fragments across ingest sources. The threshold is tunable per namespace.

Yes. The open-source `@contexta/store-arango` and `@contexta/store-neo4j` adapters both implement the `StoreAdapter` interface. Self-host the graph and let Synapta orchestrate reactivity on top.

Every edge carries two clocks: `asserted_at` (when we learned it) and `valid_from / valid_to` (when it is true). A Recall with `as_of: <date>` applies four predicates so only facts known and valid (and not yet retracted) at the anchor survive.

A reactive trigger declared in YAML. It owns a CX expression that decomposes into Motifs. When the live graph satisfies a Motif, a Locus materialises and the Reflex fires per Locus — every webhook delivery includes affected entities, the reasoning chain, and provenance.

Yes. CX expresses graph-shape completion `(c:company) -[:supplies]-> (us)` and property-band transitions `@sentiment_7d: >= 0.4 -> < 0.4` in the same language. One registration surface; no specialized trigger types.

Cooldown is per Locus, not per Reflex. One noisy account in a sentiment-drift Reflex does not throttle alerts on the other accounts watching the same pattern.

Pricing is indicative ahead of GA. The Developer tier is free for prototyping; Pro and Enterprise tiers are listed on the pricing page. Talk to us for production workloads — we will price honestly against your signal volume.

The open packages (`@contexta/types`, `parser`, `store-arango`, `store-neo4j`, `query`) are self-hostable today. The closed Synapta reactive engine is hosted; on-prem deployment is available on the Enterprise tier.

A single Synapta `Forget` call. The first pass marks edges with `retracted_at = now` rather than hard-deleting; cascade follows `derived_from` edges, not graph topology. Vault drops blobs, revokes pre-signed URLs, rotates signing keys. The audit ledger keeps a non-destructive record of who deleted what, when.

Append-only. Every Reflex fire, every Forget operation, every policy evaluation logs with operator identity, scope, decision, and full provenance chain. The ledger is queryable through the same store as recall — no separate forensic system.

Data Encryption Keys are managed per-namespace by Vault and rotated in batches. Encryption at rest underpins all storage tiers; BYOK is supported on the Enterprise tier.

Per-data policies apply field-level access control on graph nodes: PII masking, redaction, consent-gated access. Policy evaluation logs to the audit ledger. Sensitivity marks cascade along the graph.

Yes. Framework plugins for both ship in the open-source surface. Drop in a memory provider and recall returns Context Packets your agent can drop into prompts directly.

Contexta exposes both REST and MCP. MCP lets any compliant client (Claude Desktop, Cursor, Cody) recall and ingest without bespoke glue.

Any HTTPS endpoint. Payload templates support variable interpolation against the matched Locus and the Context Packet — pipe to Slack, Discord, PagerDuty, your internal API, a Zapier hook, or directly to an agent inbox.