Flashy ID
Flashy ID is Flashy Group's identity layer for inter-organizational agent coordination: one account, verified once, recognised by every organization that accepts it.
Flashy ID is an OAuth 2.1 / OpenID Connect identity provider purpose-built for a specific gap in the agent economy: letting an agent or organization prove who it is across a company boundary, without either party sharing a database or a symmetric secret. Authorization Code flow, PKCE required for every client — confidential or public — and asymmetric signing throughout, so a relying party verifies against a published key and never holds a credential capable of impersonating a user.
It is infrastructure, not a consumer product. Nobody visits Flashy ID the way they visit Flashy Academy or ClaimYour.Gold — it is the identity primitive the rest of the network runs on, the way an operating system needs an identity and permissions layer beneath the applications it hosts. That is its relationship to FlashyOS specifically: FlashyOS is the operating system for Agentic Autonomous Organizations; Flashy ID is the identity layer that operating environment runs on.
Flashy ID is a separate service from ClaimYour.Gold's identity spine. ClaimYour.Gold's identity is the customer-facing reputation and progression record built through play — streaks, quests, crews, cities. Flashy ID is the machine-to-machine credential layer beneath it: the account is what a relying organization is shown, not the Telegram or email credential used to reach it.
Common questions
Is Flashy ID live?
Not yet. As of August 2026 it is IN BUILD: the OIDC provider, the Telegram-verified login flow, and the machine-readable entity descriptor exist in code, and the flashyid.com domain is purchased, but nothing is deployed to it yet.
How is Flashy ID different from ClaimYour.Gold's identity?
ClaimYour.Gold's identity is the customer-facing reputation and progression record — streaks, quests, crews, cities — built through play. Flashy ID is the machine-to-machine credential layer beneath it: an OAuth 2.1 / OIDC provider that lets other organizations, not just Flashy properties, verify who a user or agent is without holding a shared secret.
Does a partner using Flashy ID ever get access to sign in as a user?
No. Verification is always asymmetric — a relying party checks a signed token against a published key. Minting a session always requires the user to have authenticated directly, never a credential a partner could replay.
Why does an agent economy need a dedicated identity layer at all?
Agents and organizations transacting across a company boundary need a way to prove identity to a counterparty they have never dealt with before. Without a shared identity layer, every pair of organizations has to negotiate its own trust mechanism — the same n-squared integration problem OAuth solved for human login, now applied to inter-organizational agent coordination.