HTTP, credentials and identity
Configure Agent, Host, Admin and Evaluator identities separately.
Listener
rsia serve defaults to 127.0.0.1:7788, namespace default and Agent actor http-agent. Complete deployment-side HTTPS and access control before exposing it remotely.
Startup credentials
| Environment variable | Server identity |
|---|---|
RSIA_HTTP_TOKEN | Agent tools |
RSIA_HOST_TOKEN | Trusted host integration |
RSIA_ADMIN_TOKEN | Administrator |
RSIA_EVALUATOR_TOKEN | Independent evaluator |
Generate and inject credentials securely; keep them out of URLs, source and logs. The management client's RSIA_MANAGEMENT_TOKEN authenticates to an existing server identity; it does not create one.
Trusted startup configuration binds identity. Request headers such as x-role, x-namespace and x-actor cannot select higher authority.
Routes
Model tools use /v1/tools/prepare, feedback, propose and inspect. Host facts and receipts use /v1/host/trace, snapshot and application. Management uses /v1/manage/{operation} and job status/cancellation routes.
Construct payloads from the current protocol types and check tool schemas and role scope after connecting. Missing authentication configuration may return 503; malformed requests and unauthorized identities are different failures. Do not disable authentication to make a demonstration pass.