> ## Documentation Index
> Fetch the complete documentation index at: https://docs.baselayer.id/llms.txt
> Use this file to discover all available pages before exploring further.

# get_entity

> Fetch a full entity dossier from the knowledge graph.

# get\_entity

Retrieves the complete profile for a named entity: overview, facts from edges, timeline, and graph relations. This is the tool to use when you need the full picture of a specific entity.

## Parameters

| Parameter | Type   | Required | Description             |
| --------- | ------ | -------- | ----------------------- |
| `type`    | string | Yes      | Entity type (see below) |
| `name`    | string | Yes      | Name of the entity      |

### Entity types

BaseLayer supports 14 entity types:

`person`, `place`, `project`, `plan`, `organization`, `concept`, `event`, `media`, `technology`, `goal`, `document`, `belief`, `habit`, `product`

## Read-only

Yes. This tool only reads from your memory.

## Example usage

```json theme={null}
{
  "type": "project",
  "name": "my-api"
}
```

```json theme={null}
{
  "type": "person",
  "name": "Alice"
}
```

```json theme={null}
{
  "type": "plan",
  "name": "auth-refactor"
}
```

<Tip>
  Paths in results like `baselayer://person/alice` are vault URIs, not filesystem paths. Use `get_entity` with the type and name to read them.
</Tip>

## Plan entities

Plan entities (`type="plan"`) are special. They act as persistent markdown scratchpads for cross-session coordination. Create and update them with `update_plan`, read them back with `get_entity(type="plan", name="...")`.

## Common pattern

After a `memory_search` returns matching entities, use `get_entity` to read the full dossier before taking action:

```
1. memory_search("auth architecture")  → finds "auth-service" project
2. get_entity(type="project", name="auth-service")  → full dossier
3. get_entity_relations(type="project", name="auth-service")  → connections
```