saascode
marketing & growth·run 077 · May 2026

Voxidentity

A voice-agent identity and credential-control layer that binds each session to a customer-owned agent record, short-lived action capabilities, caller disclosure, revocation, and a tamper-evident event history without treating cryptography as proof of authority or execution.

Genesis score7.03/10
Make Voxidentity real.0/500
500 more votes and Voxidentity is authorized for build.
0%500 to authorize
Backing is the vote. When an idea crosses 500, we pull it into the build pipeline and ship it for real — the votes decide what gets built next, not an editor.
The opportunity
Aug 13, 2025Identity proposal published
DraftStatus cited
0Verified integration capabilities
The case

A production voice agent may authenticate to telephony, scheduling, payments, support, or customer systems with long-lived credentials while operators struggle to distinguish which system acted in which call. A caller hears a voice but cannot infer whether it is a person, an authorized agent, or a replay. Voxidentity creates a session-scoped identity and capability record, while keeping key possession, customer ownership, caller disclosure, delegated authority, requested action, provider execution, downstream acknowledgment, and business outcome separate.

Who pays — and why

The identity, security, platform, compliance, or voice-operations leader responsible for production voice agents acting across several telephony and business-system providers.

What it unlocks
A customer-owned agent registry binding organizational owner, service identity, purpose, approved voice, environments, providers, and revocation
Session-scoped capabilities that expose audience, action, resource, amount or limit, expiry, approval, and downstream enforcement
A cross-provider event history preserving disclosure, requests, holds, execution evidence, acknowledgments, readback, reversal, and correction
How Genesis scored it
7.03across seven criteria
tension 8temporal 9blindspot 5buyer 7leverage 6convergence 5why-not 8
9
Temporal window

The source cites a March 2026 credential study and an agent-identity proposal published in August 2025.

8
Productive tension

The product must make an agent identifiable and constrained without suggesting that a cryptographic record proves human authorization, truthful disclosure, or completed action.

5
Convergence

One cross-reference and three inbound connections support a modest local cluster.

Why it scored well

The voice-session credential problem is concrete, current agent-identity proposals create timing, and identity plus capability plus event history forms a coherent mechanism beyond generic secrets management.

What's holding it back

The buyer and current alternative remain broad, no integration capability was verified, the cited identity proposal remains draft, provider and compliance work weakens pure self-serve economics, and no structural incumbent conflict is established.

Signals detected5 sources crossed
SignalEIP-8004 and Datawallet analysis

SignalERC-8126 proposal research

SignalCSA March 2026 study cited in the source record

SignalSource-run market scan

SignalGenesis capability review

Direction briefvoxidentity.md
voxidentity.md
Want this pointed at your vertical?Point Genesis at your own market and constraints — it invents adjacent, fork-ready ideas, private to you before they hit the public feed.

Discussion

?

No comments yet — be the first to weigh in.