Request logs
Trace any request by its ID
Every response and error carries a request ID. Look it up to see which provider served it, what it cost and how it ended.
What each request shows
Request IDs
Every response and error carries one. Paste it into Activity to open that request.
Who served it
Each row shows the model you asked for and the provider that answered.
Shareable views
Filter by model, outcome and date, then send the link to a teammate.
Metadata only
Rows keep timing, tokens, charge and outcome. Hopscotch never stores prompts or responses by default.
When you need it
A user reports a broken answer
The request ID shows which provider served it and how it ended.
A charge that looks wrong
Look up the request to see its model, tokens and charge.
A run of failed requests
Filter by outcome to see which requests failed and when.
A security review
Activity shows exactly what Hopscotch keeps about each call.
Request log questions
Does the log store my prompts?
No. By default, Hopscotch never stores prompts or responses. Each row keeps metadata only.
How long are requests kept?
90 days. After that the row is deleted. Its charge stays on your billing statement.
Can I export the log?
Yes. Download up to 5,000 rows as CSV.
Are failed requests logged?
Yes. Failed and refused requests appear as ordinary rows, marked by their outcome. A request your limits refused shows a $0 charge.
Send one request and find it
Make a call, then open Activity. It's there with its model, cost and outcome.