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.
/accountReturns the current plan, feature availability, and accessible project count.
Authorization
bearerApiKey Create a REST API key in Settings > Connected Apps. MCP credentials do not authenticate this API.
In: header
Response Body
application/json
application/json
application/json
application/json
curl -X GET "https://example.com/account"{ "data": { "plan": "string", "is_paid": true, "project_count": 0, "features": { "property1": true, "property2": true } }}{ "message": "Unauthenticated."}{ "message": "string", "code": "string"}{ "message": "string", "code": "string"}/account/usageAuthorization
bearerApiKey Create a REST API key in Settings > Connected Apps. MCP credentials do not authenticate this API.
In: header
Response Body
application/json
application/json
application/json
application/json
curl -X GET "https://example.com/account/usage"{ "data": { "plan": "string", "features": { "property1": true, "property2": true }, "limits": { "property1": { "limit": 0, "used": 0, "remaining": 0 }, "property2": { "limit": 0, "used": 0, "remaining": 0 } } }}{ "message": "Unauthenticated."}{ "message": "string", "code": "string"}{ "message": "string", "code": "string"}