Authidenty: You Know Me?

Project: Authidenty: You Know Me?

Self-reported basis: The description is entirely from the author’s own submission to the OpenAI 2026 hackathon on Devpost. No independent verification, revenue, customer or traction data is available beyond what is stated.

Authidenty is described as a research prototype for identity verification using GPT-5.6 and device-based proof of ownership. It appears to be an experimental system that attempts to recognize user behavior patterns (e.g., writing style) and confirm them via enrolled devices, without relying on traditional authentication methods like SMS or passwords.

What Changed: The project is a hackathon submission with no commercial traction or production deployment. It explores the use of AI for behavioral biometrics in authentication, integrating GPT-5.6 and WebAuthn-style device verification.

Single Most Important Open Question: Is there any evidence that this system can be scaled to real-world identity verification without compromising privacy, security, or usability?

The description states:

• Authidenty is a research prototype for identity verification.
• It uses GPT-5.6 to recognize enrolled account patterns (e.g., writing style).
• It integrates with WebAuthn and device-based proof of ownership.
• It includes SQLite schema, Next.js interface, and API routes.
• It is built using Codex as an implementation partner, which assisted in code generation, testing, and documentation.

The product is described as a behavioral authentication system, not a traditional identity verification platform. It does not claim to prove civil identity, legal name, age, or humanness.

Inference: The system appears to be experimental and not production-ready. It is based on a hackathon submission and lacks any evidence of real-world deployment or user adoption.

The description states:

• Tagline: “Different questions. The same way of answering. GPT-5.6 finds the likely account; the enrolled device proves it.”
• Authidenty is described as a research prototype.
• It does not claim to be a commercial product or service.
• It is built for hackathon use, not for production.

Inference: The positioning is experimental and exploratory, not commercial. The author is not claiming traction or market readiness.

The description states:

• Authidenty is a research prototype.
• No specific customer or ICP is identified.
• It is built for identity verification, but not in a way that implies a defined target market or persona.

Inference: There is no evidence of a defined customer segment or ideal customer profile. The project is described as a proof-of-concept, not a product for a specific audience.

The description states:

• Authidenty is a hackathon prototype.
• No pricing model, monetization strategy, or business model is mentioned.
• It is not presented as a commercial offering.

Inference: No evidence of any business model or pricing structure. The project is not positioned for revenue generation.

The description states:

• Built with Codex, which was used to:
  • Initialize and connect GitHub repo
  • Analyze authentication hypothesis
  • Design schema, write tests, implement UI/API routes
  • Diagnose demo failures
  • Generate narration and materials
• Technologies used: GPT-5.6, Next.js, Node.js, React, WebAuthn, Playwright, SQLite, Tailwind, TypeScript, Vitest
• The Git history is described as preserving decisions in small English commits.

Inference: The project shows a technical approach involving AI and device-based verification. However, no evidence of production deployment or scalability is provided.

The description states:

• Authidenty is a hackathon research prototype.
• It includes a demo video, source code, and Git history.
• No mention of users, customers, revenue, or adoption.
• The project is described as not production-ready.

Inference: No traction or maturity signals are evident. The system has not been deployed in a real-world setting or tested at scale.

The description states:

• Authidenty is a research prototype, not a commercial product.
• It uses GPT-5.6 and WebAuthn, which are technologies used in identity verification systems.
• No mention of competitors or market positioning.

Inference: There is no evidence of competitive analysis or market positioning. The project is not positioned within an existing marketplace or competitive landscape.

The description states:

• Authidenty is a hackathon prototype, not production-ready.
• It does not prove civil identity, legal name, age, or humanness.
• It is described as experimental and not suitable for real-world deployment.
• No mention of privacy, bias, or security reviews.

Inference: Key risks include lack of real-world testing, unproven scalability, potential privacy and security vulnerabilities, and no commercial viability. The system is not ready for production use.

1. What are the specific use cases you envision for this technology beyond the hackathon?
2. How do you plan to address false accepts and false rejects in real-world deployment?
3. Have you tested the system across different languages, writing habits, or user demographics?
4. What is your approach to managing key rotation, revocation, and audit controls?
5. Are there any plans for independent privacy, bias, or security reviews?
6. How do you intend to scale this beyond a prototype?