Mstamp: Sign API records so a third party can verify them offline (github.com)

Mstamp has introduced a novel cryptographic notary service that enables AI agents to handle API calls with enhanced audit capabilities. By wrapping the fetch API, Mstamp records requests and their corresponding responses as SHA-256 hashes, which are subsequently signed by a backend service using Ed25519. This results in a receipt that third parties can verify offline, ensuring transparency and trust in the data exchanged between AI agents and APIs. Notably, Mstamp is designed as a neutral notary, meaning it doesn't influence the validation of API responses or classify them as 'good' or 'bad'; rather, it simply records what occurred. The significance of Mstamp lies in its ability to provide verifiable records for API interactions, crucial for web scrapers that often encounter ambiguous failure states, such as HTTP 200 responses with empty or incorrect bodies. By offloading the signing process to an independent backend, Mstamp promises a compelling solution for accountability in AI/ML applications. Although the project is still in early development and lacks a hosted service, developers can install the Mstamp library and establish a local audit log. The flexibility of its design acknowledges future changes to the protocol, making the implementation of verification in AI systems more accessible while ensuring compliance with evolving standards in cryptographic attestations.