Countersign

Purpose: Preventing AI agents from making uncontrolled payments across multiple wallet and card backends.

Inferred · not functionally tested

Audience: developers building AI agents and wallet infrastructure

Inferred · not functionally tested

Functions: monitoring, payments

Inferred · not functionally tested

Interfaces: API: indicated (inferred, not tested) · MCP: unknown · CLI: indicated (inferred, not tested) · Self-hosting: unknown

Recorded constraints: pricing: commercial_oss · license: Open Source · platforms: CLI, WEB · deployment: browser, cli, cloud_managed

Constraint provenance is unknown; confirm requirements with the publisher.

Record sources: countersign.network · github.com. These links do not verify the individual claims.

In the AI security & guardrails space, Countersign takes a focused approach. Inferred · not functionally tested: It focuses on preventing AI agents from making uncontrolled payments across multiple wallet and card backends. Inferred · not functionally tested: Countersign is a B2B product aimed at developers building AI agents and wallet infrastructure. Basis unknown · not verified: It follows a commercial open-source model under the Open Source license. Basis unknown · not verified: It ships for the web and the command line.

It is developed by Countersign, and it first shipped in 2026. Development happens publicly on GitHub with 132 commits in the last 90 days. Inferred · not functionally tested: Key capabilities include cross-vendor freeze, spend policies, and tamper-evident ledger. Inferred · not functionally tested: Catalogued interfaces include a public API.

Summary written by a language model from the project’s public pages.