OAS identity
DIDs, documents, local proofs and explicitly trusted authority.
OAS defines identity primitives for the agent ecosystem: identifier parsing, document construction, cryptography, lineage, resolution and attestations. Nine Rust packages publish at 1.1.1, all mapped in the Rust catalog; TypeScript OAS packages have their own 1.0.2 exports.
A DID such as did:oas:example:agent:weather-bot names an entity. It is not a bearer credential and does not grant access. agent:instance is a compound kind; use the actual parser.
Choose the verification level for the action
Use local document/cryptographic checks when that is the required contract. For privileged actions, use the typed authority API with the configured anchor/source and verifier trust policy. Required scope, root, finality, freshness and revocation must be evaluated for the operation.
SDK 0.7.2 supports local and explicitly authorized self-rooted identities without an anchor. Shared authority is configured by the receiver. The published Rust 1.1.1 anchor policy includes historical Sigil defaults; the separate EAS adapter can be configured on Base. Neither an adapter nor a document chooses the verifier's trust roots or proves a completed network migration. See current verification and production integration.
Read the OAS SDK, entity kinds, lineage, and anchors.