Skip to main content
ClaudeWave
ToolsOfficial Registry0 stars0 forksTypeScriptApache-2.0Updated 2d ago
ClaudeWave Trust Score
77/100
Trusted
Passed
  • Open-source license (Apache-2.0)
  • Actively maintained (<30d)
  • Documented (README)
Flags
  • !No description
Last scanned: 8/6/2026
Get started
Method: Clone
Terminal
git clone https://github.com/fidacy/fidacy-open
1. Clone the repository.
2. Follow the README for installation and usage instructions.
Use cases

Tools overview

# Fidacy — Open verification + SDK

[![License: Apache 2.0](https://img.shields.io/badge/License-Apache_2.0-blue.svg)](./LICENSE)
[![OpenSSF Scorecard](https://api.securityscorecards.dev/projects/github.com/fidacy/fidacy-open/badge)](https://securityscorecards.dev/viewer/?uri=github.com/fidacy/fidacy-open)

Open verification + SDK for Fidacy — the external, signed trust layer for agent payments.

**Verify any Fidacy verdict yourself, against our public JWKS. Don't trust us — check.**

Every verdict Fidacy issues is signed. These packages let you fetch our public keys
and cryptographically verify that a risk payload or webhook genuinely came from Fidacy
and was not tampered with — entirely client-side, with no need to call back to us.

"Anyone can verify" is a testable claim here, not a slogan: a
[conformance corpus](./packages/verify/conformance) ships signed fixtures plus
expected outcomes, so a port of the verifier in any language proves
compatibility offline (`node packages/verify/conformance/run.mjs` from the repo
root, 8/8 or it is not compatible).

## Packages

| Package          | Description                                                              |
| ---------------- | ------------------------------------------------------------------------ |
| `@fidacy/verify` | Isomorphic signature verification against Fidacy's public JWKS. Zero trust in the SDK transport — verify the verdict itself. |
| `@fidacy/sdk`    | Thin, typed client for the public Fidacy API. Calls the API and verifies every response via `@fidacy/verify`. |
| `fidacy-spec`    | The open specification for Fidacy's signed payloads, JWKS, and webhook formats. See [`spec/`](./spec). |

## Quickstart

**Run it in 30 seconds** (assess + verify a real signed verdict):

```bash
git clone https://github.com/fidacy/fidacy-open && cd fidacy-open/quickstart
npm install
FIDACY_API_KEY=fky_test_…  node quickstart.mjs   # a TEST key from app.fidacy.com (mode: test)
```

Output: a signed verdict and `signature valid: true` — cryptographically verified against
the public JWKS, client-side, with no call back to Fidacy. See [`quickstart/`](./quickstart).

Or add the packages to your own project (published on npm, Apache-2.0):

```bash
npm i @fidacy/sdk @fidacy/verify
```

**Python?** Same flow, two dependencies — see [`quickstart-python/`](./quickstart-python):

```bash
cd fidacy-open/quickstart-python && pip install -r requirements.txt
FIDACY_API_KEY=fky_test_…  python3 quickstart.py
```

```ts
import { Fidacy } from '@fidacy/sdk';
import { verifyRiskPayload } from '@fidacy/verify';

const fidacy = new Fidacy({ apiKey: process.env.FIDACY_API_KEY! });

// Assess a payment mandate (AP2 intent/cart).
const result = await fidacy.assess({
  mandate: {
    vct: 'mandate.payment.1',
    payee: { id: 'merchant_demo', name: 'Demo Store' },
    payment_amount: { amount: 4299, currency: 'EUR' },
    payment_instrument: { id: 'pi_demo', type: 'card' },
  },
});
console.log('decision:', result.decision);

// Don't trust us — verify the signed verdict yourself, against the public JWKS:
const verified = await verifyRiskPayload(result.riskPayloadJws);
console.log('signature valid:', verified.valid);
console.log('decisions match:', verified.claims.decision === result.decision);
```

Runnable end-to-end example: [`examples/quickstart-node`](./examples/quickstart-node).

## Links

- Specification: [`spec/`](./spec)
- Hosted product: https://fidacy.com

## Repository

> **Home:** the canonical repository is https://github.com/fidacy/fidacy-open. Packages are published under the npm scope **@fidacy** (Apache-2.0).

## Design principles

- **Isomorphic.** `@fidacy/verify` runs in Node 18+, the browser, and edge runtimes.
  No Node-only globals.
- **Independent.** These packages only call the public API and verify signatures.
  They contain no Fidacy proprietary logic.
- **Auditable.** Apache-2.0, open source, no secrets.

## License

[Apache-2.0](./LICENSE) © 2026 ZEEPCODE GROUP LLC

What people ask about fidacy-open

What is fidacy/fidacy-open?

+

fidacy/fidacy-open is tools for the Claude AI ecosystem with 0 GitHub stars.

How do I install fidacy-open?

+

You can install fidacy-open by cloning the repository (https://github.com/fidacy/fidacy-open) or following the README instructions on GitHub. ClaudeWave also provides quick install blocks on this page.

Is fidacy/fidacy-open safe to use?

+

Our security agent has analyzed fidacy/fidacy-open and assigned a Trust Score of 77/100 (tier: Trusted). See the full breakdown of passed checks and flags on this page.

Who maintains fidacy/fidacy-open?

+

fidacy/fidacy-open is maintained by fidacy. The last recorded GitHub activity is dated 2026-08-04, with 0 open issues.

Are there alternatives to fidacy-open?

+

Yes. On ClaudeWave you can browse similar tools at /categories/tools, sorted by popularity or recent activity.

Deploy fidacy-open to your cloud

Ship this repo to production in minutes. Each platform spins up its own environment with editable env vars.

Maintain this repo? Add a badge to your README

Drop the badge into your GitHub README to show it's tracked on ClaudeWave. Each badge links back to this page and reflects the live Trust Score.

Featured on ClaudeWave: fidacy/fidacy-open
[![Featured on ClaudeWave](https://claudewave.com/api/badge/fidacy-fidacy-open)](https://claudewave.com/repo/fidacy-fidacy-open)
<a href="https://claudewave.com/repo/fidacy-fidacy-open"><img src="https://claudewave.com/api/badge/fidacy-fidacy-open" alt="Featured on ClaudeWave: fidacy/fidacy-open" width="320" height="64" /></a>

More Tools

fidacy-open alternatives