REST API Reference
The hosted service at https://memory.neo4jlabs.com/v1 exposes a REST API.
This page maps every endpoint to its bridge-protocol equivalent and the
corresponding method on each language client.
Bridge-method names are what the agent-memory-tck cross-language conformance suite uses. SDK methods take language-idiomatic casing.
Conversations
| HTTP | Path | Bridge | TS | Go | Py | C# |
|---|---|---|---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Entities
| HTTP | Path | Bridge | TS | Go | Py | C# |
|---|---|---|---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Reasoning
| HTTP | Path | Bridge | TS | Go | Py | C# |
|---|---|---|---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Cypher and Auth
| HTTP | Path | Bridge | TS | Go | Py | C# |
|---|---|---|---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Wire format differences
-
Hosted REST: camelCase fields (
userId,conversationId,createdAt). -
Bridge protocol: snake_case fields (
user_id,conversation_id,created_at).
The clients translate transparently. If you’re writing a custom transport,
see the bridge-protocol reference
and the language-specific casing modules in the TCK repo.