ApiTyped memory
Merged (newest-wins) view of a user records
Per-field merge across the user records, newest value winning — e.g. "the current lead profile" without client-side merge logic.
Per-field merge across the user records, newest value winning — e.g. "the current lead profile" without client-side merge logic.
Authorization
TokenAuth Authorization<token>
Project API key as Token lb-sk_...
In: header
Path Parameters
schemaName*string
Query Parameters
user_id*string
Response Body
application/json
curl -X GET "https://example.com/v1/records/string/merged?user_id=string"{ "merged": {}, "record_count": 0, "last_updated": "2019-08-24T14:15:22Z"}LLM-extract a record from a conversation or free text POST POST
Extracts only explicitly stated values (required is relaxed for the extraction call, then re-enforced before storing). When nothing usable is found the response is stored:false — a normal outcome, not an error. Stored records embed and meter like direct writes.
Publish a new schema version POST POST
Existing records stay pinned to the version they were written with.