An agent sends the same input with sysone_select, or POST /v1/select over HTTP. The engine compiles it into exactly the request this page shows.
MCP tool call for the default example
{
"tool": "sysone_select",
"arguments": {
"task": "Need: A bag for a three-day work trip by train. I have client meetings, so it should look smart, and I carry a 16-inch laptop.\nCode already applied these exact filters: price at most $200, in stock, fits a 16-inch laptop.",
"options": [
{
"id": "commuter_pack",
"description": "Backpack, 20 liters. Slim everyday backpack with a water-resistant shell and a sporty look. Laptop sleeve fits up to 16 inches."
},
{
"id": "convertible_tote",
"description": "Tote, 24 liters. Tote that converts to a backpack. A smart finish that suits client meetings, with a cable organizer. Laptop sleeve fits up to 16 inches."
}
]
}
}HTTP and SDK
curl -sS "$SYSONE_URL/v1/select" \
-H "Authorization: Bearer $SYSONE_TOKEN" \
-H "Content-Type: application/json" \
--data @select.json
const response = await fetch(`${process.env.SYSONE_URL}/v1/select`, {
method: "POST",
headers: {
Authorization: `Bearer ${process.env.SYSONE_TOKEN}`,
"Content-Type": "application/json",
},
body: JSON.stringify(input), // select.json
});
const { result, answers, meta } = await response.json();
// result.choice, result.none and result.fits are model probabilities; no threshold is applied.Community projects inspired ideas here; this experiment is our own design and code.