APIs and OpenAPI

Everything in the family speaks JSON over HTTP/1.1, and the services agents talk to describe themselves: point a client at the schema endpoint and it can bootstrap without docs. This page lists what serves what, where.

Self-describing services#

NullTickets is explicit about the intent: agents are expected to fetch the schema and figure out the API themselves. The server documents itself to its own users.

Endpoint summaries#

NullTickets (:7700)#

Pipelines (FSM definitions), tasks and bulk creation, cursor-paginated listing, lease claiming (POST /leases/claim), run events and artifacts, a namespaced KV store with FTS5 search, plus:

Run mutations require the Bearer lease token issued at claim time.

NullWatch (127.0.0.1:7710)#

NullBoiler (:8080)#

Runs, workflows, workers, checkpoints, streams and tracker endpoints — 30+ in total, per the OpenAPI 3.1 spec. Stream snapshots come in 5 modes (values, updates, tasks, debug, custom) with after_seq cursors; /metrics serves Prometheus. Creating a run:

curl -sS -X POST http://127.0.0.1:8080/runs \
  -H 'Content-Type: application/json' \
  -d '{"input": {...}, "steps": [...]}'

NullPantry (127.0.0.1:8765)#

Retrieval: /v1/search, /v1/ask, /v1/context-packs, /v1/vector/*. Agent memory, NullClaw-compatible: /v1/agent, /v1/memory, /v1/agent-memory, /v1/agent-sessions. All retrieval runs one shared path: ACL filter → keyword + vector candidates → graph expansion → fusion/rerank → citation-safe results.

NullHub (:19800)#

The dashboard's own API, reachable from the CLI without writing a client:

nullhub api GET /api/... --pretty

The hub also reverse-proxies its managed neighbors — /api/nullboiler/*, /api/nulltickets/store/*, /api/nullwatch/* — so browser UIs reach loopback-bound services through one origin. Managed NullClaw instances get instance-scoped admin routes (status, config, models, cron, channels, skills).

NullClaw gateway (127.0.0.1:3000)#

The gateway's HTTP API is documented in NullClaw's own gateway-api docs. Live log streaming from the hub side uses SSE.

Agent protocols#

Beyond plain REST, three protocols matter for interop:

NullBoiler additionally dispatches to workers over webhook, api_chat and openai_chat (any OpenAI-compatible gateway), plus async MQTT and Redis Streams.