API reference · Entities

Retrieve an entity

GET/v1/entities/{id}

One entity from the knowledge graph, with its recorded values, its relationships and its memories.

Open Memtro

One entity from the knowledge graph (a person, a company, a project, a commitment), with the values recorded against it, its relationships with both ends named (ended ones included and marked), and its memories. Entity ids appear on memories as subject_entity_id and entity_ids. An entity this key cannot read answers exactly as one that does not exist.

Example

Against https://platform.memtro.com, with your key in MEMTRO_API_KEY.

curl "https://platform.memtro.com/v1/entities/a83e…?memories=5" \
  -H "Authorization: Bearer $MEMTRO_API_KEY"

Shortened.

{
  "object": "entity",
  "id": "a83e…",
  "type": "person",
  "name": "Priya Shah",
  "summary": "Engineering lead, billing.",
  "card": "…",
  "card_at": "2026-11-11T02:10:00.000Z",
  "scope": "shared",
  "aliases": ["Priya"],
  "external_ids": { "email": "priya@…" },
  "properties": {},
  "created_at": "2026-06-02T09:00:00.000Z",
  "updated_at": "2026-11-03T10:14:22.000Z",
  "values": [],
  "relationships": [
    { "id": "e51a…", "from": "a83e…", "to": "0c2d…", "relation": "owns", "since": "2026-11-03", "until": null, "direction": "out", "other": { "id": "0c2d…", "name": "Billing migration", "type": "project" } }
  ],
  "memories": [{ "object": "memory", "id": "6f1c…", "content": "Priya Shah owns the billing migration (BIL-142) from 3 November 2026.", … }]
}

Authentication

An API key, as Authorization: Bearer or x-api-key.

  • Every reply, errors included, carries x-request-id and request-id headers with the same id, starting req-. Quote it to support.
  • Browsers may call it from any origin: it answers CORS preflights and allows the Authorization, x-api-key and Anthropic version headers.

Path parameters

idstringRequired

The entity's id.

Query parameters

memoriesintegerOptional

How many of its memories to include, at most 100 (read like limit on List and search memories). Not a page.

Default:

20

Response

200application/json

The entity.

object"entity"Optional

Always entity.

idstringOptional

The entity's id.

typestringOptional

person, company, project and so on.

namestringOptional

Its name.

summarystring or nullOptional

A short description.

cardstring or nullOptional

A longer description written from its own memories, where there is enough to write from.

card_atstring or nullOptional

When the card was written.

scopestringOptional

Who it belongs to.

One of shared, team or personal.

aliasesarray of stringsOptional

Other names it goes by.

external_idsobjectOptional

Its ids in the systems it came from, such as a Xero contact id or an email address.

propertiesobjectOptional

Further properties.

created_at, updated_atstringOptional

When it was first and last recorded.

valuesarray of objectsOptional

Values recorded against it ("ARR = 48,000 GBP since 2026-01-01"), up to 60.

8 fields of values
object"entity.value"Optional

Always entity.value.

key, value, unitstringOptional

What, the stated value, and its unit (unit may be null).

numbernumber or nullOptional

The value parsed as a number, if it parsed.

datestring or nullOptional

The value parsed as a date, if it parsed.

valid_from, valid_tostring or nullOptional

The period it holds for.

confidencenumberOptional

How sure.

source, memory_idstring or nullOptional

Where it came from.

updated_atstringOptional

When it was last recorded.

relationshipsarray of objectsOptional

Its relationships, up to 80.

7 fields of relationships
idstringOptional

The relationship's id.

from, tostringOptional

The entity ids at each end.

relationstringOptional

What the relationship is.

since, untilstring or nullOptional

Dates, YYYY-MM-DD.

endedtrueOptional

Present when the relationship has ended.

directionstringOptional

Whether this entity is the from (out) or the to end.

One of out or in.

otherobjectOptional

The other end: id, name, type.

memoriesarray of objectsOptional

Its memories, as in Retrieve a memory: those still current first, then the most important, then the newest.

Errors

In the OpenAI envelope, {"error": {"message", "type", "param", "code"}}. What each code means and what to do about it is in the error catalogue.

StatusCodeWhen
401invalid_api_key

The key is missing, malformed, revoked or expired.

402subscription_inactive

The organisation has no active subscription.

404not_found

No such entity, or not one this key can read.

Where agents remember your company

Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.

7-day free trial · card on file, nothing charged until it ends · cancel any time