No applicable_intents on the envelope
The agent is not told which intents it may return, and the orchestrator has no declared basis for rejecting the ones it gets.
What it means
The envelope carries no applicable_intents list. That field is how the orchestrator states which mutations it is prepared to evaluate on this call.
Why it matters
The framework's evaluation model rests on declared intent: an agent proposes, the orchestrator accepts or rejects, and each side knows the vocabulary in advance. Without the list the agent guesses at what is welcome, and rejections read as arbitrary.
How to fix it
Send the intents this extension point actually honours. An agent that receives them can skip work it knows will be discarded, which is the point of an in-auction budget.
Example that trips it
{ "id": "ep-1", "tmax": 120, "lifecycle": "LIFECYCLE_PUBLISHER_BID_REQUEST", "bid_request": { "id": "a-1" } }Check your payload
Paste a bid request or response into the tester to see whether this code fires against it, or gate on the id in CI with the CLI: the id is stable, wording is not.
Back to the full diagnostic code reference.