Engage

Receive a batch of engagement events from the client.

Fire-and-forget: validation + rate-limit run synchronously, but the GCS write (append_batch) is queued as a BackgroundTask so the response returns immediately. Beacons don't need synchronous confirmation, and pushing the network I/O off the request path was a key fix after the 2026-06-10 saturation incident — synchronous GCS writes per beacon were compounding with MCP crawler load on a single 1-vCPU instance.

post/api/engage

Request

  • Base URL: https://owlgrouptrading.com (the document declares no server; this is the origin it was published from)
  • URL: https://owlgrouptrading.com/api/engage
  • Auth: none declared

Response

Successful Response

unknown required

Changes

No recorded changes to this operation across all 1 revision of this API.