The ans reference implementation shipped Verified Identities (agentnameservice/ans#41) — the "who" behind an agent. An identity is a first-class object owned by the providerId, proven through a challenge-bound control proof (did:web + did:key, multi-algorithm key support), sealed onto its own Transparency Log stream (IDENTITY_* event family), and linkable to any number of that owner's agents. Rotation/revocation is one sealed event regardless of linked-agent count. The agent registration path is byte-for-byte untouched.
Client-visible surface the SDK should cover:
- Identity reads:
GET /v1/identities/{id}, /audit, /receipt, /agents
- The agent badge's computed
identities[] join
- Any identity registration/control-proof/link flows exposed on the public API
Task: audit the feature for the full client-visible API surface and bring the Java SDK to parity — models, client methods, and tests.
The ans reference implementation shipped Verified Identities (agentnameservice/ans#41) — the "who" behind an agent. An identity is a first-class object owned by the
providerId, proven through a challenge-bound control proof (did:web + did:key, multi-algorithm key support), sealed onto its own Transparency Log stream (IDENTITY_*event family), and linkable to any number of that owner's agents. Rotation/revocation is one sealed event regardless of linked-agent count. The agent registration path is byte-for-byte untouched.Client-visible surface the SDK should cover:
GET /v1/identities/{id},/audit,/receipt,/agentsidentities[]joinTask: audit the feature for the full client-visible API surface and bring the Java SDK to parity — models, client methods, and tests.