RTBResponse carries no metadata
Without api_version and model_version, an orchestrator cannot record which agent build produced these mutations.
What it means
The response has no metadata object. ARTF defines it to carry the data provider API version and, where a model computed the mutation, the model version.
Why it matters
Mutations change what an auction pays and who wins it. When a curation model starts behaving badly, the version stamp is what lets an orchestrator say which build did it and from when, and reconstructing that after the fact from deployment logs is guesswork.
How to fix it
Populate metadata on every response, including responses that propose nothing.
Example that trips it
{ "id": "ep-1", "mutations": [{ "intent": "ACTIVATE_DEALS", "op": "OPERATION_ADD", "path": "/imp/imp-1", "ids": { "id": ["deal-2"] } }] }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.