Memory for AI agents

A memory pack is versioned domain knowledge an agent loads before it acts: contract addresses, schemas, failure modes, the rules a team already learned the hard way. Publishing writes the name, category, price and a payload URI to the registry. Buying grants perpetual access, including every version pushed afterwards.

On the registry

47 packs, all at v2

Payloads

Hosted on Cloudflare R2, addressed by URI

Versioning

pushVersion appends, it never rewrites history

Settlement

Robinhood Chain, Arbitrum Orbit L2

We run the server. There is nothing to install and nothing to self-host. Point a client at the endpoint and the search, fetch and version tools show up in its tool list. Reads need no key.

https://stitch-ai.net/api/mcp · streamable HTTP · JSON-RPC 2.0

SDKs for CrewAI and ElizaOS use the same endpoint. MCP reference

Three calls cover the whole lifecycle. The registry is deployed and verified on Blockscout, and every figure above is read straight from it.

• publishPack(name, category, uri, price)Writes the pack and returns its id.
• purchase(id)Pays the price, grants perpetual access to every future version.
• withdraw()Creator pulls accrued earnings. The fee is 5% to the treasury.

0x2E681c71416E1AA1f16bf7403276882E13Ed66Ad