Originary

Originary addresses the challenge of verifying machine actions, such as API calls, agent decisions, gateway events, payment transactions, and provisioning activities, across organizational boundaries. It creates compact, signed records from selected facts about these actions—such as what happened, which policy applied, the result, the time, and the issuer—without exposing internal logs. These records are designed to be portable and verifiable by external parties, including customers, auditors, partners, and downstream systems, supporting needs like audit, compliance review, dispute resolution, and partner handoff.

The tool operates by recording facts from a local system action, signing the resulting record, and enabling verification outside the originating system. This process allows counterparties to independently confirm events without needing access to sensitive internal logs. Originary supports a range of workflows, including API calls, MCP tool runs, agent actions, gateway decisions, payment events, and provisioning events. The signed records it issues can be bundled and exported for audits or shared reviews, and the same record format is used across different types of workflows, making it adaptable for varied verification scenarios.

Originary is designed to integrate with existing technology stacks, working alongside systems such as API gateways, observability tools, policy engines, payment rails, and agent runtimes. It does not replace these components but instead generates verification records from their workflows.

0 licensed, indicating it is open source. It is positioned for teams and organizations that need to provide external proof of machine actions without compromising internal security or privacy. Originary offers a way to start with a single workflow and expand as verification needs grow, emphasizing its fit for environments where proof of machine actions is required for external parties.