# Memory: What the company knows, and when it knew it — Hanzo AI

> What the company knows, and when it knew it.

[Try Hanzo](https://hanzo.ai/signup)[Graph API](https://docs.hanzo.ai/docs/openapi/graph)

api.hanzo.ai

## Try it

curl https://api.hanzo.ai/v1/graph \\ -H "Authorization: Bearer $HANZO\_API\_KEY" \\ -H "Content-Type: application/json" \\ -d '{"assertions": \[{"entity": "acme/svc/api", "relation": "owner", "value": "acme/team/core", "names": true, "at": "2026-01-05T00:00:00Z", "source": "wiki/api"}\]}' curl https://api.hanzo.ai/v1/graph/resolve \\ -H "Authorization: Bearer $HANZO\_API\_KEY" \\ -H "Content-Type: application/json" \\ -d '{"entity": "acme/svc/api", "relation": "owner", "as\_of": "2026-03-01T00:00:00Z", "as\_known": "2026-02-01T00:00:00Z"}'

```
curl https://api.hanzo.ai/v1/graph \
  -H "Authorization: Bearer $HANZO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"assertions": [{"entity": "acme/svc/api", "relation": "owner", "value": "acme/team/core", "names": true, "at": "2026-01-05T00:00:00Z", "source": "wiki/api"}]}'

curl https://api.hanzo.ai/v1/graph/resolve \
  -H "Authorization: Bearer $HANZO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"entity": "acme/svc/api", "relation": "owner", "as_of": "2026-03-01T00:00:00Z", "as_known": "2026-02-01T00:00:00Z"}'
```

## API

Operations on api.hanzo.ai. One key reaches every layer.

MethodPathWhat it does

**POST**`/v1/graph`Asserts what is true of an entity.

**GET**`/v1/graph`Reads the assertions the org has recorded, bounded by as\_of and as\_known.

**POST**`/v1/graph/resolve`What is in force about an entity as of an instant, and what disagreed.

**POST**`/v1/graph/diff`What came into force, was superseded and was retracted between two instants.

**POST**`/v1/graph/answer`Answers a question from the whole graph, citing the assertions it rests on.

**GET**`/v1/base/bases`Lists every Base the caller can reach, one per org.

The graph records assertions — an entity, a relation, a value, who said it and when it was so — and never overwrites one. A read takes two instants: as\_of for when the world was so, as\_known for how much had been heard. So a past answer can be reproduced exactly, and a correction does not erase what was believed before it. Each org’s own data lives in its Base, a SQLite store of its own.

## Measured

- [LoCoMo: multi-hop ALL@20 from 18.8 to 37.5 on the held-out split](https://hanzo.ai/benchmarks/locomo)
- [LongMemEval-S: 500 questions over 4,846 sessions, top-five evidence 90.6% against 85.8% for cosine](https://hanzo.ai/benchmarks/longmemeval)
- [MemoryAgentBench: FactConsolidation substring EM from 33 to 67 on a 262k haystack](https://hanzo.ai/benchmarks/memoryagentbench)

- [CronQuestions: point-in-time questions answered through /v1/graph](https://hanzo.ai/benchmarks/cronquestions)

## Hanzo OS

## Docs

- [Graph API](https://docs.hanzo.ai/docs/openapi/graph)
- [Memory, the concept](https://docs.hanzo.ai/docs/concepts/memory)
- [hanzo graph](https://docs.hanzo.ai/docs/cli/graph)

## On this site

- [Base](https://hanzo.ai/base)
- [Search](https://hanzo.ai/search)
- [Datastore](https://hanzo.ai/datastore)
- [Object storage](https://hanzo.ai/s3)

## Memory

What the company knows, and when it knew it.

[Try Hanzo](https://hanzo.ai/signup)[Graph API](https://docs.hanzo.ai/docs/openapi/graph)
