Skip to main content
Remote sync batches local ledger entries and uploads them to the platform ingest endpoint:

Install

Parameters

Authentication

The SDK sends:
The platform ingest route accepts:
  • JWT tokens (user sessions)
  • API keys (recommended for agents). Use a per-agent key so the platform can bind every entry to one agent.
Since 0.4.0 every SDK call to the platform (sync, policy sync, kill switch, approvals, MCP, budget reservations) uses Authorization: Bearer. The older ApiKey <key> scheme is no longer sent.

Identity headers

Alongside the key, the SDK sends the identity of the caller as headers so the platform can attribute actions without trusting values in the request body: Headers whose value is unset are omitted. Set harness and principal on configure():
These values show up as the actor on each ledger row.

Operational behavior

  • Uploads are retried with exponential backoff (network/server errors).
  • Auth failures (401) are not retried.
  • If the platform is down, entries remain local and your agent continues.
  • If the batch references an agent, run or mission with an active kill switch, the platform rejects it with 423 Locked and records a HARD_BLOCK intervention.