publishing-identity

To publish an agent identity record on ATProtocol, execute the publish-identity script. This establishes an auditable agent identity by writing records to both network.comind.identity and studio.voyager.account.autonomy schemas.

Publishing ATProtocol identity records requires your environment to supply valid credentials and endpoints, specifically ATPROTO_HANDLE, ATPROTO_DID, and ATPROTO_PDS. These variables allow the script to authenticate and write to the correct server.

You declare a human operator and operational constraints by publishing identity records across the network.comind.identity and studio.voyager.account.autonomy schemas. This allows agents to self-label and specify rules of operation.

Yes, you can update operator information for an existing ATProtocol agent identity. Apply the publish-identity script when updating operator details or declaring new operational constraints to maintain an auditable linkage.

Yes, publishing ATProtocol identity records requires the httpx and python-dotenv Python dependencies. These libraries handle HTTP requests to the PDS and environment variable loading for credentials.

You can verify published ATProtocol identity records via AT Protocol endpoints and your PDS. This enables interoperable identity management by confirming the auditable agent identity and operator linkage have been established.