Input JSON HTTP

2 VersionsInput

Exposes a typed JSON ingress over HTTP POST or WebSocket, decoding each payload against the type the downstream port demands and emitting it as a t value. Use it for structured JSON ingest rather than raw-byte ingress.

How it fits

Typical backends

Push-driven prompt ingest — feed external JSON into a local model and report the reply.

Caveats

I/O contractThe output carries the generic backend type, so the type wired to the downstream port is what drives decoding; a payload that does not conform to that attached type fails the call with a type error.
Hard constraintWebSocket binary frames are only accepted when the resolved output is a byte type; every other output type requires text or JSON frames. transport fixes the channel and max_message_bytes rejects oversized payloads before decoding, both bound at startup.
LatencyTurning drop_messages off makes the response wait until the message has landed downstream, so a slow consumer slows every request.
State lifetimedrop_messages is the only hot-swappable knob; transport and max_message_bytes bind once at startup.

Versions

2f8d2b70default
Automated release
7/15/2026