Spend
The top of the page shows Credits spent in the selected range and Credits left, with a spend chart over time. Members see their own spend, including what their API keys spent. Team owners and organization admins see the team’s and each member’s, and organization admins and owners can switch to organization-wide spend.Logs
The logs table lists workflow runs, searches and API requests in one place.
Click a row to see its details. For API calls, they include the request, the response and the Request ID, which is the response’s
X-Correlation-ID header.
For organizations with customer-managed encryption, Sixtyfour does not store API request and response bodies or error messages. The details view and log exports leave them empty.
Members see their own workflow runs, including those their API keys started, and the searches they can open. Team owners and organization admins see every member’s runs. API request logs are visible to organization admins and owners.
Wherever a member sees a teammate’s run or search, such as a workflow’s run history or a search shared with the team, its cost shows as Hidden: only team owners and organization admins see what other members spent.
Export API logs
Organization admins and owners can export the active team’s API request logs. Click Export above the logs table.
The dialog previews the row count. Exports are capped at 10,000 rows; narrow the time range to export older logs in parts. Download the result as CSV or send it to Google Sheets.
Every export includes Request ID, Timestamp, Endpoint, Source, Status, Duration (ms), Cost (credits), HTTP Status, API Key and Error Message.