Open standard · Draft 0.9

Lodestone speaks the Carrick Protocol.

Carrick is an open standard for AI memory you own. Any agent works with any Carrick server, with the same tools and the same meaning, and you can move to another provider without losing your memory, your connected apps or the people who follow you. Lodestone is the first server to implement it.

Conformance

Carrick compatible

A server may call itself Carrick compatible only if it passes the protocol's conformance suite at Core level. Lodestone 0.29.2 passed Core and Federation on 17 October 2026, under the protocol's earlier name (below).

LevelWhat it coversLodestone
CoreNotes as Markdown files, six MCP tools, sign-in and a discovery filePasses
FederationSharing with people and other servers, and publications anyone can followPasses
MovingExport, import and a signed "moved to" record, so you can leave with everythingExport built; import coming

Check any server yourself: python3 conformance/carrick_conformance.py server https://your-server, from the protocol repository.

Read the standard

Issues and pull requests are welcome on GitHub. Changes are additive: no breaking changes unless there is no other way, and any that are needed are announced well ahead.

Its earlier name

The protocol was first published as the Lodestone Protocol, with the wire name lodestone/1. The Carrick names (carrick/1, /.well-known/carrick) mean exactly the same, and the earlier ones keep working everywhere until nobody uses them. Nothing you have connected needs to change.

"Carrick" and "Lodestone" are trademarks. The specification is under CC BY 4.0, and the schemas, suite and examples under Apache 2.0, so anyone may build a compatible server.