Dry run for direct-mode payloads: validates a DirectPayload against a direct: true use case configuration and previews the internal entity and meter reading updates the pipeline would apply — without persisting anything.

Unlike the ingest endpoint, validation does not stop at the first problem: ALL issues across all operations are collected into errors, each carrying the index of the operation it refers to. When the payload is valid, the response additionally contains the translated update previews plus non-blocking warnings (for example unique-id fields that are not defined in the target entity schema, or a failed server-side unique-id type derivation).

Use this endpoint while designing a direct integration, before sending events to POST /v3/erp/updates/events. See documentation at /docs/DIRECT_MODE.md.