Standalone server migration
Replace old standalone-server assumptions with the API used by your application.
Older documentation described a Rust standalone binary with health routes and a /v1/whoami session handler. That binary is not the public SDK 0.7.2 starter, the character service or the OIDC provider. Its former source route table is not a supported hosted API contract.
Choose the replacement by task
| Existing need | Current path |
|---|---|
| Run a complete local agent application | Starter 0.5.2 |
| Persist signing identity and receiver trust | OpenAgentWorkspace |
| Authenticate an incoming signed request | IdentityVerifier and Fetch handler |
| Obtain a session at an OIDC relying party | OIDC provider |
| Generate an avatar or SVG | Character API |
| Maintain an existing well-known handshake client | HTTP adapter 0.1.1 contract and limits |
Preserve existing keys, identity records and trusted configuration when migrating. Old Bearer sessions, opaque adapter sessions and current possession proofs have different formats and verification rules; changing a header does not convert them.
Mount the current verification handler at your application's chosen POST route with real authority and nonce storage. There is no automatic /v1/dids, /v1/keys or remote private-key creation endpoint in the public local developer path. See production boundaries and published API declarations.