Common questions
Concrete answers about source availability, identity, authority and interoperability.
Which SDKs exist?
TypeScript, Rust, Python, Go, Swift and Kotlin source implementations are present. Their versions, runtime floors and API coverage differ. Use the SDK table and package catalog. Source manifest names are not proof that a given registry/tag is public.
Does a DID prove a human is behind an agent?
A DID and a valid signature establish a cryptographic relationship under the relevant verification contract. Personhood, organizational legitimacy and privileged authority require additional assurance and verifier-owned policy. A kind named HMR or MHR is not that proof by itself.
Can verification work offline?
Some local document and token checks can run with all required trusted material available locally. Current privileged authority may need fresh anchor/revocation evidence. An unavailable required source must not be converted into authorization success.
Are keys portable across the six languages?
Do not assume identical encryption keys from the same seed. The implementations use different derivation paths/algorithms and optional bindings. ACT interoperability is a separate contract. Read key management.
Does creating an MHR run a threshold ceremony?
No. The current create_mhr convenience helper creates a single keypair and local document. An actual threshold-backed identity requires the configured key-share ceremony and custody workflow. See MHR and FROST.
Can I use OAS without Arsenal or AEGIS?
Yes, direct OAS primitives can create and verify local identity documents. That does not provision a broker or establish the authority required by a separate privileged service. OAS SDK describes its independent modules.
Where is the REST API?
The standalone server mounts three routes. The HTTP adapter implements three different handshake routes. The Arsenal broker is a separate service. There is no universal hosted DID/key CRUD service implied by these libraries.
How should an agent read these docs?
Use the agent guide, task-scoped .md pages, /llms.txt, and the read-only docs MCP endpoint. Never send private keys, seeds or sessions to a documentation search.