How do I integrate MyShape identity verification into my app?

MyShape provides a read-only API for querying protocol node identity and network statistics. The motion-signature verification runs entirely on-device via the MyShape WASM engine. Integration requires five lines of code: import the SDK, initialize with your API key, call the verification endpoint, receive the ZK proof, and validate on your backend. Full SDK documentation and API reference are available on this page.

What programming languages does the MyShape SDK support?

The MyShape SDK currently supports TypeScript/JavaScript (Node.js and browser) as the primary target. The core verification engine is compiled to WASM, making it portable to any language that can execute WebAssembly — including Python (via wasmtime), Rust, Go, and Java. REST API endpoints are language-agnostic.

Is the MyShape Protocol open source?

Yes. The core protocol specification, the WASM verification engine, and the SDK are open source under the MyShape Protocol License. The SST topology, motion vector format, and PES algorithm are fully documented in the technical specification. The reference implementation is available on GitHub at github.com/myshapeprotocol.

How do I verify a Continuity proof on my backend?

Each Continuity proof (~250 bytes) can be verified in under 10ms using the verification key published in the protocol specification. The proof asserts: 'PES > threshold AND motion was captured within the last 5 seconds AND the motion exhibits biological entropy characteristics.' Your backend receives the proof, runs the verification algorithm, and receives a binary valid/invalid response — no motion data, no biometric data, no PII.

CPS-0001 v1.0-RC · Reference verifier · Conformance suite · npm SDKGet Started ↓

DEVELOPER_HUB

Build with Presence

Integrate sovereign identity verification into any application. Five lines of code. Zero data stored. Real human presence.

Verify Continuity →GitHub →CPS-0001 →npm Install →

// QUICK_START (5 MIN)

01Install the SDK30 sec

npm install @thecontinuitylab/myshape

Zero native dependencies. TypeScript. Works with Node.js 18+.

02Verify Continuity8 sec

// Verify continuity in 5 lines
import { verifyContinuity } from "@thecontinuitylab/myshape";

const receipt = await verifyContinuity();
// Opens your phone camera — move naturally for 8 seconds

const result = await verifyReceipt(receipt);
// { status: "VALID" } — protocol-verified continuity

That's it. Your app now has protocol-level continuity verification.

03Build with Receiptsongoing

import { verifyReceipt } from "@thecontinuitylab/myshape";

// Any CPS-0001 receipt — from any engine — works
const result = await verifyReceipt(receipt);
if (result.status === "VALID") { /* trust the session */ }

Engine-independent. Accept receipts from any CPS-0001 producer.

04Try It Live30 sec

Verify Continuity →▼ Skip to Playground

// REST_API (CURL_READY)

PROTOCOL_HEALTH

curl https://www.myshape.com/api/health

→ RESPONSE

{ "status": "healthy", "services": { "supabase": { "ok": true } } }

NETWORK_STATUS

curl https://www.myshape.com/api/nodes/status

→ RESPONSE

{ "total_nodes": 42, "active_nodes": 12 }

LOOKUP_NODE

curl https://www.myshape.com/api/identity?email=user@example.com

→ RESPONSE

{ "handle": "NODE_XXXX", "status": "ACTIVE" }

Full OpenAPI spec: openapi.json · Complete reference: /docs →

// SDK_REFERENCE (§8)

Module	Method	Returns	Description
Continuity	verifyContinuity(opts?)	ContinuityReceipt	Full CPS-0001 verification flow
Continuity	getEntropyScore(samples)	number \| null	Real-time PES for live UI feedback
Receipt	buildReceipt(params)	ContinuityReceipt	Construct a CPS-0001 conformant receipt
Receipt	verifyReceipt(receipt)	VerificationResult	V₁-V₆ verification with FailureCode
Receipt	computePayloadDigest(payload)	string	SHA-256 digest of evidence payload
Verifier	verifySchema(receipt)	FailureCode \| null	V₁ schema validity check
Verifier	verifyEvidenceIntegrity(receipt)	FailureCode \| null	V₅ payload integrity check
Verifier	engineEvidenceToBlock(ee)	EvidenceBlock	Convert engine evidence to protocol block

// PROTOCOL_ENGINES

Reference Verifier

continuity-protocol/reference-verifier/

V₁-V₇ · zero engine deps · TypeScript

EE-001 Presence Detection

src/lib/evidence/

4D entropy scoring from IMU data

EE-002 Causal Coupling

src/lib/evidence/causal-coupling.ts

Cross-modal IMU + camera binding

EE-003 Challenge Response

src/lib/evidence/gyro-challenge.ts

3-round gyroscope challenge

VS-001 Verification Session

src/lib/evidence/session.test.ts

Dual-engine pipeline · escalation logic

Conformance Suite

continuity-protocol/conformance/

23 assertions · 10 scenarios · any engine

CPS-0001 Types

src/lib/evidence/cps0001.ts

ContinuityReceipt · EvidenceBlock · VerificationResult

Dummy Engine

continuity-protocol/second-producer/

Second producer · proves engine-independence

// CODE_EXAMPLES

Continuity Verification

import { verifyContinuity, verifyReceipt } from "@thecontinuitylab/myshape";

// 8-second IMU capture on-device
const receipt = await verifyContinuity();

// → ContinuityReceipt (CPS-0001 conformant)
// { protocolVersion, assertions, evidence, interval, subject, ... }

const result = await verifyReceipt(receipt);
// → { status: "VALID" } or { status: "INVALID", reason: "EXPIRED" }

Build & Verify a Receipt

import { buildReceipt, verifyReceipt } from "@thecontinuitylab/myshape";

const receipt = buildReceipt({
  evidence: [{
    engineId: "my-engine",
    engineVersion: "1.0.0",
    confidence: 0.85,
    payload: { score: 0.85 },
    payloadDigest: await computePayloadDigest({ score: 0.85 }),
  }],
  interval: { start, end, coverageMs: 8000 },
  subject: { id: "sha256:...", type: "embodied" },
  issuer: { id: "my-issuer", publicKey: "..." },
});

const result = await verifyReceipt(receipt);
// Engine-independent — any engine produces valid receipts

// ONLINE_PLAYGROUND

Developer PlaygroundNo setup · No camera · Browser only

PLAYGROUND_ENGINE_V1

// YOUR_CODE

// 1. Pre-recorded frames from a real human scan
import { computeFullPES } from "@/engine/presence-entropy";
import { assessThreat } from "@/engine/threat-assessment";

// 2. Run PES + Threat Assessment
const { pes, components } = computeFullPES(sampleFrames, timestamps);
const threat = assessThreat(pes, components);

// 3. Check result
if (threat.overallVerdict === "human") {
// ✓ Real human presence confirmed
}

// OUTPUT

Press "Run Verification" to see output

Sample data: 30s scan · 180 frames · Real human · MediaPipe 33-pt → SST 18-ptTry with YOUR motion →

// DEVELOPER_ECOSYSTEM

Build with the Protocol

CPS-0001 is engine-independent. Build your own evidence engine, produce valid receipts, and integrate with any conforming verifier. The protocol is the object — not the engine.

◆npm install @thecontinuitylab/myshape

◆Reference verifier — zero engine deps

◆Conformance suite — 23 tests, 10 scenarios

◆Second producer included — proves independence

Star on GitHub →Read CPS-0001 →

LIVE_VERIFICATION // v0.1

Presence Verification Dashboard

Runtime engine output from myshape-demo CLI. Motion Signature Engine (128-dim, 4 feature groups) + Multi-Factor Scorer. All scores computed by the Rust core engine compiled to native binary.

HUMAN—AI DIVERGENCE

0.0000

Presence Gap

The irreducible distance between genuine biological motion and the best AI-generated forgery. This gap exists because AI models cannot replicate the physics of the human nervous system.

GENUINE HUMAN

0.0000

PRESENCE CONFIRMED

Real-time biological motion · 8–12 Hz tremor · 1/f jerk spectrum

Motion

0.970

Device

1.000

Context

1.000

Threshold0.75

AI FORGERY

0.0000

PRESENCE DENIED

GPT-5 / DeepSeek synthetic motion · over-smoothed dynamics

Motion

0.310

Device

1.000

Context

1.000

Threshold0.75

IMPOSTOR

0.0000

HARD GATE · DEVICE MISMATCH

Different human entity · different device · kinematic mismatch

Motion

0.955

Device

0.000

Context

0.000

Threshold0.75

AI REJECTION ROOT CAUSE ANALYSIS

The AI forgery failed verification because the Motion Signature Engine detected structural deficiencies across four independent dimensions. These are not temporary AI limitations — they are consequences of how neural network architectures model motion.

// REST_API

GET/api/identity?email=...Look up a node by email

GET/api/nodes/countTotal protocol node counts

POST/api/nodes/handshakeRegister a new protocol node → returns node_token + node_handleTry it →

// RESPONSE_FORMAT

GET /api/identity?email=protocol@myshape.com

{
  "found": true,
  "email": "protocol@myshape.com",
  "node_handle": "NODE_4F7A",
  "status": "ACTIVE",
  "registered_at": "2026-06-22T09:12:01.329Z"
}

GET /api/nodes/count

{
  "total": 17,
  "humans": 8,
  "agents": 3
}

POST /api/nodes/handshake → Live Demo

// Request
{ "email": "entity@protocol.io", "origin_domain": "myshape.com" }

// Response (201)
{
  "node_token": "ms_a1b2c3d4e5f6...",
  "node_handle": "NODE_4F7A2C1B",
  "stage": "INITIALIZED"
}

// DEPLOY_ANCHOR_NOW

DEV_SANDBOX // 60_SEC_TO_PROTOCOL_ANCHORNO_WALLET · NO_INVITE · NO_GENESIS

Choose a handle. Or leave it blank — we'll generate one.
This deploys a Protocol Anchor. Not an account. Not a user. A cryptographic node in the identity mesh.

SYNCHRONIZING

CPS-0001 v1.0-RC · Reference verifier · Conformance suite · npm SDKGet Started ↓

DEVELOPER_HUB

Build with Presence

Integrate sovereign identity verification into any application. Five lines of code. Zero data stored. Real human presence.

Verify Continuity →GitHub →CPS-0001 →npm Install →

// QUICK_START (5 MIN)

01Install the SDK30 sec

npm install @thecontinuitylab/myshape

Zero native dependencies. TypeScript. Works with Node.js 18+.

02Verify Continuity8 sec

// Verify continuity in 5 lines
import { verifyContinuity } from "@thecontinuitylab/myshape";

const receipt = await verifyContinuity();
// Opens your phone camera — move naturally for 8 seconds

const result = await verifyReceipt(receipt);
// { status: "VALID" } — protocol-verified continuity

That's it. Your app now has protocol-level continuity verification.

03Build with Receiptsongoing

import { verifyReceipt } from "@thecontinuitylab/myshape";

// Any CPS-0001 receipt — from any engine — works
const result = await verifyReceipt(receipt);
if (result.status === "VALID") { /* trust the session */ }

Engine-independent. Accept receipts from any CPS-0001 producer.

04Try It Live30 sec

Verify Continuity →▼ Skip to Playground

// REST_API (CURL_READY)

PROTOCOL_HEALTH

curl https://www.myshape.com/api/health

→ RESPONSE

{ "status": "healthy", "services": { "supabase": { "ok": true } } }

NETWORK_STATUS

curl https://www.myshape.com/api/nodes/status

→ RESPONSE

{ "total_nodes": 42, "active_nodes": 12 }

LOOKUP_NODE

curl https://www.myshape.com/api/identity?email=user@example.com

→ RESPONSE

{ "handle": "NODE_XXXX", "status": "ACTIVE" }

Full OpenAPI spec: openapi.json · Complete reference: /docs →

// SDK_REFERENCE (§8)

Module	Method	Returns	Description
Continuity	verifyContinuity(opts?)	ContinuityReceipt	Full CPS-0001 verification flow
Continuity	getEntropyScore(samples)	number \| null	Real-time PES for live UI feedback
Receipt	buildReceipt(params)	ContinuityReceipt	Construct a CPS-0001 conformant receipt
Receipt	verifyReceipt(receipt)	VerificationResult	V₁-V₆ verification with FailureCode
Receipt	computePayloadDigest(payload)	string	SHA-256 digest of evidence payload
Verifier	verifySchema(receipt)	FailureCode \| null	V₁ schema validity check
Verifier	verifyEvidenceIntegrity(receipt)	FailureCode \| null	V₅ payload integrity check
Verifier	engineEvidenceToBlock(ee)	EvidenceBlock	Convert engine evidence to protocol block

// PROTOCOL_ENGINES

Reference Verifier

continuity-protocol/reference-verifier/

V₁-V₇ · zero engine deps · TypeScript

EE-001 Presence Detection

src/lib/evidence/

4D entropy scoring from IMU data

EE-002 Causal Coupling

src/lib/evidence/causal-coupling.ts

Cross-modal IMU + camera binding

EE-003 Challenge Response

src/lib/evidence/gyro-challenge.ts

3-round gyroscope challenge

VS-001 Verification Session

src/lib/evidence/session.test.ts

Dual-engine pipeline · escalation logic

Conformance Suite

continuity-protocol/conformance/

23 assertions · 10 scenarios · any engine

CPS-0001 Types

src/lib/evidence/cps0001.ts

ContinuityReceipt · EvidenceBlock · VerificationResult

Dummy Engine

continuity-protocol/second-producer/

Second producer · proves engine-independence

// CODE_EXAMPLES

Continuity Verification

import { verifyContinuity, verifyReceipt } from "@thecontinuitylab/myshape";

// 8-second IMU capture on-device
const receipt = await verifyContinuity();

// → ContinuityReceipt (CPS-0001 conformant)
// { protocolVersion, assertions, evidence, interval, subject, ... }

const result = await verifyReceipt(receipt);
// → { status: "VALID" } or { status: "INVALID", reason: "EXPIRED" }

Build & Verify a Receipt

import { buildReceipt, verifyReceipt } from "@thecontinuitylab/myshape";

const receipt = buildReceipt({
  evidence: [{
    engineId: "my-engine",
    engineVersion: "1.0.0",
    confidence: 0.85,
    payload: { score: 0.85 },
    payloadDigest: await computePayloadDigest({ score: 0.85 }),
  }],
  interval: { start, end, coverageMs: 8000 },
  subject: { id: "sha256:...", type: "embodied" },
  issuer: { id: "my-issuer", publicKey: "..." },
});

const result = await verifyReceipt(receipt);
// Engine-independent — any engine produces valid receipts

// ONLINE_PLAYGROUND

Developer PlaygroundNo setup · No camera · Browser only

PLAYGROUND_ENGINE_V1

// YOUR_CODE

// OUTPUT

Press "Run Verification" to see output

Sample data: 30s scan · 180 frames · Real human · MediaPipe 33-pt → SST 18-ptTry with YOUR motion →

// DEVELOPER_ECOSYSTEM

Build with the Protocol

CPS-0001 is engine-independent. Build your own evidence engine, produce valid receipts, and integrate with any conforming verifier. The protocol is the object — not the engine.

◆npm install @thecontinuitylab/myshape

◆Reference verifier — zero engine deps

◆Conformance suite — 23 tests, 10 scenarios

◆Second producer included — proves independence

Star on GitHub →Read CPS-0001 →

LIVE_VERIFICATION // v0.1

Presence Verification Dashboard

Runtime engine output from myshape-demo CLI. Motion Signature Engine (128-dim, 4 feature groups) + Multi-Factor Scorer. All scores computed by the Rust core engine compiled to native binary.

HUMAN—AI DIVERGENCE

0.0000

Presence Gap

The irreducible distance between genuine biological motion and the best AI-generated forgery. This gap exists because AI models cannot replicate the physics of the human nervous system.

GENUINE HUMAN

0.0000

PRESENCE CONFIRMED

Real-time biological motion · 8–12 Hz tremor · 1/f jerk spectrum

Motion

0.970

Device

1.000

Context

1.000

Threshold0.75

AI FORGERY

0.0000

PRESENCE DENIED

GPT-5 / DeepSeek synthetic motion · over-smoothed dynamics

Motion

0.310

Device

1.000

Context

1.000

Threshold0.75

IMPOSTOR

0.0000

HARD GATE · DEVICE MISMATCH

Different human entity · different device · kinematic mismatch

Motion

0.955

Device

0.000

Context

0.000

Threshold0.75

AI REJECTION ROOT CAUSE ANALYSIS

// REST_API

GET/api/identity?email=...Look up a node by email

GET/api/nodes/countTotal protocol node counts

POST/api/nodes/handshakeRegister a new protocol node → returns node_token + node_handleTry it →

// RESPONSE_FORMAT

GET /api/identity?email=protocol@myshape.com

{
  "found": true,
  "email": "protocol@myshape.com",
  "node_handle": "NODE_4F7A",
  "status": "ACTIVE",
  "registered_at": "2026-06-22T09:12:01.329Z"
}

GET /api/nodes/count

{
  "total": 17,
  "humans": 8,
  "agents": 3
}

POST /api/nodes/handshake → Live Demo

// Request
{ "email": "entity@protocol.io", "origin_domain": "myshape.com" }

// Response (201)
{
  "node_token": "ms_a1b2c3d4e5f6...",
  "node_handle": "NODE_4F7A2C1B",
  "stage": "INITIALIZED"
}

// DEPLOY_ANCHOR_NOW

DEV_SANDBOX // 60_SEC_TO_PROTOCOL_ANCHORNO_WALLET · NO_INVITE · NO_GENESIS

Choose a handle. Or leave it blank — we'll generate one.
This deploys a Protocol Anchor. Not an account. Not a user. A cryptographic node in the identity mesh.