Docs · PatentChecker

PatentChecker docs for evaluation, verification, and delivery risk

Use this lane for buyer evaluation, evidence verification, self-hosting, adapters, coverage scope, and the delivery-system surfaces behind vector and sequence IP review.

Patent IPDelivery riskVerificationSelf-serve
Need another page?
Search the docs

Jump to buyers, verification, demos, self-hosting, or adapters without opening the full docs tree first.

Mobile navigation
Jump to section
Open
This is the primary PatentChecker commercial entrypoint. The buyer evaluates in their own environment for 2 weeks using a signed, offline-verifiable evaluation receipt and a seeded self-serve workspace.
The goal is not to sell a paid pilot first. The goal is to prove activation, verified bundle generation, and conversion intent with minimal procurement friction.

Offer

  • SKU: patentchecker_evaluation
  • Commercial profile: trial_2_week
  • Price: USD 0
  • Default term: 14 days
  • Delivery mode: buyer-run self-evaluation, optionally operator-assisted
  • Verification path: offline bundle and receipt verification stays available without a paid license

Buyer Inputs

The buyer provides:
  • One watchlist or one sequence plus intended corpus scope
  • Organization and tenant identifiers for receipt issuance
  • Any buyer-approved adapter constraints
  • Security/procurement contact for handoff and follow-up
The buyer does not need to send production secrets. If raw sequence disclosure is restricted, use a hash, length, and approved local adapter workflow until counsel/security clears broader sharing.

Operator Workflow

Use the website-aligned profile:
BashRunnable example
npm run platform:self-serve:evaluation:ship -- \
  --tenant-id <tenant-id> \
  --org-id <ORG_ID> \
  --watchlist ./intake/<tenant-id>/watchlist.v0.1.json \
  --key-id <signing-key-id> \
  --private-key-file <signing-private-key.b64> \
  --profile trial_2_week \
  --workspace-root ./tenants \
  --issued-root ./ops/licenses_issued \
  --evaluation-owner omnis \
  --problem-area "<buyer problem area>" \
  --follow-up-date <YYYY-MM-DD> \
  --json
This emits:
  • Signed evaluation_license.json
  • public_keys.json
  • Seeded tenant workspace
  • Buyer-ready handoff ZIP and .sha256
  • Delivery manifest and delivery status JSON
  • Buyer email draft
  • Operator checklist

Activation Definition

An evaluation is activated only when the buyer returns evidence that the packaged first-run path completed successfully. Record that evidence with:
BashRunnable example
npm run platform:self-serve:evaluation:mark-activation -- \
  --delivery-status <delivery_status.v0.1.json> \
  --activation-return <buyer-activation-return.zip> \
  --actor <operator> \
  --json
Activation should prove:
  • Preflight doctor passed
  • Compose or starter run completed
  • Run verification passed
  • Returned activation artifact verifies deterministically

Conversion Milestones

Track the evaluation through these stages:
  • issued: receipt and workspace generated
  • sent: handoff sent to buyer
  • activated: buyer returned first-run evidence
  • follow_up_completed: conversion review completed
  • converted, declined, timed_out, canceled, or superseded: terminal outcome recorded
The minimum value proof is not "trial sent." It is buyer activation plus a conversion decision.

Success Metrics

Track:
  • Trial requests received
  • Time from request to handoff
  • Handoff-to-activation rate
  • Days to activation
  • Verified bundles generated per active evaluation
  • Follow-up completion rate
  • Conversion rate to paid monitoring, enterprise license, or court-ready/evidence packet
  • Reasons for declined or timed-out evaluations

Conversion Offers

After activation, route the buyer to the smallest paid next step that matches observed usage:
  • Production key for recurring monitoring on the buyer's own watchlists
  • Enterprise annual license for private adapters, on-prem, or air-gapped workflows
  • Court-ready packet when counsel needs a defensible export
  • Audit pack when they need repeated deterministic runs without a full annual deployment

Guardrails

  • Not legal advice.
  • Not an infringement analysis.
  • Not a Freedom-to-Operate determination.
  • No opinion on claim scope.
  • Outputs are deterministic evidence artifacts for qualified counsel and R&D review.
  • npm run platform:self-serve:evaluation:ship
  • npm run platform:self-serve:evaluation:mark-delivery
  • npm run platform:self-serve:evaluation:mark-activation
  • npm run platform:self-serve:evaluation:set-follow-up
  • npm run platform:self-serve:evaluation:mark-follow-up
  • npm run platform:self-serve:evaluation:mark-outcome
  • npm run platform:self-serve:evaluation:report
  • npm run platform:self-serve:evaluation:alert
  • npm run platform:self-serve:evaluation:scheduler
  • docs/evaluation-license-issuance-sop.md
  • docs/evaluation-quickstart.md
  • docs/crispr-therapeutics-trial-readiness-2026-04-29.md
  • docs/self-hosting.md
PatentChecker 2-week self-evaluation | Omnis documentation | Omnis Genomics