Human Verification API

The Human Verification API is the OMXUS application programming interface that allows external companies and services to verify that a user is a real, unique human being — without accessing any personal data. It is the primary revenue mechanism for the OMXUS network and the interface through which the system delivers value to the broader economy.

The OMXUS developer portal provides API access for human verification integration.

The Problem

The modern internet has no reliable way to distinguish real humans from bots, fake accounts, or duplicate identities. This creates cascading problems:

• Advertising fraud — An estimated $100 billion annually is spent on ads shown to bots, not humans
• Bot manipulation — Social media platforms host millions of automated accounts that distort public discourse
• KYC costs — Financial institutions spend billions on Know Your Customer compliance, passing costs to consumers
• Content authenticity — AI-generated content is indistinguishable from human-created content
• Election interference — Automated accounts amplify disinformation at scale
• Review fraud — Fake reviews undermine consumer trust in marketplaces

Existing solutions require users to surrender personal data (government ID, biometrics, phone numbers) to centralized authorities, creating privacy risks and surveillance infrastructure.

How the API Works

Verification Flow

1. Business sends a verification request to the OMXUS API
2. User receives a prompt to tap their NFC ring
3. Ring generates a cryptographic proof: "This is a unique, verified human"
4. OMXUS network validates the proof against the web of trust
5. API returns a boolean response to the business: verified or not

What Is Revealed

• The user is a real, unique human (not a bot or duplicate)
• The user has been vouched for by the web of trust

What Is NOT Revealed

• Name, age, gender, location, or any demographic data
• Identity of the user's vouchers
• The user's voting history or network activity
• Any information beyond "verified human: yes/no"

This is accomplished through zero-knowledge proofs — cryptographic techniques that prove a statement is true without revealing the underlying data.

Use Cases

Industry	Use Case	Current Solution	OMXUS Advantage
Advertising	Verify ad viewers are human	CAPTCHA, fingerprinting	No friction, privacy-preserving
Financial services	KYC compliance	Document upload, manual review	Instant, no personal data exposed
Social media	Prevent bot accounts	Phone number, email	One-person-one-account guarantee
E-commerce	Authentic reviews	Purchase verification	Unique human per review
Content platforms	Verify human authorship	None reliable	Cryptographic proof of human origin
Voting/surveys	Prevent ballot stuffing	IP tracking, accounts	One-person-one-vote guarantee

The OMXUS dashboard provides businesses with real-time verification analytics.

Revenue Model

The OMXUS revenue model: businesses pay for API access; revenue flows to the network and its members.

The Human Verification API is the core of the OMXUS economic model:

Pricing

• Businesses pay per verification request
• Tiered pricing based on volume
• Enterprise plans for high-volume integrations

Revenue Distribution

• Revenue flows to the OMXUS network
• Members share in revenue generated by their participation
• The network's value increases as membership grows (network effects)

Economic Alignment

This model creates a critical alignment: OMXUS makes money by protecting user privacy, not by selling user data. The business model and the ethical model are identical, eliminating the conflict of interest that plagues advertising-funded platforms.

See Earning Money for details on how members participate in revenue.

Privacy Architecture

The API is designed around the principle that identity verification does not require identity disclosure:

• Zero-knowledge proofs — Mathematical verification without data exposure
• No data storage — The API does not retain verification records linked to identities
• User consent — Every verification requires an active ring tap; no passive verification
• Auditability — Businesses can verify the system works without accessing user data

Integration

The API follows standard REST conventions:

• JSON request/response format
• API key authentication for businesses
• Webhook support for asynchronous verification
• SDKs for major platforms and languages

See Also

• Earning Money
• Technical Architecture
• Decentralized Identifiers
• Web of Trust
• Sybil Resistance
• Main Page

References

• Goldwasser, S., Micali, S., & Rackoff, C. (1989). "The Knowledge Complexity of Interactive Proof Systems." SIAM Journal on Computing, 18(1), 186-208.
• Juniper Research. (2023). Ad Fraud: Future Assessment, Key Vertical Analysis & Market Forecasts 2023-2028.
• W3C. (2022). Verifiable Credentials Data Model v1.1. W3C Recommendation.
• Narayanan, A., & Shmatikov, V. (2008). "Robust De-anonymization of Large Sparse Datasets." IEEE Symposium on Security and Privacy.