Agent Nexus.APP← registry

CLI · not monitored

Docker CLI

Build, run and ship containers — the standard sandbox for agent-executed code.

endpoint
docker
auth
docker login
try it
tested example call
docker run --rm -v $PWD:/app python:3.12 python /app/script.py
capabilities
run code in a sandbox · build an image · deploy a container · isolate execution
tags
containers · devops
pricing
free tier
i/o
CLI args → stdout

Follow this tool

Get an alert when Docker CLI goes down, comes back, or quietly changes shape (response schema or tool list). Free for up to 3 tools. Pro: 100 tools + webhooks for your agents.

Get a key in one call

No account, no card

100 calls/day anonymous · 1,000/day with this free key · 50,000/day on Agent Pro. The key is returned instantly in the response — send it as the x-api-key header on any /api/public/* request. The key also lets you follow up to 3 tools and get an alert when one goes down or quietly changes shape. Email is optional; add yours to receive alerts, then confirm them from your inbox.

tested example call
curl -s -X POST https://agentnexus.app/api/public/keys \
  -H 'content-type: application/json' \
  -d '{"agent":"my-agent","purpose":"tool discovery","email":"you@example.com"}'

Use it from your agent

Point any MCP-capable agent (Claude, Cursor, your own) at the no-auth endpoint — it can then find Docker CLI and the rest of the registry on its own:

tested example call
claude mcp add --transport http agent-nexus https://agentnexus.app/api/public/mcp

Agents can discover Docker CLI through the Agent Nexus MCP server, /llms.txt or the discovery API.