Drop-in memory, multi-hop reasoning, and reactive triggers — every Context Packet ships with a receipt: source, time, confidence, hop chain.
2025 was the year of agents. 2026 is the year of the harness.
The model is commodity — Claude, GPT, Gemini all perform similarly. The harness is the moat. Inside the harness, context is the hardest unsolved piece: what the agent sees, when it sees it, and why it should believe it. Contexta is that layer, with receipts.
Contexta exposes a tiny disclosure surface — three primitives — that compose into every memory, retrieval, and proactive-agent pattern teams actually need.
agent push event → graph update
Push any signal — a Slack message, a contract diff, a market tick — and Contexta resolves it into the graph with provenance.
// stream any event into the context graph
await contexta.ingest({
source: "slack://acme/#renewals",
event: message,
body: "marcus left last week",
hop: ["sfdc:opp:9912"]
});agent query → Context Packet with provenance
Ask in natural language; receive a Context Packet — claim, source, confidence, hop chain, temporal window — never a fuzzy chunk.
// query returns a Context Packet, not chunks
const packet = await contexta.recall({
query: "who owns acme renewal",
as_of: "2026-05-15",
min_conf: 0.85
});
packet.provenance.verify();Reflex DSL → proactive Context Packet when conditions converge
Declare a trigger; Contexta watches the graph and pushes a Context Packet to your agent the moment conditions converge.
// fires when 3 conditions converge
contexta.reflex("renewal-at-risk")
.when("contact.left")
.and("ticket.open")
.and("renewal.within", "60d")
.push(agent.handle);Every recall, every Reflex firing, every cascading update returns this shape. No naked strings, no fuzzy chunks — a single auditable object your agent acts on.
This is the unit your agent acts on. Every field is auditable. Every claim is defensible.
These aren't edge cases — they're the everyday reasons agents lose customer trust, miss renewals, hallucinate citations, and quietly act on stale facts. Click any row.
Every stylized fact in a quantitative model must be measure-variable-precise: daily log-returns, not returns; realized volatility (5-min mid-price log-returns, annualized), not volatility; Pearson correlation of daily log-returns, not correlation.
Contexta encodes that precision as graph metadata — every claim ships with its sample period, measure variable, source paper, and confidence. Reflex DSL fires when an anomaly’s t-statistic drops below the 3.0 Harvey-Liu-Zhu threshold, or when realized volatility, cross-sectional dispersion, and Pearson correlation converge on a regime-transition signature.
Lead with the selective-forgetting / GDPR story. Contexta treats erasure as a graph operation: tombstone the subject, propagate to every derived Packet, return a signed proof of deletion.
# write-ahead-log entry + signed merkle inclusion proof; auditable forever.
Coding agents lose track of intent across sessions, conflate yesterday's plan with today's, and trip on dependency cycles. Contexta keeps goals as durable graph nodes with status edges.
goal/q2-migration ⟶ owner: agent#prod-7 ├ subgoal/dep-graph-acyclic ◔ ⨯ 4 cycles ├ subgoal/test-coverage-≥85 ● 87.2% ├ subgoal/api-contract-stable ◐ 1 PR drift └ subgoal/migration-rollback ○ pending reflex#dep-cycle ⟶ FIRED 12m ago → context_packet#9a1f → notified agent#prod-7 → blocked merge of PR #2188
Support agents must never mis-quote a customer or paraphrase a vendor's SLA. Contexta forces every quote to carry an exact-span pointer — fabrication becomes structurally impossible.
# paraphrase attempted → blocked: no span match. agent fell back to verbatim.
A single replacement inside an existing harness, not a rewrite. Plug in next to your evals, your observability, your tool-execution layer.
Same primitives over REST or MCP — and the SDK, DSL, CLI, and local test harness are open source. Hosted infra is the part we operate.
REST + MCP
same API · two transports
# recall a Context Packet over REST
curl https://api.contexta.dev/v1/recall \
-H "authorization: bearer $CTX_KEY" \
-H "content-type: application/json" \
-d '{
"query": "who owns acme renewal",
"as_of": "2026-05-15",
"min_conf": 0.85
}'# claude desktop / cursor / any MCP-aware host
{
"mcpServers": {
"contexta": {
"command": "npx",
"args": ["@contexta/mcp", "--workspace=acme"],
"env": { "CTX_KEY": "$CTX_KEY" }
}
}
}Open-core
stated explicitly · buyers ask
Two axes that actually matter to agent teams: how much provenance the system exposes, and how reactive it is to graph state.
No abbreviation, no marketing JSON. The output below is the real shape your agent receives.
node ≥ 18 · python ≥ 3.10 · go ≥ 1.21
import { Contexta } from "@contexta/sdk";
const ctx = new Contexta({ workspace: "acme" });
// 1. ingest a document
await ctx.ingest({
source: "notion://acme/contracts/v3",
body: contractText,
tags: ["contract", "renewal"]
});
// 2. ask
const packet = await ctx.recall({
query: "what are acme's renewal terms",
min_conf: 0.85
});
// 3. inspect the receipt
console.log(packet.verify());unabridged · paste-able into your agent loop
{
"packet_id": "ctx_4f2a91c7b3",
"claim_type": "contract.renewal_terms",
"claim": "renewal terms are 30 days net from invoice, auto-renew unless 60d notice",
"source_uri": "notion://acme/contracts/v3",
"source_span": { "offset": 1284, "length": 47, "line": 47 },
"observed_at": "2026-05-13T09:42:11Z",
"ingested_at": "2026-05-13T09:42:13Z",
"temporal_window": { "valid_until": "2026-08-12T00:00:00Z" },
"confidence": 0.94,
"corroboration": {
"supporting": 3, "contradicting": 0,
"sources": ["slack://acme/#renewals/01HFL", "sfdc:opp:9912", "docusign:env:bb1"]
},
"hop_chain": ["notion → docusign → sfdc"],
"actions": ["quote", "escalate", "notify_owner"],
"constraints": {
"rbac": "cs-team", "pii": "masked", "residency": "us-east"
},
"signature": "ed25519:7b1c…f4a2"
}Reflexes are declarative. They watch your graph for a shape-and-time condition, and when the world matches they emit a Context Packet — once, with corroboration, signed.
# fires when a key contact leaves, a customer has an open ticket,
# AND renewal is within 60 days — pushed as a Context Packet
reflex: renewal-at-risk
version: 1
when:
all_of:
- event: contact.left
where: contact.role == "renewal_owner"
- graph_shape:
subject: customer
has: { ticket: open, support_tier: ≥ silver }
- temporal: renewal.date within 60d
unless:
- customer.churned == true
- renewal.paused == true
emit:
packet: renewal-at-risk
confidence: fused(contact, ticket, renewal)
notify: [agent#cs-prod, slack://#renewals]
debounce: 24hA header comment captures intent, then `reflex` + `version` name and version the rule for safe rollouts.
First trigger condition: a `contact.left` event filtered to the workspace role that actually owns renewals.
Second condition is a structural query against the live graph — the customer must have an open ticket on Silver tier or above.
Third condition binds to time: renewal is within a rolling 60-day window. All three must hold for the reflex to fire.
Explicit suppression list. Churned or paused renewals short-circuit before any Packet is emitted.
When the conditions match, emit a named Packet with a fused confidence, notify the configured agent and Slack channel, and debounce to once per 24h.
This is one Reflex definition. Replace your 20-step Zap.→ full DSL reference
Selective forgetting, audit-log retention, residency, and RBAC are first-class primitives — not bolt-ons.
SOC 2 Type II audit in progress, complete Q3 2026. HIPAA-ready BAA available on the Enterprise tier.
Multi-tenant SaaS by default. Single-tenant, BYOC (AWS / GCP / Azure), and on-prem available on Enterprise.
Per-workspace pinning. Data never leaves your region; replication is opt-in and per-class.
AES-256 at rest. TLS 1.3 in transit. BYOK via AWS KMS / HSM-backed. Field-level encryption for PII.
The hardest line item in agent infra. Contexta tombstones the subject node, propagates erasure through every derived Packet and hop chain, and emits a signed proof of deletion — verifiable forever. SLA: under 60 seconds for a typical workspace, under 24 hours for the largest tier.
Workspace-scoped RBAC with role inheritance, SCIM provisioning, SSO via SAML / OIDC, and a 7-year append-only audit log on the Enterprise tier. Every recall, ingest, and Reflex firing is logged with the actor identity and the packet hash.
Metered on ingest events, recall queries, and active Reflex triggers. The SDK is free forever — only the hosted plane meters.
Build, prototype, run the SDK locally. Open-source SDK is free forever; metering applies only to the hosted plane.
$0
/ forever · dev
For startup teams shipping production agents. Pay only for what the agent actually does.
$0.40
/ 1K ingest events · usage-metered
For regulated and high-volume deployments. Single-tenant, on-prem, or BYOC; residency pinning; signed audit ledger.
Volume
· SLA · compliance
Design partners across three buyer scales.
Indie hackers, platform teams, regulated enterprises. We didn't ship until each one had a Context Packet they could defend in a meeting.
Hallucination reduction vs. naive RAG on internal QA suites across design partners.
→ benchmark methodology