Register the remote Docker Hub registry as a replication endpoint by POSTing to /api/v2.0/registries with type: docker-hub, url: https://hub.docker.com, and credentials
Confirm the endpoint connectivity using POST /api/v2.0/registries/ping with the endpoint ID
Create the replication policy by POSTing to /api/v2.0/replication/policies with a body specifying src_registry (or dest_registry for push mode), filters for repository name and tag, trigger type (manual, event_based, or cron), and dest_namespace
Set the trigger to a cron schedule by providing trigger.trigger_settings.cron in standard cron format (e.g., '0 2 * * *' for 2 AM daily) when trigger.type is scheduled
Execute an immediate manual replication run via POST /api/v2.0/replication/executions with the policy_id, then monitor the run status at GET /api/v2.0/replication/executions/<id>
Known gotchas
Push and pull mode are configured via the dest_registry vs src_registry field in the policy body; swapping them reverses the replication direction and is a common authoring mistake
Namespace flattening is controlled by the dest_namespace field and the flatten_levels integer (0 = no flattening, -1 = flatten all levels); incorrect settings can create unexpected repository paths at the destination
Docker Hub rate limits apply to the Harbor adapter pulling from Docker Hub during push-mode replication; configure Docker Hub credentials in the registry endpoint to avoid anonymous pull limits
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp