POST https://deepadata.com/api/v1/extract
Authorization: Bearer dda_live_YOUR_KEY
{ "content": "Had a long call with mum
today. She remembered the kookaburra
joke from my childhood.",
"profile": "extended" }{ "data": {
"constellation": {
"emotion_primary": "warmth",
"arc_type": "bond" },
"gravity": {
"emotional_weight": 0.82,
"recall_triggers":
["kookaburra", "childhood"] },
... } }The record mirrors the person at the moment — their representation at the time, over time — not the model's later recall of them.
Any system can read it, any auditor can check it, and it stays honest to the person it describes. Every record validates against the open EDM specification (v0.8.3, MIT-licensed, machine-validated). Three canonical profiles set the capture depth — Essential (31 fields), Extended (62 fields), and Full (91 fields) — so a record is never whatever a model felt like writing that day.
Extraction is interpretation, not inference: the record captures what the subject expressed, with an explicit experiential-stance field separating lived experience from quoted, witnessed, or hypothetical content. Why that distinction matters.
That's the design. Here's the status of each, plainly. We monetize validation, sealing, registry, and telemetry — not tokens, and never your users' words.
Designed into the format. The record carries token references, not names; the tokenization gateway is in build.
Redaction-first by design — issue the typed structure, withhold the prose. Shipping as part of the issuance path.
Bring your own keys — the SDK runs extraction on your model keys today; the hosted path is completing the same decoupling.
BYOK and gateway deployment ship with design partners.
Every EDM artifact stacks six layers of significance — governance at the top, affective weight at the bottom — encoded at capture time.
Hover or focus a layer to see example fields.
The product chain
What you run. Every stage works on the same sealed record — nothing here depends on retrieval quality, ranking, or a model reading its own state.
Capture the emotionally significant structure of an interaction as a schema-bound EDM record — designed so no prose needs to leave your boundary (BYOK, with design partners).
Sign the record (Ed25519, W3C Data Integrity) and register it. Tamper-evident from the moment of capture, discoverable, re-appraised (appended, never rewritten).
Compute the per-relationship longitudinal record over sealed artifacts — the surface dependency and escalation duties ask about.
Your live view of obligation-relevant state across your user base — records, safety, registry, certificates.
One bundle per obligation — records, trajectory, certificates, reconciled against the registry. In build as part of the issuance path.