Documentation

Ports and endpoints exposed by VideoMemory for external agents/gateways. Use this as the integration reference for any agent platform, then see the OpenClaw section at the end.

General Agent Access (Container-to-Container)

Inside Docker Compose, an external agent can reach the VideoMemory service by name videomemory.

Destination Port/Proto Purpose Example
VideoMemory HTTP API 5050/tcp Core API for devices, tasks, and settings. http://videomemory:5050/api/health
OpenClaw Skill 5050/tcp Markdown skill file with curl-ready HTTP examples for OpenClaw. http://videomemory:5050/openclaw/skill.md
Direct camera input camera-defined VideoMemory pulls directly from the camera URL you register with /api/devices/network, including HTTP snapshot endpoints. http://phone:8080/snapshot.jpg

Host Exposed Ports

These are published to your local machine by compose.

Service Host Port Use URL
VideoMemory UI/API 5050 Core web UI and API. http://localhost:5050/
OpenClaw Skill 5050 Markdown skill endpoint for curl-based agent integration. http://localhost:5050/openclaw/skill.md
External Agent Gateway (optional) 18789 Port commonly used by an agent gateway in the bundled test stack. http://localhost:18789/

General Webhook Contract (VideoMemory -> Agent)

  • VideoMemory sends task updates to the configured webhook URL.
  • Typical payload includes task_id, io_id, task_description, and note.
  • If token auth is enabled, VideoMemory sends Authorization: Bearer <token>.
  • Configure values from Settings -> External Agent Integration.
  • Use the OpenClaw skill endpoint to see the recommended curl workflow while debugging agent communication.

OpenClaw-Specific Notes

  • In the bundled OpenClaw stack, VideoMemory sends alerts to http://openclaw:18789/hooks/videomemory-alert.
  • OpenClaw UI/Gateway is available on host port 18789 at http://localhost:18789/.
  • You can test the OpenClaw hook path from host via http://localhost:18789/hooks/videomemory-alert.
  • OpenClaw should fetch the skill from http://videomemory:5050/openclaw/skill.md and use the documented HTTP endpoints with curl.
  • If OpenClaw is running in a separate Docker container and VideoMemory is on the host, use http://host.docker.internal:5050/openclaw/skill.md instead.