Dereference a memory_token in one round-trip
emem_memory_token_resolveResolve a memory token citation into the cited fact, returning value, unit, band, kind, fact body, and fact URL—no token parsing or fetch chaining needed.
Instructions
Parse a emem:fact:<cell64>:<fact_cid> citation handle and return the reading it cites. value, unit, band and kind are on the response at the TOP level, alongside the full signed fact body they were lifted from. Saves the agent from string-splitting the token and chaining GET /v1/facts/<cid> manually. Memory algebra: the resolve operation (https://emem.dev/docs/model.html).
When to use: Call when an agent receives a memory_token from another agent (or out of a previous turn) and wants the value behind it. Read value for the reading and unit for what it is measured in; both are always present, and an explicit null means the fact genuinely has none (kind: "absence" has no value, and most index bands including NDVI are dimensionless) rather than that the field is missing. For a scalar, quote value_verbatim instead: it is the same number as the exact decimal string it was signed as, and re-typing a JSON number is where measured precision loss comes from. The response also carries the parsed cell + fact_cid, the full fact body, and the stable fact_url an agent can hand to any other peer. 404 with a typed code if the responder doesn't hold the cid; try /v1/fetch with the cid then, or paste the token at a mirror.
Example arguments: {"token":"emem:fact:defi.zb493.xoso.zcb6a:cxjiu7l54ujzrpnekp24n4534yojpue4mprddbvevnqtti3lh5bq"}
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| token | Yes | A `emem:fact:<cell64>:<fact_cid>` citation handle to dereference. |