Technology — NeuroPrint Analytics

01 — CORE ANALYTICAL FRAMEWORK

Three layers, one direction of data flow.

Click each layer to see the transformation detail, output schema, and responsibilities.

Biology

Static biological pattern as input

Dermatoglyphic patterns — formed in the first trimester of gestation and unchanging for life. NPA does not treat these patterns as 'identity', but as a static biological signal with high stability.

·Input source: 10-finger dermatoglyphic scan (static, non-temporal)
·Capture device-agnostic — not tied to any single device
·No behavioral data, biometric authentication, or wearable signal

layer · biology

ridge_count[ 12, 14, 11, 9, 10 ]

pattern_codeL · W · L · A · L

core_position(0.42, 0.61)

stability_score1.000

02 — WHITE-LABEL ARCHITECTURE

Our engine, your interpretation layer.

Three zones with firm boundaries. Each zone has a distinct owner, contract, and responsibility.

ZONE · A

NPA Engine

Capture orchestration · signal normalization · indicator computation · output schema.

Signal pipeline

Normalization core

Output API

owner: NPA

ZONE · B

Contract Boundary

REST API · JSON Schema · audit log · rate limit.

POST /v1/output

schema: npa.v1

HMAC-signed

owner: shared

ZONE · C

Partner Layer

Brand interpretation · narrative · UI/UX · recommendation engine · end-user.

Interpretation layer

Brand UI

End-user product

owner: partner

Decision responsibility firewall: Zone A ↔ B = NPA accountability. Zone C = partner accountability. No interpretation data flows back into Zone A.

03 — RESPONSIBILITY MATRIX

What we do, and what we deliberately leave out.

WE DO

WE DON'T

Process static biological signals

Process behavioral signals, wearables, or biometric authentication

Produce standardized numerical indicators

Produce conclusions, personality labels, or rankings

Ensure determinism & an audit trail

Promise accuracy of an end-state forecast

Provide the schema & API contract

Provide UI, narrative, or recommendation logic

Support partners through governance & compliance

Contact a partner's end-users directly

Retain request logs for technical audit

Retain individual identity beyond tenant scope

04 — OUTPUT SAMPLE

What actually comes out of the engine.

The output is data — not a conclusion. The schema is stable, deterministic, and documented as a contract.

200 OK · 412 B

{
  "request_id": "npa_req_01HF8N7K3XQZ9YR2V5W6M8C4P1",
  "tenant_id": "tnt_edutech_acme",
  "captured_at": "2026-05-20T09:42:18.116Z",
  "schema_version": "npa.output.v1",

  "indices": {
    "ridge_count_total": 142,
    "ridge_density_index": 0.642,
    "asymmetry_index": 0.184,
    "complexity_score": 0.71,
    "pattern_distribution": {
      "loop": 0.6,
      "whorl": 0.3,
      "arch": 0.1
    }
  },

  "metadata": {
    "stability_score": 1.000,
    "capture_quality": 0.97,
    "ref_population": "ID_2024_v3",
    "engine_version": "npa-engine-3.4.1"
  },

  "interpretation": null,

  "_disclaimer": "This output is data, not a conclusion. Interpretation is the tenant's responsibility."
}

→interpretation: null is not a typo. It's a promise.

05 — INTEGRATION

Three steps, hands-on with our integration team.

Capture

The partner integrates the capture SDK (mobile/web) or uses a certified partner device.

Process

Signals are sent to the engine via signed request. Normalization is deterministic — the same input produces the same output.

Receive

Output is delivered via webhook or polled. The partner brand manages the interpretation layer & UI.

Discuss integration View pricing

How NPA transforms biological signal into structured data.