The API explorer
This page is the fastest way to ask, "what does the explorer return for this exact combination of controls?" The left side is a raw JSON request, the right rail documents the accepted keys, and the response panel echoes the normalized state so you can see how subset labels, indices, and defaults were resolved.
Treat the explorer state like a request body, then inspect exactly what comes back.
This page is intentionally lower-level than the grid and graph views. Instead of clicking through controls, you can type the same state directly, see how it gets normalized, and grab the matrix, a selected cell, or the current headline answer.
Pick a request shape
Start from one of the example buttons if you want a fast template for grid matrices, grid cells, or graph answers.
Pass in the state you care about
Use the same core knobs as the existing explorers: count, metric, focus tokens, train/eval subsets, and the lens-specific controls.
Read the normalized response
The output echoes the resolved state first, so it is easy to confirm how labels, indices, defaults, and column filters were interpreted.
Send the grid or graph state through one shared request body.
Paste JSON, run it in-browser, and inspect the normalized response. The request can stay flat or tuck the explorer controls under a nested state object.
Request JSON
Subset references accept labels like ABC, arrays like ["A","B","C"], or numeric subset indices.
Normalized output
The response echoes the resolved state, then returns either the matrix, the selected cell, or the current headline answer.
// Run a request to see the response here.