TRUSTSIGNAL  ·  PROVE. VERIFY. TRUST.

Prove your records haven't changed since the day you filed them.

TrustSignal issues a cryptographic receipt for every record and anchors it on a public blockchain. When a regulator, auditor, or court asks years later, you can prove it’s untouched — in seconds, without trusting us or anyone else.

Request a PilotSee it verify live

90-day pilot  ·  your documents never leave your infrastructure  ·  receipts stay permanently verifiable, even after cancellation

Anchored on Ethereum + PolygonIndependently verifiableNo documents or PII stored
WHO IT’S FOR  ·  HEALTHCARE STAFFING

Verified at the source. Altered at the handoff.

symplr, Verisys, and Nursys confirm a license at the source. None of them seal the assembled credential packet during the agency-to-facility handoff — the moment it changes hands. That gap is where fraud lives. TrustSignal doesn't replace the source check; it sits after it, sealing the packet so any facility can prove the file is exactly what the agency sent.

7,600+
fake nursing diplomas surfaced in one federal operation (Op. Nightingale)
37%
of them passed the NCLEX and entered patient care
$6.5B
annual US travel-nursing market

Attach a tamper-evident receipt to every credential packet before it reaches the facility's MSO. The facility calls the verify endpoint and gets mathematical proof the packet is unchanged — no board re-query, no phone call, no manual process. An NFC tap at the credentialing desk binds physical presence to the submission.

See how the credential packet handoff gets sealed
HOW A PILOT WORKS

90 days. One workflow. One partner.

TrustSignal sits behind your existing workflow at the ingestion boundary. We seal a single document type, prove its integrity on demand, and the receipts outlive the pilot — and us.

  1. 01
    Collect

    Evidence enters through your existing systems. No workflow change, no new tools for your team.

  2. 02
    Receipt

    A signed, tamper-evident receipt is generated at ingestion — a mathematical proof, not a log entry.

  3. 03
    Verify

    Any time later, a single API call confirms the evidence matches its original sealed state.

  4. 04
    Review

    Your compliance, legal, and audit teams hold mathematical proof of integrity — not just internal logs.

  • 90 days, fixed fee, one-time
  • Up to ~3,000 proofs
  • 25 NFC wallet cards where applicable
  • No IT integration, no workflow change
  • Receipts permanently verifiable, even after cancellation
Request a PilotPhase 1 verticals (workforce, healthcare staffing): $8,500 / 90 days
PILOT REQUEST

Start a lightweight pilot. No IT changes required.

Share the basics and TrustSignal will follow up within 24–48 hours with next steps for your pilot. No payment or system access is requested through this form.

  • 90-day pilot, fixed fee, non-refundable
  • Up to 3,000 tamper-evident receipts
  • 25 NFC wallet cards included
  • No workflow changes for your team
  • Receipts permanently verifiable

By sending this request, you agree that TrustSignal may contact you about pilot planning, integration review, and service follow-up.

FOR ENGINEERS

One install. One call.
Your documents never leave.

Extract a feature vector locally and send numbers — not files. Get back a permanent, independently verifiable receipt. Setup is one command and about thirty minutes: no database, server, or queue to provision.

  • Pure Node.js SDK — no Python
  • We receive a feature vector, not your document
  • Independently verifiable — no TrustSignal server at audit time
  • Full receipt export on cancellation — zero lock-in
Read the API reference
trustsignal · quickstart
# ~30 min, no DevOps
$ npx trustsignal-setup

# seal at ingestion — docs never leave your infra
POST /api/v1/receipts
200  { receipt_id, signature: "ed25519:…", verify_url }

# verify anytime — on-chain math, no TrustSignal server
GET  /api/v1/receipt/:id/verify
  → { status: "clean" }     ✓ unchanged
  → { status: "mismatch" }  ✗ altered since sealing
Fastify·TypeScript·EdDSA Ed25519·RFC 8785·Polygon + Sepolia·DigiCert RFC3161·OpenAPI