Haystack Pipelines. Verified Document Memory.

RAG extractions with proof.

Get API Key →

12MCP tools

0.01mslookup

Freefor individuals

ed25519signed

The Problem

Haystack finds facts in documents. Those facts flow into agent context unsigned. No receipt of extraction, no conflict detection, no provenance chain from source to assertion.

Step 1

Connect

→

Step 2

Ingest + Extract

→

Step 3

Verify + Receipt

The Fix

npm install @verifiedstate/haystack

Beta: tagging-level integration. Ingestion works via @verifiedstate/sdk with Haystack-specific source tagging. Native Haystack features coming.

textBeta
// Add VerifiedState as a Haystack component
// Document extractions → verified assertions

What You Get Back

✓ VERIFIED

receipt.json
{
  "receipt_id": "rct_7f3a...",
  "assertion": "User prefers dark mode",
  "status": "verified",
  "confidence": 0.94,
  "signature": "ed25519:a8c3f1...",
  "verified_at": "2026-04-06T14:32:01Z",
  "chain_position": 42
}

Without VerifiedState vs. With VerifiedState

Feature	Without	With VerifiedState
Document extractions	Unsigned	Verified with receipts
Source provenance	Lost	Full chain maintained

FAQ

Which Haystack version?

Works with Haystack 2.x pipeline components.

Related Integrations

Start building with verified memory.

Free: 50,000 assertions/month. No credit card. No trial expiration.

Get Free API Key Read the Docs GitHub →