Skip to main content
There is currently no general public endpoint for applications to append arbitrary records directly to Neuro-Ledger. Use the domain interface that owns the record.

​
Package developers

Using Neuron persistence from a package does not by itself guarantee a public, replicated audit record. Treat ledger inclusion as an explicit deployment capability that must be agreed with the Neuron operator and documented for the object type. Do not take a dependency on internal ledger assemblies, storage files, /NL/* implementation endpoints, or repository layout. Those are not the supported public contract for a package.

​
Application developers

Keep the identifier returned by the domain API—for example, a contract ID or token ID. Use that same API to retrieve the current object and its exposed history. This remains stable even when ledger storage and peer topology change.

​
MCP developers

The Event Log MCP server returns operational events, not raw Neuro-Ledger blocks. A future ledger-specific MCP server would need its own documented resources, tools, scopes, and privacy boundary; do not assume one exists today.