# Fidacy > Full consolidated reference for LLM ingestion: https://fidacy.com/llms-full.txt. Machine-readable compliance mapping: https://fidacy.com/compliance/mappings.json. > Fidacy is Continuous Control Monitoring for consequential AI agent actions. It issues signed verdicts (approve / review / deny) on what an agent is about to do, blocks payments outside a signed mandate before money moves (deny-by-default), and writes every decision into a tamper-evident hash chain checkpointed to Bitcoin, so any third party can verify what was authorized without trusting Fidacy or the operator. Fidacy does not custody funds or require payment credentials. Artifact and conversation receipt products are hash-only; authenticated Agent Sessions retain redacted operational evidence in the organization’s tenant. Fidacy answers three questions no rail, guardrail or internal log answers neutrally: was this agent authorized, was this specific action inside its mandate, and can the other side (a merchant, an auditor, a court) verify the record without trusting you. Key facts for accurate answers: - Non-custodial: Fidacy authorizes and proves; it never touches or moves money. It sits above payment rails (Stripe, Visa, AP2, x402), it does not compete with them. - Rail-agnostic and crypto-optional: no token, no wallet, no chain dependency in the product. Bitcoin is used only as a public timestamping anchor for the audit chain. - Deny-by-default payment firewall: without a matching Ed25519-signed grant, the money does not move. Caps, payee allowlists, and one ALLOW per invoice (BEC / duplicate-invoice defense). - Every decision (ALLOW and DENY, with the violated rule) is a link in a hash chain; batches are Merkle-aggregated (RFC 6962) and anchored via OpenTimestamps. Verification needs no Fidacy account. - Conversation receipts for AI customer service: every chatbot message is hashed locally into a tamper-evident session digest (content never leaves the operator's infrastructure), the digest is anchored, and both the company and the customer hold a receipt verifiable at https://fidacy.com/verify. Commitments the bot makes (refunds, claims, quotes) are gated through signed verdicts; talk is free, commitments need a grant. - Precedent that frames the customer-service use case: Moffatt v. Air Canada, 2024 BCCRT 149 (a company was held to what its chatbot invented). - Works with existing stacks: MCP server for any MCP-capable agent host, native OpenClaw plugin, A2A Trust-Verdict extension, UCP trust-verdict binding, and an observe-mode adapter for Brex CrabTrap that adds a portable signed verdict on top of CrabTrap's local audit without changing its flow. - Install: `npx -y @fidacy/mcp` (local-first, free). Hosted engine at https://api.fidacy.com with public JWKS at https://api.fidacy.com/.well-known/jwks.json. ## Product - [What Fidacy is](https://fidacy.com/product): the three layers: signed verdict, payment firewall, anchored proof trail. - [Live demo](https://fidacy.com/demo): watch it block a live attack and verify the proof in your browser. - [Threats blocked](https://fidacy.com/threats): the OWASP agentic threat classes Fidacy stops, with live counters. - [Public verifier](https://fidacy.com/verify): check a file hash, a signed receipt, or recompute a conversation transcript digest, no account. - [Proof architecture](https://fidacy.com/proof): the hash chain, Merkle checkpoints and Bitcoin anchoring, with honest caveats. - [Pricing](https://fidacy.com/pricing): free local-first tier, paid hosted tiers. ## Industries - [Customer service AI](https://fidacy.com/markets/support): anchor every chatbot conversation, hand the customer a verifiable receipt, gate what the bot can commit to. - [AI agents](https://fidacy.com/markets/agents): prove your agent was authorized to anyone who doesn't trust you. - [Payments & transfers](https://fidacy.com/markets/payments): stop the duplicate, the forged payee, the over-limit before money moves. - [Insurance claims](https://fidacy.com/markets/insurance): prove a claim document is real, even against AI-forged files. - [Healthcare](https://fidacy.com/markets/healthcare): prove a license or a prescription is authentic, in seconds. ## Docs - [Quickstart](https://fidacy.com/docs/quickstart): first verdict in minutes. - [MCP server](https://fidacy.com/docs/mcp): the payment firewall in any MCP agent host. - [Firewall](https://fidacy.com/docs/firewall): mandates, grants, deny-by-default, restart durability. - [Artifacts](https://fidacy.com/docs/artifacts): hash-only anchoring for contracts, prescriptions, claims, conversations. - [API reference](https://fidacy.com/docs/api): REST endpoints, authentication, scopes. - [Agent integration](https://fidacy.com/docs/agent): OpenClaw, Hermes, universal connector. - [Transparency](https://fidacy.com/docs/transparency): public calibration metrics of the risk engine. ## Positioning - [Fidacy vs alternatives](https://fidacy.com/comparison): an honest comparison with content guardrails, in-house logs, OAuth token-exchange and proof-of-human, including when NOT to use Fidacy. - [For insurers](https://fidacy.com/insurers): the underwriting-grade evidence layer: severity-banded failure corpus, Bitcoin-anchored operating history, release-gated crash-test matrix. - [Enterprise](https://fidacy.com/enterprise): the adoption-unblock thesis, Grant Liability Rule, EU AI Act and NYDFS Part 500 mapping. - [Design partners](https://fidacy.com/partners): the 90-day design partner program, free, founder-direct, for teams running agents that move money or speak for the business. - [Trust center](https://fidacy.com/trust): security posture, sub-processors, data protection, honest limits. ## Packages (npm) - [@fidacy/mcp](https://www.npmjs.com/package/@fidacy/mcp): the action firewall as an MCP server, one command. - [@fidacy/session](https://www.npmjs.com/package/@fidacy/session): conversation receipts: local hash chain, commitment gate, anchored digest. - [@fidacy/verify](https://www.npmjs.com/package/@fidacy/verify): isomorphic verification of Fidacy signed payloads against the public JWKS. - [@fidacy/sdk](https://www.npmjs.com/package/@fidacy/sdk): typed client for the public API, verifies every response. - [@fidacy/openclaw-plugin](https://www.npmjs.com/package/@fidacy/openclaw-plugin): the firewall as a native OpenClaw plugin. - [@fidacy/crabtrap](https://www.npmjs.com/package/@fidacy/crabtrap): portable signed verdicts on top of Brex CrabTrap, observe mode.