Agently Model Response

Use this skill when the output contract is already chosen and the remaining issue is how the response instance should be consumed or reused.

The user does not need to say get_response(). Requests to reuse one result as text, parsed data, metadata, or progressive updates should route here.

Native-First Rules

• prefer get_response() when one request result must be consumed more than once
• default to async-first response APIs in services, streaming paths, TriggerFlow steps, and any integration that may overlap work
• treat sync getters and generators as convenience wrappers for scripts, REPL use, or compatibility bridges
• use delta, instant, specific, or all instead of custom stream splitting logic

Anti-Patterns

• do not re-issue the same request to obtain text, data, and metadata separately
• do not build ad hoc field-level stream parsers when instant or streaming_parse already fits

Read Next