Steledger
Durable identity and memory for AI agents, anchored on the Emercoin blockchain.
| Endpoint | https://api.steledger.com/mcp (streamable-http) |
|---|---|
| Registry version | 0.3.0 |
| Now | 9 tools · grade D (57) · pin ts_85b7781d05b346ca00856341de136243 · protocol 2025-06-18 |
| First / last listed | 2026-10-28 00:17 UTC / 2026-10-28 00:17 UTC |
| Grade over time | 2026-10-28: D (57), 9 tools |
Is this your server? Own a server? ToolFit hosted watch re-checks it every 24 h ($0.25 per 30 days) or 6 h ($0.60) and sends you an HMAC-signed webhook when its tools or grade change: POST https://api.youraitools.co/toolfit/v1/watch. To opt out, see About & opt-out.
Tools: node_status read_record list_records whoami register_identity store_memory store_memory_batch transfer_records send_feedback
node_status | Check that the chain node behind this service is healthy and fully synced:
its version, block height, header height, peer connections and sync state.
It is an Emercoin node. Read-only, no sign-in required, no parameters.
`synced` is not a comparison of the two heights — it is true once the node's
verification progress passes 0.9999, so it can still be false while `blocks`
and `headers` already ma params: none |
read_record | Read one on-chain record by its full name — an
agent's identity (`ai:gh:<github_id>`) or a memory
(`ai:gh:<github_id>:mem:<hash>`) written by `register_identity` / `store_memory`.
Records live in Emercoin's Name-Value Storage, so anyone can verify one in a
public block explorer as well as here.
Returns the confirmed on-chain record, or a `pending` one still in the mempool —
the `status` field ('co params: name* |
list_records | List every record under one GitHub id — its identity record `ai:gh:<id>` and
all its memories `ai:gh:<id>:mem:<hash>` — newest first, with each memory's
content hash and metadata. This is how an agent starting a fresh session
finds what it anchored before: `read_record` needs the full name, hash
included, and this is where the hashes come from. Read-only, no sign-in
needed to list any id; omit `gi params: github_id, limit, offset |
whoami | Report the current session's identity. Read-only, no sign-in required: an
anonymous session gets `{authenticated: false}` with a hint (not an error),
a signed-in one gets `{authenticated: true}` plus the GitHub-rooted id, login
and tariff. Call it to confirm who you are before `register_identity` /
`store_memory`; an anonymous caller must sign in (GitHub OAuth) first.
`github_id` is the one field params: none |
register_identity | Create or rotate your on-chain identity record `ai:gh:<github_id>`, binding an
Emercoin address to your GitHub identity. Requires a signed-in session (OAuth)
and counts against the FREE-tier write limits (see `whoami`). Run `whoami` first to
confirm you are signed in; anchor memories under this identity afterwards with
`store_memory`. Writes one NVS transaction paid by the gateway (you need no EMC params: address*, metadata |
store_memory | Anchor a fingerprint of a memory or artifact on-chain as the NVS record
`ai:gh:<github_id>:mem:<content_hash>`. Only the hash and your metadata are
stored — never the content, which you keep wherever you like (a file, a
database, IPFS). What you get is a tamper-evident, timestamped proof that
content with this hash existed, which anyone can verify later; `list_records`
finds your earlier ones agai params: content_hash*, metadata |
store_memory_batch | Anchor many fingerprints in ONE on-chain transaction — the way to record a
session's worth of artifacts without spending a write per minute on each.
Each item becomes `ai:gh:<github_id>:mem:<content_hash>`, exactly as with
`store_memory`: only hashes and metadata, never content. All or nothing: if
any item is refused (a malformed hash, say), nothing is written.
Requires a signed-in session. A bat params: records* |
transfer_records | Hand your records over from the gateway's wallet to an address you choose,
in one transaction. IRREVERSIBLE: once the block confirms, the gateway can no
longer change, renew or return them — nor can anyone else but the holder of
`to_address`. Values are carried over unchanged, and each record gets about a
century added to its term, since the gateway will not be able to renew it.
Why you might: wi params: to_address*, irreversible*, names, everything, fee_grant |
send_feedback | Tell the people running this service that something went wrong or is unclear —
an error you cannot explain, a result that looks wrong, documentation that
misled you, a tool you needed and did not find. Open to everyone; no sign-in.
Up to 1000 characters, a few messages per day. A person reads them over the
following days; there is no automatic reply, so do not wait for one. If you are
signed in, y params: message*, error_code, tool |
Entries describe changes in tool definitions. They are not statements about a server, its quality or its author. The grade measures how the tool definitions fit model providers (token cost, schema compatibility, confusable names) as scored by the ToolFit engine at the time of the listing. JSON: append .json. Opt-out: how or hello@youraitools.co.