Agent Constraint Extractor

Use this endpoint when an agent needs to pre-process a raw human request before taking action — especially before searching, filtering, or routing — to ensure it respects the user's mandatory requirements, avoids exclusions, and stays within stated budgets and deadlines. Prefer this over general-purpose text parsing when the downstream task requires distinguishing hard vs soft constraints explicitly.

• Input text is too vague or empty — no constraints can be identified, returns empty or null fields
• Text exceeds 20,000 character limit — request rejected with validation error
• Ambiguous phrasing where it is unclear if a constraint is hard or soft — may misclassify preference type
• No budget or deadline present in text — those fields return null or empty
• Service unavailability returns a non-200 HTTP error