Reference

Botfather's wire-level contract is documented alongside the protocol it implements. The HTTP ingest endpoints a SLAW instance calls are specified in the SLAW API reference; the end-to-end reporting flow and configuration live under Integrate.

Botfather Protocol API

The ingest endpoints — enrollment, heartbeat, sync, manifest, and skill-catalog — with request and response shapes.

Reporting Protocol

The four-endpoint flow an instance uses to report to the tower — enroll, heartbeat, sync, and manifest.

Identity & Keys

Machine IDs, per-instance API keys, Argon2 hashing, and revocation.

What Is and Isn't Synced

Exactly what data leaves an instance — metadata and metrics only.