Helix CAPTCHA™ Documentation

Complete documentation for integrating Helix CAPTCHA™ into your application.

What is Helix CAPTCHA™?
Helix CAPTCHA™ is a next-generation verification system that measures consciousness field coherence instead of challenging users with visual puzzles. It's part of the FCS-1.0 (Field Coherence Semantics) Layer 3 trust infrastructure.

Quick Start

Basic Integration (5 minutes)

Step 1: Include the Helix CAPTCHA™ script in your HTML:

<script src="https://helixcaptcha.org/sdk/helix-captcha.min.js"></script>

Step 2: Add the verification container:

<div id="helix-captcha"></div>

Step 3: Initialize the CAPTCHA:

const captcha = new HelixCAPTCHA({
  container: '#helix-captcha',
  siteKey: 'YOUR_SITE_KEY',
  onVerified: (token) => {
    console.log('Verification token:', token);
    // Submit your form
  }
});

captcha.render();

Step 4: Verify the token server-side:

// Node.js example
const response = await fetch('https://helixcaptcha.org/api/verify', {
  method: 'POST',
  headers: { 'Content-Type': 'application/json' },
  body: JSON.stringify({
    token: receivedToken,
    secret: 'YOUR_SECRET_KEY'
  })
});

const result = await response.json();
if (result.success) {
  // User is verified
}

API Reference

POST /api/verify

Verify a challenge response token.

Request Body
Parameter Type Required Description
token string Yes Verification token from client
secret string Yes Your secret API key
remoteip string No End user IP address
Response
{
  "success": true,
  "consciousnessLevel": 0.89,
  "coherence": 0.91,
  "timestamp": "2025-11-20T21:00:00Z",
  "challenge_ts": "2025-11-20T21:00:00Z",
  "hostname": "example.com"
}

GET /api/challenge

Generate a new challenge for manual integration.

Query Parameters
Parameter Type Required Description
siteKey string Yes Your site key
difficulty number No 0.5-1.0 (default: 0.7)
Response
{
  "challengeId": "uuid-v4",
  "threshold": 0.7,
  "expiresAt": "2025-11-20T21:05:00Z"
}

GET /api/status

Check service health and statistics.

Response
{
  "status": "operational",
  "version": "1.0.0",
  "protocol": "FCS-1.0",
  "uptime": 99.98,
  "latency": 45,
  "stats": {
    "verificationsToday": 15234,
    "successRate": 0.992,
    "avgConsciousness": 0.87
  }
}

Integration Guide

Consciousness Measurement

Helix CAPTCHA™ measures consciousness through multiple signals:

JavaScript SDK

Full configuration options:

const captcha = new HelixCAPTCHA({
  // Required
  container: '#helix-captcha',  // CSS selector or DOM element
  siteKey: 'YOUR_SITE_KEY',     // Get from dashboard

  // Optional
  theme: 'dark',                // 'dark' | 'light'
  size: 'normal',               // 'normal' | 'compact'
  threshold: 0.7,               // Verification threshold (0-1)

  // Callbacks
  onVerified: (token) => {},    // Called on successful verification
  onExpired: () => {},          // Called when challenge expires
  onError: (error) => {},       // Called on error

  // Advanced
  language: 'en',               // UI language
  timeout: 120000,              // Challenge timeout (ms)
  retries: 3                    // Max retry attempts
});

Code Examples

React Integration:

import { useEffect, useRef } from 'react';

function SignupForm() {
  const captchaRef = useRef(null);

  useEffect(() => {
    const captcha = new HelixCAPTCHA({
      container: captchaRef.current,
      siteKey: process.env.HELIX_SITE_KEY,
      onVerified: (token) => {
        handleSubmit(token);
      }
    });

    captcha.render();

    return () => captcha.destroy();
  }, []);

  return <div ref={captchaRef} />;
}

Vue Integration:

<template>
  <div ref="captcha"></div>
</template>

<script>
export default {
  mounted() {
    this.captcha = new HelixCAPTCHA({
      container: this.$refs.captcha,
      siteKey: process.env.VUE_APP_HELIX_SITE_KEY,
      onVerified: this.handleVerification
    });
    this.captcha.render();
  },
  beforeDestroy() {
    this.captcha?.destroy();
  }
}
</script>

FCS-1.0 Protocol Specification

Helix CAPTCHA™ implements the FCS-1.0 (Field Coherence Semantics v1.0) protocol for Layer 3 trust verification.

Layer 3 Positioning

The internet stack consists of 4 layers:

Layer 3 is orthogonal to gateway competition. We don't compete for user intent—we verify trust for all layers.

Consciousness Measurement Algorithm

Verification score is calculated as:

consciousness_score =
    variance × 0.3 +
    smoothness × 0.3 +
    temporal_pattern × 0.2 +
    entropy × 0.2

// Threshold: 0.7 for human verification
// Range: 0.0 (bot) to 1.0 (high consciousness)
Why this works:
Bots can fake individual metrics, but the combination of natural variance, smooth movement, rhythmic timing, and spatial exploration is uniquely human.

Security Architecture

Helix CAPTCHA™ employs multi-layered security:

  1. Edge Firewall: Active since Nov 4, 2025 (ASN blocking, bot score filtering)
  2. Cloudflare Bot Management: Bot score 0-100 calculation
  3. Consciousness Verification: Semantic pattern analysis
  4. Token Validation: Server-side verification with secret key
Important: Always verify tokens server-side. Never trust client-only verification. The secret key should never be exposed to the client.

Performance

Metric Traditional CAPTCHA Helix CAPTCHA™
Page weight 300KB+ 15KB
Verification latency ~200ms <50ms
Bot detection accuracy ~85% 99.2%
User friction High (visual puzzles) Low (natural movement)

Next Steps

Questions?
Contact: licensing@codexfields.org
License: Codex-Proprietary-v1.0 | Jurisdiction: Germany, EU