What Is an Identity Gateway?
An identity gateway lets government agencies accept digital credentials from multiple wallets, formats, and issuers through a single standards-based integration point.
SpruceID Blog
Thoughtful perspectives on identity, interoperability, and the systems that turn public policy into usable services.
When an AI Agent Acts on Behalf of a Resident
Government services assume the person interacting is the person acting. AI agents challenge that assumption, creating new questions about authorization, identity proofing, and auditability.
FinCEN Confirms Banks Can Accept Digital Credentials. Now They Need to Verify Them.
FinCEN and four federal banking regulators have jointly confirmed that government-issued verifiable digital credentials, including mobile driver's licenses, qualify as documentary identification under the CIP Rule.
Utah SB 275 Explained: What the SEDI Law Actually Does
Utah's SB 275 creates a legal framework for state-endorsed digital identity with 11 enumerated rights, a Duty of Loyalty, and open standards requirements. Here is what the law actually establishes.
AI Agents Have an Authorization Problem, Not Just an Identity Problem
Knowing who an agent represents is not enough. Enterprises need to know what that agent is allowed to do, with authority that is granular, portable, and revocable.
From PDF Uploads to Verifiable Evidence: Modernizing Benefits Documentation
A digital upload portal improves document transmission but does not eliminate verification work. For high-volume evidence types, structured verifiable evidence can reduce manual interpretation while improving provenance.
SEDI vs. Mobile Driver's Licenses: What's the Difference?
An mDL is a digital credential. SEDI is the framework governing how credentials, wallets, issuers, and verifiers interact. Understanding the difference matters for states building digital identity infrastructure.
What Is Identity Proofing? A Guide for Government IT Leaders
Identity proofing establishes that a person is who they claim to be. For government services, the level of assurance required depends on the risk, and getting that calibration right shapes every downstream decision.
Build, Integrate, or Reuse? An Architecture for HR1 Verification
States face three architectural models for HR1 verification, each with different implications for scalability, privacy, and vendor lock-in. The question is which model becomes the default for which type of evidence.
From Rights to Architecture: How SEDI Turns Digital Identity Principles Into Technical Requirements
SEDI's Digital Identity Bill of Rights creates obligations that policy language alone cannot enforce. Each right implies architectural constraints on verification, credential formats, wallet ecosystems, and governance.
Who Sent This Agent? The Missing Identity Layer for AI Agents
As AI agents take on more consequential actions, they need a way to prove who authorized them and what they’re allowed to do. In this post, we explore an identity model that preserves accountability without creating a new surveillance layer.
Medicaid and SNAP Need Different Rules, Not Separate Verification Infrastructure
As states implement HR1, Medicaid and SNAP can share verification infrastructure without sharing eligibility rules, reducing duplicate verification while preserving privacy and user control.
