Ingest up to 100 evaluation events in one batch. The @pecta/core SDK calls this endpoint automatically — most customers never need to call it directly.
Use this file to discover all available pages before exploring further.
POST /v1/ingest accepts batches of evaluation results produced by your gates and updates each agent’s rolling reputation window. The endpoint is designed for high-throughput, asynchronous delivery — Pecta queues each event for background processing and updates reputation scores before returning.
This endpoint is called automatically by PectaTelemetry in @pecta/core and by pecta-proxy. Most customers never need to call it directly. Use it when you are building a custom integration or shipping telemetry from a platform that cannot run the Node.js SDK.
If you have HMAC signing enabled, include the X-Pecta-Signature header with the HMAC-SHA256 digest of the raw request body:
X-Pecta-Signature: sha256=<hex-digest>
The digest is computed as HMAC-SHA256(rawBody, sk_live_key). When the header is present, Pecta verifies it before parsing the body. Omitting the header skips signature verification. See Authentication for details.
Per-gate results. Maximum 50 gates per event. Each element must include name (string, max 200), passed (boolean), latency_ms (number), and optionally reason (string, max 500) and skipped (boolean).