Intent is not among the request's applicable_intents
The mutation declares an intent the orchestrator did not offer on this call, so it is rejected on arrival.
What it means
The mutation's intent is valid but absent from the applicable_intents list the RTBRequest declared. That list is the orchestrator stating what it is prepared to evaluate.
Why it matters
The mutation is dead on arrival, and the work behind it was spent inside an auction's time budget. When it happens systematically it usually means the agent ignores the field entirely, which also means it will keep proposing intents an orchestrator has deliberately disabled.
How to fix it
Filter proposals against applicable_intents before returning them. If an intent you need is never offered, that is a conversation with the orchestrator rather than something to work around.
Example that trips it
{ "intent": "BID_SHADE", "op": "OPERATION_REPLACE", "path": "/seatbid/dsp-1/bid/bid-abc", "adjust_bid": { "price": 3.15 } }Sent against a request whose applicable_intents covered only deal and segment activation.
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.