Vraimony Embedded Case SDK — Paid
Decision-Ready Case Infrastructure
for your product.
Embed the full case-building layer into your helpdesk, CRM, claims portal, or WooCommerce install. Raw inputs go in — timeline, evidence map, reviewer case page, and signed bundle come out.
Partner license
White-label receiver
Rule packs per industry
Signed bundles
What you embed
Raw order/claim/handover inputs → decision-ready case output.
✕ Without SDK — what your reviewers receive
- ZIP of screenshots with inconsistent naming
- PDF summary written by a non-specialist
- Missing evidence discovered mid-review
- Timeline reconstructed manually from emails
- Multiple follow-up requests before decision
- No way to verify file integrity
✓ With Embedded SDK — what your reviewers receive
- Structured timeline auto-built from your data
- Evidence map: claim-by-claim support status
- Missing-items radar — gaps flagged before submission
- Reviewer-facing case page (no login required)
- Signed bundle with SHA-256 file hashes
- QR verify — integrity confirmed in 3 seconds
Where it embeds
Six integration contexts. One SDK.
🛒
WooCommerce / Admin
Build a sealed case directly from the order screen. Timeline + evidence map + reviewer link — in one click.
🎧
Helpdesk / CRM
Turn a support ticket into a decision-ready case. Attach files, auto-map to dispute type, export reviewer pack.
🏥
Claims Portal
Structure insurance, warranty, or damage claims into a reviewer-facing bundle with integrity verification.
🏢
Vendor Review Flow
Package vendor qualification evidence — certifications, delivery records, compliance docs — into a verifiable record.
⚓
Dispute Ops Tool
Batch-process chargebacks or freight claims. Rule packs per dispute type. White-label reviewer experience.
🔗
Any API / Webhook
REST connector kit. Takes structured JSON in, returns ERF case PDF. Plug into any workflow engine.
SDK API
Everything the free toolkit does — plus the decision layer.
const sdk = require('@vraimony/embedded-case-sdk');
// 1. Build a case from raw inputs (order, ticket, claim, handover)
const case_ = await sdk.buildCase({
type: 'woo_chargeback', // rule pack key
inputs: order_data, // your existing data
files: file_array, // uploaded evidence
license_key: process.env.VRAIMONY_KEY
});
// 2. Get missing-items radar
case_.radar;
// → { missing: ['delivery_confirmation'], risk: 'high', score: 62 }
// 3. Generate reviewer-facing case page URL
case_.reviewerURL;
// → 'https://verify.vraimony.com/r/vry_abc123' (no login needed)
// 4. Export sealed bundle (ed25519 signed)
case_.bundle;
// → { erf: '1.0', id: 'vry_…', signature: '…', timeline: […], evidence: […] }
// 5. White-label receiver page (your domain)
sdk.renderReceiver(case_, { brand: 'YourCo', domain: 'review.yourco.com' });
Partner tiers
Three ways to embed.
Connector
$299/mo
For agencies and dispute operators building on top of Vraimony
- ✓25 sealed cases/month
- ✓All dispute rule packs
- ✓Reviewer-facing links
- ✓SDK + API access
- ✓WooCommerce connector
- —White-label receiver
- —Custom rule packs
Apply →
Integrator
$999/mo
For SaaS products embedding the case layer into their own UX
- ✓200 sealed cases/month
- ✓All dispute rule packs
- ✓Reviewer-facing links
- ✓Full SDK + REST API
- ✓All connector kits
- ✓White-label receiver page
- —Custom rule packs
Apply →
Enterprise
Custom
For platforms, marketplaces, and insurance portals with volume and compliance needs
- ✓Unlimited cases
- ✓Custom rule packs per industry
- ✓White-label receiver + domain
- ✓Full SDK + REST + Webhooks
- ✓Batch / ops features
- ✓Compliance packaging
- ✓Dedicated onboarding
Talk to us →
Why this is difficult to copy
Not one feature. Five things working together.
📐
Canonical schema
ERF — deterministic, offline-verifiable
📋
Decision rules
Reason-specific MUST/STRONG/HELPS logic
👁
Receiver UX
Reviewer sees structured case, not a dump
🌐
Cross-channel
GitHub + SDK + extension + platform
📚
Real-case corpus
Templates from documented real cases
A competitor can clone the hash function, the extension, or the viewer in weeks. Cloning the rules engine + receiver UX + real-case library + cross-channel distribution — built on real deployments — takes years.
The upgrade path
Free toolkit builds developer trust. SDK converts it.
1 — Open Proof Toolkit (free)
Developer uses the free SDK or extension. Canonicalizes, hashes, lints, exports. Proves the concept locally. Zero friction.
Get free toolkit →
2 — Embedded SDK (paid)
Developer embeds the decision layer into their product. Gets rule packs, white-label receiver, signed bundles, batch ops, and compliance packaging.
Become a partner →
3 — Standard gravity (long-term)
ERF adoption across integrators creates a corpus of documented cases. The rules engine improves. The moat widens. The standard becomes the default.
ERF protocol →
Start embedding
Start with the free toolkit. Apply for partner access when ready.