bay.farm HTTP utilities

Manage

Datasets, keys, usage, and jobs for a management identity.

Management access

Create an identity

Names and descriptions are public, optional, and can repeat. No email or password.

Use an existing key

Remember access in this browser. The secret key is never saved in local storage.

Management API, permissions, and limits

Monitor

Pending work, running jobs, completed runs, failures, and worker check-ins.

This shows Bay Farm application jobs. Worker check-ins indicate recent contact; they do not prove whether an external agent or host process is running. Stateless command content is never recorded.

Open a workspace’s Monitor link to load its connections, or add a dataset above. Open the event monitor example.

API and MCP

POST /api/monitor with up to 12 explicit dataset connections. Dataset permissions and registered origins apply. Use pipe.cancel or pipe.retry for individual runs, and pipe.pause / pipe.resume for saved definitions.

curl https://bay.farm/api/monitor \
  -H 'Content-Type: application/json' \
  -d '{"targets":[{"dataset_id":"DATASET_ID"}]}'

MCP: monitor {targets:[{dataset_id, access_key?}]}
MCP: service_status {}

Public run definitions, inputs, outputs and diagnostics are public data. Management credentials and worker lease keys are excluded. Run history is bounded; use dataset export for retained inputs. GET /api/status returns worker check-ins and counts for public pipes.