post_v1_pubsub_jetstream_streams_stream_consumers_name_next
Fetch pulls the next batch from a consumer and acknowledges it — the request/response way to consume a stream.
Fetch pulls the next batch from a consumer and acknowledges it — the request/response way to consume a stream. The hand-off is at-most-once: a message returned here is acked here, so a caller that loses the response does not see it again. Workers needing at-least-once delivery consume the same consumer over the NATS port, where acks are theirs to send. An empty batch after the wait is an empty page, not an error.
| Tool | post_v1_pubsub_jetstream_streams_stream_consumers_name_next |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 4 |
| Operation | POST /v1/pubsub/jetstream/streams/{stream}/consumers/{name}/next |
| Product | pubsub |
Arguments
| Field | Type | Required | Default | Values | Description |
|---|---|---|---|---|---|
batch | integer | — | — | — | Batch is the most messages to return. 0 or less means 1; anything above 100 is clamped to 100. |
name | string | — | — | — | Name is the consumer, from the path. |
stream | string | — | — | — | Stream is the stream, from the path. |
waitMs | integer | — | — | — | WaitMs is how long to wait for the batch to fill before answering with what arrived. 0 or less means the default of 5000; clamped to 30000. |
tools/list declares a type and a description for each field and nothing further. A — means neither the door nor that operation constrains the field.
Call it
A tools/call carries every argument in one flat object — nothing binds to a path or a query string. Nothing above is required, so every declared argument is shown rather than a guess at which matter.
curl -X POST https://api.hanzo.ai/v1/mcp \
-H "Authorization: Bearer $HANZO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "post_v1_pubsub_jetstream_streams_stream_consumers_name_next",
"arguments": {
"batch": 0,
"name": "<name>",
"stream": "<stream>",
"waitMs": 0
}
}
}'Values are the operation's own defaults and enumerated values where it declares them, and a <placeholder> where neither source declares one. batch and waitMs hold stand-ins that cannot be spelled that way — JSON gives a number, a boolean and a timestamp no placeholder form — so those values are this page's, not the API's. Neither the door nor the operation declares one. tools/list needs no credential; tools/call does — called without one the door answers HTTP 200 with a JSON-RPC result whose isError is set and whose text says what was missing. How to get a key →
The operation behind it
| Operation | Route | Product | Summary |
|---|---|---|---|
post_v1_pubsub_jetstream_streams_stream_consumers_name_next | POST /v1/pubsub/jetstream/streams/{stream}/consumers/{name}/next | pubsub | Fetch pulls the next batch from a consumer and acknowledges it — the request/response way… |
The same capability over plain HTTP is in the pubsub API reference, on https://api.hanzo.ai.
All 755 tools · The door · API reference
Generated from tools/list on https://api.hanzo.ai/v1/mcp — 833 tools captured 2026-08-01, of which 755 are documented here (the operator surface is not published) (this build read the vendored copy; the door was unreachable).
How is this guide?