Dataset Viewer
Auto-converted to Parquet Duplicate
id
stringlengths
11
30
provider
stringclasses
5 values
question
stringlengths
27
153
expected
stringlengths
37
110
request_url
stringlengths
55
155
request_method
stringclasses
2 values
tool_calls
stringlengths
103
427
difficulty
stringclasses
3 values
guarded_by
stringclasses
6 values
pin_host
stringclasses
5 values
gh-pull-number
github
Which pull request number in olympus-labs/parthenon carried the fix for the dropped-events incident?
{"path":"number","match":"equals","value":53}
https://gh-2026-03-g12.snap.sandboxapis.dev/repos/olympus-labs/parthenon/pulls/53
GET
[{"method":"GET","url":"https://gh-2026-03-g12.snap.sandboxapis.dev/repos/olympus-labs/parthenon/pulls/53","body":null}]
read
packages/conformance/src/parity/pinned-cross-category.test.ts#closed_by_pull resolves to the closing PR on the GITHUB host, via the tracker's branchName
gh-2026-03-g12.snap.sandboxapis.dev
gh-pull-title
github
What is the title of pull request 53 in olympus-labs/parthenon?
{"path":"title","match":"equals","value":"Fix the backfill job OOMing"}
https://gh-2026-03-g12.snap.sandboxapis.dev/repos/olympus-labs/parthenon/pulls/53
GET
[{"method":"GET","url":"https://gh-2026-03-g12.snap.sandboxapis.dev/repos/olympus-labs/parthenon/pulls/53","body":null}]
read
apps/web/src/lib/tutorials.test.ts#the scripts still print what the pages say they print
gh-2026-03-g12.snap.sandboxapis.dev
gh-pull-merged
github
Did pull request 53 in olympus-labs/parthenon merge, or was it closed without merging?
{"path":"merged","match":"equals","value":true}
https://gh-2026-03-g12.snap.sandboxapis.dev/repos/olympus-labs/parthenon/pulls/53
GET
[{"method":"GET","url":"https://gh-2026-03-g12.snap.sandboxapis.dev/repos/olympus-labs/parthenon/pulls/53","body":null}]
read
packages/conformance/src/parity/pinned-cross-category.test.ts#closed_by_pull resolves to the closing PR on the GITHUB host, via the tracker's branchName
gh-2026-03-g12.snap.sandboxapis.dev
gh-pull-author
github
Who opened pull request 53 in olympus-labs/parthenon?
{"path":"user.login","match":"equals","value":"tiresias"}
https://gh-2026-03-g12.snap.sandboxapis.dev/repos/olympus-labs/parthenon/pulls/53
GET
[{"method":"GET","url":"https://gh-2026-03-g12.snap.sandboxapis.dev/repos/olympus-labs/parthenon/pulls/53","body":null}]
read
apps/web/src/lib/tutorials.test.ts#the scripts still print what the pages say they print
gh-2026-03-g12.snap.sandboxapis.dev
gh-pull-head-ref
github
Which branch did pull request 53 in olympus-labs/parthenon merge from?
{"path":"head.ref","match":"equals","value":"hotfix/backfill-job-ooming"}
https://gh-2026-03-g12.snap.sandboxapis.dev/repos/olympus-labs/parthenon/pulls/53
GET
[{"method":"GET","url":"https://gh-2026-03-g12.snap.sandboxapis.dev/repos/olympus-labs/parthenon/pulls/53","body":null}]
read
packages/conformance/src/parity/pinned-cross-category.test.ts#closed_by_pull resolves to the closing PR on the GITHUB host, via the tracker's branchName
gh-2026-03-g12.snap.sandboxapis.dev
gh-pull-head-sha
github
What is the head commit SHA of pull request 53 in olympus-labs/parthenon?
{"path":"head.sha","match":"equals","value":"94dd1fdf3b96e96c242a869801e448edeca9fd85"}
https://gh-2026-03-g12.snap.sandboxapis.dev/repos/olympus-labs/parthenon/pulls/53
GET
[{"method":"GET","url":"https://gh-2026-03-g12.snap.sandboxapis.dev/repos/olympus-labs/parthenon/pulls/53","body":null}]
read
packages/conformance/src/parity/pinned-cross-category.test.ts#closed_by_pull resolves to the closing PR on the GITHUB host, via the tracker's branchName
gh-2026-03-g12.snap.sandboxapis.dev
gh-review-state
github
What verdict did the review on pull request 53 in olympus-labs/parthenon leave?
{"path":"0.state","match":"equals","value":"APPROVED"}
https://gh-2026-03-g12.snap.sandboxapis.dev/repos/olympus-labs/parthenon/pulls/53/reviews
GET
[{"method":"GET","url":"https://gh-2026-03-g12.snap.sandboxapis.dev/repos/olympus-labs/parthenon/pulls/53/reviews","body":null}]
read
apps/web/src/lib/tutorials.test.ts#the scripts still print what the pages say they print
gh-2026-03-g12.snap.sandboxapis.dev
gh-review-count
github
How many reviews were submitted on pull request 53 in olympus-labs/parthenon?
{"path":"","match":"count","value":1}
https://gh-2026-03-g12.snap.sandboxapis.dev/repos/olympus-labs/parthenon/pulls/53/reviews
GET
[{"method":"GET","url":"https://gh-2026-03-g12.snap.sandboxapis.dev/repos/olympus-labs/parthenon/pulls/53/reviews","body":null}]
reason
apps/web/src/lib/tutorials.test.ts#the scripts still print what the pages say they print
gh-2026-03-g12.snap.sandboxapis.dev
gh-independent-approval
github
Pull request 53 in olympus-labs/parthenon was approved. Who signed it off, and was that somebody other than its author?
{"path":"0.user.login","match":"equals","value":"athena"}
https://gh-2026-03-g12.snap.sandboxapis.dev/repos/olympus-labs/parthenon/pulls/53/reviews
GET
[{"method":"GET","url":"https://gh-2026-03-g12.snap.sandboxapis.dev/repos/olympus-labs/parthenon/pulls/53","body":null},{"method":"GET","url":"https://gh-2026-03-g12.snap.sandboxapis.dev/repos/olympus-labs/parthenon/pulls/53/reviews","body":null}]
join
apps/web/src/lib/tutorials.test.ts#the scripts still print what the pages say they print
gh-2026-03-g12.snap.sandboxapis.dev
gh-merged-inside-window
github
FATE-51 was resolved at 2026-06-19T16:21:17Z. When did the pull request that fixed it merge, and was that before the tracker closed the issue?
{"path":"merged_at","match":"equals","value":"2026-06-19T16:11:17Z"}
https://gh-2026-03-g12.snap.sandboxapis.dev/repos/olympus-labs/parthenon/pulls/53
GET
[{"method":"GET","url":"https://jira-v3-g12.snap.sandboxapis.dev/rest/api/3/issue/FATE-51?fields=summary,status,issuetype,assignee,created,resolutiondate,customfield_10016,project","body":null},{"method":"GET","url":"https://gh-2026-03-g12.snap.sandboxapis.dev/repos/olympus-labs/parthenon/pulls/53","body":null}]
reason
packages/conformance/src/parity/pinned-cross-category.test.ts#the instants line up END TO END
gh-2026-03-g12.snap.sandboxapis.dev
gh-branch-exists
github
Is hotfix/backfill-job-ooming a real branch in olympus-labs/parthenon, or only a string on the pull request?
{"path":"name","match":"equals","value":"hotfix/backfill-job-ooming"}
https://gh-2026-03-g12.snap.sandboxapis.dev/repos/olympus-labs/parthenon/branches/hotfix/backfill-job-ooming
GET
[{"method":"GET","url":"https://gh-2026-03-g12.snap.sandboxapis.dev/repos/olympus-labs/parthenon/branches/hotfix/backfill-job-ooming","body":null}]
read
packages/conformance/src/parity/pinned-cross-category.test.ts#closed_by_pull resolves to the closing PR on the GITHUB host, via the tracker's branchName
gh-2026-03-g12.snap.sandboxapis.dev
gh-branch-sha-matches-pull
github
Does the branch named on pull request 53 point at the same commit the pull request calls its head?
{"path":"commit.sha","match":"equals","value":"94dd1fdf3b96e96c242a869801e448edeca9fd85"}
https://gh-2026-03-g12.snap.sandboxapis.dev/repos/olympus-labs/parthenon/branches/hotfix/backfill-job-ooming
GET
[{"method":"GET","url":"https://gh-2026-03-g12.snap.sandboxapis.dev/repos/olympus-labs/parthenon/pulls/53","body":null},{"method":"GET","url":"https://gh-2026-03-g12.snap.sandboxapis.dev/repos/olympus-labs/parthenon/branches/hotfix/backfill-job-ooming","body":null}]
join
packages/conformance/src/parity/pinned-cross-category.test.ts#closed_by_pull resolves to the closing PR on the GITHUB host, via the tracker's branchName
gh-2026-03-g12.snap.sandboxapis.dev
jira-issue-key
jira
Which Jira issue key tracks the incident where events were dropped during a rebalance?
{"path":"key","match":"equals","value":"FATE-51"}
https://jira-v3-g12.snap.sandboxapis.dev/rest/api/3/issue/FATE-51?fields=summary,status,issuetype,assignee,created,resolutiondate,customfield_10016,project
GET
[{"method":"GET","url":"https://jira-v3-g12.snap.sandboxapis.dev/rest/api/3/issue/FATE-51?fields=summary,status,issuetype,assignee,created,resolutiondate,customfield_10016,project","body":null}]
read
packages/conformance/src/parity/pinned-cross-category.test.ts#the issue is the SAME entity on the JIRA host (key) and the LINEAR host (identifier)
jira-v3-g12.snap.sandboxapis.dev
jira-summary
jira
What summary does the Jira host give FATE-51?
{"path":"fields.summary","match":"equals","value":"Postmortem follow-up: events dropped during a rebalance"}
https://jira-v3-g12.snap.sandboxapis.dev/rest/api/3/issue/FATE-51?fields=summary,status,issuetype,assignee,created,resolutiondate,customfield_10016,project
GET
[{"method":"GET","url":"https://jira-v3-g12.snap.sandboxapis.dev/rest/api/3/issue/FATE-51?fields=summary,status,issuetype,assignee,created,resolutiondate,customfield_10016,project","body":null}]
read
packages/conformance/src/parity/pinned-cross-category.test.ts#the issue is the SAME entity on the JIRA host (key) and the LINEAR host (identifier)
jira-v3-g12.snap.sandboxapis.dev
jira-status
jira
What status does the Jira host report for FATE-51?
{"path":"fields.status.name","match":"equals","value":"Done"}
https://jira-v3-g12.snap.sandboxapis.dev/rest/api/3/issue/FATE-51?fields=summary,status,issuetype,assignee,created,resolutiondate,customfield_10016,project
GET
[{"method":"GET","url":"https://jira-v3-g12.snap.sandboxapis.dev/rest/api/3/issue/FATE-51?fields=summary,status,issuetype,assignee,created,resolutiondate,customfield_10016,project","body":null}]
read
packages/conformance/src/parity/pinned-cross-category.test.ts#the issue is the SAME entity on the JIRA host (key) and the LINEAR host (identifier)
jira-v3-g12.snap.sandboxapis.dev
jira-issue-type
jira
What issue type is FATE-51 filed as?
{"path":"fields.issuetype.name","match":"equals","value":"Incident"}
https://jira-v3-g12.snap.sandboxapis.dev/rest/api/3/issue/FATE-51?fields=summary,status,issuetype,assignee,created,resolutiondate,customfield_10016,project
GET
[{"method":"GET","url":"https://jira-v3-g12.snap.sandboxapis.dev/rest/api/3/issue/FATE-51?fields=summary,status,issuetype,assignee,created,resolutiondate,customfield_10016,project","body":null}]
read
apps/web/src/lib/tutorials.test.ts#the scripts still print what the pages say they print
jira-v3-g12.snap.sandboxapis.dev
jira-assignee
jira
Who is FATE-51 assigned to?
{"path":"fields.assignee.displayName","match":"equals","value":"Tiresias"}
https://jira-v3-g12.snap.sandboxapis.dev/rest/api/3/issue/FATE-51?fields=summary,status,issuetype,assignee,created,resolutiondate,customfield_10016,project
GET
[{"method":"GET","url":"https://jira-v3-g12.snap.sandboxapis.dev/rest/api/3/issue/FATE-51?fields=summary,status,issuetype,assignee,created,resolutiondate,customfield_10016,project","body":null}]
read
apps/web/src/lib/tutorials.test.ts#the scripts still print what the pages say they print
jira-v3-g12.snap.sandboxapis.dev
jira-estimate
jira
What story point estimate does FATE-51 carry?
{"path":"fields.customfield_10016","match":"equals","value":3}
https://jira-v3-g12.snap.sandboxapis.dev/rest/api/3/issue/FATE-51?fields=summary,status,issuetype,assignee,created,resolutiondate,customfield_10016,project
GET
[{"method":"GET","url":"https://jira-v3-g12.snap.sandboxapis.dev/rest/api/3/issue/FATE-51?fields=summary,status,issuetype,assignee,created,resolutiondate,customfield_10016,project","body":null}]
read
packages/conformance/src/parity/pinned-cross-category.test.ts#the issue is the SAME entity on the JIRA host (key) and the LINEAR host (identifier)
jira-v3-g12.snap.sandboxapis.dev
jira-created
jira
When was the incident issue FATE-51 filed?
{"path":"fields.created","match":"equals","value":"2026-06-17T19:51:17.000+0000"}
https://jira-v3-g12.snap.sandboxapis.dev/rest/api/3/issue/FATE-51?fields=summary,status,issuetype,assignee,created,resolutiondate,customfield_10016,project
GET
[{"method":"GET","url":"https://jira-v3-g12.snap.sandboxapis.dev/rest/api/3/issue/FATE-51?fields=summary,status,issuetype,assignee,created,resolutiondate,customfield_10016,project","body":null}]
read
apps/web/src/lib/tutorials.test.ts#the scripts still print what the pages say they print
jira-v3-g12.snap.sandboxapis.dev
jira-resolved
jira
When was the incident issue FATE-51 resolved?
{"path":"fields.resolutiondate","match":"equals","value":"2026-06-19T16:21:17.000+0000"}
https://jira-v3-g12.snap.sandboxapis.dev/rest/api/3/issue/FATE-51?fields=summary,status,issuetype,assignee,created,resolutiondate,customfield_10016,project
GET
[{"method":"GET","url":"https://jira-v3-g12.snap.sandboxapis.dev/rest/api/3/issue/FATE-51?fields=summary,status,issuetype,assignee,created,resolutiondate,customfield_10016,project","body":null}]
read
apps/web/src/lib/tutorials.test.ts#the scripts still print what the pages say they print
jira-v3-g12.snap.sandboxapis.dev
jira-beat-the-target
jira
FATE-51 was filed at 2026-06-17T19:51:17Z and the team's target is to close an incident within 72 hours. When did it resolve, and did it beat the target?
{"path":"fields.resolutiondate","match":"equals","value":"2026-06-19T16:21:17.000+0000"}
https://jira-v3-g12.snap.sandboxapis.dev/rest/api/3/issue/FATE-51?fields=summary,status,issuetype,assignee,created,resolutiondate,customfield_10016,project
GET
[{"method":"GET","url":"https://jira-v3-g12.snap.sandboxapis.dev/rest/api/3/issue/FATE-51?fields=summary,status,issuetype,assignee,created,resolutiondate,customfield_10016,project","body":null}]
reason
apps/web/src/lib/tutorials.test.ts#the scripts still print what the pages say they print
jira-v3-g12.snap.sandboxapis.dev
jira-project-key
jira
Which Jira project does FATE-51 belong to?
{"path":"fields.project.key","match":"equals","value":"FATE"}
https://jira-v3-g12.snap.sandboxapis.dev/rest/api/3/issue/FATE-51?fields=summary,status,issuetype,assignee,created,resolutiondate,customfield_10016,project
GET
[{"method":"GET","url":"https://jira-v3-g12.snap.sandboxapis.dev/rest/api/3/issue/FATE-51?fields=summary,status,issuetype,assignee,created,resolutiondate,customfield_10016,project","body":null}]
read
apps/web/src/lib/tutorials.test.ts#the scripts still print what the pages say they print
jira-v3-g12.snap.sandboxapis.dev
jira-project-name
jira
What is the name of the Jira project whose key is FATE?
{"path":"name","match":"equals","value":"Fates"}
https://jira-v3-g12.snap.sandboxapis.dev/rest/api/3/project/FATE
GET
[{"method":"GET","url":"https://jira-v3-g12.snap.sandboxapis.dev/rest/api/3/project/FATE","body":null}]
read
apps/web/src/lib/tutorials.test.ts#the scripts still print what the pages say they print
jira-v3-g12.snap.sandboxapis.dev
slack-incident-channel-name
slack
Which channel in the olympus-labs workspace is the incident bridge?
{"path":"channels.0.name","match":"equals","value":"incident-bridge"}
https://slack-2026-08-g12.snap.sandboxapis.dev/api/conversations.list?limit=999
GET
[{"method":"GET","url":"https://slack-2026-08-g12.snap.sandboxapis.dev/api/conversations.list?limit=999","body":null}]
read
packages/conformance/src/parity/pinned-cross-category.test.ts#the incident thread is on the SLACK host: the channel, the opener, the burst
slack-2026-08-g12.snap.sandboxapis.dev
slack-incident-channel-id
slack
What is the channel id of #incident-bridge?
{"path":"channels.0.id","match":"equals","value":"CF1UPUMGC8Q"}
https://slack-2026-08-g12.snap.sandboxapis.dev/api/conversations.list?limit=999
GET
[{"method":"GET","url":"https://slack-2026-08-g12.snap.sandboxapis.dev/api/conversations.list?limit=999","body":null}]
read
packages/conformance/src/parity/pinned-cross-category.test.ts#the incident thread is on the SLACK host: the channel, the opener, the burst
slack-2026-08-g12.snap.sandboxapis.dev
slack-opener-text
slack
What did the message that opened the incident thread in #incident-bridge say?
{"path":"messages.0.text","match":"contains","value":"events dropped during a rebalance"}
https://slack-2026-08-g12.snap.sandboxapis.dev/api/conversations.history?channel=CF1UPUMGC8Q&limit=1
GET
[{"method":"GET","url":"https://slack-2026-08-g12.snap.sandboxapis.dev/api/conversations.history?channel=CF1UPUMGC8Q&limit=1","body":null}]
read
packages/conformance/src/parity/pinned-cross-category.test.ts#the incident thread is on the SLACK host: the channel, the opener, the burst
slack-2026-08-g12.snap.sandboxapis.dev
slack-opener-ts
slack
What is the Slack timestamp of the message that opened the incident thread?
{"path":"messages.0.ts","match":"equals","value":"1781726237.230977"}
https://slack-2026-08-g12.snap.sandboxapis.dev/api/conversations.history?channel=CF1UPUMGC8Q&limit=1
GET
[{"method":"GET","url":"https://slack-2026-08-g12.snap.sandboxapis.dev/api/conversations.history?channel=CF1UPUMGC8Q&limit=1","body":null}]
read
packages/conformance/src/parity/pinned-cross-category.test.ts#the incident thread is on the SLACK host: the channel, the opener, the burst
slack-2026-08-g12.snap.sandboxapis.dev
slack-reply-count
slack
How many replies does the incident thread in #incident-bridge carry?
{"path":"messages.0.reply_count","match":"equals","value":11}
https://slack-2026-08-g12.snap.sandboxapis.dev/api/conversations.history?channel=CF1UPUMGC8Q&limit=1
GET
[{"method":"GET","url":"https://slack-2026-08-g12.snap.sandboxapis.dev/api/conversations.history?channel=CF1UPUMGC8Q&limit=1","body":null}]
read
packages/conformance/src/parity/pinned-cross-category.test.ts#the incident thread is on the SLACK host: the channel, the opener, the burst
slack-2026-08-g12.snap.sandboxapis.dev
slack-opener-user-id
slack
Which user id posted the message that opened the incident thread?
{"path":"messages.0.user","match":"equals","value":"U127GRU2DLG"}
https://slack-2026-08-g12.snap.sandboxapis.dev/api/conversations.history?channel=CF1UPUMGC8Q&limit=1
GET
[{"method":"GET","url":"https://slack-2026-08-g12.snap.sandboxapis.dev/api/conversations.history?channel=CF1UPUMGC8Q&limit=1","body":null}]
read
apps/web/src/lib/tutorials.test.ts#the scripts still print what the pages say they print
slack-2026-08-g12.snap.sandboxapis.dev
slack-distinct-speakers
slack
How many different people spoke in the incident thread in #incident-bridge?
{"path":"messages.0.reply_users_count","match":"equals","value":6}
https://slack-2026-08-g12.snap.sandboxapis.dev/api/conversations.history?channel=CF1UPUMGC8Q&limit=1
GET
[{"method":"GET","url":"https://slack-2026-08-g12.snap.sandboxapis.dev/api/conversations.history?channel=CF1UPUMGC8Q&limit=1","body":null}]
reason
apps/web/src/lib/tutorials.test.ts#the scripts still print what the pages say they print
slack-2026-08-g12.snap.sandboxapis.dev
slack-thread-length
slack
Counting the message that opened it, how many messages are in the incident thread?
{"path":"messages","match":"count","value":12}
https://slack-2026-08-g12.snap.sandboxapis.dev/api/conversations.replies?channel=CF1UPUMGC8Q&ts=1781726237.230977&limit=999
GET
[{"method":"GET","url":"https://slack-2026-08-g12.snap.sandboxapis.dev/api/conversations.history?channel=CF1UPUMGC8Q&limit=1","body":null},{"method":"GET","url":"https://slack-2026-08-g12.snap.sandboxapis.dev/api/conversations.replies?channel=CF1UPUMGC8Q&ts=1781726237.230977&limit=999","body":null}]
reason
apps/web/src/lib/tutorials.test.ts#the scripts still print what the pages say they print
slack-2026-08-g12.snap.sandboxapis.dev
slack-parent-leads
slack
When the incident thread is fetched, which message comes first?
{"path":"messages.0.ts","match":"equals","value":"1781726237.230977"}
https://slack-2026-08-g12.snap.sandboxapis.dev/api/conversations.replies?channel=CF1UPUMGC8Q&ts=1781726237.230977&limit=999
GET
[{"method":"GET","url":"https://slack-2026-08-g12.snap.sandboxapis.dev/api/conversations.replies?channel=CF1UPUMGC8Q&ts=1781726237.230977&limit=999","body":null}]
read
packages/conformance/src/parity/pinned-cross-category.test.ts#the incident thread is on the SLACK host: the channel, the opener, the burst
slack-2026-08-g12.snap.sandboxapis.dev
slack-thread-runs-forward
slack
The incident thread must run forward in time, with nobody replying before it was opened. What is the timestamp of its last message?
{"path":"messages.11.ts","match":"equals","value":"1781884637.892883"}
https://slack-2026-08-g12.snap.sandboxapis.dev/api/conversations.replies?channel=CF1UPUMGC8Q&ts=1781726237.230977&limit=999
GET
[{"method":"GET","url":"https://slack-2026-08-g12.snap.sandboxapis.dev/api/conversations.replies?channel=CF1UPUMGC8Q&ts=1781726237.230977&limit=999","body":null}]
reason
packages/conformance/src/parity/pinned-cross-category.test.ts#the incident thread is on the SLACK host: the channel, the opener, the burst
slack-2026-08-g12.snap.sandboxapis.dev
slack-all-clear-text
slack
How was the incident thread in #incident-bridge closed out?
{"path":"messages.11.text","match":"contains","value":"all clear"}
https://slack-2026-08-g12.snap.sandboxapis.dev/api/conversations.replies?channel=CF1UPUMGC8Q&ts=1781726237.230977&limit=999
GET
[{"method":"GET","url":"https://slack-2026-08-g12.snap.sandboxapis.dev/api/conversations.replies?channel=CF1UPUMGC8Q&ts=1781726237.230977&limit=999","body":null}]
read
apps/web/src/lib/tutorials.test.ts#the scripts still print what the pages say they print
slack-2026-08-g12.snap.sandboxapis.dev
slack-all-clear-user-id
slack
Which user id posted the last message in the incident thread?
{"path":"messages.11.user","match":"equals","value":"U1PQUDI205V"}
https://slack-2026-08-g12.snap.sandboxapis.dev/api/conversations.replies?channel=CF1UPUMGC8Q&ts=1781726237.230977&limit=999
GET
[{"method":"GET","url":"https://slack-2026-08-g12.snap.sandboxapis.dev/api/conversations.replies?channel=CF1UPUMGC8Q&ts=1781726237.230977&limit=999","body":null}]
read
apps/web/src/lib/tutorials.test.ts#the scripts still print what the pages say they print
slack-2026-08-g12.snap.sandboxapis.dev
slack-opener-name
slack
Resolving the user id on the first message, who opened the incident thread in #incident-bridge?
{"path":"members.0.name","match":"equals","value":"cassandra"}
https://slack-2026-08-g12.snap.sandboxapis.dev/api/users.list?limit=200
GET
[{"method":"GET","url":"https://slack-2026-08-g12.snap.sandboxapis.dev/api/conversations.history?channel=CF1UPUMGC8Q&limit=1","body":null},{"method":"GET","url":"https://slack-2026-08-g12.snap.sandboxapis.dev/api/users.list?limit=200","body":null}]
join
apps/web/src/lib/tutorials.test.ts#the scripts still print what the pages say they print
slack-2026-08-g12.snap.sandboxapis.dev
slack-all-clear-name
slack
Resolving the user id on the last message, who called the all clear on the incident?
{"path":"members.1.name","match":"equals","value":"tiresias"}
https://slack-2026-08-g12.snap.sandboxapis.dev/api/users.list?limit=200
GET
[{"method":"GET","url":"https://slack-2026-08-g12.snap.sandboxapis.dev/api/conversations.replies?channel=CF1UPUMGC8Q&ts=1781726237.230977&limit=999","body":null},{"method":"GET","url":"https://slack-2026-08-g12.snap.sandboxapis.dev/api/users.list?limit=200","body":null}]
join
apps/web/src/lib/tutorials.test.ts#the scripts still print what the pages say they print
slack-2026-08-g12.snap.sandboxapis.dev
gl-merge-request-iid
gitlab
The fix merged from hotfix/backfill-job-ooming. Which merge request iid carries that branch in olympus-labs/parthenon on the GitLab host?
{"path":"0.iid","match":"equals","value":13}
https://gl-v4-g12.snap.sandboxapis.dev/api/v4/projects/olympus-labs%2Fparthenon/merge_requests?source_branch=hotfix/backfill-job-ooming
GET
[{"method":"GET","url":"https://gl-v4-g12.snap.sandboxapis.dev/api/v4/projects/olympus-labs%2Fparthenon/merge_requests?source_branch=hotfix/backfill-job-ooming","body":null}]
read
packages/conformance/src/parity/pinned-cross-category.test.ts#the head SHA is the SAME SHA on the GITLAB host (and that host serves the branch too)
gl-v4-g12.snap.sandboxapis.dev
gl-merge-request-source-branch
gitlab
What source branch does merge request 13 in olympus-labs/parthenon carry?
{"path":"0.source_branch","match":"equals","value":"hotfix/backfill-job-ooming"}
https://gl-v4-g12.snap.sandboxapis.dev/api/v4/projects/olympus-labs%2Fparthenon/merge_requests?source_branch=hotfix/backfill-job-ooming
GET
[{"method":"GET","url":"https://gl-v4-g12.snap.sandboxapis.dev/api/v4/projects/olympus-labs%2Fparthenon/merge_requests?source_branch=hotfix/backfill-job-ooming","body":null}]
read
packages/conformance/src/parity/pinned-cross-category.test.ts#the head SHA is the SAME SHA on the GITLAB host (and that host serves the branch too)
gl-v4-g12.snap.sandboxapis.dev
gl-merge-request-sha
gitlab
What head SHA does the GitLab host report for merge request 13 in olympus-labs/parthenon?
{"path":"0.sha","match":"equals","value":"94dd1fdf3b96e96c242a869801e448edeca9fd85"}
https://gl-v4-g12.snap.sandboxapis.dev/api/v4/projects/olympus-labs%2Fparthenon/merge_requests?source_branch=hotfix/backfill-job-ooming
GET
[{"method":"GET","url":"https://gl-v4-g12.snap.sandboxapis.dev/api/v4/projects/olympus-labs%2Fparthenon/merge_requests?source_branch=hotfix/backfill-job-ooming","body":null}]
read
packages/conformance/src/parity/pinned-cross-category.test.ts#the head SHA is the SAME SHA on the GITLAB host (and that host serves the branch too)
gl-v4-g12.snap.sandboxapis.dev
gl-branch-exists
gitlab
Does the GitLab host serve hotfix/backfill-job-ooming as a real branch of olympus-labs/parthenon?
{"path":"name","match":"equals","value":"hotfix/backfill-job-ooming"}
https://gl-v4-g12.snap.sandboxapis.dev/api/v4/projects/olympus-labs%2Fparthenon/repository/branches/hotfix/backfill-job-ooming
GET
[{"method":"GET","url":"https://gl-v4-g12.snap.sandboxapis.dev/api/v4/projects/olympus-labs%2Fparthenon/repository/branches/hotfix/backfill-job-ooming","body":null}]
read
packages/conformance/src/parity/pinned-cross-category.test.ts#the head SHA is the SAME SHA on the GITLAB host (and that host serves the branch too)
gl-v4-g12.snap.sandboxapis.dev
gl-branch-sha
gitlab
Which commit does hotfix/backfill-job-ooming point at on the GitLab host?
{"path":"commit.id","match":"equals","value":"94dd1fdf3b96e96c242a869801e448edeca9fd85"}
https://gl-v4-g12.snap.sandboxapis.dev/api/v4/projects/olympus-labs%2Fparthenon/repository/branches/hotfix/backfill-job-ooming
GET
[{"method":"GET","url":"https://gl-v4-g12.snap.sandboxapis.dev/api/v4/projects/olympus-labs%2Fparthenon/repository/branches/hotfix/backfill-job-ooming","body":null}]
read
packages/conformance/src/parity/pinned-cross-category.test.ts#the head SHA is the SAME SHA on the GITLAB host (and that host serves the branch too)
gl-v4-g12.snap.sandboxapis.dev
gl-sha-matches-github
gitlab
Two git hosts serve this repository. Do the GitHub pull request and the GitLab merge request for the same branch agree on the head SHA?
{"path":"0.sha","match":"equals","value":"94dd1fdf3b96e96c242a869801e448edeca9fd85"}
https://gl-v4-g12.snap.sandboxapis.dev/api/v4/projects/olympus-labs%2Fparthenon/merge_requests?source_branch=hotfix/backfill-job-ooming
GET
[{"method":"GET","url":"https://gh-2026-03-g12.snap.sandboxapis.dev/repos/olympus-labs/parthenon/pulls/53","body":null},{"method":"GET","url":"https://gl-v4-g12.snap.sandboxapis.dev/api/v4/projects/olympus-labs%2Fparthenon/merge_requests?source_branch=hotfix/backfill-job-ooming","body":null}]
join
packages/conformance/src/parity/pinned-cross-category.test.ts#the head SHA is the SAME SHA on the GITLAB host (and that host serves the branch too)
gl-v4-g12.snap.sandboxapis.dev
linear-identifier
linear
What identifier does the Linear host give the incident issue FATE-51?
{"path":"data.issue.identifier","match":"equals","value":"FATE-51"}
https://linear-2026-08-g12.snap.sandboxapis.dev/graphql
POST
[{"method":"POST","url":"https://linear-2026-08-g12.snap.sandboxapis.dev/graphql","body":"{\"query\":\"{ issue(id:\\\"FATE-51\\\") { identifier title estimate createdAt completedAt branchName state { name } team { key name } } }\"}"}]
read
packages/conformance/src/parity/pinned-cross-category.test.ts#the issue is the SAME entity on the JIRA host (key) and the LINEAR host (identifier)
linear-2026-08-g12.snap.sandboxapis.dev
linear-title
linear
What title does the Linear host give FATE-51?
{"path":"data.issue.title","match":"equals","value":"Postmortem follow-up: events dropped during a rebalance"}
https://linear-2026-08-g12.snap.sandboxapis.dev/graphql
POST
[{"method":"POST","url":"https://linear-2026-08-g12.snap.sandboxapis.dev/graphql","body":"{\"query\":\"{ issue(id:\\\"FATE-51\\\") { identifier title estimate createdAt completedAt branchName state { name } team { key name } } }\"}"}]
read
packages/conformance/src/parity/pinned-cross-category.test.ts#the issue is the SAME entity on the JIRA host (key) and the LINEAR host (identifier)
linear-2026-08-g12.snap.sandboxapis.dev
linear-estimate
linear
What estimate does the Linear host report for FATE-51?
{"path":"data.issue.estimate","match":"equals","value":3}
https://linear-2026-08-g12.snap.sandboxapis.dev/graphql
POST
[{"method":"POST","url":"https://linear-2026-08-g12.snap.sandboxapis.dev/graphql","body":"{\"query\":\"{ issue(id:\\\"FATE-51\\\") { identifier title estimate createdAt completedAt branchName state { name } team { key name } } }\"}"}]
read
packages/conformance/src/parity/pinned-cross-category.test.ts#the issue is the SAME entity on the JIRA host (key) and the LINEAR host (identifier)
linear-2026-08-g12.snap.sandboxapis.dev
linear-state
linear
What workflow state is FATE-51 in on the Linear host?
{"path":"data.issue.state.name","match":"equals","value":"Done"}
https://linear-2026-08-g12.snap.sandboxapis.dev/graphql
POST
[{"method":"POST","url":"https://linear-2026-08-g12.snap.sandboxapis.dev/graphql","body":"{\"query\":\"{ issue(id:\\\"FATE-51\\\") { identifier title estimate createdAt completedAt branchName state { name } team { key name } } }\"}"}]
read
packages/conformance/src/parity/pinned-cross-category.test.ts#the issue is the SAME entity on the JIRA host (key) and the LINEAR host (identifier)
linear-2026-08-g12.snap.sandboxapis.dev
linear-created
linear
When was FATE-51 created, according to the Linear host?
{"path":"data.issue.createdAt","match":"equals","value":"2026-06-17T19:51:17.000Z"}
https://linear-2026-08-g12.snap.sandboxapis.dev/graphql
POST
[{"method":"POST","url":"https://linear-2026-08-g12.snap.sandboxapis.dev/graphql","body":"{\"query\":\"{ issue(id:\\\"FATE-51\\\") { identifier title estimate createdAt completedAt branchName state { name } team { key name } } }\"}"}]
read
packages/conformance/src/parity/pinned-cross-category.test.ts#the issue is the SAME entity on the JIRA host (key) and the LINEAR host (identifier)
linear-2026-08-g12.snap.sandboxapis.dev
linear-completed
linear
When was FATE-51 completed, according to the Linear host?
{"path":"data.issue.completedAt","match":"equals","value":"2026-06-19T16:21:17.000Z"}
https://linear-2026-08-g12.snap.sandboxapis.dev/graphql
POST
[{"method":"POST","url":"https://linear-2026-08-g12.snap.sandboxapis.dev/graphql","body":"{\"query\":\"{ issue(id:\\\"FATE-51\\\") { identifier title estimate createdAt completedAt branchName state { name } team { key name } } }\"}"}]
read
packages/conformance/src/parity/pinned-cross-category.test.ts#the issue is the SAME entity on the JIRA host (key) and the LINEAR host (identifier)
linear-2026-08-g12.snap.sandboxapis.dev
linear-branch-name
linear
Which git branch does the Linear host say belongs to FATE-51?
{"path":"data.issue.branchName","match":"equals","value":"hotfix/backfill-job-ooming"}
https://linear-2026-08-g12.snap.sandboxapis.dev/graphql
POST
[{"method":"POST","url":"https://linear-2026-08-g12.snap.sandboxapis.dev/graphql","body":"{\"query\":\"{ issue(id:\\\"FATE-51\\\") { identifier title estimate createdAt completedAt branchName state { name } team { key name } } }\"}"}]
read
packages/conformance/src/parity/pinned-cross-category.test.ts#closed_by_pull resolves to the closing PR on the GITHUB host, via the tracker's branchName
linear-2026-08-g12.snap.sandboxapis.dev
linear-team-key
linear
Which team owns FATE-51 on the Linear host?
{"path":"data.issue.team.key","match":"equals","value":"FATE"}
https://linear-2026-08-g12.snap.sandboxapis.dev/graphql
POST
[{"method":"POST","url":"https://linear-2026-08-g12.snap.sandboxapis.dev/graphql","body":"{\"query\":\"{ issue(id:\\\"FATE-51\\\") { identifier title estimate createdAt completedAt branchName state { name } team { key name } } }\"}"}]
read
packages/conformance/src/parity/pinned-cross-category.test.ts#the issue is the SAME entity on the JIRA host (key) and the LINEAR host (identifier)
linear-2026-08-g12.snap.sandboxapis.dev
linear-title-matches-jira
linear
Two trackers hold this incident. Does the title the Linear host serves for FATE-51 match the summary the Jira host serves?
{"path":"data.issue.title","match":"equals","value":"Postmortem follow-up: events dropped during a rebalance"}
https://linear-2026-08-g12.snap.sandboxapis.dev/graphql
POST
[{"method":"GET","url":"https://jira-v3-g12.snap.sandboxapis.dev/rest/api/3/issue/FATE-51?fields=summary,status,issuetype,assignee,created,resolutiondate,customfield_10016,project","body":null},{"method":"POST","url":"https://linear-2026-08-g12.snap.sandboxapis.dev/graphql","body":"{\"query\":\"{ issue(id:\\\"FATE-51\\...
join
packages/conformance/src/parity/pinned-cross-category.test.ts#the issue is the SAME entity on the JIRA host (key) and the LINEAR host (identifier)
linear-2026-08-g12.snap.sandboxapis.dev
linear-close-matches-jira
linear
Jira resolved FATE-51 at 2026-06-19T16:21:17Z. Does the Linear host report the same close, to the second, in its own date dialect?
{"path":"data.issue.completedAt","match":"equals","value":"2026-06-19T16:21:17.000Z"}
https://linear-2026-08-g12.snap.sandboxapis.dev/graphql
POST
[{"method":"GET","url":"https://jira-v3-g12.snap.sandboxapis.dev/rest/api/3/issue/FATE-51?fields=summary,status,issuetype,assignee,created,resolutiondate,customfield_10016,project","body":null},{"method":"POST","url":"https://linear-2026-08-g12.snap.sandboxapis.dev/graphql","body":"{\"query\":\"{ issue(id:\\\"FATE-51\\...
join
packages/conformance/src/parity/pinned-cross-category.test.ts#the instants line up END TO END
linear-2026-08-g12.snap.sandboxapis.dev

olympus-labs answer-key evals

Repository id: sandboxapis/olympus-labs-evals.

Dataset Summary

53 questions an agent can answer by calling real API shapes: GitHub, GitLab, Jira, Linear and Slack. Each row carries the question, the request that answers it, and the value the answer must be. The requests go to SandboxAPIs pinned snapshot hosts, which are read-only replicas of those APIs preloaded with one simulated engineering company, olympus-labs. A pinned host returns the same bytes on every request, so a row's expected answer is as true next year as it is today.

All 53 rows follow one incident across the five services: the bug report in the tracker, the pull request that fixed it, its review, the branch it merged from, and the chat thread where it was called resolved. The identifiers agree from one service to the next, so some rows can only be answered by reading two responses and joining them.

This is version olympus-labs-g12-2026-09: generation g12 of the data set, compiled from template hello-20, artifact sha256 c27f762cc1d2656fca27e2a3ffc8c7742e41bca227cc7d36efc4cf0a8bf31d39.

from datasets import load_dataset
import json

rows = load_dataset("sandboxapis/olympus-labs-evals", split="train")
row = rows[0]
expected = json.loads(row["expected"])  # {"path": "number", "match": "equals", "value": 53}

Supported Tasks

  • Tool-using agent evaluation. Give the agent question and an HTTP tool (or the SandboxAPIs MCP server), let it choose its own calls, and score its final answer against expected. The tool_calls column is one correct route to the answer, not the only one.
  • Answer extraction from API responses. Fetch tool_calls yourself, hand the responses to the model with question, and score what it reads out of them. This isolates reading from planning.

Scoring is exact and needs no judge model. expected.match is one of:

match the answer is correct when
equals it equals expected.value (a string, an integer or a boolean)
count it is a list whose length is expected.value
contains it is a string that contains expected.value

expected.path is where the value sits in the response to request_url, as a dotted path in which numbers index arrays and "" is the whole document.

difficulty grades the row: read is one field off one response, join means two responses have to agree and the second call is only reachable once the first has been read, and reason means the answer is computed from what came back rather than copied out of it.

Two zero-dependency harnesses that score either the data set or your model, run.mjs and run.py, are in driftwork-llc/sandboxapis-examples.

Dataset Structure

Data Fields

field type what it holds
id string Stable row id, for example gh-pull-number. Never reused for a different question.
provider string github, gitlab, jira, linear or slack.
question string The question, in plain English, as an agent would be asked it.
expected string JSON: {"path", "match", "value"}, described above. A string because value changes type between rows.
request_url string The request whose response holds the answer.
request_method string GET, or POST for the Linear GraphQL rows.
tool_calls string JSON: every request the answer needs, in order, as {"method", "url", "body"}. body is the GraphQL document on Linear rows and null elsewhere.
difficulty string read, join or reason.
guarded_by string The test in the SandboxAPIs engine repository that fails if this answer changes. That repository is private; the citation shows that each answer is held by a test rather than typed from memory.
pin_host string The pinned snapshot host that request_url points at.

Example row

{
  "id": "gh-pull-number",
  "provider": "github",
  "question": "Which pull request number in olympus-labs/parthenon carried the fix for the dropped-events incident?",
  "expected": "{\"path\":\"number\",\"match\":\"equals\",\"value\":53}",
  "request_url": "https://gh-2026-03-g12.snap.sandboxapis.dev/repos/olympus-labs/parthenon/pulls/53",
  "request_method": "GET",
  "tool_calls": "[{\"method\":\"GET\",\"url\":\"https://gh-2026-03-g12.snap.sandboxapis.dev/repos/olympus-labs/parthenon/pulls/53\",\"body\":null}]",
  "difficulty": "read",
  "guarded_by": "packages/conformance/src/parity/pinned-cross-category.test.ts#closed_by_pull resolves to the closing PR on the GITHUB host, via the tracker's branchName",
  "pin_host": "gh-2026-03-g12.snap.sandboxapis.dev"
}

Data Splits

One split, train, with all 53 rows. There is no held-out split: every answer can be read from a public host, so a held-out split would not stay held out. Treat the set as an evaluation set and do not train on it.

provider rows pinned host
github 12 gh-2026-03-g12.snap.sandboxapis.dev
jira 11 jira-v3-g12.snap.sandboxapis.dev
slack 14 slack-2026-08-g12.snap.sandboxapis.dev
gitlab 6 gl-v4-g12.snap.sandboxapis.dev
linear 10 linear-2026-08-g12.snap.sandboxapis.dev

Dataset Creation

Source data

The data is generated, not recorded. A deterministic simulation runs a fictional company's engineers over 90 days of simulated time, and a compiler renders the result in each provider's API shape. Nothing in it came from a real account, a real repository or a real person.

There is one fictional company, olympus-labs, and its people and projects carry Greek-mythology names (athena, tiresias, parthenon) so that nobody mistakes a row for a real organisation's data.

Annotations

Each expected value was read off the pinned host and is held there by a test in the engine repository, named in guarded_by. A row nobody can cite does not go in the set.

Considerations for Using the Data

  • Read-only hosts. The pinned hosts accept reads only. A write returns the provider's own error status and body with a plain explanation, so an agent under test cannot change the answers for anyone else.
  • Rate limit. Anonymous callers get 60 requests an hour per IP. Scoring every row with the reference tool_calls takes 12 requests, because rows share responses. A free key from sandboxapis.dev/login raises the limit to 600 an hour; send it as Authorization: Bearer <key>.
  • Every answer is checkable live. Fetch request_url and read expected.path out of it. If the value differs, the row or the host is wrong, and we want to hear about it at sandboxapis.dev/feedback.
  • Pinned, not live. The -g12 hosts are frozen snapshots. SandboxAPIs also serves live hosts that roll forward daily; do not point this set at them, because their answers move.
  • Contamination. The rows and their answers are public. A model may have seen them, so report a score on this set alongside your own held-back tasks rather than instead of them.

Licensing Information

MIT. The hosted service and the engine that generates the data set are separate and are not covered by this licence.

Citation Information

@misc{sandboxapis_olympus_labs_evals_2026,
  author       = {{SandboxAPIs team, Driftwork LLC}},
  title        = {olympus-labs answer-key evals},
  year         = {2026},
  version      = {olympus-labs-g12-2026-09},
  publisher    = {Hugging Face},
  howpublished = {\url{https://huggingface.co/datasets/sandboxapis/olympus-labs-evals}}
}
Downloads last month
62