API Reference

SDK HTTP Endpoints

The minimal HTTP session routes Downcity can expose for RemoteAgent

SDK HTTP Endpoints

These SDK routes do not belong to Agent itself.

They are exposed by the City HTTP transport returned from city.http(). City may start the standalone server itself or mount its router in a host server such as the Downcity gateway.

The current core set includes:

  • GET /api/sdk/sessions
  • POST /api/sdk/sessions
  • GET /api/sdk/sessions/:session_id
  • POST /api/sdk/sessions/:session_id/prompt
  • GET /api/sdk/sessions/:session_id/events
  • GET /api/sdk/sessions/:session_id/messages
  • GET /api/sdk/sessions/:session_id/system
  • GET /api/sdk/sessions/:session_id/interactions
  • GET /api/sdk/sessions/:session_id/status
  • POST /api/sdk/sessions/:session_id/set
  • POST /api/sdk/sessions/:session_id/respond
  • POST /api/sdk/sessions/:session_id/fork
  • POST /api/sdk/sessions/:session_id/archive
  • GET / DELETE /api/sdk/archived-sessions
  • POST /api/plugins/action

Session Mutations

The Mutation values delivered by session.subscribe()

City RPC

City-owned RPC transport for Agents and Workspaces

Table of Contents

SDK HTTP Endpoints