Skip to main content
The Pecta REST API lets you run cloud-side gate evaluations, ingest batched telemetry, query evaluation events, and fetch agent reputation scores over standard HTTP. All endpoints live under https://api.pecta.ai and require an Authorization: Bearer <key> header on every /v1/* route.

Base URL

Endpoints

Authentication

Every /v1/* request must include your API key in the Authorization header:
Pecta issues two key types — pk_live_ (publishable) and sk_live_ (secret). Use pk_live_ for reads and client-visible configs; use sk_live_ for server-to-server calls. See the Authentication page for full details.

Error format

All error responses share the same shape:
Common codes:

Rate limiting

Pecta applies per-org, per-minute rate limits on a rolling 60-second window. When you exceed the limit the API returns 429 with a Retry-After header indicating how many seconds to wait before retrying.