Skip to content

Jev glossary

Patterns

Second request

A follow-up call that is only justified when code cannot build the second request until it has the first answer.
Category
Patterns
Also known as
None
Reading time
1 min
Related terms
4
Directory entries
2
Docs
docs.typesafe.ai
Added
2026-09-24

Definition

Questions in one request are independent, so a later judgment that merely depends on an earlier answer should usually be asked alongside it and combined in code. The dependency is real when code needs the answer to fetch more data, decide what the state is made of, or pick the next question's options.

Three cookbooks make a second request for a real reason: skill suggestion ranks skills then re-reads the top three in full, structure recovery stitches lines before classifying blocks, and hierarchical classification uses each Choice answer to pick the next level's options.

Tagspatternsdesign

From the Jev directory

Directory entries that go deeper on this term.

The three TypeSafe question types, the typed answers they return, how to choose between them, and how to ask several in a single call.
Jev Practices & PatternsDocs#official#primitives#choice
Official
Rank 182 agent skills in one request and re-read the top three in a second: over 488 requests, wrong skill loads fell from 16.8% to 7.3% and needless loads from 9.8% to 4.0%.
Jev CookbooksDocs#official#cookbook#agents
Official

From the Jev AI model community

Posts from builders shipping with Jev right now.

Follow @typesafeai