Account
Read the authenticated Screpy account, plan usage, feature allowances, and accessible project limits with the REST API.
Start with account context
Call these endpoints before an automation that depends on plan access or available capacity. The response identifies the authenticated account and exposes the current feature allowances, usage, and accessible project limit. See authentication for the required bearer key.
Do not treat plan or allowance data as permanent configuration. Read it again when a workflow starts a crawl or needs to decide whether an optional feature is available, then use projects to select the correct project. See errors and limits before implementing retries or pagination.
Endpoints
Choose the endpoint that matches the smallest unit of data or action your integration needs. Each endpoint page documents one request so the reference remains fast and focused.