From b6f2ed32e57c698e6b60aeddcfbaa976f324da07 Mon Sep 17 00:00:00 2001
From: Mehmet Dogan <mehmet@dogan.io>
Date: Wed, 12 Aug 2026 19:57:37 +0300
Subject: [PATCH 01/12] Add Redis commands reference pages

---
 docs.json                                     |   391 +
 llms-full.txt                                 | 45801 +++++++++++++++-
 llms.txt                                      |   294 +-
 redis/commands/bitmap/bitcount.mdx            |   165 +
 redis/commands/bitmap/bitfield-ro.mdx         |   161 +
 redis/commands/bitmap/bitfield.mdx            |   165 +
 redis/commands/bitmap/bitop.mdx               |   176 +
 redis/commands/bitmap/bitpos.mdx              |   167 +
 redis/commands/bitmap/getbit.mdx              |   165 +
 redis/commands/bitmap/overview.mdx            |    16 +
 redis/commands/bitmap/setbit.mdx              |   166 +
 redis/commands/connection/auth.mdx            |   145 +
 redis/commands/connection/client-getname.mdx  |   143 +
 redis/commands/connection/client-id.mdx       |   143 +
 redis/commands/connection/client-info.mdx     |   143 +
 redis/commands/connection/client-list.mdx     |   143 +
 redis/commands/connection/client-setinfo.mdx  |   148 +
 redis/commands/connection/client-setname.mdx  |   146 +
 redis/commands/connection/echo.mdx            |   165 +
 redis/commands/connection/hello.mdx           |   146 +
 redis/commands/connection/overview.mdx        |    22 +
 redis/commands/connection/ping.mdx            |   170 +
 redis/commands/connection/quit.mdx            |   144 +
 redis/commands/connection/reset.mdx           |   142 +
 redis/commands/connection/select.mdx          |   160 +
 redis/commands/functions/fcall-ro.mdx         |   187 +
 redis/commands/functions/fcall.mdx            |   180 +
 redis/commands/functions/function-delete.mdx  |   161 +
 redis/commands/functions/function-flush.mdx   |   160 +
 redis/commands/functions/function-kill.mdx    |   158 +
 redis/commands/functions/function-list.mdx    |   178 +
 redis/commands/functions/function-load.mdx    |   182 +
 redis/commands/functions/function-stats.mdx   |   168 +
 redis/commands/functions/overview.mdx         |    17 +
 redis/commands/generic/copy.mdx               |   167 +
 redis/commands/generic/del.mdx                |   164 +
 redis/commands/generic/dump.mdx               |   156 +
 redis/commands/generic/exists.mdx             |   167 +
 redis/commands/generic/expire.mdx             |   173 +
 redis/commands/generic/expireat.mdx           |   174 +
 redis/commands/generic/expiretime.mdx         |   160 +
 redis/commands/generic/keys.mdx               |   169 +
 redis/commands/generic/memory-usage.mdx       |   165 +
 redis/commands/generic/overview.mdx           |    34 +
 redis/commands/generic/persist.mdx            |   164 +
 redis/commands/generic/pexpire.mdx            |   172 +
 redis/commands/generic/pexpireat.mdx          |   174 +
 redis/commands/generic/pexpiretime.mdx        |   160 +
 redis/commands/generic/pttl.mdx               |   168 +
 redis/commands/generic/randomkey.mdx          |   162 +
 redis/commands/generic/rename.mdx             |   165 +
 redis/commands/generic/renamenx.mdx           |   165 +
 redis/commands/generic/restore.mdx            |   169 +
 redis/commands/generic/scan.mdx               |   172 +
 redis/commands/generic/touch.mdx              |   164 +
 redis/commands/generic/ttl.mdx                |   168 +
 redis/commands/generic/type.mdx               |   166 +
 redis/commands/generic/unlink.mdx             |   164 +
 redis/commands/generic/wait.mdx               |   164 +
 redis/commands/generic/waitaof.mdx            |   166 +
 redis/commands/geo/geoadd.mdx                 |   178 +
 redis/commands/geo/geodist.mdx                |   173 +
 redis/commands/geo/geohash.mdx                |   165 +
 redis/commands/geo/geopos.mdx                 |   165 +
 redis/commands/geo/georadius-ro.mdx           |   173 +
 redis/commands/geo/georadius.mdx              |   174 +
 redis/commands/geo/georadiusbymember-ro.mdx   |   171 +
 redis/commands/geo/georadiusbymember.mdx      |   172 +
 redis/commands/geo/geosearch.mdx              |   179 +
 redis/commands/geo/geosearchstore.mdx         |   180 +
 redis/commands/geo/overview.mdx               |    19 +
 redis/commands/hash/hdel.mdx                  |   166 +
 redis/commands/hash/hexists.mdx               |   168 +
 redis/commands/hash/hexpire.mdx               |   175 +
 redis/commands/hash/hexpireat.mdx             |   175 +
 redis/commands/hash/hexpiretime.mdx           |   172 +
 redis/commands/hash/hget.mdx                  |   167 +
 redis/commands/hash/hgetall.mdx               |   173 +
 redis/commands/hash/hgetdel.mdx               |   174 +
 redis/commands/hash/hgetex.mdx                |   170 +
 redis/commands/hash/hincrby.mdx               |   170 +
 redis/commands/hash/hincrbyfloat.mdx          |   174 +
 redis/commands/hash/hkeys.mdx                 |   169 +
 redis/commands/hash/hlen.mdx                  |   169 +
 redis/commands/hash/hmget.mdx                 |   171 +
 redis/commands/hash/hmset.mdx                 |   165 +
 redis/commands/hash/hpersist.mdx              |   170 +
 redis/commands/hash/hpexpire.mdx              |   175 +
 redis/commands/hash/hpexpireat.mdx            |   175 +
 redis/commands/hash/hpexpiretime.mdx          |   173 +
 redis/commands/hash/hpttl.mdx                 |   173 +
 redis/commands/hash/hrandfield.mdx            |   175 +
 redis/commands/hash/hscan.mdx                 |   181 +
 redis/commands/hash/hset.mdx                  |   169 +
 redis/commands/hash/hsetex.mdx                |   175 +
 redis/commands/hash/hsetnx.mdx                |   166 +
 redis/commands/hash/hstrlen.mdx               |   166 +
 redis/commands/hash/httl.mdx                  |   173 +
 redis/commands/hash/hvals.mdx                 |   169 +
 redis/commands/hash/overview.mdx              |    37 +
 redis/commands/hyperloglog/overview.mdx       |    12 +
 redis/commands/hyperloglog/pfadd.mdx          |   165 +
 redis/commands/hyperloglog/pfcount.mdx        |   164 +
 redis/commands/hyperloglog/pfmerge.mdx        |   165 +
 redis/commands/json/json-arrappend.mdx        |   171 +
 redis/commands/json/json-arrindex.mdx         |   173 +
 redis/commands/json/json-arrinsert.mdx        |   172 +
 redis/commands/json/json-arrlen.mdx           |   170 +
 redis/commands/json/json-arrpop.mdx           |   171 +
 redis/commands/json/json-arrtrim.mdx          |   172 +
 redis/commands/json/json-clear.mdx            |   170 +
 redis/commands/json/json-debug.mdx            |   167 +
 redis/commands/json/json-del.mdx              |   170 +
 redis/commands/json/json-forget.mdx           |   170 +
 redis/commands/json/json-get.mdx              |   173 +
 redis/commands/json/json-merge.mdx            |   173 +
 redis/commands/json/json-mget.mdx             |   170 +
 redis/commands/json/json-mset.mdx             |   175 +
 redis/commands/json/json-numincrby.mdx        |   171 +
 redis/commands/json/json-nummultby.mdx        |   175 +
 redis/commands/json/json-objkeys.mdx          |   170 +
 redis/commands/json/json-objlen.mdx           |   170 +
 redis/commands/json/json-resp.mdx             |   173 +
 redis/commands/json/json-set.mdx              |   172 +
 redis/commands/json/json-strappend.mdx        |   171 +
 redis/commands/json/json-strlen.mdx           |   170 +
 redis/commands/json/json-toggle.mdx           |   170 +
 redis/commands/json/json-type.mdx             |   170 +
 redis/commands/json/overview.mdx              |    35 +
 redis/commands/list/blmove.mdx                |   169 +
 redis/commands/list/blmpop.mdx                |   168 +
 redis/commands/list/blpop.mdx                 |   163 +
 redis/commands/list/brpop.mdx                 |   163 +
 redis/commands/list/brpoplpush.mdx            |   165 +
 redis/commands/list/lindex.mdx                |   167 +
 redis/commands/list/linsert.mdx               |   168 +
 redis/commands/list/llen.mdx                  |   166 +
 redis/commands/list/lmove.mdx                 |   168 +
 redis/commands/list/lmpop.mdx                 |   165 +
 redis/commands/list/lpop.mdx                  |   167 +
 redis/commands/list/lpos.mdx                  |   171 +
 redis/commands/list/lpush.mdx                 |   168 +
 redis/commands/list/lpushx.mdx                |   167 +
 redis/commands/list/lrange.mdx                |   168 +
 redis/commands/list/lrem.mdx                  |   168 +
 redis/commands/list/lset.mdx                  |   169 +
 redis/commands/list/ltrim.mdx                 |   168 +
 redis/commands/list/overview.mdx              |    31 +
 redis/commands/list/rpop.mdx                  |   167 +
 redis/commands/list/rpoplpush.mdx             |   161 +
 redis/commands/list/rpush.mdx                 |   168 +
 redis/commands/list/rpushx.mdx                |   167 +
 redis/commands/overview.mdx                   |    28 +
 redis/commands/pub-sub/overview.mdx           |    15 +
 redis/commands/pub-sub/psubscribe.mdx         |   153 +
 redis/commands/pub-sub/publish.mdx            |   165 +
 redis/commands/pub-sub/pubsub.mdx             |   161 +
 redis/commands/pub-sub/punsubscribe.mdx       |   147 +
 redis/commands/pub-sub/subscribe.mdx          |   153 +
 redis/commands/pub-sub/unsubscribe.mdx        |   147 +
 redis/commands/scripting/eval-ro.mdx          |   176 +
 redis/commands/scripting/eval.mdx             |   176 +
 redis/commands/scripting/evalsha-ro.mdx       |   173 +
 redis/commands/scripting/evalsha.mdx          |   173 +
 redis/commands/scripting/overview.mdx         |    17 +
 redis/commands/scripting/script-exists.mdx    |   168 +
 redis/commands/scripting/script-flush.mdx     |   164 +
 redis/commands/scripting/script-kill.mdx      |   159 +
 redis/commands/scripting/script-load.mdx      |   169 +
 redis/commands/search/overview.mdx            |    55 +
 redis/commands/search/search-aggregate.mdx    |   123 +
 redis/commands/search/search-aliasadd.mdx     |   106 +
 redis/commands/search/search-aliasdel.mdx     |    92 +
 redis/commands/search/search-count.mdx        |   112 +
 redis/commands/search/search-create.mdx       |   165 +
 redis/commands/search/search-describe.mdx     |   122 +
 redis/commands/search/search-drop.mdx         |    98 +
 redis/commands/search/search-listaliases.mdx  |    98 +
 redis/commands/search/search-listindexes.mdx  |   140 +
 redis/commands/search/search-query.mdx        |   167 +
 redis/commands/search/search-reindex.mdx      |    48 +
 redis/commands/search/search-waitindexing.mdx |   104 +
 redis/commands/server/acl.mdx                 |   178 +
 redis/commands/server/command.mdx             |   158 +
 redis/commands/server/config-get.mdx          |   163 +
 redis/commands/server/config-set.mdx          |   165 +
 redis/commands/server/dbsize.mdx              |   167 +
 redis/commands/server/flushall.mdx            |   170 +
 redis/commands/server/flushdb.mdx             |   170 +
 redis/commands/server/info.mdx                |   162 +
 redis/commands/server/monitor.mdx             |   126 +
 redis/commands/server/overview.mdx            |    19 +
 redis/commands/server/time.mdx                |   162 +
 redis/commands/set/overview.mdx               |    26 +
 redis/commands/set/sadd.mdx                   |   169 +
 redis/commands/set/scard.mdx                  |   166 +
 redis/commands/set/sdiff.mdx                  |   167 +
 redis/commands/set/sdiffstore.mdx             |   168 +
 redis/commands/set/sinter.mdx                 |   167 +
 redis/commands/set/sintercard.mdx             |   167 +
 redis/commands/set/sinterstore.mdx            |   167 +
 redis/commands/set/sismember.mdx              |   167 +
 redis/commands/set/smembers.mdx               |   166 +
 redis/commands/set/smismember.mdx             |   167 +
 redis/commands/set/smove.mdx                  |   170 +
 redis/commands/set/spop.mdx                   |   167 +
 redis/commands/set/srandmember.mdx            |   167 +
 redis/commands/set/srem.mdx                   |   167 +
 redis/commands/set/sscan.mdx                  |   176 +
 redis/commands/set/sunion.mdx                 |   167 +
 redis/commands/set/sunionstore.mdx            |   167 +
 redis/commands/sorted-set/bzmpop.mdx          |   168 +
 redis/commands/sorted-set/bzpopmax.mdx        |   163 +
 redis/commands/sorted-set/bzpopmin.mdx        |   163 +
 redis/commands/sorted-set/overview.mdx        |    44 +
 redis/commands/sorted-set/zadd.mdx            |   178 +
 redis/commands/sorted-set/zcard.mdx           |   169 +
 redis/commands/sorted-set/zcount.mdx          |   171 +
 redis/commands/sorted-set/zdiff.mdx           |   169 +
 redis/commands/sorted-set/zdiffstore.mdx      |   172 +
 redis/commands/sorted-set/zincrby.mdx         |   172 +
 redis/commands/sorted-set/zinter.mdx          |   171 +
 redis/commands/sorted-set/zintercard.mdx      |   159 +
 redis/commands/sorted-set/zinterstore.mdx     |   183 +
 redis/commands/sorted-set/zlexcount.mdx       |   171 +
 redis/commands/sorted-set/zmpop.mdx           |   165 +
 redis/commands/sorted-set/zmscore.mdx         |   177 +
 redis/commands/sorted-set/zpopmax.mdx         |   169 +
 redis/commands/sorted-set/zpopmin.mdx         |   169 +
 redis/commands/sorted-set/zrandmember.mdx     |   165 +
 redis/commands/sorted-set/zrange.mdx          |   180 +
 redis/commands/sorted-set/zrangebylex.mdx     |   163 +
 redis/commands/sorted-set/zrangebyscore.mdx   |   168 +
 redis/commands/sorted-set/zrangestore.mdx     |   169 +
 redis/commands/sorted-set/zrank.mdx           |   170 +
 redis/commands/sorted-set/zrem.mdx            |   165 +
 redis/commands/sorted-set/zremrangebylex.mdx  |   166 +
 redis/commands/sorted-set/zremrangebyrank.mdx |   166 +
 .../commands/sorted-set/zremrangebyscore.mdx  |   166 +
 redis/commands/sorted-set/zrevrange.mdx       |   167 +
 redis/commands/sorted-set/zrevrangebylex.mdx  |   163 +
 .../commands/sorted-set/zrevrangebyscore.mdx  |   168 +
 redis/commands/sorted-set/zrevrank.mdx        |   170 +
 redis/commands/sorted-set/zscan.mdx           |   183 +
 redis/commands/sorted-set/zscore.mdx          |   177 +
 redis/commands/sorted-set/zunion.mdx          |   174 +
 redis/commands/sorted-set/zunionstore.mdx     |   183 +
 redis/commands/streams/overview.mdx           |    27 +
 redis/commands/streams/xack.mdx               |   166 +
 redis/commands/streams/xackdel.mdx            |   169 +
 redis/commands/streams/xadd.mdx               |   169 +
 redis/commands/streams/xautoclaim.mdx         |   181 +
 redis/commands/streams/xclaim.mdx             |   181 +
 redis/commands/streams/xdel.mdx               |   165 +
 redis/commands/streams/xdelex.mdx             |   168 +
 redis/commands/streams/xgroup.mdx             |   178 +
 redis/commands/streams/xinfo-consumers.mdx    |   168 +
 redis/commands/streams/xinfo-groups.mdx       |   164 +
 redis/commands/streams/xinfo-stream.mdx       |   157 +
 redis/commands/streams/xlen.mdx               |   164 +
 redis/commands/streams/xpending.mdx           |   166 +
 redis/commands/streams/xrange.mdx             |   167 +
 redis/commands/streams/xread.mdx              |   171 +
 redis/commands/streams/xreadgroup.mdx         |   178 +
 redis/commands/streams/xrevrange.mdx          |   167 +
 redis/commands/streams/xtrim.mdx              |   169 +
 redis/commands/string/append.mdx              |   166 +
 redis/commands/string/decr.mdx                |   166 +
 redis/commands/string/decrby.mdx              |   167 +
 redis/commands/string/delex.mdx               |   163 +
 redis/commands/string/digest.mdx              |   161 +
 redis/commands/string/get.mdx                 |   173 +
 redis/commands/string/getdel.mdx              |   169 +
 redis/commands/string/getex.mdx               |   165 +
 redis/commands/string/getrange.mdx            |   170 +
 redis/commands/string/getset.mdx              |   165 +
 redis/commands/string/incr.mdx                |   166 +
 redis/commands/string/incrby.mdx              |   167 +
 redis/commands/string/incrbyfloat.mdx         |   171 +
 redis/commands/string/mget.mdx                |   169 +
 redis/commands/string/mset.mdx                |   168 +
 redis/commands/string/msetnx.mdx              |   167 +
 redis/commands/string/overview.mdx            |    31 +
 redis/commands/string/psetex.mdx              |   167 +
 redis/commands/string/set.mdx                 |   174 +
 redis/commands/string/setex.mdx               |   167 +
 redis/commands/string/setnx.mdx               |   165 +
 redis/commands/string/setrange.mdx            |   170 +
 redis/commands/string/strlen.mdx              |   166 +
 redis/commands/transactions/discard.mdx       |   125 +
 redis/commands/transactions/exec.mdx          |   127 +
 redis/commands/transactions/multi.mdx         |   127 +
 redis/commands/transactions/overview.mdx      |    14 +
 redis/commands/transactions/unwatch.mdx       |   126 +
 redis/commands/transactions/watch.mdx         |   138 +
 redis/overall/changelog.mdx                   |    16 +-
 redis/overall/compatibility.mdx               |   364 +-
 .../bucket-aggregations/terms.mdx             |     2 +-
 redis/search/aggregations.mdx                 |     2 +
 redis/search/aliases.mdx                      |     6 +-
 redis/search/command-reference.mdx            |   320 +-
 redis/search/counting.mdx                     |     2 +-
 redis/search/document-updates.mdx             |     2 +-
 redis/search/index-management.mdx             |    13 +-
 redis/search/querying.mdx                     |     4 +-
 redis/search/schema-definition.mdx            |     2 +
 306 files changed, 91223 insertions(+), 1389 deletions(-)
 create mode 100644 redis/commands/bitmap/bitcount.mdx
 create mode 100644 redis/commands/bitmap/bitfield-ro.mdx
 create mode 100644 redis/commands/bitmap/bitfield.mdx
 create mode 100644 redis/commands/bitmap/bitop.mdx
 create mode 100644 redis/commands/bitmap/bitpos.mdx
 create mode 100644 redis/commands/bitmap/getbit.mdx
 create mode 100644 redis/commands/bitmap/overview.mdx
 create mode 100644 redis/commands/bitmap/setbit.mdx
 create mode 100644 redis/commands/connection/auth.mdx
 create mode 100644 redis/commands/connection/client-getname.mdx
 create mode 100644 redis/commands/connection/client-id.mdx
 create mode 100644 redis/commands/connection/client-info.mdx
 create mode 100644 redis/commands/connection/client-list.mdx
 create mode 100644 redis/commands/connection/client-setinfo.mdx
 create mode 100644 redis/commands/connection/client-setname.mdx
 create mode 100644 redis/commands/connection/echo.mdx
 create mode 100644 redis/commands/connection/hello.mdx
 create mode 100644 redis/commands/connection/overview.mdx
 create mode 100644 redis/commands/connection/ping.mdx
 create mode 100644 redis/commands/connection/quit.mdx
 create mode 100644 redis/commands/connection/reset.mdx
 create mode 100644 redis/commands/connection/select.mdx
 create mode 100644 redis/commands/functions/fcall-ro.mdx
 create mode 100644 redis/commands/functions/fcall.mdx
 create mode 100644 redis/commands/functions/function-delete.mdx
 create mode 100644 redis/commands/functions/function-flush.mdx
 create mode 100644 redis/commands/functions/function-kill.mdx
 create mode 100644 redis/commands/functions/function-list.mdx
 create mode 100644 redis/commands/functions/function-load.mdx
 create mode 100644 redis/commands/functions/function-stats.mdx
 create mode 100644 redis/commands/functions/overview.mdx
 create mode 100644 redis/commands/generic/copy.mdx
 create mode 100644 redis/commands/generic/del.mdx
 create mode 100644 redis/commands/generic/dump.mdx
 create mode 100644 redis/commands/generic/exists.mdx
 create mode 100644 redis/commands/generic/expire.mdx
 create mode 100644 redis/commands/generic/expireat.mdx
 create mode 100644 redis/commands/generic/expiretime.mdx
 create mode 100644 redis/commands/generic/keys.mdx
 create mode 100644 redis/commands/generic/memory-usage.mdx
 create mode 100644 redis/commands/generic/overview.mdx
 create mode 100644 redis/commands/generic/persist.mdx
 create mode 100644 redis/commands/generic/pexpire.mdx
 create mode 100644 redis/commands/generic/pexpireat.mdx
 create mode 100644 redis/commands/generic/pexpiretime.mdx
 create mode 100644 redis/commands/generic/pttl.mdx
 create mode 100644 redis/commands/generic/randomkey.mdx
 create mode 100644 redis/commands/generic/rename.mdx
 create mode 100644 redis/commands/generic/renamenx.mdx
 create mode 100644 redis/commands/generic/restore.mdx
 create mode 100644 redis/commands/generic/scan.mdx
 create mode 100644 redis/commands/generic/touch.mdx
 create mode 100644 redis/commands/generic/ttl.mdx
 create mode 100644 redis/commands/generic/type.mdx
 create mode 100644 redis/commands/generic/unlink.mdx
 create mode 100644 redis/commands/generic/wait.mdx
 create mode 100644 redis/commands/generic/waitaof.mdx
 create mode 100644 redis/commands/geo/geoadd.mdx
 create mode 100644 redis/commands/geo/geodist.mdx
 create mode 100644 redis/commands/geo/geohash.mdx
 create mode 100644 redis/commands/geo/geopos.mdx
 create mode 100644 redis/commands/geo/georadius-ro.mdx
 create mode 100644 redis/commands/geo/georadius.mdx
 create mode 100644 redis/commands/geo/georadiusbymember-ro.mdx
 create mode 100644 redis/commands/geo/georadiusbymember.mdx
 create mode 100644 redis/commands/geo/geosearch.mdx
 create mode 100644 redis/commands/geo/geosearchstore.mdx
 create mode 100644 redis/commands/geo/overview.mdx
 create mode 100644 redis/commands/hash/hdel.mdx
 create mode 100644 redis/commands/hash/hexists.mdx
 create mode 100644 redis/commands/hash/hexpire.mdx
 create mode 100644 redis/commands/hash/hexpireat.mdx
 create mode 100644 redis/commands/hash/hexpiretime.mdx
 create mode 100644 redis/commands/hash/hget.mdx
 create mode 100644 redis/commands/hash/hgetall.mdx
 create mode 100644 redis/commands/hash/hgetdel.mdx
 create mode 100644 redis/commands/hash/hgetex.mdx
 create mode 100644 redis/commands/hash/hincrby.mdx
 create mode 100644 redis/commands/hash/hincrbyfloat.mdx
 create mode 100644 redis/commands/hash/hkeys.mdx
 create mode 100644 redis/commands/hash/hlen.mdx
 create mode 100644 redis/commands/hash/hmget.mdx
 create mode 100644 redis/commands/hash/hmset.mdx
 create mode 100644 redis/commands/hash/hpersist.mdx
 create mode 100644 redis/commands/hash/hpexpire.mdx
 create mode 100644 redis/commands/hash/hpexpireat.mdx
 create mode 100644 redis/commands/hash/hpexpiretime.mdx
 create mode 100644 redis/commands/hash/hpttl.mdx
 create mode 100644 redis/commands/hash/hrandfield.mdx
 create mode 100644 redis/commands/hash/hscan.mdx
 create mode 100644 redis/commands/hash/hset.mdx
 create mode 100644 redis/commands/hash/hsetex.mdx
 create mode 100644 redis/commands/hash/hsetnx.mdx
 create mode 100644 redis/commands/hash/hstrlen.mdx
 create mode 100644 redis/commands/hash/httl.mdx
 create mode 100644 redis/commands/hash/hvals.mdx
 create mode 100644 redis/commands/hash/overview.mdx
 create mode 100644 redis/commands/hyperloglog/overview.mdx
 create mode 100644 redis/commands/hyperloglog/pfadd.mdx
 create mode 100644 redis/commands/hyperloglog/pfcount.mdx
 create mode 100644 redis/commands/hyperloglog/pfmerge.mdx
 create mode 100644 redis/commands/json/json-arrappend.mdx
 create mode 100644 redis/commands/json/json-arrindex.mdx
 create mode 100644 redis/commands/json/json-arrinsert.mdx
 create mode 100644 redis/commands/json/json-arrlen.mdx
 create mode 100644 redis/commands/json/json-arrpop.mdx
 create mode 100644 redis/commands/json/json-arrtrim.mdx
 create mode 100644 redis/commands/json/json-clear.mdx
 create mode 100644 redis/commands/json/json-debug.mdx
 create mode 100644 redis/commands/json/json-del.mdx
 create mode 100644 redis/commands/json/json-forget.mdx
 create mode 100644 redis/commands/json/json-get.mdx
 create mode 100644 redis/commands/json/json-merge.mdx
 create mode 100644 redis/commands/json/json-mget.mdx
 create mode 100644 redis/commands/json/json-mset.mdx
 create mode 100644 redis/commands/json/json-numincrby.mdx
 create mode 100644 redis/commands/json/json-nummultby.mdx
 create mode 100644 redis/commands/json/json-objkeys.mdx
 create mode 100644 redis/commands/json/json-objlen.mdx
 create mode 100644 redis/commands/json/json-resp.mdx
 create mode 100644 redis/commands/json/json-set.mdx
 create mode 100644 redis/commands/json/json-strappend.mdx
 create mode 100644 redis/commands/json/json-strlen.mdx
 create mode 100644 redis/commands/json/json-toggle.mdx
 create mode 100644 redis/commands/json/json-type.mdx
 create mode 100644 redis/commands/json/overview.mdx
 create mode 100644 redis/commands/list/blmove.mdx
 create mode 100644 redis/commands/list/blmpop.mdx
 create mode 100644 redis/commands/list/blpop.mdx
 create mode 100644 redis/commands/list/brpop.mdx
 create mode 100644 redis/commands/list/brpoplpush.mdx
 create mode 100644 redis/commands/list/lindex.mdx
 create mode 100644 redis/commands/list/linsert.mdx
 create mode 100644 redis/commands/list/llen.mdx
 create mode 100644 redis/commands/list/lmove.mdx
 create mode 100644 redis/commands/list/lmpop.mdx
 create mode 100644 redis/commands/list/lpop.mdx
 create mode 100644 redis/commands/list/lpos.mdx
 create mode 100644 redis/commands/list/lpush.mdx
 create mode 100644 redis/commands/list/lpushx.mdx
 create mode 100644 redis/commands/list/lrange.mdx
 create mode 100644 redis/commands/list/lrem.mdx
 create mode 100644 redis/commands/list/lset.mdx
 create mode 100644 redis/commands/list/ltrim.mdx
 create mode 100644 redis/commands/list/overview.mdx
 create mode 100644 redis/commands/list/rpop.mdx
 create mode 100644 redis/commands/list/rpoplpush.mdx
 create mode 100644 redis/commands/list/rpush.mdx
 create mode 100644 redis/commands/list/rpushx.mdx
 create mode 100644 redis/commands/overview.mdx
 create mode 100644 redis/commands/pub-sub/overview.mdx
 create mode 100644 redis/commands/pub-sub/psubscribe.mdx
 create mode 100644 redis/commands/pub-sub/publish.mdx
 create mode 100644 redis/commands/pub-sub/pubsub.mdx
 create mode 100644 redis/commands/pub-sub/punsubscribe.mdx
 create mode 100644 redis/commands/pub-sub/subscribe.mdx
 create mode 100644 redis/commands/pub-sub/unsubscribe.mdx
 create mode 100644 redis/commands/scripting/eval-ro.mdx
 create mode 100644 redis/commands/scripting/eval.mdx
 create mode 100644 redis/commands/scripting/evalsha-ro.mdx
 create mode 100644 redis/commands/scripting/evalsha.mdx
 create mode 100644 redis/commands/scripting/overview.mdx
 create mode 100644 redis/commands/scripting/script-exists.mdx
 create mode 100644 redis/commands/scripting/script-flush.mdx
 create mode 100644 redis/commands/scripting/script-kill.mdx
 create mode 100644 redis/commands/scripting/script-load.mdx
 create mode 100644 redis/commands/search/overview.mdx
 create mode 100644 redis/commands/search/search-aggregate.mdx
 create mode 100644 redis/commands/search/search-aliasadd.mdx
 create mode 100644 redis/commands/search/search-aliasdel.mdx
 create mode 100644 redis/commands/search/search-count.mdx
 create mode 100644 redis/commands/search/search-create.mdx
 create mode 100644 redis/commands/search/search-describe.mdx
 create mode 100644 redis/commands/search/search-drop.mdx
 create mode 100644 redis/commands/search/search-listaliases.mdx
 create mode 100644 redis/commands/search/search-listindexes.mdx
 create mode 100644 redis/commands/search/search-query.mdx
 create mode 100644 redis/commands/search/search-reindex.mdx
 create mode 100644 redis/commands/search/search-waitindexing.mdx
 create mode 100644 redis/commands/server/acl.mdx
 create mode 100644 redis/commands/server/command.mdx
 create mode 100644 redis/commands/server/config-get.mdx
 create mode 100644 redis/commands/server/config-set.mdx
 create mode 100644 redis/commands/server/dbsize.mdx
 create mode 100644 redis/commands/server/flushall.mdx
 create mode 100644 redis/commands/server/flushdb.mdx
 create mode 100644 redis/commands/server/info.mdx
 create mode 100644 redis/commands/server/monitor.mdx
 create mode 100644 redis/commands/server/overview.mdx
 create mode 100644 redis/commands/server/time.mdx
 create mode 100644 redis/commands/set/overview.mdx
 create mode 100644 redis/commands/set/sadd.mdx
 create mode 100644 redis/commands/set/scard.mdx
 create mode 100644 redis/commands/set/sdiff.mdx
 create mode 100644 redis/commands/set/sdiffstore.mdx
 create mode 100644 redis/commands/set/sinter.mdx
 create mode 100644 redis/commands/set/sintercard.mdx
 create mode 100644 redis/commands/set/sinterstore.mdx
 create mode 100644 redis/commands/set/sismember.mdx
 create mode 100644 redis/commands/set/smembers.mdx
 create mode 100644 redis/commands/set/smismember.mdx
 create mode 100644 redis/commands/set/smove.mdx
 create mode 100644 redis/commands/set/spop.mdx
 create mode 100644 redis/commands/set/srandmember.mdx
 create mode 100644 redis/commands/set/srem.mdx
 create mode 100644 redis/commands/set/sscan.mdx
 create mode 100644 redis/commands/set/sunion.mdx
 create mode 100644 redis/commands/set/sunionstore.mdx
 create mode 100644 redis/commands/sorted-set/bzmpop.mdx
 create mode 100644 redis/commands/sorted-set/bzpopmax.mdx
 create mode 100644 redis/commands/sorted-set/bzpopmin.mdx
 create mode 100644 redis/commands/sorted-set/overview.mdx
 create mode 100644 redis/commands/sorted-set/zadd.mdx
 create mode 100644 redis/commands/sorted-set/zcard.mdx
 create mode 100644 redis/commands/sorted-set/zcount.mdx
 create mode 100644 redis/commands/sorted-set/zdiff.mdx
 create mode 100644 redis/commands/sorted-set/zdiffstore.mdx
 create mode 100644 redis/commands/sorted-set/zincrby.mdx
 create mode 100644 redis/commands/sorted-set/zinter.mdx
 create mode 100644 redis/commands/sorted-set/zintercard.mdx
 create mode 100644 redis/commands/sorted-set/zinterstore.mdx
 create mode 100644 redis/commands/sorted-set/zlexcount.mdx
 create mode 100644 redis/commands/sorted-set/zmpop.mdx
 create mode 100644 redis/commands/sorted-set/zmscore.mdx
 create mode 100644 redis/commands/sorted-set/zpopmax.mdx
 create mode 100644 redis/commands/sorted-set/zpopmin.mdx
 create mode 100644 redis/commands/sorted-set/zrandmember.mdx
 create mode 100644 redis/commands/sorted-set/zrange.mdx
 create mode 100644 redis/commands/sorted-set/zrangebylex.mdx
 create mode 100644 redis/commands/sorted-set/zrangebyscore.mdx
 create mode 100644 redis/commands/sorted-set/zrangestore.mdx
 create mode 100644 redis/commands/sorted-set/zrank.mdx
 create mode 100644 redis/commands/sorted-set/zrem.mdx
 create mode 100644 redis/commands/sorted-set/zremrangebylex.mdx
 create mode 100644 redis/commands/sorted-set/zremrangebyrank.mdx
 create mode 100644 redis/commands/sorted-set/zremrangebyscore.mdx
 create mode 100644 redis/commands/sorted-set/zrevrange.mdx
 create mode 100644 redis/commands/sorted-set/zrevrangebylex.mdx
 create mode 100644 redis/commands/sorted-set/zrevrangebyscore.mdx
 create mode 100644 redis/commands/sorted-set/zrevrank.mdx
 create mode 100644 redis/commands/sorted-set/zscan.mdx
 create mode 100644 redis/commands/sorted-set/zscore.mdx
 create mode 100644 redis/commands/sorted-set/zunion.mdx
 create mode 100644 redis/commands/sorted-set/zunionstore.mdx
 create mode 100644 redis/commands/streams/overview.mdx
 create mode 100644 redis/commands/streams/xack.mdx
 create mode 100644 redis/commands/streams/xackdel.mdx
 create mode 100644 redis/commands/streams/xadd.mdx
 create mode 100644 redis/commands/streams/xautoclaim.mdx
 create mode 100644 redis/commands/streams/xclaim.mdx
 create mode 100644 redis/commands/streams/xdel.mdx
 create mode 100644 redis/commands/streams/xdelex.mdx
 create mode 100644 redis/commands/streams/xgroup.mdx
 create mode 100644 redis/commands/streams/xinfo-consumers.mdx
 create mode 100644 redis/commands/streams/xinfo-groups.mdx
 create mode 100644 redis/commands/streams/xinfo-stream.mdx
 create mode 100644 redis/commands/streams/xlen.mdx
 create mode 100644 redis/commands/streams/xpending.mdx
 create mode 100644 redis/commands/streams/xrange.mdx
 create mode 100644 redis/commands/streams/xread.mdx
 create mode 100644 redis/commands/streams/xreadgroup.mdx
 create mode 100644 redis/commands/streams/xrevrange.mdx
 create mode 100644 redis/commands/streams/xtrim.mdx
 create mode 100644 redis/commands/string/append.mdx
 create mode 100644 redis/commands/string/decr.mdx
 create mode 100644 redis/commands/string/decrby.mdx
 create mode 100644 redis/commands/string/delex.mdx
 create mode 100644 redis/commands/string/digest.mdx
 create mode 100644 redis/commands/string/get.mdx
 create mode 100644 redis/commands/string/getdel.mdx
 create mode 100644 redis/commands/string/getex.mdx
 create mode 100644 redis/commands/string/getrange.mdx
 create mode 100644 redis/commands/string/getset.mdx
 create mode 100644 redis/commands/string/incr.mdx
 create mode 100644 redis/commands/string/incrby.mdx
 create mode 100644 redis/commands/string/incrbyfloat.mdx
 create mode 100644 redis/commands/string/mget.mdx
 create mode 100644 redis/commands/string/mset.mdx
 create mode 100644 redis/commands/string/msetnx.mdx
 create mode 100644 redis/commands/string/overview.mdx
 create mode 100644 redis/commands/string/psetex.mdx
 create mode 100644 redis/commands/string/set.mdx
 create mode 100644 redis/commands/string/setex.mdx
 create mode 100644 redis/commands/string/setnx.mdx
 create mode 100644 redis/commands/string/setrange.mdx
 create mode 100644 redis/commands/string/strlen.mdx
 create mode 100644 redis/commands/transactions/discard.mdx
 create mode 100644 redis/commands/transactions/exec.mdx
 create mode 100644 redis/commands/transactions/multi.mdx
 create mode 100644 redis/commands/transactions/overview.mdx
 create mode 100644 redis/commands/transactions/unwatch.mdx
 create mode 100644 redis/commands/transactions/watch.mdx

diff --git a/docs.json b/docs.json
index 0891e59a6..2ca3cbf5a 100644
--- a/docs.json
+++ b/docs.json
@@ -939,6 +939,393 @@
                 ]
               }
             ]
+          },
+          {
+            "group": "Command Reference",
+            "pages": [
+              "redis/commands/overview",
+              {
+                "group": "Bitmap",
+                "pages": [
+                  "redis/commands/bitmap/overview",
+                  "redis/commands/bitmap/bitcount",
+                  "redis/commands/bitmap/bitfield",
+                  "redis/commands/bitmap/bitfield-ro",
+                  "redis/commands/bitmap/bitop",
+                  "redis/commands/bitmap/bitpos",
+                  "redis/commands/bitmap/getbit",
+                  "redis/commands/bitmap/setbit"
+                ]
+              },
+              {
+                "group": "Connection",
+                "pages": [
+                  "redis/commands/connection/overview",
+                  "redis/commands/connection/auth",
+                  "redis/commands/connection/client-getname",
+                  "redis/commands/connection/client-id",
+                  "redis/commands/connection/client-info",
+                  "redis/commands/connection/client-list",
+                  "redis/commands/connection/client-setinfo",
+                  "redis/commands/connection/client-setname",
+                  "redis/commands/connection/echo",
+                  "redis/commands/connection/hello",
+                  "redis/commands/connection/ping",
+                  "redis/commands/connection/quit",
+                  "redis/commands/connection/reset",
+                  "redis/commands/connection/select"
+                ]
+              },
+              {
+                "group": "Functions",
+                "pages": [
+                  "redis/commands/functions/overview",
+                  "redis/commands/functions/fcall",
+                  "redis/commands/functions/fcall-ro",
+                  "redis/commands/functions/function-delete",
+                  "redis/commands/functions/function-flush",
+                  "redis/commands/functions/function-kill",
+                  "redis/commands/functions/function-list",
+                  "redis/commands/functions/function-load",
+                  "redis/commands/functions/function-stats"
+                ]
+              },
+              {
+                "group": "Generic",
+                "pages": [
+                  "redis/commands/generic/overview",
+                  "redis/commands/generic/copy",
+                  "redis/commands/generic/del",
+                  "redis/commands/generic/dump",
+                  "redis/commands/generic/exists",
+                  "redis/commands/generic/expire",
+                  "redis/commands/generic/expireat",
+                  "redis/commands/generic/expiretime",
+                  "redis/commands/generic/keys",
+                  "redis/commands/generic/memory-usage",
+                  "redis/commands/generic/persist",
+                  "redis/commands/generic/pexpire",
+                  "redis/commands/generic/pexpireat",
+                  "redis/commands/generic/pexpiretime",
+                  "redis/commands/generic/pttl",
+                  "redis/commands/generic/randomkey",
+                  "redis/commands/generic/rename",
+                  "redis/commands/generic/renamenx",
+                  "redis/commands/generic/restore",
+                  "redis/commands/generic/scan",
+                  "redis/commands/generic/touch",
+                  "redis/commands/generic/ttl",
+                  "redis/commands/generic/type",
+                  "redis/commands/generic/unlink",
+                  "redis/commands/generic/wait",
+                  "redis/commands/generic/waitaof"
+                ]
+              },
+              {
+                "group": "Geo",
+                "pages": [
+                  "redis/commands/geo/overview",
+                  "redis/commands/geo/geoadd",
+                  "redis/commands/geo/geodist",
+                  "redis/commands/geo/geohash",
+                  "redis/commands/geo/geopos",
+                  "redis/commands/geo/georadius",
+                  "redis/commands/geo/georadius-ro",
+                  "redis/commands/geo/georadiusbymember",
+                  "redis/commands/geo/georadiusbymember-ro",
+                  "redis/commands/geo/geosearch",
+                  "redis/commands/geo/geosearchstore"
+                ]
+              },
+              {
+                "group": "Hash",
+                "pages": [
+                  "redis/commands/hash/overview",
+                  "redis/commands/hash/hdel",
+                  "redis/commands/hash/hexists",
+                  "redis/commands/hash/hexpire",
+                  "redis/commands/hash/hexpireat",
+                  "redis/commands/hash/hexpiretime",
+                  "redis/commands/hash/hget",
+                  "redis/commands/hash/hgetall",
+                  "redis/commands/hash/hgetdel",
+                  "redis/commands/hash/hgetex",
+                  "redis/commands/hash/hincrby",
+                  "redis/commands/hash/hincrbyfloat",
+                  "redis/commands/hash/hkeys",
+                  "redis/commands/hash/hlen",
+                  "redis/commands/hash/hmget",
+                  "redis/commands/hash/hmset",
+                  "redis/commands/hash/hpersist",
+                  "redis/commands/hash/hpexpire",
+                  "redis/commands/hash/hpexpireat",
+                  "redis/commands/hash/hpexpiretime",
+                  "redis/commands/hash/hpttl",
+                  "redis/commands/hash/hrandfield",
+                  "redis/commands/hash/hscan",
+                  "redis/commands/hash/hset",
+                  "redis/commands/hash/hsetex",
+                  "redis/commands/hash/hsetnx",
+                  "redis/commands/hash/hstrlen",
+                  "redis/commands/hash/httl",
+                  "redis/commands/hash/hvals"
+                ]
+              },
+              {
+                "group": "HyperLogLog",
+                "pages": [
+                  "redis/commands/hyperloglog/overview",
+                  "redis/commands/hyperloglog/pfadd",
+                  "redis/commands/hyperloglog/pfcount",
+                  "redis/commands/hyperloglog/pfmerge"
+                ]
+              },
+              {
+                "group": "JSON",
+                "pages": [
+                  "redis/commands/json/overview",
+                  "redis/commands/json/json-arrappend",
+                  "redis/commands/json/json-arrindex",
+                  "redis/commands/json/json-arrinsert",
+                  "redis/commands/json/json-arrlen",
+                  "redis/commands/json/json-arrpop",
+                  "redis/commands/json/json-arrtrim",
+                  "redis/commands/json/json-clear",
+                  "redis/commands/json/json-del",
+                  "redis/commands/json/json-debug",
+                  "redis/commands/json/json-forget",
+                  "redis/commands/json/json-get",
+                  "redis/commands/json/json-merge",
+                  "redis/commands/json/json-mget",
+                  "redis/commands/json/json-mset",
+                  "redis/commands/json/json-numincrby",
+                  "redis/commands/json/json-nummultby",
+                  "redis/commands/json/json-objkeys",
+                  "redis/commands/json/json-objlen",
+                  "redis/commands/json/json-resp",
+                  "redis/commands/json/json-set",
+                  "redis/commands/json/json-strappend",
+                  "redis/commands/json/json-strlen",
+                  "redis/commands/json/json-toggle",
+                  "redis/commands/json/json-type"
+                ]
+              },
+              {
+                "group": "List",
+                "pages": [
+                  "redis/commands/list/overview",
+                  "redis/commands/list/blmove",
+                  "redis/commands/list/blmpop",
+                  "redis/commands/list/blpop",
+                  "redis/commands/list/brpop",
+                  "redis/commands/list/brpoplpush",
+                  "redis/commands/list/lindex",
+                  "redis/commands/list/linsert",
+                  "redis/commands/list/llen",
+                  "redis/commands/list/lmove",
+                  "redis/commands/list/lmpop",
+                  "redis/commands/list/lpop",
+                  "redis/commands/list/lpos",
+                  "redis/commands/list/lpush",
+                  "redis/commands/list/lpushx",
+                  "redis/commands/list/lrange",
+                  "redis/commands/list/lrem",
+                  "redis/commands/list/lset",
+                  "redis/commands/list/ltrim",
+                  "redis/commands/list/rpop",
+                  "redis/commands/list/rpoplpush",
+                  "redis/commands/list/rpush",
+                  "redis/commands/list/rpushx"
+                ]
+              },
+              {
+                "group": "Pub/Sub",
+                "pages": [
+                  "redis/commands/pub-sub/overview",
+                  "redis/commands/pub-sub/psubscribe",
+                  "redis/commands/pub-sub/publish",
+                  "redis/commands/pub-sub/pubsub",
+                  "redis/commands/pub-sub/punsubscribe",
+                  "redis/commands/pub-sub/subscribe",
+                  "redis/commands/pub-sub/unsubscribe"
+                ]
+              },
+              {
+                "group": "Scripting",
+                "pages": [
+                  "redis/commands/scripting/overview",
+                  "redis/commands/scripting/eval",
+                  "redis/commands/scripting/eval-ro",
+                  "redis/commands/scripting/evalsha",
+                  "redis/commands/scripting/evalsha-ro",
+                  "redis/commands/scripting/script-exists",
+                  "redis/commands/scripting/script-flush",
+                  "redis/commands/scripting/script-kill",
+                  "redis/commands/scripting/script-load"
+                ]
+              },
+              {
+                "group": "Search",
+                "pages": [
+                  "redis/commands/search/overview",
+                  "redis/commands/search/search-create",
+                  "redis/commands/search/search-reindex",
+                  "redis/commands/search/search-drop",
+                  "redis/commands/search/search-describe",
+                  "redis/commands/search/search-waitindexing",
+                  "redis/commands/search/search-listindexes",
+                  "redis/commands/search/search-query",
+                  "redis/commands/search/search-count",
+                  "redis/commands/search/search-aggregate",
+                  "redis/commands/search/search-aliasadd",
+                  "redis/commands/search/search-aliasdel",
+                  "redis/commands/search/search-listaliases"
+                ]
+              },
+              {
+                "group": "Server",
+                "pages": [
+                  "redis/commands/server/overview",
+                  "redis/commands/server/acl",
+                  "redis/commands/server/command",
+                  "redis/commands/server/config-get",
+                  "redis/commands/server/config-set",
+                  "redis/commands/server/dbsize",
+                  "redis/commands/server/flushall",
+                  "redis/commands/server/flushdb",
+                  "redis/commands/server/info",
+                  "redis/commands/server/monitor",
+                  "redis/commands/server/time"
+                ]
+              },
+              {
+                "group": "Set",
+                "pages": [
+                  "redis/commands/set/overview",
+                  "redis/commands/set/sadd",
+                  "redis/commands/set/scard",
+                  "redis/commands/set/sdiff",
+                  "redis/commands/set/sdiffstore",
+                  "redis/commands/set/sinter",
+                  "redis/commands/set/sintercard",
+                  "redis/commands/set/sinterstore",
+                  "redis/commands/set/sismember",
+                  "redis/commands/set/smembers",
+                  "redis/commands/set/smismember",
+                  "redis/commands/set/smove",
+                  "redis/commands/set/spop",
+                  "redis/commands/set/srandmember",
+                  "redis/commands/set/srem",
+                  "redis/commands/set/sscan",
+                  "redis/commands/set/sunion",
+                  "redis/commands/set/sunionstore"
+                ]
+              },
+              {
+                "group": "Sorted Set",
+                "pages": [
+                  "redis/commands/sorted-set/overview",
+                  "redis/commands/sorted-set/bzmpop",
+                  "redis/commands/sorted-set/bzpopmax",
+                  "redis/commands/sorted-set/bzpopmin",
+                  "redis/commands/sorted-set/zadd",
+                  "redis/commands/sorted-set/zcard",
+                  "redis/commands/sorted-set/zcount",
+                  "redis/commands/sorted-set/zdiff",
+                  "redis/commands/sorted-set/zdiffstore",
+                  "redis/commands/sorted-set/zincrby",
+                  "redis/commands/sorted-set/zinter",
+                  "redis/commands/sorted-set/zintercard",
+                  "redis/commands/sorted-set/zinterstore",
+                  "redis/commands/sorted-set/zlexcount",
+                  "redis/commands/sorted-set/zmpop",
+                  "redis/commands/sorted-set/zmscore",
+                  "redis/commands/sorted-set/zpopmax",
+                  "redis/commands/sorted-set/zpopmin",
+                  "redis/commands/sorted-set/zrandmember",
+                  "redis/commands/sorted-set/zrange",
+                  "redis/commands/sorted-set/zrangebylex",
+                  "redis/commands/sorted-set/zrangebyscore",
+                  "redis/commands/sorted-set/zrangestore",
+                  "redis/commands/sorted-set/zrank",
+                  "redis/commands/sorted-set/zrem",
+                  "redis/commands/sorted-set/zremrangebylex",
+                  "redis/commands/sorted-set/zremrangebyrank",
+                  "redis/commands/sorted-set/zremrangebyscore",
+                  "redis/commands/sorted-set/zrevrange",
+                  "redis/commands/sorted-set/zrevrangebylex",
+                  "redis/commands/sorted-set/zrevrangebyscore",
+                  "redis/commands/sorted-set/zrevrank",
+                  "redis/commands/sorted-set/zscan",
+                  "redis/commands/sorted-set/zscore",
+                  "redis/commands/sorted-set/zunion",
+                  "redis/commands/sorted-set/zunionstore"
+                ]
+              },
+              {
+                "group": "Streams",
+                "pages": [
+                  "redis/commands/streams/overview",
+                  "redis/commands/streams/xack",
+                  "redis/commands/streams/xackdel",
+                  "redis/commands/streams/xadd",
+                  "redis/commands/streams/xautoclaim",
+                  "redis/commands/streams/xclaim",
+                  "redis/commands/streams/xdel",
+                  "redis/commands/streams/xdelex",
+                  "redis/commands/streams/xgroup",
+                  "redis/commands/streams/xinfo-consumers",
+                  "redis/commands/streams/xinfo-groups",
+                  "redis/commands/streams/xinfo-stream",
+                  "redis/commands/streams/xlen",
+                  "redis/commands/streams/xpending",
+                  "redis/commands/streams/xrange",
+                  "redis/commands/streams/xread",
+                  "redis/commands/streams/xreadgroup",
+                  "redis/commands/streams/xrevrange",
+                  "redis/commands/streams/xtrim"
+                ]
+              },
+              {
+                "group": "String",
+                "pages": [
+                  "redis/commands/string/overview",
+                  "redis/commands/string/append",
+                  "redis/commands/string/decr",
+                  "redis/commands/string/decrby",
+                  "redis/commands/string/delex",
+                  "redis/commands/string/digest",
+                  "redis/commands/string/get",
+                  "redis/commands/string/getdel",
+                  "redis/commands/string/getex",
+                  "redis/commands/string/getrange",
+                  "redis/commands/string/getset",
+                  "redis/commands/string/incr",
+                  "redis/commands/string/incrby",
+                  "redis/commands/string/incrbyfloat",
+                  "redis/commands/string/mget",
+                  "redis/commands/string/mset",
+                  "redis/commands/string/msetnx",
+                  "redis/commands/string/psetex",
+                  "redis/commands/string/set",
+                  "redis/commands/string/setex",
+                  "redis/commands/string/setnx",
+                  "redis/commands/string/setrange",
+                  "redis/commands/string/strlen"
+                ]
+              },
+              {
+                "group": "Transactions",
+                "pages": [
+                  "redis/commands/transactions/overview",
+                  "redis/commands/transactions/discard",
+                  "redis/commands/transactions/exec",
+                  "redis/commands/transactions/multi",
+                  "redis/commands/transactions/unwatch",
+                  "redis/commands/transactions/watch"
+                ]
+              }
+            ]
           }
         ]
       },
@@ -1953,6 +2340,10 @@
       "source": "/redis/overall/rediscompatibility",
       "destination": "/redis/overall/compatibility"
     },
+    {
+      "source": "/redis/search/command-reference",
+      "destination": "/redis/commands/search/overview"
+    },
     {
       "source": "/docs/redis/overall/rediscompatibility",
       "destination": "/redis/overall/compatibility"
diff --git a/llms-full.txt b/llms-full.txt
index 8ab508bea..1521fac42 100644
--- a/llms-full.txt
+++ b/llms-full.txt
@@ -10142,7 +10142,7 @@ To view a more detailed Next.js quick start guide for setting up QStash, refer t
 
 It's also possible to schedule a background job to run at a later time using [schedules](/docs/qstash/features/schedules).
 
-If you'd like to invoke another endpoint when the background job is complete, you can use [callbacks](/docs/qstash/features/callbacks).
+If you'd like to invoke another endpoint when the background job is complete, you can use [callbacks](/docs/qstash/features/callbacks).
 
 # Batching
 Source: https://upstash.com/docs/qstash/features/batch
@@ -10441,7 +10441,7 @@ client.message.batch_json(
     "messageId": "msg_..."
   }
 ]
-```
+```
 
 # Callbacks
 Source: https://upstash.com/docs/qstash/features/callbacks
@@ -11496,7 +11496,7 @@ from qstash import QStash
 client = QStash("<QSTASH_TOKEN>")
 client.queue.get("my-queue")
 ```
-</CodeGroup>
+</CodeGroup>
 
 # Retry
 Source: https://upstash.com/docs/qstash/features/retry
@@ -16964,6 +16964,45071 @@ For debugging or monitoring purposes, you can use Realtime Dashboard in console.
   </Card>
 </CardGroup>
 
+# BITCOUNT
+Source: https://upstash.com/docs/redis/commands/bitmap/bitcount
+
+Use `BITCOUNT` to count set bits in a string.
+
+## Syntax
+
+```redis
+BITCOUNT <key> [<start> <end> [BYTE | BIT]]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<start> <end> [BYTE \| BIT]` | No | No | Range to count. Offsets are byte-based unless `BIT` is given; negative offsets count from the end. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const bits = await redis.bitcount(key);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.bitcount("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.bitcount("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.bitCount("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.bitcount("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.BitCount(context.Background(), "my-key", nil).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.bitcount("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.bitcount("my-key")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# BITFIELD
+Source: https://upstash.com/docs/redis/commands/bitmap/bitfield
+
+Use `BITFIELD` to perform arbitrary bitfield operations.
+
+## Syntax
+
+```redis
+BITFIELD <key> [GET <encoding> <offset> | [OVERFLOW WRAP | SAT | FAIL] (SET <encoding> <offset> <value> | INCRBY <encoding> <offset> <increment>) [GET <encoding> <offset> | [OVERFLOW WRAP | SAT | FAIL] (SET <encoding> <offset> <value> | INCRBY <encoding> <offset> <increment>) ...]]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `(GET <encoding> <offset> \| [OVERFLOW WRAP \| SAT \| FAIL] (SET <encoding> <offset> <value> \| INCRBY <encoding> <offset> <increment>))` | No | Yes | Choose one form: `GET` (also return the previous value); `OVERFLOW`; `WRAP`; `SAT`; `FAIL`; `SET`; `INCRBY`. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of integer or null replies, one per subcommand |
+| RESP3 | Array of integer or null replies, one per subcommand |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+const result = await redis.bitfield("my-key").get("u8", 0).exec();
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.bitfield("my-key").get("u8", 0).execute()
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.bitfield("my-key", "GET", "u8", "0");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.bitField("my-key", [{ operation: "GET", encoding: "u8", offset: 0 }]);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.bitfield("my-key").get("u8", 0).execute()
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.BitField(context.Background(), "my-key", "GET", "u8", 0).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.bitfield("my-key", "GET", "u8", "0");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("BITFIELD");
+    command.arg("my-key");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# BITFIELD_RO
+Source: https://upstash.com/docs/redis/commands/bitmap/bitfield-ro
+
+Use `BITFIELD_RO` to read one or more bitfield values without modifying the key.
+
+## Syntax
+
+```redis
+BITFIELD_RO <key> [GET <encoding> <offset> [GET <encoding> <offset> ...]]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `GET <encoding> <offset>` | No | Yes | Read the value at `<offset>` using `<encoding>`, such as `u8` or `i16`. Repeat to read several fields. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of integer or null replies, one per subcommand |
+| RESP3 | Array of integer or null replies, one per subcommand |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.bitfield_ro("my-key").get("u8", 0).execute()
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.bitfield_ro("my-key", "GET", "u8", "0");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.bitFieldRo("my-key", [{ encoding: "u8", offset: 0 }]);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.bitfield_ro("my-key", "u8", 0)
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.BitFieldRO(context.Background(), "my-key", "GET", "u8", 0).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.bitfieldReadonly("my-key", "GET", "u8", "0");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("BITFIELD_RO");
+    command.arg("my-key");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# BITOP
+Source: https://upstash.com/docs/redis/commands/bitmap/bitop
+
+Use `BITOP` to perform bitwise operations between strings.
+
+## Syntax
+
+```redis
+BITOP (AND | OR | XOR | NOT | DIFF | DIFF1 | ANDOR | ONE) <destkey> <key> [<key> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `(AND \| OR \| XOR \| NOT \| DIFF \| DIFF1 \| ANDOR \| ONE)` | Yes | No | Choose one form: `AND`; `OR`; `XOR`; `NOT`; `DIFF`; `DIFF1`; `ANDOR`; `ONE`. |
+| `<destkey>` | Yes | No | Redis key used as destkey. |
+| `<key>` | Yes | Yes | Redis key targeted by the command. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+// AND operation
+await redis.bitop("and", "destKey", "sourceKey1", "sourceKey2");
+
+// OR operation
+await redis.bitop("or", "destKey", "sourceKey1", "sourceKey2");
+
+// XOR operation
+await redis.bitop("xor", "destKey", "sourceKey1", "sourceKey2");
+
+// NOT operation (only accepts one source key)
+await redis.bitop("not", "destKey", "sourceKey");
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.bitop("AND", "destination-key", "source-key-1", "source-key-2")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.bitop("AND", "destination-key", "source-key-1", "source-key-2");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.bitOp("AND", "destination-key", ["source-key-1", "source-key-2"]);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.bitop("AND", "destination-key", "source-key-1", "source-key-2")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.BitOpAnd(context.Background(), "destination-key", "source-key-1", "source-key-2").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.bitop(redis.clients.jedis.args.BitOP.AND, "destination-key", "source-key-1", "source-key-2");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.bit_and("destination-key", &["source-key-1", "source-key-2"])?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# BITPOS
+Source: https://upstash.com/docs/redis/commands/bitmap/bitpos
+
+Use `BITPOS` to find first bit set or clear in a string.
+
+## Syntax
+
+```redis
+BITPOS <key> <bit> [<start> [<end> [BYTE | BIT]]]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<bit>` | Yes | No | Bit value to look for: `0` or `1`. |
+| `<start> [<end> [BYTE \| BIT]]` | No | No | Range to search. Offsets are byte-based unless `BIT` is given; negative offsets count from the end. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer: the position of the first matching bit, or `-1` |
+| RESP3 | Integer: the position of the first matching bit, or `-1` |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.bitpos("key", 1);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.bitpos("my-key", 1)
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.bitpos("my-key", "1");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.bitPos("my-key", 1);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.bitpos("my-key", 1)
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.BitPos(context.Background(), "my-key", 1).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.bitpos("my-key", true);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("BITPOS");
+    command.arg("my-key");
+    command.arg("1");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# GETBIT
+Source: https://upstash.com/docs/redis/commands/bitmap/getbit
+
+Use `GETBIT` to get the bit value at offset.
+
+## Syntax
+
+```redis
+GETBIT <key> <offset>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<offset>` | Yes | No | Zero-based bit offset to read. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer: the bit at the offset, `0` or `1` |
+| RESP3 | Integer: the bit at the offset, `0` or `1` |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const bit = await redis.getbit(key, 4);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.getbit("my-key", 0)
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.getbit("my-key", "0");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.getBit("my-key", 0);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.getbit("my-key", 0)
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.GetBit(context.Background(), "my-key", 0).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.getbit("my-key", 0);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.getbit("my-key", 0)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# Bitmap commands
+Source: https://upstash.com/docs/redis/commands/bitmap/overview
+
+<CardGroup cols={2}>
+<Card title="BITCOUNT" href="/redis/commands/bitmap/bitcount">Count set bits in a string</Card>
+<Card title="BITFIELD" href="/redis/commands/bitmap/bitfield">Perform arbitrary bitfield operations</Card>
+<Card title="BITFIELD_RO" href="/redis/commands/bitmap/bitfield-ro">Read-only bitfield operations</Card>
+<Card title="BITOP" href="/redis/commands/bitmap/bitop">Perform bitwise operations between strings</Card>
+<Card title="BITPOS" href="/redis/commands/bitmap/bitpos">Find first bit set or clear in a string</Card>
+<Card title="GETBIT" href="/redis/commands/bitmap/getbit">Get the bit value at offset</Card>
+<Card title="SETBIT" href="/redis/commands/bitmap/setbit">Set or clear the bit at offset</Card>
+</CardGroup>
+
+# SETBIT
+Source: https://upstash.com/docs/redis/commands/bitmap/setbit
+
+Use `SETBIT` to set or clear the bit at offset.
+
+## Syntax
+
+```redis
+SETBIT <key> <offset> <value>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<offset>` | Yes | No | Zero-based bit offset to write. |
+| `<value>` | Yes | No | Bit value to write: `0` or `1`. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer: the previous bit at the offset, `0` or `1` |
+| RESP3 | Integer: the previous bit at the offset, `0` or `1` |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const originalBit = await redis.setbit(key, 4, 1);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.setbit("my-key", 0, 1)
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.setbit("my-key", "0", "1");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.setBit("my-key", 0, 1);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.setbit("my-key", 0, 1)
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.SetBit(context.Background(), "my-key", 0, 1).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.setbit("my-key", 0, true);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.setbit("my-key", 0, true)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# AUTH
+Source: https://upstash.com/docs/redis/commands/connection/auth
+
+Use `AUTH` to authenticate to the server.
+
+## Syntax
+
+```redis
+AUTH [<username>] <password>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<username>` | No | No | Username to authenticate as. |
+| `<password>` | Yes | No | Password to authenticate with. |
+
+## Important points
+
+* This is a connection-oriented command and is available over native Redis TCP, not the stateless REST endpoint.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Simple string `OK` |
+| RESP3 | Simple string `OK` |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.auth("password");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.auth({ password: "password" });
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.auth("password")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.Do(context.Background(), "AUTH", "password").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.auth("password");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("AUTH");
+    command.arg("password");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# CLIENT GETNAME
+Source: https://upstash.com/docs/redis/commands/connection/client-getname
+
+Use `CLIENT GETNAME` to get the current connection name.
+
+## Syntax
+
+```redis
+CLIENT GETNAME
+```
+
+## Arguments
+
+This command takes no arguments.
+
+## Important points
+
+* This is a connection-oriented command and is available over native Redis TCP, not the stateless REST endpoint.
+* This command can expose administrative information or make a broad destructive change. Restrict it to trusted code paths.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Null bulk string or null array or Bulk string |
+| RESP3 | Null or Bulk string |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.client("GETNAME");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.clientGetName();
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.client_getname()
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ClientGetName(context.Background()).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.clientGetname();
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("CLIENT");
+    command.arg("GETNAME");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# CLIENT ID
+Source: https://upstash.com/docs/redis/commands/connection/client-id
+
+Use `CLIENT ID` to get the current client ID.
+
+## Syntax
+
+```redis
+CLIENT ID
+```
+
+## Arguments
+
+This command takes no arguments.
+
+## Important points
+
+* This is a connection-oriented command and is available over native Redis TCP, not the stateless REST endpoint.
+* This command can expose administrative information or make a broad destructive change. Restrict it to trusted code paths.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.client("ID");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.clientId();
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.client_id()
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ClientID(context.Background()).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.clientId();
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("CLIENT");
+    command.arg("ID");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# CLIENT INFO
+Source: https://upstash.com/docs/redis/commands/connection/client-info
+
+Use `CLIENT INFO` to get info about current connection.
+
+## Syntax
+
+```redis
+CLIENT INFO
+```
+
+## Arguments
+
+This command takes no arguments.
+
+## Important points
+
+* This is a connection-oriented command and is available over native Redis TCP, not the stateless REST endpoint.
+* This command can expose administrative information or make a broad destructive change. Restrict it to trusted code paths.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Bulk string |
+| RESP3 | Bulk string |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.client("INFO");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.clientInfo();
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.client_info()
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ClientInfo(context.Background()).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.clientInfo();
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("CLIENT");
+    command.arg("INFO");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# CLIENT LIST
+Source: https://upstash.com/docs/redis/commands/connection/client-list
+
+Use `CLIENT LIST` to list all client connections.
+
+## Syntax
+
+```redis
+CLIENT LIST
+```
+
+## Arguments
+
+This command takes no arguments.
+
+## Important points
+
+* This is a connection-oriented command and is available over native Redis TCP, not the stateless REST endpoint.
+* This command can expose administrative information or make a broad destructive change. Restrict it to trusted code paths.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Bulk string |
+| RESP3 | Bulk string |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.client("LIST");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.clientList();
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.client_list()
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ClientList(context.Background()).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.clientList();
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("CLIENT");
+    command.arg("LIST");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# CLIENT SETINFO
+Source: https://upstash.com/docs/redis/commands/connection/client-setinfo
+
+Use `CLIENT SETINFO` to set client connection attributes.
+
+## Syntax
+
+```redis
+CLIENT SETINFO <LIB-NAME | LIB-VER> <value>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `LIB-NAME \| LIB-VER` | Yes | No | Attribute to update: the client library name or version. |
+| `value` | Yes | No | Value to store for the selected client attribute. |
+
+## Important points
+
+* This is a connection-oriented command and is available over native Redis TCP, not the stateless REST endpoint.
+* This command can expose administrative information or make a broad destructive change. Restrict it to trusted code paths.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Simple string `OK` |
+| RESP3 | Simple string `OK` |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.call("CLIENT", "SETINFO", "LIB-NAME", "my-client");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.sendCommand(["CLIENT", "SETINFO", "LIB-NAME", "my-client"]);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.client_setinfo("LIB-NAME", "my-client")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.Do(context.Background(), "CLIENT", "SETINFO", "LIB-NAME", "my-client").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.clientSetInfo(redis.clients.jedis.args.ClientAttributeOption.LIB_NAME, "my-client");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("CLIENT");
+    command.arg("SETINFO");
+    command.arg("LIB-NAME");
+    command.arg("my-client");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# CLIENT SETNAME
+Source: https://upstash.com/docs/redis/commands/connection/client-setname
+
+Use `CLIENT SETNAME` to set the connection name.
+
+## Syntax
+
+```redis
+CLIENT SETNAME <connection-name>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `connection-name` | Yes | No | Name to associate with this TCP connection. |
+
+## Important points
+
+* This is a connection-oriented command and is available over native Redis TCP, not the stateless REST endpoint.
+* This command can expose administrative information or make a broad destructive change. Restrict it to trusted code paths.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Simple string `OK` |
+| RESP3 | Simple string `OK` |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.client("SETNAME", "worker-1");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.clientSetName("worker-1");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.client_setname("worker-1")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.Do(context.Background(), "CLIENT", "SETNAME", "worker-1").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.clientSetname("worker-1");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("CLIENT");
+    command.arg("SETNAME");
+    command.arg("worker-1");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# ECHO
+Source: https://upstash.com/docs/redis/commands/connection/echo
+
+Use `ECHO` to echo the given string.
+
+## Syntax
+
+```redis
+ECHO <message>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<message>` | Yes | No | Message payload. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Bulk string |
+| RESP3 | Bulk string |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const response = await redis.echo("hello world");
+console.log(response); // "hello world"
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.echo("hello")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.echo("hello");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.echo("hello");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.echo("hello")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.Echo(context.Background(), "hello").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.echo("hello");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("ECHO");
+    command.arg("hello");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# HELLO
+Source: https://upstash.com/docs/redis/commands/connection/hello
+
+Use `HELLO` to handshake with Redis protocol.
+
+## Syntax
+
+```redis
+HELLO [<protover> [AUTH <username> <password>] [SETNAME <clientname>]]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<protover> [AUTH <username> <password>] [SETNAME <clientname>]` | No | No | Protocol version to switch to, optionally with credentials and a connection name. |
+
+## Important points
+
+* This is a connection-oriented command and is available over native Redis TCP, not the stateless REST endpoint.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Flat array of alternating keys and values |
+| RESP3 | Map |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.hello();
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.hello();
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.hello()
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.Do(context.Background(), "HELLO").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+import java.nio.charset.StandardCharsets;
+import redis.clients.jedis.Jedis;
+import redis.clients.jedis.commands.ProtocolCommand;
+
+ProtocolCommand command = () -> "HELLO".getBytes(StandardCharsets.UTF_8);
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.sendCommand(command);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("HELLO");
+
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# Connection commands
+Source: https://upstash.com/docs/redis/commands/connection/overview
+
+<CardGroup cols={2}>
+<Card title="AUTH" href="/redis/commands/connection/auth">Authenticate to the server</Card>
+<Card title="CLIENT GETNAME" href="/redis/commands/connection/client-getname">Get the current connection name</Card>
+<Card title="CLIENT ID" href="/redis/commands/connection/client-id">Get the current client ID</Card>
+<Card title="CLIENT INFO" href="/redis/commands/connection/client-info">Get info about current connection</Card>
+<Card title="CLIENT LIST" href="/redis/commands/connection/client-list">List all client connections</Card>
+<Card title="CLIENT SETINFO" href="/redis/commands/connection/client-setinfo">Set client connection attributes</Card>
+<Card title="CLIENT SETNAME" href="/redis/commands/connection/client-setname">Set the connection name</Card>
+<Card title="ECHO" href="/redis/commands/connection/echo">Echo the given string</Card>
+<Card title="HELLO" href="/redis/commands/connection/hello">Handshake with Redis protocol</Card>
+<Card title="PING" href="/redis/commands/connection/ping">Ping the server</Card>
+<Card title="QUIT" href="/redis/commands/connection/quit">Close the connection</Card>
+<Card title="RESET" href="/redis/commands/connection/reset">Reset the connection</Card>
+<Card title="SELECT" href="/redis/commands/connection/select">Select the database by index</Card>
+</CardGroup>
+
+# PING
+Source: https://upstash.com/docs/redis/commands/connection/ping
+
+Use `PING` to ping the server.
+
+## Syntax
+
+```redis
+PING [<message>]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<message>` | No | No | Message payload. |
+
+## Important points
+
+* Without arguments the reply is `PONG`; with a message, the message is echoed back as a bulk string.
+* While the connection is subscribed under RESP2, `PING` replies with a two-element array holding `pong` and the message instead.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Simple string `PONG`, or the message as a bulk string; a two-element `pong`/message array while subscribed |
+| RESP3 | Simple string `PONG`, or the message as a bulk string |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const response = await redis.ping();
+console.log(response); // "PONG"
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.ping()
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.ping();
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.ping();
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.ping()
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.Ping(context.Background()).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.ping();
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("PING");
+
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# QUIT
+Source: https://upstash.com/docs/redis/commands/connection/quit
+
+Use `QUIT` to close the connection.
+
+## Syntax
+
+```redis
+QUIT
+```
+
+## Arguments
+
+This command takes no arguments.
+
+## Important points
+
+* This is a connection-oriented command and is available over native Redis TCP, not the stateless REST endpoint.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Simple string `OK` |
+| RESP3 | Simple string `OK` |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.quit();
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.sendCommand(["QUIT"]);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.quit()
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.Quit(context.Background()).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+import java.nio.charset.StandardCharsets;
+import redis.clients.jedis.Jedis;
+import redis.clients.jedis.commands.ProtocolCommand;
+
+ProtocolCommand command = () -> "QUIT".getBytes(StandardCharsets.UTF_8);
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.sendCommand(command);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("QUIT");
+
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# RESET
+Source: https://upstash.com/docs/redis/commands/connection/reset
+
+Use `RESET` to reset the connection.
+
+## Syntax
+
+```redis
+RESET
+```
+
+## Arguments
+
+This command takes no arguments.
+
+## Important points
+
+* This is a connection-oriented command and is available over native Redis TCP, not the stateless REST endpoint.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Simple string `RESET` |
+| RESP3 | Simple string `RESET` |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.reset();
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.sendCommand(["RESET"]);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.reset()
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.Do(context.Background(), "RESET").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.reset();
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("RESET");
+
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# SELECT
+Source: https://upstash.com/docs/redis/commands/connection/select
+
+Use `SELECT` to select the database by index.
+
+## Syntax
+
+```redis
+SELECT 0
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `0` | Yes | No | Database index. Upstash supports only database 0. |
+
+## Important points
+
+* Upstash exposes a single logical database. Any index other than `0` returns an error.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Simple string `OK` |
+| RESP3 | Simple string `OK` |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+<Note>
+  This command is not supported yet in `upstash_redis`.
+</Note>
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.select("0");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.sendCommand(["SELECT", "0"]);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.select("0")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.Do(context.Background(), "SELECT", "0").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.select(0);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("SELECT");
+    command.arg("0");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# FCALL
+Source: https://upstash.com/docs/redis/commands/functions/fcall
+
+Use `FCALL` to call a function.
+
+## Syntax
+
+```redis
+FCALL <function> <numkeys> [<key> [<key> ...]] [<arg> [<arg> ...]]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<function>` | Yes | No | Name of the registered function to call. |
+| `<numkeys>` | Yes | No | Number of key arguments that follow. |
+| `<key>` | No | Yes | Redis key targeted by the command. |
+| `<arg>` | No | Yes | Additional argument passed to the function. |
+
+## Important points
+
+* `numkeys` must equal the number of key arguments that immediately follow it; remaining arguments are available to the script or function as ordinary arguments.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Reply returned by the invoked function |
+| RESP3 | Reply returned by the invoked function |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const code = `
+#!lua name=mylib
+redis.register_function('helloworld',
+  function()
+    return 'Hello World!'
+  end
+)
+`;
+
+await redis.functions.load({ code, replace: true });
+
+const res = await redis.functions.call("helloworld");
+console.log(res); // "Hello World!"
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+<Note>
+  This command is not supported yet in `upstash_redis`.
+</Note>
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.fcall("my_function", "1", "my-key", "value");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.fCall("my_function", { keys: ["my-key"], arguments: ["value"] });
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.fcall("my_function", 1, "my-key", "value")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.FCall(context.Background(), "my_function", []string{"my-key"}, "value").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.fcall("my_function", java.util.List.of("my-key"), java.util.List.of("value"));
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("FCALL");
+    command.arg("my_function");
+    command.arg("1");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# FCALL_RO
+Source: https://upstash.com/docs/redis/commands/functions/fcall-ro
+
+Use `FCALL_RO` to call a read-only function.
+
+## Syntax
+
+```redis
+FCALL_RO <function> <numkeys> [<key> [<key> ...]] [<arg> [<arg> ...]]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<function>` | Yes | No | Name of the registered function to call. |
+| `<numkeys>` | Yes | No | Number of key arguments that follow. |
+| `<key>` | No | Yes | Redis key targeted by the command. |
+| `<arg>` | No | Yes | Additional argument passed to the function. |
+
+## Important points
+
+* `numkeys` must equal the number of key arguments that immediately follow it; remaining arguments are available to the script or function as ordinary arguments.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Reply returned by the invoked read-only function |
+| RESP3 | Reply returned by the invoked read-only function |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const code = `
+#!lua name=ro_lib
+
+local function get_value(keys, args)
+  return redis.call('GET', keys[1])
+end
+
+redis.register_function({
+  function_name='get_value',
+  callback=get_value,
+  flags={ 'no-writes' }
+})
+`;
+
+await redis.functions.load({ code, replace: true });
+
+// Call the read-only function
+// Note: We can modify the keys usage here, but since it represents a read-only operation
+// and we marked it with 'no-writes', it is safe to use callRo.
+const value = await redis.functions.callRo("get_value", ["mykey"])
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+<Note>
+  This command is not supported yet in `upstash_redis`.
+</Note>
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.fcall_ro("my_function", "1", "my-key", "value");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.fCallRo("my_function", { keys: ["my-key"], arguments: ["value"] });
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.fcall_ro("my_function", 1, "my-key", "value")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.FCallRO(context.Background(), "my_function", []string{"my-key"}, "value").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.fcallReadonly("my_function", java.util.List.of("my-key"), java.util.List.of("value"));
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("FCALL_RO");
+    command.arg("my_function");
+    command.arg("1");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# FUNCTION DELETE
+Source: https://upstash.com/docs/redis/commands/functions/function-delete
+
+Use `FUNCTION DELETE` to delete a library.
+
+## Syntax
+
+```redis
+FUNCTION DELETE <library-name>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<library-name>` | Yes | No | Name of the function library. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Simple string `OK` |
+| RESP3 | Simple string `OK` |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.functions.delete("mylib")
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+<Note>
+  This command is not supported yet in `upstash_redis`.
+</Note>
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.function("DELETE", "library-name");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.functionDelete("library-name");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.function_delete("library-name")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.FunctionDelete(context.Background(), "library-name").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.functionDelete("library-name");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("FUNCTION");
+    command.arg("DELETE");
+    command.arg("library-name");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# FUNCTION FLUSH
+Source: https://upstash.com/docs/redis/commands/functions/function-flush
+
+Use `FUNCTION FLUSH` to delete all libraries.
+
+## Syntax
+
+```redis
+FUNCTION FLUSH [ASYNC | SYNC]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `(ASYNC \| SYNC)` | No | No | Choose one form: `ASYNC` (request asynchronous cleanup); `SYNC` (request synchronous cleanup). |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Simple string `OK` |
+| RESP3 | Simple string `OK` |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.functions.flush()
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+<Note>
+  This command is not supported yet in `upstash_redis`.
+</Note>
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.function("FLUSH");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.functionFlush();
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.function_flush()
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.FunctionFlush(context.Background()).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.functionFlush();
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("FUNCTION");
+    command.arg("FLUSH");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# FUNCTION KILL
+Source: https://upstash.com/docs/redis/commands/functions/function-kill
+
+Use `FUNCTION KILL` to kill a running function.
+
+## Syntax
+
+```redis
+FUNCTION KILL
+```
+
+## Arguments
+
+This command takes no arguments.
+
+## Important points
+
+* The current deployment recognizes this command but reports `NOTBUSY` because it does not expose an interruptible running-function state.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Error reply (`NOTBUSY` on the current deployment) |
+| RESP3 | Error reply (`NOTBUSY` on the current deployment) |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+<Note>
+  This command is not supported yet in `upstash_redis`.
+</Note>
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.function("KILL");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.functionKill();
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.function_kill()
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.FunctionKill(context.Background()).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.functionKill();
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("FUNCTION");
+    command.arg("KILL");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# FUNCTION LIST
+Source: https://upstash.com/docs/redis/commands/functions/function-list
+
+Use `FUNCTION LIST` to list all libraries.
+
+## Syntax
+
+```redis
+FUNCTION LIST [LIBRARYNAME <library-name-pattern>] [WITHCODE]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `LIBRARYNAME <library-name-pattern>` | No | No | Return only libraries whose name matches this pattern. |
+| `WITHCODE` | No | No | Include each library's source code. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of flat arrays containing library metadata |
+| RESP3 | Array of maps containing library metadata |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const libs = await redis.functions.list({
+    libraryName: "mylib",
+    withCode: true
+})
+
+console.log(libs)
+// [
+//   {
+//     libraryName: "mylib",
+//     engine: "LUA",
+//     functions: [{
+//       name: "my_func",
+//       description: null,
+//       flags: [ "no-writes" ]
+//     }],
+//     libraryCode: "#!lua name=mylib ..."
+//   }
+// ]
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+<Note>
+  This command is not supported yet in `upstash_redis`.
+</Note>
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.function("LIST");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.functionList();
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.function_list()
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.FunctionList(context.Background(), redis.FunctionListQuery{}).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.functionList();
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("FUNCTION");
+    command.arg("LIST");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# FUNCTION LOAD
+Source: https://upstash.com/docs/redis/commands/functions/function-load
+
+Use `FUNCTION LOAD` to load a library.
+
+## Syntax
+
+```redis
+FUNCTION LOAD [REPLACE] <function-code>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `REPLACE` | No | No | Allow replacement of an existing destination. |
+| `<function-code>` | Yes | No | Library source, including its `#!lua name=<library>` shebang. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Bulk string |
+| RESP3 | Bulk string |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const code = `#!lua name=mylib
+
+  -- Simple function that returns a string
+  redis.register_function(
+    'helloworld',
+    function() return 'Hello World!' end
+  )
+
+  -- Complex function that modifies data with logic
+  local function my_hset(keys, args)
+    local hash = keys[1]
+    local time = redis.call('TIME')[1]
+    return redis.call('HSET', hash, '_last_modified_', time, unpack(args))
+  end
+
+  redis.register_function('my_hset', my_hset)
+`;
+
+const libraryName = await redis.functions.load({ code, replace: true });
+
+console.log(libraryName); // "mylib"
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+<Note>
+  This command is not supported yet in `upstash_redis`.
+</Note>
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.function("LOAD", "function-code");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.functionLoad("function-code");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.function_load("function-code")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.FunctionLoad(context.Background(), "function-code").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.functionLoad("function-code");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("FUNCTION");
+    command.arg("LOAD");
+    command.arg("function-code");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# FUNCTION STATS
+Source: https://upstash.com/docs/redis/commands/functions/function-stats
+
+Use `FUNCTION STATS` to get function execution stats.
+
+## Syntax
+
+```redis
+FUNCTION STATS
+```
+
+## Arguments
+
+This command takes no arguments.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Flat array of alternating keys and values |
+| RESP3 | Map |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const stats = await redis.functions.stats()
+
+console.log(stats)
+// {
+//   engines: {
+//     LUA: {
+//       librariesCount: 3,
+//       functionsCount: 15
+//     }
+//   }
+// }
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+<Note>
+  This command is not supported yet in `upstash_redis`.
+</Note>
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.function("STATS");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.functionStats();
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.function_stats()
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.FunctionStats(context.Background()).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.functionStats();
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("FUNCTION");
+    command.arg("STATS");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# Functions commands
+Source: https://upstash.com/docs/redis/commands/functions/overview
+
+<CardGroup cols={2}>
+<Card title="FCALL" href="/redis/commands/functions/fcall">Call a function</Card>
+<Card title="FCALL_RO" href="/redis/commands/functions/fcall-ro">Call a read-only function</Card>
+<Card title="FUNCTION DELETE" href="/redis/commands/functions/function-delete">Delete a library</Card>
+<Card title="FUNCTION FLUSH" href="/redis/commands/functions/function-flush">Delete all libraries</Card>
+<Card title="FUNCTION KILL" href="/redis/commands/functions/function-kill">Kill a running function</Card>
+<Card title="FUNCTION LIST" href="/redis/commands/functions/function-list">List all libraries</Card>
+<Card title="FUNCTION LOAD" href="/redis/commands/functions/function-load">Load a library</Card>
+<Card title="FUNCTION STATS" href="/redis/commands/functions/function-stats">Get function execution stats</Card>
+</CardGroup>
+
+# COPY
+Source: https://upstash.com/docs/redis/commands/generic/copy
+
+Use `COPY` to copy a key to another key.
+
+## Syntax
+
+```redis
+COPY <source> <destination> [DB <destination-db>] [REPLACE]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<source>` | Yes | No | Redis key used as source. |
+| `<destination>` | Yes | No | Redis key used as destination. |
+| `DB <destination-db>` | No | No | Index of the database to copy the key into. |
+| `REPLACE` | No | No | Allow replacement of an existing destination. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer: `1` if the key was copied, `0` otherwise |
+| RESP3 | Integer: `1` if the key was copied, `0` otherwise |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+const result = await redis.copy("source-key", "destination-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.copy("source-key", "destination-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.copy("source-key", "destination-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.copy("source-key", "destination-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.copy("source-key", "destination-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.Copy(context.Background(), "source-key", "destination-key", 0, false).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.copy("source-key", "destination-key", false);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.copy("source-key", "destination-key", redis::CopyOptions::default())?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# DEL
+Source: https://upstash.com/docs/redis/commands/generic/del
+
+Use `DEL` to delete one or more keys.
+
+## Syntax
+
+```redis
+DEL <key> [<key> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | Yes | Redis key targeted by the command. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.del("key1", "key2");
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.delete("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.del("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.del("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.delete("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.Del(context.Background(), "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.del("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.del("my-key")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# DUMP
+Source: https://upstash.com/docs/redis/commands/generic/dump
+
+Use `DUMP` to serialize a key's value.
+
+## Syntax
+
+```redis
+DUMP <key>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Bulk string or Null bulk string or null array |
+| RESP3 | Bulk string or Null |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+<Note>
+  This command is not supported yet in `upstash_redis`.
+</Note>
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.dump("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.dump("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.dump("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.Dump(context.Background(), "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.dump("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("DUMP");
+    command.arg("my-key");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# EXISTS
+Source: https://upstash.com/docs/redis/commands/generic/exists
+
+Use `EXISTS` to check if keys exist.
+
+## Syntax
+
+```redis
+EXISTS <key> [<key> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | Yes | Redis key targeted by the command. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.set("key1", "value1")
+await redis.set("key2", "value2")
+const keys = await redis.exists("key1", "key2", "key3");
+console.log(keys) // 2
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.exists("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.exists("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.exists("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.exists("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.Exists(context.Background(), "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.exists("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.exists("my-key")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# EXPIRE
+Source: https://upstash.com/docs/redis/commands/generic/expire
+
+Use `EXPIRE` to set a key's TTL in seconds.
+
+## Syntax
+
+```redis
+EXPIRE <key> <seconds> [NX | XX | GT | LT]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<seconds>` | Yes | No | Lifetime in seconds. |
+| `(NX \| XX \| GT \| LT)` | No | No | Choose one form: `NX` (only when the key has no expiration); `XX` (only when the key already has one); `GT` (only when the new expiration is later than the current one); `LT` (only when it is earlier). |
+
+## Important points
+
+* `NX` cannot be combined with `XX`, `GT`, or `LT`, and `GT` and `LT` cannot be used together.
+* A key with no expiration counts as an infinite one, so `GT` never sets an expiration on such a key and `LT` always does.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer: `1` if the timeout was set, `0` otherwise |
+| RESP3 | Integer: `1` if the timeout was set, `0` otherwise |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.set("mykey", "Hello");
+await redis.expire("mykey", 10);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.expire("my-key", 1000)
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.expire("my-key", "1000");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.expire("my-key", 1000);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.expire("my-key", 1000)
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+    "time"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.Expire(context.Background(), "my-key", 1000*time.Second).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.expire("my-key", 1000);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.expire("my-key", 1000)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# EXPIREAT
+Source: https://upstash.com/docs/redis/commands/generic/expireat
+
+Use `EXPIREAT` to set expiry as Unix timestamp.
+
+## Syntax
+
+```redis
+EXPIREAT <key> <unix-time-seconds> [NX | XX | GT | LT]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<unix-time-seconds>` | Yes | No | Expiration time as a Unix timestamp in seconds. |
+| `(NX \| XX \| GT \| LT)` | No | No | Choose one form: `NX` (only when the key has no expiration); `XX` (only when the key already has one); `GT` (only when the new expiration is later than the current one); `LT` (only when it is earlier). |
+
+## Important points
+
+* `NX` cannot be combined with `XX`, `GT`, or `LT`, and `GT` and `LT` cannot be used together.
+* A key with no expiration counts as an infinite one, so `GT` never sets an expiration on such a key and `LT` always does.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer: `1` if the timeout was set, `0` otherwise |
+| RESP3 | Integer: `1` if the timeout was set, `0` otherwise |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.set("mykey", "Hello");
+const tenSecondsFromNow = Math.floor(Date.now() / 1000) + 10;
+await redis.expireat("mykey", tenSecondsFromNow);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.expireat("my-key", 1735689600)
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.expireat("my-key", "1735689600");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.expireAt("my-key", 1735689600);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.expireat("my-key", 1735689600)
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+    "time"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ExpireAt(context.Background(), "my-key", time.Unix(1735689600, 0)).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.expireAt("my-key", 1735689600);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.expire_at("my-key", 1735689600)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# EXPIRETIME
+Source: https://upstash.com/docs/redis/commands/generic/expiretime
+
+Use `EXPIRETIME` to get expiry as Unix timestamp.
+
+## Syntax
+
+```redis
+EXPIRETIME <key>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+
+## Important points
+
+* Negative integer replies are sentinel values, not durations or timestamps; see the response description for missing or persistent data.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer: expiration Unix time in seconds, `-1` if the key has no expiration, `-2` if the key does not exist |
+| RESP3 | Integer: expiration Unix time in seconds, `-1` if the key has no expiration, `-2` if the key does not exist |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+<Note>
+  This command is not supported yet in `upstash_redis`.
+</Note>
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.expiretime("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.expireTime("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.expiretime("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ExpireTime(context.Background(), "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.expireTime("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.expire_time("my-key")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# KEYS
+Source: https://upstash.com/docs/redis/commands/generic/keys
+
+Use `KEYS` to find keys matching a pattern.
+
+## Syntax
+
+```redis
+KEYS <pattern>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<pattern>` | Yes | No | Glob-style pattern to match keys against. |
+
+## Important points
+
+* This command can expose administrative information or make a broad destructive change. Restrict it to trusted code paths.
+* This operation can inspect a large part of the database. Prefer cursor-based scans where possible and avoid unbounded use on hot paths.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of bulk-string keys |
+| RESP3 | Array of bulk-string keys |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const keys = await redis.keys("prefix*");
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.keys("*")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.keys("*");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.keys("*");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.keys("*")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.Keys(context.Background(), "*").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.keys("*");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.keys("*")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# MEMORY USAGE
+Source: https://upstash.com/docs/redis/commands/generic/memory-usage
+
+Use `MEMORY USAGE` to estimate memory used by a key.
+
+## Syntax
+
+```redis
+MEMORY USAGE <key> [SAMPLES <count>]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `key` | Yes | No | Key whose in-memory footprint should be estimated. |
+| `SAMPLES count` | No | No | Sampling count used when estimating large stream values. |
+
+## Important points
+
+* The result is an estimate in bytes and can change as the internal representation changes.
+* A missing key returns null. The sampling count is clamped to the deployment's supported range.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer or Null bulk string or null array |
+| RESP3 | Integer or Null |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+<Note>
+  This command is not supported yet in `upstash_redis`.
+</Note>
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.memory("USAGE", "my-key", "SAMPLES", "10");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.memoryUsage("my-key", { SAMPLES: 10 });
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.memory_usage("my-key", samples=10)
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.MemoryUsage(context.Background(), "my-key", 10).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.memoryUsage("my-key", 10);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("MEMORY");
+    command.arg("USAGE");
+    command.arg("my-key");
+    command.arg("SAMPLES");
+    command.arg("10");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# Generic commands
+Source: https://upstash.com/docs/redis/commands/generic/overview
+
+<CardGroup cols={2}>
+<Card title="COPY" href="/redis/commands/generic/copy">Copy a key to another key</Card>
+<Card title="DEL" href="/redis/commands/generic/del">Delete one or more keys</Card>
+<Card title="DUMP" href="/redis/commands/generic/dump">Serialize a key's value</Card>
+<Card title="EXISTS" href="/redis/commands/generic/exists">Check if keys exist</Card>
+<Card title="EXPIRE" href="/redis/commands/generic/expire">Set a key's TTL in seconds</Card>
+<Card title="EXPIREAT" href="/redis/commands/generic/expireat">Set expiry as Unix timestamp</Card>
+<Card title="EXPIRETIME" href="/redis/commands/generic/expiretime">Get expiry as Unix timestamp</Card>
+<Card title="KEYS" href="/redis/commands/generic/keys">Find keys matching a pattern</Card>
+<Card title="MEMORY USAGE" href="/redis/commands/generic/memory-usage">Estimate memory used by a key</Card>
+<Card title="PERSIST" href="/redis/commands/generic/persist">Remove the expiration from a key</Card>
+<Card title="PEXPIRE" href="/redis/commands/generic/pexpire">Set a key's TTL in milliseconds</Card>
+<Card title="PEXPIREAT" href="/redis/commands/generic/pexpireat">Set expiry as Unix ms timestamp</Card>
+<Card title="PEXPIRETIME" href="/redis/commands/generic/pexpiretime">Get expiry as Unix ms timestamp</Card>
+<Card title="PTTL" href="/redis/commands/generic/pttl">Get TTL in milliseconds</Card>
+<Card title="RANDOMKEY" href="/redis/commands/generic/randomkey">Return a random key</Card>
+<Card title="RENAME" href="/redis/commands/generic/rename">Rename a key</Card>
+<Card title="RENAMENX" href="/redis/commands/generic/renamenx">Rename a key if new key doesn't exist</Card>
+<Card title="RESTORE" href="/redis/commands/generic/restore">Deserialize and restore a key</Card>
+<Card title="SCAN" href="/redis/commands/generic/scan">Incrementally iterate keys</Card>
+<Card title="TOUCH" href="/redis/commands/generic/touch">Update last access time of keys</Card>
+<Card title="TTL" href="/redis/commands/generic/ttl">Get TTL in seconds</Card>
+<Card title="TYPE" href="/redis/commands/generic/type">Get the type of a key</Card>
+<Card title="UNLINK" href="/redis/commands/generic/unlink">Delete keys asynchronously</Card>
+<Card title="WAIT" href="/redis/commands/generic/wait">Wait for replica acknowledgements</Card>
+<Card title="WAITAOF" href="/redis/commands/generic/waitaof">Wait for local and replica persistence</Card>
+</CardGroup>
+
+# PERSIST
+Source: https://upstash.com/docs/redis/commands/generic/persist
+
+Use `PERSIST` to remove the expiration from a key.
+
+## Syntax
+
+```redis
+PERSIST <key>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer: `1` if the timeout was removed, `0` otherwise |
+| RESP3 | Integer: `1` if the timeout was removed, `0` otherwise |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.persist(key);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.persist("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.persist("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.persist("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.persist("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.Persist(context.Background(), "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.persist("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.persist("my-key")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# PEXPIRE
+Source: https://upstash.com/docs/redis/commands/generic/pexpire
+
+Use `PEXPIRE` to set a key's TTL in milliseconds.
+
+## Syntax
+
+```redis
+PEXPIRE <key> <milliseconds> [NX | XX | GT | LT]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<milliseconds>` | Yes | No | Lifetime in milliseconds. |
+| `(NX \| XX \| GT \| LT)` | No | No | Choose one form: `NX` (only when the key has no expiration); `XX` (only when the key already has one); `GT` (only when the new expiration is later than the current one); `LT` (only when it is earlier). |
+
+## Important points
+
+* `NX` cannot be combined with `XX`, `GT`, or `LT`, and `GT` and `LT` cannot be used together.
+* A key with no expiration counts as an infinite one, so `GT` never sets an expiration on such a key and `LT` always does.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer: `1` if the timeout was set, `0` otherwise |
+| RESP3 | Integer: `1` if the timeout was set, `0` otherwise |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.pexpire(key, 60_000); // 1 minute
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.pexpire("my-key", 1000)
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.pexpire("my-key", "1000");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.pExpire("my-key", 1000);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.pexpire("my-key", 1000)
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+    "time"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.PExpire(context.Background(), "my-key", time.Second).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.pexpire("my-key", 1000);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.pexpire("my-key", 1000)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# PEXPIREAT
+Source: https://upstash.com/docs/redis/commands/generic/pexpireat
+
+Use `PEXPIREAT` to set expiry as Unix ms timestamp.
+
+## Syntax
+
+```redis
+PEXPIREAT <key> <unix-time-milliseconds> [NX | XX | GT | LT]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<unix-time-milliseconds>` | Yes | No | Expiration time as a Unix timestamp in milliseconds. |
+| `(NX \| XX \| GT \| LT)` | No | No | Choose one form: `NX` (only when the key has no expiration); `XX` (only when the key already has one); `GT` (only when the new expiration is later than the current one); `LT` (only when it is earlier). |
+
+## Important points
+
+* `NX` cannot be combined with `XX`, `GT`, or `LT`, and `GT` and `LT` cannot be used together.
+* A key with no expiration counts as an infinite one, so `GT` never sets an expiration on such a key and `LT` always does.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer: `1` if the timeout was set, `0` otherwise |
+| RESP3 | Integer: `1` if the timeout was set, `0` otherwise |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.set("mykey", "Hello");
+const tenMinutesFromNow = Date.now() + 10 * 60 * 1000;
+await redis.pexpireat("mykey", tenMinutesFromNow);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.pexpireat("my-key", 1735689600)
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.pexpireat("my-key", "1735689600");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.pExpireAt("my-key", 1735689600);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.pexpireat("my-key", 1735689600)
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+    "time"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.PExpireAt(context.Background(), "my-key", time.UnixMilli(1735689600)).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.pexpireAt("my-key", 1735689600);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.pexpire_at("my-key", 1735689600)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# PEXPIRETIME
+Source: https://upstash.com/docs/redis/commands/generic/pexpiretime
+
+Use `PEXPIRETIME` to get expiry as Unix ms timestamp.
+
+## Syntax
+
+```redis
+PEXPIRETIME <key>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+
+## Important points
+
+* Negative integer replies are sentinel values, not durations or timestamps; see the response description for missing or persistent data.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer: expiration Unix time in milliseconds, `-1` if the key has no expiration, `-2` if the key does not exist |
+| RESP3 | Integer: expiration Unix time in milliseconds, `-1` if the key has no expiration, `-2` if the key does not exist |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+<Note>
+  This command is not supported yet in `upstash_redis`.
+</Note>
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.pexpiretime("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.pExpireTime("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.pexpiretime("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.PExpireTime(context.Background(), "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.pexpireTime("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.pexpire_time("my-key")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# PTTL
+Source: https://upstash.com/docs/redis/commands/generic/pttl
+
+Use `PTTL` to get TTL in milliseconds.
+
+## Syntax
+
+```redis
+PTTL <key>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+
+## Important points
+
+* Negative integer replies are sentinel values, not durations or timestamps; see the response description for missing or persistent data.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer: remaining lifetime in milliseconds, `-1` if the key has no expiration, `-2` if the key does not exist |
+| RESP3 | Integer: remaining lifetime in milliseconds, `-1` if the key has no expiration, `-2` if the key does not exist |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const millis = await redis.pttl(key);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.pttl("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.pttl("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.pTTL("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.pttl("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.PTTL(context.Background(), "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.pttl("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.pttl("my-key")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# RANDOMKEY
+Source: https://upstash.com/docs/redis/commands/generic/randomkey
+
+Use `RANDOMKEY` to return a random key.
+
+## Syntax
+
+```redis
+RANDOMKEY
+```
+
+## Arguments
+
+This command takes no arguments.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Null bulk string or null array or Bulk string |
+| RESP3 | Null or Bulk string |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const key = await redis.randomkey();
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.randomkey()
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.randomkey();
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.randomKey();
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.randomkey()
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.RandomKey(context.Background()).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.randomKey();
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("RANDOMKEY");
+
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# RENAME
+Source: https://upstash.com/docs/redis/commands/generic/rename
+
+Use `RENAME` to rename a key.
+
+## Syntax
+
+```redis
+RENAME <key> <newkey>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<newkey>` | Yes | No | Redis key used as newkey. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Simple string `OK` |
+| RESP3 | Simple string `OK` |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.rename("old", "new");
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.rename("old-key", "new-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.rename("old-key", "new-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.rename("old-key", "new-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.rename("old-key", "new-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.Rename(context.Background(), "old-key", "new-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.rename("old-key", "new-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.rename("old-key", "new-key")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# RENAMENX
+Source: https://upstash.com/docs/redis/commands/generic/renamenx
+
+Use `RENAMENX` to rename a key if new key doesn't exist.
+
+## Syntax
+
+```redis
+RENAMENX <key> <newkey>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<newkey>` | Yes | No | Redis key used as newkey. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer: `1` if the key was renamed, `0` if the destination already exists |
+| RESP3 | Integer: `1` if the key was renamed, `0` if the destination already exists |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const renamed = await redis.renamenx("old", "new");
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.renamenx("old-key", "new-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.renamenx("old-key", "new-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.renameNX("old-key", "new-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.renamenx("old-key", "new-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.RenameNX(context.Background(), "old-key", "new-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.renamenx("old-key", "new-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.rename_nx("old-key", "new-key")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# RESTORE
+Source: https://upstash.com/docs/redis/commands/generic/restore
+
+Use `RESTORE` to deserialize and restore a key.
+
+## Syntax
+
+```redis
+RESTORE <key> <ttl> <serialized-value> [REPLACE] [ABSTTL] [IDLETIME <seconds>] [FREQ <frequency>]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<ttl>` | Yes | No | Lifetime in milliseconds; `0` restores the key without an expiration. |
+| `<serialized-value>` | Yes | No | Payload produced by `DUMP`. |
+| `REPLACE` | No | No | Allow replacement of an existing destination. |
+| `ABSTTL` | No | No | Treat `<ttl>` as an absolute Unix timestamp in milliseconds. |
+| `IDLETIME <seconds>` | No | No | Set the key's idle time, in seconds. |
+| `FREQ <frequency>` | No | No | Set the key's access frequency counter. |
+
+## Important points
+
+* This command can expose administrative information or make a broad destructive change. Restrict it to trusted code paths.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Simple string `OK` |
+| RESP3 | Simple string `OK` |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+<Note>
+  This command is not supported yet in `upstash_redis`.
+</Note>
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.restore("my-key", "1", "serialized-value");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.restore("my-key", 1, "serialized-value");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.restore("my-key", 1, "serialized-value")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+    "time"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.Restore(context.Background(), "my-key", time.Millisecond, "serialized-value").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.restore("my-key", 1, "serialized-value".getBytes());
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("RESTORE");
+    command.arg("my-key");
+    command.arg("1");
+    command.arg("serialized-value");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# SCAN
+Source: https://upstash.com/docs/redis/commands/generic/scan
+
+Use `SCAN` to incrementally iterate keys.
+
+## Syntax
+
+```redis
+SCAN <cursor> [MATCH <pattern>] [COUNT <count>] [TYPE <type>]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<cursor>` | Yes | No | Cursor returned by the previous call; start at `0`. |
+| `MATCH <pattern>` | No | No | Return only elements matching this glob-style pattern. |
+| `COUNT <count>` | No | No | Hint for how much work each iteration should do. |
+| `TYPE <type>` | No | No | Return only keys of this type, such as `string`, `list`, or `hash`. |
+
+## Important points
+
+* This operation can inspect a large part of the database. Prefer cursor-based scans where possible and avoid unbounded use on hot paths.
+* The cursor is opaque. Start with `0` and continue until the server returns cursor `0`; a single iteration may return no elements.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Two-element array: cursor and array of bulk-string keys |
+| RESP3 | Two-element array: cursor and array of bulk-string keys |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const [cursor, keys] = await redis.scan(0, { match: "*" });
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.scan(0)
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.scan("0");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.scan("0");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.scan(0)
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, _, err := client.Scan(context.Background(), 0, "*", 0).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.scan("0");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("SCAN");
+    command.arg("0");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# TOUCH
+Source: https://upstash.com/docs/redis/commands/generic/touch
+
+Use `TOUCH` to update last access time of keys.
+
+## Syntax
+
+```redis
+TOUCH <key> [<key> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | Yes | Redis key targeted by the command. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.touch("key1", "key2", "key3");
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.touch("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.touch("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.touch("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.touch("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.Touch(context.Background(), "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.touch("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("TOUCH");
+    command.arg("my-key");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# TTL
+Source: https://upstash.com/docs/redis/commands/generic/ttl
+
+Use `TTL` to get TTL in seconds.
+
+## Syntax
+
+```redis
+TTL <key>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+
+## Important points
+
+* Negative integer replies are sentinel values, not durations or timestamps; see the response description for missing or persistent data.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer: remaining lifetime in seconds, `-1` if the key has no expiration, `-2` if the key does not exist |
+| RESP3 | Integer: remaining lifetime in seconds, `-1` if the key has no expiration, `-2` if the key does not exist |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const seconds = await redis.ttl(key);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.ttl("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.ttl("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.ttl("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.ttl("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.TTL(context.Background(), "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.ttl("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.ttl("my-key")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# TYPE
+Source: https://upstash.com/docs/redis/commands/generic/type
+
+Use `TYPE` to get the type of a key.
+
+## Syntax
+
+```redis
+TYPE <key>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Simple string: the type name, or `none` if the key does not exist |
+| RESP3 | Simple string: the type name, or `none` if the key does not exist |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.set("key", "value");
+const t = await redis.type("key");
+console.log(t) // "string"
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.type("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.type("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.type("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.type("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.Type(context.Background(), "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.type("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.key_type("my-key")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# UNLINK
+Source: https://upstash.com/docs/redis/commands/generic/unlink
+
+Use `UNLINK` to delete keys asynchronously.
+
+## Syntax
+
+```redis
+UNLINK <key> [<key> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | Yes | Redis key targeted by the command. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.unlink("key1", "key2");
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.unlink("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.unlink("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.unlink("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.unlink("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.Unlink(context.Background(), "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.unlink("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.unlink("my-key")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# WAIT
+Source: https://upstash.com/docs/redis/commands/generic/wait
+
+Use `WAIT` to wait for replica acknowledgements.
+
+## Syntax
+
+```redis
+WAIT <numreplicas> <timeout>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `numreplicas` | Yes | No | Non-negative number of replicas that should acknowledge prior writes on this connection. |
+| `timeout` | Yes | No | Maximum wait in milliseconds; `0` means no timeout. |
+
+## Important points
+
+* This deployment waits for writes enqueued before `WAIT` begins, including writes from other connections. That is broader than the per-connection wording used by Redis clients.
+* The reply can be lower than `numreplicas` when the timeout expires. This improves observed replication durability but does not make Redis a strongly consistent store.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+<Note>
+  This command is not supported yet in `upstash_redis`.
+</Note>
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.wait("1", "1000");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.wait(1, 1000);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.wait("1", "1000")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+    "time"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.Wait(context.Background(), 1, time.Second).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.waitReplicas(1, 1000);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("WAIT");
+    command.arg("1");
+    command.arg("1000");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# WAITAOF
+Source: https://upstash.com/docs/redis/commands/generic/waitaof
+
+Use `WAITAOF` to wait for local and replica persistence.
+
+## Syntax
+
+```redis
+WAITAOF <numlocal> <numreplicas> <timeout>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `numlocal` | Yes | No | Whether to wait for local persistence: `0` or `1`. |
+| `numreplicas` | Yes | No | Non-negative number of replicas whose append-only files should include prior writes. |
+| `timeout` | Yes | No | Maximum wait in milliseconds; `0` means no timeout. |
+
+## Important points
+
+* This deployment waits for writes enqueued before `WAITAOF` begins, including writes from other connections.
+* The two-element reply contains the local persistence acknowledgement first and the replica persistence count second.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Two-element array of integers: local and replica acknowledgments |
+| RESP3 | Two-element array of integers: local and replica acknowledgments |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+<Note>
+  This command is not supported yet in `upstash_redis`.
+</Note>
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.call("WAITAOF", "1", "1", "1000");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.sendCommand(["WAITAOF", "1", "1", "1000"]);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.waitaof("1", "1", "1000")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+    "time"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.WaitAOF(context.Background(), 1, 1, time.Second).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.waitAOF(1, 1, 1000);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("WAITAOF");
+    command.arg("1");
+    command.arg("1");
+    command.arg("1000");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# GEOADD
+Source: https://upstash.com/docs/redis/commands/geo/geoadd
+
+Use `GEOADD` to add geospatial items.
+
+## Syntax
+
+```redis
+GEOADD <key> [NX | XX] [CH] <longitude> <latitude> <member> [<longitude> <latitude> <member> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `(NX \| XX)` | No | No | Choose one form: `NX` (only add new members, never update an existing one); `XX` (only update members that already exist). |
+| `CH` | No | No | Count changed members rather than only new members. |
+| `<longitude> <latitude> <member>` | Yes | Yes | Longitude, latitude, and the member they belong to. Repeat to add several members. |
+
+## Important points
+
+* `NX` and `XX` are mutually exclusive.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+const result = await redis.geoadd("my-key", {
+  longitude: 29.0,
+  latitude: 41.0,
+  member: "member",
+});
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.geoadd("my-key", (29.0, 41.0, "member"))
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.geoadd("my-key", "29.0", "41.0", "member");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.geoAdd("my-key", { longitude: 29, latitude: 41, member: "member" });
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.geoadd("my-key", (29.0, 41.0, "member"))
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.GeoAdd(context.Background(), "my-key", &redis.GeoLocation{Longitude: 29.0, Latitude: 41.0, Name: "member"}).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.geoadd("my-key", 29.0, 41.0, "member");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("GEOADD");
+    command.arg("my-key");
+    command.arg("29.0");
+    command.arg("41.0");
+    command.arg("member");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# GEODIST
+Source: https://upstash.com/docs/redis/commands/geo/geodist
+
+Use `GEODIST` to get distance between two members.
+
+## Syntax
+
+```redis
+GEODIST <key> <member1> <member2> [m | km | ft | mi]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<member1>` | Yes | No | First member. |
+| `<member2>` | Yes | No | Second member. |
+| `(m \| km \| ft \| mi)` | No | No | Choose one form: `m`; `km`; `ft`; `mi`. |
+
+## Important points
+
+* The distance is always returned as a bulk string, in both RESP2 and RESP3. Client libraries commonly decode it to a language number.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Null bulk string or null array or Bulk string |
+| RESP3 | Null or Bulk string |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+const result = await redis.geodist("my-key", "member1", "member2");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.geodist("my-key", "member1", "member2")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.geodist("my-key", "member1", "member2");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.geoDist("my-key", "member1", "member2");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.geodist("my-key", "member1", "member2")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.GeoDist(context.Background(), "my-key", "member1", "member2", "m").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.geodist("my-key", "member1", "member2");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("GEODIST");
+    command.arg("my-key");
+    command.arg("member1");
+    command.arg("member2");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# GEOHASH
+Source: https://upstash.com/docs/redis/commands/geo/geohash
+
+Use `GEOHASH` to get geohash strings for members.
+
+## Syntax
+
+```redis
+GEOHASH <key> [<member> [<member> ...]]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<member>` | No | Yes | Member name. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of bulk-string geohashes or null values |
+| RESP3 | Array of bulk-string geohashes or null values |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+const result = await redis.geohash("my-key", "member");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.geohash("my-key", "member")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.geohash("my-key", "member");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.geoHash("my-key", "member");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.geohash("my-key", "member")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.GeoHash(context.Background(), "my-key", "member").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.geohash("my-key", "member");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("GEOHASH");
+    command.arg("my-key");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# GEOPOS
+Source: https://upstash.com/docs/redis/commands/geo/geopos
+
+Use `GEOPOS` to get coordinates of members.
+
+## Syntax
+
+```redis
+GEOPOS <key> [<member> [<member> ...]]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<member>` | No | Yes | Member name. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of coordinate-pair arrays or null values |
+| RESP3 | Array of coordinate-pair arrays or null values |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+const result = await redis.geopos("my-key", "member");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.geopos("my-key", "member")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.geopos("my-key", "member");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.geoPos("my-key", "member");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.geopos("my-key", "member")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.GeoPos(context.Background(), "my-key", "member").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.geopos("my-key", "member");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("GEOPOS");
+    command.arg("my-key");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# GEORADIUS
+Source: https://upstash.com/docs/redis/commands/geo/georadius
+
+Use `GEORADIUS` to query members within radius.
+
+## Syntax
+
+```redis
+GEORADIUS <key> <longitude> <latitude> <radius> (m | km | ft | mi) [WITHCOORD] [WITHDIST] [WITHHASH] [COUNT <count> [ANY]] [ASC | DESC] [STORE <storekey> | STOREDIST <storedistkey>]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<longitude>` | Yes | No | Longitude in degrees, from -180 to 180. |
+| `<latitude>` | Yes | No | Latitude in degrees, from -85.05112878 to 85.05112878. |
+| `<radius>` | Yes | No | Search radius, in the unit given after it. |
+| `(m \| km \| ft \| mi)` | Yes | No | Choose one form: `m`; `km`; `ft`; `mi`. |
+| `WITHCOORD` | No | No | Also return the longitude and latitude of each match. |
+| `WITHDIST` | No | No | Also return the distance from the center, in the requested unit. |
+| `WITHHASH` | No | No | Also return the raw 52-bit geohash score of each match. |
+| `COUNT <count> [ANY]` | No | No | Return at most `<count>` matches. `ANY` returns as soon as enough matches are found, instead of sorting every match first. |
+| `(ASC \| DESC)` | No | No | Choose one form: `ASC`; `DESC`. |
+| `(STORE <storekey> \| STOREDIST <storedistkey>)` | No | No | Choose one form: `STORE`; `STOREDIST`. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of bulk-string members or member-detail arrays, or Integer when storing |
+| RESP3 | Array of bulk-string members or member-detail arrays, or Integer when storing |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.georadius("my-key", 29.0, 41.0, 1.5, "M")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.georadius("my-key", "29.0", "41.0", "1.5", "m");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.geoRadius("my-key", { longitude: 29, latitude: 41 }, 1.5, "m");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.georadius("my-key", 29.0, 41.0, 1.5, "m")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.GeoRadius(context.Background(), "my-key", 29.0, 41.0, &redis.GeoRadiusQuery{Radius: 1.5, Unit: "m"}).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.georadius("my-key", 29.0, 41.0, 1.5, redis.clients.jedis.args.GeoUnit.M);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("GEORADIUS");
+    command.arg("my-key");
+    command.arg("29.0");
+    command.arg("41.0");
+    command.arg("1.5");
+    command.arg("m");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# GEORADIUS_RO
+Source: https://upstash.com/docs/redis/commands/geo/georadius-ro
+
+Use `GEORADIUS_RO` to find members within a radius of a point. It is the read-only form of `GEORADIUS`.
+
+## Syntax
+
+```redis
+GEORADIUS_RO <key> <longitude> <latitude> <radius> (m | km | ft | mi) [WITHCOORD] [WITHDIST] [WITHHASH] [COUNT <count> [ANY]] [ASC | DESC]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<longitude>` | Yes | No | Longitude in degrees, from -180 to 180. |
+| `<latitude>` | Yes | No | Latitude in degrees, from -85.05112878 to 85.05112878. |
+| `<radius>` | Yes | No | Search radius, in the unit given after it. |
+| `(m \| km \| ft \| mi)` | Yes | No | Choose one form: `m`; `km`; `ft`; `mi`. |
+| `WITHCOORD` | No | No | Also return the longitude and latitude of each match. |
+| `WITHDIST` | No | No | Also return the distance from the center, in the requested unit. |
+| `WITHHASH` | No | No | Also return the raw 52-bit geohash score of each match. |
+| `COUNT <count> [ANY]` | No | No | Return at most `<count>` matches. `ANY` returns as soon as enough matches are found, instead of sorting every match first. |
+| `(ASC \| DESC)` | No | No | Choose one form: `ASC`; `DESC`. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of bulk-string members or member-detail arrays |
+| RESP3 | Array of bulk-string members or member-detail arrays |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.georadius_ro("my-key", 29.0, 41.0, 1.5, "M")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.georadius_ro("my-key", "29.0", "41.0", "1.5", "m");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.geoRadiusRo("my-key", { longitude: 29, latitude: 41 }, 1.5, "m");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.execute_command("GEORADIUS_RO", "my-key", "29.0", "41.0", "1.5", "m")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.GeoRadius(context.Background(), "my-key", 29.0, 41.0, &redis.GeoRadiusQuery{Radius: 1.5, Unit: "m"}).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.georadiusReadonly("my-key", 29.0, 41.0, 1.5, redis.clients.jedis.args.GeoUnit.M);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("GEORADIUS_RO");
+    command.arg("my-key");
+    command.arg("29.0");
+    command.arg("41.0");
+    command.arg("1.5");
+    command.arg("m");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# GEORADIUSBYMEMBER
+Source: https://upstash.com/docs/redis/commands/geo/georadiusbymember
+
+Use `GEORADIUSBYMEMBER` to radius query centered on member.
+
+## Syntax
+
+```redis
+GEORADIUSBYMEMBER <key> <member> <radius> (m | km | ft | mi) [WITHCOORD] [WITHDIST] [WITHHASH] [COUNT <count> [ANY]] [ASC | DESC] [STORE <storekey> | STOREDIST <storedistkey>]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<member>` | Yes | No | Member name. |
+| `<radius>` | Yes | No | Search radius, in the unit given after it. |
+| `(m \| km \| ft \| mi)` | Yes | No | Choose one form: `m`; `km`; `ft`; `mi`. |
+| `WITHCOORD` | No | No | Also return the longitude and latitude of each match. |
+| `WITHDIST` | No | No | Also return the distance from the center, in the requested unit. |
+| `WITHHASH` | No | No | Also return the raw 52-bit geohash score of each match. |
+| `COUNT <count> [ANY]` | No | No | Return at most `<count>` matches. `ANY` returns as soon as enough matches are found, instead of sorting every match first. |
+| `(ASC \| DESC)` | No | No | Choose one form: `ASC`; `DESC`. |
+| `(STORE <storekey> \| STOREDIST <storedistkey>)` | No | No | Choose one form: `STORE`; `STOREDIST`. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of bulk-string members or member-detail arrays, or Integer when storing |
+| RESP3 | Array of bulk-string members or member-detail arrays, or Integer when storing |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.georadiusbymember("my-key", "member", 1.5, "M")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.georadiusbymember("my-key", "member", "1.5", "m");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.geoRadiusByMember("my-key", "member", 1.5, "m");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.georadiusbymember("my-key", "member", 1.5, "m")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.GeoRadiusByMember(context.Background(), "my-key", "member", &redis.GeoRadiusQuery{Radius: 1.5, Unit: "m"}).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.georadiusByMember("my-key", "member", 1.5, redis.clients.jedis.args.GeoUnit.M);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("GEORADIUSBYMEMBER");
+    command.arg("my-key");
+    command.arg("member");
+    command.arg("1.5");
+    command.arg("m");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# GEORADIUSBYMEMBER_RO
+Source: https://upstash.com/docs/redis/commands/geo/georadiusbymember-ro
+
+Use `GEORADIUSBYMEMBER_RO` to find members within a radius of another member. It is the read-only form of `GEORADIUSBYMEMBER`.
+
+## Syntax
+
+```redis
+GEORADIUSBYMEMBER_RO <key> <member> <radius> (m | km | ft | mi) [WITHCOORD] [WITHDIST] [WITHHASH] [COUNT <count> [ANY]] [ASC | DESC]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<member>` | Yes | No | Member name. |
+| `<radius>` | Yes | No | Search radius, in the unit given after it. |
+| `(m \| km \| ft \| mi)` | Yes | No | Choose one form: `m`; `km`; `ft`; `mi`. |
+| `WITHCOORD` | No | No | Also return the longitude and latitude of each match. |
+| `WITHDIST` | No | No | Also return the distance from the center, in the requested unit. |
+| `WITHHASH` | No | No | Also return the raw 52-bit geohash score of each match. |
+| `COUNT <count> [ANY]` | No | No | Return at most `<count>` matches. `ANY` returns as soon as enough matches are found, instead of sorting every match first. |
+| `(ASC \| DESC)` | No | No | Choose one form: `ASC`; `DESC`. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of bulk-string members or member-detail arrays |
+| RESP3 | Array of bulk-string members or member-detail arrays |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.georadiusbymember_ro("my-key", "member", 1.5, "M")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.georadiusbymember_ro("my-key", "member", "1.5", "m");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.geoRadiusByMemberRo("my-key", "member", 1.5, "m");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.execute_command("GEORADIUSBYMEMBER_RO", "my-key", "member", "1.5", "m")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.GeoRadiusByMember(context.Background(), "my-key", "member", &redis.GeoRadiusQuery{Radius: 1.5, Unit: "m"}).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.georadiusByMemberReadonly("my-key", "member", 1.5, redis.clients.jedis.args.GeoUnit.M);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("GEORADIUSBYMEMBER_RO");
+    command.arg("my-key");
+    command.arg("member");
+    command.arg("1.5");
+    command.arg("m");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# GEOSEARCH
+Source: https://upstash.com/docs/redis/commands/geo/geosearch
+
+Use `GEOSEARCH` to search for members in an area.
+
+## Syntax
+
+```redis
+GEOSEARCH <key> (FROMMEMBER <member> | FROMLONLAT <longitude> <latitude>) (BYRADIUS <radius> (m | km | ft | mi) | BYBOX <width> <height> (m | km | ft | mi)) [ASC | DESC] [COUNT <count> [ANY]] [WITHCOORD] [WITHDIST] [WITHHASH]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `(FROMMEMBER <member> \| FROMLONLAT <longitude> <latitude>)` | Yes | No | Choose one form: `FROMMEMBER`; `FROMLONLAT`. |
+| `(BYRADIUS <radius> (m \| km \| ft \| mi) \| BYBOX <width> <height> (m \| km \| ft \| mi))` | Yes | No | Choose one form: `BYRADIUS`; `m`; `km`; `ft`; `mi`; `BYBOX`; `m`; `km`; `ft`; `mi`. |
+| `(ASC \| DESC)` | No | No | Choose one form: `ASC`; `DESC`. |
+| `COUNT <count> [ANY]` | No | No | Return at most `<count>` matches. `ANY` returns as soon as enough matches are found, instead of sorting every match first. |
+| `WITHCOORD` | No | No | Also return the longitude and latitude of each match. |
+| `WITHDIST` | No | No | Also return the distance from the center, in the requested unit. |
+| `WITHHASH` | No | No | Also return the raw 52-bit geohash score of each match. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of bulk-string members or member-detail arrays |
+| RESP3 | Array of bulk-string members or member-detail arrays |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+const result = await redis.geosearch(
+  "my-key",
+  { type: "FROMMEMBER", member: "member" },
+  { type: "BYRADIUS", radius: 1.5, radiusType: "M" },
+  "ASC",
+);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.geosearch("my-key", member="member", radius=1.5, unit="M")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.geosearch("my-key", "FROMMEMBER", "member", "BYRADIUS", "1.5", "m");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.geoSearch("my-key", "member", { radius: 1.5, unit: "m" });
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.geosearch("my-key", member="member", radius=1.5, unit="m")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.GeoSearch(context.Background(), "my-key", &redis.GeoSearchQuery{Member: "member", Radius: 1.5, RadiusUnit: "m"}).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.geosearch("my-key", "member", 1.5, redis.clients.jedis.args.GeoUnit.M);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("GEOSEARCH");
+    command.arg("my-key");
+    command.arg("member");
+    command.arg("1.5");
+    command.arg("m");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# GEOSEARCHSTORE
+Source: https://upstash.com/docs/redis/commands/geo/geosearchstore
+
+Use `GEOSEARCHSTORE` to store geosearch results.
+
+## Syntax
+
+```redis
+GEOSEARCHSTORE <destination> <source> (FROMMEMBER <member> | FROMLONLAT <longitude> <latitude>) (BYRADIUS <radius> (m | km | ft | mi) | BYBOX <width> <height> (m | km | ft | mi)) [ASC | DESC] [COUNT <count> [ANY]] [STOREDIST]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<destination>` | Yes | No | Redis key used as destination. |
+| `<source>` | Yes | No | Redis key used as source. |
+| `(FROMMEMBER <member> \| FROMLONLAT <longitude> <latitude>)` | Yes | No | Choose one form: `FROMMEMBER`; `FROMLONLAT`. |
+| `(BYRADIUS <radius> (m \| km \| ft \| mi) \| BYBOX <width> <height> (m \| km \| ft \| mi))` | Yes | No | Choose one form: `BYRADIUS`; `m`; `km`; `ft`; `mi`; `BYBOX`; `m`; `km`; `ft`; `mi`. |
+| `(ASC \| DESC)` | No | No | Choose one form: `ASC`; `DESC`. |
+| `COUNT <count> [ANY]` | No | No | Return at most `<count>` matches. `ANY` returns as soon as enough matches are found, instead of sorting every match first. |
+| `STOREDIST` | No | No | Store each match's distance from the center instead of its geohash score. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+const result = await redis.geosearchstore(
+  "destination-key",
+  "source-key",
+  { type: "FROMMEMBER", member: "member" },
+  { type: "BYRADIUS", radius: 1.5, radiusType: "M" },
+  "ASC",
+);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.geosearchstore("destination-key", "source-key", member="member", radius=1.5, unit="M")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.geosearchstore("destination-key", "source-key", "FROMMEMBER", "member", "BYRADIUS", "1.5", "m");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.geoSearchStore("destination-key", "source-key", "member", { radius: 1.5, unit: "m" });
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.geosearchstore("destination-key", "source-key", member="member", radius=1.5, unit="m")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.GeoSearchStore(context.Background(), "source-key", "destination-key", &redis.GeoSearchStoreQuery{GeoSearchQuery: redis.GeoSearchQuery{Member: "member", Radius: 1.5, RadiusUnit: "m"}}).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.geosearchStore("destination-key", "source-key", "member", 1.5, redis.clients.jedis.args.GeoUnit.M);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("GEOSEARCHSTORE");
+    command.arg("destination-key");
+    command.arg("source-key");
+    command.arg("member");
+    command.arg("1.5");
+    command.arg("m");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# Geo commands
+Source: https://upstash.com/docs/redis/commands/geo/overview
+
+<CardGroup cols={2}>
+<Card title="GEOADD" href="/redis/commands/geo/geoadd">Add geospatial items</Card>
+<Card title="GEODIST" href="/redis/commands/geo/geodist">Get distance between two members</Card>
+<Card title="GEOHASH" href="/redis/commands/geo/geohash">Get geohash strings for members</Card>
+<Card title="GEOPOS" href="/redis/commands/geo/geopos">Get coordinates of members</Card>
+<Card title="GEORADIUS" href="/redis/commands/geo/georadius">Query members within radius</Card>
+<Card title="GEORADIUS_RO" href="/redis/commands/geo/georadius-ro">Read-only radius query</Card>
+<Card title="GEORADIUSBYMEMBER" href="/redis/commands/geo/georadiusbymember">Radius query centered on member</Card>
+<Card title="GEORADIUSBYMEMBER_RO" href="/redis/commands/geo/georadiusbymember-ro">Read-only radius query by member</Card>
+<Card title="GEOSEARCH" href="/redis/commands/geo/geosearch">Search for members in an area</Card>
+<Card title="GEOSEARCHSTORE" href="/redis/commands/geo/geosearchstore">Store geosearch results</Card>
+</CardGroup>
+
+# HDEL
+Source: https://upstash.com/docs/redis/commands/hash/hdel
+
+Use `HDEL` to delete one or more hash fields.
+
+## Syntax
+
+```redis
+HDEL <key> <field> [<field> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<field>` | Yes | Yes | Hash field name. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.hdel(key, 'field1', 'field2');
+// returns 5
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.hdel("my-key", "field")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.hdel("my-key", "field");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.hDel("my-key", "field");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.hdel("my-key", "field")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.HDel(context.Background(), "my-key", "field").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.hdel("my-key", "field");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.hdel("my-key", "field")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# HEXISTS
+Source: https://upstash.com/docs/redis/commands/hash/hexists
+
+Use `HEXISTS` to check if a hash field exists.
+
+## Syntax
+
+```redis
+HEXISTS <key> <field>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<field>` | Yes | No | Hash field name. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer: `1` if the field exists, `0` otherwise |
+| RESP3 | Integer: `1` if the field exists, `0` otherwise |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.hset("key", "field", "value");
+const exists = await redis.hexists("key", "field");
+
+console.log(exists); // 1
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.hexists("my-key", "field")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.hexists("my-key", "field");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.hExists("my-key", "field");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.hexists("my-key", "field")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.HExists(context.Background(), "my-key", "field").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.hexists("my-key", "field");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.hexists("my-key", "field")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# HEXPIRE
+Source: https://upstash.com/docs/redis/commands/hash/hexpire
+
+Use `HEXPIRE` to set field TTL in seconds.
+
+## Syntax
+
+```redis
+HEXPIRE <key> <seconds> [NX | XX | GT | LT] FIELDS <numfields> <field> [<field> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<seconds>` | Yes | No | Lifetime in seconds. |
+| `(NX \| XX \| GT \| LT)` | No | No | Choose one form: `NX` (only when the field has no expiration); `XX` (only when the field already has one); `GT` (only when the new expiration is later than the current one); `LT` (only when it is earlier). |
+| `FIELDS <numfields> <field> [<field> ...]` | Yes | No | Fields to target. Give the field count first, then that many field names. |
+
+## Important points
+
+* `NX` cannot be combined with `XX`, `GT`, or `LT`, and `GT` and `LT` cannot be used together.
+* A field with no expiration counts as an infinite one, so `GT` never sets an expiration on such a field and `LT` always does.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of integer status codes, one per field |
+| RESP3 | Array of integer status codes, one per field |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.hset("my-key", "my-field", "my-value");
+const expirationSet = await redis.hexpire("my-key", "my-field", 1);
+
+console.log(expirationSet); // 1
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.hexpire("my-key", "field", 1000)
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.hexpire("my-key", "1000", "FIELDS", "1", "field");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.hExpire("my-key", "field", 1000);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.hexpire("my-key", 1000, "field")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.HExpire(context.Background(), "my-key", 1000*time.Second, "field").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.hexpire("my-key", 1000, "field");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.hexpire("my-key", 1000, redis::ExpireOption::NONE, &["field"])?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# HEXPIREAT
+Source: https://upstash.com/docs/redis/commands/hash/hexpireat
+
+Use `HEXPIREAT` to set field expiry as timestamp.
+
+## Syntax
+
+```redis
+HEXPIREAT <key> <unix-time-seconds> [NX | XX | GT | LT] FIELDS <numfields> <field> [<field> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<unix-time-seconds>` | Yes | No | Expiration time as a Unix timestamp in seconds. |
+| `(NX \| XX \| GT \| LT)` | No | No | Choose one form: `NX` (only when the field has no expiration); `XX` (only when the field already has one); `GT` (only when the new expiration is later than the current one); `LT` (only when it is earlier). |
+| `FIELDS <numfields> <field> [<field> ...]` | Yes | No | Fields to target. Give the field count first, then that many field names. |
+
+## Important points
+
+* `NX` cannot be combined with `XX`, `GT`, or `LT`, and `GT` and `LT` cannot be used together.
+* A field with no expiration counts as an infinite one, so `GT` never sets an expiration on such a field and `LT` always does.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of integer status codes, one per field |
+| RESP3 | Array of integer status codes, one per field |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.hset("my-key", "my-field", "my-value");
+const expirationSet = await redis.hexpireat("my-key", "my-field", Math.floor(Date.now() / 1000) + 10);
+
+console.log(expirationSet); // [1]
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.hexpireat("my-key", "field", 1735689600)
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.hexpireat("my-key", "1735689600", "FIELDS", "1", "field");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.hExpireAt("my-key", "field", 1735689600);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.hexpireat("my-key", 1735689600, "field")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.HExpireAt(context.Background(), "my-key", time.Unix(1735689600, 0), "field").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.hexpireAt("my-key", 1735689600, "field");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.hexpire_at("my-key", 1735689600, redis::ExpireOption::NONE, &["field"])?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# HEXPIRETIME
+Source: https://upstash.com/docs/redis/commands/hash/hexpiretime
+
+Use `HEXPIRETIME` to get field expiry as timestamp.
+
+## Syntax
+
+```redis
+HEXPIRETIME <key> FIELDS <numfields> <field> [<field> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `FIELDS <numfields> <field> [<field> ...]` | Yes | No | Fields to target. Give the field count first, then that many field names. |
+
+## Important points
+
+* Negative integer replies are sentinel values, not durations or timestamps; see the response description for missing or persistent data.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of expiration timestamps or negative integer status codes, one per field |
+| RESP3 | Array of expiration timestamps or negative integer status codes, one per field |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.hset("my-key", "my-field", "my-value");
+await redis.hexpireat("my-key", "my-field", Math.floor(Date.now() / 1000) + 10);
+const expireTime = await redis.hexpiretime("my-key", "my-field");
+
+console.log(expireTime); // e.g., [1697059200]
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.hexpiretime("my-key", "field")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.hexpiretime("my-key", "FIELDS", "1", "field");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.hExpireTime("my-key", "field");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.hexpiretime("my-key", "field")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.HExpireTime(context.Background(), "my-key", "field").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.hexpireTime("my-key", "field");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.hexpire_time("my-key", &["field"])?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# HGET
+Source: https://upstash.com/docs/redis/commands/hash/hget
+
+Use `HGET` to get the value of a hash field.
+
+## Syntax
+
+```redis
+HGET <key> <field>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<field>` | Yes | No | Hash field name. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Bulk string or Null bulk string or null array |
+| RESP3 | Bulk string or Null |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.hset("key", {field: "value"});
+const field = await redis.hget("key", "field");
+console.log(field); // "value"
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.hget("my-key", "field")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.hget("my-key", "field");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.hGet("my-key", "field");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.hget("my-key", "field")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.HGet(context.Background(), "my-key", "field").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.hget("my-key", "field");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.hget("my-key", "field")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# HGETALL
+Source: https://upstash.com/docs/redis/commands/hash/hgetall
+
+Use `HGETALL` to get all fields and values.
+
+## Syntax
+
+```redis
+HGETALL <key>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+
+## Important points
+
+* Pair-based results may be flattened into one alternating array in RESP2 while RESP3 preserves nested pairs or a map.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Flat array of alternating keys and values |
+| RESP3 | Map |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.hset("key", {
+  field1: "value1",
+  field2: "value2",
+  });
+const hash = await redis.hgetall("key");
+console.log(hash); // { field1: "value1", field2: "value2" }
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.hgetall("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.hgetall("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.hGetAll("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.hgetall("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.HGetAll(context.Background(), "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.hgetAll("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.hgetall("my-key")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# HGETDEL
+Source: https://upstash.com/docs/redis/commands/hash/hgetdel
+
+Use `HGETDEL` to get and delete hash fields.
+
+## Syntax
+
+```redis
+HGETDEL <key> FIELDS <numfields> <field> [<field> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `FIELDS <numfields> <field> [<field> ...]` | Yes | No | Fields to target. Give the field count first, then that many field names. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of bulk-string values or null values, one per field |
+| RESP3 | Array of bulk-string values or null values, one per field |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+// Set some hash fields
+await redis.hset("user:123", { name: "John", age: "30", email: "john@example.com" });
+
+// Get and delete specific fields
+const result = await redis.hgetdel("user:123", "name", "email");
+console.log(result); // { name: "John", email: "john@example.com" }
+
+// Verify fields were deleted
+const name = await redis.hget("user:123", "name");
+console.log(name); // null
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.hgetdel("my-key", "field")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.hgetdel("my-key", "FIELDS", "1", "field");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.hGetDel("my-key", "field");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.hgetdel("my-key", "field")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.HGetDel(context.Background(), "my-key", "1", "field").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.hgetdel("my-key", "1", "field");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.hget_del("my-key", &["field"])?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# HGETEX
+Source: https://upstash.com/docs/redis/commands/hash/hgetex
+
+Use `HGETEX` to get fields and set their expiry.
+
+## Syntax
+
+```redis
+HGETEX <key> [EX <seconds> | PX <milliseconds> | EXAT <unix-time-seconds> | PXAT <unix-time-milliseconds> | PERSIST] FIELDS <numfields> <field> [<field> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `(EX <seconds> \| PX <milliseconds> \| EXAT <unix-time-seconds> \| PXAT <unix-time-milliseconds> \| PERSIST)` | No | No | Choose one form: `EX` (set a lifetime in seconds); `PX` (set a lifetime in milliseconds); `EXAT` (expire at a Unix timestamp in seconds); `PXAT` (expire at a Unix timestamp in milliseconds); `PERSIST`. |
+| `FIELDS <numfields> <field> [<field> ...]` | Yes | No | Fields to target. Give the field count first, then that many field names. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of bulk-string values or null values, one per field |
+| RESP3 | Array of bulk-string values or null values, one per field |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.hset("user:123", { name: "John", email: "john@example.com" });
+
+// Get fields and set expiration to 60 seconds
+const result = await redis.hgetex("user:123", { ex: 60 }, "name", "email");
+console.log(result); // { name: "John", email: "john@example.com" }
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.hgetex("my-key", "field")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.hgetex("my-key", "FIELDS", "1", "field");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.hGetEx("my-key", "field");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.hgetex("my-key", "field")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.HGetEX(context.Background(), "my-key", "1", "field").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.hgetex("my-key", redis.clients.jedis.params.HGetExParams.hGetExParams(), "field");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.hget_ex("my-key", &["field"], redis::Expiry::PERSIST)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# HINCRBY
+Source: https://upstash.com/docs/redis/commands/hash/hincrby
+
+Use `HINCRBY` to increment integer value of a field.
+
+## Syntax
+
+```redis
+HINCRBY <key> <field> <increment>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<field>` | Yes | No | Hash field name. |
+| `<increment>` | Yes | No | Integer amount to add to the field. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.hset("key", {
+  field: 20,
+  });
+const after = await redis.hincrby("key", "field", 2);
+console.log(after); // 22
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.hincrby("my-key", "field", 1)
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.hincrby("my-key", "field", "1");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.hIncrBy("my-key", "field", 1);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.hincrby("my-key", "field", 1)
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.HIncrBy(context.Background(), "my-key", "field", 1).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.hincrBy("my-key", "field", 1);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.hincr("my-key", "field", 1)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# HINCRBYFLOAT
+Source: https://upstash.com/docs/redis/commands/hash/hincrbyfloat
+
+Use `HINCRBYFLOAT` to increment float value of a field.
+
+## Syntax
+
+```redis
+HINCRBYFLOAT <key> <field> <increment>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<field>` | Yes | No | Hash field name. |
+| `<increment>` | Yes | No | Amount to add to the field; may be a floating-point number. |
+
+## Important points
+
+* The value is always returned as a bulk string, in both RESP2 and RESP3. Client libraries commonly decode it to a language number.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Bulk string |
+| RESP3 | Bulk string |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.hset("key", {
+  field: 20,
+  });
+const after = await redis.hincrby("key", "field", 2.5);
+console.log(after); // 22.5
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.hincrbyfloat("my-key", "field", 1.5)
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.hincrbyfloat("my-key", "field", "1.5");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.hIncrByFloat("my-key", "field", 1.5);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.hincrbyfloat("my-key", "field", 1.5)
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.HIncrByFloat(context.Background(), "my-key", "field", 1.5).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.hincrByFloat("my-key", "field", 1.5);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.hincr("my-key", "field", 1.5)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# HKEYS
+Source: https://upstash.com/docs/redis/commands/hash/hkeys
+
+Use `HKEYS` to get all fields in a hash.
+
+## Syntax
+
+```redis
+HKEYS <key>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of bulk-string fields |
+| RESP3 | Array of bulk-string fields |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.hset("key", {
+  id: 1,
+  username: "chronark",
+  });
+const fields = await redis.hkeys("key");
+console.log(fields); // ["id", "username"]
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.hkeys("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.hkeys("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.hKeys("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.hkeys("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.HKeys(context.Background(), "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.hkeys("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.hkeys("my-key")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# HLEN
+Source: https://upstash.com/docs/redis/commands/hash/hlen
+
+Use `HLEN` to get number of fields in a hash.
+
+## Syntax
+
+```redis
+HLEN <key>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.hset("key", {
+  id: 1,
+  username: "chronark",
+  });
+const fields = await redis.hlen("key");
+console.log(fields); // 2
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.hlen("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.hlen("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.hLen("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.hlen("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.HLen(context.Background(), "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.hlen("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.hlen("my-key")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# HMGET
+Source: https://upstash.com/docs/redis/commands/hash/hmget
+
+Use `HMGET` to get values of multiple fields.
+
+## Syntax
+
+```redis
+HMGET <key> <field> [<field> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<field>` | Yes | Yes | Hash field name. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of bulk-string values or null values, one per field |
+| RESP3 | Array of bulk-string values or null values, one per field |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.hset("key", {
+  id: 1,
+  username: "chronark",
+  name: "andreas"
+  });
+const fields = await redis.hmget("key", "username", "name");
+console.log(fields); // { username: "chronark", name: "andreas" }
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.hmget("my-key", "field")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.hmget("my-key", "field");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.hmGet("my-key", "field");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.hmget("my-key", ["field"])
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.HMGet(context.Background(), "my-key", "field").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.hmget("my-key", "field");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.hmget("my-key", &["field"])?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# HMSET
+Source: https://upstash.com/docs/redis/commands/hash/hmset
+
+Use `HMSET` to set multiple hash fields.
+
+## Syntax
+
+```redis
+HMSET <key> <field> <value> [<field> <value> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<field> <value>` | Yes | Yes | Field and the value to store in it. Repeat to set several fields in one call. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Simple string `OK` |
+| RESP3 | Simple string `OK` |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+const result = await redis.hmset("my-key", { field: "value" });
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.hmset("my-key", {"field": "value"})
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.hmset("my-key", "field", "value");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.hSet("my-key", { field: "value" });
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.hset("my-key", mapping={"field": "value"})
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.HMSet(context.Background(), "my-key", "field", "value").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.hmset("my-key", java.util.Map.of("field", "value"));
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.hset_multiple("my-key", &[("field", "value")])?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# HPERSIST
+Source: https://upstash.com/docs/redis/commands/hash/hpersist
+
+Use `HPERSIST` to remove field expiration.
+
+## Syntax
+
+```redis
+HPERSIST <key> FIELDS <numfields> <field> [<field> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `FIELDS <numfields> <field> [<field> ...]` | Yes | No | Fields to target. Give the field count first, then that many field names. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of integer status codes, one per field |
+| RESP3 | Array of integer status codes, one per field |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.hset("my-key", "my-field", "my-value");
+await redis.hpexpire("my-key", "my-field", 1000);
+
+const expirationRemoved = await redis.hpersist("my-key", "my-field");
+
+console.log(expirationRemoved); // [1]
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.hpersist("my-key", "field")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.hpersist("my-key", "FIELDS", "1", "field");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.hPersist("my-key", "field");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.hpersist("my-key", "field")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.HPersist(context.Background(), "my-key", "1", "field").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.hpersist("my-key", "1", "field");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.hpersist("my-key", &["field"])?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# HPEXPIRE
+Source: https://upstash.com/docs/redis/commands/hash/hpexpire
+
+Use `HPEXPIRE` to set field TTL in milliseconds.
+
+## Syntax
+
+```redis
+HPEXPIRE <key> <milliseconds> [NX | XX | GT | LT] FIELDS <numfields> <field> [<field> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<milliseconds>` | Yes | No | Lifetime in milliseconds. |
+| `(NX \| XX \| GT \| LT)` | No | No | Choose one form: `NX` (only when the field has no expiration); `XX` (only when the field already has one); `GT` (only when the new expiration is later than the current one); `LT` (only when it is earlier). |
+| `FIELDS <numfields> <field> [<field> ...]` | Yes | No | Fields to target. Give the field count first, then that many field names. |
+
+## Important points
+
+* `NX` cannot be combined with `XX`, `GT`, or `LT`, and `GT` and `LT` cannot be used together.
+* A field with no expiration counts as an infinite one, so `GT` never sets an expiration on such a field and `LT` always does.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of integer status codes, one per field |
+| RESP3 | Array of integer status codes, one per field |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.hset("my-key", "my-field", "my-value");
+const expirationSet = await redis.hpexpire("my-key", "my-field", 1000);
+
+console.log(expirationSet); // [1]
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.hpexpire("my-key", "field", 1000)
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.hpexpire("my-key", "1000", "FIELDS", "1", "field");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.hpExpire("my-key", "field", 1000);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.hpexpire("my-key", 1000, "field")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.HPExpire(context.Background(), "my-key", time.Second, "field").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.hpexpire("my-key", 1000, "field");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.hpexpire("my-key", 1000, redis::ExpireOption::NONE, &["field"])?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# HPEXPIREAT
+Source: https://upstash.com/docs/redis/commands/hash/hpexpireat
+
+Use `HPEXPIREAT` to set field expiry as ms timestamp.
+
+## Syntax
+
+```redis
+HPEXPIREAT <key> <unix-time-milliseconds> [NX | XX | GT | LT] FIELDS <numfields> <field> [<field> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<unix-time-milliseconds>` | Yes | No | Expiration time as a Unix timestamp in milliseconds. |
+| `(NX \| XX \| GT \| LT)` | No | No | Choose one form: `NX` (only when the field has no expiration); `XX` (only when the field already has one); `GT` (only when the new expiration is later than the current one); `LT` (only when it is earlier). |
+| `FIELDS <numfields> <field> [<field> ...]` | Yes | No | Fields to target. Give the field count first, then that many field names. |
+
+## Important points
+
+* `NX` cannot be combined with `XX`, `GT`, or `LT`, and `GT` and `LT` cannot be used together.
+* A field with no expiration counts as an infinite one, so `GT` never sets an expiration on such a field and `LT` always does.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of integer status codes, one per field |
+| RESP3 | Array of integer status codes, one per field |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.hset("my-key", "my-field", "my-value");
+const expirationSet = await redis.hpexpireat("my-key", "my-field", Date.now() + 1000);
+
+console.log(expirationSet); // [1]
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.hpexpireat("my-key", "field", 1735689600)
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.hpexpireat("my-key", "1735689600", "FIELDS", "1", "field");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.hpExpireAt("my-key", "field", 1735689600);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.hpexpireat("my-key", 1735689600, "field")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.HPExpireAt(context.Background(), "my-key", time.UnixMilli(1735689600), "field").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.hpexpireAt("my-key", 1735689600, "field");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.hpexpire_at("my-key", 1735689600, redis::ExpireOption::NONE, &["field"])?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# HPEXPIRETIME
+Source: https://upstash.com/docs/redis/commands/hash/hpexpiretime
+
+Use `HPEXPIRETIME` to get field expiry as ms timestamp.
+
+## Syntax
+
+```redis
+HPEXPIRETIME <key> FIELDS <numfields> <field> [<field> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `FIELDS <numfields> <field> [<field> ...]` | Yes | No | Fields to target. Give the field count first, then that many field names. |
+
+## Important points
+
+* Negative integer replies are sentinel values, not durations or timestamps; see the response description for missing or persistent data.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of expiration timestamps or negative integer status codes, one per field |
+| RESP3 | Array of expiration timestamps or negative integer status codes, one per field |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.hset("my-key", "my-field", "my-value");
+await redis.hpexpireat("my-key", "my-field", Date.now() + 1000);
+const expireTime = await redis.hpexpiretime("my-key", "my-field");
+
+console.log(expireTime); // e.g., 1697059200000
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.hpexpiretime("my-key", "field")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.hpexpiretime("my-key", "FIELDS", "1", "field");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.hpExpireTime("my-key", "field");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.hpexpiretime("my-key", "field")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.HPExpireTime(context.Background(), "my-key", "1", "field").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.hpexpireTime("my-key", "1", "field");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.hpexpire_time("my-key", &["field"])?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# HPTTL
+Source: https://upstash.com/docs/redis/commands/hash/hpttl
+
+Use `HPTTL` to get field TTL in milliseconds.
+
+## Syntax
+
+```redis
+HPTTL <key> FIELDS <numfields> <field> [<field> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `FIELDS <numfields> <field> [<field> ...]` | Yes | No | Fields to target. Give the field count first, then that many field names. |
+
+## Important points
+
+* Negative integer replies are sentinel values, not durations or timestamps; see the response description for missing or persistent data.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of TTL values or negative integer status codes, one per field |
+| RESP3 | Array of TTL values or negative integer status codes, one per field |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.hset("my-key", "my-field", "my-value");
+await redis.hpexpire("my-key", "my-field", 1000);
+const ttl = await redis.hpttl("my-key", "my-field");
+
+console.log(ttl); // e.g., [950]
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.hpttl("my-key", "field")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.hpttl("my-key", "FIELDS", "1", "field");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.hpTTL("my-key", "field");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.hpttl("my-key", "field")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.HPTTL(context.Background(), "my-key", "1", "field").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.hpttl("my-key", "1", "field");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.hpttl("my-key", &["field"])?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# HRANDFIELD
+Source: https://upstash.com/docs/redis/commands/hash/hrandfield
+
+Use `HRANDFIELD` to get random fields from a hash.
+
+## Syntax
+
+```redis
+HRANDFIELD <key> [<count> [WITHVALUES]]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<count> [WITHVALUES]` | No | No | Number of fields to return; a negative count may repeat fields. `WITHVALUES` also returns each field's value. |
+
+## Important points
+
+* Pair-based results may be flattened into one alternating array in RESP2 while RESP3 preserves nested pairs or a map.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Null bulk string or null array, Bulk string, array of fields, or flat field/value array |
+| RESP3 | Null, Bulk string, array of fields, or array of field/value pairs |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.hset("key", {
+  id: 1,
+  username: "chronark",
+  name: "andreas"
+ });
+const randomField = await redis.hrandfield("key");
+console.log(randomField); // one of "id", "username" or  "name"
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.hrandfield("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.hrandfield("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.hRandField("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.hrandfield("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.HRandField(context.Background(), "my-key", 1).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.hrandfield("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("HRANDFIELD");
+    command.arg("my-key");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# HSCAN
+Source: https://upstash.com/docs/redis/commands/hash/hscan
+
+Use `HSCAN` to incrementally iterate hash fields.
+
+## Syntax
+
+```redis
+HSCAN <key> <cursor> [MATCH <pattern>] [COUNT <count>] [NOVALUES]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<cursor>` | Yes | No | Cursor returned by the previous call; start at `0`. |
+| `MATCH <pattern>` | No | No | Return only elements matching this glob-style pattern. |
+| `COUNT <count>` | No | No | Hint for how much work each iteration should do. |
+| `NOVALUES` | No | No | Return only field names, without their values. |
+
+## Important points
+
+* This operation can inspect a large part of the database. Prefer cursor-based scans where possible and avoid unbounded use on hot paths.
+* The cursor is opaque. Start with `0` and continue until the server returns cursor `0`; a single iteration may return no elements.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Two-element array: cursor and flat field/value array, or field array with `NOVALUES` |
+| RESP3 | Two-element array: cursor and flat field/value array, or field array with `NOVALUES` |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.hset("key", {
+  id: 1,
+  username: "chronark",
+  name: "andreas"
+ });
+const [newCursor, fields] = await redis.hscan("key", 0);
+console.log(newCursor); // likely `0` since this is a very small hash
+console.log(fields); // ["id", 1, "username", "chronark", "name", "andreas"]
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.hscan("my-key", 0)
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.hscan("my-key", "0");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.hScan("my-key", "0");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.hscan("my-key", 0)
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, _, err := client.HScan(context.Background(), "my-key", 0, "*", 0).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.hscan("my-key", "0");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("HSCAN");
+    command.arg("my-key");
+    command.arg("0");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# HSET
+Source: https://upstash.com/docs/redis/commands/hash/hset
+
+Use `HSET` to set hash field values.
+
+## Syntax
+
+```redis
+HSET <key> <field> <value> [<field> <value> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<field> <value>` | Yes | Yes | Field and the value to store in it. Repeat to set several fields in one call. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.hset("key", {
+  id: 1,
+  username: "chronark",
+  name: "andreas"
+  });
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.hset("my-key", "field", "value")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.hset("my-key", "field", "value");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.hSet("my-key", "field", "value");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.hset("my-key", "field", "value")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.HSet(context.Background(), "my-key", "field", "value").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.hset("my-key", "field", "value");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.hset("my-key", "field", "value")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# HSETEX
+Source: https://upstash.com/docs/redis/commands/hash/hsetex
+
+Use `HSETEX` to set fields with expiration.
+
+## Syntax
+
+```redis
+HSETEX <key> [FNX | FXX] [EX <seconds> | PX <milliseconds> | EXAT <unix-time-seconds> | PXAT <unix-time-milliseconds> | KEEPTTL] FIELDS <numfields> <field> <value> [<field> <value> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `(FNX \| FXX)` | No | No | Choose one form: `FNX`; `FXX`. |
+| `(EX <seconds> \| PX <milliseconds> \| EXAT <unix-time-seconds> \| PXAT <unix-time-milliseconds> \| KEEPTTL)` | No | No | Choose one form: `EX` (set a lifetime in seconds); `PX` (set a lifetime in milliseconds); `EXAT` (expire at a Unix timestamp in seconds); `PXAT` (expire at a Unix timestamp in milliseconds); `KEEPTTL` (preserve the existing key lifetime). |
+| `FIELDS <numfields> <field> <value> [<field> <value> ...]` | Yes | No | Field-value pairs to set. Give the pair count first, then that many field and value pairs. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer: `1` if the fields were set, `0` otherwise |
+| RESP3 | Integer: `1` if the fields were set, `0` otherwise |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+// Set fields with 1 hour expiration
+await redis.hsetex("user:123", { expiration: { ex: 3600 } }, {
+  name: "John",
+  email: "john@example.com"
+});
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.hsetex("my-key", field="field", value="value")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.hsetex("my-key", "FIELDS", "1", "field", "value");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.hSetEx("my-key", { field: "value" });
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.hsetex("my-key", mapping={"field": "value"})
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.HSetEX(context.Background(), "my-key", "1", "field", "value").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.hsetex("my-key", redis.clients.jedis.params.HSetExParams.hSetExParams(), "field", "value");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("HSETEX");
+    command.arg("my-key");
+    command.arg("FIELDS");
+    command.arg("1");
+    command.arg("field");
+    command.arg("value");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# HSETNX
+Source: https://upstash.com/docs/redis/commands/hash/hsetnx
+
+Use `HSETNX` to set field only if it doesn't exist.
+
+## Syntax
+
+```redis
+HSETNX <key> <field> <value>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<field>` | Yes | No | Hash field name. |
+| `<value>` | Yes | No | Value to store in the field. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer: `1` if the field was set, `0` if it already exists |
+| RESP3 | Integer: `1` if the field was set, `0` if it already exists |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.hsetnx("key", "id", 1)
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.hsetnx("my-key", "field", "value")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.hsetnx("my-key", "field", "value");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.hSetNX("my-key", "field", "value");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.hsetnx("my-key", "field", "value")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.HSetNX(context.Background(), "my-key", "field", "value").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.hsetnx("my-key", "field", "value");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.hset_nx("my-key", "field", "value")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# HSTRLEN
+Source: https://upstash.com/docs/redis/commands/hash/hstrlen
+
+Use `HSTRLEN` to get length of a field's value.
+
+## Syntax
+
+```redis
+HSTRLEN <key> <field>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<field>` | Yes | No | Hash field name. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const length = await redis.hstrlen("key", "field")
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.hstrlen("my-key", "field")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.hstrlen("my-key", "field");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.hStrLen("my-key", "field");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.hstrlen("my-key", "field")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.HStrLen(context.Background(), "my-key", "field").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.hstrlen("my-key", "field");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("HSTRLEN");
+    command.arg("my-key");
+    command.arg("field");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# HTTL
+Source: https://upstash.com/docs/redis/commands/hash/httl
+
+Use `HTTL` to get field TTL in seconds.
+
+## Syntax
+
+```redis
+HTTL <key> FIELDS <numfields> <field> [<field> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `FIELDS <numfields> <field> [<field> ...]` | Yes | No | Fields to target. Give the field count first, then that many field names. |
+
+## Important points
+
+* Negative integer replies are sentinel values, not durations or timestamps; see the response description for missing or persistent data.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of TTL values or negative integer status codes, one per field |
+| RESP3 | Array of TTL values or negative integer status codes, one per field |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.hset("my-key", "my-field", "my-value");
+await redis.hexpire("my-key", "my-field", 10);
+const ttl = await redis.httl("my-key", "my-field");
+
+console.log(ttl); // e.g., [9]
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.httl("my-key", "field")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.httl("my-key", "FIELDS", "1", "field");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.hTTL("my-key", "field");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.httl("my-key", "field")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.HTTL(context.Background(), "my-key", "1", "field").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.httl("my-key", "1", "field");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.httl("my-key", &["field"])?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# HVALS
+Source: https://upstash.com/docs/redis/commands/hash/hvals
+
+Use `HVALS` to get all values in a hash.
+
+## Syntax
+
+```redis
+HVALS <key>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of bulk-string values |
+| RESP3 | Array of bulk-string values |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.hset("key", {
+  field1: "Hello",
+  field2: "World",
+})
+const values = await redis.hvals("key")
+console.log(values) // ["Hello", "World"]
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.hvals("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.hvals("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.hVals("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.hvals("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.HVals(context.Background(), "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.hvals("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.hvals("my-key")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# Hash commands
+Source: https://upstash.com/docs/redis/commands/hash/overview
+
+<CardGroup cols={2}>
+<Card title="HDEL" href="/redis/commands/hash/hdel">Delete one or more hash fields</Card>
+<Card title="HEXISTS" href="/redis/commands/hash/hexists">Check if a hash field exists</Card>
+<Card title="HEXPIRE" href="/redis/commands/hash/hexpire">Set field TTL in seconds</Card>
+<Card title="HEXPIREAT" href="/redis/commands/hash/hexpireat">Set field expiry as timestamp</Card>
+<Card title="HEXPIRETIME" href="/redis/commands/hash/hexpiretime">Get field expiry as timestamp</Card>
+<Card title="HGET" href="/redis/commands/hash/hget">Get the value of a hash field</Card>
+<Card title="HGETALL" href="/redis/commands/hash/hgetall">Get all fields and values</Card>
+<Card title="HGETDEL" href="/redis/commands/hash/hgetdel">Get and delete hash fields</Card>
+<Card title="HGETEX" href="/redis/commands/hash/hgetex">Get fields and set their expiry</Card>
+<Card title="HINCRBY" href="/redis/commands/hash/hincrby">Increment integer value of a field</Card>
+<Card title="HINCRBYFLOAT" href="/redis/commands/hash/hincrbyfloat">Increment float value of a field</Card>
+<Card title="HKEYS" href="/redis/commands/hash/hkeys">Get all fields in a hash</Card>
+<Card title="HLEN" href="/redis/commands/hash/hlen">Get number of fields in a hash</Card>
+<Card title="HMGET" href="/redis/commands/hash/hmget">Get values of multiple fields</Card>
+<Card title="HMSET" href="/redis/commands/hash/hmset">Set multiple hash fields</Card>
+<Card title="HPERSIST" href="/redis/commands/hash/hpersist">Remove field expiration</Card>
+<Card title="HPEXPIRE" href="/redis/commands/hash/hpexpire">Set field TTL in milliseconds</Card>
+<Card title="HPEXPIREAT" href="/redis/commands/hash/hpexpireat">Set field expiry as ms timestamp</Card>
+<Card title="HPEXPIRETIME" href="/redis/commands/hash/hpexpiretime">Get field expiry as ms timestamp</Card>
+<Card title="HPTTL" href="/redis/commands/hash/hpttl">Get field TTL in milliseconds</Card>
+<Card title="HRANDFIELD" href="/redis/commands/hash/hrandfield">Get random fields from a hash</Card>
+<Card title="HSCAN" href="/redis/commands/hash/hscan">Incrementally iterate hash fields</Card>
+<Card title="HSET" href="/redis/commands/hash/hset">Set hash field values</Card>
+<Card title="HSETEX" href="/redis/commands/hash/hsetex">Set fields with expiration</Card>
+<Card title="HSETNX" href="/redis/commands/hash/hsetnx">Set field only if it doesn't exist</Card>
+<Card title="HSTRLEN" href="/redis/commands/hash/hstrlen">Get length of a field's value</Card>
+<Card title="HTTL" href="/redis/commands/hash/httl">Get field TTL in seconds</Card>
+<Card title="HVALS" href="/redis/commands/hash/hvals">Get all values in a hash</Card>
+</CardGroup>
+
+# HyperLogLog commands
+Source: https://upstash.com/docs/redis/commands/hyperloglog/overview
+
+<CardGroup cols={2}>
+<Card title="PFADD" href="/redis/commands/hyperloglog/pfadd">Add elements to HyperLogLog</Card>
+<Card title="PFCOUNT" href="/redis/commands/hyperloglog/pfcount">Get estimated cardinality</Card>
+<Card title="PFMERGE" href="/redis/commands/hyperloglog/pfmerge">Merge multiple HyperLogLogs</Card>
+</CardGroup>
+
+# PFADD
+Source: https://upstash.com/docs/redis/commands/hyperloglog/pfadd
+
+Use `PFADD` to add elements to HyperLogLog.
+
+## Syntax
+
+```redis
+PFADD <key> [<element> [<element> ...]]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<element>` | No | Yes | Element to add to the HyperLogLog. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer: `1` if at least one internal register was altered, `0` otherwise |
+| RESP3 | Integer: `1` if at least one internal register was altered, `0` otherwise |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+const result = await redis.pfadd("my-key", "element");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.pfadd("my-key", "member")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.pfadd("my-key", "element");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.pfAdd("my-key", "element");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.pfadd("my-key", "member")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.PFAdd(context.Background(), "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.pfadd("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.pfadd("my-key", &["member"])?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# PFCOUNT
+Source: https://upstash.com/docs/redis/commands/hyperloglog/pfcount
+
+Use `PFCOUNT` to get estimated cardinality.
+
+## Syntax
+
+```redis
+PFCOUNT <key> [<key> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | Yes | Redis key targeted by the command. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+const result = await redis.pfcount("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.pfcount("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.pfcount("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.pfCount("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.pfcount("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.PFCount(context.Background(), "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.pfcount("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.pfcount(&["my-key"])?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# PFMERGE
+Source: https://upstash.com/docs/redis/commands/hyperloglog/pfmerge
+
+Use `PFMERGE` to merge multiple HyperLogLogs.
+
+## Syntax
+
+```redis
+PFMERGE <destkey> [<sourcekey> [<sourcekey> ...]]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<destkey>` | Yes | No | Redis key used as destkey. |
+| `<sourcekey>` | No | Yes | Redis key used as sourcekey. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Simple string `OK` |
+| RESP3 | Simple string `OK` |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+const result = await redis.pfmerge("destination-key", "source-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.pfmerge("destination-key", "source-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.pfmerge("destination-key", "source-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.pfMerge("destination-key", "source-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.pfmerge("destination-key", "source-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.PFMerge(context.Background(), "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.pfmerge("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.pfmerge("destination-key", &["source-key"])?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# JSON.ARRAPPEND
+Source: https://upstash.com/docs/redis/commands/json/json-arrappend
+
+Use `JSON.ARRAPPEND` to append values to JSON array.
+
+## Syntax
+
+```redis
+JSON.ARRAPPEND <key> <path> <value> [value ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `key` | Yes | No | JSON document key. |
+| `path` | Yes | No | Path selecting arrays. |
+| `value` | Yes | Yes | Valid JSON value to append. |
+
+## Important points
+
+* Raw TCP examples pass JSON values as valid JSON text. Typed Upstash SDK helpers serialize native objects and values for you.
+* Paths beginning with `$` use JSONPath and can match multiple values, so many JSON commands return an array of per-match results.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of integer lengths or null values, one per matched path |
+| RESP3 | Array of integer lengths or null values, one per matched path |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.json.arrappend("key", "$.path.to.array", "a");
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.json().arrappend("profile", "$.tags", "new")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.call("JSON.ARRAPPEND", "profile", "$.tags", "\"new\"");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.json.arrAppend("profile", "$.tags", "new");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.json().arrappend("profile", "$.tags", "new")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.JSONArrAppend(context.Background(), "profile", "$.tags", "new").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.JedisPooled;
+
+try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.jsonArrAppend("profile", new redis.clients.jedis.json.Path("$.tags"), "new");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::JsonCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result: redis::Value = connection.json_arr_append("profile", "$.tags", &"new")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# JSON.ARRINDEX
+Source: https://upstash.com/docs/redis/commands/json/json-arrindex
+
+Use `JSON.ARRINDEX` to find index of value in array.
+
+## Syntax
+
+```redis
+JSON.ARRINDEX <key> <path> <value> [start [stop]]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `key` | Yes | No | JSON document key. |
+| `path` | Yes | No | Path selecting arrays. |
+| `value` | Yes | No | Valid JSON value to locate. |
+| `start` | No | No | Inclusive starting index. |
+| `stop` | No | No | Exclusive ending index. |
+
+## Important points
+
+* Raw TCP examples pass JSON values as valid JSON text. Typed Upstash SDK helpers serialize native objects and values for you.
+* Paths beginning with `$` use JSONPath and can match multiple values, so many JSON commands return an array of per-match results.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of integer indexes or null values, one per matched path |
+| RESP3 | Array of integer indexes or null values, one per matched path |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const index = await redis.json.arrindex("key", "$.path.to.array", "a");
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.json().arrindex("profile", "$.tags", "new")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.call("JSON.ARRINDEX", "profile", "$.tags", "\"new\"");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.json.arrIndex("profile", "$.tags", "new");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.json().arrindex("profile", "$.tags", "new")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.JSONArrIndex(context.Background(), "profile", "$.tags", "new").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.JedisPooled;
+
+try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.jsonArrIndex("profile", new redis.clients.jedis.json.Path("$.tags"), "new");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::JsonCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result: redis::Value = connection.json_arr_index("profile", "$.tags", &"new")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# JSON.ARRINSERT
+Source: https://upstash.com/docs/redis/commands/json/json-arrinsert
+
+Use `JSON.ARRINSERT` to insert values into JSON array.
+
+## Syntax
+
+```redis
+JSON.ARRINSERT <key> <path> <index> <value> [value ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `key` | Yes | No | JSON document key. |
+| `path` | Yes | No | Path selecting arrays. |
+| `index` | Yes | No | Insertion index; negative indexes count from the end. |
+| `value` | Yes | Yes | Valid JSON value to insert. |
+
+## Important points
+
+* Raw TCP examples pass JSON values as valid JSON text. Typed Upstash SDK helpers serialize native objects and values for you.
+* Paths beginning with `$` use JSONPath and can match multiple values, so many JSON commands return an array of per-match results.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of integer lengths or null values, one per matched path |
+| RESP3 | Array of integer lengths or null values, one per matched path |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const length = await redis.json.arrinsert("key", "$.path.to.array", 2, "a", "b");
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.json().arrinsert("profile", "$.tags", 0, "first")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.call("JSON.ARRINSERT", "profile", "$.tags", "0", "\"first\"");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.json.arrInsert("profile", "$.tags", 0, "first");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.json().arrinsert("profile", "$.tags", 0, "first")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.JSONArrInsert(context.Background(), "profile", "$.tags", 0, "first").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.JedisPooled;
+
+try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.jsonArrInsert("profile", new redis.clients.jedis.json.Path("$.tags"), 0, "first");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::JsonCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result: redis::Value = connection.json_arr_insert("profile", "$.tags", 0, &"first")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# JSON.ARRLEN
+Source: https://upstash.com/docs/redis/commands/json/json-arrlen
+
+Use `JSON.ARRLEN` to get JSON array length.
+
+## Syntax
+
+```redis
+JSON.ARRLEN <key> [path]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `key` | Yes | No | JSON document key. |
+| `path` | No | No | Path selecting arrays; defaults to the root. |
+
+## Important points
+
+* Raw TCP examples pass JSON values as valid JSON text. Typed Upstash SDK helpers serialize native objects and values for you.
+* Paths beginning with `$` use JSONPath and can match multiple values, so many JSON commands return an array of per-match results.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of integer lengths or null values, one per matched path |
+| RESP3 | Array of integer lengths or null values, one per matched path |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const length = await redis.json.arrlen("key", "$.path.to.array");
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.json().arrlen("profile", "$.tags")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.call("JSON.ARRLEN", "profile", "$.tags");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.json.arrLen("profile", { path: "$.tags" });
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.json().arrlen("profile", "$.tags")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.JSONArrLen(context.Background(), "profile", "$.tags").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.JedisPooled;
+
+try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.jsonArrLen("profile", new redis.clients.jedis.json.Path("$.tags"));
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::JsonCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result: redis::Value = connection.json_arr_len("profile", "$.tags")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# JSON.ARRPOP
+Source: https://upstash.com/docs/redis/commands/json/json-arrpop
+
+Use `JSON.ARRPOP` to pop value from JSON array.
+
+## Syntax
+
+```redis
+JSON.ARRPOP <key> [path [index]]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `key` | Yes | No | JSON document key. |
+| `path` | No | No | Path selecting arrays; defaults to the root. |
+| `index` | No | No | Element index; defaults to the last element. |
+
+## Important points
+
+* Raw TCP examples pass JSON values as valid JSON text. Typed Upstash SDK helpers serialize native objects and values for you.
+* Paths beginning with `$` use JSONPath and can match multiple values, so many JSON commands return an array of per-match results.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of bulk-string JSON values or null values, one per matched path |
+| RESP3 | Array of bulk-string JSON values or null values, one per matched path |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const element = await redis.json.arrpop("key", "$.path.to.array");
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.json().arrpop("profile", "$.tags", -1)
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.call("JSON.ARRPOP", "profile", "$.tags", "-1");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.json.arrPop("profile", { path: "$.tags", index: -1 });
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.json().arrpop("profile", "$.tags", -1)
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.JSONArrPop(context.Background(), "profile", "$.tags", -1).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.JedisPooled;
+
+try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.jsonArrPop("profile", new redis.clients.jedis.json.Path("$.tags"), -1);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::JsonCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result: redis::Value = connection.json_arr_pop("profile", "$.tags", -1)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# JSON.ARRTRIM
+Source: https://upstash.com/docs/redis/commands/json/json-arrtrim
+
+Use `JSON.ARRTRIM` to trim JSON array to range.
+
+## Syntax
+
+```redis
+JSON.ARRTRIM <key> <path> <start> <stop>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `key` | Yes | No | JSON document key. |
+| `path` | Yes | No | Path selecting arrays. |
+| `start` | Yes | No | Inclusive first index to keep. |
+| `stop` | Yes | No | Inclusive last index to keep. |
+
+## Important points
+
+* Raw TCP examples pass JSON values as valid JSON text. Typed Upstash SDK helpers serialize native objects and values for you.
+* Paths beginning with `$` use JSONPath and can match multiple values, so many JSON commands return an array of per-match results.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of integer lengths or null values, one per matched path |
+| RESP3 | Array of integer lengths or null values, one per matched path |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const length = await redis.json.arrtrim("key", "$.path.to.array", 2, 10);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.json().arrtrim("profile", "$.tags", 0, 9)
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.call("JSON.ARRTRIM", "profile", "$.tags", "0", "9");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.json.arrTrim("profile", "$.tags", 0, 9);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.json().arrtrim("profile", "$.tags", 0, 9)
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.JSONArrTrimWithArgs(context.Background(), "profile", "$.tags", &redis.JSONArrTrimArgs{Start: 0, Stop: func() *int { stop := 9; return &stop }()}).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.JedisPooled;
+
+try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.jsonArrTrim("profile", new redis.clients.jedis.json.Path("$.tags"), 0, 9);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::JsonCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result: redis::Value = connection.json_arr_trim("profile", "$.tags", 0, 9)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# JSON.CLEAR
+Source: https://upstash.com/docs/redis/commands/json/json-clear
+
+Use `JSON.CLEAR` to clear JSON values.
+
+## Syntax
+
+```redis
+JSON.CLEAR <key> [path]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `key` | Yes | No | JSON document key. |
+| `path` | No | No | Path to containers or numbers; defaults to the root. |
+
+## Important points
+
+* Raw TCP examples pass JSON values as valid JSON text. Typed Upstash SDK helpers serialize native objects and values for you.
+* Paths beginning with `$` use JSONPath and can match multiple values, so many JSON commands return an array of per-match results.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.json.clear("key");
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.json().clear("profile", "$.stats")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.call("JSON.CLEAR", "profile", "$.stats");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.json.clear("profile", { path: "$.stats" });
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.json().clear("profile", "$.stats")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.JSONClear(context.Background(), "profile", "$.stats").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.JedisPooled;
+
+try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.jsonClear("profile", new redis.clients.jedis.json.Path("$.stats"));
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::JsonCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result: redis::Value = connection.json_clear("profile", "$.stats")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# JSON.DEBUG
+Source: https://upstash.com/docs/redis/commands/json/json-debug
+
+Use `JSON.DEBUG` to inspect JSON memory usage.
+
+## Syntax
+
+```redis
+JSON.DEBUG MEMORY <key> [path]
+JSON.DEBUG HELP
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `MEMORY` | One form | No | Report the approximate memory used by the JSON value selected by key and optional path. |
+| `key` | For MEMORY | No | JSON document key. |
+| `path` | No | No | JSONPath to inspect; defaults to the root. |
+| `HELP` | One form | No | Return the supported JSON.DEBUG forms. |
+
+## Important points
+
+* Raw TCP examples pass JSON values as valid JSON text. Typed Upstash SDK helpers serialize native objects and values for you.
+* Paths beginning with `$` use JSONPath and can match multiple values, so many JSON commands return an array of per-match results.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer, array of integers, or array of help strings |
+| RESP3 | Integer, array of integers, or array of help strings |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+<Note>
+  This command is not supported yet in `upstash_redis`.
+</Note>
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.call("JSON.DEBUG", "MEMORY", "profile", "$.stats");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.json.debugMemory("profile", { path: "$.stats" });
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.json().debug("MEMORY", "profile", "$.stats")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.JSONDebugMemory(context.Background(), "profile", "$.stats").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.JedisPooled;
+
+try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.jsonDebugMemory("profile", new redis.clients.jedis.json.Path("$.stats"));
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("JSON.DEBUG");
+    command.arg("MEMORY");
+    command.arg("profile");
+    command.arg("$.stats");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# JSON.DEL
+Source: https://upstash.com/docs/redis/commands/json/json-del
+
+Use `JSON.DEL` to delete JSON values.
+
+## Syntax
+
+```redis
+JSON.DEL <key> [path]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `key` | Yes | No | JSON document key. |
+| `path` | No | No | Path to delete; omitting it deletes the whole key. |
+
+## Important points
+
+* Raw TCP examples pass JSON values as valid JSON text. Typed Upstash SDK helpers serialize native objects and values for you.
+* Paths beginning with `$` use JSONPath and can match multiple values, so many JSON commands return an array of per-match results.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.json.del("key", "$.path.to.value");
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.json().delete("profile", "$.temporary")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.call("JSON.DEL", "profile", "$.temporary");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.json.del("profile", { path: "$.temporary" });
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.json().delete("profile", "$.temporary")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.JSONDel(context.Background(), "profile", "$.temporary").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.JedisPooled;
+
+try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.jsonDel("profile", new redis.clients.jedis.json.Path("$.temporary"));
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::JsonCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result: redis::Value = connection.json_del("profile", "$.temporary")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# JSON.FORGET
+Source: https://upstash.com/docs/redis/commands/json/json-forget
+
+Use `JSON.FORGET` to alias for JSON.DEL.
+
+## Syntax
+
+```redis
+JSON.FORGET <key> [path]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `key` | Yes | No | JSON document key. |
+| `path` | No | No | Path to delete; omitting it deletes the whole key. |
+
+## Important points
+
+* Raw TCP examples pass JSON values as valid JSON text. Typed Upstash SDK helpers serialize native objects and values for you.
+* Paths beginning with `$` use JSONPath and can match multiple values, so many JSON commands return an array of per-match results.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.json.forget("key", "$.path.to.value");
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.json().forget("profile", "$.temporary")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.call("JSON.FORGET", "profile", "$.temporary");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.json.forget("profile", { path: "$.temporary" });
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.json().forget("profile", "$.temporary")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.JSONForget(context.Background(), "profile", "$.temporary").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.JedisPooled;
+
+try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.jsonDel("profile", new redis.clients.jedis.json.Path("$.temporary"));
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::JsonCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result: redis::Value = connection.json_del("profile", "$.temporary")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# JSON.GET
+Source: https://upstash.com/docs/redis/commands/json/json-get
+
+Use `JSON.GET` to get JSON values.
+
+## Syntax
+
+```redis
+JSON.GET <key> [INDENT indent] [NEWLINE newline] [SPACE space] [path [path ...]]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `key` | Yes | No | JSON document key. |
+| `INDENT indent` | No | No | Indentation characters for formatted JSON. |
+| `NEWLINE newline` | No | No | Line-separator characters for formatted JSON. |
+| `SPACE space` | No | No | Characters placed after JSON separators. |
+| `path` | No | Yes | One or more paths; defaults to the root. |
+
+## Important points
+
+* Raw TCP examples pass JSON values as valid JSON text. Typed Upstash SDK helpers serialize native objects and values for you.
+* Paths beginning with `$` use JSONPath and can match multiple values, so many JSON commands return an array of per-match results.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Bulk string or Null bulk string or null array |
+| RESP3 | Bulk string or Null |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const value = await redis.json.get("key", "$.path.to.somewhere");
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.json().get("profile", "$.name")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.call("JSON.GET", "profile", "$.name");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.json.get("profile", { path: "$.name" });
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.json().get("profile", "$.name")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.JSONGet(context.Background(), "profile", "$.name").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.JedisPooled;
+
+try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.jsonGet("profile", new redis.clients.jedis.json.Path("$.name"));
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::JsonCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result: redis::Value = connection.json_get("profile", &["$.name"])?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# JSON.MERGE
+Source: https://upstash.com/docs/redis/commands/json/json-merge
+
+Use `JSON.MERGE` to merge JSON values.
+
+## Syntax
+
+```redis
+JSON.MERGE <key> <path> <value>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `key` | Yes | No | JSON document key. |
+| `path` | Yes | No | Path to merge into. |
+| `value` | Yes | No | Valid JSON value containing the merge patch. |
+
+## Important points
+
+* Raw TCP examples pass JSON values as valid JSON text. Typed Upstash SDK helpers serialize native objects and values for you.
+* Paths beginning with `$` use JSONPath and can match multiple values, so many JSON commands return an array of per-match results.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Simple string `OK` |
+| RESP3 | Simple string `OK` |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.json.merge("key", "$.path.to.value", {"new": "value"})
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.json().merge("profile", "$", {"active": True})
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.call("JSON.MERGE", "profile", "$", "{\"active\":true}");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.json.merge("profile", "$", { active: true });
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.json().merge("profile", "$", {"active": True})
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.JSONMerge(context.Background(), "profile", "$", `{"active":true}`).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.JedisPooled;
+
+try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.jsonMerge("profile", new redis.clients.jedis.json.Path("$"), java.util.Map.of("active", true));
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("JSON.MERGE");
+    command.arg("profile");
+    command.arg("$");
+    command.arg("{\"active\":true}");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# JSON.MGET
+Source: https://upstash.com/docs/redis/commands/json/json-mget
+
+Use `JSON.MGET` to get values from multiple keys.
+
+## Syntax
+
+```redis
+JSON.MGET <key> [key ...] <path>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `key` | Yes | Yes | One or more JSON document keys. |
+| `path` | Yes | No | Path read from every key. |
+
+## Important points
+
+* Raw TCP examples pass JSON values as valid JSON text. Typed Upstash SDK helpers serialize native objects and values for you.
+* Paths beginning with `$` use JSONPath and can match multiple values, so many JSON commands return an array of per-match results.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of bulk-string JSON values or null values, one per key |
+| RESP3 | Array of bulk-string JSON values or null values, one per key |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const values = await redis.json.mget(["key1", "key2"],  "$.path.to.somewhere");
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.json().mget(["profile:1", "profile:2"], "$.name")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.call("JSON.MGET", "profile:1", "profile:2", "$.name");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.json.mGet(["profile:1", "profile:2"], "$.name");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.json().mget(["profile:1", "profile:2"], "$.name")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.JSONMGet(context.Background(), "$.name", "profile:1", "profile:2").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.JedisPooled;
+
+try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.jsonMGet(new redis.clients.jedis.json.Path2("$.name"), "profile:1", "profile:2");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::JsonCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result: redis::Value = connection.json_mget(&["profile:1", "profile:2"], "$.name")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# JSON.MSET
+Source: https://upstash.com/docs/redis/commands/json/json-mset
+
+Use `JSON.MSET` to set values in multiple keys.
+
+## Syntax
+
+```redis
+JSON.MSET <key> <path> <value> [key path value ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `key path value` | Yes | Yes | One or more key, path, and valid-JSON-value triples. |
+
+## Important points
+
+* Raw TCP examples pass JSON values as valid JSON text. Typed Upstash SDK helpers serialize native objects and values for you.
+* Paths beginning with `$` use JSONPath and can match multiple values, so many JSON commands return an array of per-match results.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Simple string `OK` |
+| RESP3 | Simple string `OK` |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+const result = await redis.json.mset([
+  { key: "profile:1", path: "$", value: { name: "Ada" } },
+]);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.json().mset([("profile:1", "$", {"name": "Ada"})])
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.call("JSON.MSET", "profile:1", "$", "{\"name\":\"Ada\"}");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.json.mSet([{ key: "profile:1", path: "$", value: { name: "Ada" } }]);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.json().mset([("profile:1", "$", {"name": "Ada"})])
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.JSONMSet(context.Background(), "profile:1", "$", `{"name":"Ada"}`).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+import java.nio.charset.StandardCharsets;
+import redis.clients.jedis.Jedis;
+import redis.clients.jedis.commands.ProtocolCommand;
+
+ProtocolCommand command = () -> "JSON.MSET".getBytes(StandardCharsets.UTF_8);
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.sendCommand(command, "profile:1", "$", "{\"name\":\"Ada\"}");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("JSON.MSET");
+    command.arg("profile:1");
+    command.arg("$");
+    command.arg("{\"name\":\"Ada\"}");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# JSON.NUMINCRBY
+Source: https://upstash.com/docs/redis/commands/json/json-numincrby
+
+Use `JSON.NUMINCRBY` to increment JSON number.
+
+## Syntax
+
+```redis
+JSON.NUMINCRBY <key> <path> <value>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `key` | Yes | No | JSON document key. |
+| `path` | Yes | No | Path selecting numbers. |
+| `value` | Yes | No | Numeric amount to add. |
+
+## Important points
+
+* Raw TCP examples pass JSON values as valid JSON text. Typed Upstash SDK helpers serialize native objects and values for you.
+* Paths beginning with `$` use JSONPath and can match multiple values, so many JSON commands return an array of per-match results.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Bulk string containing a JSON number or array |
+| RESP3 | Bulk string containing a JSON number or array |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const newValue = await redis.json.numincrby("key", "$.path.to.value", 2);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.json().numincrby("profile", "$.visits", 1)
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.call("JSON.NUMINCRBY", "profile", "$.visits", "1");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.json.numIncrBy("profile", "$.visits", 1);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.json().numincrby("profile", "$.visits", 1)
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.JSONNumIncrBy(context.Background(), "profile", "$.visits", 1).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.JedisPooled;
+
+try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.jsonNumIncrBy("profile", new redis.clients.jedis.json.Path("$.visits"), 1);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::JsonCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result: redis::Value = connection.json_num_incr_by("profile", "$.visits", 1)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# JSON.NUMMULTBY
+Source: https://upstash.com/docs/redis/commands/json/json-nummultby
+
+Use `JSON.NUMMULTBY` to multiply JSON number.
+
+## Syntax
+
+```redis
+JSON.NUMMULTBY <key> <path> <value>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `key` | Yes | No | JSON document key. |
+| `path` | Yes | No | Path selecting numbers. |
+| `value` | Yes | No | Numeric multiplier. |
+
+## Important points
+
+* Raw TCP examples pass JSON values as valid JSON text. Typed Upstash SDK helpers serialize native objects and values for you.
+* Paths beginning with `$` use JSONPath and can match multiple values, so many JSON commands return an array of per-match results.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Bulk string containing a JSON number or array |
+| RESP3 | Bulk string containing a JSON number or array |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const newValue = await redis.json.nummultby("key", "$.path.to.value", 2);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.json().nummultby("profile", "$.score", 2)
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.call("JSON.NUMMULTBY", "profile", "$.score", "2");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.json.numMultBy("profile", "$.score", 2);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.json().nummultby("profile", "$.score", 2)
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.Do(context.Background(), "JSON.NUMMULTBY", "profile", "$.score", "2").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+import java.nio.charset.StandardCharsets;
+import redis.clients.jedis.Jedis;
+import redis.clients.jedis.commands.ProtocolCommand;
+
+ProtocolCommand command = () -> "JSON.NUMMULTBY".getBytes(StandardCharsets.UTF_8);
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.sendCommand(command, "profile", "$.score", "2");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("JSON.NUMMULTBY");
+    command.arg("profile");
+    command.arg("$.score");
+    command.arg("2");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# JSON.OBJKEYS
+Source: https://upstash.com/docs/redis/commands/json/json-objkeys
+
+Use `JSON.OBJKEYS` to get JSON object keys.
+
+## Syntax
+
+```redis
+JSON.OBJKEYS <key> [path]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `key` | Yes | No | JSON document key. |
+| `path` | No | No | Path selecting objects; defaults to the root. |
+
+## Important points
+
+* Raw TCP examples pass JSON values as valid JSON text. Typed Upstash SDK helpers serialize native objects and values for you.
+* Paths beginning with `$` use JSONPath and can match multiple values, so many JSON commands return an array of per-match results.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of arrays of bulk-string object keys or null values, or Null bulk string or null array |
+| RESP3 | Array of arrays of bulk-string object keys or null values, or Null |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const keys = await redis.json.objkeys("key", "$.path");
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.json().objkeys("profile", "$")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.call("JSON.OBJKEYS", "profile", "$");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.json.objKeys("profile", { path: "$" });
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.json().objkeys("profile", "$")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.JSONObjKeys(context.Background(), "profile", "$").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.JedisPooled;
+
+try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.jsonObjKeys("profile", new redis.clients.jedis.json.Path("$"));
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::JsonCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result: redis::Value = connection.json_obj_keys("profile", "$")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# JSON.OBJLEN
+Source: https://upstash.com/docs/redis/commands/json/json-objlen
+
+Use `JSON.OBJLEN` to get JSON object size.
+
+## Syntax
+
+```redis
+JSON.OBJLEN <key> [path]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `key` | Yes | No | JSON document key. |
+| `path` | No | No | Path selecting objects; defaults to the root. |
+
+## Important points
+
+* Raw TCP examples pass JSON values as valid JSON text. Typed Upstash SDK helpers serialize native objects and values for you.
+* Paths beginning with `$` use JSONPath and can match multiple values, so many JSON commands return an array of per-match results.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer, array of integer lengths or null values, or Null bulk string or null array |
+| RESP3 | Integer, array of integer lengths or null values, or Null |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const lengths = await redis.json.objlen("key", "$.path");
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.json().objlen("profile", "$")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.call("JSON.OBJLEN", "profile", "$");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.json.objLen("profile", { path: "$" });
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.json().objlen("profile", "$")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.JSONObjLen(context.Background(), "profile", "$").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.JedisPooled;
+
+try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.jsonObjLen("profile", new redis.clients.jedis.json.Path("$"));
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::JsonCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result: redis::Value = connection.json_obj_len("profile", "$")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# JSON.RESP
+Source: https://upstash.com/docs/redis/commands/json/json-resp
+
+Use `JSON.RESP` to get JSON in RESP format.
+
+## Syntax
+
+```redis
+JSON.RESP <key> [path]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `key` | Yes | No | JSON document key. |
+| `path` | No | No | Path to convert; defaults to the root. |
+
+## Important points
+
+* Raw TCP examples pass JSON values as valid JSON text. Typed Upstash SDK helpers serialize native objects and values for you.
+* Paths beginning with `$` use JSONPath and can match multiple values, so many JSON commands return an array of per-match results.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Nested array, Integer, Bulk string, Simple string (`true` or `false` for JSON booleans), or Null bulk string or null array |
+| RESP3 | Nested array, Integer, Bulk string, Simple string (`true` or `false` for JSON booleans), or Null |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+const result = await redis.json.resp("profile", "$");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.json().resp("profile", "$")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.call("JSON.RESP", "profile", "$");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.sendCommand(["JSON.RESP", "profile", "$"]);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.json().resp("profile", "$")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.Do(context.Background(), "JSON.RESP", "profile", "$").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+import java.nio.charset.StandardCharsets;
+import redis.clients.jedis.Jedis;
+import redis.clients.jedis.commands.ProtocolCommand;
+
+ProtocolCommand command = () -> "JSON.RESP".getBytes(StandardCharsets.UTF_8);
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.sendCommand(command, "profile", "$");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("JSON.RESP");
+    command.arg("profile");
+    command.arg("$");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# JSON.SET
+Source: https://upstash.com/docs/redis/commands/json/json-set
+
+Use `JSON.SET` to set JSON value.
+
+## Syntax
+
+```redis
+JSON.SET <key> <path> <value> [NX | XX]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `key` | Yes | No | JSON document key. |
+| `path` | Yes | No | Path to create or replace. |
+| `value` | Yes | No | Valid JSON value. |
+| `NX \| XX` | No | No | Write only when the path is absent (`NX`) or present (`XX`). |
+
+## Important points
+
+* Raw TCP examples pass JSON values as valid JSON text. Typed Upstash SDK helpers serialize native objects and values for you.
+* Paths beginning with `$` use JSONPath and can match multiple values, so many JSON commands return an array of per-match results.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Simple string `OK`, or Null bulk string or null array when `NX` or `XX` prevented the write |
+| RESP3 | Simple string `OK`, or Null when `NX` or `XX` prevented the write |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+redis.json.set(key, "$.path", value);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.json().set("profile", "$", {"name": "Ada"})
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.call("JSON.SET", "profile", "$", "{\"name\":\"Ada\"}");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.json.set("profile", "$", { name: "Ada" });
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.json().set("profile", "$", {"name": "Ada"})
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.JSONSet(context.Background(), "profile", "$", map[string]interface{}{"name": "Ada"}).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.JedisPooled;
+
+try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.jsonSet("profile", new redis.clients.jedis.json.Path("$"), java.util.Map.of("name", "Ada"));
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::JsonCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result: redis::Value = connection.json_set("profile", "$", &serde_json::json!({"name": "Ada"}))?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# JSON.STRAPPEND
+Source: https://upstash.com/docs/redis/commands/json/json-strappend
+
+Use `JSON.STRAPPEND` to append to JSON string.
+
+## Syntax
+
+```redis
+JSON.STRAPPEND <key> <path> <value>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `key` | Yes | No | JSON document key. |
+| `path` | Yes | No | Path selecting strings. |
+| `value` | Yes | No | JSON-encoded string to append. |
+
+## Important points
+
+* Raw TCP examples pass JSON values as valid JSON text. Typed Upstash SDK helpers serialize native objects and values for you.
+* Paths beginning with `$` use JSONPath and can match multiple values, so many JSON commands return an array of per-match results.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer, array of integer lengths or null values, or Null bulk string or null array |
+| RESP3 | Integer, array of integer lengths or null values, or Null |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.json.strappend("key", "$.path.to.str", "abc");
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.json().strappend("profile", "$.name", " Lovelace")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.call("JSON.STRAPPEND", "profile", "$.name", "\" Lovelace\"");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.json.strAppend("profile", " Lovelace", { path: "$.name" });
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.json().strappend("profile", " Lovelace", "$.name")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.JSONStrAppend(context.Background(), "profile", "$.name", `" Lovelace"`).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.JedisPooled;
+
+try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.jsonStrAppend("profile", new redis.clients.jedis.json.Path("$.name"), " Lovelace");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::JsonCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result: redis::Value = connection.json_str_append("profile", "$.name", " Lovelace")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# JSON.STRLEN
+Source: https://upstash.com/docs/redis/commands/json/json-strlen
+
+Use `JSON.STRLEN` to get JSON string length.
+
+## Syntax
+
+```redis
+JSON.STRLEN <key> [path]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `key` | Yes | No | JSON document key. |
+| `path` | No | No | Path selecting strings; defaults to the root. |
+
+## Important points
+
+* Raw TCP examples pass JSON values as valid JSON text. Typed Upstash SDK helpers serialize native objects and values for you.
+* Paths beginning with `$` use JSONPath and can match multiple values, so many JSON commands return an array of per-match results.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer, array of integer lengths or null values, or Null bulk string or null array |
+| RESP3 | Integer, array of integer lengths or null values, or Null |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.json.strlen("key", "$.path.to.str", "a");
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.json().strlen("profile", "$.name")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.call("JSON.STRLEN", "profile", "$.name");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.json.strLen("profile", { path: "$.name" });
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.json().strlen("profile", "$.name")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.JSONStrLen(context.Background(), "profile", "$.name").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.JedisPooled;
+
+try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.jsonStrLen("profile", new redis.clients.jedis.json.Path("$.name"));
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::JsonCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result: redis::Value = connection.json_str_len("profile", "$.name")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# JSON.TOGGLE
+Source: https://upstash.com/docs/redis/commands/json/json-toggle
+
+Use `JSON.TOGGLE` to toggle JSON boolean.
+
+## Syntax
+
+```redis
+JSON.TOGGLE <key> <path>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `key` | Yes | No | JSON document key. |
+| `path` | Yes | No | Path selecting Boolean values. |
+
+## Important points
+
+* Raw TCP examples pass JSON values as valid JSON text. Typed Upstash SDK helpers serialize native objects and values for you.
+* Paths beginning with `$` use JSONPath and can match multiple values, so many JSON commands return an array of per-match results.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of integer Boolean values or null values, one per matched path |
+| RESP3 | Array of integer Boolean values or null values, one per matched path |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const bool = await redis.json.toggle("key", "$.path.to.bool");
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.json().toggle("profile", "$.active")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.call("JSON.TOGGLE", "profile", "$.active");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.json.toggle("profile", "$.active");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.json().toggle("profile", "$.active")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.JSONToggle(context.Background(), "profile", "$.active").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.JedisPooled;
+
+try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.jsonToggle("profile", new redis.clients.jedis.json.Path("$.active"));
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::JsonCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result: redis::Value = connection.json_toggle("profile", "$.active")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# JSON.TYPE
+Source: https://upstash.com/docs/redis/commands/json/json-type
+
+Use `JSON.TYPE` to get JSON value type.
+
+## Syntax
+
+```redis
+JSON.TYPE <key> [path]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `key` | Yes | No | JSON document key. |
+| `path` | No | No | Path to inspect; defaults to the root. |
+
+## Important points
+
+* Raw TCP examples pass JSON values as valid JSON text. Typed Upstash SDK helpers serialize native objects and values for you.
+* Paths beginning with `$` use JSONPath and can match multiple values, so many JSON commands return an array of per-match results.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Bulk string, array of bulk-string type names, or Null bulk string or null array |
+| RESP3 | Bulk string, array of bulk-string type names, or Null |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const myType = await redis.json.type("key", "$.path.to.value");
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.json().type("profile", "$.name")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.call("JSON.TYPE", "profile", "$.name");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.json.type("profile", { path: "$.name" });
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.json().type("profile", "$.name")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.JSONType(context.Background(), "profile", "$.name").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.JedisPooled;
+
+try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.jsonType("profile", new redis.clients.jedis.json.Path("$.name"));
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::JsonCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result: redis::Value = connection.json_type("profile", "$.name")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# JSON commands
+Source: https://upstash.com/docs/redis/commands/json/overview
+
+To query inside JSON values (full-text, fuzzy, phrase, regex), see [Upstash Redis Search](/docs/redis/search/introduction).
+
+<CardGroup cols={2}>
+<Card title="JSON.ARRAPPEND" href="/redis/commands/json/json-arrappend">Append values to JSON array</Card>
+<Card title="JSON.ARRINDEX" href="/redis/commands/json/json-arrindex">Find index of value in array</Card>
+<Card title="JSON.ARRINSERT" href="/redis/commands/json/json-arrinsert">Insert values into JSON array</Card>
+<Card title="JSON.ARRLEN" href="/redis/commands/json/json-arrlen">Get JSON array length</Card>
+<Card title="JSON.ARRPOP" href="/redis/commands/json/json-arrpop">Pop value from JSON array</Card>
+<Card title="JSON.ARRTRIM" href="/redis/commands/json/json-arrtrim">Trim JSON array to range</Card>
+<Card title="JSON.CLEAR" href="/redis/commands/json/json-clear">Clear JSON values</Card>
+<Card title="JSON.DEL" href="/redis/commands/json/json-del">Delete JSON values</Card>
+<Card title="JSON.DEBUG" href="/redis/commands/json/json-debug">Inspect JSON memory usage</Card>
+<Card title="JSON.FORGET" href="/redis/commands/json/json-forget">Alias for JSON.DEL</Card>
+<Card title="JSON.GET" href="/redis/commands/json/json-get">Get JSON values</Card>
+<Card title="JSON.MERGE" href="/redis/commands/json/json-merge">Merge JSON values</Card>
+<Card title="JSON.MGET" href="/redis/commands/json/json-mget">Get values from multiple keys</Card>
+<Card title="JSON.MSET" href="/redis/commands/json/json-mset">Set values in multiple keys</Card>
+<Card title="JSON.NUMINCRBY" href="/redis/commands/json/json-numincrby">Increment JSON number</Card>
+<Card title="JSON.NUMMULTBY" href="/redis/commands/json/json-nummultby">Multiply JSON number</Card>
+<Card title="JSON.OBJKEYS" href="/redis/commands/json/json-objkeys">Get JSON object keys</Card>
+<Card title="JSON.OBJLEN" href="/redis/commands/json/json-objlen">Get JSON object size</Card>
+<Card title="JSON.RESP" href="/redis/commands/json/json-resp">Get JSON in RESP format</Card>
+<Card title="JSON.SET" href="/redis/commands/json/json-set">Set JSON value</Card>
+<Card title="JSON.STRAPPEND" href="/redis/commands/json/json-strappend">Append to JSON string</Card>
+<Card title="JSON.STRLEN" href="/redis/commands/json/json-strlen">Get JSON string length</Card>
+<Card title="JSON.TOGGLE" href="/redis/commands/json/json-toggle">Toggle JSON boolean</Card>
+<Card title="JSON.TYPE" href="/redis/commands/json/json-type">Get JSON value type</Card>
+</CardGroup>
+
+# BLMOVE
+Source: https://upstash.com/docs/redis/commands/list/blmove
+
+Use `BLMOVE` to move an element from one list to another, blocking until the source has an element or the timeout expires.
+
+## Syntax
+
+```redis
+BLMOVE <source> <destination> (LEFT | RIGHT) (LEFT | RIGHT) <timeout>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<source>` | Yes | No | Redis key used as source. |
+| `<destination>` | Yes | No | Redis key used as destination. |
+| `(LEFT \| RIGHT)` | Yes | No | Choose one form: `LEFT`; `RIGHT`. |
+| `(LEFT \| RIGHT)` | Yes | No | Choose one form: `LEFT`; `RIGHT`. |
+| `<timeout>` | Yes | No | Seconds to block; `0` blocks indefinitely. |
+
+## Important points
+
+* A blocking form holds the request until data arrives or its timeout expires. Set the client/network timeout longer than the command timeout.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Bulk string or Null bulk string or null array |
+| RESP3 | Bulk string or Null |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+<Note>
+  This command is not supported yet in `upstash_redis`.
+</Note>
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.blmove("source-key", "destination-key", "LEFT", "LEFT", "1.5");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.blMove("source-key", "destination-key", "LEFT", "LEFT", 1.5);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.blmove("source-key", "destination-key", 1.5, "LEFT", "LEFT")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+    "time"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.BLMove(context.Background(), "source-key", "destination-key", "LEFT", "LEFT", 1500*time.Millisecond).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.blmove("source-key", "destination-key", redis.clients.jedis.args.ListDirection.LEFT, redis.clients.jedis.args.ListDirection.LEFT, 1.5);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("BLMOVE");
+    command.arg("source-key");
+    command.arg("destination-key");
+    command.arg("LEFT");
+    command.arg("LEFT");
+    command.arg("1.5");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# BLMPOP
+Source: https://upstash.com/docs/redis/commands/list/blmpop
+
+Use `BLMPOP` to pop elements from the first non-empty list among several, blocking until one has elements or the timeout expires.
+
+## Syntax
+
+```redis
+BLMPOP <timeout> <numkeys> <key> [<key> ...] (LEFT | RIGHT) [COUNT <count>]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<timeout>` | Yes | No | Seconds to block; `0` blocks indefinitely. |
+| `<numkeys>` | Yes | No | Number of key arguments that follow. |
+| `<key>` | Yes | Yes | Redis key targeted by the command. |
+| `(LEFT \| RIGHT)` | Yes | No | Choose one form: `LEFT`; `RIGHT`. |
+| `COUNT <count>` | No | No | Maximum number of elements to pop. |
+
+## Important points
+
+* A blocking form holds the request until data arrives or its timeout expires. Set the client/network timeout longer than the command timeout.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Null bulk string or null array, or two-element array: key and array of values |
+| RESP3 | Null, or two-element array: key and array of values |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+<Note>
+  This command is not supported yet in `upstash_redis`.
+</Note>
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.blmpop("1.5", "1", "my-key", "LEFT");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.blmPop(1.5, "my-key", "LEFT");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.blmpop(1.5, 1, "my-key", direction="LEFT")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+    "time"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    _, result, err := client.BLMPop(context.Background(), 1500*time.Millisecond, "LEFT", 0, "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.blmpop(1.5, redis.clients.jedis.args.ListDirection.LEFT, "my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("BLMPOP");
+    command.arg("1.5");
+    command.arg("1");
+    command.arg("my-key");
+    command.arg("LEFT");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# BLPOP
+Source: https://upstash.com/docs/redis/commands/list/blpop
+
+Use `BLPOP` to pop an element from the head of the first non-empty list, blocking until one has an element or the timeout expires.
+
+## Syntax
+
+```redis
+BLPOP <key> [<key> ...] <timeout>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | Yes | Redis key targeted by the command. |
+| `<timeout>` | Yes | No | Seconds to block; `0` blocks indefinitely. |
+
+## Important points
+
+* A blocking form holds the request until data arrives or its timeout expires. Set the client/network timeout longer than the command timeout.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Null bulk string or null array, or two-element key/value array |
+| RESP3 | Null, or two-element key/value array |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+<Note>
+  This command is not supported yet in `upstash_redis`.
+</Note>
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.blpop("my-key", "1.5");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.blPop("my-key", 1.5);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.blpop(["my-key"], timeout=1.5)
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+    "time"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.BLPop(context.Background(), 1500*time.Millisecond, "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.blpop(1.5, "my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("BLPOP");
+    command.arg("my-key");
+    command.arg("1.5");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# BRPOP
+Source: https://upstash.com/docs/redis/commands/list/brpop
+
+Use `BRPOP` to pop an element from the tail of the first non-empty list, blocking until one has an element or the timeout expires.
+
+## Syntax
+
+```redis
+BRPOP <key> [<key> ...] <timeout>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | Yes | Redis key targeted by the command. |
+| `<timeout>` | Yes | No | Seconds to block; `0` blocks indefinitely. |
+
+## Important points
+
+* A blocking form holds the request until data arrives or its timeout expires. Set the client/network timeout longer than the command timeout.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Null bulk string or null array, or two-element key/value array |
+| RESP3 | Null, or two-element key/value array |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+<Note>
+  This command is not supported yet in `upstash_redis`.
+</Note>
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.brpop("my-key", "1.5");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.brPop("my-key", 1.5);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.brpop(["my-key"], timeout=1.5)
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+    "time"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.BRPop(context.Background(), 1500*time.Millisecond, "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.brpop(1.5, "my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("BRPOP");
+    command.arg("my-key");
+    command.arg("1.5");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# BRPOPLPUSH
+Source: https://upstash.com/docs/redis/commands/list/brpoplpush
+
+Use `BRPOPLPUSH` to pop an element from the tail of one list and push it to the head of another, blocking until the source has an element or the timeout expires.
+
+## Syntax
+
+```redis
+BRPOPLPUSH <source> <destination> <timeout>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<source>` | Yes | No | Redis key used as source. |
+| `<destination>` | Yes | No | Redis key used as destination. |
+| `<timeout>` | Yes | No | Seconds to block; `0` blocks indefinitely. |
+
+## Important points
+
+* A blocking form holds the request until data arrives or its timeout expires. Set the client/network timeout longer than the command timeout.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Bulk string or Null bulk string or null array |
+| RESP3 | Bulk string or Null |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+<Note>
+  This command is not supported yet in `upstash_redis`.
+</Note>
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.brpoplpush("source-key", "destination-key", "1.5");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.brPopLPush("source-key", "destination-key", 1.5);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.brpoplpush("source-key", "destination-key", timeout=1.5)
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+    "time"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.BRPopLPush(context.Background(), "source-key", "destination-key", 1500*time.Millisecond).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.brpoplpush("source-key", "destination-key", 1);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("BRPOPLPUSH");
+    command.arg("source-key");
+    command.arg("destination-key");
+    command.arg("1.5");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# LINDEX
+Source: https://upstash.com/docs/redis/commands/list/lindex
+
+Use `LINDEX` to get element by index.
+
+## Syntax
+
+```redis
+LINDEX <key> <index>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<index>` | Yes | No | Zero-based index; negative values count from the end. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Null bulk string or null array or Bulk string |
+| RESP3 | Null or Bulk string |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.rpush("key", "a", "b", "c");
+const element = await redis.lindex("key", 0);
+console.log(element); // "a"
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.lindex("my-key", 0)
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.lindex("my-key", "0");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.lIndex("my-key", 0);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.lindex("my-key", 0)
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.LIndex(context.Background(), "my-key", 0).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.lindex("my-key", 0);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.lindex("my-key", 0)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# LINSERT
+Source: https://upstash.com/docs/redis/commands/list/linsert
+
+Use `LINSERT` to insert before or after pivot.
+
+## Syntax
+
+```redis
+LINSERT <key> (BEFORE | AFTER) <pivot> <element>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `(BEFORE \| AFTER)` | Yes | No | Choose one form: `BEFORE`; `AFTER`. |
+| `<pivot>` | Yes | No | Existing element to insert next to. |
+| `<element>` | Yes | No | Element to insert. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer: the list length after insertion, `-1` if the pivot was not found, `0` if the key does not exist |
+| RESP3 | Integer: the list length after insertion, `-1` if the pivot was not found, `0` if the key does not exist |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.rpush("key", "a", "b", "c");
+await redis.linsert("key", "before", "b", "x");
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.linsert("my-key", "BEFORE", "pivot", "element")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.linsert("my-key", "BEFORE", "pivot", "element");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.lInsert("my-key", "BEFORE", "pivot", "element");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.linsert("my-key", "BEFORE", "pivot", "element")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.LInsertBefore(context.Background(), "my-key", "pivot", "element").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.linsert("my-key", redis.clients.jedis.args.ListPosition.BEFORE, "pivot", "element");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.linsert_before("my-key", "pivot", "element")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# LLEN
+Source: https://upstash.com/docs/redis/commands/list/llen
+
+Use `LLEN` to get list length.
+
+## Syntax
+
+```redis
+LLEN <key>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.rpush("key", "a", "b", "c");
+const length = await redis.llen("key");
+console.log(length); // 3
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.llen("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.llen("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.lLen("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.llen("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.LLen(context.Background(), "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.llen("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.llen("my-key")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# LMOVE
+Source: https://upstash.com/docs/redis/commands/list/lmove
+
+Use `LMOVE` to move element between lists.
+
+## Syntax
+
+```redis
+LMOVE <source> <destination> (LEFT | RIGHT) (LEFT | RIGHT)
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<source>` | Yes | No | Redis key used as source. |
+| `<destination>` | Yes | No | Redis key used as destination. |
+| `(LEFT \| RIGHT)` | Yes | No | Choose one form: `LEFT`; `RIGHT`. |
+| `(LEFT \| RIGHT)` | Yes | No | Choose one form: `LEFT`; `RIGHT`. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Bulk string |
+| RESP3 | Bulk string |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.rpush("source", "a", "b", "c");
+const element = await redis.lmove("source", "destination", "left", "left");
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.lmove("source-key", "destination-key", "LEFT", "LEFT")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.lmove("source-key", "destination-key", "LEFT", "LEFT");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.lMove("source-key", "destination-key", "LEFT", "LEFT");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.lmove("source-key", "destination-key", "LEFT", "LEFT")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.LMove(context.Background(), "source-key", "destination-key", "LEFT", "LEFT").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.lmove("source-key", "destination-key", redis.clients.jedis.args.ListDirection.LEFT, redis.clients.jedis.args.ListDirection.LEFT);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.lmove("source-key", "destination-key", redis::Direction::Left, redis::Direction::Left)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# LMPOP
+Source: https://upstash.com/docs/redis/commands/list/lmpop
+
+Use `LMPOP` to pop from multiple lists.
+
+## Syntax
+
+```redis
+LMPOP <numkeys> <key> [<key> ...] (LEFT | RIGHT) [COUNT <count>]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<numkeys>` | Yes | No | Number of key arguments that follow. |
+| `<key>` | Yes | Yes | Redis key targeted by the command. |
+| `(LEFT \| RIGHT)` | Yes | No | Choose one form: `LEFT`; `RIGHT`. |
+| `COUNT <count>` | No | No | Maximum number of elements to pop. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Null bulk string or null array, or two-element array: key and array of values |
+| RESP3 | Null, or two-element array: key and array of values |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+const result = await redis.lmpop(1, ["my-key"], "LEFT");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+<Note>
+  This command is not supported yet in `upstash_redis`.
+</Note>
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.lmpop("1", "my-key", "LEFT");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.lmPop("my-key", "LEFT");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.lmpop(1, "my-key", direction="LEFT")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    _, result, err := client.LMPop(context.Background(), "LEFT", 0, "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.lmpop(redis.clients.jedis.args.ListDirection.LEFT, "my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("LMPOP");
+    command.arg("1");
+    command.arg("my-key");
+    command.arg("LEFT");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# LPOP
+Source: https://upstash.com/docs/redis/commands/list/lpop
+
+Use `LPOP` to pop from list head.
+
+## Syntax
+
+```redis
+LPOP <key> [<count>]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<count>` | No | No | Number of elements to pop. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Null bulk string or null array, Bulk string, or array of bulk-string values |
+| RESP3 | Null, Bulk string, or array of bulk-string values |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.rpush("key", "a", "b", "c");
+const element = await redis.lpop("key");
+console.log(element); // "a"
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.lpop("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.lpop("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.lPop("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.lpop("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.LPop(context.Background(), "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.lpop("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result: Option<String> = connection.lpop("my-key", None)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# LPOS
+Source: https://upstash.com/docs/redis/commands/list/lpos
+
+Use `LPOS` to find element position.
+
+## Syntax
+
+```redis
+LPOS <key> <element> [RANK <rank>] [COUNT <num-matches>] [MAXLEN <len>]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<element>` | Yes | No | Element value to search for. |
+| `RANK <rank>` | No | No | Which match to return; negative values search from the tail. |
+| `COUNT <num-matches>` | No | No | Number of matches to return; `0` returns every match. |
+| `MAXLEN <len>` | No | No | Maximum number of entries to keep in the stream. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Null bulk string or null array, Integer, or array of integer positions |
+| RESP3 | Null, Integer, or array of integer positions |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.rpush("key", "a", "b", "c");
+const index = await redis.lpos("key", "b");
+console.log(index); // 1
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.lpos("my-key", "element")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.lpos("my-key", "element");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.lPos("my-key", "element");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.lpos("my-key", "element")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.LPos(context.Background(), "my-key", "element", redis.LPosArgs{}).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.lpos("my-key", "element");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("LPOS");
+    command.arg("my-key");
+    command.arg("element");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# LPUSH
+Source: https://upstash.com/docs/redis/commands/list/lpush
+
+Use `LPUSH` to push to list head.
+
+## Syntax
+
+```redis
+LPUSH <key> <element> [<element> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<element>` | Yes | Yes | Element to push. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const length1 = await redis.lpush("key", "a", "b", "c");
+console.log(length1); // 3
+const length2 = await redis.lpush("key", "d");
+console.log(length2); // 4
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.lpush("my-key", "element")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.lpush("my-key", "element");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.lPush("my-key", "element");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.lpush("my-key", "element")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.LPush(context.Background(), "my-key", "element").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.lpush("my-key", "element");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.lpush("my-key", "element")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# LPUSHX
+Source: https://upstash.com/docs/redis/commands/list/lpushx
+
+Use `LPUSHX` to push to head if list exists.
+
+## Syntax
+
+```redis
+LPUSHX <key> <element> [<element> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<element>` | Yes | Yes | Element to push. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.lpush("key", "a", "b", "c");
+const length = await redis.lpushx("key", "d");
+console.log(length); // 4
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.lpushx("my-key", "element")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.lpushx("my-key", "element");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.lPushX("my-key", "element");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.lpushx("my-key", "element")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.LPushX(context.Background(), "my-key", "element").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.lpushx("my-key", "element");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.lpush_exists("my-key", "element")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# LRANGE
+Source: https://upstash.com/docs/redis/commands/list/lrange
+
+Use `LRANGE` to get range of elements.
+
+## Syntax
+
+```redis
+LRANGE <key> <start> <stop>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<start>` | Yes | No | Start index; negative values count from the end. |
+| `<stop>` | Yes | No | Stop index, inclusive; negative values count from the end. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of bulk-string values |
+| RESP3 | Array of bulk-string values |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.lpush("key", "a", "b", "c");
+const elements = await redis.lrange("key", 1, 2);
+console.log(elements) // ["b", "c"]
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.lrange("my-key", 0, 0)
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.lrange("my-key", "0", "0");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.lRange("my-key", 0, 0);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.lrange("my-key", 0, 0)
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.LRange(context.Background(), "my-key", 0, 0).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.lrange("my-key", 0, 0);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.lrange("my-key", 0, 0)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# LREM
+Source: https://upstash.com/docs/redis/commands/list/lrem
+
+Use `LREM` to remove elements by value.
+
+## Syntax
+
+```redis
+LREM <key> <count> <element>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<count>` | Yes | No | How many matches to remove: positive scans head to tail, negative tail to head, `0` removes every match. |
+| `<element>` | Yes | No | Element value to remove. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.lpush("key", "a", "a", "b", "b", "c");
+const removed = await redis.lrem("key", 4, "b");
+console.log(removed) // 2
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.lrem("my-key", 1, "element")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.lrem("my-key", "1", "element");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.lRem("my-key", 1, "element");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.lrem("my-key", 1, "element")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.LRem(context.Background(), "my-key", 1, "element").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.lrem("my-key", 1, "element");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.lrem("my-key", 1, "element")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# LSET
+Source: https://upstash.com/docs/redis/commands/list/lset
+
+Use `LSET` to set element at index.
+
+## Syntax
+
+```redis
+LSET <key> <index> <element>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<index>` | Yes | No | Zero-based index; negative values count from the end. |
+| `<element>` | Yes | No | Element to store at the index. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Simple string `OK` |
+| RESP3 | Simple string `OK` |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.lpush("key", "a", "b", "c");
+await redis.lset("key", 1, "d");
+
+// list is now ["a", "d", "c"]
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.lset("my-key", 0, "element")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.lset("my-key", "0", "element");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.lSet("my-key", 0, "element");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.lset("my-key", 0, "element")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.LSet(context.Background(), "my-key", 0, "element").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.lset("my-key", 0, "element");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.lset("my-key", 0, "element")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# LTRIM
+Source: https://upstash.com/docs/redis/commands/list/ltrim
+
+Use `LTRIM` to trim list to range.
+
+## Syntax
+
+```redis
+LTRIM <key> <start> <stop>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<start>` | Yes | No | Start index; negative values count from the end. |
+| `<stop>` | Yes | No | Stop index, inclusive; negative values count from the end. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Simple string `OK` |
+| RESP3 | Simple string `OK` |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.lpush("key", "a", "b", "c", "d");
+await redis.ltrim("key", 1, 2);
+// the list is now ["b", "c"]
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.ltrim("my-key", 0, 0)
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.ltrim("my-key", "0", "0");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.lTrim("my-key", 0, 0);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.ltrim("my-key", 0, 0)
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.LTrim(context.Background(), "my-key", 0, 0).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.ltrim("my-key", 0, 0);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.ltrim("my-key", 0, 0)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# List commands
+Source: https://upstash.com/docs/redis/commands/list/overview
+
+<CardGroup cols={2}>
+<Card title="BLMOVE" href="/redis/commands/list/blmove">Blocking list move</Card>
+<Card title="BLMPOP" href="/redis/commands/list/blmpop">Blocking pop from multiple lists</Card>
+<Card title="BLPOP" href="/redis/commands/list/blpop">Blocking left pop</Card>
+<Card title="BRPOP" href="/redis/commands/list/brpop">Blocking right pop</Card>
+<Card title="BRPOPLPUSH" href="/redis/commands/list/brpoplpush">Blocking pop and push</Card>
+<Card title="LINDEX" href="/redis/commands/list/lindex">Get element by index</Card>
+<Card title="LINSERT" href="/redis/commands/list/linsert">Insert before or after pivot</Card>
+<Card title="LLEN" href="/redis/commands/list/llen">Get list length</Card>
+<Card title="LMOVE" href="/redis/commands/list/lmove">Move element between lists</Card>
+<Card title="LMPOP" href="/redis/commands/list/lmpop">Pop from multiple lists</Card>
+<Card title="LPOP" href="/redis/commands/list/lpop">Pop from list head</Card>
+<Card title="LPOS" href="/redis/commands/list/lpos">Find element position</Card>
+<Card title="LPUSH" href="/redis/commands/list/lpush">Push to list head</Card>
+<Card title="LPUSHX" href="/redis/commands/list/lpushx">Push to head if list exists</Card>
+<Card title="LRANGE" href="/redis/commands/list/lrange">Get range of elements</Card>
+<Card title="LREM" href="/redis/commands/list/lrem">Remove elements by value</Card>
+<Card title="LSET" href="/redis/commands/list/lset">Set element at index</Card>
+<Card title="LTRIM" href="/redis/commands/list/ltrim">Trim list to range</Card>
+<Card title="RPOP" href="/redis/commands/list/rpop">Pop from list tail</Card>
+<Card title="RPOPLPUSH" href="/redis/commands/list/rpoplpush">Pop from tail and push to head</Card>
+<Card title="RPUSH" href="/redis/commands/list/rpush">Push to list tail</Card>
+<Card title="RPUSHX" href="/redis/commands/list/rpushx">Push to tail if list exists</Card>
+</CardGroup>
+
+# RPOP
+Source: https://upstash.com/docs/redis/commands/list/rpop
+
+Use `RPOP` to pop from list tail.
+
+## Syntax
+
+```redis
+RPOP <key> [<count>]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<count>` | No | No | Number of elements to pop. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Null bulk string or null array, Bulk string, or array of bulk-string values |
+| RESP3 | Null, Bulk string, or array of bulk-string values |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.rpush("key", "a", "b", "c");
+const element = await redis.rpop("key");
+console.log(element); // "c"
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.rpop("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.rpop("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.rPop("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.rpop("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.RPop(context.Background(), "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.rpop("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result: Option<String> = connection.rpop("my-key", None)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# RPOPLPUSH
+Source: https://upstash.com/docs/redis/commands/list/rpoplpush
+
+Use `RPOPLPUSH` to pop from tail and push to head.
+
+## Syntax
+
+```redis
+RPOPLPUSH <source> <destination>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<source>` | Yes | No | Redis key used as source. |
+| `<destination>` | Yes | No | Redis key used as destination. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Bulk string or Null bulk string or null array |
+| RESP3 | Bulk string or Null |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.rpoplpush("source-key", "destination-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.rpoplpush("source-key", "destination-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.rPopLPush("source-key", "destination-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.rpoplpush("source-key", "destination-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.RPopLPush(context.Background(), "source-key", "destination-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.rpoplpush("source-key", "destination-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.rpoplpush("source-key", "destination-key")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# RPUSH
+Source: https://upstash.com/docs/redis/commands/list/rpush
+
+Use `RPUSH` to push to list tail.
+
+## Syntax
+
+```redis
+RPUSH <key> <element> [<element> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<element>` | Yes | Yes | Element to push. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const length1 = await redis.rpush("key", "a", "b", "c");
+console.log(length1); // 3
+const length2 = await redis.rpush("key", "d");
+console.log(length2); // 4
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.rpush("my-key", "element")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.rpush("my-key", "element");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.rPush("my-key", "element");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.rpush("my-key", "element")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.RPush(context.Background(), "my-key", "element").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.rpush("my-key", "element");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.rpush("my-key", "element")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# RPUSHX
+Source: https://upstash.com/docs/redis/commands/list/rpushx
+
+Use `RPUSHX` to push to tail if list exists.
+
+## Syntax
+
+```redis
+RPUSHX <key> <element> [<element> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<element>` | Yes | Yes | Element to push. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.lpush("key", "a", "b", "c");
+const length = await redis.rpushx("key", "d");
+console.log(length); // 4
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.rpushx("my-key", "element")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.rpushx("my-key", "element");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.rPushX("my-key", "element");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.rpushx("my-key", "element")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.RPushX(context.Background(), "my-key", "element").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.rpushx("my-key", "element");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.rpush_exists("my-key", "element")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# Redis command reference
+Source: https://upstash.com/docs/redis/commands/overview
+
+Upstash supports Redis commands over both native Redis TCP and HTTPS REST. Choose a category to browse its supported commands.
+
+<CardGroup cols={2}>
+<Card title="Bitmap" icon="grid" href="/redis/commands/bitmap/overview" horizontal>Manipulate individual bits and bit fields</Card>
+<Card title="Connection" icon="plug" href="/redis/commands/connection/overview" horizontal>Authenticate and manage client connections</Card>
+<Card title="Functions" icon="code" href="/redis/commands/functions/overview" horizontal>Load, manage, and invoke Redis functions</Card>
+<Card title="Generic" icon="sliders" href="/redis/commands/generic/overview" horizontal>Manage keys, expiration, and serialization</Card>
+<Card title="Geo" icon="location-dot" href="/redis/commands/geo/overview" horizontal>Store and query geospatial data</Card>
+<Card title="Hash" icon="hashtag" href="/redis/commands/hash/overview" horizontal>Work with field-value collections</Card>
+<Card title="HyperLogLog" icon="chart-simple" href="/redis/commands/hyperloglog/overview" horizontal>Estimate cardinality</Card>
+<Card title="JSON" icon="brackets-curly" href="/redis/commands/json/overview" horizontal>Store and manipulate JSON values</Card>
+<Card title="List" icon="list" href="/redis/commands/list/overview" horizontal>Work with ordered collections</Card>
+<Card title="Pub/Sub" icon="tower-broadcast" href="/redis/commands/pub-sub/overview" horizontal>Publish messages and manage subscriptions</Card>
+<Card title="Scripting" icon="scroll" href="/redis/commands/scripting/overview" horizontal>Load and execute Lua scripts</Card>
+<Card title="Search" icon="magnifying-glass" href="/redis/commands/search/overview" horizontal>Create, query, and manage search indexes</Card>
+<Card title="Server" icon="server" href="/redis/commands/server/overview" horizontal>Inspect and manage the Redis server</Card>
+<Card title="Set" icon="layer-group" href="/redis/commands/set/overview" horizontal>Work with unique unordered members</Card>
+<Card title="Sorted Set" icon="arrow-down-1-9" href="/redis/commands/sorted-set/overview" horizontal>Work with scored collections</Card>
+<Card title="Streams" icon="water" href="/redis/commands/streams/overview" horizontal>Process append-only logs and consumer groups</Card>
+<Card title="String" icon="font" href="/redis/commands/string/overview" horizontal>Store and manipulate string values</Card>
+<Card title="Transactions" icon="right-left" href="/redis/commands/transactions/overview" horizontal>Group operations into atomic transactions</Card>
+</CardGroup>
+
+# Pub/Sub commands
+Source: https://upstash.com/docs/redis/commands/pub-sub/overview
+
+<CardGroup cols={2}>
+<Card title="PSUBSCRIBE" href="/redis/commands/pub-sub/psubscribe">Subscribe to pattern channels</Card>
+<Card title="PUBLISH" href="/redis/commands/pub-sub/publish">Publish message to channel</Card>
+<Card title="PUBSUB" href="/redis/commands/pub-sub/pubsub">Inspect pub/sub state</Card>
+<Card title="PUNSUBSCRIBE" href="/redis/commands/pub-sub/punsubscribe">Unsubscribe from patterns</Card>
+<Card title="SUBSCRIBE" href="/redis/commands/pub-sub/subscribe">Subscribe to channels</Card>
+<Card title="UNSUBSCRIBE" href="/redis/commands/pub-sub/unsubscribe">Unsubscribe from channels</Card>
+</CardGroup>
+
+# PSUBSCRIBE
+Source: https://upstash.com/docs/redis/commands/pub-sub/psubscribe
+
+Use `PSUBSCRIBE` to subscribe to pattern channels.
+
+## Syntax
+
+```redis
+PSUBSCRIBE <pattern> [<pattern> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<pattern>` | Yes | Yes | Glob-style channel pattern. |
+
+## Important points
+
+* This is a connection-oriented command and is available over native Redis TCP, not the stateless REST endpoint.
+* Subscription commands require a dedicated TCP connection. In RESP3, subscription events use push replies.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Three-element subscription-state array per pattern |
+| RESP3 | Three-element subscription-state push reply per pattern |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const subscriber = new Redis(process.env.REDIS_URL!);
+await subscriber.psubscribe("events:*");
+subscriber.on("message", (channel, message) => console.log(channel, message));
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const subscriber = await createClient({ url: process.env.REDIS_URL }).connect();
+await subscriber.pSubscribe("events:*", (message, channel) => {
+  console.log(channel, message);
+});
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+pubsub = client.pubsub()
+pubsub.psubscribe("events:*")
+for message in pubsub.listen():
+    print(message)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    ctx := context.Background()
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    pubsub := client.PSubscribe(ctx, "events:*")
+    for message := range pubsub.Channel() {
+        fmt.Println(message.Channel, message.Payload)
+    }
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+import redis.clients.jedis.Jedis;
+import redis.clients.jedis.JedisPubSub;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  jedis.psubscribe(new JedisPubSub() {
+    @Override
+    public void onPMessage(String pattern, String channel, String message) {
+      System.out.println(channel + ": " + message);
+    }
+  }, "events:*");
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+    let mut pubsub = connection.as_pubsub();
+    pubsub.psubscribe("events:*")?;
+    loop {
+        let message = pubsub.get_message()?;
+        let payload: String = message.get_payload()?;
+        println!("{payload}");
+    }
+    #[allow(unreachable_code)]
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# PUBLISH
+Source: https://upstash.com/docs/redis/commands/pub-sub/publish
+
+Use `PUBLISH` to publish message to channel.
+
+## Syntax
+
+```redis
+PUBLISH <channel> <message>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<channel>` | Yes | No | Channel name. |
+| `<message>` | Yes | No | Message payload. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const listeners = await redis.publish("my-channel", "my-message");
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.publish("events", "hello")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.publish("events", "hello");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.publish("events", "hello");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.publish("events", "hello")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.Publish(context.Background(), "events", "hello").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.publish("events", "hello");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.publish("events", "hello")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# PUBSUB
+Source: https://upstash.com/docs/redis/commands/pub-sub/pubsub
+
+Use `PUBSUB` to inspect pub/sub state.
+
+## Syntax
+
+```redis
+PUBSUB CHANNELS [pattern]
+PUBSUB NUMSUB [channel ...]
+PUBSUB NUMPAT
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `CHANNELS [pattern]` | One form | No | List active channels, optionally filtered by a glob-style pattern. |
+| `NUMSUB [channel ...]` | One form | Yes | Return subscriber counts for the supplied channels. |
+| `NUMPAT` | One form | No | Return the number of active pattern subscriptions. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of channel names, flat channel/count array, or Integer |
+| RESP3 | Array of channel names, flat channel/count array, or Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+<Note>
+  This command is not supported yet in `upstash_redis`.
+</Note>
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.pubsub("CHANNELS", "events:*");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.pubSubChannels("events:*");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.pubsub_channels("events:*")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.PubSubChannels(context.Background(), "events:*").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.pubsubChannels("events:*");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("PUBSUB");
+    command.arg("CHANNELS");
+    command.arg("events:*");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# PUNSUBSCRIBE
+Source: https://upstash.com/docs/redis/commands/pub-sub/punsubscribe
+
+Use `PUNSUBSCRIBE` to unsubscribe from patterns.
+
+## Syntax
+
+```redis
+PUNSUBSCRIBE [<pattern> [<pattern> ...]]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<pattern>` | No | Yes | Glob-style channel pattern; omit to unsubscribe from all patterns. |
+
+## Important points
+
+* This is a connection-oriented command and is available over native Redis TCP, not the stateless REST endpoint.
+* Subscription commands require a dedicated TCP connection. In RESP3, subscription events use push replies.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Three-element subscription-state array per pattern |
+| RESP3 | Three-element subscription-state push reply per pattern |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const subscriber = new Redis(process.env.REDIS_URL!);
+await subscriber.psubscribe("events:*");
+await subscriber.punsubscribe("events:*");
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const subscriber = await createClient({ url: process.env.REDIS_URL }).connect();
+await subscriber.pSubscribe("events:*", console.log);
+await subscriber.pUnsubscribe("events:*");
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+pubsub = client.pubsub()
+pubsub.psubscribe("events:*")
+pubsub.punsubscribe("events:*")
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    ctx := context.Background()
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    pubsub := client.PSubscribe(ctx, "events:*")
+    if err := pubsub.PUnsubscribe(ctx, "events:*"); err != nil {
+        panic(err)
+    }
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+import redis.clients.jedis.Jedis;
+import redis.clients.jedis.JedisPubSub;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  jedis.psubscribe(new JedisPubSub() {
+    @Override
+    public void onPMessage(String pattern, String channel, String message) {
+      punsubscribe();
+    }
+  }, "events:*");
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+    let mut pubsub = connection.as_pubsub();
+    pubsub.psubscribe("events:*")?;
+    pubsub.punsubscribe("events:*")?;
+    #[allow(unreachable_code)]
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# SUBSCRIBE
+Source: https://upstash.com/docs/redis/commands/pub-sub/subscribe
+
+Use `SUBSCRIBE` to subscribe to channels.
+
+## Syntax
+
+```redis
+SUBSCRIBE <channel> [<channel> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<channel>` | Yes | Yes | Channel name. |
+
+## Important points
+
+* This is a connection-oriented command and is available over native Redis TCP, not the stateless REST endpoint.
+* Subscription commands require a dedicated TCP connection. In RESP3, subscription events use push replies.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Three-element subscription-state array per channel |
+| RESP3 | Three-element subscription-state push reply per channel |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const subscriber = new Redis(process.env.REDIS_URL!);
+await subscriber.subscribe("events");
+subscriber.on("message", (channel, message) => console.log(channel, message));
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const subscriber = await createClient({ url: process.env.REDIS_URL }).connect();
+await subscriber.subscribe("events", (message, channel) => {
+  console.log(channel, message);
+});
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+pubsub = client.pubsub()
+pubsub.subscribe("events")
+for message in pubsub.listen():
+    print(message)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    ctx := context.Background()
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    pubsub := client.Subscribe(ctx, "events")
+    for message := range pubsub.Channel() {
+        fmt.Println(message.Channel, message.Payload)
+    }
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+import redis.clients.jedis.Jedis;
+import redis.clients.jedis.JedisPubSub;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  jedis.subscribe(new JedisPubSub() {
+    @Override
+    public void onMessage(String channel, String message) {
+      System.out.println(channel + ": " + message);
+    }
+  }, "events");
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+    let mut pubsub = connection.as_pubsub();
+    pubsub.subscribe("events")?;
+    loop {
+        let message = pubsub.get_message()?;
+        let payload: String = message.get_payload()?;
+        println!("{payload}");
+    }
+    #[allow(unreachable_code)]
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# UNSUBSCRIBE
+Source: https://upstash.com/docs/redis/commands/pub-sub/unsubscribe
+
+Use `UNSUBSCRIBE` to unsubscribe from channels.
+
+## Syntax
+
+```redis
+UNSUBSCRIBE [<channel> [<channel> ...]]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<channel>` | No | Yes | Channel name. |
+
+## Important points
+
+* This is a connection-oriented command and is available over native Redis TCP, not the stateless REST endpoint.
+* Subscription commands require a dedicated TCP connection. In RESP3, subscription events use push replies.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Three-element subscription-state array per channel |
+| RESP3 | Three-element subscription-state push reply per channel |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const subscriber = new Redis(process.env.REDIS_URL!);
+await subscriber.subscribe("events");
+await subscriber.unsubscribe("events");
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const subscriber = await createClient({ url: process.env.REDIS_URL }).connect();
+await subscriber.subscribe("events", console.log);
+await subscriber.unsubscribe("events");
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+pubsub = client.pubsub()
+pubsub.subscribe("events")
+pubsub.unsubscribe("events")
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    ctx := context.Background()
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    pubsub := client.Subscribe(ctx, "events")
+    if err := pubsub.Unsubscribe(ctx, "events"); err != nil {
+        panic(err)
+    }
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+import redis.clients.jedis.Jedis;
+import redis.clients.jedis.JedisPubSub;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  jedis.subscribe(new JedisPubSub() {
+    @Override
+    public void onMessage(String channel, String message) {
+      unsubscribe();
+    }
+  }, "events");
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+    let mut pubsub = connection.as_pubsub();
+    pubsub.subscribe("events")?;
+    pubsub.unsubscribe("events")?;
+    #[allow(unreachable_code)]
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# EVAL
+Source: https://upstash.com/docs/redis/commands/scripting/eval
+
+Use `EVAL` to execute a Lua script.
+
+## Syntax
+
+```redis
+EVAL <script> <numkeys> [<key> [<key> ...]] [<arg> [<arg> ...]]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<script>` | Yes | No | Lua script source. |
+| `<numkeys>` | Yes | No | Number of key arguments that follow. |
+| `<key>` | No | Yes | Redis key targeted by the command. |
+| `<arg>` | No | Yes | Additional argument, available to the script as `ARGV`. |
+
+## Important points
+
+* `numkeys` must equal the number of key arguments that immediately follow it; remaining arguments are available to the script or function as ordinary arguments.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Reply produced by the evaluated script |
+| RESP3 | Reply produced by the evaluated script |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const script = `
+    return ARGV[1]
+`
+const result = await redis.eval(script, [], ["hello"]);
+console.log(result) // "hello"
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.eval("return ARGV[1]", args=["value"])
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.eval("return ARGV[1]", "0", "value");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.eval("return ARGV[1]", { arguments: ["value"] });
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.eval("return ARGV[1]", 0, "value")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.Eval(context.Background(), "return ARGV[1]", nil, "value").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.eval("return ARGV[1]", java.util.List.of(), java.util.List.of("value"));
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("EVAL");
+    command.arg("return ARGV[1]");
+    command.arg("1");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# EVAL_RO
+Source: https://upstash.com/docs/redis/commands/scripting/eval-ro
+
+Use `EVAL_RO` to execute read-only Lua script.
+
+## Syntax
+
+```redis
+EVAL_RO <script> <numkeys> [<key> [<key> ...]] [<arg> [<arg> ...]]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<script>` | Yes | No | Lua script source. |
+| `<numkeys>` | Yes | No | Number of key arguments that follow. |
+| `<key>` | No | Yes | Redis key targeted by the command. |
+| `<arg>` | No | Yes | Additional argument, available to the script as `ARGV`. |
+
+## Important points
+
+* `numkeys` must equal the number of key arguments that immediately follow it; remaining arguments are available to the script or function as ordinary arguments.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Reply produced by the evaluated read-only script |
+| RESP3 | Reply produced by the evaluated read-only script |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const script = `
+    return ARGV[1]
+`
+const result = await redis.evalRo(script, [], ["hello"]);
+console.log(result) // "hello"
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.eval_ro("return ARGV[1]", args=["value"])
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.eval_ro("return ARGV[1]", "0", "value");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.evalRo("return ARGV[1]", { arguments: ["value"] });
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.eval_ro("return ARGV[1]", 0, "value")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.EvalRO(context.Background(), "return ARGV[1]", nil, "value").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.evalReadonly("return ARGV[1]", java.util.List.of(), java.util.List.of("value"));
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("EVAL_RO");
+    command.arg("return ARGV[1]");
+    command.arg("1");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# EVALSHA
+Source: https://upstash.com/docs/redis/commands/scripting/evalsha
+
+Use `EVALSHA` to execute cached Lua script by SHA.
+
+## Syntax
+
+```redis
+EVALSHA <sha1> <numkeys> [<key> [<key> ...]] [<arg> [<arg> ...]]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<sha1>` | Yes | No | SHA1 digest of a script cached with `SCRIPT LOAD`. |
+| `<numkeys>` | Yes | No | Number of key arguments that follow. |
+| `<key>` | No | Yes | Redis key targeted by the command. |
+| `<arg>` | No | Yes | Additional argument, available to the script as `ARGV`. |
+
+## Important points
+
+* `numkeys` must equal the number of key arguments that immediately follow it; remaining arguments are available to the script or function as ordinary arguments.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Reply produced by the cached script |
+| RESP3 | Reply produced by the cached script |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const result = await redis.evalsha("fb67a0c03b48ddbf8b4c9b011e779563bdbc28cb", [], ["hello"]);
+console.log(result) // "hello"
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.evalsha("<sha1>", args=["value"])
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.evalsha("<sha1>", "0", "value");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.evalSha("<sha1>", { arguments: ["value"] });
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.evalsha("<sha1>", 0, "value")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.EvalSha(context.Background(), "<sha1>", nil, "value").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.evalsha("<sha1>", java.util.List.of(), java.util.List.of("value"));
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("EVALSHA");
+    command.arg("<sha1>");
+    command.arg("1");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# EVALSHA_RO
+Source: https://upstash.com/docs/redis/commands/scripting/evalsha-ro
+
+Use `EVALSHA_RO` to run a script cached by its SHA1 digest. The script may not write to the database.
+
+## Syntax
+
+```redis
+EVALSHA_RO <sha1> <numkeys> [<key> [<key> ...]] [<arg> [<arg> ...]]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<sha1>` | Yes | No | SHA1 digest of a script cached with `SCRIPT LOAD`. |
+| `<numkeys>` | Yes | No | Number of key arguments that follow. |
+| `<key>` | No | Yes | Redis key targeted by the command. |
+| `<arg>` | No | Yes | Additional argument, available to the script as `ARGV`. |
+
+## Important points
+
+* `numkeys` must equal the number of key arguments that immediately follow it; remaining arguments are available to the script or function as ordinary arguments.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Reply produced by the cached read-only script |
+| RESP3 | Reply produced by the cached read-only script |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const result = await redis.evalshaRo("fb67a0c03b48ddbf8b4c9b011e779563bdbc28cb", [], ["hello"]);
+console.log(result) // "hello"
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.evalsha_ro("<sha1>", args=["value"])
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.evalsha_ro("<sha1>", "0", "value");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.evalShaRo("<sha1>", { arguments: ["value"] });
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.evalsha_ro("<sha1>", 0, "value")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.EvalShaRO(context.Background(), "<sha1>", nil, "value").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.evalshaReadonly("<sha1>", java.util.List.of(), java.util.List.of("value"));
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("EVALSHA_RO");
+    command.arg("<sha1>");
+    command.arg("1");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# Scripting commands
+Source: https://upstash.com/docs/redis/commands/scripting/overview
+
+<CardGroup cols={2}>
+<Card title="EVAL" href="/redis/commands/scripting/eval">Execute a Lua script</Card>
+<Card title="EVAL_RO" href="/redis/commands/scripting/eval-ro">Execute read-only Lua script</Card>
+<Card title="EVALSHA" href="/redis/commands/scripting/evalsha">Execute cached Lua script by SHA</Card>
+<Card title="EVALSHA_RO" href="/redis/commands/scripting/evalsha-ro">Read-only execute by SHA</Card>
+<Card title="SCRIPT EXISTS" href="/redis/commands/scripting/script-exists">Check if scripts exist in cache</Card>
+<Card title="SCRIPT FLUSH" href="/redis/commands/scripting/script-flush">Clear the script cache</Card>
+<Card title="SCRIPT KILL" href="/redis/commands/scripting/script-kill">Stop a running read-only script</Card>
+<Card title="SCRIPT LOAD" href="/redis/commands/scripting/script-load">Load script into cache</Card>
+</CardGroup>
+
+# SCRIPT EXISTS
+Source: https://upstash.com/docs/redis/commands/scripting/script-exists
+
+Use `SCRIPT EXISTS` to check if scripts exist in cache.
+
+## Syntax
+
+```redis
+SCRIPT EXISTS <sha1> [<sha1> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<sha1>` | Yes | Yes | SHA1 digest of a script cached with `SCRIPT LOAD`. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of integers, one per SHA1 digest |
+| RESP3 | Array of integers, one per SHA1 digest |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.scriptExists("<sha1>", "<sha2>")
+
+// Returns 1
+// [1, 0]
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.script_exists("<sha1>")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.script("EXISTS", "<sha1>");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.scriptExists("<sha1>");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.script_exists("<sha1>")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ScriptExists(context.Background(), "<sha1>").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.scriptExists("<sha1>");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("SCRIPT");
+    command.arg("EXISTS");
+    command.arg("<sha1>");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# SCRIPT FLUSH
+Source: https://upstash.com/docs/redis/commands/scripting/script-flush
+
+Use `SCRIPT FLUSH` to clear the script cache.
+
+## Syntax
+
+```redis
+SCRIPT FLUSH [ASYNC | SYNC]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `(ASYNC \| SYNC)` | No | No | Choose one form: `ASYNC` (request asynchronous cleanup); `SYNC` (request synchronous cleanup). |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Simple string `OK` |
+| RESP3 | Simple string `OK` |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.scriptFlush();
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.script_flush()
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.script("FLUSH");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.scriptFlush();
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.script_flush()
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ScriptFlush(context.Background()).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.scriptFlush();
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("SCRIPT");
+    command.arg("FLUSH");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# SCRIPT KILL
+Source: https://upstash.com/docs/redis/commands/scripting/script-kill
+
+Use `SCRIPT KILL` to stop a running read-only script.
+
+## Syntax
+
+```redis
+SCRIPT KILL
+```
+
+## Arguments
+
+This command takes no arguments.
+
+## Important points
+
+* The current deployment recognizes this command but reports `NOTBUSY` because it does not expose an interruptible running-script state.
+* As with Redis, a script that has already performed writes must not be killed because doing so would violate atomicity.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Error reply (`NOTBUSY` on the current deployment) |
+| RESP3 | Error reply (`NOTBUSY` on the current deployment) |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+<Note>
+  This command is not supported yet in `upstash_redis`.
+</Note>
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.script("KILL");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.scriptKill();
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.script_kill()
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ScriptKill(context.Background()).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.scriptKill();
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("SCRIPT");
+    command.arg("KILL");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# SCRIPT LOAD
+Source: https://upstash.com/docs/redis/commands/scripting/script-load
+
+Use `SCRIPT LOAD` to load script into cache.
+
+## Syntax
+
+```redis
+SCRIPT LOAD <script>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<script>` | Yes | No | Lua script source. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Bulk string |
+| RESP3 | Bulk string |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const script = `
+  local value = redis.call('GET', KEYS[1])
+  return value
+`;
+const sha1 = await redis.scriptLoad(script);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.script_load("return ARGV[1]")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.script("LOAD", "return ARGV[1]");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.scriptLoad("return ARGV[1]");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.script_load("return ARGV[1]")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ScriptLoad(context.Background(), "return ARGV[1]").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.scriptLoad("return ARGV[1]");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("SCRIPT");
+    command.arg("LOAD");
+    command.arg("return ARGV[1]");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# Search commands
+Source: https://upstash.com/docs/redis/commands/search/overview
+
+<Note>
+  Upstash Redis Search uses `SEARCH.*` commands. They are separate from and incompatible with the `FT.*` commands in the open-source RediSearch module.
+</Note>
+
+For Search commands, use the Upstash [`@upstash/redis`](/docs/redis/sdks/ts/overview) or [`upstash-redis`](/docs/redis/sdks/py/overview) SDK,
+or the redis-js wrappers [`@upstash/search-redis`](/docs/redis/search/adapters/node-redis) for node-redis and [`@upstash/search-ioredis`](/docs/redis/search/adapters/ioredis) for ioredis.
+
+For feature guides and tutorials, start with the [Upstash Redis Search introduction](/docs/redis/search/introduction).
+
+<CardGroup cols={2}>
+<Card title="SEARCH.CREATE" href="/redis/commands/search/search-create">Create a search index</Card>
+<Card title="SEARCH.REINDEX" href="/redis/commands/search/search-reindex">Rebuild a search index from the current data</Card>
+<Card title="SEARCH.DROP" href="/redis/commands/search/search-drop">Remove a search index</Card>
+<Card title="SEARCH.DESCRIBE" href="/redis/commands/search/search-describe">Return metadata about a search index</Card>
+<Card title="SEARCH.WAITINDEXING" href="/redis/commands/search/search-waitindexing">Wait until pending index updates are visible</Card>
+<Card title="SEARCH.LISTINDEXES" href="/redis/commands/search/search-listindexes">List search indexes in the database</Card>
+<Card title="SEARCH.QUERY" href="/redis/commands/search/search-query">Search documents with a JSON filter</Card>
+<Card title="SEARCH.COUNT" href="/redis/commands/search/search-count">Count matching documents</Card>
+<Card title="SEARCH.AGGREGATE" href="/redis/commands/search/search-aggregate">Compute analytics over matching documents</Card>
+<Card title="SEARCH.ALIASADD" href="/redis/commands/search/search-aliasadd">Add or update an index alias</Card>
+<Card title="SEARCH.ALIASDEL" href="/redis/commands/search/search-aliasdel">Remove an index alias</Card>
+<Card title="SEARCH.LISTALIASES" href="/redis/commands/search/search-listaliases">List index aliases</Card>
+</CardGroup>
+
+`SEARCH.QUERY`, `SEARCH.COUNT`, `SEARCH.AGGREGATE`, `SEARCH.DESCRIBE`, `SEARCH.WAITINDEXING`, and `SEARCH.REINDEX` accept either an index name or alias. `SEARCH.DROP` always treats its argument as a literal index name. This makes it possible to switch an alias to a replacement index and then drop the old index without dropping the replacement.
+
+## REST API Usage
+
+All search commands can be sent via the Upstash REST API using a JSON array POST body.
+Each element of the array corresponds to a token in the command.
+
+```bash
+curl -X POST https://YOUR_ENDPOINT.upstash.io \
+  -H "Authorization: Bearer $UPSTASH_REDIS_REST_TOKEN" \
+  -d '["COMMAND", "arg1", "arg2", ...]'
+```
+
+The JSON filter and aggregation arguments are passed as string values within the array (not as nested JSON objects):
+
+```bash
+# Correct — filter is a string inside the array
+["SEARCH.QUERY", "products", "{\"name\": \"wireless\"}", "LIMIT", "10"]
+
+# Incorrect — filter is a nested object
+["SEARCH.QUERY", "products", {"name": "wireless"}, "LIMIT", "10"]
+```
+
+Pass JSON filter and aggregation arguments as string values inside the array, not as nested JSON objects.
+Search commands also work through the `/pipeline` endpoint for batching multiple commands in a single HTTP request.
+
+# SEARCH.AGGREGATE
+Source: https://upstash.com/docs/redis/commands/search/search-aggregate
+
+Use `SEARCH.AGGREGATE` to compute metrics and buckets over matching documents.
+
+## Syntax
+
+```redis
+SEARCH.AGGREGATE <name> '<json_filter>' '<json_aggregations>'
+```
+
+`<json_filter>` is an [Upstash JSON filter](/docs/redis/search/querying). The command accepts an index name or alias. See [Aggregations](/docs/redis/search/aggregations) for the aggregation object and supported operators.
+
+## Response
+
+In `redis-cli --json`, the response is an object keyed by aggregation alias:
+
+```json
+{
+  "avg_price": { "value": 49.99 },
+  "by_category": { "buckets": [{ "key": "electronics", "docCount": 42 }] }
+}
+```
+
+Raw RESP output may be rendered differently by client or protocol settings, but each top-level alias maps to its aggregation result. Returns `null` if the index does not exist.
+
+## Examples
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+const products = redis.search.index({ name: "products" });
+
+const result = await products.aggregate({
+  aggregations: {
+    avg_price: { $avg: { field: "price" } },
+  },
+});
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+products = redis.search.index(name="products")
+
+result = products.aggregate(
+    aggregations={"avg_price": {"$avg": {"field": "price"}}},
+)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import IORedis from "ioredis";
+import { createSearch } from "@upstash/search-ioredis";
+
+const redis = new IORedis(process.env.REDIS_URL!);
+const search = createSearch(redis);
+const products = search.index({ name: "products" });
+
+const result = await products.aggregate({
+  aggregations: {
+    avg_price: { $avg: { field: "price" } },
+  },
+});
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+import { createSearch } from "@upstash/search-redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const search = createSearch(client);
+const products = search.index({ name: "products" });
+
+const result = await products.aggregate({
+  aggregations: {
+    avg_price: { $avg: { field: "price" } },
+  },
+});
+```
+
+</Tab>
+
+<Tab title="Redis CLI">
+
+```bash
+SEARCH.AGGREGATE products '{}' '{"avg_price": {"$avg": {"field": "price"}}}'
+```
+
+</Tab>
+
+<Tab title="curl">
+
+```bash
+curl -X POST https://YOUR_ENDPOINT.upstash.io \
+  -H "Authorization: Bearer $UPSTASH_REDIS_REST_TOKEN" \
+  -d '["SEARCH.AGGREGATE", "products", "{}", "{\"avg_price\": {\"$avg\": {\"field\": \"price\"}}}"]'
+```
+
+</Tab>
+
+</Tabs>
+
+# SEARCH.ALIASADD
+Source: https://upstash.com/docs/redis/commands/search/search-aliasadd
+
+Use `SEARCH.ALIASADD` to create an alias or update an existing alias to point to a search index.
+
+See [Aliases](/docs/redis/search/aliases#adding-an-alias) for feature examples, including zero-downtime index swaps.
+
+The target name is not required to exist when the alias is created, so aliases can temporarily be dangling. Most commands resolve aliases, but [`SEARCH.DROP`](/docs/redis/commands/search/search-drop) always uses a literal index name.
+
+## Syntax
+
+```redis
+SEARCH.ALIASADD <alias> <index_name>
+```
+
+## Response
+
+Returns `1` if a new alias was created or `2` if an existing alias was updated, including when it already points to the supplied index.
+
+## Examples
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+const result = await redis.search.alias.add({
+  alias: "products",
+  indexName: "products-v2",
+});
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.search.alias.add(
+    alias="products",
+    index_name="products-v2",
+)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import IORedis from "ioredis";
+import { createSearch } from "@upstash/search-ioredis";
+
+const redis = new IORedis(process.env.REDIS_URL!);
+const search = createSearch(redis);
+const result = await search.alias.add({
+  alias: "products",
+  indexName: "products-v2",
+});
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+import { createSearch } from "@upstash/search-redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const search = createSearch(client);
+const result = await search.alias.add({
+  alias: "products",
+  indexName: "products-v2",
+});
+```
+
+</Tab>
+
+<Tab title="Redis CLI">
+
+```bash
+SEARCH.ALIASADD products products-v2
+```
+
+</Tab>
+
+<Tab title="curl">
+
+```bash
+curl -X POST https://YOUR_ENDPOINT.upstash.io \
+  -H "Authorization: Bearer $UPSTASH_REDIS_REST_TOKEN" \
+  -d '["SEARCH.ALIASADD", "products", "products-v2"]'
+```
+
+</Tab>
+
+</Tabs>
+
+# SEARCH.ALIASDEL
+Source: https://upstash.com/docs/redis/commands/search/search-aliasdel
+
+Use `SEARCH.ALIASDEL` to remove a search index alias.
+
+See [Deleting an Alias](/docs/redis/search/aliases#deleting-an-alias) for the feature guide.
+
+## Syntax
+
+```redis
+SEARCH.ALIASDEL <alias>
+```
+
+## Response
+
+Returns `1` if the alias was deleted or `0` if the alias was not found.
+
+## Examples
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+const result = await redis.search.alias.delete({ alias: "products" });
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.search.alias.delete(alias="products")
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import IORedis from "ioredis";
+import { createSearch } from "@upstash/search-ioredis";
+
+const redis = new IORedis(process.env.REDIS_URL!);
+const search = createSearch(redis);
+const result = await search.alias.delete({ alias: "products" });
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+import { createSearch } from "@upstash/search-redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const search = createSearch(client);
+const result = await search.alias.delete({ alias: "products" });
+```
+
+</Tab>
+
+<Tab title="Redis CLI">
+
+```bash
+SEARCH.ALIASDEL products
+```
+
+</Tab>
+
+<Tab title="curl">
+
+```bash
+curl -X POST https://YOUR_ENDPOINT.upstash.io \
+  -H "Authorization: Bearer $UPSTASH_REDIS_REST_TOKEN" \
+  -d '["SEARCH.ALIASDEL", "products"]'
+```
+
+</Tab>
+
+</Tabs>
+
+# SEARCH.COUNT
+Source: https://upstash.com/docs/redis/commands/search/search-count
+
+Use `SEARCH.COUNT` to count documents matching a query without retrieving them.
+
+See [Counting](/docs/redis/search/counting) for feature examples and common use cases.
+
+## Syntax
+
+```redis
+SEARCH.COUNT <name> '<json_filter>'
+```
+
+`<json_filter>` is an [Upstash JSON filter](/docs/redis/search/querying). The command accepts an index name or alias.
+
+## Response
+
+Returns the number of matching documents as an integer. Returns `-1` if the index does not exist.
+
+## Examples
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+const products = redis.search.index({ name: "products" });
+
+const result = await products.count({
+  filter: { inStock: true },
+});
+console.log(result.count);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+products = redis.search.index(name="products")
+
+result = products.count(filter={"inStock": True})
+print(result.count)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import IORedis from "ioredis";
+import { createSearch } from "@upstash/search-ioredis";
+
+const redis = new IORedis(process.env.REDIS_URL!);
+const search = createSearch(redis);
+const products = search.index({ name: "products" });
+
+const result = await products.count({
+  filter: { inStock: true },
+});
+console.log(result.count);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+import { createSearch } from "@upstash/search-redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const search = createSearch(client);
+const products = search.index({ name: "products" });
+
+const result = await products.count({
+  filter: { inStock: true },
+});
+console.log(result.count);
+```
+
+</Tab>
+
+<Tab title="Redis CLI">
+
+```bash
+SEARCH.COUNT products '{"inStock": true}'
+```
+
+</Tab>
+
+<Tab title="curl">
+
+```bash
+curl -X POST https://YOUR_ENDPOINT.upstash.io \
+  -H "Authorization: Bearer $UPSTASH_REDIS_REST_TOKEN" \
+  -d '["SEARCH.COUNT", "products", "{\"inStock\": true}"]'
+```
+
+</Tab>
+
+</Tabs>
+
+# SEARCH.CREATE
+Source: https://upstash.com/docs/redis/commands/search/search-create
+
+Use `SEARCH.CREATE` to create a search index over JSON, hash, or string values.
+
+See [Index Management](/docs/redis/search/index-management#creating-an-index) for a feature-level guide to creating indexes and [Schema Definition](/docs/redis/search/schema-definition) for field types and schema design.
+
+<Note>
+  Upstash Redis Search uses `SEARCH.*` commands. They are separate from and incompatible with the `FT.*` commands in the open-source RediSearch module.
+</Note>
+
+## Syntax
+
+```redis
+SEARCH.CREATE <name> ON <JSON|HASH|STRING>
+  PREFIX <count> <prefix> [<prefix> ...]
+  [LANGUAGE <language>]
+  [SKIPINITIALSCAN]
+  [EXISTSOK]
+  SCHEMA
+    <field> TEXT [NOSTEM] [NOTOKENIZE] [FROM <source_field>]
+    | <field> <U64|I64|F64|BOOL|DATE> [FAST] [FROM <source_field>]
+    | <field> <KEYWORD|FACET> [FROM <source_field>]
+    [...]
+```
+
+## Arguments
+
+| Argument | Description |
+| --- | --- |
+| `ON` | Type of Redis value to index: `JSON`, `HASH`, or `STRING`. A `STRING` value must contain a JSON object. |
+| `PREFIX` | One or more key prefixes. Prefixes in the same index cannot be duplicates or overlap one another. |
+| `LANGUAGE` | Stemming language for `TEXT` fields. Defaults to `english`. Supported values are `arabic`, `danish`, `dutch`, `english`, `finnish`, `french`, `german`, `greek`, `hungarian`, `italian`, `norwegian`, `portuguese`, `romanian`, `russian`, `spanish`, `swedish`, `tamil`, and `turkish`. |
+| `SKIPINITIALSCAN` | Create the index without scanning existing keys. Later writes are still indexed; use [`SEARCH.REINDEX`](/docs/redis/commands/search/search-reindex) to add the current matching data. |
+| `EXISTSOK` | Return `0` when an index with the same data type, prefixes, and schema already exists. A configuration mismatch returns an error. |
+| `SCHEMA` | One or more field definitions. `SCHEMA` must be the final top-level clause. |
+
+### Schema field options
+
+| Option | Valid field types | Description |
+| --- | --- | --- |
+| `FAST` | `U64`, `I64`, `F64`, `BOOL`, `DATE` | Store the field for operations such as sorting and aggregations. Score functions accept `FAST` fields of type `U64`, `I64`, or `F64`. |
+| `NOSTEM` | `TEXT` | Index text without stemming words to their roots. |
+| `NOTOKENIZE` | `TEXT` | Index the entire value as one token. |
+| `FROM <source_field>` | All field types | Read the value from a different document field or nested dot path while exposing it under `<field>` in the index. |
+
+## Response
+
+Returns `1` when the index is created. With `EXISTSOK`, returns `0` if the existing index has the same data type, prefixes, and schema. Returns an error for a different configuration or when `<name>` is already used by a non-index Redis key.
+
+## Examples
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis, s } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const products = await redis.search.createIndex({
+  name: "products",
+  dataType: "json",
+  prefix: "product:",
+  schema: s.object({
+    name: s.string(),
+    price: s.number("F64"),
+    inStock: s.boolean(),
+  }),
+});
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+
+products = redis.search.create_index(
+    name="products",
+    data_type="json",
+    prefixes="product:",
+    schema={
+        "name": "TEXT",
+        "price": {"type": "F64", "fast": True},
+        "inStock": "BOOL",
+    },
+)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import IORedis from "ioredis";
+import { createSearch, s } from "@upstash/search-ioredis";
+
+const redis = new IORedis(process.env.REDIS_URL!);
+const search = createSearch(redis);
+
+const products = await search.createIndex({
+  name: "products",
+  dataType: "json",
+  prefix: "product:",
+  schema: s.object({
+    name: s.string(),
+    price: s.number("F64"),
+    inStock: s.boolean(),
+  }),
+});
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+import { createSearch, s } from "@upstash/search-redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const search = createSearch(client);
+
+const products = await search.createIndex({
+  name: "products",
+  dataType: "json",
+  prefix: "product:",
+  schema: s.object({
+    name: s.string(),
+    price: s.number("F64"),
+    inStock: s.boolean(),
+  }),
+});
+```
+
+</Tab>
+
+<Tab title="Redis CLI">
+
+```bash
+SEARCH.CREATE products ON JSON PREFIX 1 product: SCHEMA name TEXT price F64 FAST inStock BOOL
+```
+
+</Tab>
+
+<Tab title="curl">
+
+```bash
+curl -X POST https://YOUR_ENDPOINT.upstash.io \
+  -H "Authorization: Bearer $UPSTASH_REDIS_REST_TOKEN" \
+  -d '["SEARCH.CREATE", "products", "ON", "JSON", "PREFIX", "1", "product:", "SCHEMA", "name", "TEXT", "price", "F64", "FAST", "inStock", "BOOL"]'
+```
+
+</Tab>
+
+</Tabs>
+
+# SEARCH.DESCRIBE
+Source: https://upstash.com/docs/redis/commands/search/search-describe
+
+Use `SEARCH.DESCRIBE` to return metadata about a search index.
+
+See [Describing an Index](/docs/redis/search/index-management#describing-an-index) for the feature guide.
+
+The command accepts an index name or alias. When an alias is used, the response describes its target and reports the target's index name.
+
+## Syntax
+
+```redis
+SEARCH.DESCRIBE <name>
+```
+
+## Response
+
+Returns index metadata as alternating field names and values. The response contains:
+
+| Field | Description |
+| --- | --- |
+| `name` | The index name. |
+| `type` | The indexed Redis value type: `HASH`, `JSON`, or `STRING`. |
+| `prefixes` | Key prefixes included in the index. |
+| `language` | Stemming language used by `TEXT` fields. |
+| `indexSize` | Current index size in bytes. |
+| `pendingUpdates` | Number of updates waiting to be indexed. |
+| `schema` | Field definitions, including `FROM`, `NOSTEM`, `NOTOKENIZE`, and `FAST` options where present. |
+
+```text
+[
+  "name", "products",
+  "type", "JSON",
+  "prefixes", ["product:"],
+  "language", "english",
+  "indexSize", 1234,
+  "pendingUpdates", 0,
+  "schema", [["name", "TEXT"], ["price", "F64", "FAST"]]
+]
+```
+
+Returns `null` if the index does not exist.
+
+## Examples
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+const products = redis.search.index({ name: "products" });
+const description = await products.describe();
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+products = redis.search.index(name="products")
+description = products.describe()
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import IORedis from "ioredis";
+import { createSearch } from "@upstash/search-ioredis";
+
+const redis = new IORedis(process.env.REDIS_URL!);
+const search = createSearch(redis);
+const products = search.index({ name: "products" });
+const description = await products.describe();
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+import { createSearch } from "@upstash/search-redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const search = createSearch(client);
+const products = search.index({ name: "products" });
+const description = await products.describe();
+```
+
+</Tab>
+
+<Tab title="Redis CLI">
+
+```bash
+SEARCH.DESCRIBE products
+```
+
+</Tab>
+
+<Tab title="curl">
+
+```bash
+curl -X POST https://YOUR_ENDPOINT.upstash.io \
+  -H "Authorization: Bearer $UPSTASH_REDIS_REST_TOKEN" \
+  -d '["SEARCH.DESCRIBE", "products"]'
+```
+
+</Tab>
+
+</Tabs>
+
+# SEARCH.DROP
+Source: https://upstash.com/docs/redis/commands/search/search-drop
+
+Use `SEARCH.DROP` to remove a search index. The underlying Redis keys are not deleted.
+
+See [Dropping an Index](/docs/redis/search/index-management#dropping-an-index) for the feature guide.
+
+`SEARCH.DROP` does not resolve aliases: `<name>` is always treated as the literal index name. Aliases that point to a dropped index are not removed automatically.
+
+## Syntax
+
+```redis
+SEARCH.DROP <name>
+```
+
+## Response
+
+Returns `1` if the index was dropped or `0` if the index was not found.
+
+## Examples
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+const products = redis.search.index({ name: "products" });
+const result = await products.drop();
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+products = redis.search.index(name="products")
+result = products.drop()
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import IORedis from "ioredis";
+import { createSearch } from "@upstash/search-ioredis";
+
+const redis = new IORedis(process.env.REDIS_URL!);
+const search = createSearch(redis);
+const products = search.index({ name: "products" });
+const result = await products.drop();
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+import { createSearch } from "@upstash/search-redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const search = createSearch(client);
+const products = search.index({ name: "products" });
+const result = await products.drop();
+```
+
+</Tab>
+
+<Tab title="Redis CLI">
+
+```bash
+SEARCH.DROP products
+```
+
+</Tab>
+
+<Tab title="curl">
+
+```bash
+curl -X POST https://YOUR_ENDPOINT.upstash.io \
+  -H "Authorization: Bearer $UPSTASH_REDIS_REST_TOKEN" \
+  -d '["SEARCH.DROP", "products"]'
+```
+
+</Tab>
+
+</Tabs>
+
+# SEARCH.LISTALIASES
+Source: https://upstash.com/docs/redis/commands/search/search-listaliases
+
+Use `SEARCH.LISTALIASES` to return all aliases and the indexes they point to.
+
+See [Listing Aliases](/docs/redis/search/aliases#listing-aliases) for the feature guide.
+
+## Syntax
+
+```redis
+SEARCH.LISTALIASES
+```
+
+## Response
+
+Returns an unordered array of `[alias, index_name]` pairs, or an empty array if no aliases exist. The response can include aliases whose target index no longer exists. To list every index in the database, use [`SEARCH.LISTINDEXES`](/docs/redis/commands/search/search-listindexes).
+
+The SDKs below decode the pairs into an object or dictionary that maps each alias to its index name.
+
+## Examples
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+const aliases = await redis.search.alias.list();
+// { products: "products-v2" }
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+aliases = redis.search.alias.list()
+# {"products": "products-v2"}
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import IORedis from "ioredis";
+import { createSearch } from "@upstash/search-ioredis";
+
+const redis = new IORedis(process.env.REDIS_URL!);
+const search = createSearch(redis);
+const aliases = await search.alias.list();
+// { products: "products-v2" }
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+import { createSearch } from "@upstash/search-redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const search = createSearch(client);
+const aliases = await search.alias.list();
+// { products: "products-v2" }
+```
+
+</Tab>
+
+<Tab title="Redis CLI">
+
+```bash
+SEARCH.LISTALIASES
+```
+
+</Tab>
+
+<Tab title="curl">
+
+```bash
+curl -X POST https://YOUR_ENDPOINT.upstash.io \
+  -H "Authorization: Bearer $UPSTASH_REDIS_REST_TOKEN" \
+  -d '["SEARCH.LISTALIASES"]'
+```
+
+</Tab>
+
+</Tabs>
+
+# SEARCH.LISTINDEXES
+Source: https://upstash.com/docs/redis/commands/search/search-listindexes
+
+Use `SEARCH.LISTINDEXES` to list search indexes in the database.
+
+See [Listing Indexes](/docs/redis/search/index-management#listing-indexes) for the feature guide.
+
+## Syntax
+
+```redis
+SEARCH.LISTINDEXES [MATCH <pattern>] [LIMIT <count>] [OFFSET <offset>]
+```
+
+## Arguments
+
+| Argument | Description | Default |
+| --- | --- | --- |
+| `MATCH` | Filter index names by a glob-style pattern, such as `product*`. | All indexes |
+| `LIMIT` | Maximum number of indexes to return. `0` returns all indexes. | `0` (all indexes) |
+| `OFFSET` | Number of indexes to skip for pagination. | `0` |
+
+## Response
+
+Returns one entry per index, sorted by index name. Each entry is a map containing the index `name` and its backing `type` (`HASH`, `JSON`, or `STRING`). With RESP2, each map is encoded as an array of alternating keys and values.
+
+```text
+[
+  ["name", "productIdx", "type", "HASH"],
+  ["name", "profileIdx", "type", "JSON"],
+  ["name", "sessionIdx", "type", "STRING"]
+]
+```
+
+## Examples
+
+<Note>
+  The high-level Search APIs do not currently expose `SEARCH.LISTINDEXES`. Use each client's generic command method for this command.
+</Note>
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+const indexes = await redis.exec<string[][]>([
+  "SEARCH.LISTINDEXES",
+  "MATCH",
+  "product*",
+  "LIMIT",
+  10,
+  "OFFSET",
+  0,
+]);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+indexes = redis.execute([
+    "SEARCH.LISTINDEXES",
+    "MATCH",
+    "product*",
+    "LIMIT",
+    10,
+    "OFFSET",
+    0,
+])
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import IORedis from "ioredis";
+
+const redis = new IORedis(process.env.REDIS_URL!);
+const indexes = await redis.call(
+  "SEARCH.LISTINDEXES",
+  "MATCH",
+  "product*",
+  "LIMIT",
+  10,
+  "OFFSET",
+  0,
+);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const indexes = await client.sendCommand([
+  "SEARCH.LISTINDEXES",
+  "MATCH",
+  "product*",
+  "LIMIT",
+  "10",
+  "OFFSET",
+  "0",
+]);
+```
+
+</Tab>
+
+<Tab title="Redis CLI">
+
+```bash
+SEARCH.LISTINDEXES MATCH 'product*' LIMIT 10 OFFSET 0
+```
+
+</Tab>
+
+<Tab title="curl">
+
+```bash
+curl -X POST https://YOUR_ENDPOINT.upstash.io \
+  -H "Authorization: Bearer $UPSTASH_REDIS_REST_TOKEN" \
+  -d '["SEARCH.LISTINDEXES", "MATCH", "product*", "LIMIT", "10", "OFFSET", "0"]'
+```
+
+</Tab>
+
+</Tabs>
+
+# SEARCH.QUERY
+Source: https://upstash.com/docs/redis/commands/search/search-query
+
+Use `SEARCH.QUERY` to search for documents matching a JSON filter.
+
+## Syntax
+
+```redis
+SEARCH.QUERY <name> '<query>'
+  [LIMIT <count>]
+  [OFFSET <offset>]
+  [ORDERBY <field> [ASC|DESC]]
+  [SELECT <count> <field> [<field> ...]]
+  [NOCONTENT]
+  [HIGHLIGHT FIELDS <count> <field> [<field> ...] [TAGS <open> <close>]]
+  [SCOREFUNC
+    FIELDVALUE <field>
+      [MODIFIER <NONE|LOG|LOG1P|LOG2P|LN|LN1P|LN2P|SQUARE|SQRT|RECIPROCAL>]
+      [FACTOR <number>]
+      [MISSING <number>]
+    [FIELDVALUE ...]
+    [SCOREMODE <SUM|MULTIPLY|REPLACE>]
+    [COMBINEMODE <SUM|MULTIPLY>]]
+```
+
+## Arguments
+
+| Argument | Description | Default |
+| --- | --- | --- |
+| `LIMIT` | Maximum number of results to return. Must be between 1 and 1000. | `10` |
+| `OFFSET` | Number of results to skip for pagination. Must be between 0 and 10,000. | `0` |
+| `ORDERBY` | Sort by a `FAST` field. The direction defaults to `DESC` when omitted. | Relevance score, descending |
+| `SELECT` | Return only the specified number of document fields. When the schema uses `FROM`, specify the source document field rather than its index alias. | All fields |
+| `NOCONTENT` | Return keys and scores without document content. | Disabled |
+| `HIGHLIGHT` | Wrap matching terms in tags. The default tags are `<em>` and `</em>`. | Disabled |
+| `SCOREFUNC` | Adjust relevance scores using one or more `FAST` numeric fields. `FACTOR` defaults to `1`, `MISSING` to `0`, `MODIFIER` to `NONE`, `SCOREMODE` to `SUM`, and `COMBINEMODE` to `SUM`. | Disabled |
+<Warning>
+  `NOCONTENT` cannot be combined with `SELECT` or `HIGHLIGHT`. `SCOREFUNC` cannot be combined with `ORDERBY`. Inside `MULTI` or `EVAL`, the command requires `NOCONTENT`.
+</Warning>
+
+See [Querying and filtering](/docs/redis/search/querying) for the JSON filter operators and detailed query examples.
+
+## Response
+
+Returns an array of `[key, score, content]` results, or `null` if the index does not exist:
+
+* `key` is the Redis key of the matching document.
+* `score` is the floating-point relevance score.
+* `content` is an array of field-value pairs. JSON indexes return `[["$", "<json_string>"]]`; hash indexes return `[["field", "value"], ...]`.
+
+When `NOCONTENT` is used, each result is `[key, score]`. When `SELECT` is used, only fields that exist in the document appear in the content.
+
+```text
+[
+  ["key1", 1.25, [["$", "{\"name\":\"...\"}"]]],
+  ["key2", 0.75, [["$", "{\"name\":\"...\"}"]]]
+]
+```
+
+## Examples
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis, s } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+const products = redis.search.index({
+  name: "products",
+  schema: s.object({ name: s.string() }),
+});
+
+const results = await products.query({
+  filter: { name: "wireless" },
+  limit: 10,
+  offset: 0,
+});
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+products = redis.search.index(name="products")
+
+results = products.query(
+    filter={"name": "wireless"},
+    limit=10,
+    offset=0,
+)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import IORedis from "ioredis";
+import { createSearch, s } from "@upstash/search-ioredis";
+
+const redis = new IORedis(process.env.REDIS_URL!);
+const search = createSearch(redis);
+const products = search.index({
+  name: "products",
+  schema: s.object({ name: s.string() }),
+});
+
+const results = await products.query({
+  filter: { name: "wireless" },
+  limit: 10,
+  offset: 0,
+});
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+import { createSearch, s } from "@upstash/search-redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const search = createSearch(client);
+const products = search.index({
+  name: "products",
+  schema: s.object({ name: s.string() }),
+});
+
+const results = await products.query({
+  filter: { name: "wireless" },
+  limit: 10,
+  offset: 0,
+});
+```
+
+</Tab>
+
+<Tab title="Redis CLI">
+
+```bash
+SEARCH.QUERY products '{"name": "wireless"}' LIMIT 10 OFFSET 0
+```
+
+</Tab>
+
+<Tab title="curl">
+
+```bash
+curl -X POST https://YOUR_ENDPOINT.upstash.io \
+  -H "Authorization: Bearer $UPSTASH_REDIS_REST_TOKEN" \
+  -d '["SEARCH.QUERY", "products", "{\"name\": \"wireless\"}", "LIMIT", "10", "OFFSET", "0"]'
+```
+
+</Tab>
+
+</Tabs>
+
+# SEARCH.REINDEX
+Source: https://upstash.com/docs/redis/commands/search/search-reindex
+
+Use `SEARCH.REINDEX` to rebuild an existing index from the current Redis keys that match its data type and prefixes. It is especially useful after creating an index with `SKIPINITIALSCAN`.
+
+See [Index Management](/docs/redis/search/index-management) for the feature guide to creating and managing indexes.
+
+`SEARCH.REINDEX` accepts an index name or alias. The index definition is preserved while its searchable contents are replaced with a fresh scan.
+
+<Warning>
+  Reindexing scans all matching keys and can be expensive for large datasets.
+</Warning>
+
+## Syntax
+
+```redis
+SEARCH.REINDEX <name>
+```
+
+## Response
+
+Returns `1` when the index is rebuilt or `0` if the index does not exist.
+
+## Examples
+
+<Tabs>
+
+<Tab title="Redis CLI">
+
+```bash
+SEARCH.REINDEX products
+```
+
+</Tab>
+
+<Tab title="curl">
+
+```bash
+curl -X POST https://YOUR_ENDPOINT.upstash.io \
+  -H "Authorization: Bearer $UPSTASH_REDIS_REST_TOKEN" \
+  -d '["SEARCH.REINDEX", "products"]'
+```
+
+</Tab>
+
+</Tabs>
+
+# SEARCH.WAITINDEXING
+Source: https://upstash.com/docs/redis/commands/search/search-waitindexing
+
+Use `SEARCH.WAITINDEXING` to block until all pending index updates are processed and visible to queries.
+
+See [Waiting for Indexing](/docs/redis/search/index-management#waiting-for-indexing) for guidance on when to wait for index updates.
+
+The command accepts an index name or alias and waits for every update queued before the command began. Writes that arrive later may require another call.
+
+## Syntax
+
+```redis
+SEARCH.WAITINDEXING <name>
+```
+
+## Important points
+
+<Warning>
+  Do not call `SEARCH.WAITINDEXING` after every write. Batch updates are necessary for optimal indexing performance. Use this command only when you need to ensure queries reflect recent changes, such as in tests or CI pipelines.
+</Warning>
+
+## Response
+
+Returns `1` when indexing is complete or `0` if the index was not found.
+
+## Examples
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+const products = redis.search.index({ name: "products" });
+const result = await products.waitIndexing();
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+products = redis.search.index(name="products")
+result = products.wait_indexing()
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import IORedis from "ioredis";
+import { createSearch } from "@upstash/search-ioredis";
+
+const redis = new IORedis(process.env.REDIS_URL!);
+const search = createSearch(redis);
+const products = search.index({ name: "products" });
+const result = await products.waitIndexing();
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+import { createSearch } from "@upstash/search-redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const search = createSearch(client);
+const products = search.index({ name: "products" });
+const result = await products.waitIndexing();
+```
+
+</Tab>
+
+<Tab title="Redis CLI">
+
+```bash
+SEARCH.WAITINDEXING products
+```
+
+</Tab>
+
+<Tab title="curl">
+
+```bash
+curl -X POST https://YOUR_ENDPOINT.upstash.io \
+  -H "Authorization: Bearer $UPSTASH_REDIS_REST_TOKEN" \
+  -d '["SEARCH.WAITINDEXING", "products"]'
+```
+
+</Tab>
+
+</Tabs>
+
+# ACL
+Source: https://upstash.com/docs/redis/commands/server/acl
+
+Use `ACL` to manage access control list.
+
+## Syntax
+
+```redis
+ACL CAT [category]
+ACL DELUSER <username> [username ...]
+ACL GENPASS [bits]
+ACL GETUSER <username>
+ACL HELP
+ACL LIST
+ACL LOAD
+ACL RESTTOKEN <username> <password>
+ACL GENTOKEN <username> [password]
+ACL LOG [count | RESET]
+ACL SAVE
+ACL SETUSER <username> [rule ...]
+ACL USERS
+ACL WHOAMI
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `subcommand` | Yes | No | One of the supported ACL operations shown in the syntax block. |
+| `username` | Depends | Some forms | ACL user selected by the subcommand. |
+| `rule` | No | Yes | ACL SETUSER rule; rules are applied from left to right. |
+| `count \| RESET` | No | No | Limit ACL LOG output or clear the log. |
+
+## Important points
+
+* This command can expose administrative information or make a broad destructive change. Restrict it to trusted code paths.
+* ACL is an administrative command. Changing users or rules can immediately revoke application access.
+* Upstash also supports the deployment-specific `RESTTOKEN` and `GENTOKEN` subcommands.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Simple string `OK`; Integer; Bulk string; array of bulk strings or nested metadata arrays; flat array of alternating keys and values; or Null bulk string or null array |
+| RESP3 | Simple string `OK`; Integer; Bulk string; array of bulk strings or nested metadata arrays; Map; or Null |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+<Note>
+  This command is not supported yet in `upstash_redis`.
+</Note>
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.acl("WHOAMI");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.aclWhoAmI();
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.acl_whoami()
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ACLWhoAmI(context.Background()).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.aclWhoAmI();
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.acl_whoami()?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# COMMAND
+Source: https://upstash.com/docs/redis/commands/server/command
+
+Use `COMMAND` to get command metadata.
+
+## Syntax
+
+```redis
+COMMAND
+```
+
+## Arguments
+
+This command takes no arguments.
+
+## Important points
+
+* The current Upstash deployment accepts `COMMAND` for client compatibility but returns an empty array; it does not expose the server command table.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Empty array |
+| RESP3 | Empty array |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+<Note>
+  This command is not supported yet in `upstash_redis`.
+</Note>
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.call("COMMAND");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.command();
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.command()
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.Command(context.Background()).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.command();
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("COMMAND");
+
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# CONFIG GET
+Source: https://upstash.com/docs/redis/commands/server/config-get
+
+Use `CONFIG GET` to read runtime configuration.
+
+## Syntax
+
+```redis
+CONFIG GET <parameter> [parameter ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `parameter` | Yes | Yes | One or more glob-style configuration parameter patterns. |
+
+## Important points
+
+* This command can expose administrative information or make a broad destructive change. Restrict it to trusted code paths.
+* This deployment exposes only `notify-keyspace-events`. Other patterns return no matching entries.
+* Both RESP2 and RESP3 return a flat array of alternating parameter names and values.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Flat array of alternating configuration names and values |
+| RESP3 | Flat array of alternating configuration names and values |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+<Note>
+  This command is not supported yet in `upstash_redis`.
+</Note>
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.config("GET", "notify-keyspace-events");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.configGet("notify-keyspace-events");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.config_get("notify-keyspace-events")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ConfigGet(context.Background(), "notify-keyspace-events").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.configGet("notify-keyspace-events");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("CONFIG");
+    command.arg("GET");
+    command.arg("notify-keyspace-events");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# CONFIG SET
+Source: https://upstash.com/docs/redis/commands/server/config-set
+
+Use `CONFIG SET` to change runtime configuration.
+
+## Syntax
+
+```redis
+CONFIG SET <parameter> <value> [parameter value ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `parameter` | Yes | Yes, in pairs | Runtime configuration parameter to update. |
+| `value` | Yes | Yes, in pairs | New value for the preceding parameter. |
+
+## Important points
+
+* This command can expose administrative information or make a broad destructive change. Restrict it to trusted code paths.
+* This deployment permits changes only to `notify-keyspace-events`; any other parameter returns an error.
+* Parameter/value pairs are processed from left to right. If a later pair is invalid, an earlier valid change may already have taken effect.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Simple string `OK` |
+| RESP3 | Simple string `OK` |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+<Note>
+  This command is not supported yet in `upstash_redis`.
+</Note>
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.config("SET", "notify-keyspace-events", "Ex");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.configSet("notify-keyspace-events", "Ex");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.config_set("notify-keyspace-events", "Ex")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ConfigSet(context.Background(), "notify-keyspace-events", "Ex").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.configSet("notify-keyspace-events", "Ex");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("CONFIG");
+    command.arg("SET");
+    command.arg("notify-keyspace-events");
+    command.arg("Ex");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# DBSIZE
+Source: https://upstash.com/docs/redis/commands/server/dbsize
+
+Use `DBSIZE` to get number of keys in database.
+
+## Syntax
+
+```redis
+DBSIZE
+```
+
+## Arguments
+
+This command takes no arguments.
+
+## Important points
+
+* This operation can inspect a large part of the database. Prefer cursor-based scans where possible and avoid unbounded use on hot paths.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const keys = await redis.dbsize();
+console.log(keys) // 20
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.dbsize()
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.dbsize();
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.dbSize();
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.dbsize()
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.DBSize(context.Background()).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.dbSize();
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("DBSIZE");
+
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# FLUSHALL
+Source: https://upstash.com/docs/redis/commands/server/flushall
+
+Use `FLUSHALL` to delete all keys in all databases.
+
+## Syntax
+
+```redis
+FLUSHALL [ASYNC | SYNC]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `(ASYNC \| SYNC)` | No | No | Choose one form: `ASYNC` (request asynchronous cleanup); `SYNC` (request synchronous cleanup). |
+
+## Important points
+
+* This command can expose administrative information or make a broad destructive change. Restrict it to trusted code paths.
+* This operation can inspect a large part of the database. Prefer cursor-based scans where possible and avoid unbounded use on hot paths.
+* This deletes the database contents. Test against a disposable database and require an explicit operator action in production tooling.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Simple string `OK` |
+| RESP3 | Simple string `OK` |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.flushall();
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.flushall()
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.flushall();
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.flushAll();
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.flushall()
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.FlushAll(context.Background()).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.flushAll();
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("FLUSHALL");
+
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# FLUSHDB
+Source: https://upstash.com/docs/redis/commands/server/flushdb
+
+Use `FLUSHDB` to delete all keys in current database.
+
+## Syntax
+
+```redis
+FLUSHDB [ASYNC | SYNC]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `(ASYNC \| SYNC)` | No | No | Choose one form: `ASYNC` (request asynchronous cleanup); `SYNC` (request synchronous cleanup). |
+
+## Important points
+
+* This command can expose administrative information or make a broad destructive change. Restrict it to trusted code paths.
+* This operation can inspect a large part of the database. Prefer cursor-based scans where possible and avoid unbounded use on hot paths.
+* This deletes the database contents. Test against a disposable database and require an explicit operator action in production tooling.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Simple string `OK` |
+| RESP3 | Simple string `OK` |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.flushdb();
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.flushdb()
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.flushdb();
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.flushDb();
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.flushdb()
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.FlushDB(context.Background()).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.flushDB();
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("FLUSHDB");
+
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# INFO
+Source: https://upstash.com/docs/redis/commands/server/info
+
+Use `INFO` to get server statistics and information.
+
+## Syntax
+
+```redis
+INFO [section]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `section` | No | No | Section to return: `server`, `clients`, `memory`, `stats`, `cluster`, `keyspace`, `default`, or `all`. |
+
+## Important points
+
+* This command can expose administrative information or make a broad destructive change. Restrict it to trusted code paths.
+* `default` and `all` return the same Upstash section set. Unsupported section names produce only a section heading.
+* The reply is a CRLF-delimited text report, not a RESP map. Parse it defensively because fields may be added over time.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Bulk string |
+| RESP3 | Bulk string |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+<Note>
+  This command is not supported yet in `upstash_redis`.
+</Note>
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.info("memory");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.info("memory");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.info("memory")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.Info(context.Background(), "memory").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.info("memory");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("INFO");
+    command.arg("memory");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# MONITOR
+Source: https://upstash.com/docs/redis/commands/server/monitor
+
+Use `MONITOR` to stream all commands received.
+
+## Syntax
+
+```redis
+MONITOR
+```
+
+## Arguments
+
+This command takes no arguments.
+
+## Important points
+
+* This is a connection-oriented command and is available over native Redis TCP, not the stateless REST endpoint.
+* This command can expose administrative information or make a broad destructive change. Restrict it to trusted code paths.
+* MONITOR changes the TCP connection into a continuous command stream. Use a dedicated connection and close it to stop monitoring.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Simple string `OK`, then a stream of bulk strings, one per command the server executes |
+| RESP3 | Simple string `OK`, then a stream of bulk strings, one per command the server executes |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+redis.monitor((error, monitor) => {
+  if (error) throw error;
+  monitor.on("monitor", (time, args, source, database) => {
+    console.log({ time, args, source, database });
+  });
+});
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+
+await client.monitor((command) => {
+  console.log(command);
+});
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+with client.monitor() as monitor:
+    for command in monitor.listen():
+        print(command)
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+import redis.clients.jedis.Jedis;
+import redis.clients.jedis.JedisMonitor;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  jedis.monitor(new JedisMonitor() {
+    @Override
+    public void onCommand(String command) {
+      System.out.println(command);
+    }
+  });
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let packed = redis::cmd("MONITOR").get_packed_command();
+    connection.send_packed_command(&packed)?;
+    loop {
+        println!("{:?}", connection.recv_response()?);
+    }
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# Server commands
+Source: https://upstash.com/docs/redis/commands/server/overview
+
+<CardGroup cols={2}>
+<Card title="ACL" href="/redis/commands/server/acl">Manage access control list</Card>
+<Card title="COMMAND" href="/redis/commands/server/command">Get command metadata</Card>
+<Card title="CONFIG GET" href="/redis/commands/server/config-get">Read runtime configuration</Card>
+<Card title="CONFIG SET" href="/redis/commands/server/config-set">Change runtime configuration</Card>
+<Card title="DBSIZE" href="/redis/commands/server/dbsize">Get number of keys in database</Card>
+<Card title="FLUSHALL" href="/redis/commands/server/flushall">Delete all keys in all databases</Card>
+<Card title="FLUSHDB" href="/redis/commands/server/flushdb">Delete all keys in current database</Card>
+<Card title="INFO" href="/redis/commands/server/info">Get server statistics and information</Card>
+<Card title="MONITOR" href="/redis/commands/server/monitor">Stream all commands received</Card>
+<Card title="TIME" href="/redis/commands/server/time">Get current server time</Card>
+</CardGroup>
+
+# TIME
+Source: https://upstash.com/docs/redis/commands/server/time
+
+Use `TIME` to get current server time.
+
+## Syntax
+
+```redis
+TIME
+```
+
+## Arguments
+
+This command takes no arguments.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Two-element array of bulk strings: Unix seconds and microseconds |
+| RESP3 | Two-element array of bulk strings: Unix seconds and microseconds |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+const result = await redis.time();
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.time()
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.time();
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.time();
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.time()
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.Time(context.Background()).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.time();
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("TIME");
+
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# Set commands
+Source: https://upstash.com/docs/redis/commands/set/overview
+
+<CardGroup cols={2}>
+<Card title="SADD" href="/redis/commands/set/sadd">Add members to a set</Card>
+<Card title="SCARD" href="/redis/commands/set/scard">Get set cardinality</Card>
+<Card title="SDIFF" href="/redis/commands/set/sdiff">Get set difference</Card>
+<Card title="SDIFFSTORE" href="/redis/commands/set/sdiffstore">Store set difference</Card>
+<Card title="SINTER" href="/redis/commands/set/sinter">Get set intersection</Card>
+<Card title="SINTERCARD" href="/redis/commands/set/sintercard">Get intersection cardinality</Card>
+<Card title="SINTERSTORE" href="/redis/commands/set/sinterstore">Store set intersection</Card>
+<Card title="SISMEMBER" href="/redis/commands/set/sismember">Check if member exists in set</Card>
+<Card title="SMEMBERS" href="/redis/commands/set/smembers">Get all set members</Card>
+<Card title="SMISMEMBER" href="/redis/commands/set/smismember">Check multiple members</Card>
+<Card title="SMOVE" href="/redis/commands/set/smove">Move member between sets</Card>
+<Card title="SPOP" href="/redis/commands/set/spop">Remove random members</Card>
+<Card title="SRANDMEMBER" href="/redis/commands/set/srandmember">Get random members</Card>
+<Card title="SREM" href="/redis/commands/set/srem">Remove members from a set</Card>
+<Card title="SSCAN" href="/redis/commands/set/sscan">Incrementally iterate set members</Card>
+<Card title="SUNION" href="/redis/commands/set/sunion">Get set union</Card>
+<Card title="SUNIONSTORE" href="/redis/commands/set/sunionstore">Store set union</Card>
+</CardGroup>
+
+# SADD
+Source: https://upstash.com/docs/redis/commands/set/sadd
+
+Use `SADD` to add members to a set.
+
+## Syntax
+
+```redis
+SADD <key> <member> [<member> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<member>` | Yes | Yes | Member name. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+// 3
+await redis.sadd("key", "a", "b", "c");
+
+// 0
+await redis.sadd("key", "a", "b");
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.sadd("my-key", "member")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.sadd("my-key", "member");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.sAdd("my-key", "member");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.sadd("my-key", "member")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.SAdd(context.Background(), "my-key", "member").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.sadd("my-key", "member");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.sadd("my-key", "member")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# SCARD
+Source: https://upstash.com/docs/redis/commands/set/scard
+
+Use `SCARD` to get set cardinality.
+
+## Syntax
+
+```redis
+SCARD <key>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.sadd("key", "a", "b", "c");
+const cardinality = await redis.scard("key");
+console.log(cardinality); // 3
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.scard("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.scard("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.sCard("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.scard("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.SCard(context.Background(), "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.scard("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.scard("my-key")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# SDIFF
+Source: https://upstash.com/docs/redis/commands/set/sdiff
+
+Use `SDIFF` to get set difference.
+
+## Syntax
+
+```redis
+SDIFF <key> [<key> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | Yes | Redis key targeted by the command. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of bulk-string members |
+| RESP3 | Set of bulk-string members |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.sadd("set1", "a", "b", "c");
+await redis.sadd("set2", "c", "d", "e");
+const diff =  await redis.sdiff("set1", "set2");
+console.log(diff); // ["a", "b"]
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.sdiff("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.sdiff("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.sDiff("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.sdiff(["my-key"])
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.SDiff(context.Background(), "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.sdiff("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.sdiff(&["my-key"])?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# SDIFFSTORE
+Source: https://upstash.com/docs/redis/commands/set/sdiffstore
+
+Use `SDIFFSTORE` to store set difference.
+
+## Syntax
+
+```redis
+SDIFFSTORE <destination> <key> [<key> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<destination>` | Yes | No | Redis key used as destination. |
+| `<key>` | Yes | Yes | Redis key targeted by the command. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.sadd("set1", "a", "b", "c");
+await redis.sadd("set2", "c", "d", "e");
+await redis.sdiff("dest", "set1", "set2");
+console.log(diff); // ["a", "b"]
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.sdiffstore("destination-key", "my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.sdiffstore("destination-key", "my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.sDiffStore("destination-key", "my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.sdiffstore("destination-key", ["my-key"])
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.SDiffStore(context.Background(), "destination-key", "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.sdiffstore("destination-key", "my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.sdiffstore("destination-key", &["my-key"])?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# SINTER
+Source: https://upstash.com/docs/redis/commands/set/sinter
+
+Use `SINTER` to get set intersection.
+
+## Syntax
+
+```redis
+SINTER <key> [<key> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | Yes | Redis key targeted by the command. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of bulk-string members |
+| RESP3 | Set of bulk-string members |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.sadd("set1", "a", "b", "c");
+await redis.sadd("set2", "c", "d", "e");
+const intersection =  await redis.sinter("set1", "set2");
+console.log(intersection); // ["c"]
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.sinter("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.sinter("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.sInter("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.sinter(["my-key"])
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.SInter(context.Background(), "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.sinter("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.sinter(&["my-key"])?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# SINTERCARD
+Source: https://upstash.com/docs/redis/commands/set/sintercard
+
+Use `SINTERCARD` to get intersection cardinality.
+
+## Syntax
+
+```redis
+SINTERCARD <numkeys> <key> [<key> ...] [LIMIT <limit>]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<numkeys>` | Yes | No | Number of key arguments that follow. |
+| `<key>` | Yes | Yes | Redis key targeted by the command. |
+| `LIMIT <limit>` | No | No | Stop counting once this many members match; `0` means no limit. |
+
+## Important points
+
+* `numkeys` must equal the number of key arguments that immediately follow it.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+const result = await redis.sintercard(["my-key"]);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+<Note>
+  This command is not supported yet in `upstash_redis`.
+</Note>
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.sintercard("1", "my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.sInterCard(["my-key"]);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.sintercard(1, ["my-key"])
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.SInterCard(context.Background(), 0, "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.sintercard("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("SINTERCARD");
+    command.arg("1");
+    command.arg("my-key");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# SINTERSTORE
+Source: https://upstash.com/docs/redis/commands/set/sinterstore
+
+Use `SINTERSTORE` to store set intersection.
+
+## Syntax
+
+```redis
+SINTERSTORE <destination> <key> [<key> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<destination>` | Yes | No | Redis key used as destination. |
+| `<key>` | Yes | Yes | Redis key targeted by the command. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.sadd("set1", "a", "b", "c");
+await redis.sadd("set2", "c", "d", "e");
+await redis.sinterstore("destination", "set1", "set2");
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.sinterstore("destination-key", "my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.sinterstore("destination-key", "my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.sInterStore("destination-key", "my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.sinterstore("destination-key", ["my-key"])
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.SInterStore(context.Background(), "destination-key", "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.sinterstore("destination-key", "my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.sinterstore("destination-key", &["my-key"])?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# SISMEMBER
+Source: https://upstash.com/docs/redis/commands/set/sismember
+
+Use `SISMEMBER` to check if member exists in set.
+
+## Syntax
+
+```redis
+SISMEMBER <key> <member>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<member>` | Yes | No | Member name. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer: `1` if the member is in the set, `0` otherwise |
+| RESP3 | Integer: `1` if the member is in the set, `0` otherwise |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.sadd("set", "a", "b", "c");
+const isMember =  await redis.sismember("set", "a");
+console.log(isMember); // 1
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.sismember("my-key", "member")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.sismember("my-key", "member");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.sIsMember("my-key", "member");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.sismember("my-key", "member")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.SIsMember(context.Background(), "my-key", "member").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.sismember("my-key", "member");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.sismember("my-key", "member")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# SMEMBERS
+Source: https://upstash.com/docs/redis/commands/set/smembers
+
+Use `SMEMBERS` to get all set members.
+
+## Syntax
+
+```redis
+SMEMBERS <key>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of bulk-string members |
+| RESP3 | Array of bulk-string members |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.sadd("set", "a", "b", "c");
+const members =  await redis.smembers("set");
+console.log(members); // ["a", "b", "c"]
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.smembers("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.smembers("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.sMembers("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.smembers("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.SMembers(context.Background(), "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.smembers("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.smembers("my-key")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# SMISMEMBER
+Source: https://upstash.com/docs/redis/commands/set/smismember
+
+Use `SMISMEMBER` to check multiple members.
+
+## Syntax
+
+```redis
+SMISMEMBER <key> <member> [<member> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<member>` | Yes | Yes | Member name. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of integers, one per queried member |
+| RESP3 | Array of integers, one per queried member |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.sadd("set", "a", "b", "c");
+const members =  await redis.smismember("set", ["a", "b", "d"]);
+console.log(members); // [1, 1, 0]
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.smismember("my-key", "member")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.smismember("my-key", "member");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.smIsMember("my-key", ["member"]);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.smismember("my-key", ["member"])
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.SMIsMember(context.Background(), "my-key", "member").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.smismember("my-key", "member");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.smismember("my-key", &["member"])?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# SMOVE
+Source: https://upstash.com/docs/redis/commands/set/smove
+
+Use `SMOVE` to move member between sets.
+
+## Syntax
+
+```redis
+SMOVE <source> <destination> <member>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<source>` | Yes | No | Redis key used as source. |
+| `<destination>` | Yes | No | Redis key used as destination. |
+| `<member>` | Yes | No | Member name. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer: `1` if the member was moved, `0` if it is not in the source set |
+| RESP3 | Integer: `1` if the member was moved, `0` if it is not in the source set |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.sadd("original", "a", "b", "c");
+const moved =  await redis.smove("original", "destination", "a");
+// moved:       1
+// original:    ["b", "c"]
+// destination: ["a"]
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.smove("source-key", "destination-key", "member")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.smove("source-key", "destination-key", "member");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.sMove("source-key", "destination-key", "member");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.smove("source-key", "destination-key", "member")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.SMove(context.Background(), "source-key", "destination-key", "member").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.smove("source-key", "destination-key", "member");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.smove("source-key", "destination-key", "member")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# SPOP
+Source: https://upstash.com/docs/redis/commands/set/spop
+
+Use `SPOP` to remove random members.
+
+## Syntax
+
+```redis
+SPOP <key> [<count>]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<count>` | No | No | Number of members to pop. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Null bulk string or null array, Bulk string, or array of bulk-string members |
+| RESP3 | Null, Bulk string, or set of bulk-string members |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.sadd("set", "a", "b", "c");
+const popped = await redis.spop("set");
+console.log(popped); // "a"
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.spop("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.spop("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.sPop("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.spop("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.SPop(context.Background(), "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.spop("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result: Option<String> = connection.spop("my-key")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# SRANDMEMBER
+Source: https://upstash.com/docs/redis/commands/set/srandmember
+
+Use `SRANDMEMBER` to get random members.
+
+## Syntax
+
+```redis
+SRANDMEMBER <key> [<count>]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<count>` | No | No | Number of members to return; a negative count may repeat members. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Null bulk string or null array, Bulk string, or array of bulk-string members |
+| RESP3 | Null, Bulk string, or array of bulk-string members |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.sadd("set", "a", "b", "c");
+const member = await redis.srandmember("set");
+console.log(member); // "a"
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.srandmember("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.srandmember("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.sRandMember("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.srandmember("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.SRandMember(context.Background(), "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.srandmember("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.srandmember("my-key")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# SREM
+Source: https://upstash.com/docs/redis/commands/set/srem
+
+Use `SREM` to remove members from a set.
+
+## Syntax
+
+```redis
+SREM <key> <member> [<member> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<member>` | Yes | Yes | Member name. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.sadd("set", "a", "b", "c");
+const removed = await redis.srem("set", "a", "b", "d");
+console.log(removed); // 2
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.srem("my-key", "member")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.srem("my-key", "member");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.sRem("my-key", "member");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.srem("my-key", "member")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.SRem(context.Background(), "my-key", "member").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.srem("my-key", "member");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.srem("my-key", "member")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# SSCAN
+Source: https://upstash.com/docs/redis/commands/set/sscan
+
+Use `SSCAN` to incrementally iterate set members.
+
+## Syntax
+
+```redis
+SSCAN <key> <cursor> [MATCH <pattern>] [COUNT <count>]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<cursor>` | Yes | No | Cursor returned by the previous call; start at `0`. |
+| `MATCH <pattern>` | No | No | Return only elements matching this glob-style pattern. |
+| `COUNT <count>` | No | No | Hint for how much work each iteration should do. |
+
+## Important points
+
+* This operation can inspect a large part of the database. Prefer cursor-based scans where possible and avoid unbounded use on hot paths.
+* The cursor is opaque. Start with `0` and continue until the server returns cursor `0`; a single iteration may return no elements.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Two-element array: cursor and array of bulk-string members |
+| RESP3 | Two-element array: cursor and array of bulk-string members |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.sadd("key", "a", "ab","b", "c");
+const [newCursor, fields] = await redis.sscan("key", 0, { match: "a*"});
+console.log(newCursor); // likely `0` since this is a very small set
+console.log(fields); // ["a", "ab"]
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.sscan("my-key", 0)
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.sscan("my-key", "0");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.sScan("my-key", "0");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.sscan("my-key", 0)
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, _, err := client.SScan(context.Background(), "my-key", 0, "*", 0).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.sscan("my-key", "0");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("SSCAN");
+    command.arg("my-key");
+    command.arg("0");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# SUNION
+Source: https://upstash.com/docs/redis/commands/set/sunion
+
+Use `SUNION` to get set union.
+
+## Syntax
+
+```redis
+SUNION <key> [<key> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | Yes | Redis key targeted by the command. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of bulk-string members |
+| RESP3 | Set of bulk-string members |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.sadd("set1", "a", "b", "c");
+await redis.sadd("set2", "c", "d", "e");
+const union =  await redis.sunion("set1", "set2");
+console.log(union); // ["a", "b", "c", "d", "e"]
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.sunion("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.sunion("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.sUnion("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.sunion(["my-key"])
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.SUnion(context.Background(), "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.sunion("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.sunion(&["my-key"])?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# SUNIONSTORE
+Source: https://upstash.com/docs/redis/commands/set/sunionstore
+
+Use `SUNIONSTORE` to store set union.
+
+## Syntax
+
+```redis
+SUNIONSTORE <destination> <key> [<key> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<destination>` | Yes | No | Redis key used as destination. |
+| `<key>` | Yes | Yes | Redis key targeted by the command. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.sadd("set1", "a", "b", "c");
+await redis.sadd("set2", "c", "d", "e");
+await redis.sunionstore("destination", "set1", "set2");
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.sunionstore("destination-key", "my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.sunionstore("destination-key", "my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.sUnionStore("destination-key", "my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.sunionstore("destination-key", ["my-key"])
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.SUnionStore(context.Background(), "destination-key", "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.sunionstore("destination-key", "my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.sunionstore("destination-key", &["my-key"])?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# BZMPOP
+Source: https://upstash.com/docs/redis/commands/sorted-set/bzmpop
+
+Use `BZMPOP` to pop members from the first non-empty sorted set among several, blocking until one has members or the timeout expires.
+
+## Syntax
+
+```redis
+BZMPOP <timeout> <numkeys> <key> [<key> ...] (MIN | MAX) [COUNT <count>]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<timeout>` | Yes | No | Seconds to block; `0` blocks indefinitely. |
+| `<numkeys>` | Yes | No | Number of key arguments that follow. |
+| `<key>` | Yes | Yes | Redis key targeted by the command. |
+| `(MIN \| MAX)` | Yes | No | Choose one form: `MIN`; `MAX`. |
+| `COUNT <count>` | No | No | Maximum number of members to pop. |
+
+## Important points
+
+* A blocking form holds the request until data arrives or its timeout expires. Set the client/network timeout longer than the command timeout.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Null bulk string or null array, or two-element array: key and array of member/score pairs |
+| RESP3 | Null, or two-element array: key and array of member/score pairs |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+<Note>
+  This command is not supported yet in `upstash_redis`.
+</Note>
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.bzmpop("1.5", "1", "my-key", "MIN");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.bzmPop(1.5, "my-key", "MIN");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.bzmpop(1.5, 1, ["my-key"], min=True)
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+    "time"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    _, result, err := client.BZMPop(context.Background(), 1500*time.Millisecond, "min", 0, "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.bzmpop(1.5, redis.clients.jedis.args.SortedSetOption.MIN, "my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("BZMPOP");
+    command.arg("1.5");
+    command.arg("1");
+    command.arg("my-key");
+    command.arg("MIN");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# BZPOPMAX
+Source: https://upstash.com/docs/redis/commands/sorted-set/bzpopmax
+
+Use `BZPOPMAX` to pop the highest-scoring member from the first non-empty sorted set, blocking until one has a member or the timeout expires.
+
+## Syntax
+
+```redis
+BZPOPMAX <key> [<key> ...] <timeout>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | Yes | Redis key targeted by the command. |
+| `<timeout>` | Yes | No | Seconds to block; `0` blocks indefinitely. |
+
+## Important points
+
+* A blocking form holds the request until data arrives or its timeout expires. Set the client/network timeout longer than the command timeout.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Null bulk string or null array, or three-element key/member/score array |
+| RESP3 | Null, or three-element key/member/score array |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+<Note>
+  This command is not supported yet in `upstash_redis`.
+</Note>
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.bzpopmax("my-key", "1.5");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.bzPopMax("my-key", 1.5);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.bzpopmax(["my-key"], timeout=1.5)
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+    "time"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.BZPopMax(context.Background(), 1500*time.Millisecond, "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.bzpopmax(1.5, "my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("BZPOPMAX");
+    command.arg("my-key");
+    command.arg("1.5");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# BZPOPMIN
+Source: https://upstash.com/docs/redis/commands/sorted-set/bzpopmin
+
+Use `BZPOPMIN` to pop the lowest-scoring member from the first non-empty sorted set, blocking until one has a member or the timeout expires.
+
+## Syntax
+
+```redis
+BZPOPMIN <key> [<key> ...] <timeout>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | Yes | Redis key targeted by the command. |
+| `<timeout>` | Yes | No | Seconds to block; `0` blocks indefinitely. |
+
+## Important points
+
+* A blocking form holds the request until data arrives or its timeout expires. Set the client/network timeout longer than the command timeout.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Null bulk string or null array, or three-element key/member/score array |
+| RESP3 | Null, or three-element key/member/score array |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+<Note>
+  This command is not supported yet in `upstash_redis`.
+</Note>
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.bzpopmin("my-key", "1.5");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.bzPopMin("my-key", 1.5);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.bzpopmin(["my-key"], timeout=1.5)
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+    "time"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.BZPopMin(context.Background(), 1500*time.Millisecond, "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.bzpopmin(1.5, "my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("BZPOPMIN");
+    command.arg("my-key");
+    command.arg("1.5");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# Sorted Set commands
+Source: https://upstash.com/docs/redis/commands/sorted-set/overview
+
+<CardGroup cols={2}>
+<Card title="BZMPOP" href="/redis/commands/sorted-set/bzmpop">Blocking pop from sorted sets</Card>
+<Card title="BZPOPMAX" href="/redis/commands/sorted-set/bzpopmax">Blocking pop max score member</Card>
+<Card title="BZPOPMIN" href="/redis/commands/sorted-set/bzpopmin">Blocking pop min score member</Card>
+<Card title="ZADD" href="/redis/commands/sorted-set/zadd">Add members with scores</Card>
+<Card title="ZCARD" href="/redis/commands/sorted-set/zcard">Get sorted set cardinality</Card>
+<Card title="ZCOUNT" href="/redis/commands/sorted-set/zcount">Count members in score range</Card>
+<Card title="ZDIFF" href="/redis/commands/sorted-set/zdiff">Get sorted set difference</Card>
+<Card title="ZDIFFSTORE" href="/redis/commands/sorted-set/zdiffstore">Store sorted set difference</Card>
+<Card title="ZINCRBY" href="/redis/commands/sorted-set/zincrby">Increment member's score</Card>
+<Card title="ZINTER" href="/redis/commands/sorted-set/zinter">Get sorted set intersection</Card>
+<Card title="ZINTERCARD" href="/redis/commands/sorted-set/zintercard">Get intersection cardinality</Card>
+<Card title="ZINTERSTORE" href="/redis/commands/sorted-set/zinterstore">Store sorted set intersection</Card>
+<Card title="ZLEXCOUNT" href="/redis/commands/sorted-set/zlexcount">Count members in lex range</Card>
+<Card title="ZMPOP" href="/redis/commands/sorted-set/zmpop">Pop members from sorted sets</Card>
+<Card title="ZMSCORE" href="/redis/commands/sorted-set/zmscore">Get scores of multiple members</Card>
+<Card title="ZPOPMAX" href="/redis/commands/sorted-set/zpopmax">Pop members with highest scores</Card>
+<Card title="ZPOPMIN" href="/redis/commands/sorted-set/zpopmin">Pop members with lowest scores</Card>
+<Card title="ZRANDMEMBER" href="/redis/commands/sorted-set/zrandmember">Get random members</Card>
+<Card title="ZRANGE" href="/redis/commands/sorted-set/zrange">Get members by index range</Card>
+<Card title="ZRANGEBYLEX" href="/redis/commands/sorted-set/zrangebylex">Get members by lex range</Card>
+<Card title="ZRANGEBYSCORE" href="/redis/commands/sorted-set/zrangebyscore">Get members by score range</Card>
+<Card title="ZRANGESTORE" href="/redis/commands/sorted-set/zrangestore">Store range result</Card>
+<Card title="ZRANK" href="/redis/commands/sorted-set/zrank">Get member's rank</Card>
+<Card title="ZREM" href="/redis/commands/sorted-set/zrem">Remove members</Card>
+<Card title="ZREMRANGEBYLEX" href="/redis/commands/sorted-set/zremrangebylex">Remove members by lex range</Card>
+<Card title="ZREMRANGEBYRANK" href="/redis/commands/sorted-set/zremrangebyrank">Remove members by rank range</Card>
+<Card title="ZREMRANGEBYSCORE" href="/redis/commands/sorted-set/zremrangebyscore">Remove members by score range</Card>
+<Card title="ZREVRANGE" href="/redis/commands/sorted-set/zrevrange">Get members in reverse order</Card>
+<Card title="ZREVRANGEBYLEX" href="/redis/commands/sorted-set/zrevrangebylex">Reverse lex range query</Card>
+<Card title="ZREVRANGEBYSCORE" href="/redis/commands/sorted-set/zrevrangebyscore">Reverse score range query</Card>
+<Card title="ZREVRANK" href="/redis/commands/sorted-set/zrevrank">Get member's reverse rank</Card>
+<Card title="ZSCAN" href="/redis/commands/sorted-set/zscan">Incrementally iterate sorted set</Card>
+<Card title="ZSCORE" href="/redis/commands/sorted-set/zscore">Get member's score</Card>
+<Card title="ZUNION" href="/redis/commands/sorted-set/zunion">Get sorted set union</Card>
+<Card title="ZUNIONSTORE" href="/redis/commands/sorted-set/zunionstore">Store sorted set union</Card>
+</CardGroup>
+
+# ZADD
+Source: https://upstash.com/docs/redis/commands/sorted-set/zadd
+
+Use `ZADD` to add members with scores.
+
+## Syntax
+
+```redis
+ZADD <key> [NX | XX] [GT | LT] [CH] [INCR] <score> <member> [<score> <member> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `(NX \| XX)` | No | No | Choose one form: `NX` (only add new members, never update an existing one); `XX` (only update members that already exist). |
+| `(GT \| LT)` | No | No | Choose one form: `GT` (only update when the new score is greater than the current one); `LT` (only update when it is less). Neither blocks new members from being added. |
+| `CH` | No | No | Count changed members rather than only new members. |
+| `INCR` | No | No | Increment one member instead of adding normally. |
+| `<score> <member>` | Yes | Yes | Score followed by the member it applies to. Repeat to add several members. |
+
+## Important points
+
+* `NX` cannot be combined with `XX`, `GT`, or `LT`, and `GT` and `LT` cannot be used together.
+* RESP2 represents floating-point reply values as bulk strings; RESP3 may use native double replies. Client libraries commonly decode either form to a language number.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Null bulk string or null array or Integer or Bulk string containing a number |
+| RESP3 | Null or Integer or Double |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.zadd(
+    "key",
+    { score: 2, member: "member" },
+    { score: 3, member: "member2"},
+);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.zadd("my-key", {"member": 1.5})
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.zadd("my-key", "1.5", "member");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.zAdd("my-key", { score: 1.5, value: "member" });
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.zadd("my-key", {"member": 1.5})
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ZAdd(context.Background(), "my-key", redis.Z{Score: 1.5, Member: "member"}).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.zadd("my-key", 1.5, "member");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.zadd("my-key", "member", 1.5)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# ZCARD
+Source: https://upstash.com/docs/redis/commands/sorted-set/zcard
+
+Use `ZCARD` to get sorted set cardinality.
+
+## Syntax
+
+```redis
+ZCARD <key>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.zadd("key",
+    { score: 1, member: "one"},
+    { score: 2, member: "two" },
+);
+const elements = await redis.zrank("key");
+console.log(elements); // 2
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.zcard("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.zcard("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.zCard("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.zcard("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ZCard(context.Background(), "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.zcard("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.zcard("my-key")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# ZCOUNT
+Source: https://upstash.com/docs/redis/commands/sorted-set/zcount
+
+Use `ZCOUNT` to count members in score range.
+
+## Syntax
+
+```redis
+ZCOUNT <key> <min> <max>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<min>` | Yes | No | Minimum score: a number, `-inf`, or `(score` for an exclusive bound. |
+| `<max>` | Yes | No | Maximum score: a number, `+inf`, or `(score` for an exclusive bound. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.zadd("key",
+    { score: 1, member: "one"},
+    { score: 2, member: "two" },
+);
+const elements = await redis.zcount("key", "(1", "+inf");
+console.log(elements); // 1
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.zcount("my-key", 1.5, 1.5)
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.zcount("my-key", "1.5", "1.5");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.zCount("my-key", 1.5, 1.5);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.zcount("my-key", 1.5, 1.5)
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ZCount(context.Background(), "my-key", "1.5", "1.5").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.zcount("my-key", 1.5, 1.5);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.zcount("my-key", 1.5, 1.5)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# ZDIFF
+Source: https://upstash.com/docs/redis/commands/sorted-set/zdiff
+
+Use `ZDIFF` to get sorted set difference.
+
+## Syntax
+
+```redis
+ZDIFF <numkeys> <key> [<key> ...] [WITHSCORES]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<numkeys>` | Yes | No | Number of key arguments that follow. |
+| `<key>` | Yes | Yes | Redis key targeted by the command. |
+| `WITHSCORES` | No | No | Include sorted-set scores. |
+
+## Important points
+
+* `numkeys` must equal the number of key arguments that immediately follow it.
+* Pair-based results may be flattened into one alternating array in RESP2 while RESP3 preserves nested pairs or a map.
+* RESP2 represents floating-point reply values as bulk strings; RESP3 may use native double replies. Client libraries commonly decode either form to a language number.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of members, or flat member/score array with `WITHSCORES` |
+| RESP3 | Array of members, or array of member/score pairs with `WITHSCORES` |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.zdiff(["my-key"])
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.zdiff("1", "my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.zDiff("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.zdiff(["my-key"])
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ZDiff(context.Background(), "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.zdiff("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("ZDIFF");
+    command.arg("1");
+    command.arg("my-key");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# ZDIFFSTORE
+Source: https://upstash.com/docs/redis/commands/sorted-set/zdiffstore
+
+Use `ZDIFFSTORE` to store sorted set difference.
+
+## Syntax
+
+```redis
+ZDIFFSTORE <destination> <numkeys> <key> [<key> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<destination>` | Yes | No | Redis key used as destination. |
+| `<numkeys>` | Yes | No | Number of key arguments that follow. |
+| `<key>` | Yes | Yes | Redis key targeted by the command. |
+
+## Important points
+
+* `numkeys` must equal the number of key arguments that immediately follow it.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const values = await redis.zdiffstore("destination", 2, "key1", "key2");
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.zdiffstore("destination-key", ["my-key"])
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.zdiffstore("destination-key", "1", "my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.zDiffStore("destination-key", "my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.zdiffstore("destination-key", ["my-key"])
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ZDiffStore(context.Background(), "destination-key", "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.zdiffstore("destination-key", "my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("ZDIFFSTORE");
+    command.arg("destination-key");
+    command.arg("1");
+    command.arg("my-key");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# ZINCRBY
+Source: https://upstash.com/docs/redis/commands/sorted-set/zincrby
+
+Use `ZINCRBY` to increment member's score.
+
+## Syntax
+
+```redis
+ZINCRBY <key> <increment> <member>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<increment>` | Yes | No | Amount to add to the member's score. |
+| `<member>` | Yes | No | Member name. |
+
+## Important points
+
+* RESP2 represents floating-point reply values as bulk strings; RESP3 may use native double replies. Client libraries commonly decode either form to a language number.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Bulk string containing a number |
+| RESP3 | Double |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.zadd("key", 1, "member");
+const value = await redis.zincrby("key", 2, "member");
+console.log(value); // 3
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.zincrby("my-key", 1, "member")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.zincrby("my-key", "1", "member");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.zIncrBy("my-key", 1, "member");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.zincrby("my-key", 1, "member")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ZIncrBy(context.Background(), "my-key", 1, "member").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.zincrby("my-key", 1, "member");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.zincr("my-key", "member", 1)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# ZINTER
+Source: https://upstash.com/docs/redis/commands/sorted-set/zinter
+
+Use `ZINTER` to get sorted set intersection.
+
+## Syntax
+
+```redis
+ZINTER <numkeys> <key> [<key> ...] [WEIGHTS <weight> [<weight> ...]] [AGGREGATE SUM | MIN | MAX] [WITHSCORES]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<numkeys>` | Yes | No | Number of key arguments that follow. |
+| `<key>` | Yes | Yes | Redis key targeted by the command. |
+| `WEIGHTS <weight>` | No | Yes | Multiplier applied to each input key's scores, in the order the keys were given. |
+| `(AGGREGATE SUM \| MIN \| MAX)` | No | No | Under `AGGREGATE`, choose one form: `SUM`; `MIN`; `MAX`. |
+| `WITHSCORES` | No | No | Include sorted-set scores. |
+
+## Important points
+
+* `numkeys` must equal the number of key arguments that immediately follow it.
+* Pair-based results may be flattened into one alternating array in RESP2 while RESP3 preserves nested pairs or a map.
+* RESP2 represents floating-point reply values as bulk strings; RESP3 may use native double replies. Client libraries commonly decode either form to a language number.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of members, or flat member/score array with `WITHSCORES` |
+| RESP3 | Array of members, or array of member/score pairs with `WITHSCORES` |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.zinter(["my-key"])
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.zinter("1", "my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.zInter("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.zinter(["my-key"])
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ZInter(context.Background(), &redis.ZStore{Keys: []string{"my-key"}}).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.zinter(new redis.clients.jedis.params.ZParams(), "my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("ZINTER");
+    command.arg("1");
+    command.arg("my-key");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# ZINTERCARD
+Source: https://upstash.com/docs/redis/commands/sorted-set/zintercard
+
+Use `ZINTERCARD` to get intersection cardinality.
+
+## Syntax
+
+```redis
+ZINTERCARD <numkeys> <key> [<key> ...] [LIMIT <limit>]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<numkeys>` | Yes | No | Number of key arguments that follow. |
+| `<key>` | Yes | Yes | Redis key targeted by the command. |
+| `LIMIT <limit>` | No | No | Stop counting once this many members match; `0` means no limit. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+<Note>
+  This command is not supported yet in `upstash_redis`.
+</Note>
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.zintercard("1", "my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.zInterCard("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.zintercard(1, ["my-key"])
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ZInterCard(context.Background(), 0, "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.zintercard("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("ZINTERCARD");
+    command.arg("1");
+    command.arg("my-key");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# ZINTERSTORE
+Source: https://upstash.com/docs/redis/commands/sorted-set/zinterstore
+
+Use `ZINTERSTORE` to store sorted set intersection.
+
+## Syntax
+
+```redis
+ZINTERSTORE <destination> <numkeys> <key> [<key> ...] [WEIGHTS <weight> [<weight> ...]] [AGGREGATE SUM | MIN | MAX]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<destination>` | Yes | No | Redis key used as destination. |
+| `<numkeys>` | Yes | No | Number of key arguments that follow. |
+| `<key>` | Yes | Yes | Redis key targeted by the command. |
+| `WEIGHTS <weight>` | No | Yes | Multiplier applied to each input key's scores, in the order the keys were given. |
+| `(AGGREGATE SUM \| MIN \| MAX)` | No | No | Under `AGGREGATE`, choose one form: `SUM`; `MIN`; `MAX`. |
+
+## Important points
+
+* `numkeys` must equal the number of key arguments that immediately follow it.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.zadd(
+    "key1",
+    { score: 1, member: "member1" },
+)
+await redis.zadd(
+    "key2",
+    { score: 1, member: "member1" },
+    { score: 2, member: "member2" },
+)
+
+const res = await redis.zinterstore("destination", 2, ["key1", "key2"]);
+console.log(res) // 1
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.zinterstore("destination-key", ["my-key"])
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.zinterstore("destination-key", "1", "my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.zInterStore("destination-key", "my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.zinterstore("destination-key", ["my-key"])
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ZInterStore(context.Background(), "destination-key", &redis.ZStore{Keys: []string{"my-key"}}).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.zinterstore("destination-key", "my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.zinterstore("destination-key", &["my-key"])?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# ZLEXCOUNT
+Source: https://upstash.com/docs/redis/commands/sorted-set/zlexcount
+
+Use `ZLEXCOUNT` to count members in lex range.
+
+## Syntax
+
+```redis
+ZLEXCOUNT <key> <min> <max>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<min>` | Yes | No | Lexicographic minimum: `-`, `+`, `[member` (inclusive), or `(member` (exclusive). |
+| `<max>` | Yes | No | Lexicographic maximum: `-`, `+`, `[member` (inclusive), or `(member` (exclusive). |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.zadd("key",
+    { score: 1, member: "one"},
+    { score: 2, member: "two" },
+);
+const elements = await redis.zlexcount("key", "two", "+");
+console.log(elements); // 1
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.zlexcount("my-key", "-", "+")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.zlexcount("my-key", "-", "+");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.zLexCount("my-key", "-", "+");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.zlexcount("my-key", "-", "+")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ZLexCount(context.Background(), "my-key", "-", "+").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.zlexcount("my-key", "-", "+");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.zlexcount("my-key", "-", "+")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# ZMPOP
+Source: https://upstash.com/docs/redis/commands/sorted-set/zmpop
+
+Use `ZMPOP` to pop members from sorted sets.
+
+## Syntax
+
+```redis
+ZMPOP <numkeys> <key> [<key> ...] (MIN | MAX) [COUNT <count>]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<numkeys>` | Yes | No | Number of key arguments that follow. |
+| `<key>` | Yes | Yes | Redis key targeted by the command. |
+| `(MIN \| MAX)` | Yes | No | Choose one form: `MIN`; `MAX`. |
+| `COUNT <count>` | No | No | Maximum number of members to pop. |
+
+## Important points
+
+* RESP2 represents floating-point reply values as bulk strings; RESP3 may use native double replies. Client libraries commonly decode either form to a language number.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Null bulk string or null array, or two-element array: key and array of member/score pairs |
+| RESP3 | Null, or two-element array: key and array of member/score pairs |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+<Note>
+  This command is not supported yet in `upstash_redis`.
+</Note>
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.zmpop("1", "my-key", "MIN");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.zmPop("my-key", "MIN");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.zmpop(1, ["my-key"], min=True)
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    _, result, err := client.ZMPop(context.Background(), "min", 0, "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.zmpop(redis.clients.jedis.args.SortedSetOption.MIN, "my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("ZMPOP");
+    command.arg("1");
+    command.arg("my-key");
+    command.arg("MIN");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# ZMSCORE
+Source: https://upstash.com/docs/redis/commands/sorted-set/zmscore
+
+Use `ZMSCORE` to get scores of multiple members.
+
+## Syntax
+
+```redis
+ZMSCORE <key> <member> [<member> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<member>` | Yes | Yes | Member name. |
+
+## Important points
+
+* RESP2 represents floating-point reply values as bulk strings; RESP3 may use native double replies. Client libraries commonly decode either form to a language number.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of bulk-string scores or null values, one per member |
+| RESP3 | Array of double scores or null values, one per member |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.zadd("key",
+    { score: 1, member: "m1" },
+    { score: 2, member: "m2" },
+    { score: 3, member: "m3" },
+    { score: 4, member: "m4" },
+)
+
+const scores = await redis.zmscore("key", ["m2", "m4"])
+console.log(scores) // [2, 4]
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.zmscore("my-key", ["member"])
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.zmscore("my-key", "member");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.zmScore("my-key", "member");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.zmscore("my-key", ["member"])
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ZMScore(context.Background(), "my-key", "member").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.zmscore("my-key", "member");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.zscore_multiple("my-key", &["member"])?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# ZPOPMAX
+Source: https://upstash.com/docs/redis/commands/sorted-set/zpopmax
+
+Use `ZPOPMAX` to pop members with highest scores.
+
+## Syntax
+
+```redis
+ZPOPMAX <key> [<count>]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<count>` | No | No | Number of members to pop. |
+
+## Important points
+
+* RESP2 represents floating-point reply values as bulk strings; RESP3 may use native double replies. Client libraries commonly decode either form to a language number.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Flat array of alternating members and bulk-string scores |
+| RESP3 | Flat array of alternating members and double scores |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const popped = await redis.zpopmax("key", 4);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.zpopmax("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.zpopmax("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.zPopMax("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.zpopmax("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ZPopMax(context.Background(), "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.zpopmax("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.zpopmax("my-key", 1)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# ZPOPMIN
+Source: https://upstash.com/docs/redis/commands/sorted-set/zpopmin
+
+Use `ZPOPMIN` to pop members with lowest scores.
+
+## Syntax
+
+```redis
+ZPOPMIN <key> [<count>]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<count>` | No | No | Number of members to pop. |
+
+## Important points
+
+* RESP2 represents floating-point reply values as bulk strings; RESP3 may use native double replies. Client libraries commonly decode either form to a language number.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Flat array of alternating members and bulk-string scores |
+| RESP3 | Flat array of alternating members and double scores |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const popped = await redis.zpopmin("key", 4);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.zpopmin("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.zpopmin("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.zPopMin("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.zpopmin("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ZPopMin(context.Background(), "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.zpopmin("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.zpopmin("my-key", 1)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# ZRANDMEMBER
+Source: https://upstash.com/docs/redis/commands/sorted-set/zrandmember
+
+Use `ZRANDMEMBER` to get random members.
+
+## Syntax
+
+```redis
+ZRANDMEMBER <key> [<count> [WITHSCORES]]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<count> [WITHSCORES]` | No | No | Number of members to return; a negative count may repeat members. `WITHSCORES` also returns each member's score. |
+
+## Important points
+
+* RESP2 represents floating-point reply values as bulk strings; RESP3 may use native double replies. Client libraries commonly decode either form to a language number.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Null bulk string or null array, Bulk string, array of members, or flat member/score array |
+| RESP3 | Null, Bulk string, array of members, or array of member/score pairs |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.zrandmember("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.zrandmember("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.zRandMember("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.zrandmember("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ZRandMember(context.Background(), "my-key", 1).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.zrandmember("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result: Option<String> = connection.zrandmember("my-key", None)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# ZRANGE
+Source: https://upstash.com/docs/redis/commands/sorted-set/zrange
+
+Use `ZRANGE` to get members by index range.
+
+## Syntax
+
+```redis
+ZRANGE <key> <start> <stop> [BYSCORE | BYLEX] [REV] [LIMIT <offset> <count>] [WITHSCORES]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<start>` | Yes | No | Lower bound. Interpreted as a rank by default, as a score with `BYSCORE`, or lexicographically with `BYLEX`. |
+| `<stop>` | Yes | No | Upper bound. Interpreted as a rank by default, as a score with `BYSCORE`, or lexicographically with `BYLEX`. |
+| `(BYSCORE \| BYLEX)` | No | No | Choose one form: `BYSCORE`; `BYLEX`. |
+| `REV` | No | No | Reverse the result order. |
+| `LIMIT <offset> <count>` | No | No | Skip `<offset>` matches and return at most `<count>`; a `<count>` of `-1` returns all remaining. |
+| `WITHSCORES` | No | No | Include sorted-set scores. |
+
+## Important points
+
+* Pair-based results may be flattened into one alternating array in RESP2 while RESP3 preserves nested pairs or a map.
+* RESP2 represents floating-point reply values as bulk strings; RESP3 may use native double replies. Client libraries commonly decode either form to a language number.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of members, or flat member/score array with `WITHSCORES` |
+| RESP3 | Array of members, or array of member/score pairs with `WITHSCORES` |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.zadd("key",
+    { score: 1, member: "m1" },
+    { score: 2, member: "m2" },
+)
+const res = await redis.zrange("key", 1, 3)
+console.log(res) // ["m2"]
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.zrange("my-key", 0, -1)
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.zrange("my-key", "0", "-1");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.zRange("my-key", 0, -1);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.zrange("my-key", 0, -1)
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ZRange(context.Background(), "my-key", 0, -1).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.zrange("my-key", 0, -1);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.zrange("my-key", 0, -1)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# ZRANGEBYLEX
+Source: https://upstash.com/docs/redis/commands/sorted-set/zrangebylex
+
+Use `ZRANGEBYLEX` to get members by lex range.
+
+## Syntax
+
+```redis
+ZRANGEBYLEX <key> <min> <max> [LIMIT <offset> <count>]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<min>` | Yes | No | Lexicographic minimum: `-`, `+`, `[member` (inclusive), or `(member` (exclusive). |
+| `<max>` | Yes | No | Lexicographic maximum: `-`, `+`, `[member` (inclusive), or `(member` (exclusive). |
+| `LIMIT <offset> <count>` | No | No | Skip `<offset>` matches and return at most `<count>`; a `<count>` of `-1` returns all remaining. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of bulk-string members |
+| RESP3 | Array of bulk-string members |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.zrangebylex("my-key", "-", "+")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.zrangebylex("my-key", "-", "+");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.zRangeByLex("my-key", "-", "+");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.zrangebylex("my-key", "-", "+")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ZRangeByLex(context.Background(), "my-key", &redis.ZRangeBy{Min: "-", Max: "+"}).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.zrangeByLex("my-key", "-", "+");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.zrangebylex("my-key", "-", "+")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# ZRANGEBYSCORE
+Source: https://upstash.com/docs/redis/commands/sorted-set/zrangebyscore
+
+Use `ZRANGEBYSCORE` to get members by score range.
+
+## Syntax
+
+```redis
+ZRANGEBYSCORE <key> <min> <max> [WITHSCORES] [LIMIT <offset> <count>]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<min>` | Yes | No | Minimum score: a number, `-inf`, or `(score` for an exclusive bound. |
+| `<max>` | Yes | No | Maximum score: a number, `+inf`, or `(score` for an exclusive bound. |
+| `WITHSCORES` | No | No | Include sorted-set scores. |
+| `LIMIT <offset> <count>` | No | No | Skip `<offset>` matches and return at most `<count>`; a `<count>` of `-1` returns all remaining. |
+
+## Important points
+
+* RESP2 represents floating-point reply values as bulk strings; RESP3 may use native double replies. Client libraries commonly decode either form to a language number.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of members, or flat member/score array with `WITHSCORES` |
+| RESP3 | Array of members, or array of member/score pairs with `WITHSCORES` |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.zrangebyscore("my-key", "1.5", "1.5")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.zrangebyscore("my-key", "1.5", "1.5");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.zRangeByScore("my-key", 1.5, 1.5);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.zrangebyscore("my-key", "1.5", "1.5")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ZRangeByScore(context.Background(), "my-key", &redis.ZRangeBy{Min: "1.5", Max: "1.5"}).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.zrangeByScore("my-key", 1.5, 1.5);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.zrangebyscore("my-key", 1.5, 1.5)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# ZRANGESTORE
+Source: https://upstash.com/docs/redis/commands/sorted-set/zrangestore
+
+Use `ZRANGESTORE` to store range result.
+
+## Syntax
+
+```redis
+ZRANGESTORE <dst> <src> <min> <max> [BYSCORE | BYLEX] [REV] [LIMIT <offset> <count>]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<dst>` | Yes | No | Redis key used as dst. |
+| `<src>` | Yes | No | Redis key used as src. |
+| `<min>` | Yes | No | Lower bound. Interpreted as a rank by default, as a score with `BYSCORE`, or lexicographically with `BYLEX`. |
+| `<max>` | Yes | No | Upper bound. Interpreted as a rank by default, as a score with `BYSCORE`, or lexicographically with `BYLEX`. |
+| `(BYSCORE \| BYLEX)` | No | No | Choose one form: `BYSCORE`; `BYLEX`. |
+| `REV` | No | No | Reverse the result order. |
+| `LIMIT <offset> <count>` | No | No | Skip `<offset>` matches and return at most `<count>`; a `<count>` of `-1` returns all remaining. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.zrangestore("destination-key", "source-key", "-inf", "+inf", sortby="BYSCORE")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.zrangestore("my-key", "my-key", "-inf", "+inf");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.zRangeStore("my-key", "my-key", "-inf", "+inf");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.zrangestore("destination-key", "source-key", "-inf", "+inf", byscore=True)
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ZRangeStore(context.Background(), "destination-key", redis.ZRangeArgs{Key: "source-key", Start: "-inf", Stop: "+inf", ByScore: true}).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.zrangestore("destination-key", "source-key", redis.clients.jedis.params.ZRangeParams.zrangeByScoreParams(Double.NEGATIVE_INFINITY, Double.POSITIVE_INFINITY));
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("ZRANGESTORE");
+    command.arg("my-key");
+    command.arg("my-key");
+    command.arg("-inf");
+    command.arg("+inf");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# ZRANK
+Source: https://upstash.com/docs/redis/commands/sorted-set/zrank
+
+Use `ZRANK` to get member's rank.
+
+## Syntax
+
+```redis
+ZRANK <key> <member> [WITHSCORE]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<member>` | Yes | No | Member name. |
+| `WITHSCORE` | No | No | Also return the member's score alongside its rank. |
+
+## Important points
+
+* RESP2 represents floating-point reply values as bulk strings; RESP3 may use native double replies. Client libraries commonly decode either form to a language number.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Null bulk string or null array, Integer, or two-element rank/score array |
+| RESP3 | Null, Integer, or two-element rank/score array |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const rank = await redis.zrank("key", "member");
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.zrank("my-key", "member")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.zrank("my-key", "member");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.zRank("my-key", "member");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.zrank("my-key", "member")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ZRank(context.Background(), "my-key", "member").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.zrank("my-key", "member");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.zrank("my-key", "member")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# ZREM
+Source: https://upstash.com/docs/redis/commands/sorted-set/zrem
+
+Use `ZREM` to remove members.
+
+## Syntax
+
+```redis
+ZREM <key> <member> [<member> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<member>` | Yes | Yes | Member name. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.zrem("key", "member");
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.zrem("my-key", "member")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.zrem("my-key", "member");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.zRem("my-key", "member");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.zrem("my-key", "member")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ZRem(context.Background(), "my-key", "member").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.zrem("my-key", "member");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.zrem("my-key", "member")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# ZREMRANGEBYLEX
+Source: https://upstash.com/docs/redis/commands/sorted-set/zremrangebylex
+
+Use `ZREMRANGEBYLEX` to remove members by lex range.
+
+## Syntax
+
+```redis
+ZREMRANGEBYLEX <key> <min> <max>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<min>` | Yes | No | Lexicographic minimum: `-`, `+`, `[member` (inclusive), or `(member` (exclusive). |
+| `<max>` | Yes | No | Lexicographic maximum: `-`, `+`, `[member` (inclusive), or `(member` (exclusive). |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.zremrangebylex("key", "alpha", "omega")
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.zremrangebylex("my-key", "-", "+")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.zremrangebylex("my-key", "-", "+");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.zRemRangeByLex("my-key", "-", "+");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.zremrangebylex("my-key", "-", "+")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ZRemRangeByLex(context.Background(), "my-key", "-", "+").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.zremrangeByLex("my-key", "-", "+");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.zrembylex("my-key", "-", "+")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# ZREMRANGEBYRANK
+Source: https://upstash.com/docs/redis/commands/sorted-set/zremrangebyrank
+
+Use `ZREMRANGEBYRANK` to remove members by rank range.
+
+## Syntax
+
+```redis
+ZREMRANGEBYRANK <key> <start> <stop>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<start>` | Yes | No | Start index; negative values count from the end. |
+| `<stop>` | Yes | No | Stop index, inclusive; negative values count from the end. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.zremrangebyrank("key", 4, 20)
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.zremrangebyrank("my-key", 0, 0)
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.zremrangebyrank("my-key", "0", "0");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.zRemRangeByRank("my-key", 0, 0);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.zremrangebyrank("my-key", 0, 0)
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ZRemRangeByRank(context.Background(), "my-key", 0, 0).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.zremrangeByRank("my-key", 0, 0);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.zremrangebyrank("my-key", 0, 0)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# ZREMRANGEBYSCORE
+Source: https://upstash.com/docs/redis/commands/sorted-set/zremrangebyscore
+
+Use `ZREMRANGEBYSCORE` to remove members by score range.
+
+## Syntax
+
+```redis
+ZREMRANGEBYSCORE <key> <min> <max>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<min>` | Yes | No | Minimum score: a number, `-inf`, or `(score` for an exclusive bound. |
+| `<max>` | Yes | No | Maximum score: a number, `+inf`, or `(score` for an exclusive bound. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.zremrangebyscore("key", 2, 5)
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.zremrangebyscore("my-key", 1.5, 1.5)
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.zremrangebyscore("my-key", "1.5", "1.5");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.zRemRangeByScore("my-key", 1.5, 1.5);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.zremrangebyscore("my-key", 1.5, 1.5)
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ZRemRangeByScore(context.Background(), "my-key", "1.5", "1.5").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.zremrangeByScore("my-key", 1.5, 1.5);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.zrembyscore("my-key", 1.5, 1.5)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# ZREVRANGE
+Source: https://upstash.com/docs/redis/commands/sorted-set/zrevrange
+
+Use `ZREVRANGE` to get members in reverse order.
+
+## Syntax
+
+```redis
+ZREVRANGE <key> <start> <stop> [WITHSCORES]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<start>` | Yes | No | Start index; negative values count from the end. |
+| `<stop>` | Yes | No | Stop index, inclusive; negative values count from the end. |
+| `WITHSCORES` | No | No | Include sorted-set scores. |
+
+## Important points
+
+* RESP2 represents floating-point reply values as bulk strings; RESP3 may use native double replies. Client libraries commonly decode either form to a language number.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of members, or flat member/score array with `WITHSCORES` |
+| RESP3 | Array of members, or array of member/score pairs with `WITHSCORES` |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.zrevrange("my-key", 0, 0)
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.zrevrange("my-key", "0", "0");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.zRange("my-key", 0, 0, { REV: true });
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.zrevrange("my-key", 0, 0)
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ZRevRange(context.Background(), "my-key", 0, -1).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.zrevrange("my-key", 0, -1);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.zrevrange("my-key", 0, -1)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# ZREVRANGEBYLEX
+Source: https://upstash.com/docs/redis/commands/sorted-set/zrevrangebylex
+
+Use `ZREVRANGEBYLEX` to list the members in a lexicographic range, in reverse order.
+
+## Syntax
+
+```redis
+ZREVRANGEBYLEX <key> <max> <min> [LIMIT <offset> <count>]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<max>` | Yes | No | Lexicographic maximum: `-`, `+`, `[member` (inclusive), or `(member` (exclusive). |
+| `<min>` | Yes | No | Lexicographic minimum: `-`, `+`, `[member` (inclusive), or `(member` (exclusive). |
+| `LIMIT <offset> <count>` | No | No | Skip `<offset>` matches and return at most `<count>`; a `<count>` of `-1` returns all remaining. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of bulk-string members |
+| RESP3 | Array of bulk-string members |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.zrevrangebylex("my-key", "+", "-")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.zrevrangebylex("my-key", "+", "-");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.zRange("my-key", "+", "-", { BY: "LEX", REV: true });
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.zrevrangebylex("my-key", "+", "-")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ZRevRangeByLex(context.Background(), "my-key", &redis.ZRangeBy{Min: "-", Max: "+"}).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.zrevrangeByLex("my-key", "+", "-");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.zrevrangebylex("my-key", "+", "-")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# ZREVRANGEBYSCORE
+Source: https://upstash.com/docs/redis/commands/sorted-set/zrevrangebyscore
+
+Use `ZREVRANGEBYSCORE` to list the members in a score range, ordered from the highest score down.
+
+## Syntax
+
+```redis
+ZREVRANGEBYSCORE <key> <max> <min> [WITHSCORES] [LIMIT <offset> <count>]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<max>` | Yes | No | Maximum score: a number, `+inf`, or `(score` for an exclusive bound. |
+| `<min>` | Yes | No | Minimum score: a number, `-inf`, or `(score` for an exclusive bound. |
+| `WITHSCORES` | No | No | Include sorted-set scores. |
+| `LIMIT <offset> <count>` | No | No | Skip `<offset>` matches and return at most `<count>`; a `<count>` of `-1` returns all remaining. |
+
+## Important points
+
+* RESP2 represents floating-point reply values as bulk strings; RESP3 may use native double replies. Client libraries commonly decode either form to a language number.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of members, or flat member/score array with `WITHSCORES` |
+| RESP3 | Array of members, or array of member/score pairs with `WITHSCORES` |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.zrevrangebyscore("my-key", "1.5", "1.5")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.zrevrangebyscore("my-key", "1.5", "1.5");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.zRange("my-key", 1.5, 1.5, { BY: "SCORE", REV: true });
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.zrevrangebyscore("my-key", "1.5", "1.5")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ZRevRangeByScore(context.Background(), "my-key", &redis.ZRangeBy{Min: "1.5", Max: "1.5"}).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.zrevrangeByScore("my-key", 1.5, 1.5);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.zrevrangebyscore("my-key", 1.5, 1.5)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# ZREVRANK
+Source: https://upstash.com/docs/redis/commands/sorted-set/zrevrank
+
+Use `ZREVRANK` to get member's reverse rank.
+
+## Syntax
+
+```redis
+ZREVRANK <key> <member> [WITHSCORE]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<member>` | Yes | No | Member name. |
+| `WITHSCORE` | No | No | Also return the member's score alongside its rank. |
+
+## Important points
+
+* RESP2 represents floating-point reply values as bulk strings; RESP3 may use native double replies. Client libraries commonly decode either form to a language number.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Null bulk string or null array, Integer, or two-element rank/score array |
+| RESP3 | Null, Integer, or two-element rank/score array |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const rank = await redis.zrevrank("key", "member");
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.zrevrank("my-key", "member")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.zrevrank("my-key", "member");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.zRevRank("my-key", "member");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.zrevrank("my-key", "member")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ZRevRank(context.Background(), "my-key", "member").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.zrevrank("my-key", "member");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.zrevrank("my-key", "member")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# ZSCAN
+Source: https://upstash.com/docs/redis/commands/sorted-set/zscan
+
+Use `ZSCAN` to incrementally iterate sorted set.
+
+## Syntax
+
+```redis
+ZSCAN <key> <cursor> [MATCH <pattern>] [COUNT <count>]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<cursor>` | Yes | No | Cursor returned by the previous call; start at `0`. |
+| `MATCH <pattern>` | No | No | Return only elements matching this glob-style pattern. |
+| `COUNT <count>` | No | No | Hint for how much work each iteration should do. |
+
+## Important points
+
+* This operation can inspect a large part of the database. Prefer cursor-based scans where possible and avoid unbounded use on hot paths.
+* The cursor is opaque. Start with `0` and continue until the server returns cursor `0`; a single iteration may return no elements.
+* RESP2 represents floating-point reply values as bulk strings; RESP3 may use native double replies. Client libraries commonly decode either form to a language number.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Two-element array: cursor and flat member/score array |
+| RESP3 | Two-element array: cursor and flat member/score array |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.zadd("key",
+    { score: 1, member: "a" },
+    { score: 2, member: "ab" },
+    { score: 3, member: "b" },
+    { score: 4, member: "c" },
+    { score: 5, member: "d" },
+)
+const [newCursor, members] = await redis.zscan("key", 0, { match: "a*"});
+console.log(newCursor); // likely `0` since this is a very small set
+console.log(members); // ["a", "ab"]
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.zscan("my-key", 0)
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.zscan("my-key", "0");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.zScan("my-key", "0");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.zscan("my-key", 0)
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, _, err := client.ZScan(context.Background(), "my-key", 0, "*", 0).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.zscan("my-key", "0");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("ZSCAN");
+    command.arg("my-key");
+    command.arg("0");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# ZSCORE
+Source: https://upstash.com/docs/redis/commands/sorted-set/zscore
+
+Use `ZSCORE` to get member's score.
+
+## Syntax
+
+```redis
+ZSCORE <key> <member>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<member>` | Yes | No | Member name. |
+
+## Important points
+
+* RESP2 represents floating-point reply values as bulk strings; RESP3 may use native double replies. Client libraries commonly decode either form to a language number.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Bulk string containing a number or Null bulk string or null array |
+| RESP3 | Double or Null |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.zadd("key",
+    { score: 1, member: "m1" },
+    { score: 2, member: "m2" },
+    { score: 3, member: "m3" },
+    { score: 4, member: "m4" },
+)
+
+const score = await redis.zscore("key", "m2")
+console.log(score) // 2
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.zscore("my-key", "member")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.zscore("my-key", "member");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.zScore("my-key", "member");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.zscore("my-key", "member")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ZScore(context.Background(), "my-key", "member").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.zscore("my-key", "member");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.zscore("my-key", "member")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# ZUNION
+Source: https://upstash.com/docs/redis/commands/sorted-set/zunion
+
+Use `ZUNION` to get sorted set union.
+
+## Syntax
+
+```redis
+ZUNION <numkeys> <key> [<key> ...] [WEIGHTS <weight> [<weight> ...]] [AGGREGATE SUM | MIN | MAX] [WITHSCORES]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<numkeys>` | Yes | No | Number of key arguments that follow. |
+| `<key>` | Yes | Yes | Redis key targeted by the command. |
+| `WEIGHTS <weight>` | No | Yes | Multiplier applied to each input key's scores, in the order the keys were given. |
+| `(AGGREGATE SUM \| MIN \| MAX)` | No | No | Under `AGGREGATE`, choose one form: `SUM`; `MIN`; `MAX`. |
+| `WITHSCORES` | No | No | Include sorted-set scores. |
+
+## Important points
+
+* `numkeys` must equal the number of key arguments that immediately follow it.
+* RESP2 represents floating-point reply values as bulk strings; RESP3 may use native double replies. Client libraries commonly decode either form to a language number.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of members, or flat member/score array with `WITHSCORES` |
+| RESP3 | Array of members, or array of member/score pairs with `WITHSCORES` |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+const result = await redis.zunion(1, "my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.zunion(["my-key"])
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.zunion("1", "my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.zUnion("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.zunion(["my-key"])
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ZUnion(context.Background(), redis.ZStore{Keys: []string{"my-key"}}).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.zunion(new redis.clients.jedis.params.ZParams(), "my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("ZUNION");
+    command.arg("1");
+    command.arg("my-key");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# ZUNIONSTORE
+Source: https://upstash.com/docs/redis/commands/sorted-set/zunionstore
+
+Use `ZUNIONSTORE` to store sorted set union.
+
+## Syntax
+
+```redis
+ZUNIONSTORE <destination> <numkeys> <key> [<key> ...] [WEIGHTS <weight> [<weight> ...]] [AGGREGATE SUM | MIN | MAX]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<destination>` | Yes | No | Redis key used as destination. |
+| `<numkeys>` | Yes | No | Number of key arguments that follow. |
+| `<key>` | Yes | Yes | Redis key targeted by the command. |
+| `WEIGHTS <weight>` | No | Yes | Multiplier applied to each input key's scores, in the order the keys were given. |
+| `(AGGREGATE SUM \| MIN \| MAX)` | No | No | Under `AGGREGATE`, choose one form: `SUM`; `MIN`; `MAX`. |
+
+## Important points
+
+* `numkeys` must equal the number of key arguments that immediately follow it.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.zadd(
+    "key1",
+    { score: 1, member: "member1" },
+)
+await redis.zadd(
+    "key2",
+    { score: 1, member: "member1" },
+    { score: 2, member: "member2" },
+)
+
+const res = await redis.zunionstore("destination", 2, ["key1", "key2"]);
+console.log(res) // 2
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.zunionstore("destination-key", ["my-key"])
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.zunionstore("destination-key", "1", "my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.zUnionStore("destination-key", "my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.zunionstore("destination-key", ["my-key"])
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ZUnionStore(context.Background(), "destination-key", &redis.ZStore{Keys: []string{"my-key"}}).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.zunionstore("destination-key", "my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.zunionstore("destination-key", &["my-key"])?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# Streams commands
+Source: https://upstash.com/docs/redis/commands/streams/overview
+
+<CardGroup cols={2}>
+<Card title="XACK" href="/redis/commands/streams/xack">Acknowledge stream messages</Card>
+<Card title="XACKDEL" href="/redis/commands/streams/xackdel">Acknowledge and delete messages</Card>
+<Card title="XADD" href="/redis/commands/streams/xadd">Add entry to stream</Card>
+<Card title="XAUTOCLAIM" href="/redis/commands/streams/xautoclaim">Auto-claim idle messages</Card>
+<Card title="XCLAIM" href="/redis/commands/streams/xclaim">Claim pending messages</Card>
+<Card title="XDEL" href="/redis/commands/streams/xdel">Delete stream entries</Card>
+<Card title="XDELEX" href="/redis/commands/streams/xdelex">Delete entries with expiration</Card>
+<Card title="XGROUP" href="/redis/commands/streams/xgroup">Manage consumer groups</Card>
+<Card title="XINFO CONSUMERS" href="/redis/commands/streams/xinfo-consumers">List group consumers</Card>
+<Card title="XINFO GROUPS" href="/redis/commands/streams/xinfo-groups">List stream groups</Card>
+<Card title="XINFO STREAM" href="/redis/commands/streams/xinfo-stream">Get stream info</Card>
+<Card title="XLEN" href="/redis/commands/streams/xlen">Get stream length</Card>
+<Card title="XPENDING" href="/redis/commands/streams/xpending">Get pending messages info</Card>
+<Card title="XRANGE" href="/redis/commands/streams/xrange">Get range of stream entries</Card>
+<Card title="XREAD" href="/redis/commands/streams/xread">Read stream entries</Card>
+<Card title="XREADGROUP" href="/redis/commands/streams/xreadgroup">Read as consumer group</Card>
+<Card title="XREVRANGE" href="/redis/commands/streams/xrevrange">Get range in reverse order</Card>
+<Card title="XTRIM" href="/redis/commands/streams/xtrim">Trim stream to max length</Card>
+</CardGroup>
+
+# XACK
+Source: https://upstash.com/docs/redis/commands/streams/xack
+
+Use `XACK` to acknowledge stream messages.
+
+## Syntax
+
+```redis
+XACK <key> <group> <ID> [<ID> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<group>` | Yes | No | Consumer group name. |
+| `<ID>` | Yes | Yes | Stream entry ID. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const result = await redis.xack("mystream", "mygroup", "1638360173533-0");
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.xack("my-key", "workers", "0-0")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.xack("my-key", "workers", "0-0");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.xAck("my-key", "workers", "0-0");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.xack("my-key", "workers", "0-0")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.XAck(context.Background(), "my-key", "workers", "0-0").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.xack("my-key", "workers", new redis.clients.jedis.StreamEntryID("0-0"));
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.xack("my-key", "workers", &["0-0"])?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# XACKDEL
+Source: https://upstash.com/docs/redis/commands/streams/xackdel
+
+Use `XACKDEL` to acknowledge and delete messages.
+
+## Syntax
+
+```redis
+XACKDEL <key> <group> [KEEPREF | DELREF | ACKED] IDS <numids> <id> [<id> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<group>` | Yes | No | Consumer group name. |
+| `(KEEPREF \| DELREF \| ACKED)` | No | No | Choose one form: `KEEPREF`; `DELREF`; `ACKED`. |
+| `IDS <numids> <id> [<id> ...]` | Yes | No | Entry IDs to target. Give the ID count first, then that many IDs. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of integer status codes, one per ID |
+| RESP3 | Array of integer status codes, one per ID |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+// Acknowledge and delete a single entry
+const result = await redis.xackdel("mystream", "mygroup", "1638360173533-0");
+console.log(result); // Array of results for each ID
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.xackdel("my-key", "workers", "0-0")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.call("XACKDEL", "my-key", "workers", "IDS", "1", "0-0");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.xAckDel("my-key", "workers", "0-0");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.xackdel("my-key", "workers", "0-0")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.XAckDel(context.Background(), "my-key", "workers", "KEEPREF", "0-0").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.xackdel("my-key", "workers", new redis.clients.jedis.StreamEntryID("0-0"));
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.xack_del("my-key", "workers", &["0-0"], redis::streams::StreamDeletionPolicy::KeepRef)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# XADD
+Source: https://upstash.com/docs/redis/commands/streams/xadd
+
+Use `XADD` to add entry to stream.
+
+## Syntax
+
+```redis
+XADD <key> [NOMKSTREAM] [KEEPREF | DELREF | ACKED] [(MAXLEN | MINID) [= | ~] <threshold> [LIMIT <count>]] (* | <id>) <field> <value> [<field> <value> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `NOMKSTREAM` | No | No | Do not create a missing stream. |
+| `(KEEPREF \| DELREF \| ACKED)` | No | No | Choose one form: `KEEPREF`; `DELREF`; `ACKED`. |
+| `(MAXLEN \| MINID) [= \| ~] <threshold> [LIMIT <count>]` | No | No | Trim the stream after the entry is added. `MAXLEN` caps the number of entries; `MINID` drops entries with a lower ID. `=` trims exactly and is the default; `~` trims approximately and is required before `LIMIT`, which caps how many entries a single call evicts. |
+| `(* \| <id>)` | Yes | No | Choose one form: `*`. |
+| `<field> <value>` | Yes | Yes | Field and the value to store in it. Repeat to set several fields in one call. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Bulk string or Null bulk string or null array |
+| RESP3 | Bulk string or Null |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const result = await redis.xadd("mystream", "*", { name: "John Doe", age: 30 });
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.xadd("my-key", "*", {"field": "value"})
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.xadd("my-key", "*", "field", "value");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.xAdd("my-key", "*", { field: "value" });
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.xadd("my-key", {"field": "value"})
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.XAdd(context.Background(), &redis.XAddArgs{Stream: "my-key", Values: map[string]interface{}{"field": "value"}}).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.xadd("my-key", redis.clients.jedis.StreamEntryID.NEW_ENTRY, java.util.Map.of("field", "value"));
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.xadd("my-key", "*", &[("field", "value")])?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# XAUTOCLAIM
+Source: https://upstash.com/docs/redis/commands/streams/xautoclaim
+
+Use `XAUTOCLAIM` to auto-claim idle messages.
+
+## Syntax
+
+```redis
+XAUTOCLAIM <key> <group> <consumer> <min-idle-time> <start> [COUNT <count>] [JUSTID]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<group>` | Yes | No | Consumer group name. |
+| `<consumer>` | Yes | No | Consumer name within the group. |
+| `<min-idle-time>` | Yes | No | Only claim entries that have been idle at least this many milliseconds. |
+| `<start>` | Yes | No | ID to start scanning the pending list from; `0-0` starts at the beginning. |
+| `COUNT <count>` | No | No | Maximum number of entries to claim. |
+| `JUSTID` | No | No | Return only entry IDs, without their fields and values. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Three-element array: next ID, claimed entries or IDs, and deleted IDs |
+| RESP3 | Three-element array: next ID, claimed entries or IDs, and deleted IDs |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const result = await redis.xautoclaim(
+  "mystream",
+  "mygroup",
+  "consumer1",
+  60000,
+  "0-0"
+);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.xautoclaim("my-key", "workers", "worker-1", 60000, "0-0")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.xautoclaim("my-key", "workers", "worker-1", "60000", "0-0");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.xAutoClaim("my-key", "workers", "worker-1", 60000, "0-0");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.xautoclaim("my-key", "workers", "worker-1", 60000, "0-0")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+    "time"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, _, err := client.XAutoClaim(context.Background(), &redis.XAutoClaimArgs{Stream: "my-key", Group: "workers", Consumer: "worker-1", MinIdle: time.Minute, Start: "0-0"}).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.xautoclaim("my-key", "workers", "worker-1", 60000, new redis.clients.jedis.StreamEntryID("0-0"), redis.clients.jedis.params.XAutoClaimParams.xAutoClaimParams());
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("XAUTOCLAIM");
+    command.arg("my-key");
+    command.arg("workers");
+    command.arg("worker-1");
+    command.arg("min-idle-time");
+    command.arg("start");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# XCLAIM
+Source: https://upstash.com/docs/redis/commands/streams/xclaim
+
+Use `XCLAIM` to claim pending messages.
+
+## Syntax
+
+```redis
+XCLAIM <key> <group> <consumer> <min-idle-time> <ID> [<ID> ...] [IDLE <ms>] [TIME <unix-time-milliseconds>] [RETRYCOUNT <count>] [FORCE] [JUSTID] [LASTID <lastid>]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<group>` | Yes | No | Consumer group name. |
+| `<consumer>` | Yes | No | Consumer name within the group. |
+| `<min-idle-time>` | Yes | No | Only claim entries that have been idle at least this many milliseconds. |
+| `<ID>` | Yes | Yes | Stream entry ID. |
+| `IDLE <ms>` | No | No | Set the entry's idle time to this many milliseconds. |
+| `TIME <unix-time-milliseconds>` | No | No | Set the entry's last-delivery time to this Unix timestamp in milliseconds. |
+| `RETRYCOUNT <count>` | No | No | Set the entry's delivery counter to this value. |
+| `FORCE` | No | No | Create the pending entry even when the ID is not in the group's pending list. |
+| `JUSTID` | No | No | Return only entry IDs, without their fields and values. |
+| `LASTID <lastid>` | No | No | New last-delivered ID for the group. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of entry arrays, or array of IDs with `JUSTID` |
+| RESP3 | Array of entry arrays, or array of IDs with `JUSTID` |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const result = await redis.xclaim(
+  "mystream",
+  "mygroup",
+  "consumer1",
+  60000,
+  ["1638360173533-0", "1638360173533-1"]
+);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.xclaim("my-key", "workers", "worker-1", 60000, "0-0")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.xclaim("my-key", "workers", "worker-1", "60000", "0-0");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.xClaim("my-key", "workers", "worker-1", 60000, "0-0");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.xclaim("my-key", "workers", "worker-1", 60000, ["0-0"])
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+    "time"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.XClaim(context.Background(), &redis.XClaimArgs{Stream: "my-key", Group: "workers", Consumer: "worker-1", MinIdle: time.Minute, Messages: []string{"0-0"}}).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.xclaim("my-key", "workers", "worker-1", 60000, redis.clients.jedis.params.XClaimParams.xClaimParams(), new redis.clients.jedis.StreamEntryID("0-0"));
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.xclaim("my-key", "workers", "worker-1", 60000, &["0-0"])?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# XDEL
+Source: https://upstash.com/docs/redis/commands/streams/xdel
+
+Use `XDEL` to delete stream entries.
+
+## Syntax
+
+```redis
+XDEL <key> <ID> [<ID> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<ID>` | Yes | Yes | Stream entry ID. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const result = await redis.xdel("mystream", "1638360173533-0");
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.xdel("my-key", "0-0")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.xdel("my-key", "0-0");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.xDel("my-key", "0-0");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.xdel("my-key", "0-0")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.XDel(context.Background(), "my-key", "0-0").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.xdel("my-key", new redis.clients.jedis.StreamEntryID("0-0"));
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.xdel("my-key", &["0-0"])?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# XDELEX
+Source: https://upstash.com/docs/redis/commands/streams/xdelex
+
+Use `XDELEX` to delete entries with expiration.
+
+## Syntax
+
+```redis
+XDELEX <key> [KEEPREF | DELREF | ACKED] IDS <numids> <id> [<id> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `(KEEPREF \| DELREF \| ACKED)` | No | No | Choose one form: `KEEPREF`; `DELREF`; `ACKED`. |
+| `IDS <numids> <id> [<id> ...]` | Yes | No | Entry IDs to target. Give the ID count first, then that many IDs. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of integer status codes, one per ID |
+| RESP3 | Array of integer status codes, one per ID |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+// Delete a single stream entry
+const result = await redis.xdelex("mystream", "1638360173533-0");
+console.log(result); // Array of results for each ID
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.xdelex("my-key", "0-0")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.xdelex("my-key", "IDS", "1", "0-0");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.xDelEx("my-key", "0-0");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.xdelex("my-key", "0-0")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.XDelEx(context.Background(), "my-key", "KEEPREF", "0-0").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.xdelex("my-key", new redis.clients.jedis.StreamEntryID("0-0"));
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.xdel_ex("my-key", &["0-0"], redis::streams::StreamDeletionPolicy::KeepRef)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# XGROUP
+Source: https://upstash.com/docs/redis/commands/streams/xgroup
+
+Use `XGROUP` to manage consumer groups.
+
+## Syntax
+
+```redis
+XGROUP CREATE <key> <group> <id | $> [MKSTREAM]
+XGROUP CREATECONSUMER <key> <group> <consumer>
+XGROUP DELCONSUMER <key> <group> <consumer>
+XGROUP DESTROY <key> <group>
+XGROUP SETID <key> <group> <id | $>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `subcommand` | Yes | No | Consumer-group operation shown in the syntax block. |
+| `key` | Yes | No | Stream key. |
+| `group` | Yes | No | Consumer-group name. |
+| `consumer` | Some forms | No | Consumer name for CREATECONSUMER or DELCONSUMER. |
+| `id \| $` | Some forms | No | Starting or replacement last-delivered ID; `$` means the stream's latest ID. |
+| `MKSTREAM` | No | No | Create an empty stream when CREATE targets a missing key. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Simple string `OK` for `CREATE` and `SETID`; Integer for `CREATECONSUMER`, `DELCONSUMER`, and `DESTROY` |
+| RESP3 | Simple string `OK` for `CREATE` and `SETID`; Integer for `CREATECONSUMER`, `DELCONSUMER`, and `DESTROY` |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const result = await redis.xgroup("mystream", {
+  type: "CREATE",
+  group: "mygroup",
+  id: "$",
+  options: { MKSTREAM: true }
+});
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.xgroup_create("events", "workers", "$", mkstream=True)
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.xgroup("CREATE", "events", "workers", "$", "MKSTREAM");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.xGroupCreate("events", "workers", "$", { MKSTREAM: true });
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.xgroup_create("events", "workers", "$", mkstream=True)
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.XGroupCreateMkStream(context.Background(), "events", "workers", "$").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.xgroupCreate("events", "workers", redis.clients.jedis.StreamEntryID.LAST_ENTRY, true);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.xgroup_create_mkstream("events", "workers", "$")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# XINFO CONSUMERS
+Source: https://upstash.com/docs/redis/commands/streams/xinfo-consumers
+
+Use `XINFO CONSUMERS` to list group consumers.
+
+## Syntax
+
+```redis
+XINFO CONSUMERS <key> <group>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<group>` | Yes | No | Consumer group name. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of flat consumer-metadata arrays |
+| RESP3 | Array of flat consumer-metadata arrays |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+const result = await redis.xinfo("my-key", {
+  type: "CONSUMERS",
+  group: "workers",
+});
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.xinfo_consumers("my-key", "workers")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.xinfo("CONSUMERS", "my-key", "workers");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.xInfoConsumers("my-key", "workers");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.xinfo_consumers("my-key", "workers")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.XInfoConsumers(context.Background(), "my-key", "workers").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.xinfoConsumers("my-key", "workers");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.xinfo_consumers("my-key", "workers")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# XINFO GROUPS
+Source: https://upstash.com/docs/redis/commands/streams/xinfo-groups
+
+Use `XINFO GROUPS` to list stream groups.
+
+## Syntax
+
+```redis
+XINFO GROUPS <key>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of flat group-metadata arrays |
+| RESP3 | Array of flat group-metadata arrays |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+const result = await redis.xinfo("my-key", { type: "GROUPS" });
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.xinfo_groups("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.xinfo("GROUPS", "my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.xInfoGroups("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.xinfo_groups("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.XInfoGroups(context.Background(), "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.xinfoGroups("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.xinfo_groups("my-key")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# XINFO STREAM
+Source: https://upstash.com/docs/redis/commands/streams/xinfo-stream
+
+Use `XINFO STREAM` to get stream info.
+
+## Syntax
+
+```redis
+XINFO STREAM <key> [FULL [COUNT <count>]]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `FULL [COUNT <count>]` | No | No | Return the full report, including entries and consumer-group state. `COUNT` caps how many entries each section lists; `0` returns all of them. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Flat array of alternating keys and values |
+| RESP3 | Map |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+<Note>
+  This command is not supported yet in `upstash_redis`.
+</Note>
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.xinfo("STREAM", "my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.xInfoStream("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.xinfo_stream("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.XInfoStream(context.Background(), "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.xinfoStream("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.xinfo_stream("my-key")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# XLEN
+Source: https://upstash.com/docs/redis/commands/streams/xlen
+
+Use `XLEN` to get stream length.
+
+## Syntax
+
+```redis
+XLEN <key>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const result = await redis.xlen("mystream");
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.xlen("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.xlen("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.xLen("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.xlen("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.XLen(context.Background(), "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.xlen("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.xlen("my-key")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# XPENDING
+Source: https://upstash.com/docs/redis/commands/streams/xpending
+
+Use `XPENDING` to get pending messages info.
+
+## Syntax
+
+```redis
+XPENDING <key> <group> [[IDLE <min-idle-time>] <start> <end> <count> [<consumer>]]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<group>` | Yes | No | Consumer group name. |
+| `[IDLE <min-idle-time>] <start> <end> <count> [<consumer>]` | No | No | Extended form: optionally filter by idle time, then give the ID range, the maximum number of entries to return, and optionally a single consumer to report on. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Four-element summary array, or array of pending-entry detail arrays |
+| RESP3 | Four-element summary array, or array of pending-entry detail arrays |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const result = await redis.xpending("mystream", "mygroup", "-", "+", 10);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.xpending("my-key", "workers")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.xpending("my-key", "workers");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.xPending("my-key", "workers");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.xpending("my-key", "workers")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.XPending(context.Background(), "my-key", "workers").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.xpending("my-key", "workers");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.xpending("my-key", "workers")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# XRANGE
+Source: https://upstash.com/docs/redis/commands/streams/xrange
+
+Use `XRANGE` to get range of stream entries.
+
+## Syntax
+
+```redis
+XRANGE <key> <start> <end> [COUNT <count>]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<start>` | Yes | No | First ID to return; `-` means the smallest possible ID. |
+| `<end>` | Yes | No | Last ID to return; `+` means the largest possible ID. |
+| `COUNT <count>` | No | No | Maximum number of entries to return. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of two-element entry arrays: ID and flat field/value array |
+| RESP3 | Array of two-element entry arrays: ID and flat field/value array |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const result = await redis.xrange("mystream", "-", "+");
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.xrange("my-key", "-", "+")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.xrange("my-key", "-", "+");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.xRange("my-key", "-", "+");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.xrange("my-key", "-", "+")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.XRange(context.Background(), "my-key", "-", "+").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.xrange("my-key", "-", "+");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.xrange("my-key", "-", "+")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# XREAD
+Source: https://upstash.com/docs/redis/commands/streams/xread
+
+Use `XREAD` to read stream entries.
+
+## Syntax
+
+```redis
+XREAD [COUNT <count>] [BLOCK <milliseconds>] STREAMS <key> [<key> ...] <ID> [<ID> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `COUNT <count>` | No | No | Maximum number of entries to return per stream. |
+| `BLOCK <milliseconds>` | No | No | Milliseconds to block waiting for new entries; `0` blocks indefinitely. |
+| `STREAMS <key> [<key> ...] <ID> [<ID> ...]` | Yes | No | Streams to read. List every key first, then one ID per key in the same order. |
+
+## Important points
+
+* A blocking form holds the request until data arrives or its timeout expires. Set the client/network timeout longer than the command timeout.
+* After `STREAMS`, provide all keys first and then exactly one ID for each key, in the same order.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Flat array of alternating keys and values or Null bulk string or null array |
+| RESP3 | Map or Null |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const result = await redis.xread("mystream", "0-0");
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.xread({"my-key": "0-0"})
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.xread("STREAMS", "my-key", "0-0");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.xRead({ key: "my-key", id: "0-0" });
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.xread({"my-key": "0-0"})
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.XRead(context.Background(), &redis.XReadArgs{Streams: []string{"my-key", "0-0"}}).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.xread(redis.clients.jedis.params.XReadParams.xReadParams(), java.util.Map.of("my-key", new redis.clients.jedis.StreamEntryID("0-0")));
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.xread(&["my-key"], &["0-0"])?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# XREADGROUP
+Source: https://upstash.com/docs/redis/commands/streams/xreadgroup
+
+Use `XREADGROUP` to read as consumer group.
+
+## Syntax
+
+```redis
+XREADGROUP GROUP <group> <consumer> [COUNT <count>] [BLOCK <milliseconds>] [NOACK] STREAMS <key> [<key> ...] <ID> [<ID> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `GROUP <group> <consumer>` | Yes | No | Consumer group to read from, and the consumer within it that claims the entries. |
+| `COUNT <count>` | No | No | Maximum number of entries to return per stream. |
+| `BLOCK <milliseconds>` | No | No | Milliseconds to block waiting for new entries; `0` blocks indefinitely. |
+| `NOACK` | No | No | Do not add delivered entries to the pending list. |
+| `STREAMS <key> [<key> ...] <ID> [<ID> ...]` | Yes | No | Streams to read. List every key first, then one ID per key in the same order. |
+
+## Important points
+
+* A blocking form holds the request until data arrives or its timeout expires. Set the client/network timeout longer than the command timeout.
+* After `STREAMS`, provide all keys first and then exactly one ID for each key, in the same order.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Null bulk string or null array or Flat array of alternating keys and values |
+| RESP3 | Null or Map |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const result = await redis.xreadgroup("mygroup", "consumer1", "mystream", ">");
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.xreadgroup("workers", "worker-1", {"my-key": "0-0"})
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.xreadgroup("GROUP", "workers", "worker-1", "STREAMS", "my-key", "0-0");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.xReadGroup("workers", "worker-1", { key: "my-key", id: "0-0" });
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.xreadgroup("workers", "worker-1", {"my-key": "0-0"})
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.XReadGroup(context.Background(), &redis.XReadGroupArgs{Group: "workers", Consumer: "worker-1", Streams: []string{"my-key", "0-0"}}).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.xreadGroup("workers", "worker-1", redis.clients.jedis.params.XReadGroupParams.xReadGroupParams(), java.util.Map.of("my-key", new redis.clients.jedis.StreamEntryID("0-0")));
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("XREADGROUP");
+    command.arg("GROUP");
+    command.arg("workers");
+    command.arg("worker-1");
+    command.arg("STREAMS");
+    command.arg("my-key");
+    command.arg("0-0");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# XREVRANGE
+Source: https://upstash.com/docs/redis/commands/streams/xrevrange
+
+Use `XREVRANGE` to get range in reverse order.
+
+## Syntax
+
+```redis
+XREVRANGE <key> <end> <start> [COUNT <count>]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<end>` | Yes | No | Last ID to return, scanning backwards; `-` means the smallest possible ID. |
+| `<start>` | Yes | No | First ID to return, scanning backwards; `+` means the largest possible ID. |
+| `COUNT <count>` | No | No | Maximum number of entries to return. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of two-element entry arrays: ID and flat field/value array |
+| RESP3 | Array of two-element entry arrays: ID and flat field/value array |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const result = await redis.xrevrange("mystream", "+", "-");
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.xrevrange("my-key", "+", "-")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.xrevrange("my-key", "+", "-");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.xRevRange("my-key", "+", "-");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.xrevrange("my-key", "+", "-")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.XRevRange(context.Background(), "my-key", "+", "-").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.xrevrange("my-key", "+", "-");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.xrevrange("my-key", "+", "-")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# XTRIM
+Source: https://upstash.com/docs/redis/commands/streams/xtrim
+
+Use `XTRIM` to trim stream to max length.
+
+## Syntax
+
+```redis
+XTRIM <key> (MAXLEN | MINID) [= | ~] <threshold> [LIMIT <count>] [KEEPREF | DELREF | ACKED]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `(MAXLEN \| MINID) [= \| ~] <threshold> [LIMIT <count>] [KEEPREF \| DELREF \| ACKED]` | Yes | No | Trim the stream. `MAXLEN` caps the number of entries; `MINID` drops entries with a lower ID. `=` trims exactly and is the default; `~` trims approximately and is required before `LIMIT`, which caps how many entries a single call evicts. `KEEPREF` (the default) leaves consumer-group references to the deleted entries in place, `DELREF` removes those references too, and `ACKED` only removes entries that every group has read and acknowledged. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const result = await redis.xtrim("mystream", {
+  strategy: "MAXLEN",
+  threshold: 100,
+  exactness: "~"
+});
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.xtrim("my-key", maxlen=100)
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.xtrim("my-key", "MAXLEN", "100");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.xTrim("my-key", "MAXLEN", 100);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.xtrim("my-key", maxlen=100)
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.XTrimMaxLen(context.Background(), "my-key", 100).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.xtrim("my-key", redis.clients.jedis.params.XTrimParams.xTrimParams().maxLen(100));
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.xtrim("my-key", redis::streams::StreamMaxlen::Equals(100))?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# APPEND
+Source: https://upstash.com/docs/redis/commands/string/append
+
+Use `APPEND` to append value to a string.
+
+## Syntax
+
+```redis
+APPEND <key> <value>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<value>` | Yes | No | String appended to the current value. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.append(key, "Hello");
+// returns 5
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.append("my-key", "value")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.append("my-key", "value");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.append("my-key", "value");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.append("my-key", "value")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.Append(context.Background(), "my-key", "value").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.append("my-key", "value");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.append("my-key", "value")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# DECR
+Source: https://upstash.com/docs/redis/commands/string/decr
+
+Use `DECR` to decrement integer value by 1.
+
+## Syntax
+
+```redis
+DECR <key>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.set("key", 6);
+await redis.decr("key");
+// returns 5
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.decr("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.decr("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.decr("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.decr("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.Decr(context.Background(), "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.decr("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.decr("my-key", 1)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# DECRBY
+Source: https://upstash.com/docs/redis/commands/string/decrby
+
+Use `DECRBY` to decrement integer by amount.
+
+## Syntax
+
+```redis
+DECRBY <key> <decrement>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<decrement>` | Yes | No | Amount to subtract from the current value. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.set("key", 6);
+await redis.decrby("key", 4);
+// returns 2
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.decrby("my-key", 1)
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.decrby("my-key", "1");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.decrBy("my-key", 1);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.decrby("my-key", 1)
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.DecrBy(context.Background(), "my-key", 1).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.decrBy("my-key", 1);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.decr("my-key", 1)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# DELEX
+Source: https://upstash.com/docs/redis/commands/string/delex
+
+Use `DELEX` to delete a string when a condition matches.
+
+## Syntax
+
+```redis
+DELEX <key> [IFEQ <value> | IFNE <value> | IFDEQ <digest> | IFDNE <digest>]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `key` | Yes | No | String key to delete. |
+| `IFEQ value \| IFNE value` | No | No | Delete when the stored string is equal to or different from the supplied value. |
+| `IFDEQ digest \| IFDNE digest` | No | No | Delete when the stored string digest is equal to or different from the supplied 16-character digest. |
+
+## Important points
+
+* Supply at most one condition. With no condition, `DELEX` behaves like deleting a single key.
+* Conditional forms accept string keys only. A non-string value returns an error and is not deleted.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+<Note>
+  This command is not supported yet in `upstash_redis`.
+</Note>
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.call("DELEX", "lock:job-1", "IFEQ", "worker-1");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.delEx("lock:job-1", { condition: "IFEQ", matchValue: "worker-1" });
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.execute_command("DELEX", "lock:job-1", "IFEQ", "worker-1")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.DelExArgs(context.Background(), "lock:job-1", redis.DelExArgs{Mode: "IFEQ", MatchValue: "worker-1"}).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.delex("lock:job-1", redis.clients.jedis.util.CompareCondition.valueEq("worker-1"));
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.del_ex("lock:job-1", redis::ValueComparison::ifeq("worker-1"))?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# DIGEST
+Source: https://upstash.com/docs/redis/commands/string/digest
+
+Use `DIGEST` to get the digest of a string value.
+
+## Syntax
+
+```redis
+DIGEST <key>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `key` | Yes | No | String key whose value should be hashed. |
+
+## Important points
+
+* The reply is a 16-character lowercase hexadecimal XXH3 digest of the stored string bytes.
+* A missing key returns null. A key containing a non-string value returns `WRONGTYPE`.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Bulk string or Null bulk string or null array |
+| RESP3 | Bulk string or Null |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+<Note>
+  This command is not supported yet in `upstash_redis`.
+</Note>
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.call("DIGEST", "lock:job-1");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.digest("lock:job-1");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.execute_command("DIGEST", "lock:job-1")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.Digest(context.Background(), "lock:job-1").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.digestKey("lock:job-1");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.digest("lock:job-1")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# GET
+Source: https://upstash.com/docs/redis/commands/string/get
+
+Use `GET` to get string value.
+
+## Syntax
+
+```redis
+GET <key>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Bulk string or Null bulk string or null array |
+| RESP3 | Bulk string or Null |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+type MyType = {
+    a: number;
+    b: string;
+}
+const value = await redis.get<MyType>("key");
+if (!value) {
+    // key doesn't exist
+} else {
+    // value is of type MyType
+}
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.get("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.get("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.get("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.get("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.Get(context.Background(), "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.get("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.get("my-key")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# GETDEL
+Source: https://upstash.com/docs/redis/commands/string/getdel
+
+Use `GETDEL` to get value and delete key.
+
+## Syntax
+
+```redis
+GETDEL <key>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Bulk string or Null bulk string or null array |
+| RESP3 | Bulk string or Null |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+type MyType = {
+    a: number;
+    b: string;
+}
+await redis.getdel<MyType>("key");
+// returns {a: 1, b: "2"}
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.getdel("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.getdel("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.getDel("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.getdel("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.GetDel(context.Background(), "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.getDel("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.get_del("my-key")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# GETEX
+Source: https://upstash.com/docs/redis/commands/string/getex
+
+Use `GETEX` to get value and set expiration.
+
+## Syntax
+
+```redis
+GETEX <key> [EX <seconds> | PX <milliseconds> | EXAT <unix-time-seconds> | PXAT <unix-time-milliseconds> | PERSIST]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `(EX <seconds> \| PX <milliseconds> \| EXAT <unix-time-seconds> \| PXAT <unix-time-milliseconds> \| PERSIST)` | No | No | Choose one form: `EX` (set a lifetime in seconds); `PX` (set a lifetime in milliseconds); `EXAT` (expire at a Unix timestamp in seconds); `PXAT` (expire at a Unix timestamp in milliseconds); `PERSIST`. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Bulk string or Null bulk string or null array |
+| RESP3 | Bulk string or Null |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+const result = await redis.getex("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.getex("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.getex("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.getEx("my-key", { type: "PX", value: 1000 });
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.getex("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.GetEx(context.Background(), "my-key", 0).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+import redis.clients.jedis.Jedis;
+import redis.clients.jedis.params.GetExParams;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.getEx("my-key", GetExParams.getExParams());
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.get_ex("my-key", redis::Expiry::PERSIST)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# GETRANGE
+Source: https://upstash.com/docs/redis/commands/string/getrange
+
+Use `GETRANGE` to get substring of string.
+
+## Syntax
+
+```redis
+GETRANGE <key> <start> <end>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<start>` | Yes | No | Start byte offset; negative values count from the end. |
+| `<end>` | Yes | No | End byte offset, inclusive; negative values count from the end. |
+
+## Important points
+
+* `SUBSTR` is accepted as a deprecated alias with the same arguments and reply. New code should use `GETRANGE`.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Bulk string |
+| RESP3 | Bulk string |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const substring = await redis.getrange("key", 2, 4);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.getrange("my-key", "0", "1")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.getrange("my-key", "0", "1");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.getRange("my-key", 0, 1);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.getrange("my-key", "0", "1")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.GetRange(context.Background(), "my-key", 0, 1).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.getrange("my-key", 0, 1);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.getrange("my-key", 0, 1)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# GETSET
+Source: https://upstash.com/docs/redis/commands/string/getset
+
+Use `GETSET` to set value and return old value.
+
+## Syntax
+
+```redis
+GETSET <key> <value>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<value>` | Yes | No | String value to store in place of the current one. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Bulk string or Null bulk string or null array |
+| RESP3 | Bulk string or Null |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const oldValue = await redis.getset("key", newValue);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.getset("my-key", "value")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.getset("my-key", "value");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.getSet("my-key", "value");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.getset("my-key", "value")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.GetSet(context.Background(), "my-key", "value").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.getSet("my-key", "value");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.getset("my-key", "value")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# INCR
+Source: https://upstash.com/docs/redis/commands/string/incr
+
+Use `INCR` to increment integer value by 1.
+
+## Syntax
+
+```redis
+INCR <key>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.set("key", 6);
+await redis.incr("key");
+// returns 7
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.incr("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.incr("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.incr("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.incr("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.Incr(context.Background(), "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.incr("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.incr("my-key", 1)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# INCRBY
+Source: https://upstash.com/docs/redis/commands/string/incrby
+
+Use `INCRBY` to increment integer by amount.
+
+## Syntax
+
+```redis
+INCRBY <key> <increment>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<increment>` | Yes | No | Integer amount to add to the value. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.set("key", 6);
+await redis.incrby("key", 4);
+// returns 10
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.incrby("my-key", 1)
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.incrby("my-key", "1");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.incrBy("my-key", 1);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.incrby("my-key", 1)
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.IncrBy(context.Background(), "my-key", 1).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.incrBy("my-key", 1);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.incr("my-key", 1)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# INCRBYFLOAT
+Source: https://upstash.com/docs/redis/commands/string/incrbyfloat
+
+Use `INCRBYFLOAT` to increment float by amount.
+
+## Syntax
+
+```redis
+INCRBYFLOAT <key> <increment>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<increment>` | Yes | No | Amount to add to the value; may be a floating-point number. |
+
+## Important points
+
+* The value is always returned as a bulk string, in both RESP2 and RESP3. Client libraries commonly decode it to a language number.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Bulk string |
+| RESP3 | Bulk string |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.set("key", 6);
+await redis.incrbyfloat("key", 4,5);
+// returns 10.5
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.incrbyfloat("my-key", 1.5)
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.incrbyfloat("my-key", "1.5");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.incrByFloat("my-key", 1.5);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.incrbyfloat("my-key", 1.5)
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.IncrByFloat(context.Background(), "my-key", 1.5).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.incrByFloat("my-key", 1.5);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.incr("my-key", 1.5)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# MGET
+Source: https://upstash.com/docs/redis/commands/string/mget
+
+Use `MGET` to get values of multiple keys.
+
+## Syntax
+
+```redis
+MGET <key> [<key> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | Yes | Redis key targeted by the command. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of bulk-string values or null values, one per key |
+| RESP3 | Array of bulk-string values or null values, one per key |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+type MyType = {
+    a: number;
+    b: string;
+}
+const values = await redis.mget<MyType>("key1", "key2", "key3");
+// values.length -> 3
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.mget("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.mget("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.mGet(["my-key"]);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.mget("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.MGet(context.Background(), "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.mget("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.mget(&["my-key"])?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# MSET
+Source: https://upstash.com/docs/redis/commands/string/mset
+
+Use `MSET` to set multiple keys at once.
+
+## Syntax
+
+```redis
+MSET <key> <value> [<key> <value> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key> <value>` | Yes | Yes | Key and the value to store in it. Repeat to set several keys in one call. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Simple string `OK` |
+| RESP3 | Simple string `OK` |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.mset({
+    key1: 1,
+    key2: "hello",
+    key3: { a: 1, b: "hello" },
+});
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.mset({"my-key": "value"})
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.mset("my-key", "value");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.mSet({ "my-key": "value" });
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.mset({"my-key": "value"})
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.MSet(context.Background(), "my-key", "value").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.mset("my-key", "value");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.mset(&[("my-key", "value")])?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# MSETNX
+Source: https://upstash.com/docs/redis/commands/string/msetnx
+
+Use `MSETNX` to set multiple keys if none exist.
+
+## Syntax
+
+```redis
+MSETNX <key> <value> [<key> <value> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key> <value>` | Yes | Yes | Key and the value to store in it. Repeat to set several keys in one call. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer: `1` if all keys were set, `0` if no key was set |
+| RESP3 | Integer: `1` if all keys were set, `0` if no key was set |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+redis.msetnx({
+  "key1": "value1",
+  "key2": "value2"
+})
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.msetnx({"my-key": "value"})
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.msetnx("my-key", "value");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.mSetNX({ "my-key": "value" });
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.msetnx({"my-key": "value"})
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.MSetNX(context.Background(), "my-key", "value").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.msetnx("my-key", "value");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.mset_nx(&[("my-key", "value")])?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# String commands
+Source: https://upstash.com/docs/redis/commands/string/overview
+
+<CardGroup cols={2}>
+<Card title="APPEND" href="/redis/commands/string/append">Append value to a string</Card>
+<Card title="DECR" href="/redis/commands/string/decr">Decrement integer value by 1</Card>
+<Card title="DECRBY" href="/redis/commands/string/decrby">Decrement integer by amount</Card>
+<Card title="DELEX" href="/redis/commands/string/delex">Delete a string when a condition matches</Card>
+<Card title="DIGEST" href="/redis/commands/string/digest">Get the digest of a string value</Card>
+<Card title="GET" href="/redis/commands/string/get">Get string value</Card>
+<Card title="GETDEL" href="/redis/commands/string/getdel">Get value and delete key</Card>
+<Card title="GETEX" href="/redis/commands/string/getex">Get value and set expiration</Card>
+<Card title="GETRANGE" href="/redis/commands/string/getrange">Get substring of string</Card>
+<Card title="GETSET" href="/redis/commands/string/getset">Set value and return old value</Card>
+<Card title="INCR" href="/redis/commands/string/incr">Increment integer value by 1</Card>
+<Card title="INCRBY" href="/redis/commands/string/incrby">Increment integer by amount</Card>
+<Card title="INCRBYFLOAT" href="/redis/commands/string/incrbyfloat">Increment float by amount</Card>
+<Card title="MGET" href="/redis/commands/string/mget">Get values of multiple keys</Card>
+<Card title="MSET" href="/redis/commands/string/mset">Set multiple keys at once</Card>
+<Card title="MSETNX" href="/redis/commands/string/msetnx">Set multiple keys if none exist</Card>
+<Card title="PSETEX" href="/redis/commands/string/psetex">Set value with ms expiration</Card>
+<Card title="SET" href="/redis/commands/string/set">Set string value</Card>
+<Card title="SETEX" href="/redis/commands/string/setex">Set value with expiration</Card>
+<Card title="SETNX" href="/redis/commands/string/setnx">Set value if key doesn't exist</Card>
+<Card title="SETRANGE" href="/redis/commands/string/setrange">Overwrite part of string</Card>
+<Card title="STRLEN" href="/redis/commands/string/strlen">Get string length</Card>
+</CardGroup>
+
+# PSETEX
+Source: https://upstash.com/docs/redis/commands/string/psetex
+
+Use `PSETEX` to set value with ms expiration.
+
+## Syntax
+
+```redis
+PSETEX <key> <milliseconds> <value>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<milliseconds>` | Yes | No | Lifetime in milliseconds. |
+| `<value>` | Yes | No | String value to store. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Simple string `OK` |
+| RESP3 | Simple string `OK` |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+const result = await redis.psetex("my-key", 1000, "value");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.psetex("my-key", 1000, "value")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.psetex("my-key", "1000", "value");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.pSetEx("my-key", 1000, "value");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.psetex("my-key", 1000, "value")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+    "time"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.Set(context.Background(), "my-key", "value", time.Second).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.psetex("my-key", 1000, "value");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.pset_ex("my-key", "value", 1000)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# SET
+Source: https://upstash.com/docs/redis/commands/string/set
+
+Use `SET` to set string value.
+
+## Syntax
+
+```redis
+SET <key> <value> [NX | XX | IFEQ <ifeq-value> | IFNE <ifne-value> | IFDEQ <ifdeq-digest> | IFDNE <ifdne-digest>] [GET] [EX <seconds> | PX <milliseconds> | EXAT <unix-time-seconds> | PXAT <unix-time-milliseconds> | KEEPTTL]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<value>` | Yes | No | String value to store. |
+| `(NX \| XX \| IFEQ <ifeq-value> \| IFNE <ifne-value> \| IFDEQ <ifdeq-digest> \| IFDNE <ifdne-digest>)` | No | No | Choose one form: `NX` (only when the key does not exist); `XX` (only when it already exists); `IFEQ` (only when the current value equals `<ifeq-value>`); `IFNE` (only when it differs); `IFDEQ` (only when the current value's digest equals `<ifdeq-digest>`); `IFDNE` (only when it differs). |
+| `GET` | No | No | Also return the previous value. |
+| `(EX <seconds> \| PX <milliseconds> \| EXAT <unix-time-seconds> \| PXAT <unix-time-milliseconds> \| KEEPTTL)` | No | No | Choose one form: `EX` (set a lifetime in seconds); `PX` (set a lifetime in milliseconds); `EXAT` (expire at a Unix timestamp in seconds); `PXAT` (expire at a Unix timestamp in milliseconds); `KEEPTTL` (preserve the existing key lifetime). |
+
+## Important points
+
+* `NX` and `XX` are mutually exclusive.
+* Choose at most one expiration form and at most one condition. `GET` changes a successful reply from `OK` to the previous value.
+* `IFEQ`/`IFNE` compare the current value; `IFDEQ`/`IFDNE` compare its digest. These conditional forms are implemented by this Upstash deployment.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Simple string `OK`; with `GET`, the previous value as a bulk string, or Null bulk string or null array when the key did not exist or a condition failed |
+| RESP3 | Simple string `OK`; with `GET`, the previous value as a bulk string, or Null when the key did not exist or a condition failed |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.set("my-key", {my: "value"});
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.set("my-key", "value")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.set("my-key", "value");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.set("my-key", "value");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.set("my-key", "value")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.Set(context.Background(), "my-key", "value", 0).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.set("my-key", "value");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.set("my-key", "value")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# SETEX
+Source: https://upstash.com/docs/redis/commands/string/setex
+
+Use `SETEX` to set value with expiration.
+
+## Syntax
+
+```redis
+SETEX <key> <seconds> <value>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<seconds>` | Yes | No | Lifetime in seconds. |
+| `<value>` | Yes | No | String value to store. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Simple string `OK` |
+| RESP3 | Simple string `OK` |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+const result = await redis.setex("my-key", 1000, "value");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.setex("my-key", 1000, "value")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.setex("my-key", "1000", "value");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.setEx("my-key", 1000, "value");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.setex("my-key", 1000, "value")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+    "time"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.SetEx(context.Background(), "my-key", "value", 1000*time.Second).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.setex("my-key", 1000, "value");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.set_ex("my-key", "value", 1000)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# SETNX
+Source: https://upstash.com/docs/redis/commands/string/setnx
+
+Use `SETNX` to set value if key doesn't exist.
+
+## Syntax
+
+```redis
+SETNX <key> <value>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<value>` | Yes | No | String value to store. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer: `1` if the key was set, `0` if it already exists |
+| RESP3 | Integer: `1` if the key was set, `0` if it already exists |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+const result = await redis.setnx("my-key", "value");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.setnx("my-key", "value")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.setnx("my-key", "value");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.setNX("my-key", "value");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.setnx("my-key", "value")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.SetNX(context.Background(), "my-key", "value", 0).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.setnx("my-key", "value");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.set_nx("my-key", "value")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# SETRANGE
+Source: https://upstash.com/docs/redis/commands/string/setrange
+
+Use `SETRANGE` to overwrite part of string.
+
+## Syntax
+
+```redis
+SETRANGE <key> <offset> <value>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<offset>` | Yes | No | Zero-based byte offset to write at. The value is zero-padded if the key is shorter. |
+| `<value>` | Yes | No | String written starting at the offset. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.set("key", "helloworld")
+const length = await redis.setrange("key", 5, "redis");
+console.log(length); // 10
+
+// The value of "key" is now "helloredis"
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.setrange("my-key", 0, "value")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.setrange("my-key", "0", "value");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.setRange("my-key", 0, "value");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.setrange("my-key", 0, "value")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.SetRange(context.Background(), "my-key", 0, "value").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.setrange("my-key", 0, "value");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.setrange("my-key", 0, "value")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# STRLEN
+Source: https://upstash.com/docs/redis/commands/string/strlen
+
+Use `STRLEN` to get string length.
+
+## Syntax
+
+```redis
+STRLEN <key>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.set("key", "helloworld")
+const length = await redis.strlen("key");
+console.log(length); // 10
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.strlen("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.strlen("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.strLen("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.strlen("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.StrLen(context.Background(), "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.strlen("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.strlen("my-key")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# DISCARD
+Source: https://upstash.com/docs/redis/commands/transactions/discard
+
+Use `DISCARD` to discard queued commands.
+
+## Syntax
+
+```redis
+DISCARD
+```
+
+## Arguments
+
+This command takes no arguments.
+
+## Important points
+
+* The raw command is TCP-only. For HTTP, use an Upstash SDK transaction API rather than sending this command directly.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Simple string `OK` |
+| RESP3 | Simple string `OK` |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const client = new Redis(process.env.REDIS_URL!);
+await client.multi({ pipeline: false });
+await client.set("balance", "100");
+await client.discard();
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL }).connect();
+await client.sendCommand(["MULTI"]);
+await client.sendCommand(["SET", "balance", "100"]);
+await client.sendCommand(["DISCARD"]);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+with client.pipeline(transaction=True) as pipe:
+    pipe.set("balance", "100")
+    pipe.reset()
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+ctx := context.Background()
+opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+if err != nil { panic(err) }
+client := redis.NewClient(opts)
+
+pipe := client.TxPipeline()
+pipe.Set(ctx, "balance", "100", 0)
+pipe.Discard()
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+import redis.clients.jedis.Jedis;
+import redis.clients.jedis.Transaction;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")));
+     Transaction transaction = jedis.multi()) {
+  transaction.set("balance", "100");
+  transaction.discard();
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let mut transaction = redis::pipe();
+    transaction.atomic().set("balance", "100");
+    transaction.clear();
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# EXEC
+Source: https://upstash.com/docs/redis/commands/transactions/exec
+
+Use `EXEC` to execute queued commands.
+
+## Syntax
+
+```redis
+EXEC
+```
+
+## Arguments
+
+This command takes no arguments.
+
+## Important points
+
+* The raw command is TCP-only. For HTTP, use an Upstash SDK transaction API rather than sending this command directly.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of command replies or Null bulk string or null array |
+| RESP3 | Array of command replies or Null |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const client = new Redis(process.env.REDIS_URL!);
+const result = await client.multi().set("balance", "100").exec();
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL }).connect();
+const result = await client.multi().set("balance", "100").exec();
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+with client.pipeline(transaction=True) as pipe:
+    result = pipe.set("balance", "100").execute()
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+ctx := context.Background()
+opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+if err != nil { panic(err) }
+client := redis.NewClient(opts)
+
+pipe := client.TxPipeline()
+pipe.Set(ctx, "balance", "100", 0)
+result, err := pipe.Exec(ctx)
+if err != nil { panic(err) }
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+import redis.clients.jedis.Jedis;
+import redis.clients.jedis.Transaction;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")));
+     Transaction transaction = jedis.multi()) {
+  transaction.set("balance", "100");
+  Object result = transaction.exec();
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    redis::pipe()
+        .atomic()
+        .set("balance", "100")
+        .ignore()
+        .query::<()>(&mut connection)?;
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# MULTI
+Source: https://upstash.com/docs/redis/commands/transactions/multi
+
+Use `MULTI` to start a transaction.
+
+## Syntax
+
+```redis
+MULTI
+```
+
+## Arguments
+
+This command takes no arguments.
+
+## Important points
+
+* The raw command is TCP-only. For HTTP, use an Upstash SDK transaction API rather than sending this command directly.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Simple string `OK` |
+| RESP3 | Simple string `OK` |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const client = new Redis(process.env.REDIS_URL!);
+const result = await client.multi().set("balance", "100").exec();
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL }).connect();
+const result = await client.multi().set("balance", "100").exec();
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+with client.pipeline(transaction=True) as pipe:
+    result = pipe.set("balance", "100").execute()
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+ctx := context.Background()
+opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+if err != nil { panic(err) }
+client := redis.NewClient(opts)
+
+pipe := client.TxPipeline()
+pipe.Set(ctx, "balance", "100", 0)
+result, err := pipe.Exec(ctx)
+if err != nil { panic(err) }
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+import redis.clients.jedis.Jedis;
+import redis.clients.jedis.Transaction;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")));
+     Transaction transaction = jedis.multi()) {
+  transaction.set("balance", "100");
+  Object result = transaction.exec();
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    redis::pipe()
+        .atomic()
+        .set("balance", "100")
+        .ignore()
+        .query::<()>(&mut connection)?;
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# Transactions commands
+Source: https://upstash.com/docs/redis/commands/transactions/overview
+
+<CardGroup cols={2}>
+<Card title="DISCARD" href="/redis/commands/transactions/discard">Discard queued commands</Card>
+<Card title="EXEC" href="/redis/commands/transactions/exec">Execute queued commands</Card>
+<Card title="MULTI" href="/redis/commands/transactions/multi">Start a transaction</Card>
+<Card title="UNWATCH" href="/redis/commands/transactions/unwatch">Unwatch all keys</Card>
+<Card title="WATCH" href="/redis/commands/transactions/watch">Watch keys for changes</Card>
+</CardGroup>
+
+# UNWATCH
+Source: https://upstash.com/docs/redis/commands/transactions/unwatch
+
+Use `UNWATCH` to unwatch all keys.
+
+## Syntax
+
+```redis
+UNWATCH
+```
+
+## Arguments
+
+This command takes no arguments.
+
+## Important points
+
+* The raw command is TCP-only. For HTTP, use an Upstash SDK transaction API rather than sending this command directly.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Simple string `OK` |
+| RESP3 | Simple string `OK` |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const client = new Redis(process.env.REDIS_URL!);
+await client.watch("balance");
+await client.unwatch();
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL }).connect();
+await client.watch("balance");
+await client.unwatch();
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+with client.pipeline() as pipe:
+    pipe.watch("balance")
+    pipe.unwatch()
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+ctx := context.Background()
+opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+if err != nil { panic(err) }
+client := redis.NewClient(opts)
+
+err = client.Watch(ctx, func(tx *redis.Tx) error {
+    return tx.Unwatch(ctx).Err()
+}, "balance")
+if err != nil { panic(err) }
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  jedis.watch("balance");
+  jedis.unwatch();
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    redis::transaction(&mut connection, &["balance"], |_con, _pipe| {
+        Ok(Some(()))
+    })?;
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
+# WATCH
+Source: https://upstash.com/docs/redis/commands/transactions/watch
+
+Use `WATCH` to watch keys for changes.
+
+## Syntax
+
+```redis
+WATCH <key> [<key> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | Yes | Redis key targeted by the command. |
+
+## Important points
+
+* The raw command is TCP-only. For HTTP, use an Upstash SDK transaction API rather than sending this command directly.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Simple string `OK` |
+| RESP3 | Simple string `OK` |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const client = new Redis(process.env.REDIS_URL!);
+await client.watch("balance");
+const result = await client.multi().set("balance", "100").exec();
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL }).connect();
+await client.watch("balance");
+const result = await client.multi().set("balance", "100").exec();
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+with client.pipeline() as pipe:
+    pipe.watch("balance")
+    pipe.multi()
+    pipe.set("balance", "100")
+    result = pipe.execute()
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+ctx := context.Background()
+opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+if err != nil { panic(err) }
+client := redis.NewClient(opts)
+
+err = client.Watch(ctx, func(tx *redis.Tx) error {
+    _, err := tx.TxPipelined(ctx, func(pipe redis.Pipeliner) error {
+        pipe.Set(ctx, "balance", "100", 0)
+        return nil
+    })
+    return err
+}, "balance")
+if err != nil { panic(err) }
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+import redis.clients.jedis.Jedis;
+import redis.clients.jedis.Transaction;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  jedis.watch("balance");
+  try (Transaction transaction = jedis.multi()) {
+    transaction.set("balance", "100");
+    Object result = transaction.exec();
+  }
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let _: () = redis::transaction(&mut connection, &["balance"], |con, pipe| {
+        pipe.set("balance", "100").ignore().query::<Option<()>>(con)
+    })?;
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
+
 # Auto Upgrade
 Source: https://upstash.com/docs/redis/features/auto-upgrade
 
@@ -21271,14 +66336,14 @@ Added [Upstash Redis Search](/docs/redis/search/introduction) feature, a new ext
 Redis Search is available through the [@upstash/redis](/docs/redis/sdks/ts/overview) and [upstash-redis](/docs/redis/sdks/py/overview) SDKs. If you already use `node-redis` or `ioredis`, you can use the [`@upstash/search-redis`](/docs/redis/search/adapters/node-redis) and [`@upstash/search-ioredis`](/docs/redis/search/adapters/ioredis) wrappers without switching clients.
 
 New Redis Search commands:
-* [`SEARCH.CREATE`](/docs/redis/search/command-reference#searchcreate): Create a search index
-* [`SEARCH.DROP`](/docs/redis/search/command-reference#searchdrop): Remove a search index
-* [`SEARCH.DESCRIBE`](/docs/redis/search/command-reference#searchdescribe): Return metadata about a search index
-* [`SEARCH.WAITINDEXING`](/docs/redis/search/command-reference#searchwaitindexing): Wait until pending index updates are visible to queries
-* [`SEARCH.QUERY`](/docs/redis/search/command-reference#searchquery): Search documents with a JSON filter
-* [`SEARCH.COUNT`](/docs/redis/search/command-reference#searchcount): Count matching documents without returning them
-* [`SEARCH.AGGREGATE`](/docs/redis/search/command-reference#searchaggregate): Compute analytics over matching documents
-* [`SEARCH.ALIASADD`](/docs/redis/search/command-reference#searchaliasadd), [`SEARCH.ALIASDEL`](/docs/redis/search/command-reference#searchaliasdel), and [`SEARCH.LISTALIASES`](/docs/redis/search/command-reference#searchlistaliases): Manage search index aliases
+* [`SEARCH.CREATE`](/docs/redis/commands/search/search-create): Create a search index
+* [`SEARCH.DROP`](/docs/redis/commands/search/search-drop): Remove a search index
+* [`SEARCH.DESCRIBE`](/docs/redis/commands/search/search-describe): Return metadata about a search index
+* [`SEARCH.WAITINDEXING`](/docs/redis/commands/search/search-waitindexing): Wait until pending index updates are visible to queries
+* [`SEARCH.QUERY`](/docs/redis/commands/search/search-query): Search documents with a JSON filter
+* [`SEARCH.COUNT`](/docs/redis/commands/search/search-count): Count matching documents without returning them
+* [`SEARCH.AGGREGATE`](/docs/redis/commands/search/search-aggregate): Compute analytics over matching documents
+* [`SEARCH.ALIASADD`](/docs/redis/commands/search/search-aliasadd), [`SEARCH.ALIASDEL`](/docs/redis/commands/search/search-aliasdel), and [`SEARCH.LISTALIASES`](/docs/redis/commands/search/search-listaliases): Manage search index aliases
 </Update>
 
 <Update label="December 2025">
@@ -21508,366 +66573,14 @@ Source: https://upstash.com/docs/redis/overall/compatibility
 
 Upstash supports Redis client protocol up to version `8.2`. We are also gradually adding changes introduced in later versions.
 
-This page lists Redis command support at the Upstash Redis API level. SDK command references may cover a smaller set of typed helpers.
-For example, see the [TypeScript SDK command reference](/docs/redis/sdks/ts/commands/overview) for the commands documented in `@upstash/redis`.
-
-Most of the unsupported items are in our roadmap. If you need a feature that we do not support, please drop a note to [support@upstash.com](mailto:support@upstash.com).
-So we can inform you when we are planning to support it.
-
-***
-
-## Supported Commands
-
-<AccordionGroup>
-
-<Accordion title="Bitmap" icon="grid">
-<CardGroup cols={2}>
-<Card title="BITCOUNT" href="https://redis.io/docs/latest/commands/bitcount/">Count set bits in a string</Card>
-<Card title="BITFIELD" href="https://redis.io/docs/latest/commands/bitfield/">Perform arbitrary bitfield operations</Card>
-<Card title="BITFIELD_RO" href="https://redis.io/docs/latest/commands/bitfield_ro/">Read-only bitfield operations</Card>
-<Card title="BITOP" href="https://redis.io/docs/latest/commands/bitop/">Perform bitwise operations between strings</Card>
-<Card title="BITPOS" href="https://redis.io/docs/latest/commands/bitpos/">Find first bit set or clear in a string</Card>
-<Card title="GETBIT" href="https://redis.io/docs/latest/commands/getbit/">Get the bit value at offset</Card>
-<Card title="SETBIT" href="https://redis.io/docs/latest/commands/setbit/">Set or clear the bit at offset</Card>
-</CardGroup>
-</Accordion>
-
-<Accordion title="Connection" icon="plug">
-<CardGroup cols={2}>
-<Card title="AUTH" href="https://redis.io/docs/latest/commands/auth/">Authenticate to the server</Card>
-<Card title="CLIENT GETNAME" href="https://redis.io/docs/latest/commands/client-getname/">Get the current connection name</Card>
-<Card title="CLIENT ID" href="https://redis.io/docs/latest/commands/client-id/">Get the current client ID</Card>
-<Card title="CLIENT INFO" href="https://redis.io/docs/latest/commands/client-info/">Get info about current connection</Card>
-<Card title="CLIENT LIST" href="https://redis.io/docs/latest/commands/client-list/">List all client connections</Card>
-<Card title="CLIENT SETINFO" href="https://redis.io/docs/latest/commands/client-setinfo/">Set client connection attributes</Card>
-<Card title="CLIENT SETNAME" href="https://redis.io/docs/latest/commands/client-setname/">Set the connection name</Card>
-<Card title="ECHO" href="https://redis.io/docs/latest/commands/echo/">Echo the given string</Card>
-<Card title="HELLO" href="https://redis.io/docs/latest/commands/hello/">Handshake with Redis protocol</Card>
-<Card title="PING" href="https://redis.io/docs/latest/commands/ping/">Ping the server</Card>
-<Card title="QUIT" href="https://redis.io/docs/latest/commands/quit/">Close the connection</Card>
-<Card title="RESET" href="https://redis.io/docs/latest/commands/reset/">Reset the connection</Card>
-<Card title="SELECT" href="https://redis.io/docs/latest/commands/select/">Select the database by index</Card>
-</CardGroup>
-</Accordion>
-
-<Accordion title="Functions" icon="code">
-<CardGroup cols={2}>
-<Card title="FCALL" href="https://redis.io/docs/latest/commands/fcall/">Call a function</Card>
-<Card title="FCALL_RO" href="https://redis.io/docs/latest/commands/fcall_ro/">Call a read-only function</Card>
-<Card title="FUNCTION DELETE" href="https://redis.io/docs/latest/commands/function-delete/">Delete a library</Card>
-<Card title="FUNCTION FLUSH" href="https://redis.io/docs/latest/commands/function-flush/">Delete all libraries</Card>
-<Card title="FUNCTION KILL" href="https://redis.io/docs/latest/commands/function-kill/">Kill a running function</Card>
-<Card title="FUNCTION LIST" href="https://redis.io/docs/latest/commands/function-list/">List all libraries</Card>
-<Card title="FUNCTION LOAD" href="https://redis.io/docs/latest/commands/function-load/">Load a library</Card>
-<Card title="FUNCTION STATS" href="https://redis.io/docs/latest/commands/function-stats/">Get function execution stats</Card>
-</CardGroup>
-</Accordion>
-
-<Accordion title="Generic" icon="sliders">
-<CardGroup cols={2}>
-<Card title="COPY" href="https://redis.io/docs/latest/commands/copy/">Copy a key to another key</Card>
-<Card title="DEL" href="https://redis.io/docs/latest/commands/del/">Delete one or more keys</Card>
-<Card title="DUMP" href="https://redis.io/docs/latest/commands/dump/">Serialize a key's value</Card>
-<Card title="EXISTS" href="https://redis.io/docs/latest/commands/exists/">Check if keys exist</Card>
-<Card title="EXPIRE" href="https://redis.io/docs/latest/commands/expire/">Set a key's TTL in seconds</Card>
-<Card title="EXPIREAT" href="https://redis.io/docs/latest/commands/expireat/">Set expiry as Unix timestamp</Card>
-<Card title="EXPIRETIME" href="https://redis.io/docs/latest/commands/expiretime/">Get expiry as Unix timestamp</Card>
-<Card title="KEYS" href="https://redis.io/docs/latest/commands/keys/">Find keys matching a pattern</Card>
-<Card title="PERSIST" href="https://redis.io/docs/latest/commands/persist/">Remove the expiration from a key</Card>
-<Card title="PEXPIRE" href="https://redis.io/docs/latest/commands/pexpire/">Set a key's TTL in milliseconds</Card>
-<Card title="PEXPIREAT" href="https://redis.io/docs/latest/commands/pexpireat/">Set expiry as Unix ms timestamp</Card>
-<Card title="PEXPIRETIME" href="https://redis.io/docs/latest/commands/pexpiretime/">Get expiry as Unix ms timestamp</Card>
-<Card title="PTTL" href="https://redis.io/docs/latest/commands/pttl/">Get TTL in milliseconds</Card>
-<Card title="RANDOMKEY" href="https://redis.io/docs/latest/commands/randomkey/">Return a random key</Card>
-<Card title="RENAME" href="https://redis.io/docs/latest/commands/rename/">Rename a key</Card>
-<Card title="RENAMENX" href="https://redis.io/docs/latest/commands/renamenx/">Rename a key if new key doesn't exist</Card>
-<Card title="RESTORE" href="https://redis.io/docs/latest/commands/restore/">Deserialize and restore a key</Card>
-<Card title="SCAN" href="https://redis.io/docs/latest/commands/scan/">Incrementally iterate keys</Card>
-<Card title="TOUCH" href="https://redis.io/docs/latest/commands/touch/">Update last access time of keys</Card>
-<Card title="TTL" href="https://redis.io/docs/latest/commands/ttl/">Get TTL in seconds</Card>
-<Card title="TYPE" href="https://redis.io/docs/latest/commands/type/">Get the type of a key</Card>
-<Card title="UNLINK" href="https://redis.io/docs/latest/commands/unlink/">Delete keys asynchronously</Card>
-</CardGroup>
-</Accordion>
-
-<Accordion title="Geo" icon="location-dot">
-<CardGroup cols={2}>
-<Card title="GEOADD" href="https://redis.io/docs/latest/commands/geoadd/">Add geospatial items</Card>
-<Card title="GEODIST" href="https://redis.io/docs/latest/commands/geodist/">Get distance between two members</Card>
-<Card title="GEOHASH" href="https://redis.io/docs/latest/commands/geohash/">Get geohash strings for members</Card>
-<Card title="GEOPOS" href="https://redis.io/docs/latest/commands/geopos/">Get coordinates of members</Card>
-<Card title="GEORADIUS" href="https://redis.io/docs/latest/commands/georadius/">Query members within radius</Card>
-<Card title="GEORADIUS_RO" href="https://redis.io/docs/latest/commands/georadius_ro/">Read-only radius query</Card>
-<Card title="GEORADIUSBYMEMBER" href="https://redis.io/docs/latest/commands/georadiusbymember/">Radius query centered on member</Card>
-<Card title="GEORADIUSBYMEMBER_RO" href="https://redis.io/docs/latest/commands/georadiusbymember_ro/">Read-only radius query by member</Card>
-<Card title="GEOSEARCH" href="https://redis.io/docs/latest/commands/geosearch/">Search for members in an area</Card>
-<Card title="GEOSEARCHSTORE" href="https://redis.io/docs/latest/commands/geosearchstore/">Store geosearch results</Card>
-</CardGroup>
-</Accordion>
-
-<Accordion title="Hash" icon="hashtag">
-<CardGroup cols={2}>
-<Card title="HDEL" href="https://redis.io/docs/latest/commands/hdel/">Delete one or more hash fields</Card>
-<Card title="HEXISTS" href="https://redis.io/docs/latest/commands/hexists/">Check if a hash field exists</Card>
-<Card title="HEXPIRE" href="https://redis.io/docs/latest/commands/hexpire/">Set field TTL in seconds</Card>
-<Card title="HEXPIREAT" href="https://redis.io/docs/latest/commands/hexpireat/">Set field expiry as timestamp</Card>
-<Card title="HEXPIRETIME" href="https://redis.io/docs/latest/commands/hexpiretime/">Get field expiry as timestamp</Card>
-<Card title="HGET" href="https://redis.io/docs/latest/commands/hget/">Get the value of a hash field</Card>
-<Card title="HGETALL" href="https://redis.io/docs/latest/commands/hgetall/">Get all fields and values</Card>
-<Card title="HGETDEL" href="https://redis.io/docs/latest/commands/hgetdel/">Get and delete hash fields</Card>
-<Card title="HGETEX" href="https://redis.io/docs/latest/commands/hgetex/">Get fields and set their expiry</Card>
-<Card title="HINCRBY" href="https://redis.io/docs/latest/commands/hincrby/">Increment integer value of a field</Card>
-<Card title="HINCRBYFLOAT" href="https://redis.io/docs/latest/commands/hincrbyfloat/">Increment float value of a field</Card>
-<Card title="HKEYS" href="https://redis.io/docs/latest/commands/hkeys/">Get all fields in a hash</Card>
-<Card title="HLEN" href="https://redis.io/docs/latest/commands/hlen/">Get number of fields in a hash</Card>
-<Card title="HMGET" href="https://redis.io/docs/latest/commands/hmget/">Get values of multiple fields</Card>
-<Card title="HMSET" href="https://redis.io/docs/latest/commands/hmset/">Set multiple hash fields</Card>
-<Card title="HPERSIST" href="https://redis.io/docs/latest/commands/hpersist/">Remove field expiration</Card>
-<Card title="HPEXPIRE" href="https://redis.io/docs/latest/commands/hpexpire/">Set field TTL in milliseconds</Card>
-<Card title="HPEXPIREAT" href="https://redis.io/docs/latest/commands/hpexpireat/">Set field expiry as ms timestamp</Card>
-<Card title="HPEXPIRETIME" href="https://redis.io/docs/latest/commands/hpexpiretime/">Get field expiry as ms timestamp</Card>
-<Card title="HPTTL" href="https://redis.io/docs/latest/commands/hpttl/">Get field TTL in milliseconds</Card>
-<Card title="HRANDFIELD" href="https://redis.io/docs/latest/commands/hrandfield/">Get random fields from a hash</Card>
-<Card title="HSCAN" href="https://redis.io/docs/latest/commands/hscan/">Incrementally iterate hash fields</Card>
-<Card title="HSET" href="https://redis.io/docs/latest/commands/hset/">Set hash field values</Card>
-<Card title="HSETEX" href="https://redis.io/docs/latest/commands/hsetex/">Set fields with expiration</Card>
-<Card title="HSETNX" href="https://redis.io/docs/latest/commands/hsetnx/">Set field only if it doesn't exist</Card>
-<Card title="HSTRLEN" href="https://redis.io/docs/latest/commands/hstrlen/">Get length of a field's value</Card>
-<Card title="HTTL" href="https://redis.io/docs/latest/commands/httl/">Get field TTL in seconds</Card>
-<Card title="HVALS" href="https://redis.io/docs/latest/commands/hvals/">Get all values in a hash</Card>
-</CardGroup>
-</Accordion>
-
-<Accordion title="HyperLogLog" icon="chart-simple">
-<CardGroup cols={2}>
-<Card title="PFADD" href="https://redis.io/docs/latest/commands/pfadd/">Add elements to HyperLogLog</Card>
-<Card title="PFCOUNT" href="https://redis.io/docs/latest/commands/pfcount/">Get estimated cardinality</Card>
-<Card title="PFMERGE" href="https://redis.io/docs/latest/commands/pfmerge/">Merge multiple HyperLogLogs</Card>
-</CardGroup>
-</Accordion>
-
-<Accordion title="JSON" icon="brackets-curly">
-To query inside JSON values (full-text, fuzzy, phrase, regex), see [Upstash Redis Search](/docs/redis/search/introduction).
-
-<CardGroup cols={2}>
-<Card title="JSON.ARRAPPEND" href="https://redis.io/docs/latest/commands/json.arrappend/">Append values to JSON array</Card>
-<Card title="JSON.ARRINDEX" href="https://redis.io/docs/latest/commands/json.arrindex/">Find index of value in array</Card>
-<Card title="JSON.ARRINSERT" href="https://redis.io/docs/latest/commands/json.arrinsert/">Insert values into JSON array</Card>
-<Card title="JSON.ARRLEN" href="https://redis.io/docs/latest/commands/json.arrlen/">Get JSON array length</Card>
-<Card title="JSON.ARRPOP" href="https://redis.io/docs/latest/commands/json.arrpop/">Pop value from JSON array</Card>
-<Card title="JSON.ARRTRIM" href="https://redis.io/docs/latest/commands/json.arrtrim/">Trim JSON array to range</Card>
-<Card title="JSON.CLEAR" href="https://redis.io/docs/latest/commands/json.clear/">Clear JSON values</Card>
-<Card title="JSON.DEL" href="https://redis.io/docs/latest/commands/json.del/">Delete JSON values</Card>
-<Card title="JSON.FORGET" href="https://redis.io/docs/latest/commands/json.forget/">Alias for JSON.DEL</Card>
-<Card title="JSON.GET" href="https://redis.io/docs/latest/commands/json.get/">Get JSON values</Card>
-<Card title="JSON.MERGE" href="https://redis.io/docs/latest/commands/json.merge/">Merge JSON values</Card>
-<Card title="JSON.MGET" href="https://redis.io/docs/latest/commands/json.mget/">Get values from multiple keys</Card>
-<Card title="JSON.MSET" href="https://redis.io/docs/latest/commands/json.mset/">Set values in multiple keys</Card>
-<Card title="JSON.NUMINCRBY" href="https://redis.io/docs/latest/commands/json.numincrby/">Increment JSON number</Card>
-<Card title="JSON.NUMMULTBY" href="https://redis.io/docs/latest/commands/json.nummultby/">Multiply JSON number</Card>
-<Card title="JSON.OBJKEYS" href="https://redis.io/docs/latest/commands/json.objkeys/">Get JSON object keys</Card>
-<Card title="JSON.OBJLEN" href="https://redis.io/docs/latest/commands/json.objlen/">Get JSON object size</Card>
-<Card title="JSON.RESP" href="https://redis.io/docs/latest/commands/json.resp/">Get JSON in RESP format</Card>
-<Card title="JSON.SET" href="https://redis.io/docs/latest/commands/json.set/">Set JSON value</Card>
-<Card title="JSON.STRAPPEND" href="https://redis.io/docs/latest/commands/json.strappend/">Append to JSON string</Card>
-<Card title="JSON.STRLEN" href="https://redis.io/docs/latest/commands/json.strlen/">Get JSON string length</Card>
-<Card title="JSON.TOGGLE" href="https://redis.io/docs/latest/commands/json.toggle/">Toggle JSON boolean</Card>
-<Card title="JSON.TYPE" href="https://redis.io/docs/latest/commands/json.type/">Get JSON value type</Card>
-</CardGroup>
-</Accordion>
-
-<Accordion title="List" icon="list">
-<CardGroup cols={2}>
-<Card title="BLMOVE" href="https://redis.io/docs/latest/commands/blmove/">Blocking list move</Card>
-<Card title="BLMPOP" href="https://redis.io/docs/latest/commands/blmpop/">Blocking pop from multiple lists</Card>
-<Card title="BLPOP" href="https://redis.io/docs/latest/commands/blpop/">Blocking left pop</Card>
-<Card title="BRPOP" href="https://redis.io/docs/latest/commands/brpop/">Blocking right pop</Card>
-<Card title="BRPOPLPUSH" href="https://redis.io/docs/latest/commands/brpoplpush/">Blocking pop and push</Card>
-<Card title="LINDEX" href="https://redis.io/docs/latest/commands/lindex/">Get element by index</Card>
-<Card title="LINSERT" href="https://redis.io/docs/latest/commands/linsert/">Insert before or after pivot</Card>
-<Card title="LLEN" href="https://redis.io/docs/latest/commands/llen/">Get list length</Card>
-<Card title="LMOVE" href="https://redis.io/docs/latest/commands/lmove/">Move element between lists</Card>
-<Card title="LMPOP" href="https://redis.io/docs/latest/commands/lmpop/">Pop from multiple lists</Card>
-<Card title="LPOP" href="https://redis.io/docs/latest/commands/lpop/">Pop from list head</Card>
-<Card title="LPOS" href="https://redis.io/docs/latest/commands/lpos/">Find element position</Card>
-<Card title="LPUSH" href="https://redis.io/docs/latest/commands/lpush/">Push to list head</Card>
-<Card title="LPUSHX" href="https://redis.io/docs/latest/commands/lpushx/">Push to head if list exists</Card>
-<Card title="LRANGE" href="https://redis.io/docs/latest/commands/lrange/">Get range of elements</Card>
-<Card title="LREM" href="https://redis.io/docs/latest/commands/lrem/">Remove elements by value</Card>
-<Card title="LSET" href="https://redis.io/docs/latest/commands/lset/">Set element at index</Card>
-<Card title="LTRIM" href="https://redis.io/docs/latest/commands/ltrim/">Trim list to range</Card>
-<Card title="RPOP" href="https://redis.io/docs/latest/commands/rpop/">Pop from list tail</Card>
-<Card title="RPOPLPUSH" href="https://redis.io/docs/latest/commands/rpoplpush/">Pop from tail and push to head</Card>
-<Card title="RPUSH" href="https://redis.io/docs/latest/commands/rpush/">Push to list tail</Card>
-<Card title="RPUSHX" href="https://redis.io/docs/latest/commands/rpushx/">Push to tail if list exists</Card>
-</CardGroup>
-</Accordion>
-
-<Accordion title="Pub/Sub" icon="tower-broadcast">
-<CardGroup cols={2}>
-<Card title="PSUBSCRIBE" href="https://redis.io/docs/latest/commands/psubscribe/">Subscribe to pattern channels</Card>
-<Card title="PUBLISH" href="https://redis.io/docs/latest/commands/publish/">Publish message to channel</Card>
-<Card title="PUBSUB" href="https://redis.io/docs/latest/commands/pubsub/">Inspect pub/sub state</Card>
-<Card title="PUNSUBSCRIBE" href="https://redis.io/docs/latest/commands/punsubscribe/">Unsubscribe from patterns</Card>
-<Card title="SUBSCRIBE" href="https://redis.io/docs/latest/commands/subscribe/">Subscribe to channels</Card>
-<Card title="UNSUBSCRIBE" href="https://redis.io/docs/latest/commands/unsubscribe/">Unsubscribe from channels</Card>
-</CardGroup>
-</Accordion>
-
-<Accordion title="Scripting" icon="scroll">
-<CardGroup cols={2}>
-<Card title="EVAL" href="https://redis.io/docs/latest/commands/eval/">Execute a Lua script</Card>
-<Card title="EVAL_RO" href="https://redis.io/docs/latest/commands/eval_ro/">Execute read-only Lua script</Card>
-<Card title="EVALSHA" href="https://redis.io/docs/latest/commands/evalsha/">Execute cached Lua script by SHA</Card>
-<Card title="EVALSHA_RO" href="https://redis.io/docs/latest/commands/evalsha_ro/">Read-only execute by SHA</Card>
-<Card title="SCRIPT EXISTS" href="https://redis.io/docs/latest/commands/script-exists/">Check if scripts exist in cache</Card>
-<Card title="SCRIPT FLUSH" href="https://redis.io/docs/latest/commands/script-flush/">Clear the script cache</Card>
-<Card title="SCRIPT LOAD" href="https://redis.io/docs/latest/commands/script-load/">Load script into cache</Card>
-</CardGroup>
-</Accordion>
-
-<Accordion title="Server" icon="server">
-<CardGroup cols={2}>
-<Card title="ACL" href="https://redis.io/docs/latest/commands/acl/">Manage access control list</Card>
-<Card title="DBSIZE" href="https://redis.io/docs/latest/commands/dbsize/">Get number of keys in database</Card>
-<Card title="FLUSHALL" href="https://redis.io/docs/latest/commands/flushall/">Delete all keys in all databases</Card>
-<Card title="FLUSHDB" href="https://redis.io/docs/latest/commands/flushdb/">Delete all keys in current database</Card>
-<Card title="MONITOR" href="https://redis.io/docs/latest/commands/monitor/">Stream all commands received</Card>
-<Card title="TIME" href="https://redis.io/docs/latest/commands/time/">Get current server time</Card>
-</CardGroup>
-</Accordion>
-
-<Accordion title="Set" icon="layer-group">
-<CardGroup cols={2}>
-<Card title="SADD" href="https://redis.io/docs/latest/commands/sadd/">Add members to a set</Card>
-<Card title="SCARD" href="https://redis.io/docs/latest/commands/scard/">Get set cardinality</Card>
-<Card title="SDIFF" href="https://redis.io/docs/latest/commands/sdiff/">Get set difference</Card>
-<Card title="SDIFFSTORE" href="https://redis.io/docs/latest/commands/sdiffstore/">Store set difference</Card>
-<Card title="SINTER" href="https://redis.io/docs/latest/commands/sinter/">Get set intersection</Card>
-<Card title="SINTERCARD" href="https://redis.io/docs/latest/commands/sintercard/">Get intersection cardinality</Card>
-<Card title="SINTERSTORE" href="https://redis.io/docs/latest/commands/sinterstore/">Store set intersection</Card>
-<Card title="SISMEMBER" href="https://redis.io/docs/latest/commands/sismember/">Check if member exists in set</Card>
-<Card title="SMEMBERS" href="https://redis.io/docs/latest/commands/smembers/">Get all set members</Card>
-<Card title="SMISMEMBER" href="https://redis.io/docs/latest/commands/smismember/">Check multiple members</Card>
-<Card title="SMOVE" href="https://redis.io/docs/latest/commands/smove/">Move member between sets</Card>
-<Card title="SPOP" href="https://redis.io/docs/latest/commands/spop/">Remove random members</Card>
-<Card title="SRANDMEMBER" href="https://redis.io/docs/latest/commands/srandmember/">Get random members</Card>
-<Card title="SREM" href="https://redis.io/docs/latest/commands/srem/">Remove members from a set</Card>
-<Card title="SSCAN" href="https://redis.io/docs/latest/commands/sscan/">Incrementally iterate set members</Card>
-<Card title="SUNION" href="https://redis.io/docs/latest/commands/sunion/">Get set union</Card>
-<Card title="SUNIONSTORE" href="https://redis.io/docs/latest/commands/sunionstore/">Store set union</Card>
-</CardGroup>
-</Accordion>
-
-<Accordion title="Sorted Set" icon="arrow-down-1-9">
-<CardGroup cols={2}>
-<Card title="BZMPOP" href="https://redis.io/docs/latest/commands/bzmpop/">Blocking pop from sorted sets</Card>
-<Card title="BZPOPMAX" href="https://redis.io/docs/latest/commands/bzpopmax/">Blocking pop max score member</Card>
-<Card title="BZPOPMIN" href="https://redis.io/docs/latest/commands/bzpopmin/">Blocking pop min score member</Card>
-<Card title="ZADD" href="https://redis.io/docs/latest/commands/zadd/">Add members with scores</Card>
-<Card title="ZCARD" href="https://redis.io/docs/latest/commands/zcard/">Get sorted set cardinality</Card>
-<Card title="ZCOUNT" href="https://redis.io/docs/latest/commands/zcount/">Count members in score range</Card>
-<Card title="ZDIFF" href="https://redis.io/docs/latest/commands/zdiff/">Get sorted set difference</Card>
-<Card title="ZDIFFSTORE" href="https://redis.io/docs/latest/commands/zdiffstore/">Store sorted set difference</Card>
-<Card title="ZINCRBY" href="https://redis.io/docs/latest/commands/zincrby/">Increment member's score</Card>
-<Card title="ZINTER" href="https://redis.io/docs/latest/commands/zinter/">Get sorted set intersection</Card>
-<Card title="ZINTERCARD" href="https://redis.io/docs/latest/commands/zintercard/">Get intersection cardinality</Card>
-<Card title="ZINTERSTORE" href="https://redis.io/docs/latest/commands/zinterstore/">Store sorted set intersection</Card>
-<Card title="ZLEXCOUNT" href="https://redis.io/docs/latest/commands/zlexcount/">Count members in lex range</Card>
-<Card title="ZMPOP" href="https://redis.io/docs/latest/commands/zmpop/">Pop members from sorted sets</Card>
-<Card title="ZMSCORE" href="https://redis.io/docs/latest/commands/zmscore/">Get scores of multiple members</Card>
-<Card title="ZPOPMAX" href="https://redis.io/docs/latest/commands/zpopmax/">Pop members with highest scores</Card>
-<Card title="ZPOPMIN" href="https://redis.io/docs/latest/commands/zpopmin/">Pop members with lowest scores</Card>
-<Card title="ZRANDMEMBER" href="https://redis.io/docs/latest/commands/zrandmember/">Get random members</Card>
-<Card title="ZRANGE" href="https://redis.io/docs/latest/commands/zrange/">Get members by index range</Card>
-<Card title="ZRANGEBYLEX" href="https://redis.io/docs/latest/commands/zrangebylex/">Get members by lex range</Card>
-<Card title="ZRANGEBYSCORE" href="https://redis.io/docs/latest/commands/zrangebyscore/">Get members by score range</Card>
-<Card title="ZRANGESTORE" href="https://redis.io/docs/latest/commands/zrangestore/">Store range result</Card>
-<Card title="ZRANK" href="https://redis.io/docs/latest/commands/zrank/">Get member's rank</Card>
-<Card title="ZREM" href="https://redis.io/docs/latest/commands/zrem/">Remove members</Card>
-<Card title="ZREMRANGEBYLEX" href="https://redis.io/docs/latest/commands/zremrangebylex/">Remove members by lex range</Card>
-<Card title="ZREMRANGEBYRANK" href="https://redis.io/docs/latest/commands/zremrangebyrank/">Remove members by rank range</Card>
-<Card title="ZREMRANGEBYSCORE" href="https://redis.io/docs/latest/commands/zremrangebyscore/">Remove members by score range</Card>
-<Card title="ZREVRANGE" href="https://redis.io/docs/latest/commands/zrevrange/">Get members in reverse order</Card>
-<Card title="ZREVRANGEBYLEX" href="https://redis.io/docs/latest/commands/zrevrangebylex/">Reverse lex range query</Card>
-<Card title="ZREVRANGEBYSCORE" href="https://redis.io/docs/latest/commands/zrevrangebyscore/">Reverse score range query</Card>
-<Card title="ZREVRANK" href="https://redis.io/docs/latest/commands/zrevrank/">Get member's reverse rank</Card>
-<Card title="ZSCAN" href="https://redis.io/docs/latest/commands/zscan/">Incrementally iterate sorted set</Card>
-<Card title="ZSCORE" href="https://redis.io/docs/latest/commands/zscore/">Get member's score</Card>
-<Card title="ZUNION" href="https://redis.io/docs/latest/commands/zunion/">Get sorted set union</Card>
-<Card title="ZUNIONSTORE" href="https://redis.io/docs/latest/commands/zunionstore/">Store sorted set union</Card>
-</CardGroup>
-</Accordion>
-
-<Accordion title="Streams" icon="water">
-<CardGroup cols={2}>
-<Card title="XACK" href="https://redis.io/docs/latest/commands/xack/">Acknowledge stream messages</Card>
-<Card title="XACKDEL" href="https://redis.io/docs/latest/commands/xackdel/">Acknowledge and delete messages</Card>
-<Card title="XADD" href="https://redis.io/docs/latest/commands/xadd/">Add entry to stream</Card>
-<Card title="XAUTOCLAIM" href="https://redis.io/docs/latest/commands/xautoclaim/">Auto-claim idle messages</Card>
-<Card title="XCLAIM" href="https://redis.io/docs/latest/commands/xclaim/">Claim pending messages</Card>
-<Card title="XDEL" href="https://redis.io/docs/latest/commands/xdel/">Delete stream entries</Card>
-<Card title="XDELEX" href="https://redis.io/docs/latest/commands/xdelex/">Delete entries with expiration</Card>
-<Card title="XGROUP" href="https://redis.io/docs/latest/commands/xgroup/">Manage consumer groups</Card>
-<Card title="XINFO CONSUMERS" href="https://redis.io/docs/latest/commands/xinfo-consumers/">List group consumers</Card>
-<Card title="XINFO GROUPS" href="https://redis.io/docs/latest/commands/xinfo-groups/">List stream groups</Card>
-<Card title="XINFO STREAM" href="https://redis.io/docs/latest/commands/xinfo-stream/">Get stream info</Card>
-<Card title="XLEN" href="https://redis.io/docs/latest/commands/xlen/">Get stream length</Card>
-<Card title="XPENDING" href="https://redis.io/docs/latest/commands/xpending/">Get pending messages info</Card>
-<Card title="XRANGE" href="https://redis.io/docs/latest/commands/xrange/">Get range of stream entries</Card>
-<Card title="XREAD" href="https://redis.io/docs/latest/commands/xread/">Read stream entries</Card>
-<Card title="XREADGROUP" href="https://redis.io/docs/latest/commands/xreadgroup/">Read as consumer group</Card>
-<Card title="XREVRANGE" href="https://redis.io/docs/latest/commands/xrevrange/">Get range in reverse order</Card>
-<Card title="XTRIM" href="https://redis.io/docs/latest/commands/xtrim/">Trim stream to max length</Card>
-</CardGroup>
-</Accordion>
-
-<Accordion title="String" icon="font">
-<CardGroup cols={2}>
-<Card title="APPEND" href="https://redis.io/docs/latest/commands/append/">Append value to a string</Card>
-<Card title="DECR" href="https://redis.io/docs/latest/commands/decr/">Decrement integer value by 1</Card>
-<Card title="DECRBY" href="https://redis.io/docs/latest/commands/decrby/">Decrement integer by amount</Card>
-<Card title="GET" href="https://redis.io/docs/latest/commands/get/">Get string value</Card>
-<Card title="GETDEL" href="https://redis.io/docs/latest/commands/getdel/">Get value and delete key</Card>
-<Card title="GETEX" href="https://redis.io/docs/latest/commands/getex/">Get value and set expiration</Card>
-<Card title="GETRANGE" href="https://redis.io/docs/latest/commands/getrange/">Get substring of string</Card>
-<Card title="GETSET" href="https://redis.io/docs/latest/commands/getset/">Set value and return old value</Card>
-<Card title="INCR" href="https://redis.io/docs/latest/commands/incr/">Increment integer value by 1</Card>
-<Card title="INCRBY" href="https://redis.io/docs/latest/commands/incrby/">Increment integer by amount</Card>
-<Card title="INCRBYFLOAT" href="https://redis.io/docs/latest/commands/incrbyfloat/">Increment float by amount</Card>
-<Card title="MGET" href="https://redis.io/docs/latest/commands/mget/">Get values of multiple keys</Card>
-<Card title="MSET" href="https://redis.io/docs/latest/commands/mset/">Set multiple keys at once</Card>
-<Card title="MSETNX" href="https://redis.io/docs/latest/commands/msetnx/">Set multiple keys if none exist</Card>
-<Card title="PSETEX" href="https://redis.io/docs/latest/commands/psetex/">Set value with ms expiration</Card>
-<Card title="SET" href="https://redis.io/docs/latest/commands/set/">Set string value</Card>
-<Card title="SETEX" href="https://redis.io/docs/latest/commands/setex/">Set value with expiration</Card>
-<Card title="SETNX" href="https://redis.io/docs/latest/commands/setnx/">Set value if key doesn't exist</Card>
-<Card title="SETRANGE" href="https://redis.io/docs/latest/commands/setrange/">Overwrite part of string</Card>
-<Card title="STRLEN" href="https://redis.io/docs/latest/commands/strlen/">Get string length</Card>
-</CardGroup>
-</Accordion>
-
-<Accordion title="Transactions" icon="right-left">
-<CardGroup cols={2}>
-<Card title="DISCARD" href="https://redis.io/docs/latest/commands/discard/">Discard queued commands</Card>
-<Card title="EXEC" href="https://redis.io/docs/latest/commands/exec/">Execute queued commands</Card>
-<Card title="MULTI" href="https://redis.io/docs/latest/commands/multi/">Start a transaction</Card>
-<Card title="UNWATCH" href="https://redis.io/docs/latest/commands/unwatch/">Unwatch all keys</Card>
-<Card title="WATCH" href="https://redis.io/docs/latest/commands/watch/">Watch keys for changes</Card>
-</CardGroup>
-</Accordion>
-
-</AccordionGroup>
-
-***
+<Card title="Browse the Redis command reference" icon="book-open" href="/redis/commands/overview" horizontal>
+  See every supported Redis command, organized by category.
+</Card>
 
-We run command integration tests from the following Redis clients after each code change and also periodically:
+SDK command references may cover a smaller set of typed helpers.
+For example, see the [TypeScript SDK command reference](/docs/redis/sdks/ts/commands/overview) for the commands documented in `@upstash/redis`.
 
-* **[Node-Redis](https://github.com/redis/node-redis)**
-* **[Jedis](https://github.com/redis/jedis)**
-* **[Lettuce](https://github.com/lettuce-io/lettuce-core)**
-* **[Go-Redis](https://github.com/go-redis/redis)**
-* **[Redis-py](https://github.com/redis/redis-py)**
+Most unsupported items are on our roadmap. If you need a feature that we do not support, email [support@upstash.com](mailto:support@upstash.com) so we can let you know when we plan to support it.
 
 # Prod Pack & Enterprise
 Source: https://upstash.com/docs/redis/overall/enterprise
@@ -27781,7 +72494,7 @@ SEARCH.AGGREGATE products '{}' '{"by_category": {"$terms": {"field": "category",
 `$terms` bucket counts are **approximate**. Terms are tallied per index segment and then merged, so a term's `docCount` can be slightly off, especially for terms near the `size` cutoff.
 </Warning>
 
-`docCountErrorUpperBound` reports the maximum possible error on the returned counts (set `showTermDocCountError: true` for per-bucket values), and `sumOtherDocCount` is the number of matching documents not included in the returned buckets. Raising `segmentSize` reduces the error at the cost of more work per query. For an exact count of a specific term, use [`SEARCH.COUNT`](/docs/redis/search/command-reference#searchcount) instead of reading it from a bucket.
+`docCountErrorUpperBound` reports the maximum possible error on the returned counts (set `showTermDocCountError: true` for per-bucket values), and `sumOtherDocCount` is the number of matching documents not included in the returned buckets. Raising `segmentSize` reduces the error at the cost of more work per query. For an exact count of a specific term, use [`SEARCH.COUNT`](/docs/redis/commands/search/search-count) instead of reading it from a bucket.
 
 # $avg
 Source: https://upstash.com/docs/redis/search/aggregation-operators/metric-aggregations/avg
@@ -28460,6 +73173,8 @@ Source: https://upstash.com/docs/redis/search/aggregations
 Aggregations let you compute analytics over your indexed data — metrics like averages, sums, and statistics,
 as well as bucket-based groupings like terms, ranges, and histograms.
 
+Use the [`SEARCH.AGGREGATE`](/docs/redis/commands/search/search-aggregate) command to run aggregations.
+
 They are useful when you want to answer questions like:
 
 * "What is the average price?"
@@ -28744,7 +73459,7 @@ Aliases let you create alternative names for your search indices. This is useful
 
 ### Adding an Alias
 
-The `SEARCH.ALIASADD` command creates a new alias or updates an existing alias to point to a different index.
+The [`SEARCH.ALIASADD`](/docs/redis/commands/search/search-aliasadd) command creates a new alias or updates an existing alias to point to a different index.
 
 Returns `1` if a new alias was created, or `2` if an existing alias was updated to point to a new index.
 
@@ -28855,7 +73570,7 @@ SEARCH.DROP products-v1
 
 ### Deleting an Alias
 
-The `SEARCH.ALIASDEL` command removes an alias.
+The [`SEARCH.ALIASDEL`](/docs/redis/commands/search/search-aliasdel) command removes an alias.
 
 Returns `1` if the alias was deleted, or `0` if the alias was not found.
 
@@ -28885,7 +73600,7 @@ SEARCH.ALIASDEL products
 
 ### Listing Aliases
 
-The `SEARCH.LISTALIASES` command returns all aliases and the indices they point to.
+The [`SEARCH.LISTALIASES`](/docs/redis/commands/search/search-listaliases) command returns all aliases and the indices they point to.
 
 <Tabs>
 
@@ -28915,327 +73630,18 @@ SEARCH.LISTALIASES
 # Command Reference
 Source: https://upstash.com/docs/redis/search/command-reference
 
-A complete reference of all Upstash Redis Search commands, their syntax, and return values.
-
 <Note>
-Upstash Redis Search uses `SEARCH.*` commands. These are **not** the same as the `FT.*` commands
-from the open-source RediSearch module. The two are completely separate implementations and are
-not compatible with each other.
+  Upstash Redis Search uses `SEARCH.*` commands. They are separate from and incompatible with the `FT.*` commands in the open-source RediSearch module.
 </Note>
 
-## Index Commands
-
-### SEARCH.CREATE
-
-Creates a new search index.
-
-```bash
-SEARCH.CREATE <name> ON <JSON|HASH|STRING>
-  PREFIX <count> <prefix> [<prefix> ...]
-  [LANGUAGE <language>]
-  [SKIPINITIALSCAN]
-  [EXISTSOK]
-  SCHEMA <field> <type> [FAST] [NOSTEM] [NOTOKENIZE] [FROM <source_field>] ...
-```
-
-**Returns:** `1` on success. With `EXISTSOK`, returns `0` if an identical index already exists. Returns an error if the existing index has a different configuration.
-
-<Tabs>
-<Tab title="Redis CLI">
-```bash
-SEARCH.CREATE products ON JSON PREFIX 1 product: SCHEMA name TEXT price F64 FAST inStock BOOL
-```
-</Tab>
-<Tab title="curl">
-```bash
-curl -X POST https://YOUR_ENDPOINT.upstash.io \
-  -H "Authorization: Bearer $UPSTASH_REDIS_REST_TOKEN" \
-  -d '["SEARCH.CREATE", "products", "ON", "JSON", "PREFIX", "1", "product:", "SCHEMA", "name", "TEXT", "price", "F64", "FAST", "inStock", "BOOL"]'
-```
-</Tab>
-</Tabs>
-
-***
-
-### SEARCH.DROP
-
-Removes an index. The underlying Redis keys are **not** deleted.
-
-```bash
-SEARCH.DROP <name>
-```
-
-**Returns:** `1` if dropped, `0` if the index was not found.
-
-***
-
-### SEARCH.DESCRIBE
-
-Returns metadata about an index.
-
-```bash
-SEARCH.DESCRIBE <name>
-```
-
-**Returns:** Index metadata including name, data type, prefixes, language, and schema definition. Returns `null` if the index does not exist.
-
-***
-
-### SEARCH.WAITINDEXING
-
-Blocks until all pending index updates are processed and visible to queries.
-
-```bash
-SEARCH.WAITINDEXING <name>
-```
-
-**Returns:** `1` when indexing is complete, `0` if the index was not found.
-
-<Warning>
-Do not call `SEARCH.WAITINDEXING` after every write. Batch updates are necessary for
-optimal indexing performance. Use this command only when you need to ensure queries
-reflect recent changes, such as in tests or CI pipelines.
-</Warning>
-
-***
-
-### SEARCH.LISTINDEXES
-
-Lists all search indexes in the database.
-
-```bash
-SEARCH.LISTINDEXES [MATCH <pattern>] [LIMIT <count>] [OFFSET <offset>]
-```
-
-**Parameters:**
-
-| Parameter | Description | Default |
-|-----------|-------------|---------|
-| `MATCH` | Filter index names by a glob-style pattern (e.g. `h*`). | All indexes |
-| `LIMIT` | Maximum number of indexes to return. | All indexes |
-| `OFFSET` | Number of indexes to skip (for pagination). | 0 |
-
-**Returns:** One entry per index, each a map of `name` and the backing `type` (`HASH` or `JSON`).
-
-**Response format (Redis CLI):**
-
-```
-[
-  ["name", "productIdx", "type", "HASH"],
-  ["name", "blogIdx", "type", "JSON"]
-]
-```
-
-<Tabs>
-<Tab title="Redis CLI">
-```bash
-SEARCH.LISTINDEXES MATCH 'product*' LIMIT 10 OFFSET 0
-```
-</Tab>
-<Tab title="curl">
-```bash
-curl -X POST https://YOUR_ENDPOINT.upstash.io \
-  -H "Authorization: Bearer $UPSTASH_REDIS_REST_TOKEN" \
-  -d '["SEARCH.LISTINDEXES", "MATCH", "product*", "LIMIT", "10", "OFFSET", "0"]'
-```
-</Tab>
-</Tabs>
-
-***
-
-## Query Commands
-
-### SEARCH.QUERY
-
-Searches for documents matching a JSON filter.
-
-```bash
-SEARCH.QUERY <name> '<json_filter>'
-  [LIMIT <count>]
-  [OFFSET <offset>]
-  [ORDERBY <field> <ASC|DESC>]
-  [SELECT <count> <field> [<field> ...]]
-  [NOCONTENT]
-  [HIGHLIGHT FIELDS <count> <field> [<field> ...] [TAGS <open> <close>]]
-  [SCOREFUNC ...]
-```
-
-**Parameters:**
-
-| Parameter | Description | Default |
-|-----------|-------------|---------|
-| `LIMIT` | Maximum number of results to return. Must be between 1 and 1000. | 10 |
-| `OFFSET` | Number of results to skip (for pagination). | 0 |
-| `ORDERBY` | Sort by a FAST field in `ASC` or `DESC` order. | Sort by relevance score (descending) |
-| `SELECT` | Return only specific fields. Prefix with count of fields. | All fields |
-| `NOCONTENT` | Return only keys and scores, no document content. | Disabled |
-| `HIGHLIGHT` | Wrap matching terms in tags. Default tags: `<em>` / `</em>`. | Disabled |
-| `SCOREFUNC` | Adjust relevance scores using numeric field values. | Disabled |
-
-**Response format (Redis CLI):**
-
-```
-[
-  ["key1", "score1", [["$", "{\"name\": \"...\", ...}"]]],
-  ["key2", "score2", [["$", "{\"name\": \"...\", ...}"]]]
-]
-```
-
-Each result is an array of `[key, score, content]` where:
-* `key` — the Redis key of the matching document
-* `score` — relevance score (float)
-* `content` — array of field-value pairs (for JSON indexes: `[["$", "<json_string>"]]`; for HASH indexes: `[["field", "value"], ...]`)
-
-When `NOCONTENT` is used, the content element is omitted.
-When `SELECT` is used, only the selected fields appear in the content.
-
-<Tabs>
-<Tab title="Redis CLI">
-```bash
-SEARCH.QUERY products '{"name": "wireless"}' LIMIT 10 OFFSET 0
-```
-</Tab>
-<Tab title="curl">
-```bash
-curl -X POST https://YOUR_ENDPOINT.upstash.io \
-  -H "Authorization: Bearer $UPSTASH_REDIS_REST_TOKEN" \
-  -d '["SEARCH.QUERY", "products", "{\"name\": \"wireless\"}", "LIMIT", "10", "OFFSET", "0"]'
-```
-</Tab>
-</Tabs>
-
-***
-
-### SEARCH.COUNT
-
-Returns the number of documents matching a query without retrieving them.
-
-```bash
-SEARCH.COUNT <name> '<json_filter>'
-```
-
-**Returns:** An integer — the count of matching documents.
-
-<Tabs>
-<Tab title="Redis CLI">
-```bash
-SEARCH.COUNT products '{"inStock": true}'
-```
-</Tab>
-<Tab title="curl">
-```bash
-curl -X POST https://YOUR_ENDPOINT.upstash.io \
-  -H "Authorization: Bearer $UPSTASH_REDIS_REST_TOKEN" \
-  -d '["SEARCH.COUNT", "products", "{\"inStock\": true}"]'
-```
-</Tab>
-</Tabs>
-
-***
-
-### SEARCH.AGGREGATE
-
-Computes analytics (metrics and buckets) over matching documents.
-
-```bash
-SEARCH.AGGREGATE <name> '<json_filter>' '<json_aggregations>'
-```
-
-**Response format (Redis CLI):**
-
-In `redis-cli --json`, the response is an object keyed by alias:
-
-```json
-{
-  "avg_price": { "value": 49.99 },
-  "by_category": { "buckets": [{ "key": "electronics", "docCount": 42 }] }
-}
-```
-
-Raw RESP output may be rendered differently by client/protocol settings, but semantically each top-level alias maps to its aggregation result.
-
-<Tabs>
-<Tab title="Redis CLI">
-```bash
-SEARCH.AGGREGATE products '{}' '{"avg_price": {"$avg": {"field": "price"}}}'
-```
-</Tab>
-<Tab title="curl">
-```bash
-curl -X POST https://YOUR_ENDPOINT.upstash.io \
-  -H "Authorization: Bearer $UPSTASH_REDIS_REST_TOKEN" \
-  -d '["SEARCH.AGGREGATE", "products", "{}", "{\"avg_price\": {\"$avg\": {\"field\": \"price\"}}}"]'
-```
-</Tab>
-</Tabs>
-
-***
-
-## Alias Commands
-
-### SEARCH.ALIASADD
-
-Creates or updates an alias pointing to an index.
-
-```bash
-SEARCH.ALIASADD <alias> <index_name>
-```
-
-**Returns:** `1` if a new alias was created, `2` if an existing alias was updated.
-
-***
-
-### SEARCH.ALIASDEL
-
-Removes an alias.
-
-```bash
-SEARCH.ALIASDEL <alias>
-```
-
-**Returns:** `1` if deleted, `0` if the alias was not found.
-
-***
-
-### SEARCH.LISTALIASES
-
-Returns all aliases and the indices they point to.
-
-```bash
-SEARCH.LISTALIASES
-```
-
-**Returns:** An array of `[alias, index_name]` pairs, or an empty array if no aliases exist. To list every index in the database, use [`SEARCH.LISTINDEXES`](#searchlistindexes).
-
-***
-
-## REST API Usage
-
-All search commands can be sent via the Upstash REST API using a JSON array POST body.
-Each element of the array corresponds to a token in the command.
-
-```bash
-curl -X POST https://YOUR_ENDPOINT.upstash.io \
-  -H "Authorization: Bearer $UPSTASH_REDIS_REST_TOKEN" \
-  -d '["COMMAND", "arg1", "arg2", ...]'
-```
-
-The JSON filter and aggregation arguments are passed as string values within the array (not as nested JSON objects):
-
-```bash
-# Correct — filter is a string inside the array
-["SEARCH.QUERY", "products", "{\"name\": \"wireless\"}", "LIMIT", "10"]
-
-# Incorrect — filter is a nested object
-["SEARCH.QUERY", "products", {"name": "wireless"}, "LIMIT", "10"]
-```
-
-Search commands also work through the `/pipeline` endpoint for batching multiple commands in a single HTTP request.
+<Card title="Browse Search commands" icon="magnifying-glass" href="/redis/commands/search/overview" horizontal>
+  View the complete Upstash Redis Search command reference.
+</Card>
 
 # Counting
 Source: https://upstash.com/docs/redis/search/counting
 
-The `SEARCH.COUNT` command returns the number of documents matching a query without retrieving them.
+The [`SEARCH.COUNT`](/docs/redis/commands/search/search-count) command returns the number of documents matching a query without retrieving them.
 
 You can use `SEARCH.COUNT` for analytics, pagination UI (showing "X results found"),
 or validating queries before retrieving results.
@@ -29304,7 +73710,7 @@ Any command that modifies a matching key updates the index. For example, this in
 This is not an exhaustive list. The rule is that if the command changes a key tracked by the index, the index is updated.
 
 Index updates are batched for performance, so recent writes may not immediately appear in search results.
-Use [`SEARCH.WAITINDEXING`](/docs/redis/search/index-management#waiting-for-indexing) when you need to ensure queries reflect recent changes.
+Use [`SEARCH.WAITINDEXING`](/docs/redis/commands/search/search-waitindexing) when you need to ensure queries reflect recent changes.
 
 ## JSON Documents
 
@@ -29727,7 +74133,7 @@ You define an index once by specifying:
 
 ### Creating an Index
 
-An index is identified by its name, which must be a unique key in Redis. Each index works with a single key type (JSON, hash, or string).
+The [`SEARCH.CREATE`](/docs/redis/commands/search/search-create) command creates an index identified by a name, which must be a unique key in Redis. Each index works with a single key type (JSON, hash, or string).
 
 <Tabs>
 
@@ -29904,7 +74310,8 @@ SEARCH.CREATE comments ON STRING PREFIX 1 comment: SCHEMA user.name TEXT user.em
 
 By default, when an index is created, all existing keys matching the specified type and prefixes are scanned and indexed.
 Use `SKIPINITIALSCAN` to defer indexing, which is useful for large datasets where you want to start fresh or handle
-existing data differently.
+existing data differently. Run [`SEARCH.REINDEX`](/docs/redis/commands/search/search-reindex) later to rebuild the index from
+the current matching keys.
 
 <Tabs>
 
@@ -30131,7 +74538,7 @@ Use `redis.search.createIndex()` when:
 
 ### Describing an Index
 
-The `SEARCH.DESCRIBE` command returns detailed information about an index, or `null` if the index doesn't exist.
+The [`SEARCH.DESCRIBE`](/docs/redis/commands/search/search-describe) command returns detailed information about an index, or `null` if the index doesn't exist.
 
 <Tabs>
 
@@ -30171,7 +74578,7 @@ On response, the following information is returned:
 
 ### Listing Indexes
 
-`SEARCH.LISTINDEXES` lists all search indexes in the database, reporting each index's `name` and backing `type` (`HASH` or `JSON`). Optionally filter names with `MATCH` and paginate with `LIMIT` and `OFFSET`.
+[`SEARCH.LISTINDEXES`](/docs/redis/commands/search/search-listindexes) lists all search indexes in the database, reporting each index's `name` and backing `type` (`HASH` or `JSON`). Optionally filter names with `MATCH` and paginate with `LIMIT` and `OFFSET`.
 
 <Tabs>
 
@@ -30188,7 +74595,7 @@ SEARCH.LISTINDEXES MATCH 'product*' LIMIT 10 OFFSET 0
 
 ### Dropping an Index
 
-The `SEARCH.DROP` command removes an index and stops tracking associated keys.
+The [`SEARCH.DROP`](/docs/redis/commands/search/search-drop) command removes an index and stops tracking associated keys.
 
 Returns `1` if the index was dropped, or `0` if the index was not found.
 
@@ -30221,7 +74628,7 @@ Note that, dropping an index only removes the search index. The underlying Redis
 ### Waiting for Indexing
 
 For adequate performance, index updates are batched and committed periodically. This means recent writes may not
-immediately appear in search results. Use `SEARCH.WAITINDEXING` when you need to ensure queries reflect recent changes.
+immediately appear in search results. Use [`SEARCH.WAITINDEXING`](/docs/redis/commands/search/search-waitindexing) when you need to ensure queries reflect recent changes.
 
 The `SEARCH.WAITINDEXING` command blocks until all pending index updates are processed and visible to queries.
 For examples of changing, deleting, and expiring indexed documents, see [Document Updates](/docs/redis/search/document-updates).
@@ -31790,6 +76197,8 @@ Source: https://upstash.com/docs/redis/search/querying
 
 Queries are JSON strings that describe which documents to return. If the index doesn't exist, queries return `null`.
 
+Use the [`SEARCH.QUERY`](/docs/redis/commands/search/search-query) command to run a query.
+
 We recommend searching by field values directly because we automatically provide intelligent matching behavior out of the box:
 
 <Tabs>
@@ -31893,7 +76302,7 @@ When `select` / `NOCONTENT` is used, the response shape changes — see [Control
 
 If no documents match, an empty array is returned. If the index doesn't exist, `null` is returned.
 
-For a detailed breakdown of the raw response structure, see the [Command Reference](/docs/redis/search/command-reference#searchquery).
+For exact syntax and a detailed breakdown of the raw response structure, see the [`SEARCH.QUERY` command reference](/docs/redis/commands/search/search-query).
 
 ***
 
@@ -32446,6 +76855,8 @@ const schema = s.object({
 
 We need the schema when creating or querying an index:
 
+For the complete index creation syntax, see [`SEARCH.CREATE`](/docs/redis/commands/search/search-create).
+
 ```ts
 import { Redis, s } from "@upstash/redis"
 
diff --git a/llms.txt b/llms.txt
index f86d128df..9f16941c8 100644
--- a/llms.txt
+++ b/llms.txt
@@ -281,6 +281,298 @@
 - [Deployment](https://upstash.com/docs/realtime/features/serverless.md)
 - [Pricing](https://upstash.com/docs/realtime/overall/pricing.md)
 - [Quickstart](https://upstash.com/docs/realtime/overall/quickstart.md)
+- [BITCOUNT](https://upstash.com/docs/redis/commands/bitmap/bitcount.md): Count set bits in a string.
+- [BITFIELD](https://upstash.com/docs/redis/commands/bitmap/bitfield.md): Perform arbitrary bitfield operations.
+- [BITFIELD_RO](https://upstash.com/docs/redis/commands/bitmap/bitfield-ro.md): Read bitfield values.
+- [BITOP](https://upstash.com/docs/redis/commands/bitmap/bitop.md): Perform bitwise operations between strings.
+- [BITPOS](https://upstash.com/docs/redis/commands/bitmap/bitpos.md): Find first bit set or clear in a string.
+- [GETBIT](https://upstash.com/docs/redis/commands/bitmap/getbit.md): Get the bit value at offset.
+- [Bitmap commands](https://upstash.com/docs/redis/commands/bitmap/overview.md): Commands for manipulating individual bits and bit fields in string values.
+- [SETBIT](https://upstash.com/docs/redis/commands/bitmap/setbit.md): Set or clear the bit at offset.
+- [AUTH](https://upstash.com/docs/redis/commands/connection/auth.md): Authenticate to the server.
+- [CLIENT GETNAME](https://upstash.com/docs/redis/commands/connection/client-getname.md): Get the current connection name.
+- [CLIENT ID](https://upstash.com/docs/redis/commands/connection/client-id.md): Get the current client ID.
+- [CLIENT INFO](https://upstash.com/docs/redis/commands/connection/client-info.md): Get info about current connection.
+- [CLIENT LIST](https://upstash.com/docs/redis/commands/connection/client-list.md): List all client connections.
+- [CLIENT SETINFO](https://upstash.com/docs/redis/commands/connection/client-setinfo.md): Set client connection attributes.
+- [CLIENT SETNAME](https://upstash.com/docs/redis/commands/connection/client-setname.md): Set the connection name.
+- [ECHO](https://upstash.com/docs/redis/commands/connection/echo.md): Echo the given string.
+- [HELLO](https://upstash.com/docs/redis/commands/connection/hello.md): Handshake with Redis protocol.
+- [Connection commands](https://upstash.com/docs/redis/commands/connection/overview.md): Commands for authenticating, inspecting, and managing client connections.
+- [PING](https://upstash.com/docs/redis/commands/connection/ping.md): Ping the server.
+- [QUIT](https://upstash.com/docs/redis/commands/connection/quit.md): Close the connection.
+- [RESET](https://upstash.com/docs/redis/commands/connection/reset.md): Reset the connection.
+- [SELECT](https://upstash.com/docs/redis/commands/connection/select.md): Select the database by index.
+- [FCALL](https://upstash.com/docs/redis/commands/functions/fcall.md): Call a function.
+- [FCALL_RO](https://upstash.com/docs/redis/commands/functions/fcall-ro.md): Call a read-only function.
+- [FUNCTION DELETE](https://upstash.com/docs/redis/commands/functions/function-delete.md): Delete a library.
+- [FUNCTION FLUSH](https://upstash.com/docs/redis/commands/functions/function-flush.md): Delete all libraries.
+- [FUNCTION KILL](https://upstash.com/docs/redis/commands/functions/function-kill.md): Kill a running function.
+- [FUNCTION LIST](https://upstash.com/docs/redis/commands/functions/function-list.md): List all libraries.
+- [FUNCTION LOAD](https://upstash.com/docs/redis/commands/functions/function-load.md): Load a library.
+- [FUNCTION STATS](https://upstash.com/docs/redis/commands/functions/function-stats.md): Get function execution stats.
+- [Functions commands](https://upstash.com/docs/redis/commands/functions/overview.md): Commands for loading, managing, and invoking Redis functions.
+- [COPY](https://upstash.com/docs/redis/commands/generic/copy.md): Copy a key to another key.
+- [DEL](https://upstash.com/docs/redis/commands/generic/del.md): Delete one or more keys.
+- [DUMP](https://upstash.com/docs/redis/commands/generic/dump.md): Serialize a key's value.
+- [EXISTS](https://upstash.com/docs/redis/commands/generic/exists.md): Check if keys exist.
+- [EXPIRE](https://upstash.com/docs/redis/commands/generic/expire.md): Set a key's TTL in seconds.
+- [EXPIREAT](https://upstash.com/docs/redis/commands/generic/expireat.md): Set expiry as Unix timestamp.
+- [EXPIRETIME](https://upstash.com/docs/redis/commands/generic/expiretime.md): Get expiry as Unix timestamp.
+- [KEYS](https://upstash.com/docs/redis/commands/generic/keys.md): Find keys matching a pattern.
+- [MEMORY USAGE](https://upstash.com/docs/redis/commands/generic/memory-usage.md): Estimate memory used by a key.
+- [Generic commands](https://upstash.com/docs/redis/commands/generic/overview.md): Commands for managing keys, expiration, serialization, and database-wide key operations.
+- [PERSIST](https://upstash.com/docs/redis/commands/generic/persist.md): Remove the expiration from a key.
+- [PEXPIRE](https://upstash.com/docs/redis/commands/generic/pexpire.md): Set a key's TTL in milliseconds.
+- [PEXPIREAT](https://upstash.com/docs/redis/commands/generic/pexpireat.md): Set expiry as Unix ms timestamp.
+- [PEXPIRETIME](https://upstash.com/docs/redis/commands/generic/pexpiretime.md): Get expiry as Unix ms timestamp.
+- [PTTL](https://upstash.com/docs/redis/commands/generic/pttl.md): Get TTL in milliseconds.
+- [RANDOMKEY](https://upstash.com/docs/redis/commands/generic/randomkey.md): Return a random key.
+- [RENAME](https://upstash.com/docs/redis/commands/generic/rename.md): Rename a key.
+- [RENAMENX](https://upstash.com/docs/redis/commands/generic/renamenx.md): Rename a key if new key doesn't exist.
+- [RESTORE](https://upstash.com/docs/redis/commands/generic/restore.md): Deserialize and restore a key.
+- [SCAN](https://upstash.com/docs/redis/commands/generic/scan.md): Incrementally iterate keys.
+- [TOUCH](https://upstash.com/docs/redis/commands/generic/touch.md): Update last access time of keys.
+- [TTL](https://upstash.com/docs/redis/commands/generic/ttl.md): Get TTL in seconds.
+- [TYPE](https://upstash.com/docs/redis/commands/generic/type.md): Get the type of a key.
+- [UNLINK](https://upstash.com/docs/redis/commands/generic/unlink.md): Delete keys asynchronously.
+- [WAIT](https://upstash.com/docs/redis/commands/generic/wait.md): Wait for replica acknowledgements.
+- [WAITAOF](https://upstash.com/docs/redis/commands/generic/waitaof.md): Wait for local and replica persistence.
+- [GEOADD](https://upstash.com/docs/redis/commands/geo/geoadd.md): Add geospatial items.
+- [GEODIST](https://upstash.com/docs/redis/commands/geo/geodist.md): Get distance between two members.
+- [GEOHASH](https://upstash.com/docs/redis/commands/geo/geohash.md): Get geohash strings for members.
+- [GEOPOS](https://upstash.com/docs/redis/commands/geo/geopos.md): Get coordinates of members.
+- [GEORADIUS](https://upstash.com/docs/redis/commands/geo/georadius.md): Query members within radius.
+- [GEORADIUS_RO](https://upstash.com/docs/redis/commands/geo/georadius-ro.md): Find members within a radius of a point.
+- [GEORADIUSBYMEMBER](https://upstash.com/docs/redis/commands/geo/georadiusbymember.md): Radius query centered on member.
+- [GEORADIUSBYMEMBER_RO](https://upstash.com/docs/redis/commands/geo/georadiusbymember-ro.md): Find members within a radius of another member.
+- [GEOSEARCH](https://upstash.com/docs/redis/commands/geo/geosearch.md): Search for members in an area.
+- [GEOSEARCHSTORE](https://upstash.com/docs/redis/commands/geo/geosearchstore.md): Store geosearch results.
+- [Geo commands](https://upstash.com/docs/redis/commands/geo/overview.md): Commands for storing and querying geospatial data.
+- [HDEL](https://upstash.com/docs/redis/commands/hash/hdel.md): Delete one or more hash fields.
+- [HEXISTS](https://upstash.com/docs/redis/commands/hash/hexists.md): Check if a hash field exists.
+- [HEXPIRE](https://upstash.com/docs/redis/commands/hash/hexpire.md): Set field TTL in seconds.
+- [HEXPIREAT](https://upstash.com/docs/redis/commands/hash/hexpireat.md): Set field expiry as timestamp.
+- [HEXPIRETIME](https://upstash.com/docs/redis/commands/hash/hexpiretime.md): Get field expiry as timestamp.
+- [HGET](https://upstash.com/docs/redis/commands/hash/hget.md): Get the value of a hash field.
+- [HGETALL](https://upstash.com/docs/redis/commands/hash/hgetall.md): Get all fields and values.
+- [HGETDEL](https://upstash.com/docs/redis/commands/hash/hgetdel.md): Get and delete hash fields.
+- [HGETEX](https://upstash.com/docs/redis/commands/hash/hgetex.md): Get fields and set their expiry.
+- [HINCRBY](https://upstash.com/docs/redis/commands/hash/hincrby.md): Increment integer value of a field.
+- [HINCRBYFLOAT](https://upstash.com/docs/redis/commands/hash/hincrbyfloat.md): Increment float value of a field.
+- [HKEYS](https://upstash.com/docs/redis/commands/hash/hkeys.md): Get all fields in a hash.
+- [HLEN](https://upstash.com/docs/redis/commands/hash/hlen.md): Get number of fields in a hash.
+- [HMGET](https://upstash.com/docs/redis/commands/hash/hmget.md): Get values of multiple fields.
+- [HMSET](https://upstash.com/docs/redis/commands/hash/hmset.md): Set multiple hash fields.
+- [HPERSIST](https://upstash.com/docs/redis/commands/hash/hpersist.md): Remove field expiration.
+- [HPEXPIRE](https://upstash.com/docs/redis/commands/hash/hpexpire.md): Set field TTL in milliseconds.
+- [HPEXPIREAT](https://upstash.com/docs/redis/commands/hash/hpexpireat.md): Set field expiry as ms timestamp.
+- [HPEXPIRETIME](https://upstash.com/docs/redis/commands/hash/hpexpiretime.md): Get field expiry as ms timestamp.
+- [HPTTL](https://upstash.com/docs/redis/commands/hash/hpttl.md): Get field TTL in milliseconds.
+- [HRANDFIELD](https://upstash.com/docs/redis/commands/hash/hrandfield.md): Get random fields from a hash.
+- [HSCAN](https://upstash.com/docs/redis/commands/hash/hscan.md): Incrementally iterate hash fields.
+- [HSET](https://upstash.com/docs/redis/commands/hash/hset.md): Set hash field values.
+- [HSETEX](https://upstash.com/docs/redis/commands/hash/hsetex.md): Set fields with expiration.
+- [HSETNX](https://upstash.com/docs/redis/commands/hash/hsetnx.md): Set field only if it doesn't exist.
+- [HSTRLEN](https://upstash.com/docs/redis/commands/hash/hstrlen.md): Get length of a field's value.
+- [HTTL](https://upstash.com/docs/redis/commands/hash/httl.md): Get field TTL in seconds.
+- [HVALS](https://upstash.com/docs/redis/commands/hash/hvals.md): Get all values in a hash.
+- [Hash commands](https://upstash.com/docs/redis/commands/hash/overview.md): Commands for storing and manipulating field-value collections.
+- [HyperLogLog commands](https://upstash.com/docs/redis/commands/hyperloglog/overview.md): Commands for probabilistic cardinality estimation.
+- [PFADD](https://upstash.com/docs/redis/commands/hyperloglog/pfadd.md): Add elements to HyperLogLog.
+- [PFCOUNT](https://upstash.com/docs/redis/commands/hyperloglog/pfcount.md): Get estimated cardinality.
+- [PFMERGE](https://upstash.com/docs/redis/commands/hyperloglog/pfmerge.md): Merge multiple HyperLogLogs.
+- [JSON.ARRAPPEND](https://upstash.com/docs/redis/commands/json/json-arrappend.md): Append values to JSON array.
+- [JSON.ARRINDEX](https://upstash.com/docs/redis/commands/json/json-arrindex.md): Find index of value in array.
+- [JSON.ARRINSERT](https://upstash.com/docs/redis/commands/json/json-arrinsert.md): Insert values into JSON array.
+- [JSON.ARRLEN](https://upstash.com/docs/redis/commands/json/json-arrlen.md): Get JSON array length.
+- [JSON.ARRPOP](https://upstash.com/docs/redis/commands/json/json-arrpop.md): Pop value from JSON array.
+- [JSON.ARRTRIM](https://upstash.com/docs/redis/commands/json/json-arrtrim.md): Trim JSON array to range.
+- [JSON.CLEAR](https://upstash.com/docs/redis/commands/json/json-clear.md): Clear JSON values.
+- [JSON.DEBUG](https://upstash.com/docs/redis/commands/json/json-debug.md): Inspect JSON memory usage.
+- [JSON.DEL](https://upstash.com/docs/redis/commands/json/json-del.md): Delete JSON values.
+- [JSON.FORGET](https://upstash.com/docs/redis/commands/json/json-forget.md): Alias for JSON.DEL.
+- [JSON.GET](https://upstash.com/docs/redis/commands/json/json-get.md): Get JSON values.
+- [JSON.MERGE](https://upstash.com/docs/redis/commands/json/json-merge.md): Merge JSON values.
+- [JSON.MGET](https://upstash.com/docs/redis/commands/json/json-mget.md): Get values from multiple keys.
+- [JSON.MSET](https://upstash.com/docs/redis/commands/json/json-mset.md): Set values in multiple keys.
+- [JSON.NUMINCRBY](https://upstash.com/docs/redis/commands/json/json-numincrby.md): Increment JSON number.
+- [JSON.NUMMULTBY](https://upstash.com/docs/redis/commands/json/json-nummultby.md): Multiply JSON number.
+- [JSON.OBJKEYS](https://upstash.com/docs/redis/commands/json/json-objkeys.md): Get JSON object keys.
+- [JSON.OBJLEN](https://upstash.com/docs/redis/commands/json/json-objlen.md): Get JSON object size.
+- [JSON.RESP](https://upstash.com/docs/redis/commands/json/json-resp.md): Get JSON in RESP format.
+- [JSON.SET](https://upstash.com/docs/redis/commands/json/json-set.md): Set JSON value.
+- [JSON.STRAPPEND](https://upstash.com/docs/redis/commands/json/json-strappend.md): Append to JSON string.
+- [JSON.STRLEN](https://upstash.com/docs/redis/commands/json/json-strlen.md): Get JSON string length.
+- [JSON.TOGGLE](https://upstash.com/docs/redis/commands/json/json-toggle.md): Toggle JSON boolean.
+- [JSON.TYPE](https://upstash.com/docs/redis/commands/json/json-type.md): Get JSON value type.
+- [JSON commands](https://upstash.com/docs/redis/commands/json/overview.md): Commands for storing and manipulating JSON values.
+- [BLMOVE](https://upstash.com/docs/redis/commands/list/blmove.md): Move an element between lists, blocking until one arrives.
+- [BLMPOP](https://upstash.com/docs/redis/commands/list/blmpop.md): Pop from the first non-empty list, blocking until one arrives.
+- [BLPOP](https://upstash.com/docs/redis/commands/list/blpop.md): Pop from the head of a list, blocking until an element arrives.
+- [BRPOP](https://upstash.com/docs/redis/commands/list/brpop.md): Pop from the tail of a list, blocking until an element arrives.
+- [BRPOPLPUSH](https://upstash.com/docs/redis/commands/list/brpoplpush.md): Pop from a list's tail and push it to another, blocking until an element arrives.
+- [LINDEX](https://upstash.com/docs/redis/commands/list/lindex.md): Get element by index.
+- [LINSERT](https://upstash.com/docs/redis/commands/list/linsert.md): Insert before or after pivot.
+- [LLEN](https://upstash.com/docs/redis/commands/list/llen.md): Get list length.
+- [LMOVE](https://upstash.com/docs/redis/commands/list/lmove.md): Move element between lists.
+- [LMPOP](https://upstash.com/docs/redis/commands/list/lmpop.md): Pop from multiple lists.
+- [LPOP](https://upstash.com/docs/redis/commands/list/lpop.md): Pop from list head.
+- [LPOS](https://upstash.com/docs/redis/commands/list/lpos.md): Find element position.
+- [LPUSH](https://upstash.com/docs/redis/commands/list/lpush.md): Push to list head.
+- [LPUSHX](https://upstash.com/docs/redis/commands/list/lpushx.md): Push to head if list exists.
+- [LRANGE](https://upstash.com/docs/redis/commands/list/lrange.md): Get range of elements.
+- [LREM](https://upstash.com/docs/redis/commands/list/lrem.md): Remove elements by value.
+- [LSET](https://upstash.com/docs/redis/commands/list/lset.md): Set element at index.
+- [LTRIM](https://upstash.com/docs/redis/commands/list/ltrim.md): Trim list to range.
+- [List commands](https://upstash.com/docs/redis/commands/list/overview.md): Commands for storing and manipulating ordered collections.
+- [RPOP](https://upstash.com/docs/redis/commands/list/rpop.md): Pop from list tail.
+- [RPOPLPUSH](https://upstash.com/docs/redis/commands/list/rpoplpush.md): Pop from tail and push to head.
+- [RPUSH](https://upstash.com/docs/redis/commands/list/rpush.md): Push to list tail.
+- [RPUSHX](https://upstash.com/docs/redis/commands/list/rpushx.md): Push to tail if list exists.
+- [Redis command reference](https://upstash.com/docs/redis/commands/overview.md): Browse the Redis commands supported by Upstash, organized by category.
+- [Pub/Sub commands](https://upstash.com/docs/redis/commands/pub-sub/overview.md): Commands for publishing messages and managing channel subscriptions.
+- [PSUBSCRIBE](https://upstash.com/docs/redis/commands/pub-sub/psubscribe.md): Subscribe to pattern channels.
+- [PUBLISH](https://upstash.com/docs/redis/commands/pub-sub/publish.md): Publish message to channel.
+- [PUBSUB](https://upstash.com/docs/redis/commands/pub-sub/pubsub.md): Inspect pub/sub state.
+- [PUNSUBSCRIBE](https://upstash.com/docs/redis/commands/pub-sub/punsubscribe.md): Unsubscribe from patterns.
+- [SUBSCRIBE](https://upstash.com/docs/redis/commands/pub-sub/subscribe.md): Subscribe to channels.
+- [UNSUBSCRIBE](https://upstash.com/docs/redis/commands/pub-sub/unsubscribe.md): Unsubscribe from channels.
+- [EVAL](https://upstash.com/docs/redis/commands/scripting/eval.md): Execute a Lua script.
+- [EVAL_RO](https://upstash.com/docs/redis/commands/scripting/eval-ro.md): Execute read-only Lua script.
+- [EVALSHA](https://upstash.com/docs/redis/commands/scripting/evalsha.md): Execute cached Lua script by SHA.
+- [EVALSHA_RO](https://upstash.com/docs/redis/commands/scripting/evalsha-ro.md): Run a cached script that does not write.
+- [Scripting commands](https://upstash.com/docs/redis/commands/scripting/overview.md): Commands for loading and executing Lua scripts.
+- [SCRIPT EXISTS](https://upstash.com/docs/redis/commands/scripting/script-exists.md): Check if scripts exist in cache.
+- [SCRIPT FLUSH](https://upstash.com/docs/redis/commands/scripting/script-flush.md): Clear the script cache.
+- [SCRIPT KILL](https://upstash.com/docs/redis/commands/scripting/script-kill.md): Stop a running read-only script.
+- [SCRIPT LOAD](https://upstash.com/docs/redis/commands/scripting/script-load.md): Load script into cache.
+- [Search commands](https://upstash.com/docs/redis/commands/search/overview.md): Commands for creating, querying, and managing Upstash Redis Search indexes.
+- [SEARCH.AGGREGATE](https://upstash.com/docs/redis/commands/search/search-aggregate.md): Compute analytics over matching documents.
+- [SEARCH.ALIASADD](https://upstash.com/docs/redis/commands/search/search-aliasadd.md): Create or update a search index alias.
+- [SEARCH.ALIASDEL](https://upstash.com/docs/redis/commands/search/search-aliasdel.md): Delete a search index alias.
+- [SEARCH.COUNT](https://upstash.com/docs/redis/commands/search/search-count.md): Count documents matching a query.
+- [SEARCH.CREATE](https://upstash.com/docs/redis/commands/search/search-create.md): Create a search index.
+- [SEARCH.DESCRIBE](https://upstash.com/docs/redis/commands/search/search-describe.md): Return metadata about a search index.
+- [SEARCH.DROP](https://upstash.com/docs/redis/commands/search/search-drop.md): Drop a search index without deleting its keys.
+- [SEARCH.LISTALIASES](https://upstash.com/docs/redis/commands/search/search-listaliases.md): List search index aliases.
+- [SEARCH.LISTINDEXES](https://upstash.com/docs/redis/commands/search/search-listindexes.md): List search indexes in the database.
+- [SEARCH.QUERY](https://upstash.com/docs/redis/commands/search/search-query.md): Search documents with a JSON filter.
+- [SEARCH.REINDEX](https://upstash.com/docs/redis/commands/search/search-reindex.md): Rebuild a search index from the current matching data.
+- [SEARCH.WAITINDEXING](https://upstash.com/docs/redis/commands/search/search-waitindexing.md): Wait until pending index updates are visible.
+- [ACL](https://upstash.com/docs/redis/commands/server/acl.md): Manage access control list.
+- [COMMAND](https://upstash.com/docs/redis/commands/server/command.md): Get command metadata.
+- [CONFIG GET](https://upstash.com/docs/redis/commands/server/config-get.md): Read runtime configuration.
+- [CONFIG SET](https://upstash.com/docs/redis/commands/server/config-set.md): Change runtime configuration.
+- [DBSIZE](https://upstash.com/docs/redis/commands/server/dbsize.md): Get number of keys in database.
+- [FLUSHALL](https://upstash.com/docs/redis/commands/server/flushall.md): Delete all keys in all databases.
+- [FLUSHDB](https://upstash.com/docs/redis/commands/server/flushdb.md): Delete all keys in current database.
+- [INFO](https://upstash.com/docs/redis/commands/server/info.md): Get server statistics and information.
+- [MONITOR](https://upstash.com/docs/redis/commands/server/monitor.md): Stream all commands received.
+- [Server commands](https://upstash.com/docs/redis/commands/server/overview.md): Commands for inspecting and managing the Redis server.
+- [TIME](https://upstash.com/docs/redis/commands/server/time.md): Get current server time.
+- [Set commands](https://upstash.com/docs/redis/commands/set/overview.md): Commands for storing and manipulating unordered collections of unique members.
+- [SADD](https://upstash.com/docs/redis/commands/set/sadd.md): Add members to a set.
+- [SCARD](https://upstash.com/docs/redis/commands/set/scard.md): Get set cardinality.
+- [SDIFF](https://upstash.com/docs/redis/commands/set/sdiff.md): Get set difference.
+- [SDIFFSTORE](https://upstash.com/docs/redis/commands/set/sdiffstore.md): Store set difference.
+- [SINTER](https://upstash.com/docs/redis/commands/set/sinter.md): Get set intersection.
+- [SINTERCARD](https://upstash.com/docs/redis/commands/set/sintercard.md): Get intersection cardinality.
+- [SINTERSTORE](https://upstash.com/docs/redis/commands/set/sinterstore.md): Store set intersection.
+- [SISMEMBER](https://upstash.com/docs/redis/commands/set/sismember.md): Check if member exists in set.
+- [SMEMBERS](https://upstash.com/docs/redis/commands/set/smembers.md): Get all set members.
+- [SMISMEMBER](https://upstash.com/docs/redis/commands/set/smismember.md): Check multiple members.
+- [SMOVE](https://upstash.com/docs/redis/commands/set/smove.md): Move member between sets.
+- [SPOP](https://upstash.com/docs/redis/commands/set/spop.md): Remove random members.
+- [SRANDMEMBER](https://upstash.com/docs/redis/commands/set/srandmember.md): Get random members.
+- [SREM](https://upstash.com/docs/redis/commands/set/srem.md): Remove members from a set.
+- [SSCAN](https://upstash.com/docs/redis/commands/set/sscan.md): Incrementally iterate set members.
+- [SUNION](https://upstash.com/docs/redis/commands/set/sunion.md): Get set union.
+- [SUNIONSTORE](https://upstash.com/docs/redis/commands/set/sunionstore.md): Store set union.
+- [BZMPOP](https://upstash.com/docs/redis/commands/sorted-set/bzmpop.md): Pop from the first non-empty sorted set, blocking until one arrives.
+- [BZPOPMAX](https://upstash.com/docs/redis/commands/sorted-set/bzpopmax.md): Pop the highest-scoring member, blocking until one arrives.
+- [BZPOPMIN](https://upstash.com/docs/redis/commands/sorted-set/bzpopmin.md): Pop the lowest-scoring member, blocking until one arrives.
+- [Sorted Set commands](https://upstash.com/docs/redis/commands/sorted-set/overview.md): Commands for storing and manipulating scored collections.
+- [ZADD](https://upstash.com/docs/redis/commands/sorted-set/zadd.md): Add members with scores.
+- [ZCARD](https://upstash.com/docs/redis/commands/sorted-set/zcard.md): Get sorted set cardinality.
+- [ZCOUNT](https://upstash.com/docs/redis/commands/sorted-set/zcount.md): Count members in score range.
+- [ZDIFF](https://upstash.com/docs/redis/commands/sorted-set/zdiff.md): Get sorted set difference.
+- [ZDIFFSTORE](https://upstash.com/docs/redis/commands/sorted-set/zdiffstore.md): Store sorted set difference.
+- [ZINCRBY](https://upstash.com/docs/redis/commands/sorted-set/zincrby.md): Increment member's score.
+- [ZINTER](https://upstash.com/docs/redis/commands/sorted-set/zinter.md): Get sorted set intersection.
+- [ZINTERCARD](https://upstash.com/docs/redis/commands/sorted-set/zintercard.md): Get intersection cardinality.
+- [ZINTERSTORE](https://upstash.com/docs/redis/commands/sorted-set/zinterstore.md): Store sorted set intersection.
+- [ZLEXCOUNT](https://upstash.com/docs/redis/commands/sorted-set/zlexcount.md): Count members in lex range.
+- [ZMPOP](https://upstash.com/docs/redis/commands/sorted-set/zmpop.md): Pop members from sorted sets.
+- [ZMSCORE](https://upstash.com/docs/redis/commands/sorted-set/zmscore.md): Get scores of multiple members.
+- [ZPOPMAX](https://upstash.com/docs/redis/commands/sorted-set/zpopmax.md): Pop members with highest scores.
+- [ZPOPMIN](https://upstash.com/docs/redis/commands/sorted-set/zpopmin.md): Pop members with lowest scores.
+- [ZRANDMEMBER](https://upstash.com/docs/redis/commands/sorted-set/zrandmember.md): Get random members.
+- [ZRANGE](https://upstash.com/docs/redis/commands/sorted-set/zrange.md): Get members by index range.
+- [ZRANGEBYLEX](https://upstash.com/docs/redis/commands/sorted-set/zrangebylex.md): Get members by lex range.
+- [ZRANGEBYSCORE](https://upstash.com/docs/redis/commands/sorted-set/zrangebyscore.md): Get members by score range.
+- [ZRANGESTORE](https://upstash.com/docs/redis/commands/sorted-set/zrangestore.md): Store range result.
+- [ZRANK](https://upstash.com/docs/redis/commands/sorted-set/zrank.md): Get member's rank.
+- [ZREM](https://upstash.com/docs/redis/commands/sorted-set/zrem.md): Remove members.
+- [ZREMRANGEBYLEX](https://upstash.com/docs/redis/commands/sorted-set/zremrangebylex.md): Remove members by lex range.
+- [ZREMRANGEBYRANK](https://upstash.com/docs/redis/commands/sorted-set/zremrangebyrank.md): Remove members by rank range.
+- [ZREMRANGEBYSCORE](https://upstash.com/docs/redis/commands/sorted-set/zremrangebyscore.md): Remove members by score range.
+- [ZREVRANGE](https://upstash.com/docs/redis/commands/sorted-set/zrevrange.md): Get members in reverse order.
+- [ZREVRANGEBYLEX](https://upstash.com/docs/redis/commands/sorted-set/zrevrangebylex.md): List members in a lexicographic range, in reverse order.
+- [ZREVRANGEBYSCORE](https://upstash.com/docs/redis/commands/sorted-set/zrevrangebyscore.md): List members in a score range, highest score first.
+- [ZREVRANK](https://upstash.com/docs/redis/commands/sorted-set/zrevrank.md): Get member's reverse rank.
+- [ZSCAN](https://upstash.com/docs/redis/commands/sorted-set/zscan.md): Incrementally iterate sorted set.
+- [ZSCORE](https://upstash.com/docs/redis/commands/sorted-set/zscore.md): Get member's score.
+- [ZUNION](https://upstash.com/docs/redis/commands/sorted-set/zunion.md): Get sorted set union.
+- [ZUNIONSTORE](https://upstash.com/docs/redis/commands/sorted-set/zunionstore.md): Store sorted set union.
+- [Streams commands](https://upstash.com/docs/redis/commands/streams/overview.md): Commands for append-only logs, consumer groups, and message processing.
+- [XACK](https://upstash.com/docs/redis/commands/streams/xack.md): Acknowledge stream messages.
+- [XACKDEL](https://upstash.com/docs/redis/commands/streams/xackdel.md): Acknowledge and delete messages.
+- [XADD](https://upstash.com/docs/redis/commands/streams/xadd.md): Add entry to stream.
+- [XAUTOCLAIM](https://upstash.com/docs/redis/commands/streams/xautoclaim.md): Auto-claim idle messages.
+- [XCLAIM](https://upstash.com/docs/redis/commands/streams/xclaim.md): Claim pending messages.
+- [XDEL](https://upstash.com/docs/redis/commands/streams/xdel.md): Delete stream entries.
+- [XDELEX](https://upstash.com/docs/redis/commands/streams/xdelex.md): Delete entries with expiration.
+- [XGROUP](https://upstash.com/docs/redis/commands/streams/xgroup.md): Manage consumer groups.
+- [XINFO CONSUMERS](https://upstash.com/docs/redis/commands/streams/xinfo-consumers.md): List group consumers.
+- [XINFO GROUPS](https://upstash.com/docs/redis/commands/streams/xinfo-groups.md): List stream groups.
+- [XINFO STREAM](https://upstash.com/docs/redis/commands/streams/xinfo-stream.md): Get stream info.
+- [XLEN](https://upstash.com/docs/redis/commands/streams/xlen.md): Get stream length.
+- [XPENDING](https://upstash.com/docs/redis/commands/streams/xpending.md): Get pending messages info.
+- [XRANGE](https://upstash.com/docs/redis/commands/streams/xrange.md): Get range of stream entries.
+- [XREAD](https://upstash.com/docs/redis/commands/streams/xread.md): Read stream entries.
+- [XREADGROUP](https://upstash.com/docs/redis/commands/streams/xreadgroup.md): Read as consumer group.
+- [XREVRANGE](https://upstash.com/docs/redis/commands/streams/xrevrange.md): Get range in reverse order.
+- [XTRIM](https://upstash.com/docs/redis/commands/streams/xtrim.md): Trim stream to max length.
+- [APPEND](https://upstash.com/docs/redis/commands/string/append.md): Append value to a string.
+- [DECR](https://upstash.com/docs/redis/commands/string/decr.md): Decrement integer value by 1.
+- [DECRBY](https://upstash.com/docs/redis/commands/string/decrby.md): Decrement integer by amount.
+- [DELEX](https://upstash.com/docs/redis/commands/string/delex.md): Delete a string when a condition matches.
+- [DIGEST](https://upstash.com/docs/redis/commands/string/digest.md): Get the digest of a string value.
+- [GET](https://upstash.com/docs/redis/commands/string/get.md): Get string value.
+- [GETDEL](https://upstash.com/docs/redis/commands/string/getdel.md): Get value and delete key.
+- [GETEX](https://upstash.com/docs/redis/commands/string/getex.md): Get value and set expiration.
+- [GETRANGE](https://upstash.com/docs/redis/commands/string/getrange.md): Get substring of string.
+- [GETSET](https://upstash.com/docs/redis/commands/string/getset.md): Set value and return old value.
+- [INCR](https://upstash.com/docs/redis/commands/string/incr.md): Increment integer value by 1.
+- [INCRBY](https://upstash.com/docs/redis/commands/string/incrby.md): Increment integer by amount.
+- [INCRBYFLOAT](https://upstash.com/docs/redis/commands/string/incrbyfloat.md): Increment float by amount.
+- [MGET](https://upstash.com/docs/redis/commands/string/mget.md): Get values of multiple keys.
+- [MSET](https://upstash.com/docs/redis/commands/string/mset.md): Set multiple keys at once.
+- [MSETNX](https://upstash.com/docs/redis/commands/string/msetnx.md): Set multiple keys if none exist.
+- [String commands](https://upstash.com/docs/redis/commands/string/overview.md): Commands for storing and manipulating string values.
+- [PSETEX](https://upstash.com/docs/redis/commands/string/psetex.md): Set value with ms expiration.
+- [SET](https://upstash.com/docs/redis/commands/string/set.md): Set string value.
+- [SETEX](https://upstash.com/docs/redis/commands/string/setex.md): Set value with expiration.
+- [SETNX](https://upstash.com/docs/redis/commands/string/setnx.md): Set value if key doesn't exist.
+- [SETRANGE](https://upstash.com/docs/redis/commands/string/setrange.md): Overwrite part of string.
+- [STRLEN](https://upstash.com/docs/redis/commands/string/strlen.md): Get string length.
+- [DISCARD](https://upstash.com/docs/redis/commands/transactions/discard.md): Discard queued commands.
+- [EXEC](https://upstash.com/docs/redis/commands/transactions/exec.md): Execute queued commands.
+- [MULTI](https://upstash.com/docs/redis/commands/transactions/multi.md): Start a transaction.
+- [Transactions commands](https://upstash.com/docs/redis/commands/transactions/overview.md): Commands for grouping operations into atomic transactions.
+- [UNWATCH](https://upstash.com/docs/redis/commands/transactions/unwatch.md): Unwatch all keys.
+- [WATCH](https://upstash.com/docs/redis/commands/transactions/watch.md): Watch keys for changes.
 - [Auto Upgrade](https://upstash.com/docs/redis/features/auto-upgrade.md)
 - [Backup/Restore](https://upstash.com/docs/redis/features/backup.md)
 - [Consistency](https://upstash.com/docs/redis/features/consistency.md)
@@ -779,7 +1071,7 @@
 - [$sum](https://upstash.com/docs/redis/search/aggregation-operators/metric-aggregations/sum.md)
 - [Aggregations](https://upstash.com/docs/redis/search/aggregations.md)
 - [Aliases](https://upstash.com/docs/redis/search/aliases.md)
-- [Command Reference](https://upstash.com/docs/redis/search/command-reference.md)
+- [Command Reference](https://upstash.com/docs/redis/search/command-reference.md): Browse the commands supported by Upstash Redis Search.
 - [Counting](https://upstash.com/docs/redis/search/counting.md)
 - [Document Updates](https://upstash.com/docs/redis/search/document-updates.md)
 - [Quickstart](https://upstash.com/docs/redis/search/getting-started.md)
diff --git a/redis/commands/bitmap/bitcount.mdx b/redis/commands/bitmap/bitcount.mdx
new file mode 100644
index 000000000..793810c34
--- /dev/null
+++ b/redis/commands/bitmap/bitcount.mdx
@@ -0,0 +1,165 @@
+---
+title: "BITCOUNT"
+description: "Count set bits in a string."
+---
+
+Use `BITCOUNT` to count set bits in a string.
+
+## Syntax
+
+```redis
+BITCOUNT <key> [<start> <end> [BYTE | BIT]]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<start> <end> [BYTE \| BIT]` | No | No | Range to count. Offsets are byte-based unless `BIT` is given; negative offsets count from the end. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const bits = await redis.bitcount(key);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.bitcount("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.bitcount("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.bitCount("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.bitcount("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.BitCount(context.Background(), "my-key", nil).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.bitcount("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.bitcount("my-key")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/bitmap/bitfield-ro.mdx b/redis/commands/bitmap/bitfield-ro.mdx
new file mode 100644
index 000000000..0179345d4
--- /dev/null
+++ b/redis/commands/bitmap/bitfield-ro.mdx
@@ -0,0 +1,161 @@
+---
+title: "BITFIELD_RO"
+description: "Read bitfield values."
+---
+
+Use `BITFIELD_RO` to read one or more bitfield values without modifying the key.
+
+## Syntax
+
+```redis
+BITFIELD_RO <key> [GET <encoding> <offset> [GET <encoding> <offset> ...]]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `GET <encoding> <offset>` | No | Yes | Read the value at `<offset>` using `<encoding>`, such as `u8` or `i16`. Repeat to read several fields. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of integer or null replies, one per subcommand |
+| RESP3 | Array of integer or null replies, one per subcommand |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.bitfield_ro("my-key").get("u8", 0).execute()
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.bitfield_ro("my-key", "GET", "u8", "0");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.bitFieldRo("my-key", [{ encoding: "u8", offset: 0 }]);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.bitfield_ro("my-key", "u8", 0)
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.BitFieldRO(context.Background(), "my-key", "GET", "u8", 0).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.bitfieldReadonly("my-key", "GET", "u8", "0");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("BITFIELD_RO");
+    command.arg("my-key");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/bitmap/bitfield.mdx b/redis/commands/bitmap/bitfield.mdx
new file mode 100644
index 000000000..e12bc38ee
--- /dev/null
+++ b/redis/commands/bitmap/bitfield.mdx
@@ -0,0 +1,165 @@
+---
+title: "BITFIELD"
+description: "Perform arbitrary bitfield operations."
+---
+
+Use `BITFIELD` to perform arbitrary bitfield operations.
+
+## Syntax
+
+```redis
+BITFIELD <key> [GET <encoding> <offset> | [OVERFLOW WRAP | SAT | FAIL] (SET <encoding> <offset> <value> | INCRBY <encoding> <offset> <increment>) [GET <encoding> <offset> | [OVERFLOW WRAP | SAT | FAIL] (SET <encoding> <offset> <value> | INCRBY <encoding> <offset> <increment>) ...]]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `(GET <encoding> <offset> \| [OVERFLOW WRAP \| SAT \| FAIL] (SET <encoding> <offset> <value> \| INCRBY <encoding> <offset> <increment>))` | No | Yes | Choose one form: `GET` (also return the previous value); `OVERFLOW`; `WRAP`; `SAT`; `FAIL`; `SET`; `INCRBY`. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of integer or null replies, one per subcommand |
+| RESP3 | Array of integer or null replies, one per subcommand |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+const result = await redis.bitfield("my-key").get("u8", 0).exec();
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.bitfield("my-key").get("u8", 0).execute()
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.bitfield("my-key", "GET", "u8", "0");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.bitField("my-key", [{ operation: "GET", encoding: "u8", offset: 0 }]);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.bitfield("my-key").get("u8", 0).execute()
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.BitField(context.Background(), "my-key", "GET", "u8", 0).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.bitfield("my-key", "GET", "u8", "0");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("BITFIELD");
+    command.arg("my-key");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/bitmap/bitop.mdx b/redis/commands/bitmap/bitop.mdx
new file mode 100644
index 000000000..1e5c04557
--- /dev/null
+++ b/redis/commands/bitmap/bitop.mdx
@@ -0,0 +1,176 @@
+---
+title: "BITOP"
+description: "Perform bitwise operations between strings."
+---
+
+Use `BITOP` to perform bitwise operations between strings.
+
+## Syntax
+
+```redis
+BITOP (AND | OR | XOR | NOT | DIFF | DIFF1 | ANDOR | ONE) <destkey> <key> [<key> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `(AND \| OR \| XOR \| NOT \| DIFF \| DIFF1 \| ANDOR \| ONE)` | Yes | No | Choose one form: `AND`; `OR`; `XOR`; `NOT`; `DIFF`; `DIFF1`; `ANDOR`; `ONE`. |
+| `<destkey>` | Yes | No | Redis key used as destkey. |
+| `<key>` | Yes | Yes | Redis key targeted by the command. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+// AND operation
+await redis.bitop("and", "destKey", "sourceKey1", "sourceKey2");
+
+// OR operation
+await redis.bitop("or", "destKey", "sourceKey1", "sourceKey2");
+
+// XOR operation
+await redis.bitop("xor", "destKey", "sourceKey1", "sourceKey2");
+
+// NOT operation (only accepts one source key)
+await redis.bitop("not", "destKey", "sourceKey");
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.bitop("AND", "destination-key", "source-key-1", "source-key-2")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.bitop("AND", "destination-key", "source-key-1", "source-key-2");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.bitOp("AND", "destination-key", ["source-key-1", "source-key-2"]);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.bitop("AND", "destination-key", "source-key-1", "source-key-2")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.BitOpAnd(context.Background(), "destination-key", "source-key-1", "source-key-2").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.bitop(redis.clients.jedis.args.BitOP.AND, "destination-key", "source-key-1", "source-key-2");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.bit_and("destination-key", &["source-key-1", "source-key-2"])?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/bitmap/bitpos.mdx b/redis/commands/bitmap/bitpos.mdx
new file mode 100644
index 000000000..e8beb24be
--- /dev/null
+++ b/redis/commands/bitmap/bitpos.mdx
@@ -0,0 +1,167 @@
+---
+title: "BITPOS"
+description: "Find first bit set or clear in a string."
+---
+
+Use `BITPOS` to find first bit set or clear in a string.
+
+## Syntax
+
+```redis
+BITPOS <key> <bit> [<start> [<end> [BYTE | BIT]]]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<bit>` | Yes | No | Bit value to look for: `0` or `1`. |
+| `<start> [<end> [BYTE \| BIT]]` | No | No | Range to search. Offsets are byte-based unless `BIT` is given; negative offsets count from the end. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer: the position of the first matching bit, or `-1` |
+| RESP3 | Integer: the position of the first matching bit, or `-1` |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.bitpos("key", 1);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.bitpos("my-key", 1)
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.bitpos("my-key", "1");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.bitPos("my-key", 1);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.bitpos("my-key", 1)
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.BitPos(context.Background(), "my-key", 1).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.bitpos("my-key", true);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("BITPOS");
+    command.arg("my-key");
+    command.arg("1");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/bitmap/getbit.mdx b/redis/commands/bitmap/getbit.mdx
new file mode 100644
index 000000000..0d73d6622
--- /dev/null
+++ b/redis/commands/bitmap/getbit.mdx
@@ -0,0 +1,165 @@
+---
+title: "GETBIT"
+description: "Get the bit value at offset."
+---
+
+Use `GETBIT` to get the bit value at offset.
+
+## Syntax
+
+```redis
+GETBIT <key> <offset>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<offset>` | Yes | No | Zero-based bit offset to read. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer: the bit at the offset, `0` or `1` |
+| RESP3 | Integer: the bit at the offset, `0` or `1` |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const bit = await redis.getbit(key, 4);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.getbit("my-key", 0)
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.getbit("my-key", "0");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.getBit("my-key", 0);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.getbit("my-key", 0)
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.GetBit(context.Background(), "my-key", 0).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.getbit("my-key", 0);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.getbit("my-key", 0)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/bitmap/overview.mdx b/redis/commands/bitmap/overview.mdx
new file mode 100644
index 000000000..b7cae8297
--- /dev/null
+++ b/redis/commands/bitmap/overview.mdx
@@ -0,0 +1,16 @@
+---
+title: "Bitmap commands"
+sidebarTitle: "Overview"
+description: "Commands for manipulating individual bits and bit fields in string values."
+---
+
+<CardGroup cols={2}>
+<Card title="BITCOUNT" href="/redis/commands/bitmap/bitcount">Count set bits in a string</Card>
+<Card title="BITFIELD" href="/redis/commands/bitmap/bitfield">Perform arbitrary bitfield operations</Card>
+<Card title="BITFIELD_RO" href="/redis/commands/bitmap/bitfield-ro">Read-only bitfield operations</Card>
+<Card title="BITOP" href="/redis/commands/bitmap/bitop">Perform bitwise operations between strings</Card>
+<Card title="BITPOS" href="/redis/commands/bitmap/bitpos">Find first bit set or clear in a string</Card>
+<Card title="GETBIT" href="/redis/commands/bitmap/getbit">Get the bit value at offset</Card>
+<Card title="SETBIT" href="/redis/commands/bitmap/setbit">Set or clear the bit at offset</Card>
+</CardGroup>
+
diff --git a/redis/commands/bitmap/setbit.mdx b/redis/commands/bitmap/setbit.mdx
new file mode 100644
index 000000000..a3d97c3d8
--- /dev/null
+++ b/redis/commands/bitmap/setbit.mdx
@@ -0,0 +1,166 @@
+---
+title: "SETBIT"
+description: "Set or clear the bit at offset."
+---
+
+Use `SETBIT` to set or clear the bit at offset.
+
+## Syntax
+
+```redis
+SETBIT <key> <offset> <value>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<offset>` | Yes | No | Zero-based bit offset to write. |
+| `<value>` | Yes | No | Bit value to write: `0` or `1`. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer: the previous bit at the offset, `0` or `1` |
+| RESP3 | Integer: the previous bit at the offset, `0` or `1` |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const originalBit = await redis.setbit(key, 4, 1);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.setbit("my-key", 0, 1)
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.setbit("my-key", "0", "1");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.setBit("my-key", 0, 1);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.setbit("my-key", 0, 1)
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.SetBit(context.Background(), "my-key", 0, 1).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.setbit("my-key", 0, true);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.setbit("my-key", 0, true)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/connection/auth.mdx b/redis/commands/connection/auth.mdx
new file mode 100644
index 000000000..3f5703501
--- /dev/null
+++ b/redis/commands/connection/auth.mdx
@@ -0,0 +1,145 @@
+---
+title: "AUTH"
+description: "Authenticate to the server."
+---
+
+Use `AUTH` to authenticate to the server.
+
+## Syntax
+
+```redis
+AUTH [<username>] <password>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<username>` | No | No | Username to authenticate as. |
+| `<password>` | Yes | No | Password to authenticate with. |
+
+## Important points
+
+- This is a connection-oriented command and is available over native Redis TCP, not the stateless REST endpoint.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Simple string `OK` |
+| RESP3 | Simple string `OK` |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.auth("password");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.auth({ password: "password" });
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.auth("password")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.Do(context.Background(), "AUTH", "password").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.auth("password");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("AUTH");
+    command.arg("password");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/connection/client-getname.mdx b/redis/commands/connection/client-getname.mdx
new file mode 100644
index 000000000..32e97c21e
--- /dev/null
+++ b/redis/commands/connection/client-getname.mdx
@@ -0,0 +1,143 @@
+---
+title: "CLIENT GETNAME"
+description: "Get the current connection name."
+---
+
+Use `CLIENT GETNAME` to get the current connection name.
+
+## Syntax
+
+```redis
+CLIENT GETNAME
+```
+
+## Arguments
+
+This command takes no arguments.
+
+## Important points
+
+- This is a connection-oriented command and is available over native Redis TCP, not the stateless REST endpoint.
+- This command can expose administrative information or make a broad destructive change. Restrict it to trusted code paths.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Null bulk string or null array or Bulk string |
+| RESP3 | Null or Bulk string |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.client("GETNAME");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.clientGetName();
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.client_getname()
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ClientGetName(context.Background()).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.clientGetname();
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("CLIENT");
+    command.arg("GETNAME");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/connection/client-id.mdx b/redis/commands/connection/client-id.mdx
new file mode 100644
index 000000000..11ea63524
--- /dev/null
+++ b/redis/commands/connection/client-id.mdx
@@ -0,0 +1,143 @@
+---
+title: "CLIENT ID"
+description: "Get the current client ID."
+---
+
+Use `CLIENT ID` to get the current client ID.
+
+## Syntax
+
+```redis
+CLIENT ID
+```
+
+## Arguments
+
+This command takes no arguments.
+
+## Important points
+
+- This is a connection-oriented command and is available over native Redis TCP, not the stateless REST endpoint.
+- This command can expose administrative information or make a broad destructive change. Restrict it to trusted code paths.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.client("ID");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.clientId();
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.client_id()
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ClientID(context.Background()).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.clientId();
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("CLIENT");
+    command.arg("ID");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/connection/client-info.mdx b/redis/commands/connection/client-info.mdx
new file mode 100644
index 000000000..a180fed2e
--- /dev/null
+++ b/redis/commands/connection/client-info.mdx
@@ -0,0 +1,143 @@
+---
+title: "CLIENT INFO"
+description: "Get info about current connection."
+---
+
+Use `CLIENT INFO` to get info about current connection.
+
+## Syntax
+
+```redis
+CLIENT INFO
+```
+
+## Arguments
+
+This command takes no arguments.
+
+## Important points
+
+- This is a connection-oriented command and is available over native Redis TCP, not the stateless REST endpoint.
+- This command can expose administrative information or make a broad destructive change. Restrict it to trusted code paths.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Bulk string |
+| RESP3 | Bulk string |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.client("INFO");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.clientInfo();
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.client_info()
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ClientInfo(context.Background()).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.clientInfo();
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("CLIENT");
+    command.arg("INFO");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/connection/client-list.mdx b/redis/commands/connection/client-list.mdx
new file mode 100644
index 000000000..de5274532
--- /dev/null
+++ b/redis/commands/connection/client-list.mdx
@@ -0,0 +1,143 @@
+---
+title: "CLIENT LIST"
+description: "List all client connections."
+---
+
+Use `CLIENT LIST` to list all client connections.
+
+## Syntax
+
+```redis
+CLIENT LIST
+```
+
+## Arguments
+
+This command takes no arguments.
+
+## Important points
+
+- This is a connection-oriented command and is available over native Redis TCP, not the stateless REST endpoint.
+- This command can expose administrative information or make a broad destructive change. Restrict it to trusted code paths.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Bulk string |
+| RESP3 | Bulk string |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.client("LIST");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.clientList();
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.client_list()
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ClientList(context.Background()).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.clientList();
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("CLIENT");
+    command.arg("LIST");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/connection/client-setinfo.mdx b/redis/commands/connection/client-setinfo.mdx
new file mode 100644
index 000000000..4bad31206
--- /dev/null
+++ b/redis/commands/connection/client-setinfo.mdx
@@ -0,0 +1,148 @@
+---
+title: "CLIENT SETINFO"
+description: "Set client connection attributes."
+---
+
+Use `CLIENT SETINFO` to set client connection attributes.
+
+## Syntax
+
+```redis
+CLIENT SETINFO <LIB-NAME | LIB-VER> <value>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `LIB-NAME \| LIB-VER` | Yes | No | Attribute to update: the client library name or version. |
+| `value` | Yes | No | Value to store for the selected client attribute. |
+
+## Important points
+
+- This is a connection-oriented command and is available over native Redis TCP, not the stateless REST endpoint.
+- This command can expose administrative information or make a broad destructive change. Restrict it to trusted code paths.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Simple string `OK` |
+| RESP3 | Simple string `OK` |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.call("CLIENT", "SETINFO", "LIB-NAME", "my-client");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.sendCommand(["CLIENT", "SETINFO", "LIB-NAME", "my-client"]);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.client_setinfo("LIB-NAME", "my-client")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.Do(context.Background(), "CLIENT", "SETINFO", "LIB-NAME", "my-client").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.clientSetInfo(redis.clients.jedis.args.ClientAttributeOption.LIB_NAME, "my-client");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("CLIENT");
+    command.arg("SETINFO");
+    command.arg("LIB-NAME");
+    command.arg("my-client");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/connection/client-setname.mdx b/redis/commands/connection/client-setname.mdx
new file mode 100644
index 000000000..8b185018e
--- /dev/null
+++ b/redis/commands/connection/client-setname.mdx
@@ -0,0 +1,146 @@
+---
+title: "CLIENT SETNAME"
+description: "Set the connection name."
+---
+
+Use `CLIENT SETNAME` to set the connection name.
+
+## Syntax
+
+```redis
+CLIENT SETNAME <connection-name>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `connection-name` | Yes | No | Name to associate with this TCP connection. |
+
+## Important points
+
+- This is a connection-oriented command and is available over native Redis TCP, not the stateless REST endpoint.
+- This command can expose administrative information or make a broad destructive change. Restrict it to trusted code paths.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Simple string `OK` |
+| RESP3 | Simple string `OK` |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.client("SETNAME", "worker-1");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.clientSetName("worker-1");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.client_setname("worker-1")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.Do(context.Background(), "CLIENT", "SETNAME", "worker-1").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.clientSetname("worker-1");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("CLIENT");
+    command.arg("SETNAME");
+    command.arg("worker-1");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/connection/echo.mdx b/redis/commands/connection/echo.mdx
new file mode 100644
index 000000000..2e417157b
--- /dev/null
+++ b/redis/commands/connection/echo.mdx
@@ -0,0 +1,165 @@
+---
+title: "ECHO"
+description: "Echo the given string."
+---
+
+Use `ECHO` to echo the given string.
+
+## Syntax
+
+```redis
+ECHO <message>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<message>` | Yes | No | Message payload. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Bulk string |
+| RESP3 | Bulk string |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const response = await redis.echo("hello world");
+console.log(response); // "hello world"
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.echo("hello")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.echo("hello");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.echo("hello");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.echo("hello")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.Echo(context.Background(), "hello").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.echo("hello");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("ECHO");
+    command.arg("hello");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/connection/hello.mdx b/redis/commands/connection/hello.mdx
new file mode 100644
index 000000000..bda81e58a
--- /dev/null
+++ b/redis/commands/connection/hello.mdx
@@ -0,0 +1,146 @@
+---
+title: "HELLO"
+description: "Handshake with Redis protocol."
+---
+
+Use `HELLO` to handshake with Redis protocol.
+
+## Syntax
+
+```redis
+HELLO [<protover> [AUTH <username> <password>] [SETNAME <clientname>]]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<protover> [AUTH <username> <password>] [SETNAME <clientname>]` | No | No | Protocol version to switch to, optionally with credentials and a connection name. |
+
+## Important points
+
+- This is a connection-oriented command and is available over native Redis TCP, not the stateless REST endpoint.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Flat array of alternating keys and values |
+| RESP3 | Map |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.hello();
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.hello();
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.hello()
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.Do(context.Background(), "HELLO").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+import java.nio.charset.StandardCharsets;
+import redis.clients.jedis.Jedis;
+import redis.clients.jedis.commands.ProtocolCommand;
+
+ProtocolCommand command = () -> "HELLO".getBytes(StandardCharsets.UTF_8);
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.sendCommand(command);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("HELLO");
+
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/connection/overview.mdx b/redis/commands/connection/overview.mdx
new file mode 100644
index 000000000..d9b1254fa
--- /dev/null
+++ b/redis/commands/connection/overview.mdx
@@ -0,0 +1,22 @@
+---
+title: "Connection commands"
+sidebarTitle: "Overview"
+description: "Commands for authenticating, inspecting, and managing client connections."
+---
+
+<CardGroup cols={2}>
+<Card title="AUTH" href="/redis/commands/connection/auth">Authenticate to the server</Card>
+<Card title="CLIENT GETNAME" href="/redis/commands/connection/client-getname">Get the current connection name</Card>
+<Card title="CLIENT ID" href="/redis/commands/connection/client-id">Get the current client ID</Card>
+<Card title="CLIENT INFO" href="/redis/commands/connection/client-info">Get info about current connection</Card>
+<Card title="CLIENT LIST" href="/redis/commands/connection/client-list">List all client connections</Card>
+<Card title="CLIENT SETINFO" href="/redis/commands/connection/client-setinfo">Set client connection attributes</Card>
+<Card title="CLIENT SETNAME" href="/redis/commands/connection/client-setname">Set the connection name</Card>
+<Card title="ECHO" href="/redis/commands/connection/echo">Echo the given string</Card>
+<Card title="HELLO" href="/redis/commands/connection/hello">Handshake with Redis protocol</Card>
+<Card title="PING" href="/redis/commands/connection/ping">Ping the server</Card>
+<Card title="QUIT" href="/redis/commands/connection/quit">Close the connection</Card>
+<Card title="RESET" href="/redis/commands/connection/reset">Reset the connection</Card>
+<Card title="SELECT" href="/redis/commands/connection/select">Select the database by index</Card>
+</CardGroup>
+
diff --git a/redis/commands/connection/ping.mdx b/redis/commands/connection/ping.mdx
new file mode 100644
index 000000000..f36ea01ba
--- /dev/null
+++ b/redis/commands/connection/ping.mdx
@@ -0,0 +1,170 @@
+---
+title: "PING"
+description: "Ping the server."
+---
+
+Use `PING` to ping the server.
+
+## Syntax
+
+```redis
+PING [<message>]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<message>` | No | No | Message payload. |
+
+## Important points
+
+- Without arguments the reply is `PONG`; with a message, the message is echoed back as a bulk string.
+- While the connection is subscribed under RESP2, `PING` replies with a two-element array holding `pong` and the message instead.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Simple string `PONG`, or the message as a bulk string; a two-element `pong`/message array while subscribed |
+| RESP3 | Simple string `PONG`, or the message as a bulk string |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const response = await redis.ping();
+console.log(response); // "PONG"
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.ping()
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.ping();
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.ping();
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.ping()
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.Ping(context.Background()).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.ping();
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("PING");
+
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/connection/quit.mdx b/redis/commands/connection/quit.mdx
new file mode 100644
index 000000000..4dd30581b
--- /dev/null
+++ b/redis/commands/connection/quit.mdx
@@ -0,0 +1,144 @@
+---
+title: "QUIT"
+description: "Close the connection."
+---
+
+Use `QUIT` to close the connection.
+
+## Syntax
+
+```redis
+QUIT
+```
+
+## Arguments
+
+This command takes no arguments.
+
+## Important points
+
+- This is a connection-oriented command and is available over native Redis TCP, not the stateless REST endpoint.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Simple string `OK` |
+| RESP3 | Simple string `OK` |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.quit();
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.sendCommand(["QUIT"]);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.quit()
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.Quit(context.Background()).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+import java.nio.charset.StandardCharsets;
+import redis.clients.jedis.Jedis;
+import redis.clients.jedis.commands.ProtocolCommand;
+
+ProtocolCommand command = () -> "QUIT".getBytes(StandardCharsets.UTF_8);
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.sendCommand(command);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("QUIT");
+
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/connection/reset.mdx b/redis/commands/connection/reset.mdx
new file mode 100644
index 000000000..17f351773
--- /dev/null
+++ b/redis/commands/connection/reset.mdx
@@ -0,0 +1,142 @@
+---
+title: "RESET"
+description: "Reset the connection."
+---
+
+Use `RESET` to reset the connection.
+
+## Syntax
+
+```redis
+RESET
+```
+
+## Arguments
+
+This command takes no arguments.
+
+## Important points
+
+- This is a connection-oriented command and is available over native Redis TCP, not the stateless REST endpoint.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Simple string `RESET` |
+| RESP3 | Simple string `RESET` |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.reset();
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.sendCommand(["RESET"]);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.reset()
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.Do(context.Background(), "RESET").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.reset();
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("RESET");
+
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/connection/select.mdx b/redis/commands/connection/select.mdx
new file mode 100644
index 000000000..b442bc6a1
--- /dev/null
+++ b/redis/commands/connection/select.mdx
@@ -0,0 +1,160 @@
+---
+title: "SELECT"
+description: "Select the database by index."
+---
+
+Use `SELECT` to select the database by index.
+
+## Syntax
+
+```redis
+SELECT 0
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `0` | Yes | No | Database index. Upstash supports only database 0. |
+
+## Important points
+
+- Upstash exposes a single logical database. Any index other than `0` returns an error.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Simple string `OK` |
+| RESP3 | Simple string `OK` |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+<Note>
+  This command is not supported yet in `upstash_redis`.
+</Note>
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.select("0");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.sendCommand(["SELECT", "0"]);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.select("0")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.Do(context.Background(), "SELECT", "0").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.select(0);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("SELECT");
+    command.arg("0");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/functions/fcall-ro.mdx b/redis/commands/functions/fcall-ro.mdx
new file mode 100644
index 000000000..008e0055c
--- /dev/null
+++ b/redis/commands/functions/fcall-ro.mdx
@@ -0,0 +1,187 @@
+---
+title: "FCALL_RO"
+description: "Call a read-only function."
+---
+
+Use `FCALL_RO` to call a read-only function.
+
+## Syntax
+
+```redis
+FCALL_RO <function> <numkeys> [<key> [<key> ...]] [<arg> [<arg> ...]]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<function>` | Yes | No | Name of the registered function to call. |
+| `<numkeys>` | Yes | No | Number of key arguments that follow. |
+| `<key>` | No | Yes | Redis key targeted by the command. |
+| `<arg>` | No | Yes | Additional argument passed to the function. |
+
+## Important points
+
+- `numkeys` must equal the number of key arguments that immediately follow it; remaining arguments are available to the script or function as ordinary arguments.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Reply returned by the invoked read-only function |
+| RESP3 | Reply returned by the invoked read-only function |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const code = `
+#!lua name=ro_lib
+
+local function get_value(keys, args)
+  return redis.call('GET', keys[1])
+end
+
+redis.register_function({
+  function_name='get_value',
+  callback=get_value,
+  flags={ 'no-writes' }
+})
+`;
+
+await redis.functions.load({ code, replace: true });
+
+// Call the read-only function
+// Note: We can modify the keys usage here, but since it represents a read-only operation
+// and we marked it with 'no-writes', it is safe to use callRo.
+const value = await redis.functions.callRo("get_value", ["mykey"])
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+<Note>
+  This command is not supported yet in `upstash_redis`.
+</Note>
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.fcall_ro("my_function", "1", "my-key", "value");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.fCallRo("my_function", { keys: ["my-key"], arguments: ["value"] });
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.fcall_ro("my_function", 1, "my-key", "value")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.FCallRO(context.Background(), "my_function", []string{"my-key"}, "value").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.fcallReadonly("my_function", java.util.List.of("my-key"), java.util.List.of("value"));
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("FCALL_RO");
+    command.arg("my_function");
+    command.arg("1");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/functions/fcall.mdx b/redis/commands/functions/fcall.mdx
new file mode 100644
index 000000000..8b38b129c
--- /dev/null
+++ b/redis/commands/functions/fcall.mdx
@@ -0,0 +1,180 @@
+---
+title: "FCALL"
+description: "Call a function."
+---
+
+Use `FCALL` to call a function.
+
+## Syntax
+
+```redis
+FCALL <function> <numkeys> [<key> [<key> ...]] [<arg> [<arg> ...]]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<function>` | Yes | No | Name of the registered function to call. |
+| `<numkeys>` | Yes | No | Number of key arguments that follow. |
+| `<key>` | No | Yes | Redis key targeted by the command. |
+| `<arg>` | No | Yes | Additional argument passed to the function. |
+
+## Important points
+
+- `numkeys` must equal the number of key arguments that immediately follow it; remaining arguments are available to the script or function as ordinary arguments.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Reply returned by the invoked function |
+| RESP3 | Reply returned by the invoked function |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const code = `
+#!lua name=mylib
+redis.register_function('helloworld',
+  function()
+    return 'Hello World!'
+  end
+)
+`;
+
+await redis.functions.load({ code, replace: true });
+
+const res = await redis.functions.call("helloworld");
+console.log(res); // "Hello World!"
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+<Note>
+  This command is not supported yet in `upstash_redis`.
+</Note>
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.fcall("my_function", "1", "my-key", "value");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.fCall("my_function", { keys: ["my-key"], arguments: ["value"] });
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.fcall("my_function", 1, "my-key", "value")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.FCall(context.Background(), "my_function", []string{"my-key"}, "value").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.fcall("my_function", java.util.List.of("my-key"), java.util.List.of("value"));
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("FCALL");
+    command.arg("my_function");
+    command.arg("1");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/functions/function-delete.mdx b/redis/commands/functions/function-delete.mdx
new file mode 100644
index 000000000..60b8938b5
--- /dev/null
+++ b/redis/commands/functions/function-delete.mdx
@@ -0,0 +1,161 @@
+---
+title: "FUNCTION DELETE"
+description: "Delete a library."
+---
+
+Use `FUNCTION DELETE` to delete a library.
+
+## Syntax
+
+```redis
+FUNCTION DELETE <library-name>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<library-name>` | Yes | No | Name of the function library. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Simple string `OK` |
+| RESP3 | Simple string `OK` |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.functions.delete("mylib")
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+<Note>
+  This command is not supported yet in `upstash_redis`.
+</Note>
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.function("DELETE", "library-name");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.functionDelete("library-name");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.function_delete("library-name")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.FunctionDelete(context.Background(), "library-name").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.functionDelete("library-name");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("FUNCTION");
+    command.arg("DELETE");
+    command.arg("library-name");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/functions/function-flush.mdx b/redis/commands/functions/function-flush.mdx
new file mode 100644
index 000000000..c772e84f9
--- /dev/null
+++ b/redis/commands/functions/function-flush.mdx
@@ -0,0 +1,160 @@
+---
+title: "FUNCTION FLUSH"
+description: "Delete all libraries."
+---
+
+Use `FUNCTION FLUSH` to delete all libraries.
+
+## Syntax
+
+```redis
+FUNCTION FLUSH [ASYNC | SYNC]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `(ASYNC \| SYNC)` | No | No | Choose one form: `ASYNC` (request asynchronous cleanup); `SYNC` (request synchronous cleanup). |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Simple string `OK` |
+| RESP3 | Simple string `OK` |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.functions.flush()
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+<Note>
+  This command is not supported yet in `upstash_redis`.
+</Note>
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.function("FLUSH");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.functionFlush();
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.function_flush()
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.FunctionFlush(context.Background()).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.functionFlush();
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("FUNCTION");
+    command.arg("FLUSH");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/functions/function-kill.mdx b/redis/commands/functions/function-kill.mdx
new file mode 100644
index 000000000..b788c9911
--- /dev/null
+++ b/redis/commands/functions/function-kill.mdx
@@ -0,0 +1,158 @@
+---
+title: "FUNCTION KILL"
+description: "Kill a running function."
+---
+
+Use `FUNCTION KILL` to kill a running function.
+
+## Syntax
+
+```redis
+FUNCTION KILL
+```
+
+## Arguments
+
+This command takes no arguments.
+
+## Important points
+
+- The current deployment recognizes this command but reports `NOTBUSY` because it does not expose an interruptible running-function state.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Error reply (`NOTBUSY` on the current deployment) |
+| RESP3 | Error reply (`NOTBUSY` on the current deployment) |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+<Note>
+  This command is not supported yet in `upstash_redis`.
+</Note>
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.function("KILL");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.functionKill();
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.function_kill()
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.FunctionKill(context.Background()).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.functionKill();
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("FUNCTION");
+    command.arg("KILL");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/functions/function-list.mdx b/redis/commands/functions/function-list.mdx
new file mode 100644
index 000000000..b094ddd50
--- /dev/null
+++ b/redis/commands/functions/function-list.mdx
@@ -0,0 +1,178 @@
+---
+title: "FUNCTION LIST"
+description: "List all libraries."
+---
+
+Use `FUNCTION LIST` to list all libraries.
+
+## Syntax
+
+```redis
+FUNCTION LIST [LIBRARYNAME <library-name-pattern>] [WITHCODE]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `LIBRARYNAME <library-name-pattern>` | No | No | Return only libraries whose name matches this pattern. |
+| `WITHCODE` | No | No | Include each library's source code. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of flat arrays containing library metadata |
+| RESP3 | Array of maps containing library metadata |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const libs = await redis.functions.list({
+    libraryName: "mylib",
+    withCode: true
+})
+
+console.log(libs)
+// [
+//   {
+//     libraryName: "mylib",
+//     engine: "LUA",
+//     functions: [{
+//       name: "my_func",
+//       description: null,
+//       flags: [ "no-writes" ]
+//     }],
+//     libraryCode: "#!lua name=mylib ..."
+//   }
+// ]
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+<Note>
+  This command is not supported yet in `upstash_redis`.
+</Note>
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.function("LIST");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.functionList();
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.function_list()
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.FunctionList(context.Background(), redis.FunctionListQuery{}).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.functionList();
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("FUNCTION");
+    command.arg("LIST");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/functions/function-load.mdx b/redis/commands/functions/function-load.mdx
new file mode 100644
index 000000000..03ddce3b7
--- /dev/null
+++ b/redis/commands/functions/function-load.mdx
@@ -0,0 +1,182 @@
+---
+title: "FUNCTION LOAD"
+description: "Load a library."
+---
+
+Use `FUNCTION LOAD` to load a library.
+
+## Syntax
+
+```redis
+FUNCTION LOAD [REPLACE] <function-code>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `REPLACE` | No | No | Allow replacement of an existing destination. |
+| `<function-code>` | Yes | No | Library source, including its `#!lua name=<library>` shebang. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Bulk string |
+| RESP3 | Bulk string |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const code = `#!lua name=mylib
+
+  -- Simple function that returns a string
+  redis.register_function(
+    'helloworld',
+    function() return 'Hello World!' end
+  )
+
+  -- Complex function that modifies data with logic
+  local function my_hset(keys, args)
+    local hash = keys[1]
+    local time = redis.call('TIME')[1]
+    return redis.call('HSET', hash, '_last_modified_', time, unpack(args))
+  end
+
+  redis.register_function('my_hset', my_hset)
+`;
+
+const libraryName = await redis.functions.load({ code, replace: true });
+
+console.log(libraryName); // "mylib"
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+<Note>
+  This command is not supported yet in `upstash_redis`.
+</Note>
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.function("LOAD", "function-code");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.functionLoad("function-code");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.function_load("function-code")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.FunctionLoad(context.Background(), "function-code").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.functionLoad("function-code");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("FUNCTION");
+    command.arg("LOAD");
+    command.arg("function-code");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/functions/function-stats.mdx b/redis/commands/functions/function-stats.mdx
new file mode 100644
index 000000000..343565af5
--- /dev/null
+++ b/redis/commands/functions/function-stats.mdx
@@ -0,0 +1,168 @@
+---
+title: "FUNCTION STATS"
+description: "Get function execution stats."
+---
+
+Use `FUNCTION STATS` to get function execution stats.
+
+## Syntax
+
+```redis
+FUNCTION STATS
+```
+
+## Arguments
+
+This command takes no arguments.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Flat array of alternating keys and values |
+| RESP3 | Map |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const stats = await redis.functions.stats()
+
+console.log(stats)
+// {
+//   engines: {
+//     LUA: {
+//       librariesCount: 3,
+//       functionsCount: 15
+//     }
+//   }
+// }
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+<Note>
+  This command is not supported yet in `upstash_redis`.
+</Note>
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.function("STATS");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.functionStats();
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.function_stats()
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.FunctionStats(context.Background()).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.functionStats();
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("FUNCTION");
+    command.arg("STATS");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/functions/overview.mdx b/redis/commands/functions/overview.mdx
new file mode 100644
index 000000000..8f0f517f6
--- /dev/null
+++ b/redis/commands/functions/overview.mdx
@@ -0,0 +1,17 @@
+---
+title: "Functions commands"
+sidebarTitle: "Overview"
+description: "Commands for loading, managing, and invoking Redis functions."
+---
+
+<CardGroup cols={2}>
+<Card title="FCALL" href="/redis/commands/functions/fcall">Call a function</Card>
+<Card title="FCALL_RO" href="/redis/commands/functions/fcall-ro">Call a read-only function</Card>
+<Card title="FUNCTION DELETE" href="/redis/commands/functions/function-delete">Delete a library</Card>
+<Card title="FUNCTION FLUSH" href="/redis/commands/functions/function-flush">Delete all libraries</Card>
+<Card title="FUNCTION KILL" href="/redis/commands/functions/function-kill">Kill a running function</Card>
+<Card title="FUNCTION LIST" href="/redis/commands/functions/function-list">List all libraries</Card>
+<Card title="FUNCTION LOAD" href="/redis/commands/functions/function-load">Load a library</Card>
+<Card title="FUNCTION STATS" href="/redis/commands/functions/function-stats">Get function execution stats</Card>
+</CardGroup>
+
diff --git a/redis/commands/generic/copy.mdx b/redis/commands/generic/copy.mdx
new file mode 100644
index 000000000..b4c14c40e
--- /dev/null
+++ b/redis/commands/generic/copy.mdx
@@ -0,0 +1,167 @@
+---
+title: "COPY"
+description: "Copy a key to another key."
+---
+
+Use `COPY` to copy a key to another key.
+
+## Syntax
+
+```redis
+COPY <source> <destination> [DB <destination-db>] [REPLACE]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<source>` | Yes | No | Redis key used as source. |
+| `<destination>` | Yes | No | Redis key used as destination. |
+| `DB <destination-db>` | No | No | Index of the database to copy the key into. |
+| `REPLACE` | No | No | Allow replacement of an existing destination. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer: `1` if the key was copied, `0` otherwise |
+| RESP3 | Integer: `1` if the key was copied, `0` otherwise |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+const result = await redis.copy("source-key", "destination-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.copy("source-key", "destination-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.copy("source-key", "destination-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.copy("source-key", "destination-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.copy("source-key", "destination-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.Copy(context.Background(), "source-key", "destination-key", 0, false).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.copy("source-key", "destination-key", false);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.copy("source-key", "destination-key", redis::CopyOptions::default())?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/generic/del.mdx b/redis/commands/generic/del.mdx
new file mode 100644
index 000000000..3609da3e2
--- /dev/null
+++ b/redis/commands/generic/del.mdx
@@ -0,0 +1,164 @@
+---
+title: "DEL"
+description: "Delete one or more keys."
+---
+
+Use `DEL` to delete one or more keys.
+
+## Syntax
+
+```redis
+DEL <key> [<key> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | Yes | Redis key targeted by the command. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.del("key1", "key2");
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.delete("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.del("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.del("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.delete("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.Del(context.Background(), "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.del("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.del("my-key")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/generic/dump.mdx b/redis/commands/generic/dump.mdx
new file mode 100644
index 000000000..8b8f57b0c
--- /dev/null
+++ b/redis/commands/generic/dump.mdx
@@ -0,0 +1,156 @@
+---
+title: "DUMP"
+description: "Serialize a key's value."
+---
+
+Use `DUMP` to serialize a key's value.
+
+## Syntax
+
+```redis
+DUMP <key>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Bulk string or Null bulk string or null array |
+| RESP3 | Bulk string or Null |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+<Note>
+  This command is not supported yet in `upstash_redis`.
+</Note>
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.dump("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.dump("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.dump("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.Dump(context.Background(), "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.dump("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("DUMP");
+    command.arg("my-key");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/generic/exists.mdx b/redis/commands/generic/exists.mdx
new file mode 100644
index 000000000..722dd52f1
--- /dev/null
+++ b/redis/commands/generic/exists.mdx
@@ -0,0 +1,167 @@
+---
+title: "EXISTS"
+description: "Check if keys exist."
+---
+
+Use `EXISTS` to check if keys exist.
+
+## Syntax
+
+```redis
+EXISTS <key> [<key> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | Yes | Redis key targeted by the command. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.set("key1", "value1")
+await redis.set("key2", "value2")
+const keys = await redis.exists("key1", "key2", "key3");
+console.log(keys) // 2
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.exists("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.exists("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.exists("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.exists("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.Exists(context.Background(), "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.exists("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.exists("my-key")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/generic/expire.mdx b/redis/commands/generic/expire.mdx
new file mode 100644
index 000000000..c654249be
--- /dev/null
+++ b/redis/commands/generic/expire.mdx
@@ -0,0 +1,173 @@
+---
+title: "EXPIRE"
+description: "Set a key's TTL in seconds."
+---
+
+Use `EXPIRE` to set a key's TTL in seconds.
+
+## Syntax
+
+```redis
+EXPIRE <key> <seconds> [NX | XX | GT | LT]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<seconds>` | Yes | No | Lifetime in seconds. |
+| `(NX \| XX \| GT \| LT)` | No | No | Choose one form: `NX` (only when the key has no expiration); `XX` (only when the key already has one); `GT` (only when the new expiration is later than the current one); `LT` (only when it is earlier). |
+
+## Important points
+
+- `NX` cannot be combined with `XX`, `GT`, or `LT`, and `GT` and `LT` cannot be used together.
+- A key with no expiration counts as an infinite one, so `GT` never sets an expiration on such a key and `LT` always does.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer: `1` if the timeout was set, `0` otherwise |
+| RESP3 | Integer: `1` if the timeout was set, `0` otherwise |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.set("mykey", "Hello");
+await redis.expire("mykey", 10);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.expire("my-key", 1000)
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.expire("my-key", "1000");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.expire("my-key", 1000);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.expire("my-key", 1000)
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+    "time"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.Expire(context.Background(), "my-key", 1000*time.Second).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.expire("my-key", 1000);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.expire("my-key", 1000)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/generic/expireat.mdx b/redis/commands/generic/expireat.mdx
new file mode 100644
index 000000000..26b0803f9
--- /dev/null
+++ b/redis/commands/generic/expireat.mdx
@@ -0,0 +1,174 @@
+---
+title: "EXPIREAT"
+description: "Set expiry as Unix timestamp."
+---
+
+Use `EXPIREAT` to set expiry as Unix timestamp.
+
+## Syntax
+
+```redis
+EXPIREAT <key> <unix-time-seconds> [NX | XX | GT | LT]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<unix-time-seconds>` | Yes | No | Expiration time as a Unix timestamp in seconds. |
+| `(NX \| XX \| GT \| LT)` | No | No | Choose one form: `NX` (only when the key has no expiration); `XX` (only when the key already has one); `GT` (only when the new expiration is later than the current one); `LT` (only when it is earlier). |
+
+## Important points
+
+- `NX` cannot be combined with `XX`, `GT`, or `LT`, and `GT` and `LT` cannot be used together.
+- A key with no expiration counts as an infinite one, so `GT` never sets an expiration on such a key and `LT` always does.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer: `1` if the timeout was set, `0` otherwise |
+| RESP3 | Integer: `1` if the timeout was set, `0` otherwise |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.set("mykey", "Hello");
+const tenSecondsFromNow = Math.floor(Date.now() / 1000) + 10;
+await redis.expireat("mykey", tenSecondsFromNow);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.expireat("my-key", 1735689600)
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.expireat("my-key", "1735689600");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.expireAt("my-key", 1735689600);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.expireat("my-key", 1735689600)
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+    "time"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ExpireAt(context.Background(), "my-key", time.Unix(1735689600, 0)).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.expireAt("my-key", 1735689600);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.expire_at("my-key", 1735689600)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/generic/expiretime.mdx b/redis/commands/generic/expiretime.mdx
new file mode 100644
index 000000000..1691087cf
--- /dev/null
+++ b/redis/commands/generic/expiretime.mdx
@@ -0,0 +1,160 @@
+---
+title: "EXPIRETIME"
+description: "Get expiry as Unix timestamp."
+---
+
+Use `EXPIRETIME` to get expiry as Unix timestamp.
+
+## Syntax
+
+```redis
+EXPIRETIME <key>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+
+## Important points
+
+- Negative integer replies are sentinel values, not durations or timestamps; see the response description for missing or persistent data.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer: expiration Unix time in seconds, `-1` if the key has no expiration, `-2` if the key does not exist |
+| RESP3 | Integer: expiration Unix time in seconds, `-1` if the key has no expiration, `-2` if the key does not exist |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+<Note>
+  This command is not supported yet in `upstash_redis`.
+</Note>
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.expiretime("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.expireTime("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.expiretime("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ExpireTime(context.Background(), "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.expireTime("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.expire_time("my-key")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/generic/keys.mdx b/redis/commands/generic/keys.mdx
new file mode 100644
index 000000000..f7c47d9ba
--- /dev/null
+++ b/redis/commands/generic/keys.mdx
@@ -0,0 +1,169 @@
+---
+title: "KEYS"
+description: "Find keys matching a pattern."
+---
+
+Use `KEYS` to find keys matching a pattern.
+
+## Syntax
+
+```redis
+KEYS <pattern>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<pattern>` | Yes | No | Glob-style pattern to match keys against. |
+
+## Important points
+
+- This command can expose administrative information or make a broad destructive change. Restrict it to trusted code paths.
+- This operation can inspect a large part of the database. Prefer cursor-based scans where possible and avoid unbounded use on hot paths.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of bulk-string keys |
+| RESP3 | Array of bulk-string keys |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const keys = await redis.keys("prefix*");
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.keys("*")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.keys("*");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.keys("*");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.keys("*")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.Keys(context.Background(), "*").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.keys("*");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.keys("*")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/generic/memory-usage.mdx b/redis/commands/generic/memory-usage.mdx
new file mode 100644
index 000000000..d5977a0c1
--- /dev/null
+++ b/redis/commands/generic/memory-usage.mdx
@@ -0,0 +1,165 @@
+---
+title: "MEMORY USAGE"
+description: "Estimate memory used by a key."
+---
+
+Use `MEMORY USAGE` to estimate memory used by a key.
+
+## Syntax
+
+```redis
+MEMORY USAGE <key> [SAMPLES <count>]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `key` | Yes | No | Key whose in-memory footprint should be estimated. |
+| `SAMPLES count` | No | No | Sampling count used when estimating large stream values. |
+
+## Important points
+
+- The result is an estimate in bytes and can change as the internal representation changes.
+- A missing key returns null. The sampling count is clamped to the deployment's supported range.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer or Null bulk string or null array |
+| RESP3 | Integer or Null |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+<Note>
+  This command is not supported yet in `upstash_redis`.
+</Note>
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.memory("USAGE", "my-key", "SAMPLES", "10");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.memoryUsage("my-key", { SAMPLES: 10 });
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.memory_usage("my-key", samples=10)
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.MemoryUsage(context.Background(), "my-key", 10).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.memoryUsage("my-key", 10);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("MEMORY");
+    command.arg("USAGE");
+    command.arg("my-key");
+    command.arg("SAMPLES");
+    command.arg("10");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/generic/overview.mdx b/redis/commands/generic/overview.mdx
new file mode 100644
index 000000000..eae4fc72b
--- /dev/null
+++ b/redis/commands/generic/overview.mdx
@@ -0,0 +1,34 @@
+---
+title: "Generic commands"
+sidebarTitle: "Overview"
+description: "Commands for managing keys, expiration, serialization, and database-wide key operations."
+---
+
+<CardGroup cols={2}>
+<Card title="COPY" href="/redis/commands/generic/copy">Copy a key to another key</Card>
+<Card title="DEL" href="/redis/commands/generic/del">Delete one or more keys</Card>
+<Card title="DUMP" href="/redis/commands/generic/dump">Serialize a key's value</Card>
+<Card title="EXISTS" href="/redis/commands/generic/exists">Check if keys exist</Card>
+<Card title="EXPIRE" href="/redis/commands/generic/expire">Set a key's TTL in seconds</Card>
+<Card title="EXPIREAT" href="/redis/commands/generic/expireat">Set expiry as Unix timestamp</Card>
+<Card title="EXPIRETIME" href="/redis/commands/generic/expiretime">Get expiry as Unix timestamp</Card>
+<Card title="KEYS" href="/redis/commands/generic/keys">Find keys matching a pattern</Card>
+<Card title="MEMORY USAGE" href="/redis/commands/generic/memory-usage">Estimate memory used by a key</Card>
+<Card title="PERSIST" href="/redis/commands/generic/persist">Remove the expiration from a key</Card>
+<Card title="PEXPIRE" href="/redis/commands/generic/pexpire">Set a key's TTL in milliseconds</Card>
+<Card title="PEXPIREAT" href="/redis/commands/generic/pexpireat">Set expiry as Unix ms timestamp</Card>
+<Card title="PEXPIRETIME" href="/redis/commands/generic/pexpiretime">Get expiry as Unix ms timestamp</Card>
+<Card title="PTTL" href="/redis/commands/generic/pttl">Get TTL in milliseconds</Card>
+<Card title="RANDOMKEY" href="/redis/commands/generic/randomkey">Return a random key</Card>
+<Card title="RENAME" href="/redis/commands/generic/rename">Rename a key</Card>
+<Card title="RENAMENX" href="/redis/commands/generic/renamenx">Rename a key if new key doesn't exist</Card>
+<Card title="RESTORE" href="/redis/commands/generic/restore">Deserialize and restore a key</Card>
+<Card title="SCAN" href="/redis/commands/generic/scan">Incrementally iterate keys</Card>
+<Card title="TOUCH" href="/redis/commands/generic/touch">Update last access time of keys</Card>
+<Card title="TTL" href="/redis/commands/generic/ttl">Get TTL in seconds</Card>
+<Card title="TYPE" href="/redis/commands/generic/type">Get the type of a key</Card>
+<Card title="UNLINK" href="/redis/commands/generic/unlink">Delete keys asynchronously</Card>
+<Card title="WAIT" href="/redis/commands/generic/wait">Wait for replica acknowledgements</Card>
+<Card title="WAITAOF" href="/redis/commands/generic/waitaof">Wait for local and replica persistence</Card>
+</CardGroup>
+
diff --git a/redis/commands/generic/persist.mdx b/redis/commands/generic/persist.mdx
new file mode 100644
index 000000000..aa336279b
--- /dev/null
+++ b/redis/commands/generic/persist.mdx
@@ -0,0 +1,164 @@
+---
+title: "PERSIST"
+description: "Remove the expiration from a key."
+---
+
+Use `PERSIST` to remove the expiration from a key.
+
+## Syntax
+
+```redis
+PERSIST <key>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer: `1` if the timeout was removed, `0` otherwise |
+| RESP3 | Integer: `1` if the timeout was removed, `0` otherwise |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.persist(key);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.persist("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.persist("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.persist("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.persist("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.Persist(context.Background(), "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.persist("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.persist("my-key")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/generic/pexpire.mdx b/redis/commands/generic/pexpire.mdx
new file mode 100644
index 000000000..0aa4f0543
--- /dev/null
+++ b/redis/commands/generic/pexpire.mdx
@@ -0,0 +1,172 @@
+---
+title: "PEXPIRE"
+description: "Set a key's TTL in milliseconds."
+---
+
+Use `PEXPIRE` to set a key's TTL in milliseconds.
+
+## Syntax
+
+```redis
+PEXPIRE <key> <milliseconds> [NX | XX | GT | LT]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<milliseconds>` | Yes | No | Lifetime in milliseconds. |
+| `(NX \| XX \| GT \| LT)` | No | No | Choose one form: `NX` (only when the key has no expiration); `XX` (only when the key already has one); `GT` (only when the new expiration is later than the current one); `LT` (only when it is earlier). |
+
+## Important points
+
+- `NX` cannot be combined with `XX`, `GT`, or `LT`, and `GT` and `LT` cannot be used together.
+- A key with no expiration counts as an infinite one, so `GT` never sets an expiration on such a key and `LT` always does.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer: `1` if the timeout was set, `0` otherwise |
+| RESP3 | Integer: `1` if the timeout was set, `0` otherwise |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.pexpire(key, 60_000); // 1 minute
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.pexpire("my-key", 1000)
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.pexpire("my-key", "1000");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.pExpire("my-key", 1000);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.pexpire("my-key", 1000)
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+    "time"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.PExpire(context.Background(), "my-key", time.Second).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.pexpire("my-key", 1000);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.pexpire("my-key", 1000)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/generic/pexpireat.mdx b/redis/commands/generic/pexpireat.mdx
new file mode 100644
index 000000000..de9f09e89
--- /dev/null
+++ b/redis/commands/generic/pexpireat.mdx
@@ -0,0 +1,174 @@
+---
+title: "PEXPIREAT"
+description: "Set expiry as Unix ms timestamp."
+---
+
+Use `PEXPIREAT` to set expiry as Unix ms timestamp.
+
+## Syntax
+
+```redis
+PEXPIREAT <key> <unix-time-milliseconds> [NX | XX | GT | LT]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<unix-time-milliseconds>` | Yes | No | Expiration time as a Unix timestamp in milliseconds. |
+| `(NX \| XX \| GT \| LT)` | No | No | Choose one form: `NX` (only when the key has no expiration); `XX` (only when the key already has one); `GT` (only when the new expiration is later than the current one); `LT` (only when it is earlier). |
+
+## Important points
+
+- `NX` cannot be combined with `XX`, `GT`, or `LT`, and `GT` and `LT` cannot be used together.
+- A key with no expiration counts as an infinite one, so `GT` never sets an expiration on such a key and `LT` always does.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer: `1` if the timeout was set, `0` otherwise |
+| RESP3 | Integer: `1` if the timeout was set, `0` otherwise |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.set("mykey", "Hello");
+const tenMinutesFromNow = Date.now() + 10 * 60 * 1000;
+await redis.pexpireat("mykey", tenMinutesFromNow);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.pexpireat("my-key", 1735689600)
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.pexpireat("my-key", "1735689600");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.pExpireAt("my-key", 1735689600);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.pexpireat("my-key", 1735689600)
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+    "time"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.PExpireAt(context.Background(), "my-key", time.UnixMilli(1735689600)).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.pexpireAt("my-key", 1735689600);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.pexpire_at("my-key", 1735689600)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/generic/pexpiretime.mdx b/redis/commands/generic/pexpiretime.mdx
new file mode 100644
index 000000000..95a0cfc21
--- /dev/null
+++ b/redis/commands/generic/pexpiretime.mdx
@@ -0,0 +1,160 @@
+---
+title: "PEXPIRETIME"
+description: "Get expiry as Unix ms timestamp."
+---
+
+Use `PEXPIRETIME` to get expiry as Unix ms timestamp.
+
+## Syntax
+
+```redis
+PEXPIRETIME <key>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+
+## Important points
+
+- Negative integer replies are sentinel values, not durations or timestamps; see the response description for missing or persistent data.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer: expiration Unix time in milliseconds, `-1` if the key has no expiration, `-2` if the key does not exist |
+| RESP3 | Integer: expiration Unix time in milliseconds, `-1` if the key has no expiration, `-2` if the key does not exist |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+<Note>
+  This command is not supported yet in `upstash_redis`.
+</Note>
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.pexpiretime("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.pExpireTime("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.pexpiretime("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.PExpireTime(context.Background(), "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.pexpireTime("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.pexpire_time("my-key")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/generic/pttl.mdx b/redis/commands/generic/pttl.mdx
new file mode 100644
index 000000000..4db46d05c
--- /dev/null
+++ b/redis/commands/generic/pttl.mdx
@@ -0,0 +1,168 @@
+---
+title: "PTTL"
+description: "Get TTL in milliseconds."
+---
+
+Use `PTTL` to get TTL in milliseconds.
+
+## Syntax
+
+```redis
+PTTL <key>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+
+## Important points
+
+- Negative integer replies are sentinel values, not durations or timestamps; see the response description for missing or persistent data.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer: remaining lifetime in milliseconds, `-1` if the key has no expiration, `-2` if the key does not exist |
+| RESP3 | Integer: remaining lifetime in milliseconds, `-1` if the key has no expiration, `-2` if the key does not exist |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const millis = await redis.pttl(key);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.pttl("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.pttl("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.pTTL("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.pttl("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.PTTL(context.Background(), "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.pttl("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.pttl("my-key")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/generic/randomkey.mdx b/redis/commands/generic/randomkey.mdx
new file mode 100644
index 000000000..36f87cd68
--- /dev/null
+++ b/redis/commands/generic/randomkey.mdx
@@ -0,0 +1,162 @@
+---
+title: "RANDOMKEY"
+description: "Return a random key."
+---
+
+Use `RANDOMKEY` to return a random key.
+
+## Syntax
+
+```redis
+RANDOMKEY
+```
+
+## Arguments
+
+This command takes no arguments.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Null bulk string or null array or Bulk string |
+| RESP3 | Null or Bulk string |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const key = await redis.randomkey();
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.randomkey()
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.randomkey();
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.randomKey();
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.randomkey()
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.RandomKey(context.Background()).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.randomKey();
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("RANDOMKEY");
+
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/generic/rename.mdx b/redis/commands/generic/rename.mdx
new file mode 100644
index 000000000..c262ff19b
--- /dev/null
+++ b/redis/commands/generic/rename.mdx
@@ -0,0 +1,165 @@
+---
+title: "RENAME"
+description: "Rename a key."
+---
+
+Use `RENAME` to rename a key.
+
+## Syntax
+
+```redis
+RENAME <key> <newkey>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<newkey>` | Yes | No | Redis key used as newkey. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Simple string `OK` |
+| RESP3 | Simple string `OK` |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.rename("old", "new");
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.rename("old-key", "new-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.rename("old-key", "new-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.rename("old-key", "new-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.rename("old-key", "new-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.Rename(context.Background(), "old-key", "new-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.rename("old-key", "new-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.rename("old-key", "new-key")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/generic/renamenx.mdx b/redis/commands/generic/renamenx.mdx
new file mode 100644
index 000000000..a063c6ac8
--- /dev/null
+++ b/redis/commands/generic/renamenx.mdx
@@ -0,0 +1,165 @@
+---
+title: "RENAMENX"
+description: "Rename a key if new key doesn't exist."
+---
+
+Use `RENAMENX` to rename a key if new key doesn't exist.
+
+## Syntax
+
+```redis
+RENAMENX <key> <newkey>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<newkey>` | Yes | No | Redis key used as newkey. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer: `1` if the key was renamed, `0` if the destination already exists |
+| RESP3 | Integer: `1` if the key was renamed, `0` if the destination already exists |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const renamed = await redis.renamenx("old", "new");
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.renamenx("old-key", "new-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.renamenx("old-key", "new-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.renameNX("old-key", "new-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.renamenx("old-key", "new-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.RenameNX(context.Background(), "old-key", "new-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.renamenx("old-key", "new-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.rename_nx("old-key", "new-key")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/generic/restore.mdx b/redis/commands/generic/restore.mdx
new file mode 100644
index 000000000..43ac3ece4
--- /dev/null
+++ b/redis/commands/generic/restore.mdx
@@ -0,0 +1,169 @@
+---
+title: "RESTORE"
+description: "Deserialize and restore a key."
+---
+
+Use `RESTORE` to deserialize and restore a key.
+
+## Syntax
+
+```redis
+RESTORE <key> <ttl> <serialized-value> [REPLACE] [ABSTTL] [IDLETIME <seconds>] [FREQ <frequency>]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<ttl>` | Yes | No | Lifetime in milliseconds; `0` restores the key without an expiration. |
+| `<serialized-value>` | Yes | No | Payload produced by `DUMP`. |
+| `REPLACE` | No | No | Allow replacement of an existing destination. |
+| `ABSTTL` | No | No | Treat `<ttl>` as an absolute Unix timestamp in milliseconds. |
+| `IDLETIME <seconds>` | No | No | Set the key's idle time, in seconds. |
+| `FREQ <frequency>` | No | No | Set the key's access frequency counter. |
+
+## Important points
+
+- This command can expose administrative information or make a broad destructive change. Restrict it to trusted code paths.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Simple string `OK` |
+| RESP3 | Simple string `OK` |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+<Note>
+  This command is not supported yet in `upstash_redis`.
+</Note>
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.restore("my-key", "1", "serialized-value");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.restore("my-key", 1, "serialized-value");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.restore("my-key", 1, "serialized-value")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+    "time"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.Restore(context.Background(), "my-key", time.Millisecond, "serialized-value").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.restore("my-key", 1, "serialized-value".getBytes());
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("RESTORE");
+    command.arg("my-key");
+    command.arg("1");
+    command.arg("serialized-value");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/generic/scan.mdx b/redis/commands/generic/scan.mdx
new file mode 100644
index 000000000..f0c8a5757
--- /dev/null
+++ b/redis/commands/generic/scan.mdx
@@ -0,0 +1,172 @@
+---
+title: "SCAN"
+description: "Incrementally iterate keys."
+---
+
+Use `SCAN` to incrementally iterate keys.
+
+## Syntax
+
+```redis
+SCAN <cursor> [MATCH <pattern>] [COUNT <count>] [TYPE <type>]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<cursor>` | Yes | No | Cursor returned by the previous call; start at `0`. |
+| `MATCH <pattern>` | No | No | Return only elements matching this glob-style pattern. |
+| `COUNT <count>` | No | No | Hint for how much work each iteration should do. |
+| `TYPE <type>` | No | No | Return only keys of this type, such as `string`, `list`, or `hash`. |
+
+## Important points
+
+- This operation can inspect a large part of the database. Prefer cursor-based scans where possible and avoid unbounded use on hot paths.
+- The cursor is opaque. Start with `0` and continue until the server returns cursor `0`; a single iteration may return no elements.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Two-element array: cursor and array of bulk-string keys |
+| RESP3 | Two-element array: cursor and array of bulk-string keys |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const [cursor, keys] = await redis.scan(0, { match: "*" });
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.scan(0)
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.scan("0");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.scan("0");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.scan(0)
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, _, err := client.Scan(context.Background(), 0, "*", 0).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.scan("0");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("SCAN");
+    command.arg("0");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/generic/touch.mdx b/redis/commands/generic/touch.mdx
new file mode 100644
index 000000000..54efe07ba
--- /dev/null
+++ b/redis/commands/generic/touch.mdx
@@ -0,0 +1,164 @@
+---
+title: "TOUCH"
+description: "Update last access time of keys."
+---
+
+Use `TOUCH` to update last access time of keys.
+
+## Syntax
+
+```redis
+TOUCH <key> [<key> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | Yes | Redis key targeted by the command. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.touch("key1", "key2", "key3");
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.touch("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.touch("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.touch("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.touch("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.Touch(context.Background(), "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.touch("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("TOUCH");
+    command.arg("my-key");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/generic/ttl.mdx b/redis/commands/generic/ttl.mdx
new file mode 100644
index 000000000..d99a05e18
--- /dev/null
+++ b/redis/commands/generic/ttl.mdx
@@ -0,0 +1,168 @@
+---
+title: "TTL"
+description: "Get TTL in seconds."
+---
+
+Use `TTL` to get TTL in seconds.
+
+## Syntax
+
+```redis
+TTL <key>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+
+## Important points
+
+- Negative integer replies are sentinel values, not durations or timestamps; see the response description for missing or persistent data.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer: remaining lifetime in seconds, `-1` if the key has no expiration, `-2` if the key does not exist |
+| RESP3 | Integer: remaining lifetime in seconds, `-1` if the key has no expiration, `-2` if the key does not exist |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const seconds = await redis.ttl(key);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.ttl("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.ttl("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.ttl("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.ttl("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.TTL(context.Background(), "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.ttl("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.ttl("my-key")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/generic/type.mdx b/redis/commands/generic/type.mdx
new file mode 100644
index 000000000..a97d0580c
--- /dev/null
+++ b/redis/commands/generic/type.mdx
@@ -0,0 +1,166 @@
+---
+title: "TYPE"
+description: "Get the type of a key."
+---
+
+Use `TYPE` to get the type of a key.
+
+## Syntax
+
+```redis
+TYPE <key>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Simple string: the type name, or `none` if the key does not exist |
+| RESP3 | Simple string: the type name, or `none` if the key does not exist |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.set("key", "value");
+const t = await redis.type("key");
+console.log(t) // "string"
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.type("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.type("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.type("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.type("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.Type(context.Background(), "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.type("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.key_type("my-key")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/generic/unlink.mdx b/redis/commands/generic/unlink.mdx
new file mode 100644
index 000000000..6ce84c42e
--- /dev/null
+++ b/redis/commands/generic/unlink.mdx
@@ -0,0 +1,164 @@
+---
+title: "UNLINK"
+description: "Delete keys asynchronously."
+---
+
+Use `UNLINK` to delete keys asynchronously.
+
+## Syntax
+
+```redis
+UNLINK <key> [<key> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | Yes | Redis key targeted by the command. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.unlink("key1", "key2");
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.unlink("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.unlink("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.unlink("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.unlink("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.Unlink(context.Background(), "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.unlink("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.unlink("my-key")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/generic/wait.mdx b/redis/commands/generic/wait.mdx
new file mode 100644
index 000000000..d6932da9a
--- /dev/null
+++ b/redis/commands/generic/wait.mdx
@@ -0,0 +1,164 @@
+---
+title: "WAIT"
+description: "Wait for replica acknowledgements."
+---
+
+Use `WAIT` to wait for replica acknowledgements.
+
+## Syntax
+
+```redis
+WAIT <numreplicas> <timeout>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `numreplicas` | Yes | No | Non-negative number of replicas that should acknowledge prior writes on this connection. |
+| `timeout` | Yes | No | Maximum wait in milliseconds; `0` means no timeout. |
+
+## Important points
+
+- This deployment waits for writes enqueued before `WAIT` begins, including writes from other connections. That is broader than the per-connection wording used by Redis clients.
+- The reply can be lower than `numreplicas` when the timeout expires. This improves observed replication durability but does not make Redis a strongly consistent store.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+<Note>
+  This command is not supported yet in `upstash_redis`.
+</Note>
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.wait("1", "1000");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.wait(1, 1000);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.wait("1", "1000")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+    "time"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.Wait(context.Background(), 1, time.Second).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.waitReplicas(1, 1000);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("WAIT");
+    command.arg("1");
+    command.arg("1000");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/generic/waitaof.mdx b/redis/commands/generic/waitaof.mdx
new file mode 100644
index 000000000..5e8c3b65c
--- /dev/null
+++ b/redis/commands/generic/waitaof.mdx
@@ -0,0 +1,166 @@
+---
+title: "WAITAOF"
+description: "Wait for local and replica persistence."
+---
+
+Use `WAITAOF` to wait for local and replica persistence.
+
+## Syntax
+
+```redis
+WAITAOF <numlocal> <numreplicas> <timeout>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `numlocal` | Yes | No | Whether to wait for local persistence: `0` or `1`. |
+| `numreplicas` | Yes | No | Non-negative number of replicas whose append-only files should include prior writes. |
+| `timeout` | Yes | No | Maximum wait in milliseconds; `0` means no timeout. |
+
+## Important points
+
+- This deployment waits for writes enqueued before `WAITAOF` begins, including writes from other connections.
+- The two-element reply contains the local persistence acknowledgement first and the replica persistence count second.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Two-element array of integers: local and replica acknowledgments |
+| RESP3 | Two-element array of integers: local and replica acknowledgments |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+<Note>
+  This command is not supported yet in `upstash_redis`.
+</Note>
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.call("WAITAOF", "1", "1", "1000");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.sendCommand(["WAITAOF", "1", "1", "1000"]);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.waitaof("1", "1", "1000")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+    "time"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.WaitAOF(context.Background(), 1, 1, time.Second).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.waitAOF(1, 1, 1000);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("WAITAOF");
+    command.arg("1");
+    command.arg("1");
+    command.arg("1000");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/geo/geoadd.mdx b/redis/commands/geo/geoadd.mdx
new file mode 100644
index 000000000..92a32ac4d
--- /dev/null
+++ b/redis/commands/geo/geoadd.mdx
@@ -0,0 +1,178 @@
+---
+title: "GEOADD"
+description: "Add geospatial items."
+---
+
+Use `GEOADD` to add geospatial items.
+
+## Syntax
+
+```redis
+GEOADD <key> [NX | XX] [CH] <longitude> <latitude> <member> [<longitude> <latitude> <member> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `(NX \| XX)` | No | No | Choose one form: `NX` (only add new members, never update an existing one); `XX` (only update members that already exist). |
+| `CH` | No | No | Count changed members rather than only new members. |
+| `<longitude> <latitude> <member>` | Yes | Yes | Longitude, latitude, and the member they belong to. Repeat to add several members. |
+
+## Important points
+
+- `NX` and `XX` are mutually exclusive.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+const result = await redis.geoadd("my-key", {
+  longitude: 29.0,
+  latitude: 41.0,
+  member: "member",
+});
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.geoadd("my-key", (29.0, 41.0, "member"))
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.geoadd("my-key", "29.0", "41.0", "member");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.geoAdd("my-key", { longitude: 29, latitude: 41, member: "member" });
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.geoadd("my-key", (29.0, 41.0, "member"))
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.GeoAdd(context.Background(), "my-key", &redis.GeoLocation{Longitude: 29.0, Latitude: 41.0, Name: "member"}).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.geoadd("my-key", 29.0, 41.0, "member");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("GEOADD");
+    command.arg("my-key");
+    command.arg("29.0");
+    command.arg("41.0");
+    command.arg("member");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/geo/geodist.mdx b/redis/commands/geo/geodist.mdx
new file mode 100644
index 000000000..ed5b123ab
--- /dev/null
+++ b/redis/commands/geo/geodist.mdx
@@ -0,0 +1,173 @@
+---
+title: "GEODIST"
+description: "Get distance between two members."
+---
+
+Use `GEODIST` to get distance between two members.
+
+## Syntax
+
+```redis
+GEODIST <key> <member1> <member2> [m | km | ft | mi]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<member1>` | Yes | No | First member. |
+| `<member2>` | Yes | No | Second member. |
+| `(m \| km \| ft \| mi)` | No | No | Choose one form: `m`; `km`; `ft`; `mi`. |
+
+## Important points
+
+- The distance is always returned as a bulk string, in both RESP2 and RESP3. Client libraries commonly decode it to a language number.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Null bulk string or null array or Bulk string |
+| RESP3 | Null or Bulk string |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+const result = await redis.geodist("my-key", "member1", "member2");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.geodist("my-key", "member1", "member2")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.geodist("my-key", "member1", "member2");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.geoDist("my-key", "member1", "member2");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.geodist("my-key", "member1", "member2")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.GeoDist(context.Background(), "my-key", "member1", "member2", "m").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.geodist("my-key", "member1", "member2");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("GEODIST");
+    command.arg("my-key");
+    command.arg("member1");
+    command.arg("member2");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/geo/geohash.mdx b/redis/commands/geo/geohash.mdx
new file mode 100644
index 000000000..30db2b6fc
--- /dev/null
+++ b/redis/commands/geo/geohash.mdx
@@ -0,0 +1,165 @@
+---
+title: "GEOHASH"
+description: "Get geohash strings for members."
+---
+
+Use `GEOHASH` to get geohash strings for members.
+
+## Syntax
+
+```redis
+GEOHASH <key> [<member> [<member> ...]]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<member>` | No | Yes | Member name. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of bulk-string geohashes or null values |
+| RESP3 | Array of bulk-string geohashes or null values |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+const result = await redis.geohash("my-key", "member");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.geohash("my-key", "member")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.geohash("my-key", "member");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.geoHash("my-key", "member");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.geohash("my-key", "member")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.GeoHash(context.Background(), "my-key", "member").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.geohash("my-key", "member");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("GEOHASH");
+    command.arg("my-key");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/geo/geopos.mdx b/redis/commands/geo/geopos.mdx
new file mode 100644
index 000000000..2f1f14db0
--- /dev/null
+++ b/redis/commands/geo/geopos.mdx
@@ -0,0 +1,165 @@
+---
+title: "GEOPOS"
+description: "Get coordinates of members."
+---
+
+Use `GEOPOS` to get coordinates of members.
+
+## Syntax
+
+```redis
+GEOPOS <key> [<member> [<member> ...]]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<member>` | No | Yes | Member name. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of coordinate-pair arrays or null values |
+| RESP3 | Array of coordinate-pair arrays or null values |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+const result = await redis.geopos("my-key", "member");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.geopos("my-key", "member")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.geopos("my-key", "member");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.geoPos("my-key", "member");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.geopos("my-key", "member")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.GeoPos(context.Background(), "my-key", "member").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.geopos("my-key", "member");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("GEOPOS");
+    command.arg("my-key");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/geo/georadius-ro.mdx b/redis/commands/geo/georadius-ro.mdx
new file mode 100644
index 000000000..320ced899
--- /dev/null
+++ b/redis/commands/geo/georadius-ro.mdx
@@ -0,0 +1,173 @@
+---
+title: "GEORADIUS_RO"
+description: "Find members within a radius of a point."
+---
+
+Use `GEORADIUS_RO` to find members within a radius of a point. It is the read-only form of `GEORADIUS`.
+
+## Syntax
+
+```redis
+GEORADIUS_RO <key> <longitude> <latitude> <radius> (m | km | ft | mi) [WITHCOORD] [WITHDIST] [WITHHASH] [COUNT <count> [ANY]] [ASC | DESC]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<longitude>` | Yes | No | Longitude in degrees, from -180 to 180. |
+| `<latitude>` | Yes | No | Latitude in degrees, from -85.05112878 to 85.05112878. |
+| `<radius>` | Yes | No | Search radius, in the unit given after it. |
+| `(m \| km \| ft \| mi)` | Yes | No | Choose one form: `m`; `km`; `ft`; `mi`. |
+| `WITHCOORD` | No | No | Also return the longitude and latitude of each match. |
+| `WITHDIST` | No | No | Also return the distance from the center, in the requested unit. |
+| `WITHHASH` | No | No | Also return the raw 52-bit geohash score of each match. |
+| `COUNT <count> [ANY]` | No | No | Return at most `<count>` matches. `ANY` returns as soon as enough matches are found, instead of sorting every match first. |
+| `(ASC \| DESC)` | No | No | Choose one form: `ASC`; `DESC`. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of bulk-string members or member-detail arrays |
+| RESP3 | Array of bulk-string members or member-detail arrays |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.georadius_ro("my-key", 29.0, 41.0, 1.5, "M")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.georadius_ro("my-key", "29.0", "41.0", "1.5", "m");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.geoRadiusRo("my-key", { longitude: 29, latitude: 41 }, 1.5, "m");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.execute_command("GEORADIUS_RO", "my-key", "29.0", "41.0", "1.5", "m")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.GeoRadius(context.Background(), "my-key", 29.0, 41.0, &redis.GeoRadiusQuery{Radius: 1.5, Unit: "m"}).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.georadiusReadonly("my-key", 29.0, 41.0, 1.5, redis.clients.jedis.args.GeoUnit.M);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("GEORADIUS_RO");
+    command.arg("my-key");
+    command.arg("29.0");
+    command.arg("41.0");
+    command.arg("1.5");
+    command.arg("m");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/geo/georadius.mdx b/redis/commands/geo/georadius.mdx
new file mode 100644
index 000000000..e5cae094b
--- /dev/null
+++ b/redis/commands/geo/georadius.mdx
@@ -0,0 +1,174 @@
+---
+title: "GEORADIUS"
+description: "Query members within radius."
+---
+
+Use `GEORADIUS` to query members within radius.
+
+## Syntax
+
+```redis
+GEORADIUS <key> <longitude> <latitude> <radius> (m | km | ft | mi) [WITHCOORD] [WITHDIST] [WITHHASH] [COUNT <count> [ANY]] [ASC | DESC] [STORE <storekey> | STOREDIST <storedistkey>]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<longitude>` | Yes | No | Longitude in degrees, from -180 to 180. |
+| `<latitude>` | Yes | No | Latitude in degrees, from -85.05112878 to 85.05112878. |
+| `<radius>` | Yes | No | Search radius, in the unit given after it. |
+| `(m \| km \| ft \| mi)` | Yes | No | Choose one form: `m`; `km`; `ft`; `mi`. |
+| `WITHCOORD` | No | No | Also return the longitude and latitude of each match. |
+| `WITHDIST` | No | No | Also return the distance from the center, in the requested unit. |
+| `WITHHASH` | No | No | Also return the raw 52-bit geohash score of each match. |
+| `COUNT <count> [ANY]` | No | No | Return at most `<count>` matches. `ANY` returns as soon as enough matches are found, instead of sorting every match first. |
+| `(ASC \| DESC)` | No | No | Choose one form: `ASC`; `DESC`. |
+| `(STORE <storekey> \| STOREDIST <storedistkey>)` | No | No | Choose one form: `STORE`; `STOREDIST`. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of bulk-string members or member-detail arrays, or Integer when storing |
+| RESP3 | Array of bulk-string members or member-detail arrays, or Integer when storing |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.georadius("my-key", 29.0, 41.0, 1.5, "M")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.georadius("my-key", "29.0", "41.0", "1.5", "m");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.geoRadius("my-key", { longitude: 29, latitude: 41 }, 1.5, "m");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.georadius("my-key", 29.0, 41.0, 1.5, "m")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.GeoRadius(context.Background(), "my-key", 29.0, 41.0, &redis.GeoRadiusQuery{Radius: 1.5, Unit: "m"}).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.georadius("my-key", 29.0, 41.0, 1.5, redis.clients.jedis.args.GeoUnit.M);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("GEORADIUS");
+    command.arg("my-key");
+    command.arg("29.0");
+    command.arg("41.0");
+    command.arg("1.5");
+    command.arg("m");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/geo/georadiusbymember-ro.mdx b/redis/commands/geo/georadiusbymember-ro.mdx
new file mode 100644
index 000000000..e91b21305
--- /dev/null
+++ b/redis/commands/geo/georadiusbymember-ro.mdx
@@ -0,0 +1,171 @@
+---
+title: "GEORADIUSBYMEMBER_RO"
+description: "Find members within a radius of another member."
+---
+
+Use `GEORADIUSBYMEMBER_RO` to find members within a radius of another member. It is the read-only form of `GEORADIUSBYMEMBER`.
+
+## Syntax
+
+```redis
+GEORADIUSBYMEMBER_RO <key> <member> <radius> (m | km | ft | mi) [WITHCOORD] [WITHDIST] [WITHHASH] [COUNT <count> [ANY]] [ASC | DESC]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<member>` | Yes | No | Member name. |
+| `<radius>` | Yes | No | Search radius, in the unit given after it. |
+| `(m \| km \| ft \| mi)` | Yes | No | Choose one form: `m`; `km`; `ft`; `mi`. |
+| `WITHCOORD` | No | No | Also return the longitude and latitude of each match. |
+| `WITHDIST` | No | No | Also return the distance from the center, in the requested unit. |
+| `WITHHASH` | No | No | Also return the raw 52-bit geohash score of each match. |
+| `COUNT <count> [ANY]` | No | No | Return at most `<count>` matches. `ANY` returns as soon as enough matches are found, instead of sorting every match first. |
+| `(ASC \| DESC)` | No | No | Choose one form: `ASC`; `DESC`. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of bulk-string members or member-detail arrays |
+| RESP3 | Array of bulk-string members or member-detail arrays |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.georadiusbymember_ro("my-key", "member", 1.5, "M")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.georadiusbymember_ro("my-key", "member", "1.5", "m");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.geoRadiusByMemberRo("my-key", "member", 1.5, "m");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.execute_command("GEORADIUSBYMEMBER_RO", "my-key", "member", "1.5", "m")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.GeoRadiusByMember(context.Background(), "my-key", "member", &redis.GeoRadiusQuery{Radius: 1.5, Unit: "m"}).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.georadiusByMemberReadonly("my-key", "member", 1.5, redis.clients.jedis.args.GeoUnit.M);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("GEORADIUSBYMEMBER_RO");
+    command.arg("my-key");
+    command.arg("member");
+    command.arg("1.5");
+    command.arg("m");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/geo/georadiusbymember.mdx b/redis/commands/geo/georadiusbymember.mdx
new file mode 100644
index 000000000..f2a6990d2
--- /dev/null
+++ b/redis/commands/geo/georadiusbymember.mdx
@@ -0,0 +1,172 @@
+---
+title: "GEORADIUSBYMEMBER"
+description: "Radius query centered on member."
+---
+
+Use `GEORADIUSBYMEMBER` to radius query centered on member.
+
+## Syntax
+
+```redis
+GEORADIUSBYMEMBER <key> <member> <radius> (m | km | ft | mi) [WITHCOORD] [WITHDIST] [WITHHASH] [COUNT <count> [ANY]] [ASC | DESC] [STORE <storekey> | STOREDIST <storedistkey>]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<member>` | Yes | No | Member name. |
+| `<radius>` | Yes | No | Search radius, in the unit given after it. |
+| `(m \| km \| ft \| mi)` | Yes | No | Choose one form: `m`; `km`; `ft`; `mi`. |
+| `WITHCOORD` | No | No | Also return the longitude and latitude of each match. |
+| `WITHDIST` | No | No | Also return the distance from the center, in the requested unit. |
+| `WITHHASH` | No | No | Also return the raw 52-bit geohash score of each match. |
+| `COUNT <count> [ANY]` | No | No | Return at most `<count>` matches. `ANY` returns as soon as enough matches are found, instead of sorting every match first. |
+| `(ASC \| DESC)` | No | No | Choose one form: `ASC`; `DESC`. |
+| `(STORE <storekey> \| STOREDIST <storedistkey>)` | No | No | Choose one form: `STORE`; `STOREDIST`. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of bulk-string members or member-detail arrays, or Integer when storing |
+| RESP3 | Array of bulk-string members or member-detail arrays, or Integer when storing |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.georadiusbymember("my-key", "member", 1.5, "M")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.georadiusbymember("my-key", "member", "1.5", "m");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.geoRadiusByMember("my-key", "member", 1.5, "m");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.georadiusbymember("my-key", "member", 1.5, "m")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.GeoRadiusByMember(context.Background(), "my-key", "member", &redis.GeoRadiusQuery{Radius: 1.5, Unit: "m"}).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.georadiusByMember("my-key", "member", 1.5, redis.clients.jedis.args.GeoUnit.M);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("GEORADIUSBYMEMBER");
+    command.arg("my-key");
+    command.arg("member");
+    command.arg("1.5");
+    command.arg("m");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/geo/geosearch.mdx b/redis/commands/geo/geosearch.mdx
new file mode 100644
index 000000000..514be6a4d
--- /dev/null
+++ b/redis/commands/geo/geosearch.mdx
@@ -0,0 +1,179 @@
+---
+title: "GEOSEARCH"
+description: "Search for members in an area."
+---
+
+Use `GEOSEARCH` to search for members in an area.
+
+## Syntax
+
+```redis
+GEOSEARCH <key> (FROMMEMBER <member> | FROMLONLAT <longitude> <latitude>) (BYRADIUS <radius> (m | km | ft | mi) | BYBOX <width> <height> (m | km | ft | mi)) [ASC | DESC] [COUNT <count> [ANY]] [WITHCOORD] [WITHDIST] [WITHHASH]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `(FROMMEMBER <member> \| FROMLONLAT <longitude> <latitude>)` | Yes | No | Choose one form: `FROMMEMBER`; `FROMLONLAT`. |
+| `(BYRADIUS <radius> (m \| km \| ft \| mi) \| BYBOX <width> <height> (m \| km \| ft \| mi))` | Yes | No | Choose one form: `BYRADIUS`; `m`; `km`; `ft`; `mi`; `BYBOX`; `m`; `km`; `ft`; `mi`. |
+| `(ASC \| DESC)` | No | No | Choose one form: `ASC`; `DESC`. |
+| `COUNT <count> [ANY]` | No | No | Return at most `<count>` matches. `ANY` returns as soon as enough matches are found, instead of sorting every match first. |
+| `WITHCOORD` | No | No | Also return the longitude and latitude of each match. |
+| `WITHDIST` | No | No | Also return the distance from the center, in the requested unit. |
+| `WITHHASH` | No | No | Also return the raw 52-bit geohash score of each match. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of bulk-string members or member-detail arrays |
+| RESP3 | Array of bulk-string members or member-detail arrays |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+const result = await redis.geosearch(
+  "my-key",
+  { type: "FROMMEMBER", member: "member" },
+  { type: "BYRADIUS", radius: 1.5, radiusType: "M" },
+  "ASC",
+);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.geosearch("my-key", member="member", radius=1.5, unit="M")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.geosearch("my-key", "FROMMEMBER", "member", "BYRADIUS", "1.5", "m");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.geoSearch("my-key", "member", { radius: 1.5, unit: "m" });
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.geosearch("my-key", member="member", radius=1.5, unit="m")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.GeoSearch(context.Background(), "my-key", &redis.GeoSearchQuery{Member: "member", Radius: 1.5, RadiusUnit: "m"}).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.geosearch("my-key", "member", 1.5, redis.clients.jedis.args.GeoUnit.M);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("GEOSEARCH");
+    command.arg("my-key");
+    command.arg("member");
+    command.arg("1.5");
+    command.arg("m");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/geo/geosearchstore.mdx b/redis/commands/geo/geosearchstore.mdx
new file mode 100644
index 000000000..41230e96e
--- /dev/null
+++ b/redis/commands/geo/geosearchstore.mdx
@@ -0,0 +1,180 @@
+---
+title: "GEOSEARCHSTORE"
+description: "Store geosearch results."
+---
+
+Use `GEOSEARCHSTORE` to store geosearch results.
+
+## Syntax
+
+```redis
+GEOSEARCHSTORE <destination> <source> (FROMMEMBER <member> | FROMLONLAT <longitude> <latitude>) (BYRADIUS <radius> (m | km | ft | mi) | BYBOX <width> <height> (m | km | ft | mi)) [ASC | DESC] [COUNT <count> [ANY]] [STOREDIST]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<destination>` | Yes | No | Redis key used as destination. |
+| `<source>` | Yes | No | Redis key used as source. |
+| `(FROMMEMBER <member> \| FROMLONLAT <longitude> <latitude>)` | Yes | No | Choose one form: `FROMMEMBER`; `FROMLONLAT`. |
+| `(BYRADIUS <radius> (m \| km \| ft \| mi) \| BYBOX <width> <height> (m \| km \| ft \| mi))` | Yes | No | Choose one form: `BYRADIUS`; `m`; `km`; `ft`; `mi`; `BYBOX`; `m`; `km`; `ft`; `mi`. |
+| `(ASC \| DESC)` | No | No | Choose one form: `ASC`; `DESC`. |
+| `COUNT <count> [ANY]` | No | No | Return at most `<count>` matches. `ANY` returns as soon as enough matches are found, instead of sorting every match first. |
+| `STOREDIST` | No | No | Store each match's distance from the center instead of its geohash score. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+const result = await redis.geosearchstore(
+  "destination-key",
+  "source-key",
+  { type: "FROMMEMBER", member: "member" },
+  { type: "BYRADIUS", radius: 1.5, radiusType: "M" },
+  "ASC",
+);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.geosearchstore("destination-key", "source-key", member="member", radius=1.5, unit="M")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.geosearchstore("destination-key", "source-key", "FROMMEMBER", "member", "BYRADIUS", "1.5", "m");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.geoSearchStore("destination-key", "source-key", "member", { radius: 1.5, unit: "m" });
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.geosearchstore("destination-key", "source-key", member="member", radius=1.5, unit="m")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.GeoSearchStore(context.Background(), "source-key", "destination-key", &redis.GeoSearchStoreQuery{GeoSearchQuery: redis.GeoSearchQuery{Member: "member", Radius: 1.5, RadiusUnit: "m"}}).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.geosearchStore("destination-key", "source-key", "member", 1.5, redis.clients.jedis.args.GeoUnit.M);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("GEOSEARCHSTORE");
+    command.arg("destination-key");
+    command.arg("source-key");
+    command.arg("member");
+    command.arg("1.5");
+    command.arg("m");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/geo/overview.mdx b/redis/commands/geo/overview.mdx
new file mode 100644
index 000000000..e1a4b64fc
--- /dev/null
+++ b/redis/commands/geo/overview.mdx
@@ -0,0 +1,19 @@
+---
+title: "Geo commands"
+sidebarTitle: "Overview"
+description: "Commands for storing and querying geospatial data."
+---
+
+<CardGroup cols={2}>
+<Card title="GEOADD" href="/redis/commands/geo/geoadd">Add geospatial items</Card>
+<Card title="GEODIST" href="/redis/commands/geo/geodist">Get distance between two members</Card>
+<Card title="GEOHASH" href="/redis/commands/geo/geohash">Get geohash strings for members</Card>
+<Card title="GEOPOS" href="/redis/commands/geo/geopos">Get coordinates of members</Card>
+<Card title="GEORADIUS" href="/redis/commands/geo/georadius">Query members within radius</Card>
+<Card title="GEORADIUS_RO" href="/redis/commands/geo/georadius-ro">Read-only radius query</Card>
+<Card title="GEORADIUSBYMEMBER" href="/redis/commands/geo/georadiusbymember">Radius query centered on member</Card>
+<Card title="GEORADIUSBYMEMBER_RO" href="/redis/commands/geo/georadiusbymember-ro">Read-only radius query by member</Card>
+<Card title="GEOSEARCH" href="/redis/commands/geo/geosearch">Search for members in an area</Card>
+<Card title="GEOSEARCHSTORE" href="/redis/commands/geo/geosearchstore">Store geosearch results</Card>
+</CardGroup>
+
diff --git a/redis/commands/hash/hdel.mdx b/redis/commands/hash/hdel.mdx
new file mode 100644
index 000000000..c3c148701
--- /dev/null
+++ b/redis/commands/hash/hdel.mdx
@@ -0,0 +1,166 @@
+---
+title: "HDEL"
+description: "Delete one or more hash fields."
+---
+
+Use `HDEL` to delete one or more hash fields.
+
+## Syntax
+
+```redis
+HDEL <key> <field> [<field> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<field>` | Yes | Yes | Hash field name. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.hdel(key, 'field1', 'field2');
+// returns 5
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.hdel("my-key", "field")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.hdel("my-key", "field");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.hDel("my-key", "field");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.hdel("my-key", "field")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.HDel(context.Background(), "my-key", "field").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.hdel("my-key", "field");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.hdel("my-key", "field")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/hash/hexists.mdx b/redis/commands/hash/hexists.mdx
new file mode 100644
index 000000000..d09eecd7f
--- /dev/null
+++ b/redis/commands/hash/hexists.mdx
@@ -0,0 +1,168 @@
+---
+title: "HEXISTS"
+description: "Check if a hash field exists."
+---
+
+Use `HEXISTS` to check if a hash field exists.
+
+## Syntax
+
+```redis
+HEXISTS <key> <field>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<field>` | Yes | No | Hash field name. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer: `1` if the field exists, `0` otherwise |
+| RESP3 | Integer: `1` if the field exists, `0` otherwise |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.hset("key", "field", "value");
+const exists = await redis.hexists("key", "field");
+
+console.log(exists); // 1
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.hexists("my-key", "field")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.hexists("my-key", "field");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.hExists("my-key", "field");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.hexists("my-key", "field")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.HExists(context.Background(), "my-key", "field").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.hexists("my-key", "field");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.hexists("my-key", "field")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/hash/hexpire.mdx b/redis/commands/hash/hexpire.mdx
new file mode 100644
index 000000000..5b94ee30f
--- /dev/null
+++ b/redis/commands/hash/hexpire.mdx
@@ -0,0 +1,175 @@
+---
+title: "HEXPIRE"
+description: "Set field TTL in seconds."
+---
+
+Use `HEXPIRE` to set field TTL in seconds.
+
+## Syntax
+
+```redis
+HEXPIRE <key> <seconds> [NX | XX | GT | LT] FIELDS <numfields> <field> [<field> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<seconds>` | Yes | No | Lifetime in seconds. |
+| `(NX \| XX \| GT \| LT)` | No | No | Choose one form: `NX` (only when the field has no expiration); `XX` (only when the field already has one); `GT` (only when the new expiration is later than the current one); `LT` (only when it is earlier). |
+| `FIELDS <numfields> <field> [<field> ...]` | Yes | No | Fields to target. Give the field count first, then that many field names. |
+
+## Important points
+
+- `NX` cannot be combined with `XX`, `GT`, or `LT`, and `GT` and `LT` cannot be used together.
+- A field with no expiration counts as an infinite one, so `GT` never sets an expiration on such a field and `LT` always does.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of integer status codes, one per field |
+| RESP3 | Array of integer status codes, one per field |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.hset("my-key", "my-field", "my-value");
+const expirationSet = await redis.hexpire("my-key", "my-field", 1);
+
+console.log(expirationSet); // 1
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.hexpire("my-key", "field", 1000)
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.hexpire("my-key", "1000", "FIELDS", "1", "field");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.hExpire("my-key", "field", 1000);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.hexpire("my-key", 1000, "field")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.HExpire(context.Background(), "my-key", 1000*time.Second, "field").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.hexpire("my-key", 1000, "field");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.hexpire("my-key", 1000, redis::ExpireOption::NONE, &["field"])?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/hash/hexpireat.mdx b/redis/commands/hash/hexpireat.mdx
new file mode 100644
index 000000000..b4c7ee41d
--- /dev/null
+++ b/redis/commands/hash/hexpireat.mdx
@@ -0,0 +1,175 @@
+---
+title: "HEXPIREAT"
+description: "Set field expiry as timestamp."
+---
+
+Use `HEXPIREAT` to set field expiry as timestamp.
+
+## Syntax
+
+```redis
+HEXPIREAT <key> <unix-time-seconds> [NX | XX | GT | LT] FIELDS <numfields> <field> [<field> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<unix-time-seconds>` | Yes | No | Expiration time as a Unix timestamp in seconds. |
+| `(NX \| XX \| GT \| LT)` | No | No | Choose one form: `NX` (only when the field has no expiration); `XX` (only when the field already has one); `GT` (only when the new expiration is later than the current one); `LT` (only when it is earlier). |
+| `FIELDS <numfields> <field> [<field> ...]` | Yes | No | Fields to target. Give the field count first, then that many field names. |
+
+## Important points
+
+- `NX` cannot be combined with `XX`, `GT`, or `LT`, and `GT` and `LT` cannot be used together.
+- A field with no expiration counts as an infinite one, so `GT` never sets an expiration on such a field and `LT` always does.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of integer status codes, one per field |
+| RESP3 | Array of integer status codes, one per field |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.hset("my-key", "my-field", "my-value");
+const expirationSet = await redis.hexpireat("my-key", "my-field", Math.floor(Date.now() / 1000) + 10);
+
+console.log(expirationSet); // [1]
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.hexpireat("my-key", "field", 1735689600)
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.hexpireat("my-key", "1735689600", "FIELDS", "1", "field");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.hExpireAt("my-key", "field", 1735689600);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.hexpireat("my-key", 1735689600, "field")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.HExpireAt(context.Background(), "my-key", time.Unix(1735689600, 0), "field").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.hexpireAt("my-key", 1735689600, "field");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.hexpire_at("my-key", 1735689600, redis::ExpireOption::NONE, &["field"])?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/hash/hexpiretime.mdx b/redis/commands/hash/hexpiretime.mdx
new file mode 100644
index 000000000..a49dda5e5
--- /dev/null
+++ b/redis/commands/hash/hexpiretime.mdx
@@ -0,0 +1,172 @@
+---
+title: "HEXPIRETIME"
+description: "Get field expiry as timestamp."
+---
+
+Use `HEXPIRETIME` to get field expiry as timestamp.
+
+## Syntax
+
+```redis
+HEXPIRETIME <key> FIELDS <numfields> <field> [<field> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `FIELDS <numfields> <field> [<field> ...]` | Yes | No | Fields to target. Give the field count first, then that many field names. |
+
+## Important points
+
+- Negative integer replies are sentinel values, not durations or timestamps; see the response description for missing or persistent data.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of expiration timestamps or negative integer status codes, one per field |
+| RESP3 | Array of expiration timestamps or negative integer status codes, one per field |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.hset("my-key", "my-field", "my-value");
+await redis.hexpireat("my-key", "my-field", Math.floor(Date.now() / 1000) + 10);
+const expireTime = await redis.hexpiretime("my-key", "my-field");
+
+console.log(expireTime); // e.g., [1697059200]
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.hexpiretime("my-key", "field")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.hexpiretime("my-key", "FIELDS", "1", "field");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.hExpireTime("my-key", "field");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.hexpiretime("my-key", "field")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.HExpireTime(context.Background(), "my-key", "field").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.hexpireTime("my-key", "field");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.hexpire_time("my-key", &["field"])?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/hash/hget.mdx b/redis/commands/hash/hget.mdx
new file mode 100644
index 000000000..878a5b3f1
--- /dev/null
+++ b/redis/commands/hash/hget.mdx
@@ -0,0 +1,167 @@
+---
+title: "HGET"
+description: "Get the value of a hash field."
+---
+
+Use `HGET` to get the value of a hash field.
+
+## Syntax
+
+```redis
+HGET <key> <field>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<field>` | Yes | No | Hash field name. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Bulk string or Null bulk string or null array |
+| RESP3 | Bulk string or Null |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.hset("key", {field: "value"});
+const field = await redis.hget("key", "field");
+console.log(field); // "value"
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.hget("my-key", "field")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.hget("my-key", "field");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.hGet("my-key", "field");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.hget("my-key", "field")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.HGet(context.Background(), "my-key", "field").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.hget("my-key", "field");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.hget("my-key", "field")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/hash/hgetall.mdx b/redis/commands/hash/hgetall.mdx
new file mode 100644
index 000000000..399421f4b
--- /dev/null
+++ b/redis/commands/hash/hgetall.mdx
@@ -0,0 +1,173 @@
+---
+title: "HGETALL"
+description: "Get all fields and values."
+---
+
+Use `HGETALL` to get all fields and values.
+
+## Syntax
+
+```redis
+HGETALL <key>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+
+## Important points
+
+- Pair-based results may be flattened into one alternating array in RESP2 while RESP3 preserves nested pairs or a map.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Flat array of alternating keys and values |
+| RESP3 | Map |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.hset("key", {
+  field1: "value1",
+  field2: "value2",
+  });
+const hash = await redis.hgetall("key");
+console.log(hash); // { field1: "value1", field2: "value2" }
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.hgetall("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.hgetall("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.hGetAll("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.hgetall("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.HGetAll(context.Background(), "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.hgetAll("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.hgetall("my-key")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/hash/hgetdel.mdx b/redis/commands/hash/hgetdel.mdx
new file mode 100644
index 000000000..c6f398f35
--- /dev/null
+++ b/redis/commands/hash/hgetdel.mdx
@@ -0,0 +1,174 @@
+---
+title: "HGETDEL"
+description: "Get and delete hash fields."
+---
+
+Use `HGETDEL` to get and delete hash fields.
+
+## Syntax
+
+```redis
+HGETDEL <key> FIELDS <numfields> <field> [<field> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `FIELDS <numfields> <field> [<field> ...]` | Yes | No | Fields to target. Give the field count first, then that many field names. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of bulk-string values or null values, one per field |
+| RESP3 | Array of bulk-string values or null values, one per field |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+// Set some hash fields
+await redis.hset("user:123", { name: "John", age: "30", email: "john@example.com" });
+
+// Get and delete specific fields
+const result = await redis.hgetdel("user:123", "name", "email");
+console.log(result); // { name: "John", email: "john@example.com" }
+
+// Verify fields were deleted
+const name = await redis.hget("user:123", "name");
+console.log(name); // null
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.hgetdel("my-key", "field")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.hgetdel("my-key", "FIELDS", "1", "field");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.hGetDel("my-key", "field");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.hgetdel("my-key", "field")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.HGetDel(context.Background(), "my-key", "1", "field").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.hgetdel("my-key", "1", "field");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.hget_del("my-key", &["field"])?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/hash/hgetex.mdx b/redis/commands/hash/hgetex.mdx
new file mode 100644
index 000000000..cbf30e21c
--- /dev/null
+++ b/redis/commands/hash/hgetex.mdx
@@ -0,0 +1,170 @@
+---
+title: "HGETEX"
+description: "Get fields and set their expiry."
+---
+
+Use `HGETEX` to get fields and set their expiry.
+
+## Syntax
+
+```redis
+HGETEX <key> [EX <seconds> | PX <milliseconds> | EXAT <unix-time-seconds> | PXAT <unix-time-milliseconds> | PERSIST] FIELDS <numfields> <field> [<field> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `(EX <seconds> \| PX <milliseconds> \| EXAT <unix-time-seconds> \| PXAT <unix-time-milliseconds> \| PERSIST)` | No | No | Choose one form: `EX` (set a lifetime in seconds); `PX` (set a lifetime in milliseconds); `EXAT` (expire at a Unix timestamp in seconds); `PXAT` (expire at a Unix timestamp in milliseconds); `PERSIST`. |
+| `FIELDS <numfields> <field> [<field> ...]` | Yes | No | Fields to target. Give the field count first, then that many field names. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of bulk-string values or null values, one per field |
+| RESP3 | Array of bulk-string values or null values, one per field |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.hset("user:123", { name: "John", email: "john@example.com" });
+
+// Get fields and set expiration to 60 seconds
+const result = await redis.hgetex("user:123", { ex: 60 }, "name", "email");
+console.log(result); // { name: "John", email: "john@example.com" }
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.hgetex("my-key", "field")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.hgetex("my-key", "FIELDS", "1", "field");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.hGetEx("my-key", "field");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.hgetex("my-key", "field")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.HGetEX(context.Background(), "my-key", "1", "field").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.hgetex("my-key", redis.clients.jedis.params.HGetExParams.hGetExParams(), "field");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.hget_ex("my-key", &["field"], redis::Expiry::PERSIST)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/hash/hincrby.mdx b/redis/commands/hash/hincrby.mdx
new file mode 100644
index 000000000..31d0b5241
--- /dev/null
+++ b/redis/commands/hash/hincrby.mdx
@@ -0,0 +1,170 @@
+---
+title: "HINCRBY"
+description: "Increment integer value of a field."
+---
+
+Use `HINCRBY` to increment integer value of a field.
+
+## Syntax
+
+```redis
+HINCRBY <key> <field> <increment>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<field>` | Yes | No | Hash field name. |
+| `<increment>` | Yes | No | Integer amount to add to the field. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.hset("key", {
+  field: 20,
+  });
+const after = await redis.hincrby("key", "field", 2);
+console.log(after); // 22
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.hincrby("my-key", "field", 1)
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.hincrby("my-key", "field", "1");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.hIncrBy("my-key", "field", 1);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.hincrby("my-key", "field", 1)
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.HIncrBy(context.Background(), "my-key", "field", 1).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.hincrBy("my-key", "field", 1);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.hincr("my-key", "field", 1)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/hash/hincrbyfloat.mdx b/redis/commands/hash/hincrbyfloat.mdx
new file mode 100644
index 000000000..4fdaae54b
--- /dev/null
+++ b/redis/commands/hash/hincrbyfloat.mdx
@@ -0,0 +1,174 @@
+---
+title: "HINCRBYFLOAT"
+description: "Increment float value of a field."
+---
+
+Use `HINCRBYFLOAT` to increment float value of a field.
+
+## Syntax
+
+```redis
+HINCRBYFLOAT <key> <field> <increment>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<field>` | Yes | No | Hash field name. |
+| `<increment>` | Yes | No | Amount to add to the field; may be a floating-point number. |
+
+## Important points
+
+- The value is always returned as a bulk string, in both RESP2 and RESP3. Client libraries commonly decode it to a language number.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Bulk string |
+| RESP3 | Bulk string |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.hset("key", {
+  field: 20,
+  });
+const after = await redis.hincrby("key", "field", 2.5);
+console.log(after); // 22.5
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.hincrbyfloat("my-key", "field", 1.5)
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.hincrbyfloat("my-key", "field", "1.5");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.hIncrByFloat("my-key", "field", 1.5);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.hincrbyfloat("my-key", "field", 1.5)
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.HIncrByFloat(context.Background(), "my-key", "field", 1.5).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.hincrByFloat("my-key", "field", 1.5);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.hincr("my-key", "field", 1.5)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/hash/hkeys.mdx b/redis/commands/hash/hkeys.mdx
new file mode 100644
index 000000000..62be5b473
--- /dev/null
+++ b/redis/commands/hash/hkeys.mdx
@@ -0,0 +1,169 @@
+---
+title: "HKEYS"
+description: "Get all fields in a hash."
+---
+
+Use `HKEYS` to get all fields in a hash.
+
+## Syntax
+
+```redis
+HKEYS <key>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of bulk-string fields |
+| RESP3 | Array of bulk-string fields |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.hset("key", {
+  id: 1,
+  username: "chronark",
+  });
+const fields = await redis.hkeys("key");
+console.log(fields); // ["id", "username"]
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.hkeys("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.hkeys("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.hKeys("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.hkeys("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.HKeys(context.Background(), "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.hkeys("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.hkeys("my-key")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/hash/hlen.mdx b/redis/commands/hash/hlen.mdx
new file mode 100644
index 000000000..a212ef54c
--- /dev/null
+++ b/redis/commands/hash/hlen.mdx
@@ -0,0 +1,169 @@
+---
+title: "HLEN"
+description: "Get number of fields in a hash."
+---
+
+Use `HLEN` to get number of fields in a hash.
+
+## Syntax
+
+```redis
+HLEN <key>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.hset("key", {
+  id: 1,
+  username: "chronark",
+  });
+const fields = await redis.hlen("key");
+console.log(fields); // 2
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.hlen("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.hlen("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.hLen("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.hlen("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.HLen(context.Background(), "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.hlen("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.hlen("my-key")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/hash/hmget.mdx b/redis/commands/hash/hmget.mdx
new file mode 100644
index 000000000..2896d7126
--- /dev/null
+++ b/redis/commands/hash/hmget.mdx
@@ -0,0 +1,171 @@
+---
+title: "HMGET"
+description: "Get values of multiple fields."
+---
+
+Use `HMGET` to get values of multiple fields.
+
+## Syntax
+
+```redis
+HMGET <key> <field> [<field> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<field>` | Yes | Yes | Hash field name. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of bulk-string values or null values, one per field |
+| RESP3 | Array of bulk-string values or null values, one per field |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.hset("key", {
+  id: 1,
+  username: "chronark",
+  name: "andreas"
+  });
+const fields = await redis.hmget("key", "username", "name");
+console.log(fields); // { username: "chronark", name: "andreas" }
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.hmget("my-key", "field")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.hmget("my-key", "field");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.hmGet("my-key", "field");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.hmget("my-key", ["field"])
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.HMGet(context.Background(), "my-key", "field").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.hmget("my-key", "field");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.hmget("my-key", &["field"])?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/hash/hmset.mdx b/redis/commands/hash/hmset.mdx
new file mode 100644
index 000000000..a03dc7453
--- /dev/null
+++ b/redis/commands/hash/hmset.mdx
@@ -0,0 +1,165 @@
+---
+title: "HMSET"
+description: "Set multiple hash fields."
+---
+
+Use `HMSET` to set multiple hash fields.
+
+## Syntax
+
+```redis
+HMSET <key> <field> <value> [<field> <value> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<field> <value>` | Yes | Yes | Field and the value to store in it. Repeat to set several fields in one call. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Simple string `OK` |
+| RESP3 | Simple string `OK` |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+const result = await redis.hmset("my-key", { field: "value" });
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.hmset("my-key", {"field": "value"})
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.hmset("my-key", "field", "value");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.hSet("my-key", { field: "value" });
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.hset("my-key", mapping={"field": "value"})
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.HMSet(context.Background(), "my-key", "field", "value").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.hmset("my-key", java.util.Map.of("field", "value"));
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.hset_multiple("my-key", &[("field", "value")])?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/hash/hpersist.mdx b/redis/commands/hash/hpersist.mdx
new file mode 100644
index 000000000..5ee8e3d11
--- /dev/null
+++ b/redis/commands/hash/hpersist.mdx
@@ -0,0 +1,170 @@
+---
+title: "HPERSIST"
+description: "Remove field expiration."
+---
+
+Use `HPERSIST` to remove field expiration.
+
+## Syntax
+
+```redis
+HPERSIST <key> FIELDS <numfields> <field> [<field> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `FIELDS <numfields> <field> [<field> ...]` | Yes | No | Fields to target. Give the field count first, then that many field names. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of integer status codes, one per field |
+| RESP3 | Array of integer status codes, one per field |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.hset("my-key", "my-field", "my-value");
+await redis.hpexpire("my-key", "my-field", 1000);
+
+const expirationRemoved = await redis.hpersist("my-key", "my-field");
+
+console.log(expirationRemoved); // [1]
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.hpersist("my-key", "field")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.hpersist("my-key", "FIELDS", "1", "field");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.hPersist("my-key", "field");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.hpersist("my-key", "field")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.HPersist(context.Background(), "my-key", "1", "field").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.hpersist("my-key", "1", "field");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.hpersist("my-key", &["field"])?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/hash/hpexpire.mdx b/redis/commands/hash/hpexpire.mdx
new file mode 100644
index 000000000..d248ee7e0
--- /dev/null
+++ b/redis/commands/hash/hpexpire.mdx
@@ -0,0 +1,175 @@
+---
+title: "HPEXPIRE"
+description: "Set field TTL in milliseconds."
+---
+
+Use `HPEXPIRE` to set field TTL in milliseconds.
+
+## Syntax
+
+```redis
+HPEXPIRE <key> <milliseconds> [NX | XX | GT | LT] FIELDS <numfields> <field> [<field> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<milliseconds>` | Yes | No | Lifetime in milliseconds. |
+| `(NX \| XX \| GT \| LT)` | No | No | Choose one form: `NX` (only when the field has no expiration); `XX` (only when the field already has one); `GT` (only when the new expiration is later than the current one); `LT` (only when it is earlier). |
+| `FIELDS <numfields> <field> [<field> ...]` | Yes | No | Fields to target. Give the field count first, then that many field names. |
+
+## Important points
+
+- `NX` cannot be combined with `XX`, `GT`, or `LT`, and `GT` and `LT` cannot be used together.
+- A field with no expiration counts as an infinite one, so `GT` never sets an expiration on such a field and `LT` always does.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of integer status codes, one per field |
+| RESP3 | Array of integer status codes, one per field |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.hset("my-key", "my-field", "my-value");
+const expirationSet = await redis.hpexpire("my-key", "my-field", 1000);
+
+console.log(expirationSet); // [1]
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.hpexpire("my-key", "field", 1000)
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.hpexpire("my-key", "1000", "FIELDS", "1", "field");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.hpExpire("my-key", "field", 1000);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.hpexpire("my-key", 1000, "field")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.HPExpire(context.Background(), "my-key", time.Second, "field").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.hpexpire("my-key", 1000, "field");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.hpexpire("my-key", 1000, redis::ExpireOption::NONE, &["field"])?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/hash/hpexpireat.mdx b/redis/commands/hash/hpexpireat.mdx
new file mode 100644
index 000000000..f1cc73bf9
--- /dev/null
+++ b/redis/commands/hash/hpexpireat.mdx
@@ -0,0 +1,175 @@
+---
+title: "HPEXPIREAT"
+description: "Set field expiry as ms timestamp."
+---
+
+Use `HPEXPIREAT` to set field expiry as ms timestamp.
+
+## Syntax
+
+```redis
+HPEXPIREAT <key> <unix-time-milliseconds> [NX | XX | GT | LT] FIELDS <numfields> <field> [<field> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<unix-time-milliseconds>` | Yes | No | Expiration time as a Unix timestamp in milliseconds. |
+| `(NX \| XX \| GT \| LT)` | No | No | Choose one form: `NX` (only when the field has no expiration); `XX` (only when the field already has one); `GT` (only when the new expiration is later than the current one); `LT` (only when it is earlier). |
+| `FIELDS <numfields> <field> [<field> ...]` | Yes | No | Fields to target. Give the field count first, then that many field names. |
+
+## Important points
+
+- `NX` cannot be combined with `XX`, `GT`, or `LT`, and `GT` and `LT` cannot be used together.
+- A field with no expiration counts as an infinite one, so `GT` never sets an expiration on such a field and `LT` always does.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of integer status codes, one per field |
+| RESP3 | Array of integer status codes, one per field |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.hset("my-key", "my-field", "my-value");
+const expirationSet = await redis.hpexpireat("my-key", "my-field", Date.now() + 1000);
+
+console.log(expirationSet); // [1]
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.hpexpireat("my-key", "field", 1735689600)
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.hpexpireat("my-key", "1735689600", "FIELDS", "1", "field");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.hpExpireAt("my-key", "field", 1735689600);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.hpexpireat("my-key", 1735689600, "field")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.HPExpireAt(context.Background(), "my-key", time.UnixMilli(1735689600), "field").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.hpexpireAt("my-key", 1735689600, "field");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.hpexpire_at("my-key", 1735689600, redis::ExpireOption::NONE, &["field"])?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/hash/hpexpiretime.mdx b/redis/commands/hash/hpexpiretime.mdx
new file mode 100644
index 000000000..6a33bd761
--- /dev/null
+++ b/redis/commands/hash/hpexpiretime.mdx
@@ -0,0 +1,173 @@
+---
+title: "HPEXPIRETIME"
+description: "Get field expiry as ms timestamp."
+---
+
+Use `HPEXPIRETIME` to get field expiry as ms timestamp.
+
+## Syntax
+
+```redis
+HPEXPIRETIME <key> FIELDS <numfields> <field> [<field> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `FIELDS <numfields> <field> [<field> ...]` | Yes | No | Fields to target. Give the field count first, then that many field names. |
+
+## Important points
+
+- Negative integer replies are sentinel values, not durations or timestamps; see the response description for missing or persistent data.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of expiration timestamps or negative integer status codes, one per field |
+| RESP3 | Array of expiration timestamps or negative integer status codes, one per field |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.hset("my-key", "my-field", "my-value");
+await redis.hpexpireat("my-key", "my-field", Date.now() + 1000);
+const expireTime = await redis.hpexpiretime("my-key", "my-field");
+
+console.log(expireTime); // e.g., 1697059200000
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.hpexpiretime("my-key", "field")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.hpexpiretime("my-key", "FIELDS", "1", "field");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.hpExpireTime("my-key", "field");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.hpexpiretime("my-key", "field")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.HPExpireTime(context.Background(), "my-key", "1", "field").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.hpexpireTime("my-key", "1", "field");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.hpexpire_time("my-key", &["field"])?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/hash/hpttl.mdx b/redis/commands/hash/hpttl.mdx
new file mode 100644
index 000000000..e5fe97277
--- /dev/null
+++ b/redis/commands/hash/hpttl.mdx
@@ -0,0 +1,173 @@
+---
+title: "HPTTL"
+description: "Get field TTL in milliseconds."
+---
+
+Use `HPTTL` to get field TTL in milliseconds.
+
+## Syntax
+
+```redis
+HPTTL <key> FIELDS <numfields> <field> [<field> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `FIELDS <numfields> <field> [<field> ...]` | Yes | No | Fields to target. Give the field count first, then that many field names. |
+
+## Important points
+
+- Negative integer replies are sentinel values, not durations or timestamps; see the response description for missing or persistent data.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of TTL values or negative integer status codes, one per field |
+| RESP3 | Array of TTL values or negative integer status codes, one per field |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.hset("my-key", "my-field", "my-value");
+await redis.hpexpire("my-key", "my-field", 1000);
+const ttl = await redis.hpttl("my-key", "my-field");
+
+console.log(ttl); // e.g., [950]
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.hpttl("my-key", "field")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.hpttl("my-key", "FIELDS", "1", "field");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.hpTTL("my-key", "field");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.hpttl("my-key", "field")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.HPTTL(context.Background(), "my-key", "1", "field").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.hpttl("my-key", "1", "field");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.hpttl("my-key", &["field"])?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/hash/hrandfield.mdx b/redis/commands/hash/hrandfield.mdx
new file mode 100644
index 000000000..406a79257
--- /dev/null
+++ b/redis/commands/hash/hrandfield.mdx
@@ -0,0 +1,175 @@
+---
+title: "HRANDFIELD"
+description: "Get random fields from a hash."
+---
+
+Use `HRANDFIELD` to get random fields from a hash.
+
+## Syntax
+
+```redis
+HRANDFIELD <key> [<count> [WITHVALUES]]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<count> [WITHVALUES]` | No | No | Number of fields to return; a negative count may repeat fields. `WITHVALUES` also returns each field's value. |
+
+## Important points
+
+- Pair-based results may be flattened into one alternating array in RESP2 while RESP3 preserves nested pairs or a map.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Null bulk string or null array, Bulk string, array of fields, or flat field/value array |
+| RESP3 | Null, Bulk string, array of fields, or array of field/value pairs |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.hset("key", {
+  id: 1,
+  username: "chronark",
+  name: "andreas"
+ });
+const randomField = await redis.hrandfield("key");
+console.log(randomField); // one of "id", "username" or  "name"
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.hrandfield("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.hrandfield("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.hRandField("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.hrandfield("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.HRandField(context.Background(), "my-key", 1).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.hrandfield("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("HRANDFIELD");
+    command.arg("my-key");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/hash/hscan.mdx b/redis/commands/hash/hscan.mdx
new file mode 100644
index 000000000..078ea959b
--- /dev/null
+++ b/redis/commands/hash/hscan.mdx
@@ -0,0 +1,181 @@
+---
+title: "HSCAN"
+description: "Incrementally iterate hash fields."
+---
+
+Use `HSCAN` to incrementally iterate hash fields.
+
+## Syntax
+
+```redis
+HSCAN <key> <cursor> [MATCH <pattern>] [COUNT <count>] [NOVALUES]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<cursor>` | Yes | No | Cursor returned by the previous call; start at `0`. |
+| `MATCH <pattern>` | No | No | Return only elements matching this glob-style pattern. |
+| `COUNT <count>` | No | No | Hint for how much work each iteration should do. |
+| `NOVALUES` | No | No | Return only field names, without their values. |
+
+## Important points
+
+- This operation can inspect a large part of the database. Prefer cursor-based scans where possible and avoid unbounded use on hot paths.
+- The cursor is opaque. Start with `0` and continue until the server returns cursor `0`; a single iteration may return no elements.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Two-element array: cursor and flat field/value array, or field array with `NOVALUES` |
+| RESP3 | Two-element array: cursor and flat field/value array, or field array with `NOVALUES` |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.hset("key", {
+  id: 1,
+  username: "chronark",
+  name: "andreas"
+ });
+const [newCursor, fields] = await redis.hscan("key", 0);
+console.log(newCursor); // likely `0` since this is a very small hash
+console.log(fields); // ["id", 1, "username", "chronark", "name", "andreas"]
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.hscan("my-key", 0)
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.hscan("my-key", "0");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.hScan("my-key", "0");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.hscan("my-key", 0)
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, _, err := client.HScan(context.Background(), "my-key", 0, "*", 0).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.hscan("my-key", "0");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("HSCAN");
+    command.arg("my-key");
+    command.arg("0");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/hash/hset.mdx b/redis/commands/hash/hset.mdx
new file mode 100644
index 000000000..137c51da1
--- /dev/null
+++ b/redis/commands/hash/hset.mdx
@@ -0,0 +1,169 @@
+---
+title: "HSET"
+description: "Set hash field values."
+---
+
+Use `HSET` to set hash field values.
+
+## Syntax
+
+```redis
+HSET <key> <field> <value> [<field> <value> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<field> <value>` | Yes | Yes | Field and the value to store in it. Repeat to set several fields in one call. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.hset("key", {
+  id: 1,
+  username: "chronark",
+  name: "andreas"
+  });
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.hset("my-key", "field", "value")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.hset("my-key", "field", "value");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.hSet("my-key", "field", "value");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.hset("my-key", "field", "value")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.HSet(context.Background(), "my-key", "field", "value").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.hset("my-key", "field", "value");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.hset("my-key", "field", "value")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/hash/hsetex.mdx b/redis/commands/hash/hsetex.mdx
new file mode 100644
index 000000000..59fe51c45
--- /dev/null
+++ b/redis/commands/hash/hsetex.mdx
@@ -0,0 +1,175 @@
+---
+title: "HSETEX"
+description: "Set fields with expiration."
+---
+
+Use `HSETEX` to set fields with expiration.
+
+## Syntax
+
+```redis
+HSETEX <key> [FNX | FXX] [EX <seconds> | PX <milliseconds> | EXAT <unix-time-seconds> | PXAT <unix-time-milliseconds> | KEEPTTL] FIELDS <numfields> <field> <value> [<field> <value> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `(FNX \| FXX)` | No | No | Choose one form: `FNX`; `FXX`. |
+| `(EX <seconds> \| PX <milliseconds> \| EXAT <unix-time-seconds> \| PXAT <unix-time-milliseconds> \| KEEPTTL)` | No | No | Choose one form: `EX` (set a lifetime in seconds); `PX` (set a lifetime in milliseconds); `EXAT` (expire at a Unix timestamp in seconds); `PXAT` (expire at a Unix timestamp in milliseconds); `KEEPTTL` (preserve the existing key lifetime). |
+| `FIELDS <numfields> <field> <value> [<field> <value> ...]` | Yes | No | Field-value pairs to set. Give the pair count first, then that many field and value pairs. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer: `1` if the fields were set, `0` otherwise |
+| RESP3 | Integer: `1` if the fields were set, `0` otherwise |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+// Set fields with 1 hour expiration
+await redis.hsetex("user:123", { expiration: { ex: 3600 } }, {
+  name: "John",
+  email: "john@example.com"
+});
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.hsetex("my-key", field="field", value="value")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.hsetex("my-key", "FIELDS", "1", "field", "value");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.hSetEx("my-key", { field: "value" });
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.hsetex("my-key", mapping={"field": "value"})
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.HSetEX(context.Background(), "my-key", "1", "field", "value").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.hsetex("my-key", redis.clients.jedis.params.HSetExParams.hSetExParams(), "field", "value");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("HSETEX");
+    command.arg("my-key");
+    command.arg("FIELDS");
+    command.arg("1");
+    command.arg("field");
+    command.arg("value");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/hash/hsetnx.mdx b/redis/commands/hash/hsetnx.mdx
new file mode 100644
index 000000000..70a359a97
--- /dev/null
+++ b/redis/commands/hash/hsetnx.mdx
@@ -0,0 +1,166 @@
+---
+title: "HSETNX"
+description: "Set field only if it doesn't exist."
+---
+
+Use `HSETNX` to set field only if it doesn't exist.
+
+## Syntax
+
+```redis
+HSETNX <key> <field> <value>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<field>` | Yes | No | Hash field name. |
+| `<value>` | Yes | No | Value to store in the field. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer: `1` if the field was set, `0` if it already exists |
+| RESP3 | Integer: `1` if the field was set, `0` if it already exists |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.hsetnx("key", "id", 1)
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.hsetnx("my-key", "field", "value")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.hsetnx("my-key", "field", "value");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.hSetNX("my-key", "field", "value");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.hsetnx("my-key", "field", "value")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.HSetNX(context.Background(), "my-key", "field", "value").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.hsetnx("my-key", "field", "value");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.hset_nx("my-key", "field", "value")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/hash/hstrlen.mdx b/redis/commands/hash/hstrlen.mdx
new file mode 100644
index 000000000..0baa104eb
--- /dev/null
+++ b/redis/commands/hash/hstrlen.mdx
@@ -0,0 +1,166 @@
+---
+title: "HSTRLEN"
+description: "Get length of a field's value."
+---
+
+Use `HSTRLEN` to get length of a field's value.
+
+## Syntax
+
+```redis
+HSTRLEN <key> <field>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<field>` | Yes | No | Hash field name. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const length = await redis.hstrlen("key", "field")
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.hstrlen("my-key", "field")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.hstrlen("my-key", "field");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.hStrLen("my-key", "field");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.hstrlen("my-key", "field")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.HStrLen(context.Background(), "my-key", "field").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.hstrlen("my-key", "field");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("HSTRLEN");
+    command.arg("my-key");
+    command.arg("field");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/hash/httl.mdx b/redis/commands/hash/httl.mdx
new file mode 100644
index 000000000..ecff590a6
--- /dev/null
+++ b/redis/commands/hash/httl.mdx
@@ -0,0 +1,173 @@
+---
+title: "HTTL"
+description: "Get field TTL in seconds."
+---
+
+Use `HTTL` to get field TTL in seconds.
+
+## Syntax
+
+```redis
+HTTL <key> FIELDS <numfields> <field> [<field> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `FIELDS <numfields> <field> [<field> ...]` | Yes | No | Fields to target. Give the field count first, then that many field names. |
+
+## Important points
+
+- Negative integer replies are sentinel values, not durations or timestamps; see the response description for missing or persistent data.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of TTL values or negative integer status codes, one per field |
+| RESP3 | Array of TTL values or negative integer status codes, one per field |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.hset("my-key", "my-field", "my-value");
+await redis.hexpire("my-key", "my-field", 10);
+const ttl = await redis.httl("my-key", "my-field");
+
+console.log(ttl); // e.g., [9]
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.httl("my-key", "field")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.httl("my-key", "FIELDS", "1", "field");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.hTTL("my-key", "field");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.httl("my-key", "field")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.HTTL(context.Background(), "my-key", "1", "field").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.httl("my-key", "1", "field");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.httl("my-key", &["field"])?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/hash/hvals.mdx b/redis/commands/hash/hvals.mdx
new file mode 100644
index 000000000..a5203f676
--- /dev/null
+++ b/redis/commands/hash/hvals.mdx
@@ -0,0 +1,169 @@
+---
+title: "HVALS"
+description: "Get all values in a hash."
+---
+
+Use `HVALS` to get all values in a hash.
+
+## Syntax
+
+```redis
+HVALS <key>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of bulk-string values |
+| RESP3 | Array of bulk-string values |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.hset("key", {
+  field1: "Hello",
+  field2: "World",
+})
+const values = await redis.hvals("key")
+console.log(values) // ["Hello", "World"]
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.hvals("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.hvals("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.hVals("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.hvals("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.HVals(context.Background(), "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.hvals("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.hvals("my-key")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/hash/overview.mdx b/redis/commands/hash/overview.mdx
new file mode 100644
index 000000000..16f428d77
--- /dev/null
+++ b/redis/commands/hash/overview.mdx
@@ -0,0 +1,37 @@
+---
+title: "Hash commands"
+sidebarTitle: "Overview"
+description: "Commands for storing and manipulating field-value collections."
+---
+
+<CardGroup cols={2}>
+<Card title="HDEL" href="/redis/commands/hash/hdel">Delete one or more hash fields</Card>
+<Card title="HEXISTS" href="/redis/commands/hash/hexists">Check if a hash field exists</Card>
+<Card title="HEXPIRE" href="/redis/commands/hash/hexpire">Set field TTL in seconds</Card>
+<Card title="HEXPIREAT" href="/redis/commands/hash/hexpireat">Set field expiry as timestamp</Card>
+<Card title="HEXPIRETIME" href="/redis/commands/hash/hexpiretime">Get field expiry as timestamp</Card>
+<Card title="HGET" href="/redis/commands/hash/hget">Get the value of a hash field</Card>
+<Card title="HGETALL" href="/redis/commands/hash/hgetall">Get all fields and values</Card>
+<Card title="HGETDEL" href="/redis/commands/hash/hgetdel">Get and delete hash fields</Card>
+<Card title="HGETEX" href="/redis/commands/hash/hgetex">Get fields and set their expiry</Card>
+<Card title="HINCRBY" href="/redis/commands/hash/hincrby">Increment integer value of a field</Card>
+<Card title="HINCRBYFLOAT" href="/redis/commands/hash/hincrbyfloat">Increment float value of a field</Card>
+<Card title="HKEYS" href="/redis/commands/hash/hkeys">Get all fields in a hash</Card>
+<Card title="HLEN" href="/redis/commands/hash/hlen">Get number of fields in a hash</Card>
+<Card title="HMGET" href="/redis/commands/hash/hmget">Get values of multiple fields</Card>
+<Card title="HMSET" href="/redis/commands/hash/hmset">Set multiple hash fields</Card>
+<Card title="HPERSIST" href="/redis/commands/hash/hpersist">Remove field expiration</Card>
+<Card title="HPEXPIRE" href="/redis/commands/hash/hpexpire">Set field TTL in milliseconds</Card>
+<Card title="HPEXPIREAT" href="/redis/commands/hash/hpexpireat">Set field expiry as ms timestamp</Card>
+<Card title="HPEXPIRETIME" href="/redis/commands/hash/hpexpiretime">Get field expiry as ms timestamp</Card>
+<Card title="HPTTL" href="/redis/commands/hash/hpttl">Get field TTL in milliseconds</Card>
+<Card title="HRANDFIELD" href="/redis/commands/hash/hrandfield">Get random fields from a hash</Card>
+<Card title="HSCAN" href="/redis/commands/hash/hscan">Incrementally iterate hash fields</Card>
+<Card title="HSET" href="/redis/commands/hash/hset">Set hash field values</Card>
+<Card title="HSETEX" href="/redis/commands/hash/hsetex">Set fields with expiration</Card>
+<Card title="HSETNX" href="/redis/commands/hash/hsetnx">Set field only if it doesn't exist</Card>
+<Card title="HSTRLEN" href="/redis/commands/hash/hstrlen">Get length of a field's value</Card>
+<Card title="HTTL" href="/redis/commands/hash/httl">Get field TTL in seconds</Card>
+<Card title="HVALS" href="/redis/commands/hash/hvals">Get all values in a hash</Card>
+</CardGroup>
+
diff --git a/redis/commands/hyperloglog/overview.mdx b/redis/commands/hyperloglog/overview.mdx
new file mode 100644
index 000000000..104ff6fa0
--- /dev/null
+++ b/redis/commands/hyperloglog/overview.mdx
@@ -0,0 +1,12 @@
+---
+title: "HyperLogLog commands"
+sidebarTitle: "Overview"
+description: "Commands for probabilistic cardinality estimation."
+---
+
+<CardGroup cols={2}>
+<Card title="PFADD" href="/redis/commands/hyperloglog/pfadd">Add elements to HyperLogLog</Card>
+<Card title="PFCOUNT" href="/redis/commands/hyperloglog/pfcount">Get estimated cardinality</Card>
+<Card title="PFMERGE" href="/redis/commands/hyperloglog/pfmerge">Merge multiple HyperLogLogs</Card>
+</CardGroup>
+
diff --git a/redis/commands/hyperloglog/pfadd.mdx b/redis/commands/hyperloglog/pfadd.mdx
new file mode 100644
index 000000000..a3cda9b5b
--- /dev/null
+++ b/redis/commands/hyperloglog/pfadd.mdx
@@ -0,0 +1,165 @@
+---
+title: "PFADD"
+description: "Add elements to HyperLogLog."
+---
+
+Use `PFADD` to add elements to HyperLogLog.
+
+## Syntax
+
+```redis
+PFADD <key> [<element> [<element> ...]]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<element>` | No | Yes | Element to add to the HyperLogLog. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer: `1` if at least one internal register was altered, `0` otherwise |
+| RESP3 | Integer: `1` if at least one internal register was altered, `0` otherwise |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+const result = await redis.pfadd("my-key", "element");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.pfadd("my-key", "member")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.pfadd("my-key", "element");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.pfAdd("my-key", "element");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.pfadd("my-key", "member")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.PFAdd(context.Background(), "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.pfadd("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.pfadd("my-key", &["member"])?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/hyperloglog/pfcount.mdx b/redis/commands/hyperloglog/pfcount.mdx
new file mode 100644
index 000000000..adc886b1a
--- /dev/null
+++ b/redis/commands/hyperloglog/pfcount.mdx
@@ -0,0 +1,164 @@
+---
+title: "PFCOUNT"
+description: "Get estimated cardinality."
+---
+
+Use `PFCOUNT` to get estimated cardinality.
+
+## Syntax
+
+```redis
+PFCOUNT <key> [<key> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | Yes | Redis key targeted by the command. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+const result = await redis.pfcount("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.pfcount("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.pfcount("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.pfCount("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.pfcount("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.PFCount(context.Background(), "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.pfcount("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.pfcount(&["my-key"])?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/hyperloglog/pfmerge.mdx b/redis/commands/hyperloglog/pfmerge.mdx
new file mode 100644
index 000000000..5e1cbd3c7
--- /dev/null
+++ b/redis/commands/hyperloglog/pfmerge.mdx
@@ -0,0 +1,165 @@
+---
+title: "PFMERGE"
+description: "Merge multiple HyperLogLogs."
+---
+
+Use `PFMERGE` to merge multiple HyperLogLogs.
+
+## Syntax
+
+```redis
+PFMERGE <destkey> [<sourcekey> [<sourcekey> ...]]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<destkey>` | Yes | No | Redis key used as destkey. |
+| `<sourcekey>` | No | Yes | Redis key used as sourcekey. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Simple string `OK` |
+| RESP3 | Simple string `OK` |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+const result = await redis.pfmerge("destination-key", "source-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.pfmerge("destination-key", "source-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.pfmerge("destination-key", "source-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.pfMerge("destination-key", "source-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.pfmerge("destination-key", "source-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.PFMerge(context.Background(), "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.pfmerge("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.pfmerge("destination-key", &["source-key"])?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/json/json-arrappend.mdx b/redis/commands/json/json-arrappend.mdx
new file mode 100644
index 000000000..52cebfd40
--- /dev/null
+++ b/redis/commands/json/json-arrappend.mdx
@@ -0,0 +1,171 @@
+---
+title: "JSON.ARRAPPEND"
+description: "Append values to JSON array."
+---
+
+Use `JSON.ARRAPPEND` to append values to JSON array.
+
+## Syntax
+
+```redis
+JSON.ARRAPPEND <key> <path> <value> [value ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `key` | Yes | No | JSON document key. |
+| `path` | Yes | No | Path selecting arrays. |
+| `value` | Yes | Yes | Valid JSON value to append. |
+
+## Important points
+
+- Raw TCP examples pass JSON values as valid JSON text. Typed Upstash SDK helpers serialize native objects and values for you.
+- Paths beginning with `$` use JSONPath and can match multiple values, so many JSON commands return an array of per-match results.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of integer lengths or null values, one per matched path |
+| RESP3 | Array of integer lengths or null values, one per matched path |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.json.arrappend("key", "$.path.to.array", "a");
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.json().arrappend("profile", "$.tags", "new")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.call("JSON.ARRAPPEND", "profile", "$.tags", "\"new\"");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.json.arrAppend("profile", "$.tags", "new");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.json().arrappend("profile", "$.tags", "new")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.JSONArrAppend(context.Background(), "profile", "$.tags", "new").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.JedisPooled;
+
+try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.jsonArrAppend("profile", new redis.clients.jedis.json.Path("$.tags"), "new");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::JsonCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result: redis::Value = connection.json_arr_append("profile", "$.tags", &"new")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/json/json-arrindex.mdx b/redis/commands/json/json-arrindex.mdx
new file mode 100644
index 000000000..5ebfebeb8
--- /dev/null
+++ b/redis/commands/json/json-arrindex.mdx
@@ -0,0 +1,173 @@
+---
+title: "JSON.ARRINDEX"
+description: "Find index of value in array."
+---
+
+Use `JSON.ARRINDEX` to find index of value in array.
+
+## Syntax
+
+```redis
+JSON.ARRINDEX <key> <path> <value> [start [stop]]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `key` | Yes | No | JSON document key. |
+| `path` | Yes | No | Path selecting arrays. |
+| `value` | Yes | No | Valid JSON value to locate. |
+| `start` | No | No | Inclusive starting index. |
+| `stop` | No | No | Exclusive ending index. |
+
+## Important points
+
+- Raw TCP examples pass JSON values as valid JSON text. Typed Upstash SDK helpers serialize native objects and values for you.
+- Paths beginning with `$` use JSONPath and can match multiple values, so many JSON commands return an array of per-match results.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of integer indexes or null values, one per matched path |
+| RESP3 | Array of integer indexes or null values, one per matched path |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const index = await redis.json.arrindex("key", "$.path.to.array", "a");
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.json().arrindex("profile", "$.tags", "new")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.call("JSON.ARRINDEX", "profile", "$.tags", "\"new\"");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.json.arrIndex("profile", "$.tags", "new");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.json().arrindex("profile", "$.tags", "new")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.JSONArrIndex(context.Background(), "profile", "$.tags", "new").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.JedisPooled;
+
+try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.jsonArrIndex("profile", new redis.clients.jedis.json.Path("$.tags"), "new");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::JsonCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result: redis::Value = connection.json_arr_index("profile", "$.tags", &"new")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/json/json-arrinsert.mdx b/redis/commands/json/json-arrinsert.mdx
new file mode 100644
index 000000000..4ee00277a
--- /dev/null
+++ b/redis/commands/json/json-arrinsert.mdx
@@ -0,0 +1,172 @@
+---
+title: "JSON.ARRINSERT"
+description: "Insert values into JSON array."
+---
+
+Use `JSON.ARRINSERT` to insert values into JSON array.
+
+## Syntax
+
+```redis
+JSON.ARRINSERT <key> <path> <index> <value> [value ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `key` | Yes | No | JSON document key. |
+| `path` | Yes | No | Path selecting arrays. |
+| `index` | Yes | No | Insertion index; negative indexes count from the end. |
+| `value` | Yes | Yes | Valid JSON value to insert. |
+
+## Important points
+
+- Raw TCP examples pass JSON values as valid JSON text. Typed Upstash SDK helpers serialize native objects and values for you.
+- Paths beginning with `$` use JSONPath and can match multiple values, so many JSON commands return an array of per-match results.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of integer lengths or null values, one per matched path |
+| RESP3 | Array of integer lengths or null values, one per matched path |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const length = await redis.json.arrinsert("key", "$.path.to.array", 2, "a", "b");
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.json().arrinsert("profile", "$.tags", 0, "first")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.call("JSON.ARRINSERT", "profile", "$.tags", "0", "\"first\"");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.json.arrInsert("profile", "$.tags", 0, "first");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.json().arrinsert("profile", "$.tags", 0, "first")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.JSONArrInsert(context.Background(), "profile", "$.tags", 0, "first").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.JedisPooled;
+
+try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.jsonArrInsert("profile", new redis.clients.jedis.json.Path("$.tags"), 0, "first");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::JsonCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result: redis::Value = connection.json_arr_insert("profile", "$.tags", 0, &"first")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/json/json-arrlen.mdx b/redis/commands/json/json-arrlen.mdx
new file mode 100644
index 000000000..b20916421
--- /dev/null
+++ b/redis/commands/json/json-arrlen.mdx
@@ -0,0 +1,170 @@
+---
+title: "JSON.ARRLEN"
+description: "Get JSON array length."
+---
+
+Use `JSON.ARRLEN` to get JSON array length.
+
+## Syntax
+
+```redis
+JSON.ARRLEN <key> [path]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `key` | Yes | No | JSON document key. |
+| `path` | No | No | Path selecting arrays; defaults to the root. |
+
+## Important points
+
+- Raw TCP examples pass JSON values as valid JSON text. Typed Upstash SDK helpers serialize native objects and values for you.
+- Paths beginning with `$` use JSONPath and can match multiple values, so many JSON commands return an array of per-match results.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of integer lengths or null values, one per matched path |
+| RESP3 | Array of integer lengths or null values, one per matched path |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const length = await redis.json.arrlen("key", "$.path.to.array");
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.json().arrlen("profile", "$.tags")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.call("JSON.ARRLEN", "profile", "$.tags");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.json.arrLen("profile", { path: "$.tags" });
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.json().arrlen("profile", "$.tags")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.JSONArrLen(context.Background(), "profile", "$.tags").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.JedisPooled;
+
+try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.jsonArrLen("profile", new redis.clients.jedis.json.Path("$.tags"));
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::JsonCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result: redis::Value = connection.json_arr_len("profile", "$.tags")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/json/json-arrpop.mdx b/redis/commands/json/json-arrpop.mdx
new file mode 100644
index 000000000..8d549bd8e
--- /dev/null
+++ b/redis/commands/json/json-arrpop.mdx
@@ -0,0 +1,171 @@
+---
+title: "JSON.ARRPOP"
+description: "Pop value from JSON array."
+---
+
+Use `JSON.ARRPOP` to pop value from JSON array.
+
+## Syntax
+
+```redis
+JSON.ARRPOP <key> [path [index]]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `key` | Yes | No | JSON document key. |
+| `path` | No | No | Path selecting arrays; defaults to the root. |
+| `index` | No | No | Element index; defaults to the last element. |
+
+## Important points
+
+- Raw TCP examples pass JSON values as valid JSON text. Typed Upstash SDK helpers serialize native objects and values for you.
+- Paths beginning with `$` use JSONPath and can match multiple values, so many JSON commands return an array of per-match results.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of bulk-string JSON values or null values, one per matched path |
+| RESP3 | Array of bulk-string JSON values or null values, one per matched path |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const element = await redis.json.arrpop("key", "$.path.to.array");
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.json().arrpop("profile", "$.tags", -1)
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.call("JSON.ARRPOP", "profile", "$.tags", "-1");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.json.arrPop("profile", { path: "$.tags", index: -1 });
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.json().arrpop("profile", "$.tags", -1)
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.JSONArrPop(context.Background(), "profile", "$.tags", -1).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.JedisPooled;
+
+try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.jsonArrPop("profile", new redis.clients.jedis.json.Path("$.tags"), -1);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::JsonCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result: redis::Value = connection.json_arr_pop("profile", "$.tags", -1)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/json/json-arrtrim.mdx b/redis/commands/json/json-arrtrim.mdx
new file mode 100644
index 000000000..b96952495
--- /dev/null
+++ b/redis/commands/json/json-arrtrim.mdx
@@ -0,0 +1,172 @@
+---
+title: "JSON.ARRTRIM"
+description: "Trim JSON array to range."
+---
+
+Use `JSON.ARRTRIM` to trim JSON array to range.
+
+## Syntax
+
+```redis
+JSON.ARRTRIM <key> <path> <start> <stop>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `key` | Yes | No | JSON document key. |
+| `path` | Yes | No | Path selecting arrays. |
+| `start` | Yes | No | Inclusive first index to keep. |
+| `stop` | Yes | No | Inclusive last index to keep. |
+
+## Important points
+
+- Raw TCP examples pass JSON values as valid JSON text. Typed Upstash SDK helpers serialize native objects and values for you.
+- Paths beginning with `$` use JSONPath and can match multiple values, so many JSON commands return an array of per-match results.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of integer lengths or null values, one per matched path |
+| RESP3 | Array of integer lengths or null values, one per matched path |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const length = await redis.json.arrtrim("key", "$.path.to.array", 2, 10);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.json().arrtrim("profile", "$.tags", 0, 9)
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.call("JSON.ARRTRIM", "profile", "$.tags", "0", "9");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.json.arrTrim("profile", "$.tags", 0, 9);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.json().arrtrim("profile", "$.tags", 0, 9)
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.JSONArrTrimWithArgs(context.Background(), "profile", "$.tags", &redis.JSONArrTrimArgs{Start: 0, Stop: func() *int { stop := 9; return &stop }()}).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.JedisPooled;
+
+try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.jsonArrTrim("profile", new redis.clients.jedis.json.Path("$.tags"), 0, 9);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::JsonCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result: redis::Value = connection.json_arr_trim("profile", "$.tags", 0, 9)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/json/json-clear.mdx b/redis/commands/json/json-clear.mdx
new file mode 100644
index 000000000..d2c3dd212
--- /dev/null
+++ b/redis/commands/json/json-clear.mdx
@@ -0,0 +1,170 @@
+---
+title: "JSON.CLEAR"
+description: "Clear JSON values."
+---
+
+Use `JSON.CLEAR` to clear JSON values.
+
+## Syntax
+
+```redis
+JSON.CLEAR <key> [path]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `key` | Yes | No | JSON document key. |
+| `path` | No | No | Path to containers or numbers; defaults to the root. |
+
+## Important points
+
+- Raw TCP examples pass JSON values as valid JSON text. Typed Upstash SDK helpers serialize native objects and values for you.
+- Paths beginning with `$` use JSONPath and can match multiple values, so many JSON commands return an array of per-match results.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.json.clear("key");
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.json().clear("profile", "$.stats")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.call("JSON.CLEAR", "profile", "$.stats");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.json.clear("profile", { path: "$.stats" });
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.json().clear("profile", "$.stats")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.JSONClear(context.Background(), "profile", "$.stats").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.JedisPooled;
+
+try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.jsonClear("profile", new redis.clients.jedis.json.Path("$.stats"));
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::JsonCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result: redis::Value = connection.json_clear("profile", "$.stats")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/json/json-debug.mdx b/redis/commands/json/json-debug.mdx
new file mode 100644
index 000000000..1443580b0
--- /dev/null
+++ b/redis/commands/json/json-debug.mdx
@@ -0,0 +1,167 @@
+---
+title: "JSON.DEBUG"
+description: "Inspect JSON memory usage."
+---
+
+Use `JSON.DEBUG` to inspect JSON memory usage.
+
+## Syntax
+
+```redis
+JSON.DEBUG MEMORY <key> [path]
+JSON.DEBUG HELP
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `MEMORY` | One form | No | Report the approximate memory used by the JSON value selected by key and optional path. |
+| `key` | For MEMORY | No | JSON document key. |
+| `path` | No | No | JSONPath to inspect; defaults to the root. |
+| `HELP` | One form | No | Return the supported JSON.DEBUG forms. |
+
+## Important points
+
+- Raw TCP examples pass JSON values as valid JSON text. Typed Upstash SDK helpers serialize native objects and values for you.
+- Paths beginning with `$` use JSONPath and can match multiple values, so many JSON commands return an array of per-match results.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer, array of integers, or array of help strings |
+| RESP3 | Integer, array of integers, or array of help strings |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+<Note>
+  This command is not supported yet in `upstash_redis`.
+</Note>
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.call("JSON.DEBUG", "MEMORY", "profile", "$.stats");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.json.debugMemory("profile", { path: "$.stats" });
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.json().debug("MEMORY", "profile", "$.stats")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.JSONDebugMemory(context.Background(), "profile", "$.stats").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.JedisPooled;
+
+try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.jsonDebugMemory("profile", new redis.clients.jedis.json.Path("$.stats"));
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("JSON.DEBUG");
+    command.arg("MEMORY");
+    command.arg("profile");
+    command.arg("$.stats");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/json/json-del.mdx b/redis/commands/json/json-del.mdx
new file mode 100644
index 000000000..ed66ab693
--- /dev/null
+++ b/redis/commands/json/json-del.mdx
@@ -0,0 +1,170 @@
+---
+title: "JSON.DEL"
+description: "Delete JSON values."
+---
+
+Use `JSON.DEL` to delete JSON values.
+
+## Syntax
+
+```redis
+JSON.DEL <key> [path]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `key` | Yes | No | JSON document key. |
+| `path` | No | No | Path to delete; omitting it deletes the whole key. |
+
+## Important points
+
+- Raw TCP examples pass JSON values as valid JSON text. Typed Upstash SDK helpers serialize native objects and values for you.
+- Paths beginning with `$` use JSONPath and can match multiple values, so many JSON commands return an array of per-match results.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.json.del("key", "$.path.to.value");
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.json().delete("profile", "$.temporary")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.call("JSON.DEL", "profile", "$.temporary");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.json.del("profile", { path: "$.temporary" });
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.json().delete("profile", "$.temporary")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.JSONDel(context.Background(), "profile", "$.temporary").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.JedisPooled;
+
+try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.jsonDel("profile", new redis.clients.jedis.json.Path("$.temporary"));
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::JsonCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result: redis::Value = connection.json_del("profile", "$.temporary")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/json/json-forget.mdx b/redis/commands/json/json-forget.mdx
new file mode 100644
index 000000000..7fd5da321
--- /dev/null
+++ b/redis/commands/json/json-forget.mdx
@@ -0,0 +1,170 @@
+---
+title: "JSON.FORGET"
+description: "Alias for JSON.DEL."
+---
+
+Use `JSON.FORGET` to alias for JSON.DEL.
+
+## Syntax
+
+```redis
+JSON.FORGET <key> [path]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `key` | Yes | No | JSON document key. |
+| `path` | No | No | Path to delete; omitting it deletes the whole key. |
+
+## Important points
+
+- Raw TCP examples pass JSON values as valid JSON text. Typed Upstash SDK helpers serialize native objects and values for you.
+- Paths beginning with `$` use JSONPath and can match multiple values, so many JSON commands return an array of per-match results.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.json.forget("key", "$.path.to.value");
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.json().forget("profile", "$.temporary")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.call("JSON.FORGET", "profile", "$.temporary");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.json.forget("profile", { path: "$.temporary" });
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.json().forget("profile", "$.temporary")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.JSONForget(context.Background(), "profile", "$.temporary").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.JedisPooled;
+
+try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.jsonDel("profile", new redis.clients.jedis.json.Path("$.temporary"));
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::JsonCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result: redis::Value = connection.json_del("profile", "$.temporary")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/json/json-get.mdx b/redis/commands/json/json-get.mdx
new file mode 100644
index 000000000..7b365d10b
--- /dev/null
+++ b/redis/commands/json/json-get.mdx
@@ -0,0 +1,173 @@
+---
+title: "JSON.GET"
+description: "Get JSON values."
+---
+
+Use `JSON.GET` to get JSON values.
+
+## Syntax
+
+```redis
+JSON.GET <key> [INDENT indent] [NEWLINE newline] [SPACE space] [path [path ...]]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `key` | Yes | No | JSON document key. |
+| `INDENT indent` | No | No | Indentation characters for formatted JSON. |
+| `NEWLINE newline` | No | No | Line-separator characters for formatted JSON. |
+| `SPACE space` | No | No | Characters placed after JSON separators. |
+| `path` | No | Yes | One or more paths; defaults to the root. |
+
+## Important points
+
+- Raw TCP examples pass JSON values as valid JSON text. Typed Upstash SDK helpers serialize native objects and values for you.
+- Paths beginning with `$` use JSONPath and can match multiple values, so many JSON commands return an array of per-match results.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Bulk string or Null bulk string or null array |
+| RESP3 | Bulk string or Null |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const value = await redis.json.get("key", "$.path.to.somewhere");
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.json().get("profile", "$.name")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.call("JSON.GET", "profile", "$.name");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.json.get("profile", { path: "$.name" });
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.json().get("profile", "$.name")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.JSONGet(context.Background(), "profile", "$.name").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.JedisPooled;
+
+try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.jsonGet("profile", new redis.clients.jedis.json.Path("$.name"));
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::JsonCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result: redis::Value = connection.json_get("profile", &["$.name"])?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/json/json-merge.mdx b/redis/commands/json/json-merge.mdx
new file mode 100644
index 000000000..7792d31b4
--- /dev/null
+++ b/redis/commands/json/json-merge.mdx
@@ -0,0 +1,173 @@
+---
+title: "JSON.MERGE"
+description: "Merge JSON values."
+---
+
+Use `JSON.MERGE` to merge JSON values.
+
+## Syntax
+
+```redis
+JSON.MERGE <key> <path> <value>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `key` | Yes | No | JSON document key. |
+| `path` | Yes | No | Path to merge into. |
+| `value` | Yes | No | Valid JSON value containing the merge patch. |
+
+## Important points
+
+- Raw TCP examples pass JSON values as valid JSON text. Typed Upstash SDK helpers serialize native objects and values for you.
+- Paths beginning with `$` use JSONPath and can match multiple values, so many JSON commands return an array of per-match results.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Simple string `OK` |
+| RESP3 | Simple string `OK` |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.json.merge("key", "$.path.to.value", {"new": "value"})
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.json().merge("profile", "$", {"active": True})
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.call("JSON.MERGE", "profile", "$", "{\"active\":true}");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.json.merge("profile", "$", { active: true });
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.json().merge("profile", "$", {"active": True})
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.JSONMerge(context.Background(), "profile", "$", `{"active":true}`).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.JedisPooled;
+
+try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.jsonMerge("profile", new redis.clients.jedis.json.Path("$"), java.util.Map.of("active", true));
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("JSON.MERGE");
+    command.arg("profile");
+    command.arg("$");
+    command.arg("{\"active\":true}");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/json/json-mget.mdx b/redis/commands/json/json-mget.mdx
new file mode 100644
index 000000000..62378e27a
--- /dev/null
+++ b/redis/commands/json/json-mget.mdx
@@ -0,0 +1,170 @@
+---
+title: "JSON.MGET"
+description: "Get values from multiple keys."
+---
+
+Use `JSON.MGET` to get values from multiple keys.
+
+## Syntax
+
+```redis
+JSON.MGET <key> [key ...] <path>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `key` | Yes | Yes | One or more JSON document keys. |
+| `path` | Yes | No | Path read from every key. |
+
+## Important points
+
+- Raw TCP examples pass JSON values as valid JSON text. Typed Upstash SDK helpers serialize native objects and values for you.
+- Paths beginning with `$` use JSONPath and can match multiple values, so many JSON commands return an array of per-match results.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of bulk-string JSON values or null values, one per key |
+| RESP3 | Array of bulk-string JSON values or null values, one per key |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const values = await redis.json.mget(["key1", "key2"],  "$.path.to.somewhere");
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.json().mget(["profile:1", "profile:2"], "$.name")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.call("JSON.MGET", "profile:1", "profile:2", "$.name");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.json.mGet(["profile:1", "profile:2"], "$.name");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.json().mget(["profile:1", "profile:2"], "$.name")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.JSONMGet(context.Background(), "$.name", "profile:1", "profile:2").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.JedisPooled;
+
+try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.jsonMGet(new redis.clients.jedis.json.Path2("$.name"), "profile:1", "profile:2");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::JsonCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result: redis::Value = connection.json_mget(&["profile:1", "profile:2"], "$.name")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/json/json-mset.mdx b/redis/commands/json/json-mset.mdx
new file mode 100644
index 000000000..ab7f3a196
--- /dev/null
+++ b/redis/commands/json/json-mset.mdx
@@ -0,0 +1,175 @@
+---
+title: "JSON.MSET"
+description: "Set values in multiple keys."
+---
+
+Use `JSON.MSET` to set values in multiple keys.
+
+## Syntax
+
+```redis
+JSON.MSET <key> <path> <value> [key path value ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `key path value` | Yes | Yes | One or more key, path, and valid-JSON-value triples. |
+
+## Important points
+
+- Raw TCP examples pass JSON values as valid JSON text. Typed Upstash SDK helpers serialize native objects and values for you.
+- Paths beginning with `$` use JSONPath and can match multiple values, so many JSON commands return an array of per-match results.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Simple string `OK` |
+| RESP3 | Simple string `OK` |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+const result = await redis.json.mset([
+  { key: "profile:1", path: "$", value: { name: "Ada" } },
+]);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.json().mset([("profile:1", "$", {"name": "Ada"})])
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.call("JSON.MSET", "profile:1", "$", "{\"name\":\"Ada\"}");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.json.mSet([{ key: "profile:1", path: "$", value: { name: "Ada" } }]);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.json().mset([("profile:1", "$", {"name": "Ada"})])
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.JSONMSet(context.Background(), "profile:1", "$", `{"name":"Ada"}`).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+import java.nio.charset.StandardCharsets;
+import redis.clients.jedis.Jedis;
+import redis.clients.jedis.commands.ProtocolCommand;
+
+ProtocolCommand command = () -> "JSON.MSET".getBytes(StandardCharsets.UTF_8);
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.sendCommand(command, "profile:1", "$", "{\"name\":\"Ada\"}");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("JSON.MSET");
+    command.arg("profile:1");
+    command.arg("$");
+    command.arg("{\"name\":\"Ada\"}");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/json/json-numincrby.mdx b/redis/commands/json/json-numincrby.mdx
new file mode 100644
index 000000000..7aea132a0
--- /dev/null
+++ b/redis/commands/json/json-numincrby.mdx
@@ -0,0 +1,171 @@
+---
+title: "JSON.NUMINCRBY"
+description: "Increment JSON number."
+---
+
+Use `JSON.NUMINCRBY` to increment JSON number.
+
+## Syntax
+
+```redis
+JSON.NUMINCRBY <key> <path> <value>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `key` | Yes | No | JSON document key. |
+| `path` | Yes | No | Path selecting numbers. |
+| `value` | Yes | No | Numeric amount to add. |
+
+## Important points
+
+- Raw TCP examples pass JSON values as valid JSON text. Typed Upstash SDK helpers serialize native objects and values for you.
+- Paths beginning with `$` use JSONPath and can match multiple values, so many JSON commands return an array of per-match results.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Bulk string containing a JSON number or array |
+| RESP3 | Bulk string containing a JSON number or array |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const newValue = await redis.json.numincrby("key", "$.path.to.value", 2);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.json().numincrby("profile", "$.visits", 1)
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.call("JSON.NUMINCRBY", "profile", "$.visits", "1");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.json.numIncrBy("profile", "$.visits", 1);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.json().numincrby("profile", "$.visits", 1)
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.JSONNumIncrBy(context.Background(), "profile", "$.visits", 1).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.JedisPooled;
+
+try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.jsonNumIncrBy("profile", new redis.clients.jedis.json.Path("$.visits"), 1);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::JsonCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result: redis::Value = connection.json_num_incr_by("profile", "$.visits", 1)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/json/json-nummultby.mdx b/redis/commands/json/json-nummultby.mdx
new file mode 100644
index 000000000..e4557dd7b
--- /dev/null
+++ b/redis/commands/json/json-nummultby.mdx
@@ -0,0 +1,175 @@
+---
+title: "JSON.NUMMULTBY"
+description: "Multiply JSON number."
+---
+
+Use `JSON.NUMMULTBY` to multiply JSON number.
+
+## Syntax
+
+```redis
+JSON.NUMMULTBY <key> <path> <value>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `key` | Yes | No | JSON document key. |
+| `path` | Yes | No | Path selecting numbers. |
+| `value` | Yes | No | Numeric multiplier. |
+
+## Important points
+
+- Raw TCP examples pass JSON values as valid JSON text. Typed Upstash SDK helpers serialize native objects and values for you.
+- Paths beginning with `$` use JSONPath and can match multiple values, so many JSON commands return an array of per-match results.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Bulk string containing a JSON number or array |
+| RESP3 | Bulk string containing a JSON number or array |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const newValue = await redis.json.nummultby("key", "$.path.to.value", 2);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.json().nummultby("profile", "$.score", 2)
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.call("JSON.NUMMULTBY", "profile", "$.score", "2");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.json.numMultBy("profile", "$.score", 2);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.json().nummultby("profile", "$.score", 2)
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.Do(context.Background(), "JSON.NUMMULTBY", "profile", "$.score", "2").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+import java.nio.charset.StandardCharsets;
+import redis.clients.jedis.Jedis;
+import redis.clients.jedis.commands.ProtocolCommand;
+
+ProtocolCommand command = () -> "JSON.NUMMULTBY".getBytes(StandardCharsets.UTF_8);
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.sendCommand(command, "profile", "$.score", "2");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("JSON.NUMMULTBY");
+    command.arg("profile");
+    command.arg("$.score");
+    command.arg("2");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/json/json-objkeys.mdx b/redis/commands/json/json-objkeys.mdx
new file mode 100644
index 000000000..aa67aa2c4
--- /dev/null
+++ b/redis/commands/json/json-objkeys.mdx
@@ -0,0 +1,170 @@
+---
+title: "JSON.OBJKEYS"
+description: "Get JSON object keys."
+---
+
+Use `JSON.OBJKEYS` to get JSON object keys.
+
+## Syntax
+
+```redis
+JSON.OBJKEYS <key> [path]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `key` | Yes | No | JSON document key. |
+| `path` | No | No | Path selecting objects; defaults to the root. |
+
+## Important points
+
+- Raw TCP examples pass JSON values as valid JSON text. Typed Upstash SDK helpers serialize native objects and values for you.
+- Paths beginning with `$` use JSONPath and can match multiple values, so many JSON commands return an array of per-match results.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of arrays of bulk-string object keys or null values, or Null bulk string or null array |
+| RESP3 | Array of arrays of bulk-string object keys or null values, or Null |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const keys = await redis.json.objkeys("key", "$.path");
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.json().objkeys("profile", "$")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.call("JSON.OBJKEYS", "profile", "$");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.json.objKeys("profile", { path: "$" });
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.json().objkeys("profile", "$")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.JSONObjKeys(context.Background(), "profile", "$").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.JedisPooled;
+
+try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.jsonObjKeys("profile", new redis.clients.jedis.json.Path("$"));
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::JsonCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result: redis::Value = connection.json_obj_keys("profile", "$")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/json/json-objlen.mdx b/redis/commands/json/json-objlen.mdx
new file mode 100644
index 000000000..3c5176463
--- /dev/null
+++ b/redis/commands/json/json-objlen.mdx
@@ -0,0 +1,170 @@
+---
+title: "JSON.OBJLEN"
+description: "Get JSON object size."
+---
+
+Use `JSON.OBJLEN` to get JSON object size.
+
+## Syntax
+
+```redis
+JSON.OBJLEN <key> [path]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `key` | Yes | No | JSON document key. |
+| `path` | No | No | Path selecting objects; defaults to the root. |
+
+## Important points
+
+- Raw TCP examples pass JSON values as valid JSON text. Typed Upstash SDK helpers serialize native objects and values for you.
+- Paths beginning with `$` use JSONPath and can match multiple values, so many JSON commands return an array of per-match results.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer, array of integer lengths or null values, or Null bulk string or null array |
+| RESP3 | Integer, array of integer lengths or null values, or Null |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const lengths = await redis.json.objlen("key", "$.path");
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.json().objlen("profile", "$")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.call("JSON.OBJLEN", "profile", "$");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.json.objLen("profile", { path: "$" });
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.json().objlen("profile", "$")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.JSONObjLen(context.Background(), "profile", "$").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.JedisPooled;
+
+try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.jsonObjLen("profile", new redis.clients.jedis.json.Path("$"));
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::JsonCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result: redis::Value = connection.json_obj_len("profile", "$")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/json/json-resp.mdx b/redis/commands/json/json-resp.mdx
new file mode 100644
index 000000000..06af1f2ac
--- /dev/null
+++ b/redis/commands/json/json-resp.mdx
@@ -0,0 +1,173 @@
+---
+title: "JSON.RESP"
+description: "Get JSON in RESP format."
+---
+
+Use `JSON.RESP` to get JSON in RESP format.
+
+## Syntax
+
+```redis
+JSON.RESP <key> [path]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `key` | Yes | No | JSON document key. |
+| `path` | No | No | Path to convert; defaults to the root. |
+
+## Important points
+
+- Raw TCP examples pass JSON values as valid JSON text. Typed Upstash SDK helpers serialize native objects and values for you.
+- Paths beginning with `$` use JSONPath and can match multiple values, so many JSON commands return an array of per-match results.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Nested array, Integer, Bulk string, Simple string (`true` or `false` for JSON booleans), or Null bulk string or null array |
+| RESP3 | Nested array, Integer, Bulk string, Simple string (`true` or `false` for JSON booleans), or Null |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+const result = await redis.json.resp("profile", "$");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.json().resp("profile", "$")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.call("JSON.RESP", "profile", "$");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.sendCommand(["JSON.RESP", "profile", "$"]);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.json().resp("profile", "$")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.Do(context.Background(), "JSON.RESP", "profile", "$").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+import java.nio.charset.StandardCharsets;
+import redis.clients.jedis.Jedis;
+import redis.clients.jedis.commands.ProtocolCommand;
+
+ProtocolCommand command = () -> "JSON.RESP".getBytes(StandardCharsets.UTF_8);
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.sendCommand(command, "profile", "$");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("JSON.RESP");
+    command.arg("profile");
+    command.arg("$");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/json/json-set.mdx b/redis/commands/json/json-set.mdx
new file mode 100644
index 000000000..9f58cda2e
--- /dev/null
+++ b/redis/commands/json/json-set.mdx
@@ -0,0 +1,172 @@
+---
+title: "JSON.SET"
+description: "Set JSON value."
+---
+
+Use `JSON.SET` to set JSON value.
+
+## Syntax
+
+```redis
+JSON.SET <key> <path> <value> [NX | XX]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `key` | Yes | No | JSON document key. |
+| `path` | Yes | No | Path to create or replace. |
+| `value` | Yes | No | Valid JSON value. |
+| `NX \| XX` | No | No | Write only when the path is absent (`NX`) or present (`XX`). |
+
+## Important points
+
+- Raw TCP examples pass JSON values as valid JSON text. Typed Upstash SDK helpers serialize native objects and values for you.
+- Paths beginning with `$` use JSONPath and can match multiple values, so many JSON commands return an array of per-match results.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Simple string `OK`, or Null bulk string or null array when `NX` or `XX` prevented the write |
+| RESP3 | Simple string `OK`, or Null when `NX` or `XX` prevented the write |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+redis.json.set(key, "$.path", value);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.json().set("profile", "$", {"name": "Ada"})
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.call("JSON.SET", "profile", "$", "{\"name\":\"Ada\"}");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.json.set("profile", "$", { name: "Ada" });
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.json().set("profile", "$", {"name": "Ada"})
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.JSONSet(context.Background(), "profile", "$", map[string]interface{}{"name": "Ada"}).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.JedisPooled;
+
+try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.jsonSet("profile", new redis.clients.jedis.json.Path("$"), java.util.Map.of("name", "Ada"));
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::JsonCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result: redis::Value = connection.json_set("profile", "$", &serde_json::json!({"name": "Ada"}))?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/json/json-strappend.mdx b/redis/commands/json/json-strappend.mdx
new file mode 100644
index 000000000..407000b60
--- /dev/null
+++ b/redis/commands/json/json-strappend.mdx
@@ -0,0 +1,171 @@
+---
+title: "JSON.STRAPPEND"
+description: "Append to JSON string."
+---
+
+Use `JSON.STRAPPEND` to append to JSON string.
+
+## Syntax
+
+```redis
+JSON.STRAPPEND <key> <path> <value>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `key` | Yes | No | JSON document key. |
+| `path` | Yes | No | Path selecting strings. |
+| `value` | Yes | No | JSON-encoded string to append. |
+
+## Important points
+
+- Raw TCP examples pass JSON values as valid JSON text. Typed Upstash SDK helpers serialize native objects and values for you.
+- Paths beginning with `$` use JSONPath and can match multiple values, so many JSON commands return an array of per-match results.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer, array of integer lengths or null values, or Null bulk string or null array |
+| RESP3 | Integer, array of integer lengths or null values, or Null |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.json.strappend("key", "$.path.to.str", "abc");
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.json().strappend("profile", "$.name", " Lovelace")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.call("JSON.STRAPPEND", "profile", "$.name", "\" Lovelace\"");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.json.strAppend("profile", " Lovelace", { path: "$.name" });
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.json().strappend("profile", " Lovelace", "$.name")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.JSONStrAppend(context.Background(), "profile", "$.name", `" Lovelace"`).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.JedisPooled;
+
+try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.jsonStrAppend("profile", new redis.clients.jedis.json.Path("$.name"), " Lovelace");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::JsonCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result: redis::Value = connection.json_str_append("profile", "$.name", " Lovelace")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/json/json-strlen.mdx b/redis/commands/json/json-strlen.mdx
new file mode 100644
index 000000000..06a821119
--- /dev/null
+++ b/redis/commands/json/json-strlen.mdx
@@ -0,0 +1,170 @@
+---
+title: "JSON.STRLEN"
+description: "Get JSON string length."
+---
+
+Use `JSON.STRLEN` to get JSON string length.
+
+## Syntax
+
+```redis
+JSON.STRLEN <key> [path]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `key` | Yes | No | JSON document key. |
+| `path` | No | No | Path selecting strings; defaults to the root. |
+
+## Important points
+
+- Raw TCP examples pass JSON values as valid JSON text. Typed Upstash SDK helpers serialize native objects and values for you.
+- Paths beginning with `$` use JSONPath and can match multiple values, so many JSON commands return an array of per-match results.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer, array of integer lengths or null values, or Null bulk string or null array |
+| RESP3 | Integer, array of integer lengths or null values, or Null |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.json.strlen("key", "$.path.to.str", "a");
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.json().strlen("profile", "$.name")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.call("JSON.STRLEN", "profile", "$.name");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.json.strLen("profile", { path: "$.name" });
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.json().strlen("profile", "$.name")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.JSONStrLen(context.Background(), "profile", "$.name").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.JedisPooled;
+
+try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.jsonStrLen("profile", new redis.clients.jedis.json.Path("$.name"));
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::JsonCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result: redis::Value = connection.json_str_len("profile", "$.name")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/json/json-toggle.mdx b/redis/commands/json/json-toggle.mdx
new file mode 100644
index 000000000..22c48f16e
--- /dev/null
+++ b/redis/commands/json/json-toggle.mdx
@@ -0,0 +1,170 @@
+---
+title: "JSON.TOGGLE"
+description: "Toggle JSON boolean."
+---
+
+Use `JSON.TOGGLE` to toggle JSON boolean.
+
+## Syntax
+
+```redis
+JSON.TOGGLE <key> <path>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `key` | Yes | No | JSON document key. |
+| `path` | Yes | No | Path selecting Boolean values. |
+
+## Important points
+
+- Raw TCP examples pass JSON values as valid JSON text. Typed Upstash SDK helpers serialize native objects and values for you.
+- Paths beginning with `$` use JSONPath and can match multiple values, so many JSON commands return an array of per-match results.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of integer Boolean values or null values, one per matched path |
+| RESP3 | Array of integer Boolean values or null values, one per matched path |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const bool = await redis.json.toggle("key", "$.path.to.bool");
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.json().toggle("profile", "$.active")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.call("JSON.TOGGLE", "profile", "$.active");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.json.toggle("profile", "$.active");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.json().toggle("profile", "$.active")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.JSONToggle(context.Background(), "profile", "$.active").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.JedisPooled;
+
+try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.jsonToggle("profile", new redis.clients.jedis.json.Path("$.active"));
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::JsonCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result: redis::Value = connection.json_toggle("profile", "$.active")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/json/json-type.mdx b/redis/commands/json/json-type.mdx
new file mode 100644
index 000000000..e71c424b6
--- /dev/null
+++ b/redis/commands/json/json-type.mdx
@@ -0,0 +1,170 @@
+---
+title: "JSON.TYPE"
+description: "Get JSON value type."
+---
+
+Use `JSON.TYPE` to get JSON value type.
+
+## Syntax
+
+```redis
+JSON.TYPE <key> [path]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `key` | Yes | No | JSON document key. |
+| `path` | No | No | Path to inspect; defaults to the root. |
+
+## Important points
+
+- Raw TCP examples pass JSON values as valid JSON text. Typed Upstash SDK helpers serialize native objects and values for you.
+- Paths beginning with `$` use JSONPath and can match multiple values, so many JSON commands return an array of per-match results.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Bulk string, array of bulk-string type names, or Null bulk string or null array |
+| RESP3 | Bulk string, array of bulk-string type names, or Null |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const myType = await redis.json.type("key", "$.path.to.value");
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.json().type("profile", "$.name")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.call("JSON.TYPE", "profile", "$.name");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.json.type("profile", { path: "$.name" });
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.json().type("profile", "$.name")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.JSONType(context.Background(), "profile", "$.name").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.JedisPooled;
+
+try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.jsonType("profile", new redis.clients.jedis.json.Path("$.name"));
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::JsonCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result: redis::Value = connection.json_type("profile", "$.name")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/json/overview.mdx b/redis/commands/json/overview.mdx
new file mode 100644
index 000000000..85b6b8501
--- /dev/null
+++ b/redis/commands/json/overview.mdx
@@ -0,0 +1,35 @@
+---
+title: "JSON commands"
+sidebarTitle: "Overview"
+description: "Commands for storing and manipulating JSON values."
+---
+
+To query inside JSON values (full-text, fuzzy, phrase, regex), see [Upstash Redis Search](/redis/search/introduction).
+
+<CardGroup cols={2}>
+<Card title="JSON.ARRAPPEND" href="/redis/commands/json/json-arrappend">Append values to JSON array</Card>
+<Card title="JSON.ARRINDEX" href="/redis/commands/json/json-arrindex">Find index of value in array</Card>
+<Card title="JSON.ARRINSERT" href="/redis/commands/json/json-arrinsert">Insert values into JSON array</Card>
+<Card title="JSON.ARRLEN" href="/redis/commands/json/json-arrlen">Get JSON array length</Card>
+<Card title="JSON.ARRPOP" href="/redis/commands/json/json-arrpop">Pop value from JSON array</Card>
+<Card title="JSON.ARRTRIM" href="/redis/commands/json/json-arrtrim">Trim JSON array to range</Card>
+<Card title="JSON.CLEAR" href="/redis/commands/json/json-clear">Clear JSON values</Card>
+<Card title="JSON.DEL" href="/redis/commands/json/json-del">Delete JSON values</Card>
+<Card title="JSON.DEBUG" href="/redis/commands/json/json-debug">Inspect JSON memory usage</Card>
+<Card title="JSON.FORGET" href="/redis/commands/json/json-forget">Alias for JSON.DEL</Card>
+<Card title="JSON.GET" href="/redis/commands/json/json-get">Get JSON values</Card>
+<Card title="JSON.MERGE" href="/redis/commands/json/json-merge">Merge JSON values</Card>
+<Card title="JSON.MGET" href="/redis/commands/json/json-mget">Get values from multiple keys</Card>
+<Card title="JSON.MSET" href="/redis/commands/json/json-mset">Set values in multiple keys</Card>
+<Card title="JSON.NUMINCRBY" href="/redis/commands/json/json-numincrby">Increment JSON number</Card>
+<Card title="JSON.NUMMULTBY" href="/redis/commands/json/json-nummultby">Multiply JSON number</Card>
+<Card title="JSON.OBJKEYS" href="/redis/commands/json/json-objkeys">Get JSON object keys</Card>
+<Card title="JSON.OBJLEN" href="/redis/commands/json/json-objlen">Get JSON object size</Card>
+<Card title="JSON.RESP" href="/redis/commands/json/json-resp">Get JSON in RESP format</Card>
+<Card title="JSON.SET" href="/redis/commands/json/json-set">Set JSON value</Card>
+<Card title="JSON.STRAPPEND" href="/redis/commands/json/json-strappend">Append to JSON string</Card>
+<Card title="JSON.STRLEN" href="/redis/commands/json/json-strlen">Get JSON string length</Card>
+<Card title="JSON.TOGGLE" href="/redis/commands/json/json-toggle">Toggle JSON boolean</Card>
+<Card title="JSON.TYPE" href="/redis/commands/json/json-type">Get JSON value type</Card>
+</CardGroup>
+
diff --git a/redis/commands/list/blmove.mdx b/redis/commands/list/blmove.mdx
new file mode 100644
index 000000000..4029f254f
--- /dev/null
+++ b/redis/commands/list/blmove.mdx
@@ -0,0 +1,169 @@
+---
+title: "BLMOVE"
+description: "Move an element between lists, blocking until one arrives."
+---
+
+Use `BLMOVE` to move an element from one list to another, blocking until the source has an element or the timeout expires.
+
+## Syntax
+
+```redis
+BLMOVE <source> <destination> (LEFT | RIGHT) (LEFT | RIGHT) <timeout>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<source>` | Yes | No | Redis key used as source. |
+| `<destination>` | Yes | No | Redis key used as destination. |
+| `(LEFT \| RIGHT)` | Yes | No | Choose one form: `LEFT`; `RIGHT`. |
+| `(LEFT \| RIGHT)` | Yes | No | Choose one form: `LEFT`; `RIGHT`. |
+| `<timeout>` | Yes | No | Seconds to block; `0` blocks indefinitely. |
+
+## Important points
+
+- A blocking form holds the request until data arrives or its timeout expires. Set the client/network timeout longer than the command timeout.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Bulk string or Null bulk string or null array |
+| RESP3 | Bulk string or Null |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+<Note>
+  This command is not supported yet in `upstash_redis`.
+</Note>
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.blmove("source-key", "destination-key", "LEFT", "LEFT", "1.5");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.blMove("source-key", "destination-key", "LEFT", "LEFT", 1.5);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.blmove("source-key", "destination-key", 1.5, "LEFT", "LEFT")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+    "time"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.BLMove(context.Background(), "source-key", "destination-key", "LEFT", "LEFT", 1500*time.Millisecond).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.blmove("source-key", "destination-key", redis.clients.jedis.args.ListDirection.LEFT, redis.clients.jedis.args.ListDirection.LEFT, 1.5);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("BLMOVE");
+    command.arg("source-key");
+    command.arg("destination-key");
+    command.arg("LEFT");
+    command.arg("LEFT");
+    command.arg("1.5");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/list/blmpop.mdx b/redis/commands/list/blmpop.mdx
new file mode 100644
index 000000000..a3e44cd55
--- /dev/null
+++ b/redis/commands/list/blmpop.mdx
@@ -0,0 +1,168 @@
+---
+title: "BLMPOP"
+description: "Pop from the first non-empty list, blocking until one arrives."
+---
+
+Use `BLMPOP` to pop elements from the first non-empty list among several, blocking until one has elements or the timeout expires.
+
+## Syntax
+
+```redis
+BLMPOP <timeout> <numkeys> <key> [<key> ...] (LEFT | RIGHT) [COUNT <count>]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<timeout>` | Yes | No | Seconds to block; `0` blocks indefinitely. |
+| `<numkeys>` | Yes | No | Number of key arguments that follow. |
+| `<key>` | Yes | Yes | Redis key targeted by the command. |
+| `(LEFT \| RIGHT)` | Yes | No | Choose one form: `LEFT`; `RIGHT`. |
+| `COUNT <count>` | No | No | Maximum number of elements to pop. |
+
+## Important points
+
+- A blocking form holds the request until data arrives or its timeout expires. Set the client/network timeout longer than the command timeout.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Null bulk string or null array, or two-element array: key and array of values |
+| RESP3 | Null, or two-element array: key and array of values |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+<Note>
+  This command is not supported yet in `upstash_redis`.
+</Note>
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.blmpop("1.5", "1", "my-key", "LEFT");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.blmPop(1.5, "my-key", "LEFT");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.blmpop(1.5, 1, "my-key", direction="LEFT")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+    "time"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    _, result, err := client.BLMPop(context.Background(), 1500*time.Millisecond, "LEFT", 0, "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.blmpop(1.5, redis.clients.jedis.args.ListDirection.LEFT, "my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("BLMPOP");
+    command.arg("1.5");
+    command.arg("1");
+    command.arg("my-key");
+    command.arg("LEFT");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/list/blpop.mdx b/redis/commands/list/blpop.mdx
new file mode 100644
index 000000000..0daab6bf5
--- /dev/null
+++ b/redis/commands/list/blpop.mdx
@@ -0,0 +1,163 @@
+---
+title: "BLPOP"
+description: "Pop from the head of a list, blocking until an element arrives."
+---
+
+Use `BLPOP` to pop an element from the head of the first non-empty list, blocking until one has an element or the timeout expires.
+
+## Syntax
+
+```redis
+BLPOP <key> [<key> ...] <timeout>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | Yes | Redis key targeted by the command. |
+| `<timeout>` | Yes | No | Seconds to block; `0` blocks indefinitely. |
+
+## Important points
+
+- A blocking form holds the request until data arrives or its timeout expires. Set the client/network timeout longer than the command timeout.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Null bulk string or null array, or two-element key/value array |
+| RESP3 | Null, or two-element key/value array |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+<Note>
+  This command is not supported yet in `upstash_redis`.
+</Note>
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.blpop("my-key", "1.5");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.blPop("my-key", 1.5);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.blpop(["my-key"], timeout=1.5)
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+    "time"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.BLPop(context.Background(), 1500*time.Millisecond, "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.blpop(1.5, "my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("BLPOP");
+    command.arg("my-key");
+    command.arg("1.5");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/list/brpop.mdx b/redis/commands/list/brpop.mdx
new file mode 100644
index 000000000..47d344da0
--- /dev/null
+++ b/redis/commands/list/brpop.mdx
@@ -0,0 +1,163 @@
+---
+title: "BRPOP"
+description: "Pop from the tail of a list, blocking until an element arrives."
+---
+
+Use `BRPOP` to pop an element from the tail of the first non-empty list, blocking until one has an element or the timeout expires.
+
+## Syntax
+
+```redis
+BRPOP <key> [<key> ...] <timeout>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | Yes | Redis key targeted by the command. |
+| `<timeout>` | Yes | No | Seconds to block; `0` blocks indefinitely. |
+
+## Important points
+
+- A blocking form holds the request until data arrives or its timeout expires. Set the client/network timeout longer than the command timeout.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Null bulk string or null array, or two-element key/value array |
+| RESP3 | Null, or two-element key/value array |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+<Note>
+  This command is not supported yet in `upstash_redis`.
+</Note>
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.brpop("my-key", "1.5");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.brPop("my-key", 1.5);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.brpop(["my-key"], timeout=1.5)
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+    "time"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.BRPop(context.Background(), 1500*time.Millisecond, "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.brpop(1.5, "my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("BRPOP");
+    command.arg("my-key");
+    command.arg("1.5");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/list/brpoplpush.mdx b/redis/commands/list/brpoplpush.mdx
new file mode 100644
index 000000000..aee6d0995
--- /dev/null
+++ b/redis/commands/list/brpoplpush.mdx
@@ -0,0 +1,165 @@
+---
+title: "BRPOPLPUSH"
+description: "Pop from a list's tail and push it to another, blocking until an element arrives."
+---
+
+Use `BRPOPLPUSH` to pop an element from the tail of one list and push it to the head of another, blocking until the source has an element or the timeout expires.
+
+## Syntax
+
+```redis
+BRPOPLPUSH <source> <destination> <timeout>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<source>` | Yes | No | Redis key used as source. |
+| `<destination>` | Yes | No | Redis key used as destination. |
+| `<timeout>` | Yes | No | Seconds to block; `0` blocks indefinitely. |
+
+## Important points
+
+- A blocking form holds the request until data arrives or its timeout expires. Set the client/network timeout longer than the command timeout.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Bulk string or Null bulk string or null array |
+| RESP3 | Bulk string or Null |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+<Note>
+  This command is not supported yet in `upstash_redis`.
+</Note>
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.brpoplpush("source-key", "destination-key", "1.5");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.brPopLPush("source-key", "destination-key", 1.5);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.brpoplpush("source-key", "destination-key", timeout=1.5)
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+    "time"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.BRPopLPush(context.Background(), "source-key", "destination-key", 1500*time.Millisecond).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.brpoplpush("source-key", "destination-key", 1);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("BRPOPLPUSH");
+    command.arg("source-key");
+    command.arg("destination-key");
+    command.arg("1.5");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/list/lindex.mdx b/redis/commands/list/lindex.mdx
new file mode 100644
index 000000000..c6fe12061
--- /dev/null
+++ b/redis/commands/list/lindex.mdx
@@ -0,0 +1,167 @@
+---
+title: "LINDEX"
+description: "Get element by index."
+---
+
+Use `LINDEX` to get element by index.
+
+## Syntax
+
+```redis
+LINDEX <key> <index>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<index>` | Yes | No | Zero-based index; negative values count from the end. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Null bulk string or null array or Bulk string |
+| RESP3 | Null or Bulk string |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.rpush("key", "a", "b", "c");
+const element = await redis.lindex("key", 0);
+console.log(element); // "a"
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.lindex("my-key", 0)
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.lindex("my-key", "0");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.lIndex("my-key", 0);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.lindex("my-key", 0)
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.LIndex(context.Background(), "my-key", 0).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.lindex("my-key", 0);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.lindex("my-key", 0)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/list/linsert.mdx b/redis/commands/list/linsert.mdx
new file mode 100644
index 000000000..ec8e6b7fe
--- /dev/null
+++ b/redis/commands/list/linsert.mdx
@@ -0,0 +1,168 @@
+---
+title: "LINSERT"
+description: "Insert before or after pivot."
+---
+
+Use `LINSERT` to insert before or after pivot.
+
+## Syntax
+
+```redis
+LINSERT <key> (BEFORE | AFTER) <pivot> <element>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `(BEFORE \| AFTER)` | Yes | No | Choose one form: `BEFORE`; `AFTER`. |
+| `<pivot>` | Yes | No | Existing element to insert next to. |
+| `<element>` | Yes | No | Element to insert. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer: the list length after insertion, `-1` if the pivot was not found, `0` if the key does not exist |
+| RESP3 | Integer: the list length after insertion, `-1` if the pivot was not found, `0` if the key does not exist |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.rpush("key", "a", "b", "c");
+await redis.linsert("key", "before", "b", "x");
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.linsert("my-key", "BEFORE", "pivot", "element")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.linsert("my-key", "BEFORE", "pivot", "element");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.lInsert("my-key", "BEFORE", "pivot", "element");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.linsert("my-key", "BEFORE", "pivot", "element")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.LInsertBefore(context.Background(), "my-key", "pivot", "element").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.linsert("my-key", redis.clients.jedis.args.ListPosition.BEFORE, "pivot", "element");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.linsert_before("my-key", "pivot", "element")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/list/llen.mdx b/redis/commands/list/llen.mdx
new file mode 100644
index 000000000..06e5c5204
--- /dev/null
+++ b/redis/commands/list/llen.mdx
@@ -0,0 +1,166 @@
+---
+title: "LLEN"
+description: "Get list length."
+---
+
+Use `LLEN` to get list length.
+
+## Syntax
+
+```redis
+LLEN <key>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.rpush("key", "a", "b", "c");
+const length = await redis.llen("key");
+console.log(length); // 3
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.llen("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.llen("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.lLen("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.llen("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.LLen(context.Background(), "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.llen("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.llen("my-key")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/list/lmove.mdx b/redis/commands/list/lmove.mdx
new file mode 100644
index 000000000..abc0d8fde
--- /dev/null
+++ b/redis/commands/list/lmove.mdx
@@ -0,0 +1,168 @@
+---
+title: "LMOVE"
+description: "Move element between lists."
+---
+
+Use `LMOVE` to move element between lists.
+
+## Syntax
+
+```redis
+LMOVE <source> <destination> (LEFT | RIGHT) (LEFT | RIGHT)
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<source>` | Yes | No | Redis key used as source. |
+| `<destination>` | Yes | No | Redis key used as destination. |
+| `(LEFT \| RIGHT)` | Yes | No | Choose one form: `LEFT`; `RIGHT`. |
+| `(LEFT \| RIGHT)` | Yes | No | Choose one form: `LEFT`; `RIGHT`. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Bulk string |
+| RESP3 | Bulk string |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.rpush("source", "a", "b", "c");
+const element = await redis.lmove("source", "destination", "left", "left");
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.lmove("source-key", "destination-key", "LEFT", "LEFT")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.lmove("source-key", "destination-key", "LEFT", "LEFT");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.lMove("source-key", "destination-key", "LEFT", "LEFT");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.lmove("source-key", "destination-key", "LEFT", "LEFT")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.LMove(context.Background(), "source-key", "destination-key", "LEFT", "LEFT").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.lmove("source-key", "destination-key", redis.clients.jedis.args.ListDirection.LEFT, redis.clients.jedis.args.ListDirection.LEFT);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.lmove("source-key", "destination-key", redis::Direction::Left, redis::Direction::Left)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/list/lmpop.mdx b/redis/commands/list/lmpop.mdx
new file mode 100644
index 000000000..79883544b
--- /dev/null
+++ b/redis/commands/list/lmpop.mdx
@@ -0,0 +1,165 @@
+---
+title: "LMPOP"
+description: "Pop from multiple lists."
+---
+
+Use `LMPOP` to pop from multiple lists.
+
+## Syntax
+
+```redis
+LMPOP <numkeys> <key> [<key> ...] (LEFT | RIGHT) [COUNT <count>]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<numkeys>` | Yes | No | Number of key arguments that follow. |
+| `<key>` | Yes | Yes | Redis key targeted by the command. |
+| `(LEFT \| RIGHT)` | Yes | No | Choose one form: `LEFT`; `RIGHT`. |
+| `COUNT <count>` | No | No | Maximum number of elements to pop. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Null bulk string or null array, or two-element array: key and array of values |
+| RESP3 | Null, or two-element array: key and array of values |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+const result = await redis.lmpop(1, ["my-key"], "LEFT");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+<Note>
+  This command is not supported yet in `upstash_redis`.
+</Note>
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.lmpop("1", "my-key", "LEFT");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.lmPop("my-key", "LEFT");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.lmpop(1, "my-key", direction="LEFT")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    _, result, err := client.LMPop(context.Background(), "LEFT", 0, "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.lmpop(redis.clients.jedis.args.ListDirection.LEFT, "my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("LMPOP");
+    command.arg("1");
+    command.arg("my-key");
+    command.arg("LEFT");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/list/lpop.mdx b/redis/commands/list/lpop.mdx
new file mode 100644
index 000000000..6dd2f2d09
--- /dev/null
+++ b/redis/commands/list/lpop.mdx
@@ -0,0 +1,167 @@
+---
+title: "LPOP"
+description: "Pop from list head."
+---
+
+Use `LPOP` to pop from list head.
+
+## Syntax
+
+```redis
+LPOP <key> [<count>]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<count>` | No | No | Number of elements to pop. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Null bulk string or null array, Bulk string, or array of bulk-string values |
+| RESP3 | Null, Bulk string, or array of bulk-string values |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.rpush("key", "a", "b", "c");
+const element = await redis.lpop("key");
+console.log(element); // "a"
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.lpop("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.lpop("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.lPop("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.lpop("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.LPop(context.Background(), "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.lpop("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result: Option<String> = connection.lpop("my-key", None)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/list/lpos.mdx b/redis/commands/list/lpos.mdx
new file mode 100644
index 000000000..b3e667222
--- /dev/null
+++ b/redis/commands/list/lpos.mdx
@@ -0,0 +1,171 @@
+---
+title: "LPOS"
+description: "Find element position."
+---
+
+Use `LPOS` to find element position.
+
+## Syntax
+
+```redis
+LPOS <key> <element> [RANK <rank>] [COUNT <num-matches>] [MAXLEN <len>]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<element>` | Yes | No | Element value to search for. |
+| `RANK <rank>` | No | No | Which match to return; negative values search from the tail. |
+| `COUNT <num-matches>` | No | No | Number of matches to return; `0` returns every match. |
+| `MAXLEN <len>` | No | No | Maximum number of entries to keep in the stream. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Null bulk string or null array, Integer, or array of integer positions |
+| RESP3 | Null, Integer, or array of integer positions |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.rpush("key", "a", "b", "c");
+const index = await redis.lpos("key", "b");
+console.log(index); // 1
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.lpos("my-key", "element")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.lpos("my-key", "element");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.lPos("my-key", "element");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.lpos("my-key", "element")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.LPos(context.Background(), "my-key", "element", redis.LPosArgs{}).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.lpos("my-key", "element");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("LPOS");
+    command.arg("my-key");
+    command.arg("element");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/list/lpush.mdx b/redis/commands/list/lpush.mdx
new file mode 100644
index 000000000..8dbbbcce6
--- /dev/null
+++ b/redis/commands/list/lpush.mdx
@@ -0,0 +1,168 @@
+---
+title: "LPUSH"
+description: "Push to list head."
+---
+
+Use `LPUSH` to push to list head.
+
+## Syntax
+
+```redis
+LPUSH <key> <element> [<element> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<element>` | Yes | Yes | Element to push. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const length1 = await redis.lpush("key", "a", "b", "c");
+console.log(length1); // 3
+const length2 = await redis.lpush("key", "d");
+console.log(length2); // 4
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.lpush("my-key", "element")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.lpush("my-key", "element");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.lPush("my-key", "element");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.lpush("my-key", "element")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.LPush(context.Background(), "my-key", "element").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.lpush("my-key", "element");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.lpush("my-key", "element")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/list/lpushx.mdx b/redis/commands/list/lpushx.mdx
new file mode 100644
index 000000000..f6ce11a9c
--- /dev/null
+++ b/redis/commands/list/lpushx.mdx
@@ -0,0 +1,167 @@
+---
+title: "LPUSHX"
+description: "Push to head if list exists."
+---
+
+Use `LPUSHX` to push to head if list exists.
+
+## Syntax
+
+```redis
+LPUSHX <key> <element> [<element> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<element>` | Yes | Yes | Element to push. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.lpush("key", "a", "b", "c");
+const length = await redis.lpushx("key", "d");
+console.log(length); // 4
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.lpushx("my-key", "element")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.lpushx("my-key", "element");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.lPushX("my-key", "element");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.lpushx("my-key", "element")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.LPushX(context.Background(), "my-key", "element").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.lpushx("my-key", "element");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.lpush_exists("my-key", "element")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/list/lrange.mdx b/redis/commands/list/lrange.mdx
new file mode 100644
index 000000000..6309cff7c
--- /dev/null
+++ b/redis/commands/list/lrange.mdx
@@ -0,0 +1,168 @@
+---
+title: "LRANGE"
+description: "Get range of elements."
+---
+
+Use `LRANGE` to get range of elements.
+
+## Syntax
+
+```redis
+LRANGE <key> <start> <stop>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<start>` | Yes | No | Start index; negative values count from the end. |
+| `<stop>` | Yes | No | Stop index, inclusive; negative values count from the end. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of bulk-string values |
+| RESP3 | Array of bulk-string values |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.lpush("key", "a", "b", "c");
+const elements = await redis.lrange("key", 1, 2);
+console.log(elements) // ["b", "c"]
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.lrange("my-key", 0, 0)
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.lrange("my-key", "0", "0");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.lRange("my-key", 0, 0);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.lrange("my-key", 0, 0)
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.LRange(context.Background(), "my-key", 0, 0).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.lrange("my-key", 0, 0);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.lrange("my-key", 0, 0)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/list/lrem.mdx b/redis/commands/list/lrem.mdx
new file mode 100644
index 000000000..d9b6bf354
--- /dev/null
+++ b/redis/commands/list/lrem.mdx
@@ -0,0 +1,168 @@
+---
+title: "LREM"
+description: "Remove elements by value."
+---
+
+Use `LREM` to remove elements by value.
+
+## Syntax
+
+```redis
+LREM <key> <count> <element>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<count>` | Yes | No | How many matches to remove: positive scans head to tail, negative tail to head, `0` removes every match. |
+| `<element>` | Yes | No | Element value to remove. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.lpush("key", "a", "a", "b", "b", "c");
+const removed = await redis.lrem("key", 4, "b");
+console.log(removed) // 2
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.lrem("my-key", 1, "element")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.lrem("my-key", "1", "element");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.lRem("my-key", 1, "element");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.lrem("my-key", 1, "element")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.LRem(context.Background(), "my-key", 1, "element").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.lrem("my-key", 1, "element");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.lrem("my-key", 1, "element")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/list/lset.mdx b/redis/commands/list/lset.mdx
new file mode 100644
index 000000000..44b253136
--- /dev/null
+++ b/redis/commands/list/lset.mdx
@@ -0,0 +1,169 @@
+---
+title: "LSET"
+description: "Set element at index."
+---
+
+Use `LSET` to set element at index.
+
+## Syntax
+
+```redis
+LSET <key> <index> <element>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<index>` | Yes | No | Zero-based index; negative values count from the end. |
+| `<element>` | Yes | No | Element to store at the index. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Simple string `OK` |
+| RESP3 | Simple string `OK` |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.lpush("key", "a", "b", "c");
+await redis.lset("key", 1, "d");
+
+// list is now ["a", "d", "c"]
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.lset("my-key", 0, "element")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.lset("my-key", "0", "element");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.lSet("my-key", 0, "element");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.lset("my-key", 0, "element")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.LSet(context.Background(), "my-key", 0, "element").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.lset("my-key", 0, "element");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.lset("my-key", 0, "element")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/list/ltrim.mdx b/redis/commands/list/ltrim.mdx
new file mode 100644
index 000000000..68abb714c
--- /dev/null
+++ b/redis/commands/list/ltrim.mdx
@@ -0,0 +1,168 @@
+---
+title: "LTRIM"
+description: "Trim list to range."
+---
+
+Use `LTRIM` to trim list to range.
+
+## Syntax
+
+```redis
+LTRIM <key> <start> <stop>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<start>` | Yes | No | Start index; negative values count from the end. |
+| `<stop>` | Yes | No | Stop index, inclusive; negative values count from the end. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Simple string `OK` |
+| RESP3 | Simple string `OK` |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.lpush("key", "a", "b", "c", "d");
+await redis.ltrim("key", 1, 2);
+// the list is now ["b", "c"]
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.ltrim("my-key", 0, 0)
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.ltrim("my-key", "0", "0");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.lTrim("my-key", 0, 0);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.ltrim("my-key", 0, 0)
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.LTrim(context.Background(), "my-key", 0, 0).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.ltrim("my-key", 0, 0);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.ltrim("my-key", 0, 0)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/list/overview.mdx b/redis/commands/list/overview.mdx
new file mode 100644
index 000000000..40b8d6ad2
--- /dev/null
+++ b/redis/commands/list/overview.mdx
@@ -0,0 +1,31 @@
+---
+title: "List commands"
+sidebarTitle: "Overview"
+description: "Commands for storing and manipulating ordered collections."
+---
+
+<CardGroup cols={2}>
+<Card title="BLMOVE" href="/redis/commands/list/blmove">Blocking list move</Card>
+<Card title="BLMPOP" href="/redis/commands/list/blmpop">Blocking pop from multiple lists</Card>
+<Card title="BLPOP" href="/redis/commands/list/blpop">Blocking left pop</Card>
+<Card title="BRPOP" href="/redis/commands/list/brpop">Blocking right pop</Card>
+<Card title="BRPOPLPUSH" href="/redis/commands/list/brpoplpush">Blocking pop and push</Card>
+<Card title="LINDEX" href="/redis/commands/list/lindex">Get element by index</Card>
+<Card title="LINSERT" href="/redis/commands/list/linsert">Insert before or after pivot</Card>
+<Card title="LLEN" href="/redis/commands/list/llen">Get list length</Card>
+<Card title="LMOVE" href="/redis/commands/list/lmove">Move element between lists</Card>
+<Card title="LMPOP" href="/redis/commands/list/lmpop">Pop from multiple lists</Card>
+<Card title="LPOP" href="/redis/commands/list/lpop">Pop from list head</Card>
+<Card title="LPOS" href="/redis/commands/list/lpos">Find element position</Card>
+<Card title="LPUSH" href="/redis/commands/list/lpush">Push to list head</Card>
+<Card title="LPUSHX" href="/redis/commands/list/lpushx">Push to head if list exists</Card>
+<Card title="LRANGE" href="/redis/commands/list/lrange">Get range of elements</Card>
+<Card title="LREM" href="/redis/commands/list/lrem">Remove elements by value</Card>
+<Card title="LSET" href="/redis/commands/list/lset">Set element at index</Card>
+<Card title="LTRIM" href="/redis/commands/list/ltrim">Trim list to range</Card>
+<Card title="RPOP" href="/redis/commands/list/rpop">Pop from list tail</Card>
+<Card title="RPOPLPUSH" href="/redis/commands/list/rpoplpush">Pop from tail and push to head</Card>
+<Card title="RPUSH" href="/redis/commands/list/rpush">Push to list tail</Card>
+<Card title="RPUSHX" href="/redis/commands/list/rpushx">Push to tail if list exists</Card>
+</CardGroup>
+
diff --git a/redis/commands/list/rpop.mdx b/redis/commands/list/rpop.mdx
new file mode 100644
index 000000000..f5fec43ed
--- /dev/null
+++ b/redis/commands/list/rpop.mdx
@@ -0,0 +1,167 @@
+---
+title: "RPOP"
+description: "Pop from list tail."
+---
+
+Use `RPOP` to pop from list tail.
+
+## Syntax
+
+```redis
+RPOP <key> [<count>]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<count>` | No | No | Number of elements to pop. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Null bulk string or null array, Bulk string, or array of bulk-string values |
+| RESP3 | Null, Bulk string, or array of bulk-string values |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.rpush("key", "a", "b", "c");
+const element = await redis.rpop("key");
+console.log(element); // "c"
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.rpop("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.rpop("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.rPop("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.rpop("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.RPop(context.Background(), "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.rpop("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result: Option<String> = connection.rpop("my-key", None)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/list/rpoplpush.mdx b/redis/commands/list/rpoplpush.mdx
new file mode 100644
index 000000000..da40f419b
--- /dev/null
+++ b/redis/commands/list/rpoplpush.mdx
@@ -0,0 +1,161 @@
+---
+title: "RPOPLPUSH"
+description: "Pop from tail and push to head."
+---
+
+Use `RPOPLPUSH` to pop from tail and push to head.
+
+## Syntax
+
+```redis
+RPOPLPUSH <source> <destination>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<source>` | Yes | No | Redis key used as source. |
+| `<destination>` | Yes | No | Redis key used as destination. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Bulk string or Null bulk string or null array |
+| RESP3 | Bulk string or Null |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.rpoplpush("source-key", "destination-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.rpoplpush("source-key", "destination-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.rPopLPush("source-key", "destination-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.rpoplpush("source-key", "destination-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.RPopLPush(context.Background(), "source-key", "destination-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.rpoplpush("source-key", "destination-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.rpoplpush("source-key", "destination-key")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/list/rpush.mdx b/redis/commands/list/rpush.mdx
new file mode 100644
index 000000000..cd82718f4
--- /dev/null
+++ b/redis/commands/list/rpush.mdx
@@ -0,0 +1,168 @@
+---
+title: "RPUSH"
+description: "Push to list tail."
+---
+
+Use `RPUSH` to push to list tail.
+
+## Syntax
+
+```redis
+RPUSH <key> <element> [<element> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<element>` | Yes | Yes | Element to push. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const length1 = await redis.rpush("key", "a", "b", "c");
+console.log(length1); // 3
+const length2 = await redis.rpush("key", "d");
+console.log(length2); // 4
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.rpush("my-key", "element")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.rpush("my-key", "element");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.rPush("my-key", "element");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.rpush("my-key", "element")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.RPush(context.Background(), "my-key", "element").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.rpush("my-key", "element");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.rpush("my-key", "element")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/list/rpushx.mdx b/redis/commands/list/rpushx.mdx
new file mode 100644
index 000000000..917b532fd
--- /dev/null
+++ b/redis/commands/list/rpushx.mdx
@@ -0,0 +1,167 @@
+---
+title: "RPUSHX"
+description: "Push to tail if list exists."
+---
+
+Use `RPUSHX` to push to tail if list exists.
+
+## Syntax
+
+```redis
+RPUSHX <key> <element> [<element> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<element>` | Yes | Yes | Element to push. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.lpush("key", "a", "b", "c");
+const length = await redis.rpushx("key", "d");
+console.log(length); // 4
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.rpushx("my-key", "element")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.rpushx("my-key", "element");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.rPushX("my-key", "element");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.rpushx("my-key", "element")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.RPushX(context.Background(), "my-key", "element").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.rpushx("my-key", "element");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.rpush_exists("my-key", "element")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/overview.mdx b/redis/commands/overview.mdx
new file mode 100644
index 000000000..9d5d6231e
--- /dev/null
+++ b/redis/commands/overview.mdx
@@ -0,0 +1,28 @@
+---
+title: "Redis command reference"
+sidebarTitle: "Overview"
+description: "Browse the Redis commands supported by Upstash, organized by category."
+---
+
+Upstash supports Redis commands over both native Redis TCP and HTTPS REST. Choose a category to browse its supported commands.
+
+<CardGroup cols={2}>
+<Card title="Bitmap" icon="grid" href="/redis/commands/bitmap/overview" horizontal>Manipulate individual bits and bit fields</Card>
+<Card title="Connection" icon="plug" href="/redis/commands/connection/overview" horizontal>Authenticate and manage client connections</Card>
+<Card title="Functions" icon="code" href="/redis/commands/functions/overview" horizontal>Load, manage, and invoke Redis functions</Card>
+<Card title="Generic" icon="sliders" href="/redis/commands/generic/overview" horizontal>Manage keys, expiration, and serialization</Card>
+<Card title="Geo" icon="location-dot" href="/redis/commands/geo/overview" horizontal>Store and query geospatial data</Card>
+<Card title="Hash" icon="hashtag" href="/redis/commands/hash/overview" horizontal>Work with field-value collections</Card>
+<Card title="HyperLogLog" icon="chart-simple" href="/redis/commands/hyperloglog/overview" horizontal>Estimate cardinality</Card>
+<Card title="JSON" icon="brackets-curly" href="/redis/commands/json/overview" horizontal>Store and manipulate JSON values</Card>
+<Card title="List" icon="list" href="/redis/commands/list/overview" horizontal>Work with ordered collections</Card>
+<Card title="Pub/Sub" icon="tower-broadcast" href="/redis/commands/pub-sub/overview" horizontal>Publish messages and manage subscriptions</Card>
+<Card title="Scripting" icon="scroll" href="/redis/commands/scripting/overview" horizontal>Load and execute Lua scripts</Card>
+<Card title="Search" icon="magnifying-glass" href="/redis/commands/search/overview" horizontal>Create, query, and manage search indexes</Card>
+<Card title="Server" icon="server" href="/redis/commands/server/overview" horizontal>Inspect and manage the Redis server</Card>
+<Card title="Set" icon="layer-group" href="/redis/commands/set/overview" horizontal>Work with unique unordered members</Card>
+<Card title="Sorted Set" icon="arrow-down-1-9" href="/redis/commands/sorted-set/overview" horizontal>Work with scored collections</Card>
+<Card title="Streams" icon="water" href="/redis/commands/streams/overview" horizontal>Process append-only logs and consumer groups</Card>
+<Card title="String" icon="font" href="/redis/commands/string/overview" horizontal>Store and manipulate string values</Card>
+<Card title="Transactions" icon="right-left" href="/redis/commands/transactions/overview" horizontal>Group operations into atomic transactions</Card>
+</CardGroup>
diff --git a/redis/commands/pub-sub/overview.mdx b/redis/commands/pub-sub/overview.mdx
new file mode 100644
index 000000000..801252483
--- /dev/null
+++ b/redis/commands/pub-sub/overview.mdx
@@ -0,0 +1,15 @@
+---
+title: "Pub/Sub commands"
+sidebarTitle: "Overview"
+description: "Commands for publishing messages and managing channel subscriptions."
+---
+
+<CardGroup cols={2}>
+<Card title="PSUBSCRIBE" href="/redis/commands/pub-sub/psubscribe">Subscribe to pattern channels</Card>
+<Card title="PUBLISH" href="/redis/commands/pub-sub/publish">Publish message to channel</Card>
+<Card title="PUBSUB" href="/redis/commands/pub-sub/pubsub">Inspect pub/sub state</Card>
+<Card title="PUNSUBSCRIBE" href="/redis/commands/pub-sub/punsubscribe">Unsubscribe from patterns</Card>
+<Card title="SUBSCRIBE" href="/redis/commands/pub-sub/subscribe">Subscribe to channels</Card>
+<Card title="UNSUBSCRIBE" href="/redis/commands/pub-sub/unsubscribe">Unsubscribe from channels</Card>
+</CardGroup>
+
diff --git a/redis/commands/pub-sub/psubscribe.mdx b/redis/commands/pub-sub/psubscribe.mdx
new file mode 100644
index 000000000..d6b957277
--- /dev/null
+++ b/redis/commands/pub-sub/psubscribe.mdx
@@ -0,0 +1,153 @@
+---
+title: "PSUBSCRIBE"
+description: "Subscribe to pattern channels."
+---
+
+Use `PSUBSCRIBE` to subscribe to pattern channels.
+
+## Syntax
+
+```redis
+PSUBSCRIBE <pattern> [<pattern> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<pattern>` | Yes | Yes | Glob-style channel pattern. |
+
+## Important points
+
+- This is a connection-oriented command and is available over native Redis TCP, not the stateless REST endpoint.
+- Subscription commands require a dedicated TCP connection. In RESP3, subscription events use push replies.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Three-element subscription-state array per pattern |
+| RESP3 | Three-element subscription-state push reply per pattern |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const subscriber = new Redis(process.env.REDIS_URL!);
+await subscriber.psubscribe("events:*");
+subscriber.on("message", (channel, message) => console.log(channel, message));
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const subscriber = await createClient({ url: process.env.REDIS_URL }).connect();
+await subscriber.pSubscribe("events:*", (message, channel) => {
+  console.log(channel, message);
+});
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+pubsub = client.pubsub()
+pubsub.psubscribe("events:*")
+for message in pubsub.listen():
+    print(message)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    ctx := context.Background()
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    pubsub := client.PSubscribe(ctx, "events:*")
+    for message := range pubsub.Channel() {
+        fmt.Println(message.Channel, message.Payload)
+    }
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+import redis.clients.jedis.Jedis;
+import redis.clients.jedis.JedisPubSub;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  jedis.psubscribe(new JedisPubSub() {
+    @Override
+    public void onPMessage(String pattern, String channel, String message) {
+      System.out.println(channel + ": " + message);
+    }
+  }, "events:*");
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+    let mut pubsub = connection.as_pubsub();
+    pubsub.psubscribe("events:*")?;
+    loop {
+        let message = pubsub.get_message()?;
+        let payload: String = message.get_payload()?;
+        println!("{payload}");
+    }
+    #[allow(unreachable_code)]
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/pub-sub/publish.mdx b/redis/commands/pub-sub/publish.mdx
new file mode 100644
index 000000000..147814aee
--- /dev/null
+++ b/redis/commands/pub-sub/publish.mdx
@@ -0,0 +1,165 @@
+---
+title: "PUBLISH"
+description: "Publish message to channel."
+---
+
+Use `PUBLISH` to publish message to channel.
+
+## Syntax
+
+```redis
+PUBLISH <channel> <message>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<channel>` | Yes | No | Channel name. |
+| `<message>` | Yes | No | Message payload. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const listeners = await redis.publish("my-channel", "my-message");
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.publish("events", "hello")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.publish("events", "hello");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.publish("events", "hello");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.publish("events", "hello")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.Publish(context.Background(), "events", "hello").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.publish("events", "hello");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.publish("events", "hello")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/pub-sub/pubsub.mdx b/redis/commands/pub-sub/pubsub.mdx
new file mode 100644
index 000000000..b4f5dce2b
--- /dev/null
+++ b/redis/commands/pub-sub/pubsub.mdx
@@ -0,0 +1,161 @@
+---
+title: "PUBSUB"
+description: "Inspect pub/sub state."
+---
+
+Use `PUBSUB` to inspect pub/sub state.
+
+## Syntax
+
+```redis
+PUBSUB CHANNELS [pattern]
+PUBSUB NUMSUB [channel ...]
+PUBSUB NUMPAT
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `CHANNELS [pattern]` | One form | No | List active channels, optionally filtered by a glob-style pattern. |
+| `NUMSUB [channel ...]` | One form | Yes | Return subscriber counts for the supplied channels. |
+| `NUMPAT` | One form | No | Return the number of active pattern subscriptions. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of channel names, flat channel/count array, or Integer |
+| RESP3 | Array of channel names, flat channel/count array, or Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+<Note>
+  This command is not supported yet in `upstash_redis`.
+</Note>
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.pubsub("CHANNELS", "events:*");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.pubSubChannels("events:*");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.pubsub_channels("events:*")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.PubSubChannels(context.Background(), "events:*").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.pubsubChannels("events:*");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("PUBSUB");
+    command.arg("CHANNELS");
+    command.arg("events:*");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/pub-sub/punsubscribe.mdx b/redis/commands/pub-sub/punsubscribe.mdx
new file mode 100644
index 000000000..5e841d04f
--- /dev/null
+++ b/redis/commands/pub-sub/punsubscribe.mdx
@@ -0,0 +1,147 @@
+---
+title: "PUNSUBSCRIBE"
+description: "Unsubscribe from patterns."
+---
+
+Use `PUNSUBSCRIBE` to unsubscribe from patterns.
+
+## Syntax
+
+```redis
+PUNSUBSCRIBE [<pattern> [<pattern> ...]]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<pattern>` | No | Yes | Glob-style channel pattern; omit to unsubscribe from all patterns. |
+
+## Important points
+
+- This is a connection-oriented command and is available over native Redis TCP, not the stateless REST endpoint.
+- Subscription commands require a dedicated TCP connection. In RESP3, subscription events use push replies.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Three-element subscription-state array per pattern |
+| RESP3 | Three-element subscription-state push reply per pattern |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const subscriber = new Redis(process.env.REDIS_URL!);
+await subscriber.psubscribe("events:*");
+await subscriber.punsubscribe("events:*");
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const subscriber = await createClient({ url: process.env.REDIS_URL }).connect();
+await subscriber.pSubscribe("events:*", console.log);
+await subscriber.pUnsubscribe("events:*");
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+pubsub = client.pubsub()
+pubsub.psubscribe("events:*")
+pubsub.punsubscribe("events:*")
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    ctx := context.Background()
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    pubsub := client.PSubscribe(ctx, "events:*")
+    if err := pubsub.PUnsubscribe(ctx, "events:*"); err != nil {
+        panic(err)
+    }
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+import redis.clients.jedis.Jedis;
+import redis.clients.jedis.JedisPubSub;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  jedis.psubscribe(new JedisPubSub() {
+    @Override
+    public void onPMessage(String pattern, String channel, String message) {
+      punsubscribe();
+    }
+  }, "events:*");
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+    let mut pubsub = connection.as_pubsub();
+    pubsub.psubscribe("events:*")?;
+    pubsub.punsubscribe("events:*")?;
+    #[allow(unreachable_code)]
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/pub-sub/subscribe.mdx b/redis/commands/pub-sub/subscribe.mdx
new file mode 100644
index 000000000..09fcff185
--- /dev/null
+++ b/redis/commands/pub-sub/subscribe.mdx
@@ -0,0 +1,153 @@
+---
+title: "SUBSCRIBE"
+description: "Subscribe to channels."
+---
+
+Use `SUBSCRIBE` to subscribe to channels.
+
+## Syntax
+
+```redis
+SUBSCRIBE <channel> [<channel> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<channel>` | Yes | Yes | Channel name. |
+
+## Important points
+
+- This is a connection-oriented command and is available over native Redis TCP, not the stateless REST endpoint.
+- Subscription commands require a dedicated TCP connection. In RESP3, subscription events use push replies.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Three-element subscription-state array per channel |
+| RESP3 | Three-element subscription-state push reply per channel |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const subscriber = new Redis(process.env.REDIS_URL!);
+await subscriber.subscribe("events");
+subscriber.on("message", (channel, message) => console.log(channel, message));
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const subscriber = await createClient({ url: process.env.REDIS_URL }).connect();
+await subscriber.subscribe("events", (message, channel) => {
+  console.log(channel, message);
+});
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+pubsub = client.pubsub()
+pubsub.subscribe("events")
+for message in pubsub.listen():
+    print(message)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    ctx := context.Background()
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    pubsub := client.Subscribe(ctx, "events")
+    for message := range pubsub.Channel() {
+        fmt.Println(message.Channel, message.Payload)
+    }
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+import redis.clients.jedis.Jedis;
+import redis.clients.jedis.JedisPubSub;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  jedis.subscribe(new JedisPubSub() {
+    @Override
+    public void onMessage(String channel, String message) {
+      System.out.println(channel + ": " + message);
+    }
+  }, "events");
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+    let mut pubsub = connection.as_pubsub();
+    pubsub.subscribe("events")?;
+    loop {
+        let message = pubsub.get_message()?;
+        let payload: String = message.get_payload()?;
+        println!("{payload}");
+    }
+    #[allow(unreachable_code)]
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/pub-sub/unsubscribe.mdx b/redis/commands/pub-sub/unsubscribe.mdx
new file mode 100644
index 000000000..59796fece
--- /dev/null
+++ b/redis/commands/pub-sub/unsubscribe.mdx
@@ -0,0 +1,147 @@
+---
+title: "UNSUBSCRIBE"
+description: "Unsubscribe from channels."
+---
+
+Use `UNSUBSCRIBE` to unsubscribe from channels.
+
+## Syntax
+
+```redis
+UNSUBSCRIBE [<channel> [<channel> ...]]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<channel>` | No | Yes | Channel name. |
+
+## Important points
+
+- This is a connection-oriented command and is available over native Redis TCP, not the stateless REST endpoint.
+- Subscription commands require a dedicated TCP connection. In RESP3, subscription events use push replies.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Three-element subscription-state array per channel |
+| RESP3 | Three-element subscription-state push reply per channel |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const subscriber = new Redis(process.env.REDIS_URL!);
+await subscriber.subscribe("events");
+await subscriber.unsubscribe("events");
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const subscriber = await createClient({ url: process.env.REDIS_URL }).connect();
+await subscriber.subscribe("events", console.log);
+await subscriber.unsubscribe("events");
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+pubsub = client.pubsub()
+pubsub.subscribe("events")
+pubsub.unsubscribe("events")
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    ctx := context.Background()
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    pubsub := client.Subscribe(ctx, "events")
+    if err := pubsub.Unsubscribe(ctx, "events"); err != nil {
+        panic(err)
+    }
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+import redis.clients.jedis.Jedis;
+import redis.clients.jedis.JedisPubSub;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  jedis.subscribe(new JedisPubSub() {
+    @Override
+    public void onMessage(String channel, String message) {
+      unsubscribe();
+    }
+  }, "events");
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+    let mut pubsub = connection.as_pubsub();
+    pubsub.subscribe("events")?;
+    pubsub.unsubscribe("events")?;
+    #[allow(unreachable_code)]
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/scripting/eval-ro.mdx b/redis/commands/scripting/eval-ro.mdx
new file mode 100644
index 000000000..cc6f1628d
--- /dev/null
+++ b/redis/commands/scripting/eval-ro.mdx
@@ -0,0 +1,176 @@
+---
+title: "EVAL_RO"
+description: "Execute read-only Lua script."
+---
+
+Use `EVAL_RO` to execute read-only Lua script.
+
+## Syntax
+
+```redis
+EVAL_RO <script> <numkeys> [<key> [<key> ...]] [<arg> [<arg> ...]]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<script>` | Yes | No | Lua script source. |
+| `<numkeys>` | Yes | No | Number of key arguments that follow. |
+| `<key>` | No | Yes | Redis key targeted by the command. |
+| `<arg>` | No | Yes | Additional argument, available to the script as `ARGV`. |
+
+## Important points
+
+- `numkeys` must equal the number of key arguments that immediately follow it; remaining arguments are available to the script or function as ordinary arguments.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Reply produced by the evaluated read-only script |
+| RESP3 | Reply produced by the evaluated read-only script |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const script = `
+    return ARGV[1]
+`
+const result = await redis.evalRo(script, [], ["hello"]);
+console.log(result) // "hello"
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.eval_ro("return ARGV[1]", args=["value"])
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.eval_ro("return ARGV[1]", "0", "value");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.evalRo("return ARGV[1]", { arguments: ["value"] });
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.eval_ro("return ARGV[1]", 0, "value")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.EvalRO(context.Background(), "return ARGV[1]", nil, "value").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.evalReadonly("return ARGV[1]", java.util.List.of(), java.util.List.of("value"));
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("EVAL_RO");
+    command.arg("return ARGV[1]");
+    command.arg("1");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/scripting/eval.mdx b/redis/commands/scripting/eval.mdx
new file mode 100644
index 000000000..1ca37b1bf
--- /dev/null
+++ b/redis/commands/scripting/eval.mdx
@@ -0,0 +1,176 @@
+---
+title: "EVAL"
+description: "Execute a Lua script."
+---
+
+Use `EVAL` to execute a Lua script.
+
+## Syntax
+
+```redis
+EVAL <script> <numkeys> [<key> [<key> ...]] [<arg> [<arg> ...]]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<script>` | Yes | No | Lua script source. |
+| `<numkeys>` | Yes | No | Number of key arguments that follow. |
+| `<key>` | No | Yes | Redis key targeted by the command. |
+| `<arg>` | No | Yes | Additional argument, available to the script as `ARGV`. |
+
+## Important points
+
+- `numkeys` must equal the number of key arguments that immediately follow it; remaining arguments are available to the script or function as ordinary arguments.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Reply produced by the evaluated script |
+| RESP3 | Reply produced by the evaluated script |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const script = `
+    return ARGV[1]
+`
+const result = await redis.eval(script, [], ["hello"]);
+console.log(result) // "hello"
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.eval("return ARGV[1]", args=["value"])
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.eval("return ARGV[1]", "0", "value");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.eval("return ARGV[1]", { arguments: ["value"] });
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.eval("return ARGV[1]", 0, "value")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.Eval(context.Background(), "return ARGV[1]", nil, "value").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.eval("return ARGV[1]", java.util.List.of(), java.util.List.of("value"));
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("EVAL");
+    command.arg("return ARGV[1]");
+    command.arg("1");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/scripting/evalsha-ro.mdx b/redis/commands/scripting/evalsha-ro.mdx
new file mode 100644
index 000000000..e1b978a50
--- /dev/null
+++ b/redis/commands/scripting/evalsha-ro.mdx
@@ -0,0 +1,173 @@
+---
+title: "EVALSHA_RO"
+description: "Run a cached script that does not write."
+---
+
+Use `EVALSHA_RO` to run a script cached by its SHA1 digest. The script may not write to the database.
+
+## Syntax
+
+```redis
+EVALSHA_RO <sha1> <numkeys> [<key> [<key> ...]] [<arg> [<arg> ...]]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<sha1>` | Yes | No | SHA1 digest of a script cached with `SCRIPT LOAD`. |
+| `<numkeys>` | Yes | No | Number of key arguments that follow. |
+| `<key>` | No | Yes | Redis key targeted by the command. |
+| `<arg>` | No | Yes | Additional argument, available to the script as `ARGV`. |
+
+## Important points
+
+- `numkeys` must equal the number of key arguments that immediately follow it; remaining arguments are available to the script or function as ordinary arguments.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Reply produced by the cached read-only script |
+| RESP3 | Reply produced by the cached read-only script |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const result = await redis.evalshaRo("fb67a0c03b48ddbf8b4c9b011e779563bdbc28cb", [], ["hello"]);
+console.log(result) // "hello"
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.evalsha_ro("<sha1>", args=["value"])
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.evalsha_ro("<sha1>", "0", "value");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.evalShaRo("<sha1>", { arguments: ["value"] });
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.evalsha_ro("<sha1>", 0, "value")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.EvalShaRO(context.Background(), "<sha1>", nil, "value").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.evalshaReadonly("<sha1>", java.util.List.of(), java.util.List.of("value"));
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("EVALSHA_RO");
+    command.arg("<sha1>");
+    command.arg("1");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/scripting/evalsha.mdx b/redis/commands/scripting/evalsha.mdx
new file mode 100644
index 000000000..bff7e4c37
--- /dev/null
+++ b/redis/commands/scripting/evalsha.mdx
@@ -0,0 +1,173 @@
+---
+title: "EVALSHA"
+description: "Execute cached Lua script by SHA."
+---
+
+Use `EVALSHA` to execute cached Lua script by SHA.
+
+## Syntax
+
+```redis
+EVALSHA <sha1> <numkeys> [<key> [<key> ...]] [<arg> [<arg> ...]]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<sha1>` | Yes | No | SHA1 digest of a script cached with `SCRIPT LOAD`. |
+| `<numkeys>` | Yes | No | Number of key arguments that follow. |
+| `<key>` | No | Yes | Redis key targeted by the command. |
+| `<arg>` | No | Yes | Additional argument, available to the script as `ARGV`. |
+
+## Important points
+
+- `numkeys` must equal the number of key arguments that immediately follow it; remaining arguments are available to the script or function as ordinary arguments.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Reply produced by the cached script |
+| RESP3 | Reply produced by the cached script |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const result = await redis.evalsha("fb67a0c03b48ddbf8b4c9b011e779563bdbc28cb", [], ["hello"]);
+console.log(result) // "hello"
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.evalsha("<sha1>", args=["value"])
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.evalsha("<sha1>", "0", "value");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.evalSha("<sha1>", { arguments: ["value"] });
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.evalsha("<sha1>", 0, "value")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.EvalSha(context.Background(), "<sha1>", nil, "value").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.evalsha("<sha1>", java.util.List.of(), java.util.List.of("value"));
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("EVALSHA");
+    command.arg("<sha1>");
+    command.arg("1");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/scripting/overview.mdx b/redis/commands/scripting/overview.mdx
new file mode 100644
index 000000000..2dfa7a84c
--- /dev/null
+++ b/redis/commands/scripting/overview.mdx
@@ -0,0 +1,17 @@
+---
+title: "Scripting commands"
+sidebarTitle: "Overview"
+description: "Commands for loading and executing Lua scripts."
+---
+
+<CardGroup cols={2}>
+<Card title="EVAL" href="/redis/commands/scripting/eval">Execute a Lua script</Card>
+<Card title="EVAL_RO" href="/redis/commands/scripting/eval-ro">Execute read-only Lua script</Card>
+<Card title="EVALSHA" href="/redis/commands/scripting/evalsha">Execute cached Lua script by SHA</Card>
+<Card title="EVALSHA_RO" href="/redis/commands/scripting/evalsha-ro">Read-only execute by SHA</Card>
+<Card title="SCRIPT EXISTS" href="/redis/commands/scripting/script-exists">Check if scripts exist in cache</Card>
+<Card title="SCRIPT FLUSH" href="/redis/commands/scripting/script-flush">Clear the script cache</Card>
+<Card title="SCRIPT KILL" href="/redis/commands/scripting/script-kill">Stop a running read-only script</Card>
+<Card title="SCRIPT LOAD" href="/redis/commands/scripting/script-load">Load script into cache</Card>
+</CardGroup>
+
diff --git a/redis/commands/scripting/script-exists.mdx b/redis/commands/scripting/script-exists.mdx
new file mode 100644
index 000000000..31256dd47
--- /dev/null
+++ b/redis/commands/scripting/script-exists.mdx
@@ -0,0 +1,168 @@
+---
+title: "SCRIPT EXISTS"
+description: "Check if scripts exist in cache."
+---
+
+Use `SCRIPT EXISTS` to check if scripts exist in cache.
+
+## Syntax
+
+```redis
+SCRIPT EXISTS <sha1> [<sha1> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<sha1>` | Yes | Yes | SHA1 digest of a script cached with `SCRIPT LOAD`. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of integers, one per SHA1 digest |
+| RESP3 | Array of integers, one per SHA1 digest |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.scriptExists("<sha1>", "<sha2>")
+
+// Returns 1
+// [1, 0]
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.script_exists("<sha1>")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.script("EXISTS", "<sha1>");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.scriptExists("<sha1>");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.script_exists("<sha1>")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ScriptExists(context.Background(), "<sha1>").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.scriptExists("<sha1>");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("SCRIPT");
+    command.arg("EXISTS");
+    command.arg("<sha1>");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/scripting/script-flush.mdx b/redis/commands/scripting/script-flush.mdx
new file mode 100644
index 000000000..0a3555c10
--- /dev/null
+++ b/redis/commands/scripting/script-flush.mdx
@@ -0,0 +1,164 @@
+---
+title: "SCRIPT FLUSH"
+description: "Clear the script cache."
+---
+
+Use `SCRIPT FLUSH` to clear the script cache.
+
+## Syntax
+
+```redis
+SCRIPT FLUSH [ASYNC | SYNC]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `(ASYNC \| SYNC)` | No | No | Choose one form: `ASYNC` (request asynchronous cleanup); `SYNC` (request synchronous cleanup). |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Simple string `OK` |
+| RESP3 | Simple string `OK` |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.scriptFlush();
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.script_flush()
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.script("FLUSH");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.scriptFlush();
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.script_flush()
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ScriptFlush(context.Background()).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.scriptFlush();
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("SCRIPT");
+    command.arg("FLUSH");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/scripting/script-kill.mdx b/redis/commands/scripting/script-kill.mdx
new file mode 100644
index 000000000..3c3e24084
--- /dev/null
+++ b/redis/commands/scripting/script-kill.mdx
@@ -0,0 +1,159 @@
+---
+title: "SCRIPT KILL"
+description: "Stop a running read-only script."
+---
+
+Use `SCRIPT KILL` to stop a running read-only script.
+
+## Syntax
+
+```redis
+SCRIPT KILL
+```
+
+## Arguments
+
+This command takes no arguments.
+
+## Important points
+
+- The current deployment recognizes this command but reports `NOTBUSY` because it does not expose an interruptible running-script state.
+- As with Redis, a script that has already performed writes must not be killed because doing so would violate atomicity.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Error reply (`NOTBUSY` on the current deployment) |
+| RESP3 | Error reply (`NOTBUSY` on the current deployment) |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+<Note>
+  This command is not supported yet in `upstash_redis`.
+</Note>
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.script("KILL");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.scriptKill();
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.script_kill()
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ScriptKill(context.Background()).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.scriptKill();
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("SCRIPT");
+    command.arg("KILL");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/scripting/script-load.mdx b/redis/commands/scripting/script-load.mdx
new file mode 100644
index 000000000..e673c3a8c
--- /dev/null
+++ b/redis/commands/scripting/script-load.mdx
@@ -0,0 +1,169 @@
+---
+title: "SCRIPT LOAD"
+description: "Load script into cache."
+---
+
+Use `SCRIPT LOAD` to load script into cache.
+
+## Syntax
+
+```redis
+SCRIPT LOAD <script>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<script>` | Yes | No | Lua script source. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Bulk string |
+| RESP3 | Bulk string |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const script = `
+  local value = redis.call('GET', KEYS[1])
+  return value
+`;
+const sha1 = await redis.scriptLoad(script);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.script_load("return ARGV[1]")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.script("LOAD", "return ARGV[1]");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.scriptLoad("return ARGV[1]");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.script_load("return ARGV[1]")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ScriptLoad(context.Background(), "return ARGV[1]").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.scriptLoad("return ARGV[1]");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("SCRIPT");
+    command.arg("LOAD");
+    command.arg("return ARGV[1]");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/search/overview.mdx b/redis/commands/search/overview.mdx
new file mode 100644
index 000000000..ac3885c6f
--- /dev/null
+++ b/redis/commands/search/overview.mdx
@@ -0,0 +1,55 @@
+---
+title: "Search commands"
+sidebarTitle: "Overview"
+description: "Commands for creating, querying, and managing Upstash Redis Search indexes."
+---
+
+<Note>
+  Upstash Redis Search uses `SEARCH.*` commands. They are separate from and incompatible with the `FT.*` commands in the open-source RediSearch module.
+</Note>
+
+For Search commands, use the Upstash [`@upstash/redis`](/redis/sdks/ts/overview) or [`upstash-redis`](/redis/sdks/py/overview) SDK,
+or the redis-js wrappers [`@upstash/search-redis`](/redis/search/adapters/node-redis) for node-redis and [`@upstash/search-ioredis`](/redis/search/adapters/ioredis) for ioredis.
+
+For feature guides and tutorials, start with the [Upstash Redis Search introduction](/redis/search/introduction).
+
+<CardGroup cols={2}>
+<Card title="SEARCH.CREATE" href="/redis/commands/search/search-create">Create a search index</Card>
+<Card title="SEARCH.REINDEX" href="/redis/commands/search/search-reindex">Rebuild a search index from the current data</Card>
+<Card title="SEARCH.DROP" href="/redis/commands/search/search-drop">Remove a search index</Card>
+<Card title="SEARCH.DESCRIBE" href="/redis/commands/search/search-describe">Return metadata about a search index</Card>
+<Card title="SEARCH.WAITINDEXING" href="/redis/commands/search/search-waitindexing">Wait until pending index updates are visible</Card>
+<Card title="SEARCH.LISTINDEXES" href="/redis/commands/search/search-listindexes">List search indexes in the database</Card>
+<Card title="SEARCH.QUERY" href="/redis/commands/search/search-query">Search documents with a JSON filter</Card>
+<Card title="SEARCH.COUNT" href="/redis/commands/search/search-count">Count matching documents</Card>
+<Card title="SEARCH.AGGREGATE" href="/redis/commands/search/search-aggregate">Compute analytics over matching documents</Card>
+<Card title="SEARCH.ALIASADD" href="/redis/commands/search/search-aliasadd">Add or update an index alias</Card>
+<Card title="SEARCH.ALIASDEL" href="/redis/commands/search/search-aliasdel">Remove an index alias</Card>
+<Card title="SEARCH.LISTALIASES" href="/redis/commands/search/search-listaliases">List index aliases</Card>
+</CardGroup>
+
+`SEARCH.QUERY`, `SEARCH.COUNT`, `SEARCH.AGGREGATE`, `SEARCH.DESCRIBE`, `SEARCH.WAITINDEXING`, and `SEARCH.REINDEX` accept either an index name or alias. `SEARCH.DROP` always treats its argument as a literal index name. This makes it possible to switch an alias to a replacement index and then drop the old index without dropping the replacement.
+
+## REST API Usage
+
+All search commands can be sent via the Upstash REST API using a JSON array POST body.
+Each element of the array corresponds to a token in the command.
+
+```bash
+curl -X POST https://YOUR_ENDPOINT.upstash.io \
+  -H "Authorization: Bearer $UPSTASH_REDIS_REST_TOKEN" \
+  -d '["COMMAND", "arg1", "arg2", ...]'
+```
+
+The JSON filter and aggregation arguments are passed as string values within the array (not as nested JSON objects):
+
+```bash
+# Correct — filter is a string inside the array
+["SEARCH.QUERY", "products", "{\"name\": \"wireless\"}", "LIMIT", "10"]
+
+# Incorrect — filter is a nested object
+["SEARCH.QUERY", "products", {"name": "wireless"}, "LIMIT", "10"]
+```
+
+Pass JSON filter and aggregation arguments as string values inside the array, not as nested JSON objects.
+Search commands also work through the `/pipeline` endpoint for batching multiple commands in a single HTTP request.
diff --git a/redis/commands/search/search-aggregate.mdx b/redis/commands/search/search-aggregate.mdx
new file mode 100644
index 000000000..90a40bec7
--- /dev/null
+++ b/redis/commands/search/search-aggregate.mdx
@@ -0,0 +1,123 @@
+---
+title: "SEARCH.AGGREGATE"
+description: "Compute analytics over matching documents."
+---
+
+Use `SEARCH.AGGREGATE` to compute metrics and buckets over matching documents.
+
+## Syntax
+
+```redis
+SEARCH.AGGREGATE <name> '<json_filter>' '<json_aggregations>'
+```
+
+`<json_filter>` is an [Upstash JSON filter](/redis/search/querying). The command accepts an index name or alias. See [Aggregations](/redis/search/aggregations) for the aggregation object and supported operators.
+
+## Response
+
+In `redis-cli --json`, the response is an object keyed by aggregation alias:
+
+```json
+{
+  "avg_price": { "value": 49.99 },
+  "by_category": { "buckets": [{ "key": "electronics", "docCount": 42 }] }
+}
+```
+
+Raw RESP output may be rendered differently by client or protocol settings, but each top-level alias maps to its aggregation result. Returns `null` if the index does not exist.
+
+## Examples
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+const products = redis.search.index({ name: "products" });
+
+const result = await products.aggregate({
+  aggregations: {
+    avg_price: { $avg: { field: "price" } },
+  },
+});
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+products = redis.search.index(name="products")
+
+result = products.aggregate(
+    aggregations={"avg_price": {"$avg": {"field": "price"}}},
+)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import IORedis from "ioredis";
+import { createSearch } from "@upstash/search-ioredis";
+
+const redis = new IORedis(process.env.REDIS_URL!);
+const search = createSearch(redis);
+const products = search.index({ name: "products" });
+
+const result = await products.aggregate({
+  aggregations: {
+    avg_price: { $avg: { field: "price" } },
+  },
+});
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+import { createSearch } from "@upstash/search-redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const search = createSearch(client);
+const products = search.index({ name: "products" });
+
+const result = await products.aggregate({
+  aggregations: {
+    avg_price: { $avg: { field: "price" } },
+  },
+});
+```
+
+</Tab>
+
+<Tab title="Redis CLI">
+
+```bash
+SEARCH.AGGREGATE products '{}' '{"avg_price": {"$avg": {"field": "price"}}}'
+```
+
+</Tab>
+
+<Tab title="curl">
+
+```bash
+curl -X POST https://YOUR_ENDPOINT.upstash.io \
+  -H "Authorization: Bearer $UPSTASH_REDIS_REST_TOKEN" \
+  -d '["SEARCH.AGGREGATE", "products", "{}", "{\"avg_price\": {\"$avg\": {\"field\": \"price\"}}}"]'
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/search/search-aliasadd.mdx b/redis/commands/search/search-aliasadd.mdx
new file mode 100644
index 000000000..7baecf1d8
--- /dev/null
+++ b/redis/commands/search/search-aliasadd.mdx
@@ -0,0 +1,106 @@
+---
+title: "SEARCH.ALIASADD"
+description: "Create or update a search index alias."
+---
+
+Use `SEARCH.ALIASADD` to create an alias or update an existing alias to point to a search index.
+
+See [Aliases](/redis/search/aliases#adding-an-alias) for feature examples, including zero-downtime index swaps.
+
+The target name is not required to exist when the alias is created, so aliases can temporarily be dangling. Most commands resolve aliases, but [`SEARCH.DROP`](/redis/commands/search/search-drop) always uses a literal index name.
+
+## Syntax
+
+```redis
+SEARCH.ALIASADD <alias> <index_name>
+```
+
+## Response
+
+Returns `1` if a new alias was created or `2` if an existing alias was updated, including when it already points to the supplied index.
+
+## Examples
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+const result = await redis.search.alias.add({
+  alias: "products",
+  indexName: "products-v2",
+});
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.search.alias.add(
+    alias="products",
+    index_name="products-v2",
+)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import IORedis from "ioredis";
+import { createSearch } from "@upstash/search-ioredis";
+
+const redis = new IORedis(process.env.REDIS_URL!);
+const search = createSearch(redis);
+const result = await search.alias.add({
+  alias: "products",
+  indexName: "products-v2",
+});
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+import { createSearch } from "@upstash/search-redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const search = createSearch(client);
+const result = await search.alias.add({
+  alias: "products",
+  indexName: "products-v2",
+});
+```
+
+</Tab>
+
+<Tab title="Redis CLI">
+
+```bash
+SEARCH.ALIASADD products products-v2
+```
+
+</Tab>
+
+<Tab title="curl">
+
+```bash
+curl -X POST https://YOUR_ENDPOINT.upstash.io \
+  -H "Authorization: Bearer $UPSTASH_REDIS_REST_TOKEN" \
+  -d '["SEARCH.ALIASADD", "products", "products-v2"]'
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/search/search-aliasdel.mdx b/redis/commands/search/search-aliasdel.mdx
new file mode 100644
index 000000000..e081a67f3
--- /dev/null
+++ b/redis/commands/search/search-aliasdel.mdx
@@ -0,0 +1,92 @@
+---
+title: "SEARCH.ALIASDEL"
+description: "Delete a search index alias."
+---
+
+Use `SEARCH.ALIASDEL` to remove a search index alias.
+
+See [Deleting an Alias](/redis/search/aliases#deleting-an-alias) for the feature guide.
+
+## Syntax
+
+```redis
+SEARCH.ALIASDEL <alias>
+```
+
+## Response
+
+Returns `1` if the alias was deleted or `0` if the alias was not found.
+
+## Examples
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+const result = await redis.search.alias.delete({ alias: "products" });
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.search.alias.delete(alias="products")
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import IORedis from "ioredis";
+import { createSearch } from "@upstash/search-ioredis";
+
+const redis = new IORedis(process.env.REDIS_URL!);
+const search = createSearch(redis);
+const result = await search.alias.delete({ alias: "products" });
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+import { createSearch } from "@upstash/search-redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const search = createSearch(client);
+const result = await search.alias.delete({ alias: "products" });
+```
+
+</Tab>
+
+<Tab title="Redis CLI">
+
+```bash
+SEARCH.ALIASDEL products
+```
+
+</Tab>
+
+<Tab title="curl">
+
+```bash
+curl -X POST https://YOUR_ENDPOINT.upstash.io \
+  -H "Authorization: Bearer $UPSTASH_REDIS_REST_TOKEN" \
+  -d '["SEARCH.ALIASDEL", "products"]'
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/search/search-count.mdx b/redis/commands/search/search-count.mdx
new file mode 100644
index 000000000..0d5f25e5e
--- /dev/null
+++ b/redis/commands/search/search-count.mdx
@@ -0,0 +1,112 @@
+---
+title: "SEARCH.COUNT"
+description: "Count documents matching a query."
+---
+
+Use `SEARCH.COUNT` to count documents matching a query without retrieving them.
+
+See [Counting](/redis/search/counting) for feature examples and common use cases.
+
+## Syntax
+
+```redis
+SEARCH.COUNT <name> '<json_filter>'
+```
+
+`<json_filter>` is an [Upstash JSON filter](/redis/search/querying). The command accepts an index name or alias.
+
+## Response
+
+Returns the number of matching documents as an integer. Returns `-1` if the index does not exist.
+
+## Examples
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+const products = redis.search.index({ name: "products" });
+
+const result = await products.count({
+  filter: { inStock: true },
+});
+console.log(result.count);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+products = redis.search.index(name="products")
+
+result = products.count(filter={"inStock": True})
+print(result.count)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import IORedis from "ioredis";
+import { createSearch } from "@upstash/search-ioredis";
+
+const redis = new IORedis(process.env.REDIS_URL!);
+const search = createSearch(redis);
+const products = search.index({ name: "products" });
+
+const result = await products.count({
+  filter: { inStock: true },
+});
+console.log(result.count);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+import { createSearch } from "@upstash/search-redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const search = createSearch(client);
+const products = search.index({ name: "products" });
+
+const result = await products.count({
+  filter: { inStock: true },
+});
+console.log(result.count);
+```
+
+</Tab>
+
+<Tab title="Redis CLI">
+
+```bash
+SEARCH.COUNT products '{"inStock": true}'
+```
+
+</Tab>
+
+<Tab title="curl">
+
+```bash
+curl -X POST https://YOUR_ENDPOINT.upstash.io \
+  -H "Authorization: Bearer $UPSTASH_REDIS_REST_TOKEN" \
+  -d '["SEARCH.COUNT", "products", "{\"inStock\": true}"]'
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/search/search-create.mdx b/redis/commands/search/search-create.mdx
new file mode 100644
index 000000000..87559c3c2
--- /dev/null
+++ b/redis/commands/search/search-create.mdx
@@ -0,0 +1,165 @@
+---
+title: "SEARCH.CREATE"
+description: "Create a search index."
+---
+
+Use `SEARCH.CREATE` to create a search index over JSON, hash, or string values.
+
+See [Index Management](/redis/search/index-management#creating-an-index) for a feature-level guide to creating indexes and [Schema Definition](/redis/search/schema-definition) for field types and schema design.
+
+<Note>
+  Upstash Redis Search uses `SEARCH.*` commands. They are separate from and incompatible with the `FT.*` commands in the open-source RediSearch module.
+</Note>
+
+## Syntax
+
+```redis
+SEARCH.CREATE <name> ON <JSON|HASH|STRING>
+  PREFIX <count> <prefix> [<prefix> ...]
+  [LANGUAGE <language>]
+  [SKIPINITIALSCAN]
+  [EXISTSOK]
+  SCHEMA
+    <field> TEXT [NOSTEM] [NOTOKENIZE] [FROM <source_field>]
+    | <field> <U64|I64|F64|BOOL|DATE> [FAST] [FROM <source_field>]
+    | <field> <KEYWORD|FACET> [FROM <source_field>]
+    [...]
+```
+
+## Arguments
+
+| Argument | Description |
+| --- | --- |
+| `ON` | Type of Redis value to index: `JSON`, `HASH`, or `STRING`. A `STRING` value must contain a JSON object. |
+| `PREFIX` | One or more key prefixes. Prefixes in the same index cannot be duplicates or overlap one another. |
+| `LANGUAGE` | Stemming language for `TEXT` fields. Defaults to `english`. Supported values are `arabic`, `danish`, `dutch`, `english`, `finnish`, `french`, `german`, `greek`, `hungarian`, `italian`, `norwegian`, `portuguese`, `romanian`, `russian`, `spanish`, `swedish`, `tamil`, and `turkish`. |
+| `SKIPINITIALSCAN` | Create the index without scanning existing keys. Later writes are still indexed; use [`SEARCH.REINDEX`](/redis/commands/search/search-reindex) to add the current matching data. |
+| `EXISTSOK` | Return `0` when an index with the same data type, prefixes, and schema already exists. A configuration mismatch returns an error. |
+| `SCHEMA` | One or more field definitions. `SCHEMA` must be the final top-level clause. |
+
+### Schema field options
+
+| Option | Valid field types | Description |
+| --- | --- | --- |
+| `FAST` | `U64`, `I64`, `F64`, `BOOL`, `DATE` | Store the field for operations such as sorting and aggregations. Score functions accept `FAST` fields of type `U64`, `I64`, or `F64`. |
+| `NOSTEM` | `TEXT` | Index text without stemming words to their roots. |
+| `NOTOKENIZE` | `TEXT` | Index the entire value as one token. |
+| `FROM <source_field>` | All field types | Read the value from a different document field or nested dot path while exposing it under `<field>` in the index. |
+
+## Response
+
+Returns `1` when the index is created. With `EXISTSOK`, returns `0` if the existing index has the same data type, prefixes, and schema. Returns an error for a different configuration or when `<name>` is already used by a non-index Redis key.
+
+## Examples
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis, s } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const products = await redis.search.createIndex({
+  name: "products",
+  dataType: "json",
+  prefix: "product:",
+  schema: s.object({
+    name: s.string(),
+    price: s.number("F64"),
+    inStock: s.boolean(),
+  }),
+});
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+
+products = redis.search.create_index(
+    name="products",
+    data_type="json",
+    prefixes="product:",
+    schema={
+        "name": "TEXT",
+        "price": {"type": "F64", "fast": True},
+        "inStock": "BOOL",
+    },
+)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import IORedis from "ioredis";
+import { createSearch, s } from "@upstash/search-ioredis";
+
+const redis = new IORedis(process.env.REDIS_URL!);
+const search = createSearch(redis);
+
+const products = await search.createIndex({
+  name: "products",
+  dataType: "json",
+  prefix: "product:",
+  schema: s.object({
+    name: s.string(),
+    price: s.number("F64"),
+    inStock: s.boolean(),
+  }),
+});
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+import { createSearch, s } from "@upstash/search-redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const search = createSearch(client);
+
+const products = await search.createIndex({
+  name: "products",
+  dataType: "json",
+  prefix: "product:",
+  schema: s.object({
+    name: s.string(),
+    price: s.number("F64"),
+    inStock: s.boolean(),
+  }),
+});
+```
+
+</Tab>
+
+<Tab title="Redis CLI">
+
+```bash
+SEARCH.CREATE products ON JSON PREFIX 1 product: SCHEMA name TEXT price F64 FAST inStock BOOL
+```
+
+</Tab>
+
+<Tab title="curl">
+
+```bash
+curl -X POST https://YOUR_ENDPOINT.upstash.io \
+  -H "Authorization: Bearer $UPSTASH_REDIS_REST_TOKEN" \
+  -d '["SEARCH.CREATE", "products", "ON", "JSON", "PREFIX", "1", "product:", "SCHEMA", "name", "TEXT", "price", "F64", "FAST", "inStock", "BOOL"]'
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/search/search-describe.mdx b/redis/commands/search/search-describe.mdx
new file mode 100644
index 000000000..21526a295
--- /dev/null
+++ b/redis/commands/search/search-describe.mdx
@@ -0,0 +1,122 @@
+---
+title: "SEARCH.DESCRIBE"
+description: "Return metadata about a search index."
+---
+
+Use `SEARCH.DESCRIBE` to return metadata about a search index.
+
+See [Describing an Index](/redis/search/index-management#describing-an-index) for the feature guide.
+
+The command accepts an index name or alias. When an alias is used, the response describes its target and reports the target's index name.
+
+## Syntax
+
+```redis
+SEARCH.DESCRIBE <name>
+```
+
+## Response
+
+Returns index metadata as alternating field names and values. The response contains:
+
+| Field | Description |
+| --- | --- |
+| `name` | The index name. |
+| `type` | The indexed Redis value type: `HASH`, `JSON`, or `STRING`. |
+| `prefixes` | Key prefixes included in the index. |
+| `language` | Stemming language used by `TEXT` fields. |
+| `indexSize` | Current index size in bytes. |
+| `pendingUpdates` | Number of updates waiting to be indexed. |
+| `schema` | Field definitions, including `FROM`, `NOSTEM`, `NOTOKENIZE`, and `FAST` options where present. |
+
+```text
+[
+  "name", "products",
+  "type", "JSON",
+  "prefixes", ["product:"],
+  "language", "english",
+  "indexSize", 1234,
+  "pendingUpdates", 0,
+  "schema", [["name", "TEXT"], ["price", "F64", "FAST"]]
+]
+```
+
+Returns `null` if the index does not exist.
+
+## Examples
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+const products = redis.search.index({ name: "products" });
+const description = await products.describe();
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+products = redis.search.index(name="products")
+description = products.describe()
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import IORedis from "ioredis";
+import { createSearch } from "@upstash/search-ioredis";
+
+const redis = new IORedis(process.env.REDIS_URL!);
+const search = createSearch(redis);
+const products = search.index({ name: "products" });
+const description = await products.describe();
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+import { createSearch } from "@upstash/search-redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const search = createSearch(client);
+const products = search.index({ name: "products" });
+const description = await products.describe();
+```
+
+</Tab>
+
+<Tab title="Redis CLI">
+
+```bash
+SEARCH.DESCRIBE products
+```
+
+</Tab>
+
+<Tab title="curl">
+
+```bash
+curl -X POST https://YOUR_ENDPOINT.upstash.io \
+  -H "Authorization: Bearer $UPSTASH_REDIS_REST_TOKEN" \
+  -d '["SEARCH.DESCRIBE", "products"]'
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/search/search-drop.mdx b/redis/commands/search/search-drop.mdx
new file mode 100644
index 000000000..fa68fe86c
--- /dev/null
+++ b/redis/commands/search/search-drop.mdx
@@ -0,0 +1,98 @@
+---
+title: "SEARCH.DROP"
+description: "Drop a search index without deleting its keys."
+---
+
+Use `SEARCH.DROP` to remove a search index. The underlying Redis keys are not deleted.
+
+See [Dropping an Index](/redis/search/index-management#dropping-an-index) for the feature guide.
+
+`SEARCH.DROP` does not resolve aliases: `<name>` is always treated as the literal index name. Aliases that point to a dropped index are not removed automatically.
+
+## Syntax
+
+```redis
+SEARCH.DROP <name>
+```
+
+## Response
+
+Returns `1` if the index was dropped or `0` if the index was not found.
+
+## Examples
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+const products = redis.search.index({ name: "products" });
+const result = await products.drop();
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+products = redis.search.index(name="products")
+result = products.drop()
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import IORedis from "ioredis";
+import { createSearch } from "@upstash/search-ioredis";
+
+const redis = new IORedis(process.env.REDIS_URL!);
+const search = createSearch(redis);
+const products = search.index({ name: "products" });
+const result = await products.drop();
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+import { createSearch } from "@upstash/search-redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const search = createSearch(client);
+const products = search.index({ name: "products" });
+const result = await products.drop();
+```
+
+</Tab>
+
+<Tab title="Redis CLI">
+
+```bash
+SEARCH.DROP products
+```
+
+</Tab>
+
+<Tab title="curl">
+
+```bash
+curl -X POST https://YOUR_ENDPOINT.upstash.io \
+  -H "Authorization: Bearer $UPSTASH_REDIS_REST_TOKEN" \
+  -d '["SEARCH.DROP", "products"]'
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/search/search-listaliases.mdx b/redis/commands/search/search-listaliases.mdx
new file mode 100644
index 000000000..c9cc35296
--- /dev/null
+++ b/redis/commands/search/search-listaliases.mdx
@@ -0,0 +1,98 @@
+---
+title: "SEARCH.LISTALIASES"
+description: "List search index aliases."
+---
+
+Use `SEARCH.LISTALIASES` to return all aliases and the indexes they point to.
+
+See [Listing Aliases](/redis/search/aliases#listing-aliases) for the feature guide.
+
+## Syntax
+
+```redis
+SEARCH.LISTALIASES
+```
+
+## Response
+
+Returns an unordered array of `[alias, index_name]` pairs, or an empty array if no aliases exist. The response can include aliases whose target index no longer exists. To list every index in the database, use [`SEARCH.LISTINDEXES`](/redis/commands/search/search-listindexes).
+
+The SDKs below decode the pairs into an object or dictionary that maps each alias to its index name.
+
+## Examples
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+const aliases = await redis.search.alias.list();
+// { products: "products-v2" }
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+aliases = redis.search.alias.list()
+# {"products": "products-v2"}
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import IORedis from "ioredis";
+import { createSearch } from "@upstash/search-ioredis";
+
+const redis = new IORedis(process.env.REDIS_URL!);
+const search = createSearch(redis);
+const aliases = await search.alias.list();
+// { products: "products-v2" }
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+import { createSearch } from "@upstash/search-redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const search = createSearch(client);
+const aliases = await search.alias.list();
+// { products: "products-v2" }
+```
+
+</Tab>
+
+<Tab title="Redis CLI">
+
+```bash
+SEARCH.LISTALIASES
+```
+
+</Tab>
+
+<Tab title="curl">
+
+```bash
+curl -X POST https://YOUR_ENDPOINT.upstash.io \
+  -H "Authorization: Bearer $UPSTASH_REDIS_REST_TOKEN" \
+  -d '["SEARCH.LISTALIASES"]'
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/search/search-listindexes.mdx b/redis/commands/search/search-listindexes.mdx
new file mode 100644
index 000000000..404233bc1
--- /dev/null
+++ b/redis/commands/search/search-listindexes.mdx
@@ -0,0 +1,140 @@
+---
+title: "SEARCH.LISTINDEXES"
+description: "List search indexes in the database."
+---
+
+Use `SEARCH.LISTINDEXES` to list search indexes in the database.
+
+See [Listing Indexes](/redis/search/index-management#listing-indexes) for the feature guide.
+
+## Syntax
+
+```redis
+SEARCH.LISTINDEXES [MATCH <pattern>] [LIMIT <count>] [OFFSET <offset>]
+```
+
+## Arguments
+
+| Argument | Description | Default |
+| --- | --- | --- |
+| `MATCH` | Filter index names by a glob-style pattern, such as `product*`. | All indexes |
+| `LIMIT` | Maximum number of indexes to return. `0` returns all indexes. | `0` (all indexes) |
+| `OFFSET` | Number of indexes to skip for pagination. | `0` |
+
+## Response
+
+Returns one entry per index, sorted by index name. Each entry is a map containing the index `name` and its backing `type` (`HASH`, `JSON`, or `STRING`). With RESP2, each map is encoded as an array of alternating keys and values.
+
+```text
+[
+  ["name", "productIdx", "type", "HASH"],
+  ["name", "profileIdx", "type", "JSON"],
+  ["name", "sessionIdx", "type", "STRING"]
+]
+```
+
+## Examples
+
+<Note>
+  The high-level Search APIs do not currently expose `SEARCH.LISTINDEXES`. Use each client's generic command method for this command.
+</Note>
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+const indexes = await redis.exec<string[][]>([
+  "SEARCH.LISTINDEXES",
+  "MATCH",
+  "product*",
+  "LIMIT",
+  10,
+  "OFFSET",
+  0,
+]);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+indexes = redis.execute([
+    "SEARCH.LISTINDEXES",
+    "MATCH",
+    "product*",
+    "LIMIT",
+    10,
+    "OFFSET",
+    0,
+])
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import IORedis from "ioredis";
+
+const redis = new IORedis(process.env.REDIS_URL!);
+const indexes = await redis.call(
+  "SEARCH.LISTINDEXES",
+  "MATCH",
+  "product*",
+  "LIMIT",
+  10,
+  "OFFSET",
+  0,
+);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const indexes = await client.sendCommand([
+  "SEARCH.LISTINDEXES",
+  "MATCH",
+  "product*",
+  "LIMIT",
+  "10",
+  "OFFSET",
+  "0",
+]);
+```
+
+</Tab>
+
+<Tab title="Redis CLI">
+
+```bash
+SEARCH.LISTINDEXES MATCH 'product*' LIMIT 10 OFFSET 0
+```
+
+</Tab>
+
+<Tab title="curl">
+
+```bash
+curl -X POST https://YOUR_ENDPOINT.upstash.io \
+  -H "Authorization: Bearer $UPSTASH_REDIS_REST_TOKEN" \
+  -d '["SEARCH.LISTINDEXES", "MATCH", "product*", "LIMIT", "10", "OFFSET", "0"]'
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/search/search-query.mdx b/redis/commands/search/search-query.mdx
new file mode 100644
index 000000000..5d5ad6497
--- /dev/null
+++ b/redis/commands/search/search-query.mdx
@@ -0,0 +1,167 @@
+---
+title: "SEARCH.QUERY"
+description: "Search documents with a JSON filter."
+---
+
+Use `SEARCH.QUERY` to search for documents matching a JSON filter.
+
+## Syntax
+
+```redis
+SEARCH.QUERY <name> '<query>'
+  [LIMIT <count>]
+  [OFFSET <offset>]
+  [ORDERBY <field> [ASC|DESC]]
+  [SELECT <count> <field> [<field> ...]]
+  [NOCONTENT]
+  [HIGHLIGHT FIELDS <count> <field> [<field> ...] [TAGS <open> <close>]]
+  [SCOREFUNC
+    FIELDVALUE <field>
+      [MODIFIER <NONE|LOG|LOG1P|LOG2P|LN|LN1P|LN2P|SQUARE|SQRT|RECIPROCAL>]
+      [FACTOR <number>]
+      [MISSING <number>]
+    [FIELDVALUE ...]
+    [SCOREMODE <SUM|MULTIPLY|REPLACE>]
+    [COMBINEMODE <SUM|MULTIPLY>]]
+```
+
+## Arguments
+
+| Argument | Description | Default |
+| --- | --- | --- |
+| `LIMIT` | Maximum number of results to return. Must be between 1 and 1000. | `10` |
+| `OFFSET` | Number of results to skip for pagination. Must be between 0 and 10,000. | `0` |
+| `ORDERBY` | Sort by a `FAST` field. The direction defaults to `DESC` when omitted. | Relevance score, descending |
+| `SELECT` | Return only the specified number of document fields. When the schema uses `FROM`, specify the source document field rather than its index alias. | All fields |
+| `NOCONTENT` | Return keys and scores without document content. | Disabled |
+| `HIGHLIGHT` | Wrap matching terms in tags. The default tags are `<em>` and `</em>`. | Disabled |
+| `SCOREFUNC` | Adjust relevance scores using one or more `FAST` numeric fields. `FACTOR` defaults to `1`, `MISSING` to `0`, `MODIFIER` to `NONE`, `SCOREMODE` to `SUM`, and `COMBINEMODE` to `SUM`. | Disabled |
+<Warning>
+  `NOCONTENT` cannot be combined with `SELECT` or `HIGHLIGHT`. `SCOREFUNC` cannot be combined with `ORDERBY`. Inside `MULTI` or `EVAL`, the command requires `NOCONTENT`.
+</Warning>
+
+See [Querying and filtering](/redis/search/querying) for the JSON filter operators and detailed query examples.
+
+## Response
+
+Returns an array of `[key, score, content]` results, or `null` if the index does not exist:
+
+- `key` is the Redis key of the matching document.
+- `score` is the floating-point relevance score.
+- `content` is an array of field-value pairs. JSON indexes return `[["$", "<json_string>"]]`; hash indexes return `[["field", "value"], ...]`.
+
+When `NOCONTENT` is used, each result is `[key, score]`. When `SELECT` is used, only fields that exist in the document appear in the content.
+
+```text
+[
+  ["key1", 1.25, [["$", "{\"name\":\"...\"}"]]],
+  ["key2", 0.75, [["$", "{\"name\":\"...\"}"]]]
+]
+```
+
+## Examples
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis, s } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+const products = redis.search.index({
+  name: "products",
+  schema: s.object({ name: s.string() }),
+});
+
+const results = await products.query({
+  filter: { name: "wireless" },
+  limit: 10,
+  offset: 0,
+});
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+products = redis.search.index(name="products")
+
+results = products.query(
+    filter={"name": "wireless"},
+    limit=10,
+    offset=0,
+)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import IORedis from "ioredis";
+import { createSearch, s } from "@upstash/search-ioredis";
+
+const redis = new IORedis(process.env.REDIS_URL!);
+const search = createSearch(redis);
+const products = search.index({
+  name: "products",
+  schema: s.object({ name: s.string() }),
+});
+
+const results = await products.query({
+  filter: { name: "wireless" },
+  limit: 10,
+  offset: 0,
+});
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+import { createSearch, s } from "@upstash/search-redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const search = createSearch(client);
+const products = search.index({
+  name: "products",
+  schema: s.object({ name: s.string() }),
+});
+
+const results = await products.query({
+  filter: { name: "wireless" },
+  limit: 10,
+  offset: 0,
+});
+```
+
+</Tab>
+
+<Tab title="Redis CLI">
+
+```bash
+SEARCH.QUERY products '{"name": "wireless"}' LIMIT 10 OFFSET 0
+```
+
+</Tab>
+
+<Tab title="curl">
+
+```bash
+curl -X POST https://YOUR_ENDPOINT.upstash.io \
+  -H "Authorization: Bearer $UPSTASH_REDIS_REST_TOKEN" \
+  -d '["SEARCH.QUERY", "products", "{\"name\": \"wireless\"}", "LIMIT", "10", "OFFSET", "0"]'
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/search/search-reindex.mdx b/redis/commands/search/search-reindex.mdx
new file mode 100644
index 000000000..35f19d45d
--- /dev/null
+++ b/redis/commands/search/search-reindex.mdx
@@ -0,0 +1,48 @@
+---
+title: "SEARCH.REINDEX"
+description: "Rebuild a search index from the current matching data."
+---
+
+Use `SEARCH.REINDEX` to rebuild an existing index from the current Redis keys that match its data type and prefixes. It is especially useful after creating an index with `SKIPINITIALSCAN`.
+
+See [Index Management](/redis/search/index-management) for the feature guide to creating and managing indexes.
+
+`SEARCH.REINDEX` accepts an index name or alias. The index definition is preserved while its searchable contents are replaced with a fresh scan.
+
+<Warning>
+  Reindexing scans all matching keys and can be expensive for large datasets.
+</Warning>
+
+## Syntax
+
+```redis
+SEARCH.REINDEX <name>
+```
+
+## Response
+
+Returns `1` when the index is rebuilt or `0` if the index does not exist.
+
+## Examples
+
+<Tabs>
+
+<Tab title="Redis CLI">
+
+```bash
+SEARCH.REINDEX products
+```
+
+</Tab>
+
+<Tab title="curl">
+
+```bash
+curl -X POST https://YOUR_ENDPOINT.upstash.io \
+  -H "Authorization: Bearer $UPSTASH_REDIS_REST_TOKEN" \
+  -d '["SEARCH.REINDEX", "products"]'
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/search/search-waitindexing.mdx b/redis/commands/search/search-waitindexing.mdx
new file mode 100644
index 000000000..233376511
--- /dev/null
+++ b/redis/commands/search/search-waitindexing.mdx
@@ -0,0 +1,104 @@
+---
+title: "SEARCH.WAITINDEXING"
+description: "Wait until pending index updates are visible."
+---
+
+Use `SEARCH.WAITINDEXING` to block until all pending index updates are processed and visible to queries.
+
+See [Waiting for Indexing](/redis/search/index-management#waiting-for-indexing) for guidance on when to wait for index updates.
+
+The command accepts an index name or alias and waits for every update queued before the command began. Writes that arrive later may require another call.
+
+## Syntax
+
+```redis
+SEARCH.WAITINDEXING <name>
+```
+
+## Important points
+
+<Warning>
+  Do not call `SEARCH.WAITINDEXING` after every write. Batch updates are necessary for optimal indexing performance. Use this command only when you need to ensure queries reflect recent changes, such as in tests or CI pipelines.
+</Warning>
+
+## Response
+
+Returns `1` when indexing is complete or `0` if the index was not found.
+
+## Examples
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+const products = redis.search.index({ name: "products" });
+const result = await products.waitIndexing();
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+products = redis.search.index(name="products")
+result = products.wait_indexing()
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import IORedis from "ioredis";
+import { createSearch } from "@upstash/search-ioredis";
+
+const redis = new IORedis(process.env.REDIS_URL!);
+const search = createSearch(redis);
+const products = search.index({ name: "products" });
+const result = await products.waitIndexing();
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+import { createSearch } from "@upstash/search-redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const search = createSearch(client);
+const products = search.index({ name: "products" });
+const result = await products.waitIndexing();
+```
+
+</Tab>
+
+<Tab title="Redis CLI">
+
+```bash
+SEARCH.WAITINDEXING products
+```
+
+</Tab>
+
+<Tab title="curl">
+
+```bash
+curl -X POST https://YOUR_ENDPOINT.upstash.io \
+  -H "Authorization: Bearer $UPSTASH_REDIS_REST_TOKEN" \
+  -d '["SEARCH.WAITINDEXING", "products"]'
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/server/acl.mdx b/redis/commands/server/acl.mdx
new file mode 100644
index 000000000..a8b40a2f8
--- /dev/null
+++ b/redis/commands/server/acl.mdx
@@ -0,0 +1,178 @@
+---
+title: "ACL"
+description: "Manage access control list."
+---
+
+Use `ACL` to manage access control list.
+
+## Syntax
+
+```redis
+ACL CAT [category]
+ACL DELUSER <username> [username ...]
+ACL GENPASS [bits]
+ACL GETUSER <username>
+ACL HELP
+ACL LIST
+ACL LOAD
+ACL RESTTOKEN <username> <password>
+ACL GENTOKEN <username> [password]
+ACL LOG [count | RESET]
+ACL SAVE
+ACL SETUSER <username> [rule ...]
+ACL USERS
+ACL WHOAMI
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `subcommand` | Yes | No | One of the supported ACL operations shown in the syntax block. |
+| `username` | Depends | Some forms | ACL user selected by the subcommand. |
+| `rule` | No | Yes | ACL SETUSER rule; rules are applied from left to right. |
+| `count \| RESET` | No | No | Limit ACL LOG output or clear the log. |
+
+## Important points
+
+- This command can expose administrative information or make a broad destructive change. Restrict it to trusted code paths.
+- ACL is an administrative command. Changing users or rules can immediately revoke application access.
+- Upstash also supports the deployment-specific `RESTTOKEN` and `GENTOKEN` subcommands.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Simple string `OK`; Integer; Bulk string; array of bulk strings or nested metadata arrays; flat array of alternating keys and values; or Null bulk string or null array |
+| RESP3 | Simple string `OK`; Integer; Bulk string; array of bulk strings or nested metadata arrays; Map; or Null |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+<Note>
+  This command is not supported yet in `upstash_redis`.
+</Note>
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.acl("WHOAMI");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.aclWhoAmI();
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.acl_whoami()
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ACLWhoAmI(context.Background()).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.aclWhoAmI();
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.acl_whoami()?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/server/command.mdx b/redis/commands/server/command.mdx
new file mode 100644
index 000000000..5362f62a5
--- /dev/null
+++ b/redis/commands/server/command.mdx
@@ -0,0 +1,158 @@
+---
+title: "COMMAND"
+description: "Get command metadata."
+---
+
+Use `COMMAND` to get command metadata.
+
+## Syntax
+
+```redis
+COMMAND
+```
+
+## Arguments
+
+This command takes no arguments.
+
+## Important points
+
+- The current Upstash deployment accepts `COMMAND` for client compatibility but returns an empty array; it does not expose the server command table.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Empty array |
+| RESP3 | Empty array |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+<Note>
+  This command is not supported yet in `upstash_redis`.
+</Note>
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.call("COMMAND");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.command();
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.command()
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.Command(context.Background()).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.command();
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("COMMAND");
+
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/server/config-get.mdx b/redis/commands/server/config-get.mdx
new file mode 100644
index 000000000..58b7b8b7f
--- /dev/null
+++ b/redis/commands/server/config-get.mdx
@@ -0,0 +1,163 @@
+---
+title: "CONFIG GET"
+description: "Read runtime configuration."
+---
+
+Use `CONFIG GET` to read runtime configuration.
+
+## Syntax
+
+```redis
+CONFIG GET <parameter> [parameter ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `parameter` | Yes | Yes | One or more glob-style configuration parameter patterns. |
+
+## Important points
+
+- This command can expose administrative information or make a broad destructive change. Restrict it to trusted code paths.
+- This deployment exposes only `notify-keyspace-events`. Other patterns return no matching entries.
+- Both RESP2 and RESP3 return a flat array of alternating parameter names and values.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Flat array of alternating configuration names and values |
+| RESP3 | Flat array of alternating configuration names and values |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+<Note>
+  This command is not supported yet in `upstash_redis`.
+</Note>
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.config("GET", "notify-keyspace-events");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.configGet("notify-keyspace-events");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.config_get("notify-keyspace-events")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ConfigGet(context.Background(), "notify-keyspace-events").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.configGet("notify-keyspace-events");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("CONFIG");
+    command.arg("GET");
+    command.arg("notify-keyspace-events");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/server/config-set.mdx b/redis/commands/server/config-set.mdx
new file mode 100644
index 000000000..a7fbf04c2
--- /dev/null
+++ b/redis/commands/server/config-set.mdx
@@ -0,0 +1,165 @@
+---
+title: "CONFIG SET"
+description: "Change runtime configuration."
+---
+
+Use `CONFIG SET` to change runtime configuration.
+
+## Syntax
+
+```redis
+CONFIG SET <parameter> <value> [parameter value ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `parameter` | Yes | Yes, in pairs | Runtime configuration parameter to update. |
+| `value` | Yes | Yes, in pairs | New value for the preceding parameter. |
+
+## Important points
+
+- This command can expose administrative information or make a broad destructive change. Restrict it to trusted code paths.
+- This deployment permits changes only to `notify-keyspace-events`; any other parameter returns an error.
+- Parameter/value pairs are processed from left to right. If a later pair is invalid, an earlier valid change may already have taken effect.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Simple string `OK` |
+| RESP3 | Simple string `OK` |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+<Note>
+  This command is not supported yet in `upstash_redis`.
+</Note>
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.config("SET", "notify-keyspace-events", "Ex");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.configSet("notify-keyspace-events", "Ex");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.config_set("notify-keyspace-events", "Ex")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ConfigSet(context.Background(), "notify-keyspace-events", "Ex").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.configSet("notify-keyspace-events", "Ex");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("CONFIG");
+    command.arg("SET");
+    command.arg("notify-keyspace-events");
+    command.arg("Ex");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/server/dbsize.mdx b/redis/commands/server/dbsize.mdx
new file mode 100644
index 000000000..931a9092e
--- /dev/null
+++ b/redis/commands/server/dbsize.mdx
@@ -0,0 +1,167 @@
+---
+title: "DBSIZE"
+description: "Get number of keys in database."
+---
+
+Use `DBSIZE` to get number of keys in database.
+
+## Syntax
+
+```redis
+DBSIZE
+```
+
+## Arguments
+
+This command takes no arguments.
+
+## Important points
+
+- This operation can inspect a large part of the database. Prefer cursor-based scans where possible and avoid unbounded use on hot paths.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const keys = await redis.dbsize();
+console.log(keys) // 20
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.dbsize()
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.dbsize();
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.dbSize();
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.dbsize()
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.DBSize(context.Background()).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.dbSize();
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("DBSIZE");
+
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/server/flushall.mdx b/redis/commands/server/flushall.mdx
new file mode 100644
index 000000000..dfced8b51
--- /dev/null
+++ b/redis/commands/server/flushall.mdx
@@ -0,0 +1,170 @@
+---
+title: "FLUSHALL"
+description: "Delete all keys in all databases."
+---
+
+Use `FLUSHALL` to delete all keys in all databases.
+
+## Syntax
+
+```redis
+FLUSHALL [ASYNC | SYNC]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `(ASYNC \| SYNC)` | No | No | Choose one form: `ASYNC` (request asynchronous cleanup); `SYNC` (request synchronous cleanup). |
+
+## Important points
+
+- This command can expose administrative information or make a broad destructive change. Restrict it to trusted code paths.
+- This operation can inspect a large part of the database. Prefer cursor-based scans where possible and avoid unbounded use on hot paths.
+- This deletes the database contents. Test against a disposable database and require an explicit operator action in production tooling.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Simple string `OK` |
+| RESP3 | Simple string `OK` |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.flushall();
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.flushall()
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.flushall();
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.flushAll();
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.flushall()
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.FlushAll(context.Background()).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.flushAll();
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("FLUSHALL");
+
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/server/flushdb.mdx b/redis/commands/server/flushdb.mdx
new file mode 100644
index 000000000..9224d5227
--- /dev/null
+++ b/redis/commands/server/flushdb.mdx
@@ -0,0 +1,170 @@
+---
+title: "FLUSHDB"
+description: "Delete all keys in current database."
+---
+
+Use `FLUSHDB` to delete all keys in current database.
+
+## Syntax
+
+```redis
+FLUSHDB [ASYNC | SYNC]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `(ASYNC \| SYNC)` | No | No | Choose one form: `ASYNC` (request asynchronous cleanup); `SYNC` (request synchronous cleanup). |
+
+## Important points
+
+- This command can expose administrative information or make a broad destructive change. Restrict it to trusted code paths.
+- This operation can inspect a large part of the database. Prefer cursor-based scans where possible and avoid unbounded use on hot paths.
+- This deletes the database contents. Test against a disposable database and require an explicit operator action in production tooling.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Simple string `OK` |
+| RESP3 | Simple string `OK` |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.flushdb();
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.flushdb()
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.flushdb();
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.flushDb();
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.flushdb()
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.FlushDB(context.Background()).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.flushDB();
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("FLUSHDB");
+
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/server/info.mdx b/redis/commands/server/info.mdx
new file mode 100644
index 000000000..a7c5929e8
--- /dev/null
+++ b/redis/commands/server/info.mdx
@@ -0,0 +1,162 @@
+---
+title: "INFO"
+description: "Get server statistics and information."
+---
+
+Use `INFO` to get server statistics and information.
+
+## Syntax
+
+```redis
+INFO [section]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `section` | No | No | Section to return: `server`, `clients`, `memory`, `stats`, `cluster`, `keyspace`, `default`, or `all`. |
+
+## Important points
+
+- This command can expose administrative information or make a broad destructive change. Restrict it to trusted code paths.
+- `default` and `all` return the same Upstash section set. Unsupported section names produce only a section heading.
+- The reply is a CRLF-delimited text report, not a RESP map. Parse it defensively because fields may be added over time.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Bulk string |
+| RESP3 | Bulk string |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+<Note>
+  This command is not supported yet in `upstash_redis`.
+</Note>
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.info("memory");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.info("memory");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.info("memory")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.Info(context.Background(), "memory").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.info("memory");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("INFO");
+    command.arg("memory");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/server/monitor.mdx b/redis/commands/server/monitor.mdx
new file mode 100644
index 000000000..e1e76d8b6
--- /dev/null
+++ b/redis/commands/server/monitor.mdx
@@ -0,0 +1,126 @@
+---
+title: "MONITOR"
+description: "Stream all commands received."
+---
+
+Use `MONITOR` to stream all commands received.
+
+## Syntax
+
+```redis
+MONITOR
+```
+
+## Arguments
+
+This command takes no arguments.
+
+## Important points
+
+- This is a connection-oriented command and is available over native Redis TCP, not the stateless REST endpoint.
+- This command can expose administrative information or make a broad destructive change. Restrict it to trusted code paths.
+- MONITOR changes the TCP connection into a continuous command stream. Use a dedicated connection and close it to stop monitoring.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Simple string `OK`, then a stream of bulk strings, one per command the server executes |
+| RESP3 | Simple string `OK`, then a stream of bulk strings, one per command the server executes |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+redis.monitor((error, monitor) => {
+  if (error) throw error;
+  monitor.on("monitor", (time, args, source, database) => {
+    console.log({ time, args, source, database });
+  });
+});
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+
+await client.monitor((command) => {
+  console.log(command);
+});
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+with client.monitor() as monitor:
+    for command in monitor.listen():
+        print(command)
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+import redis.clients.jedis.Jedis;
+import redis.clients.jedis.JedisMonitor;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  jedis.monitor(new JedisMonitor() {
+    @Override
+    public void onCommand(String command) {
+      System.out.println(command);
+    }
+  });
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let packed = redis::cmd("MONITOR").get_packed_command();
+    connection.send_packed_command(&packed)?;
+    loop {
+        println!("{:?}", connection.recv_response()?);
+    }
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/server/overview.mdx b/redis/commands/server/overview.mdx
new file mode 100644
index 000000000..b7210b355
--- /dev/null
+++ b/redis/commands/server/overview.mdx
@@ -0,0 +1,19 @@
+---
+title: "Server commands"
+sidebarTitle: "Overview"
+description: "Commands for inspecting and managing the Redis server."
+---
+
+<CardGroup cols={2}>
+<Card title="ACL" href="/redis/commands/server/acl">Manage access control list</Card>
+<Card title="COMMAND" href="/redis/commands/server/command">Get command metadata</Card>
+<Card title="CONFIG GET" href="/redis/commands/server/config-get">Read runtime configuration</Card>
+<Card title="CONFIG SET" href="/redis/commands/server/config-set">Change runtime configuration</Card>
+<Card title="DBSIZE" href="/redis/commands/server/dbsize">Get number of keys in database</Card>
+<Card title="FLUSHALL" href="/redis/commands/server/flushall">Delete all keys in all databases</Card>
+<Card title="FLUSHDB" href="/redis/commands/server/flushdb">Delete all keys in current database</Card>
+<Card title="INFO" href="/redis/commands/server/info">Get server statistics and information</Card>
+<Card title="MONITOR" href="/redis/commands/server/monitor">Stream all commands received</Card>
+<Card title="TIME" href="/redis/commands/server/time">Get current server time</Card>
+</CardGroup>
+
diff --git a/redis/commands/server/time.mdx b/redis/commands/server/time.mdx
new file mode 100644
index 000000000..f2bf97543
--- /dev/null
+++ b/redis/commands/server/time.mdx
@@ -0,0 +1,162 @@
+---
+title: "TIME"
+description: "Get current server time."
+---
+
+Use `TIME` to get current server time.
+
+## Syntax
+
+```redis
+TIME
+```
+
+## Arguments
+
+This command takes no arguments.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Two-element array of bulk strings: Unix seconds and microseconds |
+| RESP3 | Two-element array of bulk strings: Unix seconds and microseconds |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+const result = await redis.time();
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.time()
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.time();
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.time();
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.time()
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.Time(context.Background()).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.time();
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("TIME");
+
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/set/overview.mdx b/redis/commands/set/overview.mdx
new file mode 100644
index 000000000..5ccf6426e
--- /dev/null
+++ b/redis/commands/set/overview.mdx
@@ -0,0 +1,26 @@
+---
+title: "Set commands"
+sidebarTitle: "Overview"
+description: "Commands for storing and manipulating unordered collections of unique members."
+---
+
+<CardGroup cols={2}>
+<Card title="SADD" href="/redis/commands/set/sadd">Add members to a set</Card>
+<Card title="SCARD" href="/redis/commands/set/scard">Get set cardinality</Card>
+<Card title="SDIFF" href="/redis/commands/set/sdiff">Get set difference</Card>
+<Card title="SDIFFSTORE" href="/redis/commands/set/sdiffstore">Store set difference</Card>
+<Card title="SINTER" href="/redis/commands/set/sinter">Get set intersection</Card>
+<Card title="SINTERCARD" href="/redis/commands/set/sintercard">Get intersection cardinality</Card>
+<Card title="SINTERSTORE" href="/redis/commands/set/sinterstore">Store set intersection</Card>
+<Card title="SISMEMBER" href="/redis/commands/set/sismember">Check if member exists in set</Card>
+<Card title="SMEMBERS" href="/redis/commands/set/smembers">Get all set members</Card>
+<Card title="SMISMEMBER" href="/redis/commands/set/smismember">Check multiple members</Card>
+<Card title="SMOVE" href="/redis/commands/set/smove">Move member between sets</Card>
+<Card title="SPOP" href="/redis/commands/set/spop">Remove random members</Card>
+<Card title="SRANDMEMBER" href="/redis/commands/set/srandmember">Get random members</Card>
+<Card title="SREM" href="/redis/commands/set/srem">Remove members from a set</Card>
+<Card title="SSCAN" href="/redis/commands/set/sscan">Incrementally iterate set members</Card>
+<Card title="SUNION" href="/redis/commands/set/sunion">Get set union</Card>
+<Card title="SUNIONSTORE" href="/redis/commands/set/sunionstore">Store set union</Card>
+</CardGroup>
+
diff --git a/redis/commands/set/sadd.mdx b/redis/commands/set/sadd.mdx
new file mode 100644
index 000000000..7806abfea
--- /dev/null
+++ b/redis/commands/set/sadd.mdx
@@ -0,0 +1,169 @@
+---
+title: "SADD"
+description: "Add members to a set."
+---
+
+Use `SADD` to add members to a set.
+
+## Syntax
+
+```redis
+SADD <key> <member> [<member> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<member>` | Yes | Yes | Member name. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+// 3
+await redis.sadd("key", "a", "b", "c");
+
+// 0
+await redis.sadd("key", "a", "b");
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.sadd("my-key", "member")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.sadd("my-key", "member");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.sAdd("my-key", "member");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.sadd("my-key", "member")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.SAdd(context.Background(), "my-key", "member").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.sadd("my-key", "member");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.sadd("my-key", "member")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/set/scard.mdx b/redis/commands/set/scard.mdx
new file mode 100644
index 000000000..8b7e0db80
--- /dev/null
+++ b/redis/commands/set/scard.mdx
@@ -0,0 +1,166 @@
+---
+title: "SCARD"
+description: "Get set cardinality."
+---
+
+Use `SCARD` to get set cardinality.
+
+## Syntax
+
+```redis
+SCARD <key>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.sadd("key", "a", "b", "c");
+const cardinality = await redis.scard("key");
+console.log(cardinality); // 3
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.scard("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.scard("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.sCard("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.scard("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.SCard(context.Background(), "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.scard("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.scard("my-key")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/set/sdiff.mdx b/redis/commands/set/sdiff.mdx
new file mode 100644
index 000000000..270b761ab
--- /dev/null
+++ b/redis/commands/set/sdiff.mdx
@@ -0,0 +1,167 @@
+---
+title: "SDIFF"
+description: "Get set difference."
+---
+
+Use `SDIFF` to get set difference.
+
+## Syntax
+
+```redis
+SDIFF <key> [<key> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | Yes | Redis key targeted by the command. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of bulk-string members |
+| RESP3 | Set of bulk-string members |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.sadd("set1", "a", "b", "c");
+await redis.sadd("set2", "c", "d", "e");
+const diff =  await redis.sdiff("set1", "set2");
+console.log(diff); // ["a", "b"]
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.sdiff("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.sdiff("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.sDiff("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.sdiff(["my-key"])
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.SDiff(context.Background(), "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.sdiff("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.sdiff(&["my-key"])?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/set/sdiffstore.mdx b/redis/commands/set/sdiffstore.mdx
new file mode 100644
index 000000000..ff1044cab
--- /dev/null
+++ b/redis/commands/set/sdiffstore.mdx
@@ -0,0 +1,168 @@
+---
+title: "SDIFFSTORE"
+description: "Store set difference."
+---
+
+Use `SDIFFSTORE` to store set difference.
+
+## Syntax
+
+```redis
+SDIFFSTORE <destination> <key> [<key> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<destination>` | Yes | No | Redis key used as destination. |
+| `<key>` | Yes | Yes | Redis key targeted by the command. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.sadd("set1", "a", "b", "c");
+await redis.sadd("set2", "c", "d", "e");
+await redis.sdiff("dest", "set1", "set2");
+console.log(diff); // ["a", "b"]
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.sdiffstore("destination-key", "my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.sdiffstore("destination-key", "my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.sDiffStore("destination-key", "my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.sdiffstore("destination-key", ["my-key"])
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.SDiffStore(context.Background(), "destination-key", "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.sdiffstore("destination-key", "my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.sdiffstore("destination-key", &["my-key"])?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/set/sinter.mdx b/redis/commands/set/sinter.mdx
new file mode 100644
index 000000000..f85f64ac1
--- /dev/null
+++ b/redis/commands/set/sinter.mdx
@@ -0,0 +1,167 @@
+---
+title: "SINTER"
+description: "Get set intersection."
+---
+
+Use `SINTER` to get set intersection.
+
+## Syntax
+
+```redis
+SINTER <key> [<key> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | Yes | Redis key targeted by the command. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of bulk-string members |
+| RESP3 | Set of bulk-string members |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.sadd("set1", "a", "b", "c");
+await redis.sadd("set2", "c", "d", "e");
+const intersection =  await redis.sinter("set1", "set2");
+console.log(intersection); // ["c"]
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.sinter("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.sinter("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.sInter("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.sinter(["my-key"])
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.SInter(context.Background(), "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.sinter("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.sinter(&["my-key"])?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/set/sintercard.mdx b/redis/commands/set/sintercard.mdx
new file mode 100644
index 000000000..2e7af9bdb
--- /dev/null
+++ b/redis/commands/set/sintercard.mdx
@@ -0,0 +1,167 @@
+---
+title: "SINTERCARD"
+description: "Get intersection cardinality."
+---
+
+Use `SINTERCARD` to get intersection cardinality.
+
+## Syntax
+
+```redis
+SINTERCARD <numkeys> <key> [<key> ...] [LIMIT <limit>]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<numkeys>` | Yes | No | Number of key arguments that follow. |
+| `<key>` | Yes | Yes | Redis key targeted by the command. |
+| `LIMIT <limit>` | No | No | Stop counting once this many members match; `0` means no limit. |
+
+## Important points
+
+- `numkeys` must equal the number of key arguments that immediately follow it.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+const result = await redis.sintercard(["my-key"]);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+<Note>
+  This command is not supported yet in `upstash_redis`.
+</Note>
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.sintercard("1", "my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.sInterCard(["my-key"]);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.sintercard(1, ["my-key"])
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.SInterCard(context.Background(), 0, "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.sintercard("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("SINTERCARD");
+    command.arg("1");
+    command.arg("my-key");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/set/sinterstore.mdx b/redis/commands/set/sinterstore.mdx
new file mode 100644
index 000000000..2ca7eb1a5
--- /dev/null
+++ b/redis/commands/set/sinterstore.mdx
@@ -0,0 +1,167 @@
+---
+title: "SINTERSTORE"
+description: "Store set intersection."
+---
+
+Use `SINTERSTORE` to store set intersection.
+
+## Syntax
+
+```redis
+SINTERSTORE <destination> <key> [<key> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<destination>` | Yes | No | Redis key used as destination. |
+| `<key>` | Yes | Yes | Redis key targeted by the command. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.sadd("set1", "a", "b", "c");
+await redis.sadd("set2", "c", "d", "e");
+await redis.sinterstore("destination", "set1", "set2");
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.sinterstore("destination-key", "my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.sinterstore("destination-key", "my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.sInterStore("destination-key", "my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.sinterstore("destination-key", ["my-key"])
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.SInterStore(context.Background(), "destination-key", "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.sinterstore("destination-key", "my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.sinterstore("destination-key", &["my-key"])?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/set/sismember.mdx b/redis/commands/set/sismember.mdx
new file mode 100644
index 000000000..5b91af3c2
--- /dev/null
+++ b/redis/commands/set/sismember.mdx
@@ -0,0 +1,167 @@
+---
+title: "SISMEMBER"
+description: "Check if member exists in set."
+---
+
+Use `SISMEMBER` to check if member exists in set.
+
+## Syntax
+
+```redis
+SISMEMBER <key> <member>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<member>` | Yes | No | Member name. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer: `1` if the member is in the set, `0` otherwise |
+| RESP3 | Integer: `1` if the member is in the set, `0` otherwise |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.sadd("set", "a", "b", "c");
+const isMember =  await redis.sismember("set", "a");
+console.log(isMember); // 1
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.sismember("my-key", "member")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.sismember("my-key", "member");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.sIsMember("my-key", "member");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.sismember("my-key", "member")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.SIsMember(context.Background(), "my-key", "member").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.sismember("my-key", "member");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.sismember("my-key", "member")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/set/smembers.mdx b/redis/commands/set/smembers.mdx
new file mode 100644
index 000000000..079b0d69e
--- /dev/null
+++ b/redis/commands/set/smembers.mdx
@@ -0,0 +1,166 @@
+---
+title: "SMEMBERS"
+description: "Get all set members."
+---
+
+Use `SMEMBERS` to get all set members.
+
+## Syntax
+
+```redis
+SMEMBERS <key>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of bulk-string members |
+| RESP3 | Array of bulk-string members |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.sadd("set", "a", "b", "c");
+const members =  await redis.smembers("set");
+console.log(members); // ["a", "b", "c"]
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.smembers("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.smembers("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.sMembers("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.smembers("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.SMembers(context.Background(), "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.smembers("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.smembers("my-key")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/set/smismember.mdx b/redis/commands/set/smismember.mdx
new file mode 100644
index 000000000..444443f10
--- /dev/null
+++ b/redis/commands/set/smismember.mdx
@@ -0,0 +1,167 @@
+---
+title: "SMISMEMBER"
+description: "Check multiple members."
+---
+
+Use `SMISMEMBER` to check multiple members.
+
+## Syntax
+
+```redis
+SMISMEMBER <key> <member> [<member> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<member>` | Yes | Yes | Member name. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of integers, one per queried member |
+| RESP3 | Array of integers, one per queried member |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.sadd("set", "a", "b", "c");
+const members =  await redis.smismember("set", ["a", "b", "d"]);
+console.log(members); // [1, 1, 0]
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.smismember("my-key", "member")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.smismember("my-key", "member");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.smIsMember("my-key", ["member"]);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.smismember("my-key", ["member"])
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.SMIsMember(context.Background(), "my-key", "member").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.smismember("my-key", "member");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.smismember("my-key", &["member"])?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/set/smove.mdx b/redis/commands/set/smove.mdx
new file mode 100644
index 000000000..9d0d69f62
--- /dev/null
+++ b/redis/commands/set/smove.mdx
@@ -0,0 +1,170 @@
+---
+title: "SMOVE"
+description: "Move member between sets."
+---
+
+Use `SMOVE` to move member between sets.
+
+## Syntax
+
+```redis
+SMOVE <source> <destination> <member>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<source>` | Yes | No | Redis key used as source. |
+| `<destination>` | Yes | No | Redis key used as destination. |
+| `<member>` | Yes | No | Member name. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer: `1` if the member was moved, `0` if it is not in the source set |
+| RESP3 | Integer: `1` if the member was moved, `0` if it is not in the source set |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.sadd("original", "a", "b", "c");
+const moved =  await redis.smove("original", "destination", "a");
+// moved:       1
+// original:    ["b", "c"]
+// destination: ["a"]
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.smove("source-key", "destination-key", "member")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.smove("source-key", "destination-key", "member");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.sMove("source-key", "destination-key", "member");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.smove("source-key", "destination-key", "member")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.SMove(context.Background(), "source-key", "destination-key", "member").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.smove("source-key", "destination-key", "member");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.smove("source-key", "destination-key", "member")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/set/spop.mdx b/redis/commands/set/spop.mdx
new file mode 100644
index 000000000..dcdd326c3
--- /dev/null
+++ b/redis/commands/set/spop.mdx
@@ -0,0 +1,167 @@
+---
+title: "SPOP"
+description: "Remove random members."
+---
+
+Use `SPOP` to remove random members.
+
+## Syntax
+
+```redis
+SPOP <key> [<count>]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<count>` | No | No | Number of members to pop. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Null bulk string or null array, Bulk string, or array of bulk-string members |
+| RESP3 | Null, Bulk string, or set of bulk-string members |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.sadd("set", "a", "b", "c");
+const popped = await redis.spop("set");
+console.log(popped); // "a"
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.spop("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.spop("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.sPop("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.spop("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.SPop(context.Background(), "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.spop("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result: Option<String> = connection.spop("my-key")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/set/srandmember.mdx b/redis/commands/set/srandmember.mdx
new file mode 100644
index 000000000..a5a9e02db
--- /dev/null
+++ b/redis/commands/set/srandmember.mdx
@@ -0,0 +1,167 @@
+---
+title: "SRANDMEMBER"
+description: "Get random members."
+---
+
+Use `SRANDMEMBER` to get random members.
+
+## Syntax
+
+```redis
+SRANDMEMBER <key> [<count>]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<count>` | No | No | Number of members to return; a negative count may repeat members. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Null bulk string or null array, Bulk string, or array of bulk-string members |
+| RESP3 | Null, Bulk string, or array of bulk-string members |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.sadd("set", "a", "b", "c");
+const member = await redis.srandmember("set");
+console.log(member); // "a"
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.srandmember("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.srandmember("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.sRandMember("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.srandmember("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.SRandMember(context.Background(), "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.srandmember("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.srandmember("my-key")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/set/srem.mdx b/redis/commands/set/srem.mdx
new file mode 100644
index 000000000..a26b5ff7e
--- /dev/null
+++ b/redis/commands/set/srem.mdx
@@ -0,0 +1,167 @@
+---
+title: "SREM"
+description: "Remove members from a set."
+---
+
+Use `SREM` to remove members from a set.
+
+## Syntax
+
+```redis
+SREM <key> <member> [<member> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<member>` | Yes | Yes | Member name. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.sadd("set", "a", "b", "c");
+const removed = await redis.srem("set", "a", "b", "d");
+console.log(removed); // 2
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.srem("my-key", "member")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.srem("my-key", "member");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.sRem("my-key", "member");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.srem("my-key", "member")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.SRem(context.Background(), "my-key", "member").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.srem("my-key", "member");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.srem("my-key", "member")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/set/sscan.mdx b/redis/commands/set/sscan.mdx
new file mode 100644
index 000000000..10cd7a1ea
--- /dev/null
+++ b/redis/commands/set/sscan.mdx
@@ -0,0 +1,176 @@
+---
+title: "SSCAN"
+description: "Incrementally iterate set members."
+---
+
+Use `SSCAN` to incrementally iterate set members.
+
+## Syntax
+
+```redis
+SSCAN <key> <cursor> [MATCH <pattern>] [COUNT <count>]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<cursor>` | Yes | No | Cursor returned by the previous call; start at `0`. |
+| `MATCH <pattern>` | No | No | Return only elements matching this glob-style pattern. |
+| `COUNT <count>` | No | No | Hint for how much work each iteration should do. |
+
+## Important points
+
+- This operation can inspect a large part of the database. Prefer cursor-based scans where possible and avoid unbounded use on hot paths.
+- The cursor is opaque. Start with `0` and continue until the server returns cursor `0`; a single iteration may return no elements.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Two-element array: cursor and array of bulk-string members |
+| RESP3 | Two-element array: cursor and array of bulk-string members |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.sadd("key", "a", "ab","b", "c");
+const [newCursor, fields] = await redis.sscan("key", 0, { match: "a*"});
+console.log(newCursor); // likely `0` since this is a very small set
+console.log(fields); // ["a", "ab"]
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.sscan("my-key", 0)
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.sscan("my-key", "0");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.sScan("my-key", "0");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.sscan("my-key", 0)
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, _, err := client.SScan(context.Background(), "my-key", 0, "*", 0).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.sscan("my-key", "0");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("SSCAN");
+    command.arg("my-key");
+    command.arg("0");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/set/sunion.mdx b/redis/commands/set/sunion.mdx
new file mode 100644
index 000000000..bbcc7c9d7
--- /dev/null
+++ b/redis/commands/set/sunion.mdx
@@ -0,0 +1,167 @@
+---
+title: "SUNION"
+description: "Get set union."
+---
+
+Use `SUNION` to get set union.
+
+## Syntax
+
+```redis
+SUNION <key> [<key> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | Yes | Redis key targeted by the command. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of bulk-string members |
+| RESP3 | Set of bulk-string members |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.sadd("set1", "a", "b", "c");
+await redis.sadd("set2", "c", "d", "e");
+const union =  await redis.sunion("set1", "set2");
+console.log(union); // ["a", "b", "c", "d", "e"]
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.sunion("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.sunion("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.sUnion("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.sunion(["my-key"])
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.SUnion(context.Background(), "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.sunion("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.sunion(&["my-key"])?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/set/sunionstore.mdx b/redis/commands/set/sunionstore.mdx
new file mode 100644
index 000000000..60d189e39
--- /dev/null
+++ b/redis/commands/set/sunionstore.mdx
@@ -0,0 +1,167 @@
+---
+title: "SUNIONSTORE"
+description: "Store set union."
+---
+
+Use `SUNIONSTORE` to store set union.
+
+## Syntax
+
+```redis
+SUNIONSTORE <destination> <key> [<key> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<destination>` | Yes | No | Redis key used as destination. |
+| `<key>` | Yes | Yes | Redis key targeted by the command. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.sadd("set1", "a", "b", "c");
+await redis.sadd("set2", "c", "d", "e");
+await redis.sunionstore("destination", "set1", "set2");
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.sunionstore("destination-key", "my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.sunionstore("destination-key", "my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.sUnionStore("destination-key", "my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.sunionstore("destination-key", ["my-key"])
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.SUnionStore(context.Background(), "destination-key", "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.sunionstore("destination-key", "my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.sunionstore("destination-key", &["my-key"])?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/sorted-set/bzmpop.mdx b/redis/commands/sorted-set/bzmpop.mdx
new file mode 100644
index 000000000..850016718
--- /dev/null
+++ b/redis/commands/sorted-set/bzmpop.mdx
@@ -0,0 +1,168 @@
+---
+title: "BZMPOP"
+description: "Pop from the first non-empty sorted set, blocking until one arrives."
+---
+
+Use `BZMPOP` to pop members from the first non-empty sorted set among several, blocking until one has members or the timeout expires.
+
+## Syntax
+
+```redis
+BZMPOP <timeout> <numkeys> <key> [<key> ...] (MIN | MAX) [COUNT <count>]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<timeout>` | Yes | No | Seconds to block; `0` blocks indefinitely. |
+| `<numkeys>` | Yes | No | Number of key arguments that follow. |
+| `<key>` | Yes | Yes | Redis key targeted by the command. |
+| `(MIN \| MAX)` | Yes | No | Choose one form: `MIN`; `MAX`. |
+| `COUNT <count>` | No | No | Maximum number of members to pop. |
+
+## Important points
+
+- A blocking form holds the request until data arrives or its timeout expires. Set the client/network timeout longer than the command timeout.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Null bulk string or null array, or two-element array: key and array of member/score pairs |
+| RESP3 | Null, or two-element array: key and array of member/score pairs |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+<Note>
+  This command is not supported yet in `upstash_redis`.
+</Note>
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.bzmpop("1.5", "1", "my-key", "MIN");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.bzmPop(1.5, "my-key", "MIN");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.bzmpop(1.5, 1, ["my-key"], min=True)
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+    "time"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    _, result, err := client.BZMPop(context.Background(), 1500*time.Millisecond, "min", 0, "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.bzmpop(1.5, redis.clients.jedis.args.SortedSetOption.MIN, "my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("BZMPOP");
+    command.arg("1.5");
+    command.arg("1");
+    command.arg("my-key");
+    command.arg("MIN");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/sorted-set/bzpopmax.mdx b/redis/commands/sorted-set/bzpopmax.mdx
new file mode 100644
index 000000000..c5b97a869
--- /dev/null
+++ b/redis/commands/sorted-set/bzpopmax.mdx
@@ -0,0 +1,163 @@
+---
+title: "BZPOPMAX"
+description: "Pop the highest-scoring member, blocking until one arrives."
+---
+
+Use `BZPOPMAX` to pop the highest-scoring member from the first non-empty sorted set, blocking until one has a member or the timeout expires.
+
+## Syntax
+
+```redis
+BZPOPMAX <key> [<key> ...] <timeout>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | Yes | Redis key targeted by the command. |
+| `<timeout>` | Yes | No | Seconds to block; `0` blocks indefinitely. |
+
+## Important points
+
+- A blocking form holds the request until data arrives or its timeout expires. Set the client/network timeout longer than the command timeout.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Null bulk string or null array, or three-element key/member/score array |
+| RESP3 | Null, or three-element key/member/score array |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+<Note>
+  This command is not supported yet in `upstash_redis`.
+</Note>
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.bzpopmax("my-key", "1.5");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.bzPopMax("my-key", 1.5);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.bzpopmax(["my-key"], timeout=1.5)
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+    "time"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.BZPopMax(context.Background(), 1500*time.Millisecond, "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.bzpopmax(1.5, "my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("BZPOPMAX");
+    command.arg("my-key");
+    command.arg("1.5");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/sorted-set/bzpopmin.mdx b/redis/commands/sorted-set/bzpopmin.mdx
new file mode 100644
index 000000000..45d560114
--- /dev/null
+++ b/redis/commands/sorted-set/bzpopmin.mdx
@@ -0,0 +1,163 @@
+---
+title: "BZPOPMIN"
+description: "Pop the lowest-scoring member, blocking until one arrives."
+---
+
+Use `BZPOPMIN` to pop the lowest-scoring member from the first non-empty sorted set, blocking until one has a member or the timeout expires.
+
+## Syntax
+
+```redis
+BZPOPMIN <key> [<key> ...] <timeout>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | Yes | Redis key targeted by the command. |
+| `<timeout>` | Yes | No | Seconds to block; `0` blocks indefinitely. |
+
+## Important points
+
+- A blocking form holds the request until data arrives or its timeout expires. Set the client/network timeout longer than the command timeout.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Null bulk string or null array, or three-element key/member/score array |
+| RESP3 | Null, or three-element key/member/score array |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+<Note>
+  This command is not supported yet in `upstash_redis`.
+</Note>
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.bzpopmin("my-key", "1.5");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.bzPopMin("my-key", 1.5);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.bzpopmin(["my-key"], timeout=1.5)
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+    "time"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.BZPopMin(context.Background(), 1500*time.Millisecond, "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.bzpopmin(1.5, "my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("BZPOPMIN");
+    command.arg("my-key");
+    command.arg("1.5");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/sorted-set/overview.mdx b/redis/commands/sorted-set/overview.mdx
new file mode 100644
index 000000000..4ed7fbeed
--- /dev/null
+++ b/redis/commands/sorted-set/overview.mdx
@@ -0,0 +1,44 @@
+---
+title: "Sorted Set commands"
+sidebarTitle: "Overview"
+description: "Commands for storing and manipulating scored collections."
+---
+
+<CardGroup cols={2}>
+<Card title="BZMPOP" href="/redis/commands/sorted-set/bzmpop">Blocking pop from sorted sets</Card>
+<Card title="BZPOPMAX" href="/redis/commands/sorted-set/bzpopmax">Blocking pop max score member</Card>
+<Card title="BZPOPMIN" href="/redis/commands/sorted-set/bzpopmin">Blocking pop min score member</Card>
+<Card title="ZADD" href="/redis/commands/sorted-set/zadd">Add members with scores</Card>
+<Card title="ZCARD" href="/redis/commands/sorted-set/zcard">Get sorted set cardinality</Card>
+<Card title="ZCOUNT" href="/redis/commands/sorted-set/zcount">Count members in score range</Card>
+<Card title="ZDIFF" href="/redis/commands/sorted-set/zdiff">Get sorted set difference</Card>
+<Card title="ZDIFFSTORE" href="/redis/commands/sorted-set/zdiffstore">Store sorted set difference</Card>
+<Card title="ZINCRBY" href="/redis/commands/sorted-set/zincrby">Increment member's score</Card>
+<Card title="ZINTER" href="/redis/commands/sorted-set/zinter">Get sorted set intersection</Card>
+<Card title="ZINTERCARD" href="/redis/commands/sorted-set/zintercard">Get intersection cardinality</Card>
+<Card title="ZINTERSTORE" href="/redis/commands/sorted-set/zinterstore">Store sorted set intersection</Card>
+<Card title="ZLEXCOUNT" href="/redis/commands/sorted-set/zlexcount">Count members in lex range</Card>
+<Card title="ZMPOP" href="/redis/commands/sorted-set/zmpop">Pop members from sorted sets</Card>
+<Card title="ZMSCORE" href="/redis/commands/sorted-set/zmscore">Get scores of multiple members</Card>
+<Card title="ZPOPMAX" href="/redis/commands/sorted-set/zpopmax">Pop members with highest scores</Card>
+<Card title="ZPOPMIN" href="/redis/commands/sorted-set/zpopmin">Pop members with lowest scores</Card>
+<Card title="ZRANDMEMBER" href="/redis/commands/sorted-set/zrandmember">Get random members</Card>
+<Card title="ZRANGE" href="/redis/commands/sorted-set/zrange">Get members by index range</Card>
+<Card title="ZRANGEBYLEX" href="/redis/commands/sorted-set/zrangebylex">Get members by lex range</Card>
+<Card title="ZRANGEBYSCORE" href="/redis/commands/sorted-set/zrangebyscore">Get members by score range</Card>
+<Card title="ZRANGESTORE" href="/redis/commands/sorted-set/zrangestore">Store range result</Card>
+<Card title="ZRANK" href="/redis/commands/sorted-set/zrank">Get member's rank</Card>
+<Card title="ZREM" href="/redis/commands/sorted-set/zrem">Remove members</Card>
+<Card title="ZREMRANGEBYLEX" href="/redis/commands/sorted-set/zremrangebylex">Remove members by lex range</Card>
+<Card title="ZREMRANGEBYRANK" href="/redis/commands/sorted-set/zremrangebyrank">Remove members by rank range</Card>
+<Card title="ZREMRANGEBYSCORE" href="/redis/commands/sorted-set/zremrangebyscore">Remove members by score range</Card>
+<Card title="ZREVRANGE" href="/redis/commands/sorted-set/zrevrange">Get members in reverse order</Card>
+<Card title="ZREVRANGEBYLEX" href="/redis/commands/sorted-set/zrevrangebylex">Reverse lex range query</Card>
+<Card title="ZREVRANGEBYSCORE" href="/redis/commands/sorted-set/zrevrangebyscore">Reverse score range query</Card>
+<Card title="ZREVRANK" href="/redis/commands/sorted-set/zrevrank">Get member's reverse rank</Card>
+<Card title="ZSCAN" href="/redis/commands/sorted-set/zscan">Incrementally iterate sorted set</Card>
+<Card title="ZSCORE" href="/redis/commands/sorted-set/zscore">Get member's score</Card>
+<Card title="ZUNION" href="/redis/commands/sorted-set/zunion">Get sorted set union</Card>
+<Card title="ZUNIONSTORE" href="/redis/commands/sorted-set/zunionstore">Store sorted set union</Card>
+</CardGroup>
+
diff --git a/redis/commands/sorted-set/zadd.mdx b/redis/commands/sorted-set/zadd.mdx
new file mode 100644
index 000000000..c8979f823
--- /dev/null
+++ b/redis/commands/sorted-set/zadd.mdx
@@ -0,0 +1,178 @@
+---
+title: "ZADD"
+description: "Add members with scores."
+---
+
+Use `ZADD` to add members with scores.
+
+## Syntax
+
+```redis
+ZADD <key> [NX | XX] [GT | LT] [CH] [INCR] <score> <member> [<score> <member> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `(NX \| XX)` | No | No | Choose one form: `NX` (only add new members, never update an existing one); `XX` (only update members that already exist). |
+| `(GT \| LT)` | No | No | Choose one form: `GT` (only update when the new score is greater than the current one); `LT` (only update when it is less). Neither blocks new members from being added. |
+| `CH` | No | No | Count changed members rather than only new members. |
+| `INCR` | No | No | Increment one member instead of adding normally. |
+| `<score> <member>` | Yes | Yes | Score followed by the member it applies to. Repeat to add several members. |
+
+## Important points
+
+- `NX` cannot be combined with `XX`, `GT`, or `LT`, and `GT` and `LT` cannot be used together.
+- RESP2 represents floating-point reply values as bulk strings; RESP3 may use native double replies. Client libraries commonly decode either form to a language number.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Null bulk string or null array or Integer or Bulk string containing a number |
+| RESP3 | Null or Integer or Double |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.zadd(
+    "key",
+    { score: 2, member: "member" },
+    { score: 3, member: "member2"},
+);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.zadd("my-key", {"member": 1.5})
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.zadd("my-key", "1.5", "member");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.zAdd("my-key", { score: 1.5, value: "member" });
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.zadd("my-key", {"member": 1.5})
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ZAdd(context.Background(), "my-key", redis.Z{Score: 1.5, Member: "member"}).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.zadd("my-key", 1.5, "member");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.zadd("my-key", "member", 1.5)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/sorted-set/zcard.mdx b/redis/commands/sorted-set/zcard.mdx
new file mode 100644
index 000000000..c796615db
--- /dev/null
+++ b/redis/commands/sorted-set/zcard.mdx
@@ -0,0 +1,169 @@
+---
+title: "ZCARD"
+description: "Get sorted set cardinality."
+---
+
+Use `ZCARD` to get sorted set cardinality.
+
+## Syntax
+
+```redis
+ZCARD <key>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.zadd("key",
+    { score: 1, member: "one"},
+    { score: 2, member: "two" },
+);
+const elements = await redis.zrank("key");
+console.log(elements); // 2
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.zcard("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.zcard("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.zCard("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.zcard("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ZCard(context.Background(), "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.zcard("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.zcard("my-key")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/sorted-set/zcount.mdx b/redis/commands/sorted-set/zcount.mdx
new file mode 100644
index 000000000..d79be3b26
--- /dev/null
+++ b/redis/commands/sorted-set/zcount.mdx
@@ -0,0 +1,171 @@
+---
+title: "ZCOUNT"
+description: "Count members in score range."
+---
+
+Use `ZCOUNT` to count members in score range.
+
+## Syntax
+
+```redis
+ZCOUNT <key> <min> <max>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<min>` | Yes | No | Minimum score: a number, `-inf`, or `(score` for an exclusive bound. |
+| `<max>` | Yes | No | Maximum score: a number, `+inf`, or `(score` for an exclusive bound. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.zadd("key",
+    { score: 1, member: "one"},
+    { score: 2, member: "two" },
+);
+const elements = await redis.zcount("key", "(1", "+inf");
+console.log(elements); // 1
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.zcount("my-key", 1.5, 1.5)
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.zcount("my-key", "1.5", "1.5");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.zCount("my-key", 1.5, 1.5);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.zcount("my-key", 1.5, 1.5)
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ZCount(context.Background(), "my-key", "1.5", "1.5").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.zcount("my-key", 1.5, 1.5);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.zcount("my-key", 1.5, 1.5)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/sorted-set/zdiff.mdx b/redis/commands/sorted-set/zdiff.mdx
new file mode 100644
index 000000000..dc20c131a
--- /dev/null
+++ b/redis/commands/sorted-set/zdiff.mdx
@@ -0,0 +1,169 @@
+---
+title: "ZDIFF"
+description: "Get sorted set difference."
+---
+
+Use `ZDIFF` to get sorted set difference.
+
+## Syntax
+
+```redis
+ZDIFF <numkeys> <key> [<key> ...] [WITHSCORES]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<numkeys>` | Yes | No | Number of key arguments that follow. |
+| `<key>` | Yes | Yes | Redis key targeted by the command. |
+| `WITHSCORES` | No | No | Include sorted-set scores. |
+
+## Important points
+
+- `numkeys` must equal the number of key arguments that immediately follow it.
+- Pair-based results may be flattened into one alternating array in RESP2 while RESP3 preserves nested pairs or a map.
+- RESP2 represents floating-point reply values as bulk strings; RESP3 may use native double replies. Client libraries commonly decode either form to a language number.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of members, or flat member/score array with `WITHSCORES` |
+| RESP3 | Array of members, or array of member/score pairs with `WITHSCORES` |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.zdiff(["my-key"])
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.zdiff("1", "my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.zDiff("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.zdiff(["my-key"])
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ZDiff(context.Background(), "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.zdiff("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("ZDIFF");
+    command.arg("1");
+    command.arg("my-key");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/sorted-set/zdiffstore.mdx b/redis/commands/sorted-set/zdiffstore.mdx
new file mode 100644
index 000000000..24135e2e1
--- /dev/null
+++ b/redis/commands/sorted-set/zdiffstore.mdx
@@ -0,0 +1,172 @@
+---
+title: "ZDIFFSTORE"
+description: "Store sorted set difference."
+---
+
+Use `ZDIFFSTORE` to store sorted set difference.
+
+## Syntax
+
+```redis
+ZDIFFSTORE <destination> <numkeys> <key> [<key> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<destination>` | Yes | No | Redis key used as destination. |
+| `<numkeys>` | Yes | No | Number of key arguments that follow. |
+| `<key>` | Yes | Yes | Redis key targeted by the command. |
+
+## Important points
+
+- `numkeys` must equal the number of key arguments that immediately follow it.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const values = await redis.zdiffstore("destination", 2, "key1", "key2");
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.zdiffstore("destination-key", ["my-key"])
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.zdiffstore("destination-key", "1", "my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.zDiffStore("destination-key", "my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.zdiffstore("destination-key", ["my-key"])
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ZDiffStore(context.Background(), "destination-key", "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.zdiffstore("destination-key", "my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("ZDIFFSTORE");
+    command.arg("destination-key");
+    command.arg("1");
+    command.arg("my-key");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/sorted-set/zincrby.mdx b/redis/commands/sorted-set/zincrby.mdx
new file mode 100644
index 000000000..b4c0b277f
--- /dev/null
+++ b/redis/commands/sorted-set/zincrby.mdx
@@ -0,0 +1,172 @@
+---
+title: "ZINCRBY"
+description: "Increment member's score."
+---
+
+Use `ZINCRBY` to increment member's score.
+
+## Syntax
+
+```redis
+ZINCRBY <key> <increment> <member>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<increment>` | Yes | No | Amount to add to the member's score. |
+| `<member>` | Yes | No | Member name. |
+
+## Important points
+
+- RESP2 represents floating-point reply values as bulk strings; RESP3 may use native double replies. Client libraries commonly decode either form to a language number.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Bulk string containing a number |
+| RESP3 | Double |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.zadd("key", 1, "member");
+const value = await redis.zincrby("key", 2, "member");
+console.log(value); // 3
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.zincrby("my-key", 1, "member")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.zincrby("my-key", "1", "member");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.zIncrBy("my-key", 1, "member");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.zincrby("my-key", 1, "member")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ZIncrBy(context.Background(), "my-key", 1, "member").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.zincrby("my-key", 1, "member");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.zincr("my-key", "member", 1)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/sorted-set/zinter.mdx b/redis/commands/sorted-set/zinter.mdx
new file mode 100644
index 000000000..f59f4c9ac
--- /dev/null
+++ b/redis/commands/sorted-set/zinter.mdx
@@ -0,0 +1,171 @@
+---
+title: "ZINTER"
+description: "Get sorted set intersection."
+---
+
+Use `ZINTER` to get sorted set intersection.
+
+## Syntax
+
+```redis
+ZINTER <numkeys> <key> [<key> ...] [WEIGHTS <weight> [<weight> ...]] [AGGREGATE SUM | MIN | MAX] [WITHSCORES]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<numkeys>` | Yes | No | Number of key arguments that follow. |
+| `<key>` | Yes | Yes | Redis key targeted by the command. |
+| `WEIGHTS <weight>` | No | Yes | Multiplier applied to each input key's scores, in the order the keys were given. |
+| `(AGGREGATE SUM \| MIN \| MAX)` | No | No | Under `AGGREGATE`, choose one form: `SUM`; `MIN`; `MAX`. |
+| `WITHSCORES` | No | No | Include sorted-set scores. |
+
+## Important points
+
+- `numkeys` must equal the number of key arguments that immediately follow it.
+- Pair-based results may be flattened into one alternating array in RESP2 while RESP3 preserves nested pairs or a map.
+- RESP2 represents floating-point reply values as bulk strings; RESP3 may use native double replies. Client libraries commonly decode either form to a language number.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of members, or flat member/score array with `WITHSCORES` |
+| RESP3 | Array of members, or array of member/score pairs with `WITHSCORES` |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.zinter(["my-key"])
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.zinter("1", "my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.zInter("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.zinter(["my-key"])
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ZInter(context.Background(), &redis.ZStore{Keys: []string{"my-key"}}).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.zinter(new redis.clients.jedis.params.ZParams(), "my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("ZINTER");
+    command.arg("1");
+    command.arg("my-key");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/sorted-set/zintercard.mdx b/redis/commands/sorted-set/zintercard.mdx
new file mode 100644
index 000000000..c7f47fa4a
--- /dev/null
+++ b/redis/commands/sorted-set/zintercard.mdx
@@ -0,0 +1,159 @@
+---
+title: "ZINTERCARD"
+description: "Get intersection cardinality."
+---
+
+Use `ZINTERCARD` to get intersection cardinality.
+
+## Syntax
+
+```redis
+ZINTERCARD <numkeys> <key> [<key> ...] [LIMIT <limit>]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<numkeys>` | Yes | No | Number of key arguments that follow. |
+| `<key>` | Yes | Yes | Redis key targeted by the command. |
+| `LIMIT <limit>` | No | No | Stop counting once this many members match; `0` means no limit. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+<Note>
+  This command is not supported yet in `upstash_redis`.
+</Note>
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.zintercard("1", "my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.zInterCard("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.zintercard(1, ["my-key"])
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ZInterCard(context.Background(), 0, "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.zintercard("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("ZINTERCARD");
+    command.arg("1");
+    command.arg("my-key");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/sorted-set/zinterstore.mdx b/redis/commands/sorted-set/zinterstore.mdx
new file mode 100644
index 000000000..915c1ddc9
--- /dev/null
+++ b/redis/commands/sorted-set/zinterstore.mdx
@@ -0,0 +1,183 @@
+---
+title: "ZINTERSTORE"
+description: "Store sorted set intersection."
+---
+
+Use `ZINTERSTORE` to store sorted set intersection.
+
+## Syntax
+
+```redis
+ZINTERSTORE <destination> <numkeys> <key> [<key> ...] [WEIGHTS <weight> [<weight> ...]] [AGGREGATE SUM | MIN | MAX]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<destination>` | Yes | No | Redis key used as destination. |
+| `<numkeys>` | Yes | No | Number of key arguments that follow. |
+| `<key>` | Yes | Yes | Redis key targeted by the command. |
+| `WEIGHTS <weight>` | No | Yes | Multiplier applied to each input key's scores, in the order the keys were given. |
+| `(AGGREGATE SUM \| MIN \| MAX)` | No | No | Under `AGGREGATE`, choose one form: `SUM`; `MIN`; `MAX`. |
+
+## Important points
+
+- `numkeys` must equal the number of key arguments that immediately follow it.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.zadd(
+    "key1",
+    { score: 1, member: "member1" },
+)
+await redis.zadd(
+    "key2",
+    { score: 1, member: "member1" },
+    { score: 2, member: "member2" },
+)
+
+const res = await redis.zinterstore("destination", 2, ["key1", "key2"]);
+console.log(res) // 1
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.zinterstore("destination-key", ["my-key"])
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.zinterstore("destination-key", "1", "my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.zInterStore("destination-key", "my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.zinterstore("destination-key", ["my-key"])
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ZInterStore(context.Background(), "destination-key", &redis.ZStore{Keys: []string{"my-key"}}).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.zinterstore("destination-key", "my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.zinterstore("destination-key", &["my-key"])?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/sorted-set/zlexcount.mdx b/redis/commands/sorted-set/zlexcount.mdx
new file mode 100644
index 000000000..678f29be3
--- /dev/null
+++ b/redis/commands/sorted-set/zlexcount.mdx
@@ -0,0 +1,171 @@
+---
+title: "ZLEXCOUNT"
+description: "Count members in lex range."
+---
+
+Use `ZLEXCOUNT` to count members in lex range.
+
+## Syntax
+
+```redis
+ZLEXCOUNT <key> <min> <max>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<min>` | Yes | No | Lexicographic minimum: `-`, `+`, `[member` (inclusive), or `(member` (exclusive). |
+| `<max>` | Yes | No | Lexicographic maximum: `-`, `+`, `[member` (inclusive), or `(member` (exclusive). |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.zadd("key",
+    { score: 1, member: "one"},
+    { score: 2, member: "two" },
+);
+const elements = await redis.zlexcount("key", "two", "+");
+console.log(elements); // 1
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.zlexcount("my-key", "-", "+")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.zlexcount("my-key", "-", "+");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.zLexCount("my-key", "-", "+");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.zlexcount("my-key", "-", "+")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ZLexCount(context.Background(), "my-key", "-", "+").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.zlexcount("my-key", "-", "+");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.zlexcount("my-key", "-", "+")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/sorted-set/zmpop.mdx b/redis/commands/sorted-set/zmpop.mdx
new file mode 100644
index 000000000..0b1e0ddcd
--- /dev/null
+++ b/redis/commands/sorted-set/zmpop.mdx
@@ -0,0 +1,165 @@
+---
+title: "ZMPOP"
+description: "Pop members from sorted sets."
+---
+
+Use `ZMPOP` to pop members from sorted sets.
+
+## Syntax
+
+```redis
+ZMPOP <numkeys> <key> [<key> ...] (MIN | MAX) [COUNT <count>]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<numkeys>` | Yes | No | Number of key arguments that follow. |
+| `<key>` | Yes | Yes | Redis key targeted by the command. |
+| `(MIN \| MAX)` | Yes | No | Choose one form: `MIN`; `MAX`. |
+| `COUNT <count>` | No | No | Maximum number of members to pop. |
+
+## Important points
+
+- RESP2 represents floating-point reply values as bulk strings; RESP3 may use native double replies. Client libraries commonly decode either form to a language number.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Null bulk string or null array, or two-element array: key and array of member/score pairs |
+| RESP3 | Null, or two-element array: key and array of member/score pairs |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+<Note>
+  This command is not supported yet in `upstash_redis`.
+</Note>
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.zmpop("1", "my-key", "MIN");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.zmPop("my-key", "MIN");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.zmpop(1, ["my-key"], min=True)
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    _, result, err := client.ZMPop(context.Background(), "min", 0, "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.zmpop(redis.clients.jedis.args.SortedSetOption.MIN, "my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("ZMPOP");
+    command.arg("1");
+    command.arg("my-key");
+    command.arg("MIN");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/sorted-set/zmscore.mdx b/redis/commands/sorted-set/zmscore.mdx
new file mode 100644
index 000000000..5a45f26cb
--- /dev/null
+++ b/redis/commands/sorted-set/zmscore.mdx
@@ -0,0 +1,177 @@
+---
+title: "ZMSCORE"
+description: "Get scores of multiple members."
+---
+
+Use `ZMSCORE` to get scores of multiple members.
+
+## Syntax
+
+```redis
+ZMSCORE <key> <member> [<member> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<member>` | Yes | Yes | Member name. |
+
+## Important points
+
+- RESP2 represents floating-point reply values as bulk strings; RESP3 may use native double replies. Client libraries commonly decode either form to a language number.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of bulk-string scores or null values, one per member |
+| RESP3 | Array of double scores or null values, one per member |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.zadd("key",
+    { score: 1, member: "m1" },
+    { score: 2, member: "m2" },
+    { score: 3, member: "m3" },
+    { score: 4, member: "m4" },
+)
+
+const scores = await redis.zmscore("key", ["m2", "m4"])
+console.log(scores) // [2, 4]
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.zmscore("my-key", ["member"])
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.zmscore("my-key", "member");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.zmScore("my-key", "member");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.zmscore("my-key", ["member"])
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ZMScore(context.Background(), "my-key", "member").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.zmscore("my-key", "member");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.zscore_multiple("my-key", &["member"])?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/sorted-set/zpopmax.mdx b/redis/commands/sorted-set/zpopmax.mdx
new file mode 100644
index 000000000..056d93903
--- /dev/null
+++ b/redis/commands/sorted-set/zpopmax.mdx
@@ -0,0 +1,169 @@
+---
+title: "ZPOPMAX"
+description: "Pop members with highest scores."
+---
+
+Use `ZPOPMAX` to pop members with highest scores.
+
+## Syntax
+
+```redis
+ZPOPMAX <key> [<count>]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<count>` | No | No | Number of members to pop. |
+
+## Important points
+
+- RESP2 represents floating-point reply values as bulk strings; RESP3 may use native double replies. Client libraries commonly decode either form to a language number.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Flat array of alternating members and bulk-string scores |
+| RESP3 | Flat array of alternating members and double scores |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const popped = await redis.zpopmax("key", 4);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.zpopmax("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.zpopmax("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.zPopMax("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.zpopmax("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ZPopMax(context.Background(), "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.zpopmax("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.zpopmax("my-key", 1)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/sorted-set/zpopmin.mdx b/redis/commands/sorted-set/zpopmin.mdx
new file mode 100644
index 000000000..5993444cb
--- /dev/null
+++ b/redis/commands/sorted-set/zpopmin.mdx
@@ -0,0 +1,169 @@
+---
+title: "ZPOPMIN"
+description: "Pop members with lowest scores."
+---
+
+Use `ZPOPMIN` to pop members with lowest scores.
+
+## Syntax
+
+```redis
+ZPOPMIN <key> [<count>]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<count>` | No | No | Number of members to pop. |
+
+## Important points
+
+- RESP2 represents floating-point reply values as bulk strings; RESP3 may use native double replies. Client libraries commonly decode either form to a language number.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Flat array of alternating members and bulk-string scores |
+| RESP3 | Flat array of alternating members and double scores |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const popped = await redis.zpopmin("key", 4);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.zpopmin("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.zpopmin("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.zPopMin("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.zpopmin("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ZPopMin(context.Background(), "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.zpopmin("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.zpopmin("my-key", 1)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/sorted-set/zrandmember.mdx b/redis/commands/sorted-set/zrandmember.mdx
new file mode 100644
index 000000000..f7a424646
--- /dev/null
+++ b/redis/commands/sorted-set/zrandmember.mdx
@@ -0,0 +1,165 @@
+---
+title: "ZRANDMEMBER"
+description: "Get random members."
+---
+
+Use `ZRANDMEMBER` to get random members.
+
+## Syntax
+
+```redis
+ZRANDMEMBER <key> [<count> [WITHSCORES]]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<count> [WITHSCORES]` | No | No | Number of members to return; a negative count may repeat members. `WITHSCORES` also returns each member's score. |
+
+## Important points
+
+- RESP2 represents floating-point reply values as bulk strings; RESP3 may use native double replies. Client libraries commonly decode either form to a language number.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Null bulk string or null array, Bulk string, array of members, or flat member/score array |
+| RESP3 | Null, Bulk string, array of members, or array of member/score pairs |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.zrandmember("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.zrandmember("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.zRandMember("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.zrandmember("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ZRandMember(context.Background(), "my-key", 1).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.zrandmember("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result: Option<String> = connection.zrandmember("my-key", None)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/sorted-set/zrange.mdx b/redis/commands/sorted-set/zrange.mdx
new file mode 100644
index 000000000..9e66f27d8
--- /dev/null
+++ b/redis/commands/sorted-set/zrange.mdx
@@ -0,0 +1,180 @@
+---
+title: "ZRANGE"
+description: "Get members by index range."
+---
+
+Use `ZRANGE` to get members by index range.
+
+## Syntax
+
+```redis
+ZRANGE <key> <start> <stop> [BYSCORE | BYLEX] [REV] [LIMIT <offset> <count>] [WITHSCORES]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<start>` | Yes | No | Lower bound. Interpreted as a rank by default, as a score with `BYSCORE`, or lexicographically with `BYLEX`. |
+| `<stop>` | Yes | No | Upper bound. Interpreted as a rank by default, as a score with `BYSCORE`, or lexicographically with `BYLEX`. |
+| `(BYSCORE \| BYLEX)` | No | No | Choose one form: `BYSCORE`; `BYLEX`. |
+| `REV` | No | No | Reverse the result order. |
+| `LIMIT <offset> <count>` | No | No | Skip `<offset>` matches and return at most `<count>`; a `<count>` of `-1` returns all remaining. |
+| `WITHSCORES` | No | No | Include sorted-set scores. |
+
+## Important points
+
+- Pair-based results may be flattened into one alternating array in RESP2 while RESP3 preserves nested pairs or a map.
+- RESP2 represents floating-point reply values as bulk strings; RESP3 may use native double replies. Client libraries commonly decode either form to a language number.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of members, or flat member/score array with `WITHSCORES` |
+| RESP3 | Array of members, or array of member/score pairs with `WITHSCORES` |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.zadd("key",
+    { score: 1, member: "m1" },
+    { score: 2, member: "m2" },
+)
+const res = await redis.zrange("key", 1, 3)
+console.log(res) // ["m2"]
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.zrange("my-key", 0, -1)
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.zrange("my-key", "0", "-1");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.zRange("my-key", 0, -1);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.zrange("my-key", 0, -1)
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ZRange(context.Background(), "my-key", 0, -1).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.zrange("my-key", 0, -1);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.zrange("my-key", 0, -1)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/sorted-set/zrangebylex.mdx b/redis/commands/sorted-set/zrangebylex.mdx
new file mode 100644
index 000000000..aaf53d08d
--- /dev/null
+++ b/redis/commands/sorted-set/zrangebylex.mdx
@@ -0,0 +1,163 @@
+---
+title: "ZRANGEBYLEX"
+description: "Get members by lex range."
+---
+
+Use `ZRANGEBYLEX` to get members by lex range.
+
+## Syntax
+
+```redis
+ZRANGEBYLEX <key> <min> <max> [LIMIT <offset> <count>]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<min>` | Yes | No | Lexicographic minimum: `-`, `+`, `[member` (inclusive), or `(member` (exclusive). |
+| `<max>` | Yes | No | Lexicographic maximum: `-`, `+`, `[member` (inclusive), or `(member` (exclusive). |
+| `LIMIT <offset> <count>` | No | No | Skip `<offset>` matches and return at most `<count>`; a `<count>` of `-1` returns all remaining. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of bulk-string members |
+| RESP3 | Array of bulk-string members |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.zrangebylex("my-key", "-", "+")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.zrangebylex("my-key", "-", "+");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.zRangeByLex("my-key", "-", "+");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.zrangebylex("my-key", "-", "+")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ZRangeByLex(context.Background(), "my-key", &redis.ZRangeBy{Min: "-", Max: "+"}).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.zrangeByLex("my-key", "-", "+");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.zrangebylex("my-key", "-", "+")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/sorted-set/zrangebyscore.mdx b/redis/commands/sorted-set/zrangebyscore.mdx
new file mode 100644
index 000000000..866dc88da
--- /dev/null
+++ b/redis/commands/sorted-set/zrangebyscore.mdx
@@ -0,0 +1,168 @@
+---
+title: "ZRANGEBYSCORE"
+description: "Get members by score range."
+---
+
+Use `ZRANGEBYSCORE` to get members by score range.
+
+## Syntax
+
+```redis
+ZRANGEBYSCORE <key> <min> <max> [WITHSCORES] [LIMIT <offset> <count>]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<min>` | Yes | No | Minimum score: a number, `-inf`, or `(score` for an exclusive bound. |
+| `<max>` | Yes | No | Maximum score: a number, `+inf`, or `(score` for an exclusive bound. |
+| `WITHSCORES` | No | No | Include sorted-set scores. |
+| `LIMIT <offset> <count>` | No | No | Skip `<offset>` matches and return at most `<count>`; a `<count>` of `-1` returns all remaining. |
+
+## Important points
+
+- RESP2 represents floating-point reply values as bulk strings; RESP3 may use native double replies. Client libraries commonly decode either form to a language number.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of members, or flat member/score array with `WITHSCORES` |
+| RESP3 | Array of members, or array of member/score pairs with `WITHSCORES` |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.zrangebyscore("my-key", "1.5", "1.5")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.zrangebyscore("my-key", "1.5", "1.5");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.zRangeByScore("my-key", 1.5, 1.5);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.zrangebyscore("my-key", "1.5", "1.5")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ZRangeByScore(context.Background(), "my-key", &redis.ZRangeBy{Min: "1.5", Max: "1.5"}).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.zrangeByScore("my-key", 1.5, 1.5);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.zrangebyscore("my-key", 1.5, 1.5)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/sorted-set/zrangestore.mdx b/redis/commands/sorted-set/zrangestore.mdx
new file mode 100644
index 000000000..d765ff21c
--- /dev/null
+++ b/redis/commands/sorted-set/zrangestore.mdx
@@ -0,0 +1,169 @@
+---
+title: "ZRANGESTORE"
+description: "Store range result."
+---
+
+Use `ZRANGESTORE` to store range result.
+
+## Syntax
+
+```redis
+ZRANGESTORE <dst> <src> <min> <max> [BYSCORE | BYLEX] [REV] [LIMIT <offset> <count>]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<dst>` | Yes | No | Redis key used as dst. |
+| `<src>` | Yes | No | Redis key used as src. |
+| `<min>` | Yes | No | Lower bound. Interpreted as a rank by default, as a score with `BYSCORE`, or lexicographically with `BYLEX`. |
+| `<max>` | Yes | No | Upper bound. Interpreted as a rank by default, as a score with `BYSCORE`, or lexicographically with `BYLEX`. |
+| `(BYSCORE \| BYLEX)` | No | No | Choose one form: `BYSCORE`; `BYLEX`. |
+| `REV` | No | No | Reverse the result order. |
+| `LIMIT <offset> <count>` | No | No | Skip `<offset>` matches and return at most `<count>`; a `<count>` of `-1` returns all remaining. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.zrangestore("destination-key", "source-key", "-inf", "+inf", sortby="BYSCORE")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.zrangestore("my-key", "my-key", "-inf", "+inf");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.zRangeStore("my-key", "my-key", "-inf", "+inf");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.zrangestore("destination-key", "source-key", "-inf", "+inf", byscore=True)
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ZRangeStore(context.Background(), "destination-key", redis.ZRangeArgs{Key: "source-key", Start: "-inf", Stop: "+inf", ByScore: true}).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.zrangestore("destination-key", "source-key", redis.clients.jedis.params.ZRangeParams.zrangeByScoreParams(Double.NEGATIVE_INFINITY, Double.POSITIVE_INFINITY));
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("ZRANGESTORE");
+    command.arg("my-key");
+    command.arg("my-key");
+    command.arg("-inf");
+    command.arg("+inf");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/sorted-set/zrank.mdx b/redis/commands/sorted-set/zrank.mdx
new file mode 100644
index 000000000..85ebb0092
--- /dev/null
+++ b/redis/commands/sorted-set/zrank.mdx
@@ -0,0 +1,170 @@
+---
+title: "ZRANK"
+description: "Get member's rank."
+---
+
+Use `ZRANK` to get member's rank.
+
+## Syntax
+
+```redis
+ZRANK <key> <member> [WITHSCORE]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<member>` | Yes | No | Member name. |
+| `WITHSCORE` | No | No | Also return the member's score alongside its rank. |
+
+## Important points
+
+- RESP2 represents floating-point reply values as bulk strings; RESP3 may use native double replies. Client libraries commonly decode either form to a language number.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Null bulk string or null array, Integer, or two-element rank/score array |
+| RESP3 | Null, Integer, or two-element rank/score array |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const rank = await redis.zrank("key", "member");
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.zrank("my-key", "member")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.zrank("my-key", "member");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.zRank("my-key", "member");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.zrank("my-key", "member")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ZRank(context.Background(), "my-key", "member").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.zrank("my-key", "member");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.zrank("my-key", "member")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/sorted-set/zrem.mdx b/redis/commands/sorted-set/zrem.mdx
new file mode 100644
index 000000000..902c0cc24
--- /dev/null
+++ b/redis/commands/sorted-set/zrem.mdx
@@ -0,0 +1,165 @@
+---
+title: "ZREM"
+description: "Remove members."
+---
+
+Use `ZREM` to remove members.
+
+## Syntax
+
+```redis
+ZREM <key> <member> [<member> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<member>` | Yes | Yes | Member name. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.zrem("key", "member");
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.zrem("my-key", "member")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.zrem("my-key", "member");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.zRem("my-key", "member");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.zrem("my-key", "member")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ZRem(context.Background(), "my-key", "member").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.zrem("my-key", "member");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.zrem("my-key", "member")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/sorted-set/zremrangebylex.mdx b/redis/commands/sorted-set/zremrangebylex.mdx
new file mode 100644
index 000000000..c3eb1433e
--- /dev/null
+++ b/redis/commands/sorted-set/zremrangebylex.mdx
@@ -0,0 +1,166 @@
+---
+title: "ZREMRANGEBYLEX"
+description: "Remove members by lex range."
+---
+
+Use `ZREMRANGEBYLEX` to remove members by lex range.
+
+## Syntax
+
+```redis
+ZREMRANGEBYLEX <key> <min> <max>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<min>` | Yes | No | Lexicographic minimum: `-`, `+`, `[member` (inclusive), or `(member` (exclusive). |
+| `<max>` | Yes | No | Lexicographic maximum: `-`, `+`, `[member` (inclusive), or `(member` (exclusive). |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.zremrangebylex("key", "alpha", "omega")
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.zremrangebylex("my-key", "-", "+")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.zremrangebylex("my-key", "-", "+");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.zRemRangeByLex("my-key", "-", "+");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.zremrangebylex("my-key", "-", "+")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ZRemRangeByLex(context.Background(), "my-key", "-", "+").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.zremrangeByLex("my-key", "-", "+");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.zrembylex("my-key", "-", "+")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/sorted-set/zremrangebyrank.mdx b/redis/commands/sorted-set/zremrangebyrank.mdx
new file mode 100644
index 000000000..cb9dd110b
--- /dev/null
+++ b/redis/commands/sorted-set/zremrangebyrank.mdx
@@ -0,0 +1,166 @@
+---
+title: "ZREMRANGEBYRANK"
+description: "Remove members by rank range."
+---
+
+Use `ZREMRANGEBYRANK` to remove members by rank range.
+
+## Syntax
+
+```redis
+ZREMRANGEBYRANK <key> <start> <stop>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<start>` | Yes | No | Start index; negative values count from the end. |
+| `<stop>` | Yes | No | Stop index, inclusive; negative values count from the end. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.zremrangebyrank("key", 4, 20)
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.zremrangebyrank("my-key", 0, 0)
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.zremrangebyrank("my-key", "0", "0");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.zRemRangeByRank("my-key", 0, 0);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.zremrangebyrank("my-key", 0, 0)
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ZRemRangeByRank(context.Background(), "my-key", 0, 0).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.zremrangeByRank("my-key", 0, 0);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.zremrangebyrank("my-key", 0, 0)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/sorted-set/zremrangebyscore.mdx b/redis/commands/sorted-set/zremrangebyscore.mdx
new file mode 100644
index 000000000..ccf5ba923
--- /dev/null
+++ b/redis/commands/sorted-set/zremrangebyscore.mdx
@@ -0,0 +1,166 @@
+---
+title: "ZREMRANGEBYSCORE"
+description: "Remove members by score range."
+---
+
+Use `ZREMRANGEBYSCORE` to remove members by score range.
+
+## Syntax
+
+```redis
+ZREMRANGEBYSCORE <key> <min> <max>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<min>` | Yes | No | Minimum score: a number, `-inf`, or `(score` for an exclusive bound. |
+| `<max>` | Yes | No | Maximum score: a number, `+inf`, or `(score` for an exclusive bound. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.zremrangebyscore("key", 2, 5)
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.zremrangebyscore("my-key", 1.5, 1.5)
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.zremrangebyscore("my-key", "1.5", "1.5");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.zRemRangeByScore("my-key", 1.5, 1.5);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.zremrangebyscore("my-key", 1.5, 1.5)
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ZRemRangeByScore(context.Background(), "my-key", "1.5", "1.5").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.zremrangeByScore("my-key", 1.5, 1.5);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.zrembyscore("my-key", 1.5, 1.5)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/sorted-set/zrevrange.mdx b/redis/commands/sorted-set/zrevrange.mdx
new file mode 100644
index 000000000..737ce1736
--- /dev/null
+++ b/redis/commands/sorted-set/zrevrange.mdx
@@ -0,0 +1,167 @@
+---
+title: "ZREVRANGE"
+description: "Get members in reverse order."
+---
+
+Use `ZREVRANGE` to get members in reverse order.
+
+## Syntax
+
+```redis
+ZREVRANGE <key> <start> <stop> [WITHSCORES]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<start>` | Yes | No | Start index; negative values count from the end. |
+| `<stop>` | Yes | No | Stop index, inclusive; negative values count from the end. |
+| `WITHSCORES` | No | No | Include sorted-set scores. |
+
+## Important points
+
+- RESP2 represents floating-point reply values as bulk strings; RESP3 may use native double replies. Client libraries commonly decode either form to a language number.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of members, or flat member/score array with `WITHSCORES` |
+| RESP3 | Array of members, or array of member/score pairs with `WITHSCORES` |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.zrevrange("my-key", 0, 0)
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.zrevrange("my-key", "0", "0");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.zRange("my-key", 0, 0, { REV: true });
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.zrevrange("my-key", 0, 0)
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ZRevRange(context.Background(), "my-key", 0, -1).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.zrevrange("my-key", 0, -1);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.zrevrange("my-key", 0, -1)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/sorted-set/zrevrangebylex.mdx b/redis/commands/sorted-set/zrevrangebylex.mdx
new file mode 100644
index 000000000..09e8edf38
--- /dev/null
+++ b/redis/commands/sorted-set/zrevrangebylex.mdx
@@ -0,0 +1,163 @@
+---
+title: "ZREVRANGEBYLEX"
+description: "List members in a lexicographic range, in reverse order."
+---
+
+Use `ZREVRANGEBYLEX` to list the members in a lexicographic range, in reverse order.
+
+## Syntax
+
+```redis
+ZREVRANGEBYLEX <key> <max> <min> [LIMIT <offset> <count>]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<max>` | Yes | No | Lexicographic maximum: `-`, `+`, `[member` (inclusive), or `(member` (exclusive). |
+| `<min>` | Yes | No | Lexicographic minimum: `-`, `+`, `[member` (inclusive), or `(member` (exclusive). |
+| `LIMIT <offset> <count>` | No | No | Skip `<offset>` matches and return at most `<count>`; a `<count>` of `-1` returns all remaining. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of bulk-string members |
+| RESP3 | Array of bulk-string members |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.zrevrangebylex("my-key", "+", "-")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.zrevrangebylex("my-key", "+", "-");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.zRange("my-key", "+", "-", { BY: "LEX", REV: true });
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.zrevrangebylex("my-key", "+", "-")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ZRevRangeByLex(context.Background(), "my-key", &redis.ZRangeBy{Min: "-", Max: "+"}).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.zrevrangeByLex("my-key", "+", "-");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.zrevrangebylex("my-key", "+", "-")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/sorted-set/zrevrangebyscore.mdx b/redis/commands/sorted-set/zrevrangebyscore.mdx
new file mode 100644
index 000000000..feebc90c2
--- /dev/null
+++ b/redis/commands/sorted-set/zrevrangebyscore.mdx
@@ -0,0 +1,168 @@
+---
+title: "ZREVRANGEBYSCORE"
+description: "List members in a score range, highest score first."
+---
+
+Use `ZREVRANGEBYSCORE` to list the members in a score range, ordered from the highest score down.
+
+## Syntax
+
+```redis
+ZREVRANGEBYSCORE <key> <max> <min> [WITHSCORES] [LIMIT <offset> <count>]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<max>` | Yes | No | Maximum score: a number, `+inf`, or `(score` for an exclusive bound. |
+| `<min>` | Yes | No | Minimum score: a number, `-inf`, or `(score` for an exclusive bound. |
+| `WITHSCORES` | No | No | Include sorted-set scores. |
+| `LIMIT <offset> <count>` | No | No | Skip `<offset>` matches and return at most `<count>`; a `<count>` of `-1` returns all remaining. |
+
+## Important points
+
+- RESP2 represents floating-point reply values as bulk strings; RESP3 may use native double replies. Client libraries commonly decode either form to a language number.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of members, or flat member/score array with `WITHSCORES` |
+| RESP3 | Array of members, or array of member/score pairs with `WITHSCORES` |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.zrevrangebyscore("my-key", "1.5", "1.5")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.zrevrangebyscore("my-key", "1.5", "1.5");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.zRange("my-key", 1.5, 1.5, { BY: "SCORE", REV: true });
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.zrevrangebyscore("my-key", "1.5", "1.5")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ZRevRangeByScore(context.Background(), "my-key", &redis.ZRangeBy{Min: "1.5", Max: "1.5"}).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.zrevrangeByScore("my-key", 1.5, 1.5);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.zrevrangebyscore("my-key", 1.5, 1.5)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/sorted-set/zrevrank.mdx b/redis/commands/sorted-set/zrevrank.mdx
new file mode 100644
index 000000000..e4d6e089b
--- /dev/null
+++ b/redis/commands/sorted-set/zrevrank.mdx
@@ -0,0 +1,170 @@
+---
+title: "ZREVRANK"
+description: "Get member's reverse rank."
+---
+
+Use `ZREVRANK` to get member's reverse rank.
+
+## Syntax
+
+```redis
+ZREVRANK <key> <member> [WITHSCORE]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<member>` | Yes | No | Member name. |
+| `WITHSCORE` | No | No | Also return the member's score alongside its rank. |
+
+## Important points
+
+- RESP2 represents floating-point reply values as bulk strings; RESP3 may use native double replies. Client libraries commonly decode either form to a language number.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Null bulk string or null array, Integer, or two-element rank/score array |
+| RESP3 | Null, Integer, or two-element rank/score array |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const rank = await redis.zrevrank("key", "member");
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.zrevrank("my-key", "member")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.zrevrank("my-key", "member");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.zRevRank("my-key", "member");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.zrevrank("my-key", "member")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ZRevRank(context.Background(), "my-key", "member").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.zrevrank("my-key", "member");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.zrevrank("my-key", "member")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/sorted-set/zscan.mdx b/redis/commands/sorted-set/zscan.mdx
new file mode 100644
index 000000000..d10ff7557
--- /dev/null
+++ b/redis/commands/sorted-set/zscan.mdx
@@ -0,0 +1,183 @@
+---
+title: "ZSCAN"
+description: "Incrementally iterate sorted set."
+---
+
+Use `ZSCAN` to incrementally iterate sorted set.
+
+## Syntax
+
+```redis
+ZSCAN <key> <cursor> [MATCH <pattern>] [COUNT <count>]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<cursor>` | Yes | No | Cursor returned by the previous call; start at `0`. |
+| `MATCH <pattern>` | No | No | Return only elements matching this glob-style pattern. |
+| `COUNT <count>` | No | No | Hint for how much work each iteration should do. |
+
+## Important points
+
+- This operation can inspect a large part of the database. Prefer cursor-based scans where possible and avoid unbounded use on hot paths.
+- The cursor is opaque. Start with `0` and continue until the server returns cursor `0`; a single iteration may return no elements.
+- RESP2 represents floating-point reply values as bulk strings; RESP3 may use native double replies. Client libraries commonly decode either form to a language number.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Two-element array: cursor and flat member/score array |
+| RESP3 | Two-element array: cursor and flat member/score array |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.zadd("key",
+    { score: 1, member: "a" },
+    { score: 2, member: "ab" },
+    { score: 3, member: "b" },
+    { score: 4, member: "c" },
+    { score: 5, member: "d" },
+)
+const [newCursor, members] = await redis.zscan("key", 0, { match: "a*"});
+console.log(newCursor); // likely `0` since this is a very small set
+console.log(members); // ["a", "ab"]
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.zscan("my-key", 0)
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.zscan("my-key", "0");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.zScan("my-key", "0");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.zscan("my-key", 0)
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, _, err := client.ZScan(context.Background(), "my-key", 0, "*", 0).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.zscan("my-key", "0");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("ZSCAN");
+    command.arg("my-key");
+    command.arg("0");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/sorted-set/zscore.mdx b/redis/commands/sorted-set/zscore.mdx
new file mode 100644
index 000000000..20cf2af29
--- /dev/null
+++ b/redis/commands/sorted-set/zscore.mdx
@@ -0,0 +1,177 @@
+---
+title: "ZSCORE"
+description: "Get member's score."
+---
+
+Use `ZSCORE` to get member's score.
+
+## Syntax
+
+```redis
+ZSCORE <key> <member>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<member>` | Yes | No | Member name. |
+
+## Important points
+
+- RESP2 represents floating-point reply values as bulk strings; RESP3 may use native double replies. Client libraries commonly decode either form to a language number.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Bulk string containing a number or Null bulk string or null array |
+| RESP3 | Double or Null |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.zadd("key",
+    { score: 1, member: "m1" },
+    { score: 2, member: "m2" },
+    { score: 3, member: "m3" },
+    { score: 4, member: "m4" },
+)
+
+const score = await redis.zscore("key", "m2")
+console.log(score) // 2
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.zscore("my-key", "member")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.zscore("my-key", "member");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.zScore("my-key", "member");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.zscore("my-key", "member")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ZScore(context.Background(), "my-key", "member").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.zscore("my-key", "member");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.zscore("my-key", "member")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/sorted-set/zunion.mdx b/redis/commands/sorted-set/zunion.mdx
new file mode 100644
index 000000000..a9133d2fb
--- /dev/null
+++ b/redis/commands/sorted-set/zunion.mdx
@@ -0,0 +1,174 @@
+---
+title: "ZUNION"
+description: "Get sorted set union."
+---
+
+Use `ZUNION` to get sorted set union.
+
+## Syntax
+
+```redis
+ZUNION <numkeys> <key> [<key> ...] [WEIGHTS <weight> [<weight> ...]] [AGGREGATE SUM | MIN | MAX] [WITHSCORES]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<numkeys>` | Yes | No | Number of key arguments that follow. |
+| `<key>` | Yes | Yes | Redis key targeted by the command. |
+| `WEIGHTS <weight>` | No | Yes | Multiplier applied to each input key's scores, in the order the keys were given. |
+| `(AGGREGATE SUM \| MIN \| MAX)` | No | No | Under `AGGREGATE`, choose one form: `SUM`; `MIN`; `MAX`. |
+| `WITHSCORES` | No | No | Include sorted-set scores. |
+
+## Important points
+
+- `numkeys` must equal the number of key arguments that immediately follow it.
+- RESP2 represents floating-point reply values as bulk strings; RESP3 may use native double replies. Client libraries commonly decode either form to a language number.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of members, or flat member/score array with `WITHSCORES` |
+| RESP3 | Array of members, or array of member/score pairs with `WITHSCORES` |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+const result = await redis.zunion(1, "my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.zunion(["my-key"])
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.zunion("1", "my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.zUnion("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.zunion(["my-key"])
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ZUnion(context.Background(), redis.ZStore{Keys: []string{"my-key"}}).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.zunion(new redis.clients.jedis.params.ZParams(), "my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("ZUNION");
+    command.arg("1");
+    command.arg("my-key");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/sorted-set/zunionstore.mdx b/redis/commands/sorted-set/zunionstore.mdx
new file mode 100644
index 000000000..e14aa254d
--- /dev/null
+++ b/redis/commands/sorted-set/zunionstore.mdx
@@ -0,0 +1,183 @@
+---
+title: "ZUNIONSTORE"
+description: "Store sorted set union."
+---
+
+Use `ZUNIONSTORE` to store sorted set union.
+
+## Syntax
+
+```redis
+ZUNIONSTORE <destination> <numkeys> <key> [<key> ...] [WEIGHTS <weight> [<weight> ...]] [AGGREGATE SUM | MIN | MAX]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<destination>` | Yes | No | Redis key used as destination. |
+| `<numkeys>` | Yes | No | Number of key arguments that follow. |
+| `<key>` | Yes | Yes | Redis key targeted by the command. |
+| `WEIGHTS <weight>` | No | Yes | Multiplier applied to each input key's scores, in the order the keys were given. |
+| `(AGGREGATE SUM \| MIN \| MAX)` | No | No | Under `AGGREGATE`, choose one form: `SUM`; `MIN`; `MAX`. |
+
+## Important points
+
+- `numkeys` must equal the number of key arguments that immediately follow it.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.zadd(
+    "key1",
+    { score: 1, member: "member1" },
+)
+await redis.zadd(
+    "key2",
+    { score: 1, member: "member1" },
+    { score: 2, member: "member2" },
+)
+
+const res = await redis.zunionstore("destination", 2, ["key1", "key2"]);
+console.log(res) // 2
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.zunionstore("destination-key", ["my-key"])
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.zunionstore("destination-key", "1", "my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.zUnionStore("destination-key", "my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.zunionstore("destination-key", ["my-key"])
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.ZUnionStore(context.Background(), "destination-key", &redis.ZStore{Keys: []string{"my-key"}}).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.zunionstore("destination-key", "my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.zunionstore("destination-key", &["my-key"])?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/streams/overview.mdx b/redis/commands/streams/overview.mdx
new file mode 100644
index 000000000..9d5f9bca7
--- /dev/null
+++ b/redis/commands/streams/overview.mdx
@@ -0,0 +1,27 @@
+---
+title: "Streams commands"
+sidebarTitle: "Overview"
+description: "Commands for append-only logs, consumer groups, and message processing."
+---
+
+<CardGroup cols={2}>
+<Card title="XACK" href="/redis/commands/streams/xack">Acknowledge stream messages</Card>
+<Card title="XACKDEL" href="/redis/commands/streams/xackdel">Acknowledge and delete messages</Card>
+<Card title="XADD" href="/redis/commands/streams/xadd">Add entry to stream</Card>
+<Card title="XAUTOCLAIM" href="/redis/commands/streams/xautoclaim">Auto-claim idle messages</Card>
+<Card title="XCLAIM" href="/redis/commands/streams/xclaim">Claim pending messages</Card>
+<Card title="XDEL" href="/redis/commands/streams/xdel">Delete stream entries</Card>
+<Card title="XDELEX" href="/redis/commands/streams/xdelex">Delete entries with expiration</Card>
+<Card title="XGROUP" href="/redis/commands/streams/xgroup">Manage consumer groups</Card>
+<Card title="XINFO CONSUMERS" href="/redis/commands/streams/xinfo-consumers">List group consumers</Card>
+<Card title="XINFO GROUPS" href="/redis/commands/streams/xinfo-groups">List stream groups</Card>
+<Card title="XINFO STREAM" href="/redis/commands/streams/xinfo-stream">Get stream info</Card>
+<Card title="XLEN" href="/redis/commands/streams/xlen">Get stream length</Card>
+<Card title="XPENDING" href="/redis/commands/streams/xpending">Get pending messages info</Card>
+<Card title="XRANGE" href="/redis/commands/streams/xrange">Get range of stream entries</Card>
+<Card title="XREAD" href="/redis/commands/streams/xread">Read stream entries</Card>
+<Card title="XREADGROUP" href="/redis/commands/streams/xreadgroup">Read as consumer group</Card>
+<Card title="XREVRANGE" href="/redis/commands/streams/xrevrange">Get range in reverse order</Card>
+<Card title="XTRIM" href="/redis/commands/streams/xtrim">Trim stream to max length</Card>
+</CardGroup>
+
diff --git a/redis/commands/streams/xack.mdx b/redis/commands/streams/xack.mdx
new file mode 100644
index 000000000..1f07233b0
--- /dev/null
+++ b/redis/commands/streams/xack.mdx
@@ -0,0 +1,166 @@
+---
+title: "XACK"
+description: "Acknowledge stream messages."
+---
+
+Use `XACK` to acknowledge stream messages.
+
+## Syntax
+
+```redis
+XACK <key> <group> <ID> [<ID> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<group>` | Yes | No | Consumer group name. |
+| `<ID>` | Yes | Yes | Stream entry ID. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const result = await redis.xack("mystream", "mygroup", "1638360173533-0");
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.xack("my-key", "workers", "0-0")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.xack("my-key", "workers", "0-0");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.xAck("my-key", "workers", "0-0");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.xack("my-key", "workers", "0-0")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.XAck(context.Background(), "my-key", "workers", "0-0").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.xack("my-key", "workers", new redis.clients.jedis.StreamEntryID("0-0"));
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.xack("my-key", "workers", &["0-0"])?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/streams/xackdel.mdx b/redis/commands/streams/xackdel.mdx
new file mode 100644
index 000000000..677fe5c4a
--- /dev/null
+++ b/redis/commands/streams/xackdel.mdx
@@ -0,0 +1,169 @@
+---
+title: "XACKDEL"
+description: "Acknowledge and delete messages."
+---
+
+Use `XACKDEL` to acknowledge and delete messages.
+
+## Syntax
+
+```redis
+XACKDEL <key> <group> [KEEPREF | DELREF | ACKED] IDS <numids> <id> [<id> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<group>` | Yes | No | Consumer group name. |
+| `(KEEPREF \| DELREF \| ACKED)` | No | No | Choose one form: `KEEPREF`; `DELREF`; `ACKED`. |
+| `IDS <numids> <id> [<id> ...]` | Yes | No | Entry IDs to target. Give the ID count first, then that many IDs. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of integer status codes, one per ID |
+| RESP3 | Array of integer status codes, one per ID |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+// Acknowledge and delete a single entry
+const result = await redis.xackdel("mystream", "mygroup", "1638360173533-0");
+console.log(result); // Array of results for each ID
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.xackdel("my-key", "workers", "0-0")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.call("XACKDEL", "my-key", "workers", "IDS", "1", "0-0");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.xAckDel("my-key", "workers", "0-0");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.xackdel("my-key", "workers", "0-0")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.XAckDel(context.Background(), "my-key", "workers", "KEEPREF", "0-0").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.xackdel("my-key", "workers", new redis.clients.jedis.StreamEntryID("0-0"));
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.xack_del("my-key", "workers", &["0-0"], redis::streams::StreamDeletionPolicy::KeepRef)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/streams/xadd.mdx b/redis/commands/streams/xadd.mdx
new file mode 100644
index 000000000..2b19b7847
--- /dev/null
+++ b/redis/commands/streams/xadd.mdx
@@ -0,0 +1,169 @@
+---
+title: "XADD"
+description: "Add entry to stream."
+---
+
+Use `XADD` to add entry to stream.
+
+## Syntax
+
+```redis
+XADD <key> [NOMKSTREAM] [KEEPREF | DELREF | ACKED] [(MAXLEN | MINID) [= | ~] <threshold> [LIMIT <count>]] (* | <id>) <field> <value> [<field> <value> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `NOMKSTREAM` | No | No | Do not create a missing stream. |
+| `(KEEPREF \| DELREF \| ACKED)` | No | No | Choose one form: `KEEPREF`; `DELREF`; `ACKED`. |
+| `(MAXLEN \| MINID) [= \| ~] <threshold> [LIMIT <count>]` | No | No | Trim the stream after the entry is added. `MAXLEN` caps the number of entries; `MINID` drops entries with a lower ID. `=` trims exactly and is the default; `~` trims approximately and is required before `LIMIT`, which caps how many entries a single call evicts. |
+| `(* \| <id>)` | Yes | No | Choose one form: `*`. |
+| `<field> <value>` | Yes | Yes | Field and the value to store in it. Repeat to set several fields in one call. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Bulk string or Null bulk string or null array |
+| RESP3 | Bulk string or Null |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const result = await redis.xadd("mystream", "*", { name: "John Doe", age: 30 });
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.xadd("my-key", "*", {"field": "value"})
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.xadd("my-key", "*", "field", "value");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.xAdd("my-key", "*", { field: "value" });
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.xadd("my-key", {"field": "value"})
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.XAdd(context.Background(), &redis.XAddArgs{Stream: "my-key", Values: map[string]interface{}{"field": "value"}}).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.xadd("my-key", redis.clients.jedis.StreamEntryID.NEW_ENTRY, java.util.Map.of("field", "value"));
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.xadd("my-key", "*", &[("field", "value")])?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/streams/xautoclaim.mdx b/redis/commands/streams/xautoclaim.mdx
new file mode 100644
index 000000000..3cc2abf82
--- /dev/null
+++ b/redis/commands/streams/xautoclaim.mdx
@@ -0,0 +1,181 @@
+---
+title: "XAUTOCLAIM"
+description: "Auto-claim idle messages."
+---
+
+Use `XAUTOCLAIM` to auto-claim idle messages.
+
+## Syntax
+
+```redis
+XAUTOCLAIM <key> <group> <consumer> <min-idle-time> <start> [COUNT <count>] [JUSTID]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<group>` | Yes | No | Consumer group name. |
+| `<consumer>` | Yes | No | Consumer name within the group. |
+| `<min-idle-time>` | Yes | No | Only claim entries that have been idle at least this many milliseconds. |
+| `<start>` | Yes | No | ID to start scanning the pending list from; `0-0` starts at the beginning. |
+| `COUNT <count>` | No | No | Maximum number of entries to claim. |
+| `JUSTID` | No | No | Return only entry IDs, without their fields and values. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Three-element array: next ID, claimed entries or IDs, and deleted IDs |
+| RESP3 | Three-element array: next ID, claimed entries or IDs, and deleted IDs |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const result = await redis.xautoclaim(
+  "mystream",
+  "mygroup",
+  "consumer1",
+  60000,
+  "0-0"
+);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.xautoclaim("my-key", "workers", "worker-1", 60000, "0-0")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.xautoclaim("my-key", "workers", "worker-1", "60000", "0-0");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.xAutoClaim("my-key", "workers", "worker-1", 60000, "0-0");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.xautoclaim("my-key", "workers", "worker-1", 60000, "0-0")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+    "time"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, _, err := client.XAutoClaim(context.Background(), &redis.XAutoClaimArgs{Stream: "my-key", Group: "workers", Consumer: "worker-1", MinIdle: time.Minute, Start: "0-0"}).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.xautoclaim("my-key", "workers", "worker-1", 60000, new redis.clients.jedis.StreamEntryID("0-0"), redis.clients.jedis.params.XAutoClaimParams.xAutoClaimParams());
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("XAUTOCLAIM");
+    command.arg("my-key");
+    command.arg("workers");
+    command.arg("worker-1");
+    command.arg("min-idle-time");
+    command.arg("start");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/streams/xclaim.mdx b/redis/commands/streams/xclaim.mdx
new file mode 100644
index 000000000..95d389a29
--- /dev/null
+++ b/redis/commands/streams/xclaim.mdx
@@ -0,0 +1,181 @@
+---
+title: "XCLAIM"
+description: "Claim pending messages."
+---
+
+Use `XCLAIM` to claim pending messages.
+
+## Syntax
+
+```redis
+XCLAIM <key> <group> <consumer> <min-idle-time> <ID> [<ID> ...] [IDLE <ms>] [TIME <unix-time-milliseconds>] [RETRYCOUNT <count>] [FORCE] [JUSTID] [LASTID <lastid>]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<group>` | Yes | No | Consumer group name. |
+| `<consumer>` | Yes | No | Consumer name within the group. |
+| `<min-idle-time>` | Yes | No | Only claim entries that have been idle at least this many milliseconds. |
+| `<ID>` | Yes | Yes | Stream entry ID. |
+| `IDLE <ms>` | No | No | Set the entry's idle time to this many milliseconds. |
+| `TIME <unix-time-milliseconds>` | No | No | Set the entry's last-delivery time to this Unix timestamp in milliseconds. |
+| `RETRYCOUNT <count>` | No | No | Set the entry's delivery counter to this value. |
+| `FORCE` | No | No | Create the pending entry even when the ID is not in the group's pending list. |
+| `JUSTID` | No | No | Return only entry IDs, without their fields and values. |
+| `LASTID <lastid>` | No | No | New last-delivered ID for the group. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of entry arrays, or array of IDs with `JUSTID` |
+| RESP3 | Array of entry arrays, or array of IDs with `JUSTID` |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const result = await redis.xclaim(
+  "mystream",
+  "mygroup",
+  "consumer1",
+  60000,
+  ["1638360173533-0", "1638360173533-1"]
+);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.xclaim("my-key", "workers", "worker-1", 60000, "0-0")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.xclaim("my-key", "workers", "worker-1", "60000", "0-0");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.xClaim("my-key", "workers", "worker-1", 60000, "0-0");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.xclaim("my-key", "workers", "worker-1", 60000, ["0-0"])
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+    "time"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.XClaim(context.Background(), &redis.XClaimArgs{Stream: "my-key", Group: "workers", Consumer: "worker-1", MinIdle: time.Minute, Messages: []string{"0-0"}}).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.xclaim("my-key", "workers", "worker-1", 60000, redis.clients.jedis.params.XClaimParams.xClaimParams(), new redis.clients.jedis.StreamEntryID("0-0"));
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.xclaim("my-key", "workers", "worker-1", 60000, &["0-0"])?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/streams/xdel.mdx b/redis/commands/streams/xdel.mdx
new file mode 100644
index 000000000..cab4afb6b
--- /dev/null
+++ b/redis/commands/streams/xdel.mdx
@@ -0,0 +1,165 @@
+---
+title: "XDEL"
+description: "Delete stream entries."
+---
+
+Use `XDEL` to delete stream entries.
+
+## Syntax
+
+```redis
+XDEL <key> <ID> [<ID> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<ID>` | Yes | Yes | Stream entry ID. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const result = await redis.xdel("mystream", "1638360173533-0");
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.xdel("my-key", "0-0")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.xdel("my-key", "0-0");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.xDel("my-key", "0-0");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.xdel("my-key", "0-0")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.XDel(context.Background(), "my-key", "0-0").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.xdel("my-key", new redis.clients.jedis.StreamEntryID("0-0"));
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.xdel("my-key", &["0-0"])?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/streams/xdelex.mdx b/redis/commands/streams/xdelex.mdx
new file mode 100644
index 000000000..e4a690276
--- /dev/null
+++ b/redis/commands/streams/xdelex.mdx
@@ -0,0 +1,168 @@
+---
+title: "XDELEX"
+description: "Delete entries with expiration."
+---
+
+Use `XDELEX` to delete entries with expiration.
+
+## Syntax
+
+```redis
+XDELEX <key> [KEEPREF | DELREF | ACKED] IDS <numids> <id> [<id> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `(KEEPREF \| DELREF \| ACKED)` | No | No | Choose one form: `KEEPREF`; `DELREF`; `ACKED`. |
+| `IDS <numids> <id> [<id> ...]` | Yes | No | Entry IDs to target. Give the ID count first, then that many IDs. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of integer status codes, one per ID |
+| RESP3 | Array of integer status codes, one per ID |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+// Delete a single stream entry
+const result = await redis.xdelex("mystream", "1638360173533-0");
+console.log(result); // Array of results for each ID
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.xdelex("my-key", "0-0")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.xdelex("my-key", "IDS", "1", "0-0");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.xDelEx("my-key", "0-0");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.xdelex("my-key", "0-0")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.XDelEx(context.Background(), "my-key", "KEEPREF", "0-0").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.xdelex("my-key", new redis.clients.jedis.StreamEntryID("0-0"));
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.xdel_ex("my-key", &["0-0"], redis::streams::StreamDeletionPolicy::KeepRef)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/streams/xgroup.mdx b/redis/commands/streams/xgroup.mdx
new file mode 100644
index 000000000..c63dd66ad
--- /dev/null
+++ b/redis/commands/streams/xgroup.mdx
@@ -0,0 +1,178 @@
+---
+title: "XGROUP"
+description: "Manage consumer groups."
+---
+
+Use `XGROUP` to manage consumer groups.
+
+## Syntax
+
+```redis
+XGROUP CREATE <key> <group> <id | $> [MKSTREAM]
+XGROUP CREATECONSUMER <key> <group> <consumer>
+XGROUP DELCONSUMER <key> <group> <consumer>
+XGROUP DESTROY <key> <group>
+XGROUP SETID <key> <group> <id | $>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `subcommand` | Yes | No | Consumer-group operation shown in the syntax block. |
+| `key` | Yes | No | Stream key. |
+| `group` | Yes | No | Consumer-group name. |
+| `consumer` | Some forms | No | Consumer name for CREATECONSUMER or DELCONSUMER. |
+| `id \| $` | Some forms | No | Starting or replacement last-delivered ID; `$` means the stream's latest ID. |
+| `MKSTREAM` | No | No | Create an empty stream when CREATE targets a missing key. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Simple string `OK` for `CREATE` and `SETID`; Integer for `CREATECONSUMER`, `DELCONSUMER`, and `DESTROY` |
+| RESP3 | Simple string `OK` for `CREATE` and `SETID`; Integer for `CREATECONSUMER`, `DELCONSUMER`, and `DESTROY` |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const result = await redis.xgroup("mystream", {
+  type: "CREATE",
+  group: "mygroup",
+  id: "$",
+  options: { MKSTREAM: true }
+});
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.xgroup_create("events", "workers", "$", mkstream=True)
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.xgroup("CREATE", "events", "workers", "$", "MKSTREAM");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.xGroupCreate("events", "workers", "$", { MKSTREAM: true });
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.xgroup_create("events", "workers", "$", mkstream=True)
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.XGroupCreateMkStream(context.Background(), "events", "workers", "$").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.xgroupCreate("events", "workers", redis.clients.jedis.StreamEntryID.LAST_ENTRY, true);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.xgroup_create_mkstream("events", "workers", "$")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/streams/xinfo-consumers.mdx b/redis/commands/streams/xinfo-consumers.mdx
new file mode 100644
index 000000000..5b2152b0b
--- /dev/null
+++ b/redis/commands/streams/xinfo-consumers.mdx
@@ -0,0 +1,168 @@
+---
+title: "XINFO CONSUMERS"
+description: "List group consumers."
+---
+
+Use `XINFO CONSUMERS` to list group consumers.
+
+## Syntax
+
+```redis
+XINFO CONSUMERS <key> <group>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<group>` | Yes | No | Consumer group name. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of flat consumer-metadata arrays |
+| RESP3 | Array of flat consumer-metadata arrays |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+const result = await redis.xinfo("my-key", {
+  type: "CONSUMERS",
+  group: "workers",
+});
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.xinfo_consumers("my-key", "workers")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.xinfo("CONSUMERS", "my-key", "workers");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.xInfoConsumers("my-key", "workers");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.xinfo_consumers("my-key", "workers")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.XInfoConsumers(context.Background(), "my-key", "workers").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.xinfoConsumers("my-key", "workers");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.xinfo_consumers("my-key", "workers")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/streams/xinfo-groups.mdx b/redis/commands/streams/xinfo-groups.mdx
new file mode 100644
index 000000000..432563f3a
--- /dev/null
+++ b/redis/commands/streams/xinfo-groups.mdx
@@ -0,0 +1,164 @@
+---
+title: "XINFO GROUPS"
+description: "List stream groups."
+---
+
+Use `XINFO GROUPS` to list stream groups.
+
+## Syntax
+
+```redis
+XINFO GROUPS <key>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of flat group-metadata arrays |
+| RESP3 | Array of flat group-metadata arrays |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+const result = await redis.xinfo("my-key", { type: "GROUPS" });
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.xinfo_groups("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.xinfo("GROUPS", "my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.xInfoGroups("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.xinfo_groups("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.XInfoGroups(context.Background(), "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.xinfoGroups("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.xinfo_groups("my-key")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/streams/xinfo-stream.mdx b/redis/commands/streams/xinfo-stream.mdx
new file mode 100644
index 000000000..6a57c858f
--- /dev/null
+++ b/redis/commands/streams/xinfo-stream.mdx
@@ -0,0 +1,157 @@
+---
+title: "XINFO STREAM"
+description: "Get stream info."
+---
+
+Use `XINFO STREAM` to get stream info.
+
+## Syntax
+
+```redis
+XINFO STREAM <key> [FULL [COUNT <count>]]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `FULL [COUNT <count>]` | No | No | Return the full report, including entries and consumer-group state. `COUNT` caps how many entries each section lists; `0` returns all of them. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Flat array of alternating keys and values |
+| RESP3 | Map |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+<Note>
+  This command is not supported yet in `upstash_redis`.
+</Note>
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.xinfo("STREAM", "my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.xInfoStream("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.xinfo_stream("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.XInfoStream(context.Background(), "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.xinfoStream("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.xinfo_stream("my-key")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/streams/xlen.mdx b/redis/commands/streams/xlen.mdx
new file mode 100644
index 000000000..5f2cdc242
--- /dev/null
+++ b/redis/commands/streams/xlen.mdx
@@ -0,0 +1,164 @@
+---
+title: "XLEN"
+description: "Get stream length."
+---
+
+Use `XLEN` to get stream length.
+
+## Syntax
+
+```redis
+XLEN <key>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const result = await redis.xlen("mystream");
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.xlen("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.xlen("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.xLen("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.xlen("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.XLen(context.Background(), "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.xlen("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.xlen("my-key")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/streams/xpending.mdx b/redis/commands/streams/xpending.mdx
new file mode 100644
index 000000000..51385326b
--- /dev/null
+++ b/redis/commands/streams/xpending.mdx
@@ -0,0 +1,166 @@
+---
+title: "XPENDING"
+description: "Get pending messages info."
+---
+
+Use `XPENDING` to get pending messages info.
+
+## Syntax
+
+```redis
+XPENDING <key> <group> [[IDLE <min-idle-time>] <start> <end> <count> [<consumer>]]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<group>` | Yes | No | Consumer group name. |
+| `[IDLE <min-idle-time>] <start> <end> <count> [<consumer>]` | No | No | Extended form: optionally filter by idle time, then give the ID range, the maximum number of entries to return, and optionally a single consumer to report on. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Four-element summary array, or array of pending-entry detail arrays |
+| RESP3 | Four-element summary array, or array of pending-entry detail arrays |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const result = await redis.xpending("mystream", "mygroup", "-", "+", 10);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.xpending("my-key", "workers")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.xpending("my-key", "workers");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.xPending("my-key", "workers");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.xpending("my-key", "workers")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.XPending(context.Background(), "my-key", "workers").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.xpending("my-key", "workers");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.xpending("my-key", "workers")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/streams/xrange.mdx b/redis/commands/streams/xrange.mdx
new file mode 100644
index 000000000..b944a564c
--- /dev/null
+++ b/redis/commands/streams/xrange.mdx
@@ -0,0 +1,167 @@
+---
+title: "XRANGE"
+description: "Get range of stream entries."
+---
+
+Use `XRANGE` to get range of stream entries.
+
+## Syntax
+
+```redis
+XRANGE <key> <start> <end> [COUNT <count>]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<start>` | Yes | No | First ID to return; `-` means the smallest possible ID. |
+| `<end>` | Yes | No | Last ID to return; `+` means the largest possible ID. |
+| `COUNT <count>` | No | No | Maximum number of entries to return. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of two-element entry arrays: ID and flat field/value array |
+| RESP3 | Array of two-element entry arrays: ID and flat field/value array |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const result = await redis.xrange("mystream", "-", "+");
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.xrange("my-key", "-", "+")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.xrange("my-key", "-", "+");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.xRange("my-key", "-", "+");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.xrange("my-key", "-", "+")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.XRange(context.Background(), "my-key", "-", "+").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.xrange("my-key", "-", "+");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.xrange("my-key", "-", "+")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/streams/xread.mdx b/redis/commands/streams/xread.mdx
new file mode 100644
index 000000000..6c5ed1148
--- /dev/null
+++ b/redis/commands/streams/xread.mdx
@@ -0,0 +1,171 @@
+---
+title: "XREAD"
+description: "Read stream entries."
+---
+
+Use `XREAD` to read stream entries.
+
+## Syntax
+
+```redis
+XREAD [COUNT <count>] [BLOCK <milliseconds>] STREAMS <key> [<key> ...] <ID> [<ID> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `COUNT <count>` | No | No | Maximum number of entries to return per stream. |
+| `BLOCK <milliseconds>` | No | No | Milliseconds to block waiting for new entries; `0` blocks indefinitely. |
+| `STREAMS <key> [<key> ...] <ID> [<ID> ...]` | Yes | No | Streams to read. List every key first, then one ID per key in the same order. |
+
+## Important points
+
+- A blocking form holds the request until data arrives or its timeout expires. Set the client/network timeout longer than the command timeout.
+- After `STREAMS`, provide all keys first and then exactly one ID for each key, in the same order.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Flat array of alternating keys and values or Null bulk string or null array |
+| RESP3 | Map or Null |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const result = await redis.xread("mystream", "0-0");
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.xread({"my-key": "0-0"})
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.xread("STREAMS", "my-key", "0-0");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.xRead({ key: "my-key", id: "0-0" });
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.xread({"my-key": "0-0"})
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.XRead(context.Background(), &redis.XReadArgs{Streams: []string{"my-key", "0-0"}}).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.xread(redis.clients.jedis.params.XReadParams.xReadParams(), java.util.Map.of("my-key", new redis.clients.jedis.StreamEntryID("0-0")));
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.xread(&["my-key"], &["0-0"])?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/streams/xreadgroup.mdx b/redis/commands/streams/xreadgroup.mdx
new file mode 100644
index 000000000..73f3dca6e
--- /dev/null
+++ b/redis/commands/streams/xreadgroup.mdx
@@ -0,0 +1,178 @@
+---
+title: "XREADGROUP"
+description: "Read as consumer group."
+---
+
+Use `XREADGROUP` to read as consumer group.
+
+## Syntax
+
+```redis
+XREADGROUP GROUP <group> <consumer> [COUNT <count>] [BLOCK <milliseconds>] [NOACK] STREAMS <key> [<key> ...] <ID> [<ID> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `GROUP <group> <consumer>` | Yes | No | Consumer group to read from, and the consumer within it that claims the entries. |
+| `COUNT <count>` | No | No | Maximum number of entries to return per stream. |
+| `BLOCK <milliseconds>` | No | No | Milliseconds to block waiting for new entries; `0` blocks indefinitely. |
+| `NOACK` | No | No | Do not add delivered entries to the pending list. |
+| `STREAMS <key> [<key> ...] <ID> [<ID> ...]` | Yes | No | Streams to read. List every key first, then one ID per key in the same order. |
+
+## Important points
+
+- A blocking form holds the request until data arrives or its timeout expires. Set the client/network timeout longer than the command timeout.
+- After `STREAMS`, provide all keys first and then exactly one ID for each key, in the same order.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Null bulk string or null array or Flat array of alternating keys and values |
+| RESP3 | Null or Map |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const result = await redis.xreadgroup("mygroup", "consumer1", "mystream", ">");
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.xreadgroup("workers", "worker-1", {"my-key": "0-0"})
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.xreadgroup("GROUP", "workers", "worker-1", "STREAMS", "my-key", "0-0");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.xReadGroup("workers", "worker-1", { key: "my-key", id: "0-0" });
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.xreadgroup("workers", "worker-1", {"my-key": "0-0"})
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.XReadGroup(context.Background(), &redis.XReadGroupArgs{Group: "workers", Consumer: "worker-1", Streams: []string{"my-key", "0-0"}}).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.xreadGroup("workers", "worker-1", redis.clients.jedis.params.XReadGroupParams.xReadGroupParams(), java.util.Map.of("my-key", new redis.clients.jedis.StreamEntryID("0-0")));
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let mut command = redis::cmd("XREADGROUP");
+    command.arg("GROUP");
+    command.arg("workers");
+    command.arg("worker-1");
+    command.arg("STREAMS");
+    command.arg("my-key");
+    command.arg("0-0");
+    let result: redis::Value = command.query(&mut connection)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/streams/xrevrange.mdx b/redis/commands/streams/xrevrange.mdx
new file mode 100644
index 000000000..b05c5408f
--- /dev/null
+++ b/redis/commands/streams/xrevrange.mdx
@@ -0,0 +1,167 @@
+---
+title: "XREVRANGE"
+description: "Get range in reverse order."
+---
+
+Use `XREVRANGE` to get range in reverse order.
+
+## Syntax
+
+```redis
+XREVRANGE <key> <end> <start> [COUNT <count>]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<end>` | Yes | No | Last ID to return, scanning backwards; `-` means the smallest possible ID. |
+| `<start>` | Yes | No | First ID to return, scanning backwards; `+` means the largest possible ID. |
+| `COUNT <count>` | No | No | Maximum number of entries to return. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of two-element entry arrays: ID and flat field/value array |
+| RESP3 | Array of two-element entry arrays: ID and flat field/value array |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const result = await redis.xrevrange("mystream", "+", "-");
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.xrevrange("my-key", "+", "-")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.xrevrange("my-key", "+", "-");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.xRevRange("my-key", "+", "-");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.xrevrange("my-key", "+", "-")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.XRevRange(context.Background(), "my-key", "+", "-").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.xrevrange("my-key", "+", "-");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.xrevrange("my-key", "+", "-")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/streams/xtrim.mdx b/redis/commands/streams/xtrim.mdx
new file mode 100644
index 000000000..b3f3d6e9b
--- /dev/null
+++ b/redis/commands/streams/xtrim.mdx
@@ -0,0 +1,169 @@
+---
+title: "XTRIM"
+description: "Trim stream to max length."
+---
+
+Use `XTRIM` to trim stream to max length.
+
+## Syntax
+
+```redis
+XTRIM <key> (MAXLEN | MINID) [= | ~] <threshold> [LIMIT <count>] [KEEPREF | DELREF | ACKED]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `(MAXLEN \| MINID) [= \| ~] <threshold> [LIMIT <count>] [KEEPREF \| DELREF \| ACKED]` | Yes | No | Trim the stream. `MAXLEN` caps the number of entries; `MINID` drops entries with a lower ID. `=` trims exactly and is the default; `~` trims approximately and is required before `LIMIT`, which caps how many entries a single call evicts. `KEEPREF` (the default) leaves consumer-group references to the deleted entries in place, `DELREF` removes those references too, and `ACKED` only removes entries that every group has read and acknowledged. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const result = await redis.xtrim("mystream", {
+  strategy: "MAXLEN",
+  threshold: 100,
+  exactness: "~"
+});
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.xtrim("my-key", maxlen=100)
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.xtrim("my-key", "MAXLEN", "100");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.xTrim("my-key", "MAXLEN", 100);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.xtrim("my-key", maxlen=100)
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.XTrimMaxLen(context.Background(), "my-key", 100).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.xtrim("my-key", redis.clients.jedis.params.XTrimParams.xTrimParams().maxLen(100));
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.xtrim("my-key", redis::streams::StreamMaxlen::Equals(100))?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/string/append.mdx b/redis/commands/string/append.mdx
new file mode 100644
index 000000000..2c41069c3
--- /dev/null
+++ b/redis/commands/string/append.mdx
@@ -0,0 +1,166 @@
+---
+title: "APPEND"
+description: "Append value to a string."
+---
+
+Use `APPEND` to append value to a string.
+
+## Syntax
+
+```redis
+APPEND <key> <value>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<value>` | Yes | No | String appended to the current value. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.append(key, "Hello");
+// returns 5
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.append("my-key", "value")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.append("my-key", "value");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.append("my-key", "value");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.append("my-key", "value")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.Append(context.Background(), "my-key", "value").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.append("my-key", "value");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.append("my-key", "value")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/string/decr.mdx b/redis/commands/string/decr.mdx
new file mode 100644
index 000000000..6d60f809f
--- /dev/null
+++ b/redis/commands/string/decr.mdx
@@ -0,0 +1,166 @@
+---
+title: "DECR"
+description: "Decrement integer value by 1."
+---
+
+Use `DECR` to decrement integer value by 1.
+
+## Syntax
+
+```redis
+DECR <key>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.set("key", 6);
+await redis.decr("key");
+// returns 5
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.decr("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.decr("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.decr("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.decr("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.Decr(context.Background(), "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.decr("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.decr("my-key", 1)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/string/decrby.mdx b/redis/commands/string/decrby.mdx
new file mode 100644
index 000000000..3fc38b3c9
--- /dev/null
+++ b/redis/commands/string/decrby.mdx
@@ -0,0 +1,167 @@
+---
+title: "DECRBY"
+description: "Decrement integer by amount."
+---
+
+Use `DECRBY` to decrement integer by amount.
+
+## Syntax
+
+```redis
+DECRBY <key> <decrement>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<decrement>` | Yes | No | Amount to subtract from the current value. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.set("key", 6);
+await redis.decrby("key", 4);
+// returns 2
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.decrby("my-key", 1)
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.decrby("my-key", "1");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.decrBy("my-key", 1);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.decrby("my-key", 1)
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.DecrBy(context.Background(), "my-key", 1).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.decrBy("my-key", 1);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.decr("my-key", 1)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/string/delex.mdx b/redis/commands/string/delex.mdx
new file mode 100644
index 000000000..0d13e8b38
--- /dev/null
+++ b/redis/commands/string/delex.mdx
@@ -0,0 +1,163 @@
+---
+title: "DELEX"
+description: "Delete a string when a condition matches."
+---
+
+Use `DELEX` to delete a string when a condition matches.
+
+## Syntax
+
+```redis
+DELEX <key> [IFEQ <value> | IFNE <value> | IFDEQ <digest> | IFDNE <digest>]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `key` | Yes | No | String key to delete. |
+| `IFEQ value \| IFNE value` | No | No | Delete when the stored string is equal to or different from the supplied value. |
+| `IFDEQ digest \| IFDNE digest` | No | No | Delete when the stored string digest is equal to or different from the supplied 16-character digest. |
+
+## Important points
+
+- Supply at most one condition. With no condition, `DELEX` behaves like deleting a single key.
+- Conditional forms accept string keys only. A non-string value returns an error and is not deleted.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+<Note>
+  This command is not supported yet in `upstash_redis`.
+</Note>
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.call("DELEX", "lock:job-1", "IFEQ", "worker-1");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.delEx("lock:job-1", { condition: "IFEQ", matchValue: "worker-1" });
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.execute_command("DELEX", "lock:job-1", "IFEQ", "worker-1")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.DelExArgs(context.Background(), "lock:job-1", redis.DelExArgs{Mode: "IFEQ", MatchValue: "worker-1"}).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.delex("lock:job-1", redis.clients.jedis.util.CompareCondition.valueEq("worker-1"));
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.del_ex("lock:job-1", redis::ValueComparison::ifeq("worker-1"))?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/string/digest.mdx b/redis/commands/string/digest.mdx
new file mode 100644
index 000000000..aec43d312
--- /dev/null
+++ b/redis/commands/string/digest.mdx
@@ -0,0 +1,161 @@
+---
+title: "DIGEST"
+description: "Get the digest of a string value."
+---
+
+Use `DIGEST` to get the digest of a string value.
+
+## Syntax
+
+```redis
+DIGEST <key>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `key` | Yes | No | String key whose value should be hashed. |
+
+## Important points
+
+- The reply is a 16-character lowercase hexadecimal XXH3 digest of the stored string bytes.
+- A missing key returns null. A key containing a non-string value returns `WRONGTYPE`.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Bulk string or Null bulk string or null array |
+| RESP3 | Bulk string or Null |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+<Note>
+  This command is not supported yet in `@upstash/redis`.
+</Note>
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+<Note>
+  This command is not supported yet in `upstash_redis`.
+</Note>
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.call("DIGEST", "lock:job-1");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.digest("lock:job-1");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.execute_command("DIGEST", "lock:job-1")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.Digest(context.Background(), "lock:job-1").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.digestKey("lock:job-1");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.digest("lock:job-1")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/string/get.mdx b/redis/commands/string/get.mdx
new file mode 100644
index 000000000..929f8c251
--- /dev/null
+++ b/redis/commands/string/get.mdx
@@ -0,0 +1,173 @@
+---
+title: "GET"
+description: "Get string value."
+---
+
+Use `GET` to get string value.
+
+## Syntax
+
+```redis
+GET <key>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Bulk string or Null bulk string or null array |
+| RESP3 | Bulk string or Null |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+type MyType = {
+    a: number;
+    b: string;
+}
+const value = await redis.get<MyType>("key");
+if (!value) {
+    // key doesn't exist
+} else {
+    // value is of type MyType
+}
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.get("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.get("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.get("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.get("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.Get(context.Background(), "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.get("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.get("my-key")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/string/getdel.mdx b/redis/commands/string/getdel.mdx
new file mode 100644
index 000000000..0c810eaf4
--- /dev/null
+++ b/redis/commands/string/getdel.mdx
@@ -0,0 +1,169 @@
+---
+title: "GETDEL"
+description: "Get value and delete key."
+---
+
+Use `GETDEL` to get value and delete key.
+
+## Syntax
+
+```redis
+GETDEL <key>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Bulk string or Null bulk string or null array |
+| RESP3 | Bulk string or Null |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+type MyType = {
+    a: number;
+    b: string;
+}
+await redis.getdel<MyType>("key");
+// returns {a: 1, b: "2"}
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.getdel("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.getdel("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.getDel("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.getdel("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.GetDel(context.Background(), "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.getDel("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.get_del("my-key")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/string/getex.mdx b/redis/commands/string/getex.mdx
new file mode 100644
index 000000000..817b4cf74
--- /dev/null
+++ b/redis/commands/string/getex.mdx
@@ -0,0 +1,165 @@
+---
+title: "GETEX"
+description: "Get value and set expiration."
+---
+
+Use `GETEX` to get value and set expiration.
+
+## Syntax
+
+```redis
+GETEX <key> [EX <seconds> | PX <milliseconds> | EXAT <unix-time-seconds> | PXAT <unix-time-milliseconds> | PERSIST]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `(EX <seconds> \| PX <milliseconds> \| EXAT <unix-time-seconds> \| PXAT <unix-time-milliseconds> \| PERSIST)` | No | No | Choose one form: `EX` (set a lifetime in seconds); `PX` (set a lifetime in milliseconds); `EXAT` (expire at a Unix timestamp in seconds); `PXAT` (expire at a Unix timestamp in milliseconds); `PERSIST`. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Bulk string or Null bulk string or null array |
+| RESP3 | Bulk string or Null |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+const result = await redis.getex("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.getex("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.getex("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.getEx("my-key", { type: "PX", value: 1000 });
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.getex("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.GetEx(context.Background(), "my-key", 0).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+import redis.clients.jedis.Jedis;
+import redis.clients.jedis.params.GetExParams;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.getEx("my-key", GetExParams.getExParams());
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.get_ex("my-key", redis::Expiry::PERSIST)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/string/getrange.mdx b/redis/commands/string/getrange.mdx
new file mode 100644
index 000000000..994aea1d9
--- /dev/null
+++ b/redis/commands/string/getrange.mdx
@@ -0,0 +1,170 @@
+---
+title: "GETRANGE"
+description: "Get substring of string."
+---
+
+Use `GETRANGE` to get substring of string.
+
+## Syntax
+
+```redis
+GETRANGE <key> <start> <end>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<start>` | Yes | No | Start byte offset; negative values count from the end. |
+| `<end>` | Yes | No | End byte offset, inclusive; negative values count from the end. |
+
+## Important points
+
+- `SUBSTR` is accepted as a deprecated alias with the same arguments and reply. New code should use `GETRANGE`.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Bulk string |
+| RESP3 | Bulk string |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const substring = await redis.getrange("key", 2, 4);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.getrange("my-key", "0", "1")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.getrange("my-key", "0", "1");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.getRange("my-key", 0, 1);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.getrange("my-key", "0", "1")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.GetRange(context.Background(), "my-key", 0, 1).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.getrange("my-key", 0, 1);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.getrange("my-key", 0, 1)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/string/getset.mdx b/redis/commands/string/getset.mdx
new file mode 100644
index 000000000..f5a053e88
--- /dev/null
+++ b/redis/commands/string/getset.mdx
@@ -0,0 +1,165 @@
+---
+title: "GETSET"
+description: "Set value and return old value."
+---
+
+Use `GETSET` to set value and return old value.
+
+## Syntax
+
+```redis
+GETSET <key> <value>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<value>` | Yes | No | String value to store in place of the current one. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Bulk string or Null bulk string or null array |
+| RESP3 | Bulk string or Null |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+const oldValue = await redis.getset("key", newValue);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.getset("my-key", "value")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.getset("my-key", "value");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.getSet("my-key", "value");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.getset("my-key", "value")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.GetSet(context.Background(), "my-key", "value").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.getSet("my-key", "value");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.getset("my-key", "value")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/string/incr.mdx b/redis/commands/string/incr.mdx
new file mode 100644
index 000000000..0dc60886a
--- /dev/null
+++ b/redis/commands/string/incr.mdx
@@ -0,0 +1,166 @@
+---
+title: "INCR"
+description: "Increment integer value by 1."
+---
+
+Use `INCR` to increment integer value by 1.
+
+## Syntax
+
+```redis
+INCR <key>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.set("key", 6);
+await redis.incr("key");
+// returns 7
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.incr("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.incr("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.incr("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.incr("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.Incr(context.Background(), "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.incr("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.incr("my-key", 1)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/string/incrby.mdx b/redis/commands/string/incrby.mdx
new file mode 100644
index 000000000..0c8d74bbf
--- /dev/null
+++ b/redis/commands/string/incrby.mdx
@@ -0,0 +1,167 @@
+---
+title: "INCRBY"
+description: "Increment integer by amount."
+---
+
+Use `INCRBY` to increment integer by amount.
+
+## Syntax
+
+```redis
+INCRBY <key> <increment>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<increment>` | Yes | No | Integer amount to add to the value. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.set("key", 6);
+await redis.incrby("key", 4);
+// returns 10
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.incrby("my-key", 1)
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.incrby("my-key", "1");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.incrBy("my-key", 1);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.incrby("my-key", 1)
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.IncrBy(context.Background(), "my-key", 1).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.incrBy("my-key", 1);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.incr("my-key", 1)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/string/incrbyfloat.mdx b/redis/commands/string/incrbyfloat.mdx
new file mode 100644
index 000000000..3f255268c
--- /dev/null
+++ b/redis/commands/string/incrbyfloat.mdx
@@ -0,0 +1,171 @@
+---
+title: "INCRBYFLOAT"
+description: "Increment float by amount."
+---
+
+Use `INCRBYFLOAT` to increment float by amount.
+
+## Syntax
+
+```redis
+INCRBYFLOAT <key> <increment>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<increment>` | Yes | No | Amount to add to the value; may be a floating-point number. |
+
+## Important points
+
+- The value is always returned as a bulk string, in both RESP2 and RESP3. Client libraries commonly decode it to a language number.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Bulk string |
+| RESP3 | Bulk string |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.set("key", 6);
+await redis.incrbyfloat("key", 4,5);
+// returns 10.5
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.incrbyfloat("my-key", 1.5)
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.incrbyfloat("my-key", "1.5");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.incrByFloat("my-key", 1.5);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.incrbyfloat("my-key", 1.5)
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.IncrByFloat(context.Background(), "my-key", 1.5).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.incrByFloat("my-key", 1.5);
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.incr("my-key", 1.5)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/string/mget.mdx b/redis/commands/string/mget.mdx
new file mode 100644
index 000000000..91d943bdd
--- /dev/null
+++ b/redis/commands/string/mget.mdx
@@ -0,0 +1,169 @@
+---
+title: "MGET"
+description: "Get values of multiple keys."
+---
+
+Use `MGET` to get values of multiple keys.
+
+## Syntax
+
+```redis
+MGET <key> [<key> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | Yes | Redis key targeted by the command. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of bulk-string values or null values, one per key |
+| RESP3 | Array of bulk-string values or null values, one per key |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+type MyType = {
+    a: number;
+    b: string;
+}
+const values = await redis.mget<MyType>("key1", "key2", "key3");
+// values.length -> 3
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.mget("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.mget("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.mGet(["my-key"]);
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.mget("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.MGet(context.Background(), "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.mget("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.mget(&["my-key"])?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/string/mset.mdx b/redis/commands/string/mset.mdx
new file mode 100644
index 000000000..c4cbd1d79
--- /dev/null
+++ b/redis/commands/string/mset.mdx
@@ -0,0 +1,168 @@
+---
+title: "MSET"
+description: "Set multiple keys at once."
+---
+
+Use `MSET` to set multiple keys at once.
+
+## Syntax
+
+```redis
+MSET <key> <value> [<key> <value> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key> <value>` | Yes | Yes | Key and the value to store in it. Repeat to set several keys in one call. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Simple string `OK` |
+| RESP3 | Simple string `OK` |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.mset({
+    key1: 1,
+    key2: "hello",
+    key3: { a: 1, b: "hello" },
+});
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.mset({"my-key": "value"})
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.mset("my-key", "value");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.mSet({ "my-key": "value" });
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.mset({"my-key": "value"})
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.MSet(context.Background(), "my-key", "value").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.mset("my-key", "value");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.mset(&[("my-key", "value")])?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/string/msetnx.mdx b/redis/commands/string/msetnx.mdx
new file mode 100644
index 000000000..d5d91331b
--- /dev/null
+++ b/redis/commands/string/msetnx.mdx
@@ -0,0 +1,167 @@
+---
+title: "MSETNX"
+description: "Set multiple keys if none exist."
+---
+
+Use `MSETNX` to set multiple keys if none exist.
+
+## Syntax
+
+```redis
+MSETNX <key> <value> [<key> <value> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key> <value>` | Yes | Yes | Key and the value to store in it. Repeat to set several keys in one call. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer: `1` if all keys were set, `0` if no key was set |
+| RESP3 | Integer: `1` if all keys were set, `0` if no key was set |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+redis.msetnx({
+  "key1": "value1",
+  "key2": "value2"
+})
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.msetnx({"my-key": "value"})
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.msetnx("my-key", "value");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.mSetNX({ "my-key": "value" });
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.msetnx({"my-key": "value"})
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.MSetNX(context.Background(), "my-key", "value").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.msetnx("my-key", "value");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.mset_nx(&[("my-key", "value")])?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/string/overview.mdx b/redis/commands/string/overview.mdx
new file mode 100644
index 000000000..d9c8e1928
--- /dev/null
+++ b/redis/commands/string/overview.mdx
@@ -0,0 +1,31 @@
+---
+title: "String commands"
+sidebarTitle: "Overview"
+description: "Commands for storing and manipulating string values."
+---
+
+<CardGroup cols={2}>
+<Card title="APPEND" href="/redis/commands/string/append">Append value to a string</Card>
+<Card title="DECR" href="/redis/commands/string/decr">Decrement integer value by 1</Card>
+<Card title="DECRBY" href="/redis/commands/string/decrby">Decrement integer by amount</Card>
+<Card title="DELEX" href="/redis/commands/string/delex">Delete a string when a condition matches</Card>
+<Card title="DIGEST" href="/redis/commands/string/digest">Get the digest of a string value</Card>
+<Card title="GET" href="/redis/commands/string/get">Get string value</Card>
+<Card title="GETDEL" href="/redis/commands/string/getdel">Get value and delete key</Card>
+<Card title="GETEX" href="/redis/commands/string/getex">Get value and set expiration</Card>
+<Card title="GETRANGE" href="/redis/commands/string/getrange">Get substring of string</Card>
+<Card title="GETSET" href="/redis/commands/string/getset">Set value and return old value</Card>
+<Card title="INCR" href="/redis/commands/string/incr">Increment integer value by 1</Card>
+<Card title="INCRBY" href="/redis/commands/string/incrby">Increment integer by amount</Card>
+<Card title="INCRBYFLOAT" href="/redis/commands/string/incrbyfloat">Increment float by amount</Card>
+<Card title="MGET" href="/redis/commands/string/mget">Get values of multiple keys</Card>
+<Card title="MSET" href="/redis/commands/string/mset">Set multiple keys at once</Card>
+<Card title="MSETNX" href="/redis/commands/string/msetnx">Set multiple keys if none exist</Card>
+<Card title="PSETEX" href="/redis/commands/string/psetex">Set value with ms expiration</Card>
+<Card title="SET" href="/redis/commands/string/set">Set string value</Card>
+<Card title="SETEX" href="/redis/commands/string/setex">Set value with expiration</Card>
+<Card title="SETNX" href="/redis/commands/string/setnx">Set value if key doesn't exist</Card>
+<Card title="SETRANGE" href="/redis/commands/string/setrange">Overwrite part of string</Card>
+<Card title="STRLEN" href="/redis/commands/string/strlen">Get string length</Card>
+</CardGroup>
+
diff --git a/redis/commands/string/psetex.mdx b/redis/commands/string/psetex.mdx
new file mode 100644
index 000000000..b2b78cce7
--- /dev/null
+++ b/redis/commands/string/psetex.mdx
@@ -0,0 +1,167 @@
+---
+title: "PSETEX"
+description: "Set value with ms expiration."
+---
+
+Use `PSETEX` to set value with ms expiration.
+
+## Syntax
+
+```redis
+PSETEX <key> <milliseconds> <value>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<milliseconds>` | Yes | No | Lifetime in milliseconds. |
+| `<value>` | Yes | No | String value to store. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Simple string `OK` |
+| RESP3 | Simple string `OK` |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+const result = await redis.psetex("my-key", 1000, "value");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.psetex("my-key", 1000, "value")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.psetex("my-key", "1000", "value");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.pSetEx("my-key", 1000, "value");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.psetex("my-key", 1000, "value")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+    "time"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.Set(context.Background(), "my-key", "value", time.Second).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.psetex("my-key", 1000, "value");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.pset_ex("my-key", "value", 1000)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/string/set.mdx b/redis/commands/string/set.mdx
new file mode 100644
index 000000000..c078be4a2
--- /dev/null
+++ b/redis/commands/string/set.mdx
@@ -0,0 +1,174 @@
+---
+title: "SET"
+description: "Set string value."
+---
+
+Use `SET` to set string value.
+
+## Syntax
+
+```redis
+SET <key> <value> [NX | XX | IFEQ <ifeq-value> | IFNE <ifne-value> | IFDEQ <ifdeq-digest> | IFDNE <ifdne-digest>] [GET] [EX <seconds> | PX <milliseconds> | EXAT <unix-time-seconds> | PXAT <unix-time-milliseconds> | KEEPTTL]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<value>` | Yes | No | String value to store. |
+| `(NX \| XX \| IFEQ <ifeq-value> \| IFNE <ifne-value> \| IFDEQ <ifdeq-digest> \| IFDNE <ifdne-digest>)` | No | No | Choose one form: `NX` (only when the key does not exist); `XX` (only when it already exists); `IFEQ` (only when the current value equals `<ifeq-value>`); `IFNE` (only when it differs); `IFDEQ` (only when the current value's digest equals `<ifdeq-digest>`); `IFDNE` (only when it differs). |
+| `GET` | No | No | Also return the previous value. |
+| `(EX <seconds> \| PX <milliseconds> \| EXAT <unix-time-seconds> \| PXAT <unix-time-milliseconds> \| KEEPTTL)` | No | No | Choose one form: `EX` (set a lifetime in seconds); `PX` (set a lifetime in milliseconds); `EXAT` (expire at a Unix timestamp in seconds); `PXAT` (expire at a Unix timestamp in milliseconds); `KEEPTTL` (preserve the existing key lifetime). |
+
+## Important points
+
+- `NX` and `XX` are mutually exclusive.
+- Choose at most one expiration form and at most one condition. `GET` changes a successful reply from `OK` to the previous value.
+- `IFEQ`/`IFNE` compare the current value; `IFDEQ`/`IFDNE` compare its digest. These conditional forms are implemented by this Upstash deployment.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Simple string `OK`; with `GET`, the previous value as a bulk string, or Null bulk string or null array when the key did not exist or a condition failed |
+| RESP3 | Simple string `OK`; with `GET`, the previous value as a bulk string, or Null when the key did not exist or a condition failed |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.set("my-key", {my: "value"});
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.set("my-key", "value")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.set("my-key", "value");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.set("my-key", "value");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.set("my-key", "value")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.Set(context.Background(), "my-key", "value", 0).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.set("my-key", "value");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.set("my-key", "value")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/string/setex.mdx b/redis/commands/string/setex.mdx
new file mode 100644
index 000000000..a258c4727
--- /dev/null
+++ b/redis/commands/string/setex.mdx
@@ -0,0 +1,167 @@
+---
+title: "SETEX"
+description: "Set value with expiration."
+---
+
+Use `SETEX` to set value with expiration.
+
+## Syntax
+
+```redis
+SETEX <key> <seconds> <value>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<seconds>` | Yes | No | Lifetime in seconds. |
+| `<value>` | Yes | No | String value to store. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Simple string `OK` |
+| RESP3 | Simple string `OK` |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+const result = await redis.setex("my-key", 1000, "value");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.setex("my-key", 1000, "value")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.setex("my-key", "1000", "value");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.setEx("my-key", 1000, "value");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.setex("my-key", 1000, "value")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+    "time"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.SetEx(context.Background(), "my-key", "value", 1000*time.Second).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.setex("my-key", 1000, "value");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.set_ex("my-key", "value", 1000)?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/string/setnx.mdx b/redis/commands/string/setnx.mdx
new file mode 100644
index 000000000..0d0d2aee0
--- /dev/null
+++ b/redis/commands/string/setnx.mdx
@@ -0,0 +1,165 @@
+---
+title: "SETNX"
+description: "Set value if key doesn't exist."
+---
+
+Use `SETNX` to set value if key doesn't exist.
+
+## Syntax
+
+```redis
+SETNX <key> <value>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<value>` | Yes | No | String value to store. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer: `1` if the key was set, `0` if it already exists |
+| RESP3 | Integer: `1` if the key was set, `0` if it already exists |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+const result = await redis.setnx("my-key", "value");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.setnx("my-key", "value")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.setnx("my-key", "value");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.setNX("my-key", "value");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.setnx("my-key", "value")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.SetNX(context.Background(), "my-key", "value", 0).Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.setnx("my-key", "value");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.set_nx("my-key", "value")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/string/setrange.mdx b/redis/commands/string/setrange.mdx
new file mode 100644
index 000000000..1516cda30
--- /dev/null
+++ b/redis/commands/string/setrange.mdx
@@ -0,0 +1,170 @@
+---
+title: "SETRANGE"
+description: "Overwrite part of string."
+---
+
+Use `SETRANGE` to overwrite part of string.
+
+## Syntax
+
+```redis
+SETRANGE <key> <offset> <value>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+| `<offset>` | Yes | No | Zero-based byte offset to write at. The value is zero-padded if the key is shorter. |
+| `<value>` | Yes | No | String written starting at the offset. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.set("key", "helloworld")
+const length = await redis.setrange("key", 5, "redis");
+console.log(length); // 10
+
+// The value of "key" is now "helloredis"
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.setrange("my-key", 0, "value")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.setrange("my-key", "0", "value");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.setRange("my-key", 0, "value");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.setrange("my-key", 0, "value")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.SetRange(context.Background(), "my-key", 0, "value").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.setrange("my-key", 0, "value");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.setrange("my-key", 0, "value")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/string/strlen.mdx b/redis/commands/string/strlen.mdx
new file mode 100644
index 000000000..61b8848a1
--- /dev/null
+++ b/redis/commands/string/strlen.mdx
@@ -0,0 +1,166 @@
+---
+title: "STRLEN"
+description: "Get string length."
+---
+
+Use `STRLEN` to get string length.
+
+## Syntax
+
+```redis
+STRLEN <key>
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | No | Redis key targeted by the command. |
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Integer |
+| RESP3 | Integer |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="@upstash/redis">
+
+```ts
+import { Redis } from "@upstash/redis";
+
+const redis = Redis.fromEnv();
+
+await redis.set("key", "helloworld")
+const length = await redis.strlen("key");
+console.log(length); // 10
+```
+
+</Tab>
+
+<Tab title="upstash_redis">
+
+```python
+from upstash_redis import Redis
+
+redis = Redis.from_env()
+result = redis.strlen("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const redis = new Redis(process.env.REDIS_URL!);
+const result = await redis.strlen("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL })
+  .on("error", console.error)
+  .connect();
+const result = await client.strLen("my-key");
+console.log(result);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+result = client.strlen("my-key")
+print(result)
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+
+    "github.com/redis/go-redis/v9"
+)
+
+func main() {
+    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+    if err != nil {
+        panic(err)
+    }
+    client := redis.NewClient(opts)
+    result, err := client.StrLen(context.Background(), "my-key").Result()
+    if err != nil {
+        panic(err)
+    }
+    fmt.Println(result)
+}
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  Object result = jedis.strlen("my-key");
+  System.out.println(result);
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+use redis::TypedCommands;
+
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let result = connection.strlen("my-key")?;
+    println!("{result:?}");
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/transactions/discard.mdx b/redis/commands/transactions/discard.mdx
new file mode 100644
index 000000000..e604464a0
--- /dev/null
+++ b/redis/commands/transactions/discard.mdx
@@ -0,0 +1,125 @@
+---
+title: "DISCARD"
+description: "Discard queued commands."
+---
+
+Use `DISCARD` to discard queued commands.
+
+## Syntax
+
+```redis
+DISCARD
+```
+
+## Arguments
+
+This command takes no arguments.
+
+## Important points
+
+- The raw command is TCP-only. For HTTP, use an Upstash SDK transaction API rather than sending this command directly.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Simple string `OK` |
+| RESP3 | Simple string `OK` |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const client = new Redis(process.env.REDIS_URL!);
+await client.multi({ pipeline: false });
+await client.set("balance", "100");
+await client.discard();
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL }).connect();
+await client.sendCommand(["MULTI"]);
+await client.sendCommand(["SET", "balance", "100"]);
+await client.sendCommand(["DISCARD"]);
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+with client.pipeline(transaction=True) as pipe:
+    pipe.set("balance", "100")
+    pipe.reset()
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+ctx := context.Background()
+opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+if err != nil { panic(err) }
+client := redis.NewClient(opts)
+
+pipe := client.TxPipeline()
+pipe.Set(ctx, "balance", "100", 0)
+pipe.Discard()
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+import redis.clients.jedis.Jedis;
+import redis.clients.jedis.Transaction;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")));
+     Transaction transaction = jedis.multi()) {
+  transaction.set("balance", "100");
+  transaction.discard();
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let mut transaction = redis::pipe();
+    transaction.atomic().set("balance", "100");
+    transaction.clear();
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/transactions/exec.mdx b/redis/commands/transactions/exec.mdx
new file mode 100644
index 000000000..26d5e111c
--- /dev/null
+++ b/redis/commands/transactions/exec.mdx
@@ -0,0 +1,127 @@
+---
+title: "EXEC"
+description: "Execute queued commands."
+---
+
+Use `EXEC` to execute queued commands.
+
+## Syntax
+
+```redis
+EXEC
+```
+
+## Arguments
+
+This command takes no arguments.
+
+## Important points
+
+- The raw command is TCP-only. For HTTP, use an Upstash SDK transaction API rather than sending this command directly.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Array of command replies or Null bulk string or null array |
+| RESP3 | Array of command replies or Null |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const client = new Redis(process.env.REDIS_URL!);
+const result = await client.multi().set("balance", "100").exec();
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL }).connect();
+const result = await client.multi().set("balance", "100").exec();
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+with client.pipeline(transaction=True) as pipe:
+    result = pipe.set("balance", "100").execute()
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+ctx := context.Background()
+opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+if err != nil { panic(err) }
+client := redis.NewClient(opts)
+
+pipe := client.TxPipeline()
+pipe.Set(ctx, "balance", "100", 0)
+result, err := pipe.Exec(ctx)
+if err != nil { panic(err) }
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+import redis.clients.jedis.Jedis;
+import redis.clients.jedis.Transaction;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")));
+     Transaction transaction = jedis.multi()) {
+  transaction.set("balance", "100");
+  Object result = transaction.exec();
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    redis::pipe()
+        .atomic()
+        .set("balance", "100")
+        .ignore()
+        .query::<()>(&mut connection)?;
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/transactions/multi.mdx b/redis/commands/transactions/multi.mdx
new file mode 100644
index 000000000..36614c7a8
--- /dev/null
+++ b/redis/commands/transactions/multi.mdx
@@ -0,0 +1,127 @@
+---
+title: "MULTI"
+description: "Start a transaction."
+---
+
+Use `MULTI` to start a transaction.
+
+## Syntax
+
+```redis
+MULTI
+```
+
+## Arguments
+
+This command takes no arguments.
+
+## Important points
+
+- The raw command is TCP-only. For HTTP, use an Upstash SDK transaction API rather than sending this command directly.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Simple string `OK` |
+| RESP3 | Simple string `OK` |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const client = new Redis(process.env.REDIS_URL!);
+const result = await client.multi().set("balance", "100").exec();
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL }).connect();
+const result = await client.multi().set("balance", "100").exec();
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+with client.pipeline(transaction=True) as pipe:
+    result = pipe.set("balance", "100").execute()
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+ctx := context.Background()
+opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+if err != nil { panic(err) }
+client := redis.NewClient(opts)
+
+pipe := client.TxPipeline()
+pipe.Set(ctx, "balance", "100", 0)
+result, err := pipe.Exec(ctx)
+if err != nil { panic(err) }
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+import redis.clients.jedis.Jedis;
+import redis.clients.jedis.Transaction;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")));
+     Transaction transaction = jedis.multi()) {
+  transaction.set("balance", "100");
+  Object result = transaction.exec();
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    redis::pipe()
+        .atomic()
+        .set("balance", "100")
+        .ignore()
+        .query::<()>(&mut connection)?;
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/transactions/overview.mdx b/redis/commands/transactions/overview.mdx
new file mode 100644
index 000000000..3a16d1795
--- /dev/null
+++ b/redis/commands/transactions/overview.mdx
@@ -0,0 +1,14 @@
+---
+title: "Transactions commands"
+sidebarTitle: "Overview"
+description: "Commands for grouping operations into atomic transactions."
+---
+
+<CardGroup cols={2}>
+<Card title="DISCARD" href="/redis/commands/transactions/discard">Discard queued commands</Card>
+<Card title="EXEC" href="/redis/commands/transactions/exec">Execute queued commands</Card>
+<Card title="MULTI" href="/redis/commands/transactions/multi">Start a transaction</Card>
+<Card title="UNWATCH" href="/redis/commands/transactions/unwatch">Unwatch all keys</Card>
+<Card title="WATCH" href="/redis/commands/transactions/watch">Watch keys for changes</Card>
+</CardGroup>
+
diff --git a/redis/commands/transactions/unwatch.mdx b/redis/commands/transactions/unwatch.mdx
new file mode 100644
index 000000000..b13db9a03
--- /dev/null
+++ b/redis/commands/transactions/unwatch.mdx
@@ -0,0 +1,126 @@
+---
+title: "UNWATCH"
+description: "Unwatch all keys."
+---
+
+Use `UNWATCH` to unwatch all keys.
+
+## Syntax
+
+```redis
+UNWATCH
+```
+
+## Arguments
+
+This command takes no arguments.
+
+## Important points
+
+- The raw command is TCP-only. For HTTP, use an Upstash SDK transaction API rather than sending this command directly.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Simple string `OK` |
+| RESP3 | Simple string `OK` |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const client = new Redis(process.env.REDIS_URL!);
+await client.watch("balance");
+await client.unwatch();
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL }).connect();
+await client.watch("balance");
+await client.unwatch();
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+with client.pipeline() as pipe:
+    pipe.watch("balance")
+    pipe.unwatch()
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+ctx := context.Background()
+opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+if err != nil { panic(err) }
+client := redis.NewClient(opts)
+
+err = client.Watch(ctx, func(tx *redis.Tx) error {
+    return tx.Unwatch(ctx).Err()
+}, "balance")
+if err != nil { panic(err) }
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+import redis.clients.jedis.Jedis;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  jedis.watch("balance");
+  jedis.unwatch();
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    redis::transaction(&mut connection, &["balance"], |_con, _pipe| {
+        Ok(Some(()))
+    })?;
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/commands/transactions/watch.mdx b/redis/commands/transactions/watch.mdx
new file mode 100644
index 000000000..aa4865d80
--- /dev/null
+++ b/redis/commands/transactions/watch.mdx
@@ -0,0 +1,138 @@
+---
+title: "WATCH"
+description: "Watch keys for changes."
+---
+
+Use `WATCH` to watch keys for changes.
+
+## Syntax
+
+```redis
+WATCH <key> [<key> ...]
+```
+
+## Arguments
+
+| Argument | Required | Repeatable | Description |
+| --- | --- | --- | --- |
+| `<key>` | Yes | Yes | Redis key targeted by the command. |
+
+## Important points
+
+- The raw command is TCP-only. For HTTP, use an Upstash SDK transaction API rather than sending this command directly.
+
+## Response
+
+The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
+
+| Protocol | Reply |
+| --- | --- |
+| RESP2 | Simple string `OK` |
+| RESP3 | Simple string `OK` |
+
+<Note>
+  Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
+</Note>
+
+## Examples
+
+TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
+
+<Tabs>
+
+<Tab title="ioredis">
+
+```ts
+import Redis from "ioredis";
+
+const client = new Redis(process.env.REDIS_URL!);
+await client.watch("balance");
+const result = await client.multi().set("balance", "100").exec();
+```
+
+</Tab>
+
+<Tab title="node-redis">
+
+```ts
+import { createClient } from "redis";
+
+const client = await createClient({ url: process.env.REDIS_URL }).connect();
+await client.watch("balance");
+const result = await client.multi().set("balance", "100").exec();
+```
+
+</Tab>
+
+<Tab title="redis-py">
+
+```python
+import os
+import redis
+
+client = redis.from_url(os.environ["REDIS_URL"])
+with client.pipeline() as pipe:
+    pipe.watch("balance")
+    pipe.multi()
+    pipe.set("balance", "100")
+    result = pipe.execute()
+```
+
+</Tab>
+
+<Tab title="go-redis">
+
+```go
+ctx := context.Background()
+opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))
+if err != nil { panic(err) }
+client := redis.NewClient(opts)
+
+err = client.Watch(ctx, func(tx *redis.Tx) error {
+    _, err := tx.TxPipelined(ctx, func(pipe redis.Pipeliner) error {
+        pipe.Set(ctx, "balance", "100", 0)
+        return nil
+    })
+    return err
+}, "balance")
+if err != nil { panic(err) }
+```
+
+</Tab>
+
+<Tab title="jedis">
+
+```java
+import java.net.URI;
+import redis.clients.jedis.Jedis;
+import redis.clients.jedis.Transaction;
+
+try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
+  jedis.watch("balance");
+  try (Transaction transaction = jedis.multi()) {
+    transaction.set("balance", "100");
+    Object result = transaction.exec();
+  }
+}
+```
+
+</Tab>
+
+<Tab title="redis-rs">
+
+```rust
+fn main() -> redis::RedisResult<()> {
+    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
+    let client = redis::Client::open(url)?;
+    let mut connection = client.get_connection()?;
+
+    let _: () = redis::transaction(&mut connection, &["balance"], |con, pipe| {
+        pipe.set("balance", "100").ignore().query::<Option<()>>(con)
+    })?;
+    Ok(())
+}
+```
+
+</Tab>
+
+</Tabs>
diff --git a/redis/overall/changelog.mdx b/redis/overall/changelog.mdx
index 18b61581f..af8e7be30 100644
--- a/redis/overall/changelog.mdx
+++ b/redis/overall/changelog.mdx
@@ -8,14 +8,14 @@ Added [Upstash Redis Search](/redis/search/introduction) feature, a new extensio
 Redis Search is available through the [@upstash/redis](/redis/sdks/ts/overview) and [upstash-redis](/redis/sdks/py/overview) SDKs. If you already use `node-redis` or `ioredis`, you can use the [`@upstash/search-redis`](/redis/search/adapters/node-redis) and [`@upstash/search-ioredis`](/redis/search/adapters/ioredis) wrappers without switching clients.
 
 New Redis Search commands:
-- [`SEARCH.CREATE`](/redis/search/command-reference#searchcreate): Create a search index
-- [`SEARCH.DROP`](/redis/search/command-reference#searchdrop): Remove a search index
-- [`SEARCH.DESCRIBE`](/redis/search/command-reference#searchdescribe): Return metadata about a search index
-- [`SEARCH.WAITINDEXING`](/redis/search/command-reference#searchwaitindexing): Wait until pending index updates are visible to queries
-- [`SEARCH.QUERY`](/redis/search/command-reference#searchquery): Search documents with a JSON filter
-- [`SEARCH.COUNT`](/redis/search/command-reference#searchcount): Count matching documents without returning them
-- [`SEARCH.AGGREGATE`](/redis/search/command-reference#searchaggregate): Compute analytics over matching documents
-- [`SEARCH.ALIASADD`](/redis/search/command-reference#searchaliasadd), [`SEARCH.ALIASDEL`](/redis/search/command-reference#searchaliasdel), and [`SEARCH.LISTALIASES`](/redis/search/command-reference#searchlistaliases): Manage search index aliases
+- [`SEARCH.CREATE`](/redis/commands/search/search-create): Create a search index
+- [`SEARCH.DROP`](/redis/commands/search/search-drop): Remove a search index
+- [`SEARCH.DESCRIBE`](/redis/commands/search/search-describe): Return metadata about a search index
+- [`SEARCH.WAITINDEXING`](/redis/commands/search/search-waitindexing): Wait until pending index updates are visible to queries
+- [`SEARCH.QUERY`](/redis/commands/search/search-query): Search documents with a JSON filter
+- [`SEARCH.COUNT`](/redis/commands/search/search-count): Count matching documents without returning them
+- [`SEARCH.AGGREGATE`](/redis/commands/search/search-aggregate): Compute analytics over matching documents
+- [`SEARCH.ALIASADD`](/redis/commands/search/search-aliasadd), [`SEARCH.ALIASDEL`](/redis/commands/search/search-aliasdel), and [`SEARCH.LISTALIASES`](/redis/commands/search/search-listaliases): Manage search index aliases
 </Update>
 
 <Update label="December 2025">
diff --git a/redis/overall/compatibility.mdx b/redis/overall/compatibility.mdx
index 4f267b72c..3dba3a023 100755
--- a/redis/overall/compatibility.mdx
+++ b/redis/overall/compatibility.mdx
@@ -9,363 +9,11 @@ sidebarTitle: "Compatibility"
 
 Upstash supports Redis client protocol up to version `8.2`. We are also gradually adding changes introduced in later versions.
 
-This page lists Redis command support at the Upstash Redis API level. SDK command references may cover a smaller set of typed helpers.
-For example, see the [TypeScript SDK command reference](/redis/sdks/ts/commands/overview) for the commands documented in `@upstash/redis`.
-
-Most of the unsupported items are in our roadmap. If you need a feature that we do not support, please drop a note to [support@upstash.com](mailto:support@upstash.com).
-So we can inform you when we are planning to support it.
-
----
-
-## Supported Commands
-
-<AccordionGroup>
-
-<Accordion title="Bitmap" icon="grid">
-<CardGroup cols={2}>
-<Card title="BITCOUNT" href="https://redis.io/docs/latest/commands/bitcount/">Count set bits in a string</Card>
-<Card title="BITFIELD" href="https://redis.io/docs/latest/commands/bitfield/">Perform arbitrary bitfield operations</Card>
-<Card title="BITFIELD_RO" href="https://redis.io/docs/latest/commands/bitfield_ro/">Read-only bitfield operations</Card>
-<Card title="BITOP" href="https://redis.io/docs/latest/commands/bitop/">Perform bitwise operations between strings</Card>
-<Card title="BITPOS" href="https://redis.io/docs/latest/commands/bitpos/">Find first bit set or clear in a string</Card>
-<Card title="GETBIT" href="https://redis.io/docs/latest/commands/getbit/">Get the bit value at offset</Card>
-<Card title="SETBIT" href="https://redis.io/docs/latest/commands/setbit/">Set or clear the bit at offset</Card>
-</CardGroup>
-</Accordion>
-
-<Accordion title="Connection" icon="plug">
-<CardGroup cols={2}>
-<Card title="AUTH" href="https://redis.io/docs/latest/commands/auth/">Authenticate to the server</Card>
-<Card title="CLIENT GETNAME" href="https://redis.io/docs/latest/commands/client-getname/">Get the current connection name</Card>
-<Card title="CLIENT ID" href="https://redis.io/docs/latest/commands/client-id/">Get the current client ID</Card>
-<Card title="CLIENT INFO" href="https://redis.io/docs/latest/commands/client-info/">Get info about current connection</Card>
-<Card title="CLIENT LIST" href="https://redis.io/docs/latest/commands/client-list/">List all client connections</Card>
-<Card title="CLIENT SETINFO" href="https://redis.io/docs/latest/commands/client-setinfo/">Set client connection attributes</Card>
-<Card title="CLIENT SETNAME" href="https://redis.io/docs/latest/commands/client-setname/">Set the connection name</Card>
-<Card title="ECHO" href="https://redis.io/docs/latest/commands/echo/">Echo the given string</Card>
-<Card title="HELLO" href="https://redis.io/docs/latest/commands/hello/">Handshake with Redis protocol</Card>
-<Card title="PING" href="https://redis.io/docs/latest/commands/ping/">Ping the server</Card>
-<Card title="QUIT" href="https://redis.io/docs/latest/commands/quit/">Close the connection</Card>
-<Card title="RESET" href="https://redis.io/docs/latest/commands/reset/">Reset the connection</Card>
-<Card title="SELECT" href="https://redis.io/docs/latest/commands/select/">Select the database by index</Card>
-</CardGroup>
-</Accordion>
-
-<Accordion title="Functions" icon="code">
-<CardGroup cols={2}>
-<Card title="FCALL" href="https://redis.io/docs/latest/commands/fcall/">Call a function</Card>
-<Card title="FCALL_RO" href="https://redis.io/docs/latest/commands/fcall_ro/">Call a read-only function</Card>
-<Card title="FUNCTION DELETE" href="https://redis.io/docs/latest/commands/function-delete/">Delete a library</Card>
-<Card title="FUNCTION FLUSH" href="https://redis.io/docs/latest/commands/function-flush/">Delete all libraries</Card>
-<Card title="FUNCTION KILL" href="https://redis.io/docs/latest/commands/function-kill/">Kill a running function</Card>
-<Card title="FUNCTION LIST" href="https://redis.io/docs/latest/commands/function-list/">List all libraries</Card>
-<Card title="FUNCTION LOAD" href="https://redis.io/docs/latest/commands/function-load/">Load a library</Card>
-<Card title="FUNCTION STATS" href="https://redis.io/docs/latest/commands/function-stats/">Get function execution stats</Card>
-</CardGroup>
-</Accordion>
-
-<Accordion title="Generic" icon="sliders">
-<CardGroup cols={2}>
-<Card title="COPY" href="https://redis.io/docs/latest/commands/copy/">Copy a key to another key</Card>
-<Card title="DEL" href="https://redis.io/docs/latest/commands/del/">Delete one or more keys</Card>
-<Card title="DUMP" href="https://redis.io/docs/latest/commands/dump/">Serialize a key's value</Card>
-<Card title="EXISTS" href="https://redis.io/docs/latest/commands/exists/">Check if keys exist</Card>
-<Card title="EXPIRE" href="https://redis.io/docs/latest/commands/expire/">Set a key's TTL in seconds</Card>
-<Card title="EXPIREAT" href="https://redis.io/docs/latest/commands/expireat/">Set expiry as Unix timestamp</Card>
-<Card title="EXPIRETIME" href="https://redis.io/docs/latest/commands/expiretime/">Get expiry as Unix timestamp</Card>
-<Card title="KEYS" href="https://redis.io/docs/latest/commands/keys/">Find keys matching a pattern</Card>
-<Card title="PERSIST" href="https://redis.io/docs/latest/commands/persist/">Remove the expiration from a key</Card>
-<Card title="PEXPIRE" href="https://redis.io/docs/latest/commands/pexpire/">Set a key's TTL in milliseconds</Card>
-<Card title="PEXPIREAT" href="https://redis.io/docs/latest/commands/pexpireat/">Set expiry as Unix ms timestamp</Card>
-<Card title="PEXPIRETIME" href="https://redis.io/docs/latest/commands/pexpiretime/">Get expiry as Unix ms timestamp</Card>
-<Card title="PTTL" href="https://redis.io/docs/latest/commands/pttl/">Get TTL in milliseconds</Card>
-<Card title="RANDOMKEY" href="https://redis.io/docs/latest/commands/randomkey/">Return a random key</Card>
-<Card title="RENAME" href="https://redis.io/docs/latest/commands/rename/">Rename a key</Card>
-<Card title="RENAMENX" href="https://redis.io/docs/latest/commands/renamenx/">Rename a key if new key doesn't exist</Card>
-<Card title="RESTORE" href="https://redis.io/docs/latest/commands/restore/">Deserialize and restore a key</Card>
-<Card title="SCAN" href="https://redis.io/docs/latest/commands/scan/">Incrementally iterate keys</Card>
-<Card title="TOUCH" href="https://redis.io/docs/latest/commands/touch/">Update last access time of keys</Card>
-<Card title="TTL" href="https://redis.io/docs/latest/commands/ttl/">Get TTL in seconds</Card>
-<Card title="TYPE" href="https://redis.io/docs/latest/commands/type/">Get the type of a key</Card>
-<Card title="UNLINK" href="https://redis.io/docs/latest/commands/unlink/">Delete keys asynchronously</Card>
-</CardGroup>
-</Accordion>
-
-<Accordion title="Geo" icon="location-dot">
-<CardGroup cols={2}>
-<Card title="GEOADD" href="https://redis.io/docs/latest/commands/geoadd/">Add geospatial items</Card>
-<Card title="GEODIST" href="https://redis.io/docs/latest/commands/geodist/">Get distance between two members</Card>
-<Card title="GEOHASH" href="https://redis.io/docs/latest/commands/geohash/">Get geohash strings for members</Card>
-<Card title="GEOPOS" href="https://redis.io/docs/latest/commands/geopos/">Get coordinates of members</Card>
-<Card title="GEORADIUS" href="https://redis.io/docs/latest/commands/georadius/">Query members within radius</Card>
-<Card title="GEORADIUS_RO" href="https://redis.io/docs/latest/commands/georadius_ro/">Read-only radius query</Card>
-<Card title="GEORADIUSBYMEMBER" href="https://redis.io/docs/latest/commands/georadiusbymember/">Radius query centered on member</Card>
-<Card title="GEORADIUSBYMEMBER_RO" href="https://redis.io/docs/latest/commands/georadiusbymember_ro/">Read-only radius query by member</Card>
-<Card title="GEOSEARCH" href="https://redis.io/docs/latest/commands/geosearch/">Search for members in an area</Card>
-<Card title="GEOSEARCHSTORE" href="https://redis.io/docs/latest/commands/geosearchstore/">Store geosearch results</Card>
-</CardGroup>
-</Accordion>
-
-<Accordion title="Hash" icon="hashtag">
-<CardGroup cols={2}>
-<Card title="HDEL" href="https://redis.io/docs/latest/commands/hdel/">Delete one or more hash fields</Card>
-<Card title="HEXISTS" href="https://redis.io/docs/latest/commands/hexists/">Check if a hash field exists</Card>
-<Card title="HEXPIRE" href="https://redis.io/docs/latest/commands/hexpire/">Set field TTL in seconds</Card>
-<Card title="HEXPIREAT" href="https://redis.io/docs/latest/commands/hexpireat/">Set field expiry as timestamp</Card>
-<Card title="HEXPIRETIME" href="https://redis.io/docs/latest/commands/hexpiretime/">Get field expiry as timestamp</Card>
-<Card title="HGET" href="https://redis.io/docs/latest/commands/hget/">Get the value of a hash field</Card>
-<Card title="HGETALL" href="https://redis.io/docs/latest/commands/hgetall/">Get all fields and values</Card>
-<Card title="HGETDEL" href="https://redis.io/docs/latest/commands/hgetdel/">Get and delete hash fields</Card>
-<Card title="HGETEX" href="https://redis.io/docs/latest/commands/hgetex/">Get fields and set their expiry</Card>
-<Card title="HINCRBY" href="https://redis.io/docs/latest/commands/hincrby/">Increment integer value of a field</Card>
-<Card title="HINCRBYFLOAT" href="https://redis.io/docs/latest/commands/hincrbyfloat/">Increment float value of a field</Card>
-<Card title="HKEYS" href="https://redis.io/docs/latest/commands/hkeys/">Get all fields in a hash</Card>
-<Card title="HLEN" href="https://redis.io/docs/latest/commands/hlen/">Get number of fields in a hash</Card>
-<Card title="HMGET" href="https://redis.io/docs/latest/commands/hmget/">Get values of multiple fields</Card>
-<Card title="HMSET" href="https://redis.io/docs/latest/commands/hmset/">Set multiple hash fields</Card>
-<Card title="HPERSIST" href="https://redis.io/docs/latest/commands/hpersist/">Remove field expiration</Card>
-<Card title="HPEXPIRE" href="https://redis.io/docs/latest/commands/hpexpire/">Set field TTL in milliseconds</Card>
-<Card title="HPEXPIREAT" href="https://redis.io/docs/latest/commands/hpexpireat/">Set field expiry as ms timestamp</Card>
-<Card title="HPEXPIRETIME" href="https://redis.io/docs/latest/commands/hpexpiretime/">Get field expiry as ms timestamp</Card>
-<Card title="HPTTL" href="https://redis.io/docs/latest/commands/hpttl/">Get field TTL in milliseconds</Card>
-<Card title="HRANDFIELD" href="https://redis.io/docs/latest/commands/hrandfield/">Get random fields from a hash</Card>
-<Card title="HSCAN" href="https://redis.io/docs/latest/commands/hscan/">Incrementally iterate hash fields</Card>
-<Card title="HSET" href="https://redis.io/docs/latest/commands/hset/">Set hash field values</Card>
-<Card title="HSETEX" href="https://redis.io/docs/latest/commands/hsetex/">Set fields with expiration</Card>
-<Card title="HSETNX" href="https://redis.io/docs/latest/commands/hsetnx/">Set field only if it doesn't exist</Card>
-<Card title="HSTRLEN" href="https://redis.io/docs/latest/commands/hstrlen/">Get length of a field's value</Card>
-<Card title="HTTL" href="https://redis.io/docs/latest/commands/httl/">Get field TTL in seconds</Card>
-<Card title="HVALS" href="https://redis.io/docs/latest/commands/hvals/">Get all values in a hash</Card>
-</CardGroup>
-</Accordion>
-
-<Accordion title="HyperLogLog" icon="chart-simple">
-<CardGroup cols={2}>
-<Card title="PFADD" href="https://redis.io/docs/latest/commands/pfadd/">Add elements to HyperLogLog</Card>
-<Card title="PFCOUNT" href="https://redis.io/docs/latest/commands/pfcount/">Get estimated cardinality</Card>
-<Card title="PFMERGE" href="https://redis.io/docs/latest/commands/pfmerge/">Merge multiple HyperLogLogs</Card>
-</CardGroup>
-</Accordion>
-
-<Accordion title="JSON" icon="brackets-curly">
-To query inside JSON values (full-text, fuzzy, phrase, regex), see [Upstash Redis Search](/redis/search/introduction).
+<Card title="Browse the Redis command reference" icon="book-open" href="/redis/commands/overview" horizontal>
+  See every supported Redis command, organized by category.
+</Card>
 
-<CardGroup cols={2}>
-<Card title="JSON.ARRAPPEND" href="https://redis.io/docs/latest/commands/json.arrappend/">Append values to JSON array</Card>
-<Card title="JSON.ARRINDEX" href="https://redis.io/docs/latest/commands/json.arrindex/">Find index of value in array</Card>
-<Card title="JSON.ARRINSERT" href="https://redis.io/docs/latest/commands/json.arrinsert/">Insert values into JSON array</Card>
-<Card title="JSON.ARRLEN" href="https://redis.io/docs/latest/commands/json.arrlen/">Get JSON array length</Card>
-<Card title="JSON.ARRPOP" href="https://redis.io/docs/latest/commands/json.arrpop/">Pop value from JSON array</Card>
-<Card title="JSON.ARRTRIM" href="https://redis.io/docs/latest/commands/json.arrtrim/">Trim JSON array to range</Card>
-<Card title="JSON.CLEAR" href="https://redis.io/docs/latest/commands/json.clear/">Clear JSON values</Card>
-<Card title="JSON.DEL" href="https://redis.io/docs/latest/commands/json.del/">Delete JSON values</Card>
-<Card title="JSON.FORGET" href="https://redis.io/docs/latest/commands/json.forget/">Alias for JSON.DEL</Card>
-<Card title="JSON.GET" href="https://redis.io/docs/latest/commands/json.get/">Get JSON values</Card>
-<Card title="JSON.MERGE" href="https://redis.io/docs/latest/commands/json.merge/">Merge JSON values</Card>
-<Card title="JSON.MGET" href="https://redis.io/docs/latest/commands/json.mget/">Get values from multiple keys</Card>
-<Card title="JSON.MSET" href="https://redis.io/docs/latest/commands/json.mset/">Set values in multiple keys</Card>
-<Card title="JSON.NUMINCRBY" href="https://redis.io/docs/latest/commands/json.numincrby/">Increment JSON number</Card>
-<Card title="JSON.NUMMULTBY" href="https://redis.io/docs/latest/commands/json.nummultby/">Multiply JSON number</Card>
-<Card title="JSON.OBJKEYS" href="https://redis.io/docs/latest/commands/json.objkeys/">Get JSON object keys</Card>
-<Card title="JSON.OBJLEN" href="https://redis.io/docs/latest/commands/json.objlen/">Get JSON object size</Card>
-<Card title="JSON.RESP" href="https://redis.io/docs/latest/commands/json.resp/">Get JSON in RESP format</Card>
-<Card title="JSON.SET" href="https://redis.io/docs/latest/commands/json.set/">Set JSON value</Card>
-<Card title="JSON.STRAPPEND" href="https://redis.io/docs/latest/commands/json.strappend/">Append to JSON string</Card>
-<Card title="JSON.STRLEN" href="https://redis.io/docs/latest/commands/json.strlen/">Get JSON string length</Card>
-<Card title="JSON.TOGGLE" href="https://redis.io/docs/latest/commands/json.toggle/">Toggle JSON boolean</Card>
-<Card title="JSON.TYPE" href="https://redis.io/docs/latest/commands/json.type/">Get JSON value type</Card>
-</CardGroup>
-</Accordion>
-
-<Accordion title="List" icon="list">
-<CardGroup cols={2}>
-<Card title="BLMOVE" href="https://redis.io/docs/latest/commands/blmove/">Blocking list move</Card>
-<Card title="BLMPOP" href="https://redis.io/docs/latest/commands/blmpop/">Blocking pop from multiple lists</Card>
-<Card title="BLPOP" href="https://redis.io/docs/latest/commands/blpop/">Blocking left pop</Card>
-<Card title="BRPOP" href="https://redis.io/docs/latest/commands/brpop/">Blocking right pop</Card>
-<Card title="BRPOPLPUSH" href="https://redis.io/docs/latest/commands/brpoplpush/">Blocking pop and push</Card>
-<Card title="LINDEX" href="https://redis.io/docs/latest/commands/lindex/">Get element by index</Card>
-<Card title="LINSERT" href="https://redis.io/docs/latest/commands/linsert/">Insert before or after pivot</Card>
-<Card title="LLEN" href="https://redis.io/docs/latest/commands/llen/">Get list length</Card>
-<Card title="LMOVE" href="https://redis.io/docs/latest/commands/lmove/">Move element between lists</Card>
-<Card title="LMPOP" href="https://redis.io/docs/latest/commands/lmpop/">Pop from multiple lists</Card>
-<Card title="LPOP" href="https://redis.io/docs/latest/commands/lpop/">Pop from list head</Card>
-<Card title="LPOS" href="https://redis.io/docs/latest/commands/lpos/">Find element position</Card>
-<Card title="LPUSH" href="https://redis.io/docs/latest/commands/lpush/">Push to list head</Card>
-<Card title="LPUSHX" href="https://redis.io/docs/latest/commands/lpushx/">Push to head if list exists</Card>
-<Card title="LRANGE" href="https://redis.io/docs/latest/commands/lrange/">Get range of elements</Card>
-<Card title="LREM" href="https://redis.io/docs/latest/commands/lrem/">Remove elements by value</Card>
-<Card title="LSET" href="https://redis.io/docs/latest/commands/lset/">Set element at index</Card>
-<Card title="LTRIM" href="https://redis.io/docs/latest/commands/ltrim/">Trim list to range</Card>
-<Card title="RPOP" href="https://redis.io/docs/latest/commands/rpop/">Pop from list tail</Card>
-<Card title="RPOPLPUSH" href="https://redis.io/docs/latest/commands/rpoplpush/">Pop from tail and push to head</Card>
-<Card title="RPUSH" href="https://redis.io/docs/latest/commands/rpush/">Push to list tail</Card>
-<Card title="RPUSHX" href="https://redis.io/docs/latest/commands/rpushx/">Push to tail if list exists</Card>
-</CardGroup>
-</Accordion>
-
-<Accordion title="Pub/Sub" icon="tower-broadcast">
-<CardGroup cols={2}>
-<Card title="PSUBSCRIBE" href="https://redis.io/docs/latest/commands/psubscribe/">Subscribe to pattern channels</Card>
-<Card title="PUBLISH" href="https://redis.io/docs/latest/commands/publish/">Publish message to channel</Card>
-<Card title="PUBSUB" href="https://redis.io/docs/latest/commands/pubsub/">Inspect pub/sub state</Card>
-<Card title="PUNSUBSCRIBE" href="https://redis.io/docs/latest/commands/punsubscribe/">Unsubscribe from patterns</Card>
-<Card title="SUBSCRIBE" href="https://redis.io/docs/latest/commands/subscribe/">Subscribe to channels</Card>
-<Card title="UNSUBSCRIBE" href="https://redis.io/docs/latest/commands/unsubscribe/">Unsubscribe from channels</Card>
-</CardGroup>
-</Accordion>
-
-<Accordion title="Scripting" icon="scroll">
-<CardGroup cols={2}>
-<Card title="EVAL" href="https://redis.io/docs/latest/commands/eval/">Execute a Lua script</Card>
-<Card title="EVAL_RO" href="https://redis.io/docs/latest/commands/eval_ro/">Execute read-only Lua script</Card>
-<Card title="EVALSHA" href="https://redis.io/docs/latest/commands/evalsha/">Execute cached Lua script by SHA</Card>
-<Card title="EVALSHA_RO" href="https://redis.io/docs/latest/commands/evalsha_ro/">Read-only execute by SHA</Card>
-<Card title="SCRIPT EXISTS" href="https://redis.io/docs/latest/commands/script-exists/">Check if scripts exist in cache</Card>
-<Card title="SCRIPT FLUSH" href="https://redis.io/docs/latest/commands/script-flush/">Clear the script cache</Card>
-<Card title="SCRIPT LOAD" href="https://redis.io/docs/latest/commands/script-load/">Load script into cache</Card>
-</CardGroup>
-</Accordion>
-
-<Accordion title="Server" icon="server">
-<CardGroup cols={2}>
-<Card title="ACL" href="https://redis.io/docs/latest/commands/acl/">Manage access control list</Card>
-<Card title="DBSIZE" href="https://redis.io/docs/latest/commands/dbsize/">Get number of keys in database</Card>
-<Card title="FLUSHALL" href="https://redis.io/docs/latest/commands/flushall/">Delete all keys in all databases</Card>
-<Card title="FLUSHDB" href="https://redis.io/docs/latest/commands/flushdb/">Delete all keys in current database</Card>
-<Card title="MONITOR" href="https://redis.io/docs/latest/commands/monitor/">Stream all commands received</Card>
-<Card title="TIME" href="https://redis.io/docs/latest/commands/time/">Get current server time</Card>
-</CardGroup>
-</Accordion>
-
-<Accordion title="Set" icon="layer-group">
-<CardGroup cols={2}>
-<Card title="SADD" href="https://redis.io/docs/latest/commands/sadd/">Add members to a set</Card>
-<Card title="SCARD" href="https://redis.io/docs/latest/commands/scard/">Get set cardinality</Card>
-<Card title="SDIFF" href="https://redis.io/docs/latest/commands/sdiff/">Get set difference</Card>
-<Card title="SDIFFSTORE" href="https://redis.io/docs/latest/commands/sdiffstore/">Store set difference</Card>
-<Card title="SINTER" href="https://redis.io/docs/latest/commands/sinter/">Get set intersection</Card>
-<Card title="SINTERCARD" href="https://redis.io/docs/latest/commands/sintercard/">Get intersection cardinality</Card>
-<Card title="SINTERSTORE" href="https://redis.io/docs/latest/commands/sinterstore/">Store set intersection</Card>
-<Card title="SISMEMBER" href="https://redis.io/docs/latest/commands/sismember/">Check if member exists in set</Card>
-<Card title="SMEMBERS" href="https://redis.io/docs/latest/commands/smembers/">Get all set members</Card>
-<Card title="SMISMEMBER" href="https://redis.io/docs/latest/commands/smismember/">Check multiple members</Card>
-<Card title="SMOVE" href="https://redis.io/docs/latest/commands/smove/">Move member between sets</Card>
-<Card title="SPOP" href="https://redis.io/docs/latest/commands/spop/">Remove random members</Card>
-<Card title="SRANDMEMBER" href="https://redis.io/docs/latest/commands/srandmember/">Get random members</Card>
-<Card title="SREM" href="https://redis.io/docs/latest/commands/srem/">Remove members from a set</Card>
-<Card title="SSCAN" href="https://redis.io/docs/latest/commands/sscan/">Incrementally iterate set members</Card>
-<Card title="SUNION" href="https://redis.io/docs/latest/commands/sunion/">Get set union</Card>
-<Card title="SUNIONSTORE" href="https://redis.io/docs/latest/commands/sunionstore/">Store set union</Card>
-</CardGroup>
-</Accordion>
-
-<Accordion title="Sorted Set" icon="arrow-down-1-9">
-<CardGroup cols={2}>
-<Card title="BZMPOP" href="https://redis.io/docs/latest/commands/bzmpop/">Blocking pop from sorted sets</Card>
-<Card title="BZPOPMAX" href="https://redis.io/docs/latest/commands/bzpopmax/">Blocking pop max score member</Card>
-<Card title="BZPOPMIN" href="https://redis.io/docs/latest/commands/bzpopmin/">Blocking pop min score member</Card>
-<Card title="ZADD" href="https://redis.io/docs/latest/commands/zadd/">Add members with scores</Card>
-<Card title="ZCARD" href="https://redis.io/docs/latest/commands/zcard/">Get sorted set cardinality</Card>
-<Card title="ZCOUNT" href="https://redis.io/docs/latest/commands/zcount/">Count members in score range</Card>
-<Card title="ZDIFF" href="https://redis.io/docs/latest/commands/zdiff/">Get sorted set difference</Card>
-<Card title="ZDIFFSTORE" href="https://redis.io/docs/latest/commands/zdiffstore/">Store sorted set difference</Card>
-<Card title="ZINCRBY" href="https://redis.io/docs/latest/commands/zincrby/">Increment member's score</Card>
-<Card title="ZINTER" href="https://redis.io/docs/latest/commands/zinter/">Get sorted set intersection</Card>
-<Card title="ZINTERCARD" href="https://redis.io/docs/latest/commands/zintercard/">Get intersection cardinality</Card>
-<Card title="ZINTERSTORE" href="https://redis.io/docs/latest/commands/zinterstore/">Store sorted set intersection</Card>
-<Card title="ZLEXCOUNT" href="https://redis.io/docs/latest/commands/zlexcount/">Count members in lex range</Card>
-<Card title="ZMPOP" href="https://redis.io/docs/latest/commands/zmpop/">Pop members from sorted sets</Card>
-<Card title="ZMSCORE" href="https://redis.io/docs/latest/commands/zmscore/">Get scores of multiple members</Card>
-<Card title="ZPOPMAX" href="https://redis.io/docs/latest/commands/zpopmax/">Pop members with highest scores</Card>
-<Card title="ZPOPMIN" href="https://redis.io/docs/latest/commands/zpopmin/">Pop members with lowest scores</Card>
-<Card title="ZRANDMEMBER" href="https://redis.io/docs/latest/commands/zrandmember/">Get random members</Card>
-<Card title="ZRANGE" href="https://redis.io/docs/latest/commands/zrange/">Get members by index range</Card>
-<Card title="ZRANGEBYLEX" href="https://redis.io/docs/latest/commands/zrangebylex/">Get members by lex range</Card>
-<Card title="ZRANGEBYSCORE" href="https://redis.io/docs/latest/commands/zrangebyscore/">Get members by score range</Card>
-<Card title="ZRANGESTORE" href="https://redis.io/docs/latest/commands/zrangestore/">Store range result</Card>
-<Card title="ZRANK" href="https://redis.io/docs/latest/commands/zrank/">Get member's rank</Card>
-<Card title="ZREM" href="https://redis.io/docs/latest/commands/zrem/">Remove members</Card>
-<Card title="ZREMRANGEBYLEX" href="https://redis.io/docs/latest/commands/zremrangebylex/">Remove members by lex range</Card>
-<Card title="ZREMRANGEBYRANK" href="https://redis.io/docs/latest/commands/zremrangebyrank/">Remove members by rank range</Card>
-<Card title="ZREMRANGEBYSCORE" href="https://redis.io/docs/latest/commands/zremrangebyscore/">Remove members by score range</Card>
-<Card title="ZREVRANGE" href="https://redis.io/docs/latest/commands/zrevrange/">Get members in reverse order</Card>
-<Card title="ZREVRANGEBYLEX" href="https://redis.io/docs/latest/commands/zrevrangebylex/">Reverse lex range query</Card>
-<Card title="ZREVRANGEBYSCORE" href="https://redis.io/docs/latest/commands/zrevrangebyscore/">Reverse score range query</Card>
-<Card title="ZREVRANK" href="https://redis.io/docs/latest/commands/zrevrank/">Get member's reverse rank</Card>
-<Card title="ZSCAN" href="https://redis.io/docs/latest/commands/zscan/">Incrementally iterate sorted set</Card>
-<Card title="ZSCORE" href="https://redis.io/docs/latest/commands/zscore/">Get member's score</Card>
-<Card title="ZUNION" href="https://redis.io/docs/latest/commands/zunion/">Get sorted set union</Card>
-<Card title="ZUNIONSTORE" href="https://redis.io/docs/latest/commands/zunionstore/">Store sorted set union</Card>
-</CardGroup>
-</Accordion>
-
-<Accordion title="Streams" icon="water">
-<CardGroup cols={2}>
-<Card title="XACK" href="https://redis.io/docs/latest/commands/xack/">Acknowledge stream messages</Card>
-<Card title="XACKDEL" href="https://redis.io/docs/latest/commands/xackdel/">Acknowledge and delete messages</Card>
-<Card title="XADD" href="https://redis.io/docs/latest/commands/xadd/">Add entry to stream</Card>
-<Card title="XAUTOCLAIM" href="https://redis.io/docs/latest/commands/xautoclaim/">Auto-claim idle messages</Card>
-<Card title="XCLAIM" href="https://redis.io/docs/latest/commands/xclaim/">Claim pending messages</Card>
-<Card title="XDEL" href="https://redis.io/docs/latest/commands/xdel/">Delete stream entries</Card>
-<Card title="XDELEX" href="https://redis.io/docs/latest/commands/xdelex/">Delete entries with expiration</Card>
-<Card title="XGROUP" href="https://redis.io/docs/latest/commands/xgroup/">Manage consumer groups</Card>
-<Card title="XINFO CONSUMERS" href="https://redis.io/docs/latest/commands/xinfo-consumers/">List group consumers</Card>
-<Card title="XINFO GROUPS" href="https://redis.io/docs/latest/commands/xinfo-groups/">List stream groups</Card>
-<Card title="XINFO STREAM" href="https://redis.io/docs/latest/commands/xinfo-stream/">Get stream info</Card>
-<Card title="XLEN" href="https://redis.io/docs/latest/commands/xlen/">Get stream length</Card>
-<Card title="XPENDING" href="https://redis.io/docs/latest/commands/xpending/">Get pending messages info</Card>
-<Card title="XRANGE" href="https://redis.io/docs/latest/commands/xrange/">Get range of stream entries</Card>
-<Card title="XREAD" href="https://redis.io/docs/latest/commands/xread/">Read stream entries</Card>
-<Card title="XREADGROUP" href="https://redis.io/docs/latest/commands/xreadgroup/">Read as consumer group</Card>
-<Card title="XREVRANGE" href="https://redis.io/docs/latest/commands/xrevrange/">Get range in reverse order</Card>
-<Card title="XTRIM" href="https://redis.io/docs/latest/commands/xtrim/">Trim stream to max length</Card>
-</CardGroup>
-</Accordion>
-
-<Accordion title="String" icon="font">
-<CardGroup cols={2}>
-<Card title="APPEND" href="https://redis.io/docs/latest/commands/append/">Append value to a string</Card>
-<Card title="DECR" href="https://redis.io/docs/latest/commands/decr/">Decrement integer value by 1</Card>
-<Card title="DECRBY" href="https://redis.io/docs/latest/commands/decrby/">Decrement integer by amount</Card>
-<Card title="GET" href="https://redis.io/docs/latest/commands/get/">Get string value</Card>
-<Card title="GETDEL" href="https://redis.io/docs/latest/commands/getdel/">Get value and delete key</Card>
-<Card title="GETEX" href="https://redis.io/docs/latest/commands/getex/">Get value and set expiration</Card>
-<Card title="GETRANGE" href="https://redis.io/docs/latest/commands/getrange/">Get substring of string</Card>
-<Card title="GETSET" href="https://redis.io/docs/latest/commands/getset/">Set value and return old value</Card>
-<Card title="INCR" href="https://redis.io/docs/latest/commands/incr/">Increment integer value by 1</Card>
-<Card title="INCRBY" href="https://redis.io/docs/latest/commands/incrby/">Increment integer by amount</Card>
-<Card title="INCRBYFLOAT" href="https://redis.io/docs/latest/commands/incrbyfloat/">Increment float by amount</Card>
-<Card title="MGET" href="https://redis.io/docs/latest/commands/mget/">Get values of multiple keys</Card>
-<Card title="MSET" href="https://redis.io/docs/latest/commands/mset/">Set multiple keys at once</Card>
-<Card title="MSETNX" href="https://redis.io/docs/latest/commands/msetnx/">Set multiple keys if none exist</Card>
-<Card title="PSETEX" href="https://redis.io/docs/latest/commands/psetex/">Set value with ms expiration</Card>
-<Card title="SET" href="https://redis.io/docs/latest/commands/set/">Set string value</Card>
-<Card title="SETEX" href="https://redis.io/docs/latest/commands/setex/">Set value with expiration</Card>
-<Card title="SETNX" href="https://redis.io/docs/latest/commands/setnx/">Set value if key doesn't exist</Card>
-<Card title="SETRANGE" href="https://redis.io/docs/latest/commands/setrange/">Overwrite part of string</Card>
-<Card title="STRLEN" href="https://redis.io/docs/latest/commands/strlen/">Get string length</Card>
-</CardGroup>
-</Accordion>
-
-<Accordion title="Transactions" icon="right-left">
-<CardGroup cols={2}>
-<Card title="DISCARD" href="https://redis.io/docs/latest/commands/discard/">Discard queued commands</Card>
-<Card title="EXEC" href="https://redis.io/docs/latest/commands/exec/">Execute queued commands</Card>
-<Card title="MULTI" href="https://redis.io/docs/latest/commands/multi/">Start a transaction</Card>
-<Card title="UNWATCH" href="https://redis.io/docs/latest/commands/unwatch/">Unwatch all keys</Card>
-<Card title="WATCH" href="https://redis.io/docs/latest/commands/watch/">Watch keys for changes</Card>
-</CardGroup>
-</Accordion>
-
-</AccordionGroup>
-
----
-
-We run command integration tests from the following Redis clients after each code change and also periodically:
+SDK command references may cover a smaller set of typed helpers.
+For example, see the [TypeScript SDK command reference](/redis/sdks/ts/commands/overview) for the commands documented in `@upstash/redis`.
 
-- **[Node-Redis](https://github.com/redis/node-redis)**
-- **[Jedis](https://github.com/redis/jedis)**
-- **[Lettuce](https://github.com/lettuce-io/lettuce-core)**
-- **[Go-Redis](https://github.com/go-redis/redis)**
-- **[Redis-py](https://github.com/redis/redis-py)**
+Most unsupported items are on our roadmap. If you need a feature that we do not support, email [support@upstash.com](mailto:support@upstash.com) so we can let you know when we plan to support it.
diff --git a/redis/search/aggregation-operators/bucket-aggregations/terms.mdx b/redis/search/aggregation-operators/bucket-aggregations/terms.mdx
index 5ad61c859..3ed3ca471 100644
--- a/redis/search/aggregation-operators/bucket-aggregations/terms.mdx
+++ b/redis/search/aggregation-operators/bucket-aggregations/terms.mdx
@@ -89,4 +89,4 @@ SEARCH.AGGREGATE products '{}' '{"by_category": {"$terms": {"field": "category",
 `$terms` bucket counts are **approximate**. Terms are tallied per index segment and then merged, so a term's `docCount` can be slightly off, especially for terms near the `size` cutoff.
 </Warning>
 
-`docCountErrorUpperBound` reports the maximum possible error on the returned counts (set `showTermDocCountError: true` for per-bucket values), and `sumOtherDocCount` is the number of matching documents not included in the returned buckets. Raising `segmentSize` reduces the error at the cost of more work per query. For an exact count of a specific term, use [`SEARCH.COUNT`](/redis/search/command-reference#searchcount) instead of reading it from a bucket.
+`docCountErrorUpperBound` reports the maximum possible error on the returned counts (set `showTermDocCountError: true` for per-bucket values), and `sumOtherDocCount` is the number of matching documents not included in the returned buckets. Raising `segmentSize` reduces the error at the cost of more work per query. For an exact count of a specific term, use [`SEARCH.COUNT`](/redis/commands/search/search-count) instead of reading it from a bucket.
diff --git a/redis/search/aggregations.mdx b/redis/search/aggregations.mdx
index 7d1c7da39..fab1b3abe 100644
--- a/redis/search/aggregations.mdx
+++ b/redis/search/aggregations.mdx
@@ -5,6 +5,8 @@ title: Aggregations
 Aggregations let you compute analytics over your indexed data — metrics like averages, sums, and statistics,
 as well as bucket-based groupings like terms, ranges, and histograms.
 
+Use the [`SEARCH.AGGREGATE`](/redis/commands/search/search-aggregate) command to run aggregations.
+
 They are useful when you want to answer questions like:
 
 - "What is the average price?"
diff --git a/redis/search/aliases.mdx b/redis/search/aliases.mdx
index d4758b8a5..91c5b6f24 100644
--- a/redis/search/aliases.mdx
+++ b/redis/search/aliases.mdx
@@ -8,7 +8,7 @@ Aliases let you create alternative names for your search indices. This is useful
 
 ### Adding an Alias
 
-The `SEARCH.ALIASADD` command creates a new alias or updates an existing alias to point to a different index.
+The [`SEARCH.ALIASADD`](/redis/commands/search/search-aliasadd) command creates a new alias or updates an existing alias to point to a different index.
 
 Returns `1` if a new alias was created, or `2` if an existing alias was updated to point to a new index.
 
@@ -119,7 +119,7 @@ SEARCH.DROP products-v1
 
 ### Deleting an Alias
 
-The `SEARCH.ALIASDEL` command removes an alias.
+The [`SEARCH.ALIASDEL`](/redis/commands/search/search-aliasdel) command removes an alias.
 
 Returns `1` if the alias was deleted, or `0` if the alias was not found.
 
@@ -149,7 +149,7 @@ SEARCH.ALIASDEL products
 
 ### Listing Aliases
 
-The `SEARCH.LISTALIASES` command returns all aliases and the indices they point to.
+The [`SEARCH.LISTALIASES`](/redis/commands/search/search-listaliases) command returns all aliases and the indices they point to.
 
 <Tabs>
 
diff --git a/redis/search/command-reference.mdx b/redis/search/command-reference.mdx
index 80f8799dd..6a4f4b08b 100644
--- a/redis/search/command-reference.mdx
+++ b/redis/search/command-reference.mdx
@@ -1,320 +1,12 @@
 ---
-title: Command Reference
+title: "Command Reference"
+description: "Browse the commands supported by Upstash Redis Search."
 ---
 
-A complete reference of all Upstash Redis Search commands, their syntax, and return values.
-
 <Note>
-Upstash Redis Search uses `SEARCH.*` commands. These are **not** the same as the `FT.*` commands
-from the open-source RediSearch module. The two are completely separate implementations and are
-not compatible with each other.
+  Upstash Redis Search uses `SEARCH.*` commands. They are separate from and incompatible with the `FT.*` commands in the open-source RediSearch module.
 </Note>
 
-## Index Commands
-
-### SEARCH.CREATE
-
-Creates a new search index.
-
-```bash
-SEARCH.CREATE <name> ON <JSON|HASH|STRING>
-  PREFIX <count> <prefix> [<prefix> ...]
-  [LANGUAGE <language>]
-  [SKIPINITIALSCAN]
-  [EXISTSOK]
-  SCHEMA <field> <type> [FAST] [NOSTEM] [NOTOKENIZE] [FROM <source_field>] ...
-```
-
-**Returns:** `1` on success. With `EXISTSOK`, returns `0` if an identical index already exists. Returns an error if the existing index has a different configuration.
-
-<Tabs>
-<Tab title="Redis CLI">
-```bash
-SEARCH.CREATE products ON JSON PREFIX 1 product: SCHEMA name TEXT price F64 FAST inStock BOOL
-```
-</Tab>
-<Tab title="curl">
-```bash
-curl -X POST https://YOUR_ENDPOINT.upstash.io \
-  -H "Authorization: Bearer $UPSTASH_REDIS_REST_TOKEN" \
-  -d '["SEARCH.CREATE", "products", "ON", "JSON", "PREFIX", "1", "product:", "SCHEMA", "name", "TEXT", "price", "F64", "FAST", "inStock", "BOOL"]'
-```
-</Tab>
-</Tabs>
-
----
-
-### SEARCH.DROP
-
-Removes an index. The underlying Redis keys are **not** deleted.
-
-```bash
-SEARCH.DROP <name>
-```
-
-**Returns:** `1` if dropped, `0` if the index was not found.
-
----
-
-### SEARCH.DESCRIBE
-
-Returns metadata about an index.
-
-```bash
-SEARCH.DESCRIBE <name>
-```
-
-**Returns:** Index metadata including name, data type, prefixes, language, and schema definition. Returns `null` if the index does not exist.
-
----
-
-### SEARCH.WAITINDEXING
-
-Blocks until all pending index updates are processed and visible to queries.
-
-```bash
-SEARCH.WAITINDEXING <name>
-```
-
-**Returns:** `1` when indexing is complete, `0` if the index was not found.
-
-<Warning>
-Do not call `SEARCH.WAITINDEXING` after every write. Batch updates are necessary for
-optimal indexing performance. Use this command only when you need to ensure queries
-reflect recent changes, such as in tests or CI pipelines.
-</Warning>
-
----
-
-### SEARCH.LISTINDEXES
-
-Lists all search indexes in the database.
-
-```bash
-SEARCH.LISTINDEXES [MATCH <pattern>] [LIMIT <count>] [OFFSET <offset>]
-```
-
-**Parameters:**
-
-| Parameter | Description | Default |
-|-----------|-------------|---------|
-| `MATCH` | Filter index names by a glob-style pattern (e.g. `h*`). | All indexes |
-| `LIMIT` | Maximum number of indexes to return. | All indexes |
-| `OFFSET` | Number of indexes to skip (for pagination). | 0 |
-
-**Returns:** One entry per index, each a map of `name` and the backing `type` (`HASH` or `JSON`).
-
-**Response format (Redis CLI):**
-
-```
-[
-  ["name", "productIdx", "type", "HASH"],
-  ["name", "blogIdx", "type", "JSON"]
-]
-```
-
-<Tabs>
-<Tab title="Redis CLI">
-```bash
-SEARCH.LISTINDEXES MATCH 'product*' LIMIT 10 OFFSET 0
-```
-</Tab>
-<Tab title="curl">
-```bash
-curl -X POST https://YOUR_ENDPOINT.upstash.io \
-  -H "Authorization: Bearer $UPSTASH_REDIS_REST_TOKEN" \
-  -d '["SEARCH.LISTINDEXES", "MATCH", "product*", "LIMIT", "10", "OFFSET", "0"]'
-```
-</Tab>
-</Tabs>
-
----
-
-## Query Commands
-
-### SEARCH.QUERY
-
-Searches for documents matching a JSON filter.
-
-```bash
-SEARCH.QUERY <name> '<json_filter>'
-  [LIMIT <count>]
-  [OFFSET <offset>]
-  [ORDERBY <field> <ASC|DESC>]
-  [SELECT <count> <field> [<field> ...]]
-  [NOCONTENT]
-  [HIGHLIGHT FIELDS <count> <field> [<field> ...] [TAGS <open> <close>]]
-  [SCOREFUNC ...]
-```
-
-**Parameters:**
-
-| Parameter | Description | Default |
-|-----------|-------------|---------|
-| `LIMIT` | Maximum number of results to return. Must be between 1 and 1000. | 10 |
-| `OFFSET` | Number of results to skip (for pagination). | 0 |
-| `ORDERBY` | Sort by a FAST field in `ASC` or `DESC` order. | Sort by relevance score (descending) |
-| `SELECT` | Return only specific fields. Prefix with count of fields. | All fields |
-| `NOCONTENT` | Return only keys and scores, no document content. | Disabled |
-| `HIGHLIGHT` | Wrap matching terms in tags. Default tags: `<em>` / `</em>`. | Disabled |
-| `SCOREFUNC` | Adjust relevance scores using numeric field values. | Disabled |
-
-**Response format (Redis CLI):**
-
-```
-[
-  ["key1", "score1", [["$", "{\"name\": \"...\", ...}"]]],
-  ["key2", "score2", [["$", "{\"name\": \"...\", ...}"]]]
-]
-```
-
-Each result is an array of `[key, score, content]` where:
-- `key` — the Redis key of the matching document
-- `score` — relevance score (float)
-- `content` — array of field-value pairs (for JSON indexes: `[["$", "<json_string>"]]`; for HASH indexes: `[["field", "value"], ...]`)
-
-When `NOCONTENT` is used, the content element is omitted.
-When `SELECT` is used, only the selected fields appear in the content.
-
-<Tabs>
-<Tab title="Redis CLI">
-```bash
-SEARCH.QUERY products '{"name": "wireless"}' LIMIT 10 OFFSET 0
-```
-</Tab>
-<Tab title="curl">
-```bash
-curl -X POST https://YOUR_ENDPOINT.upstash.io \
-  -H "Authorization: Bearer $UPSTASH_REDIS_REST_TOKEN" \
-  -d '["SEARCH.QUERY", "products", "{\"name\": \"wireless\"}", "LIMIT", "10", "OFFSET", "0"]'
-```
-</Tab>
-</Tabs>
-
----
-
-### SEARCH.COUNT
-
-Returns the number of documents matching a query without retrieving them.
-
-```bash
-SEARCH.COUNT <name> '<json_filter>'
-```
-
-**Returns:** An integer — the count of matching documents.
-
-<Tabs>
-<Tab title="Redis CLI">
-```bash
-SEARCH.COUNT products '{"inStock": true}'
-```
-</Tab>
-<Tab title="curl">
-```bash
-curl -X POST https://YOUR_ENDPOINT.upstash.io \
-  -H "Authorization: Bearer $UPSTASH_REDIS_REST_TOKEN" \
-  -d '["SEARCH.COUNT", "products", "{\"inStock\": true}"]'
-```
-</Tab>
-</Tabs>
-
----
-
-### SEARCH.AGGREGATE
-
-Computes analytics (metrics and buckets) over matching documents.
-
-```bash
-SEARCH.AGGREGATE <name> '<json_filter>' '<json_aggregations>'
-```
-
-**Response format (Redis CLI):**
-
-In `redis-cli --json`, the response is an object keyed by alias:
-
-```json
-{
-  "avg_price": { "value": 49.99 },
-  "by_category": { "buckets": [{ "key": "electronics", "docCount": 42 }] }
-}
-```
-
-Raw RESP output may be rendered differently by client/protocol settings, but semantically each top-level alias maps to its aggregation result.
-
-<Tabs>
-<Tab title="Redis CLI">
-```bash
-SEARCH.AGGREGATE products '{}' '{"avg_price": {"$avg": {"field": "price"}}}'
-```
-</Tab>
-<Tab title="curl">
-```bash
-curl -X POST https://YOUR_ENDPOINT.upstash.io \
-  -H "Authorization: Bearer $UPSTASH_REDIS_REST_TOKEN" \
-  -d '["SEARCH.AGGREGATE", "products", "{}", "{\"avg_price\": {\"$avg\": {\"field\": \"price\"}}}"]'
-```
-</Tab>
-</Tabs>
-
----
-
-## Alias Commands
-
-### SEARCH.ALIASADD
-
-Creates or updates an alias pointing to an index.
-
-```bash
-SEARCH.ALIASADD <alias> <index_name>
-```
-
-**Returns:** `1` if a new alias was created, `2` if an existing alias was updated.
-
----
-
-### SEARCH.ALIASDEL
-
-Removes an alias.
-
-```bash
-SEARCH.ALIASDEL <alias>
-```
-
-**Returns:** `1` if deleted, `0` if the alias was not found.
-
----
-
-### SEARCH.LISTALIASES
-
-Returns all aliases and the indices they point to.
-
-```bash
-SEARCH.LISTALIASES
-```
-
-**Returns:** An array of `[alias, index_name]` pairs, or an empty array if no aliases exist. To list every index in the database, use [`SEARCH.LISTINDEXES`](#searchlistindexes).
-
----
-
-## REST API Usage
-
-All search commands can be sent via the Upstash REST API using a JSON array POST body.
-Each element of the array corresponds to a token in the command.
-
-```bash
-curl -X POST https://YOUR_ENDPOINT.upstash.io \
-  -H "Authorization: Bearer $UPSTASH_REDIS_REST_TOKEN" \
-  -d '["COMMAND", "arg1", "arg2", ...]'
-```
-
-The JSON filter and aggregation arguments are passed as string values within the array (not as nested JSON objects):
-
-```bash
-# Correct — filter is a string inside the array
-["SEARCH.QUERY", "products", "{\"name\": \"wireless\"}", "LIMIT", "10"]
-
-# Incorrect — filter is a nested object
-["SEARCH.QUERY", "products", {"name": "wireless"}, "LIMIT", "10"]
-```
-
-Search commands also work through the `/pipeline` endpoint for batching multiple commands in a single HTTP request.
+<Card title="Browse Search commands" icon="magnifying-glass" href="/redis/commands/search/overview" horizontal>
+  View the complete Upstash Redis Search command reference.
+</Card>
diff --git a/redis/search/counting.mdx b/redis/search/counting.mdx
index add892cde..a6c353ac3 100644
--- a/redis/search/counting.mdx
+++ b/redis/search/counting.mdx
@@ -2,7 +2,7 @@
 title: Counting
 ---
 
-The `SEARCH.COUNT` command returns the number of documents matching a query without retrieving them.
+The [`SEARCH.COUNT`](/redis/commands/search/search-count) command returns the number of documents matching a query without retrieving them.
 
 You can use `SEARCH.COUNT` for analytics, pagination UI (showing "X results found"),
 or validating queries before retrieving results.
diff --git a/redis/search/document-updates.mdx b/redis/search/document-updates.mdx
index 1e788bb94..f925d5e4c 100644
--- a/redis/search/document-updates.mdx
+++ b/redis/search/document-updates.mdx
@@ -20,7 +20,7 @@ Any command that modifies a matching key updates the index. For example, this in
 This is not an exhaustive list. The rule is that if the command changes a key tracked by the index, the index is updated.
 
 Index updates are batched for performance, so recent writes may not immediately appear in search results.
-Use [`SEARCH.WAITINDEXING`](/redis/search/index-management#waiting-for-indexing) when you need to ensure queries reflect recent changes.
+Use [`SEARCH.WAITINDEXING`](/redis/commands/search/search-waitindexing) when you need to ensure queries reflect recent changes.
 
 ## JSON Documents
 
diff --git a/redis/search/index-management.mdx b/redis/search/index-management.mdx
index aad1fa9ae..d74461a33 100644
--- a/redis/search/index-management.mdx
+++ b/redis/search/index-management.mdx
@@ -16,7 +16,7 @@ You define an index once by specifying:
 
 ### Creating an Index
 
-An index is identified by its name, which must be a unique key in Redis. Each index works with a single key type (JSON, hash, or string).
+The [`SEARCH.CREATE`](/redis/commands/search/search-create) command creates an index identified by a name, which must be a unique key in Redis. Each index works with a single key type (JSON, hash, or string).
 
 <Tabs>
 
@@ -193,7 +193,8 @@ SEARCH.CREATE comments ON STRING PREFIX 1 comment: SCHEMA user.name TEXT user.em
 
 By default, when an index is created, all existing keys matching the specified type and prefixes are scanned and indexed.
 Use `SKIPINITIALSCAN` to defer indexing, which is useful for large datasets where you want to start fresh or handle
-existing data differently.
+existing data differently. Run [`SEARCH.REINDEX`](/redis/commands/search/search-reindex) later to rebuild the index from
+the current matching keys.
 
 <Tabs>
 
@@ -420,7 +421,7 @@ Use `redis.search.createIndex()` when:
 
 ### Describing an Index
 
-The `SEARCH.DESCRIBE` command returns detailed information about an index, or `null` if the index doesn't exist.
+The [`SEARCH.DESCRIBE`](/redis/commands/search/search-describe) command returns detailed information about an index, or `null` if the index doesn't exist.
 
 <Tabs>
 
@@ -460,7 +461,7 @@ On response, the following information is returned:
 
 ### Listing Indexes
 
-`SEARCH.LISTINDEXES` lists all search indexes in the database, reporting each index's `name` and backing `type` (`HASH` or `JSON`). Optionally filter names with `MATCH` and paginate with `LIMIT` and `OFFSET`.
+[`SEARCH.LISTINDEXES`](/redis/commands/search/search-listindexes) lists all search indexes in the database, reporting each index's `name` and backing `type` (`HASH` or `JSON`). Optionally filter names with `MATCH` and paginate with `LIMIT` and `OFFSET`.
 
 <Tabs>
 
@@ -477,7 +478,7 @@ SEARCH.LISTINDEXES MATCH 'product*' LIMIT 10 OFFSET 0
 
 ### Dropping an Index
 
-The `SEARCH.DROP` command removes an index and stops tracking associated keys.
+The [`SEARCH.DROP`](/redis/commands/search/search-drop) command removes an index and stops tracking associated keys.
 
 Returns `1` if the index was dropped, or `0` if the index was not found.
 
@@ -510,7 +511,7 @@ Note that, dropping an index only removes the search index. The underlying Redis
 ### Waiting for Indexing
 
 For adequate performance, index updates are batched and committed periodically. This means recent writes may not
-immediately appear in search results. Use `SEARCH.WAITINDEXING` when you need to ensure queries reflect recent changes.
+immediately appear in search results. Use [`SEARCH.WAITINDEXING`](/redis/commands/search/search-waitindexing) when you need to ensure queries reflect recent changes.
 
 The `SEARCH.WAITINDEXING` command blocks until all pending index updates are processed and visible to queries.
 For examples of changing, deleting, and expiring indexed documents, see [Document Updates](/redis/search/document-updates).
diff --git a/redis/search/querying.mdx b/redis/search/querying.mdx
index 7b0f923de..1681dc17d 100644
--- a/redis/search/querying.mdx
+++ b/redis/search/querying.mdx
@@ -4,6 +4,8 @@ title: Queries
 
 Queries are JSON strings that describe which documents to return. If the index doesn't exist, queries return `null`.
 
+Use the [`SEARCH.QUERY`](/redis/commands/search/search-query) command to run a query.
+
 We recommend searching by field values directly because we automatically provide intelligent matching behavior out of the box:
 
 <Tabs>
@@ -107,7 +109,7 @@ When `select` / `NOCONTENT` is used, the response shape changes — see [Control
 
 If no documents match, an empty array is returned. If the index doesn't exist, `null` is returned.
 
-For a detailed breakdown of the raw response structure, see the [Command Reference](/redis/search/command-reference#searchquery).
+For exact syntax and a detailed breakdown of the raw response structure, see the [`SEARCH.QUERY` command reference](/redis/commands/search/search-query).
 
 ---
 
diff --git a/redis/search/schema-definition.mdx b/redis/search/schema-definition.mdx
index b5bf2faec..0bdf84553 100644
--- a/redis/search/schema-definition.mdx
+++ b/redis/search/schema-definition.mdx
@@ -93,6 +93,8 @@ const schema = s.object({
 
 We need the schema when creating or querying an index:
 
+For the complete index creation syntax, see [`SEARCH.CREATE`](/redis/commands/search/search-create).
+
 ```ts
 import { Redis, s } from "@upstash/redis"
 

From 820fb21ab12556e994bf135cb227b25e48f60dd2 Mon Sep 17 00:00:00 2001
From: "github-actions[bot]"
 <41898282+github-actions[bot]@users.noreply.github.com>
Date: Wed, 12 Aug 2026 18:36:36 +0000
Subject: [PATCH 02/12] chore(llms): regenerate llms.txt and llms-full.txt

---
 llms-full.txt | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/llms-full.txt b/llms-full.txt
index 1521fac42..47a2af7a1 100644
--- a/llms-full.txt
+++ b/llms-full.txt
@@ -10142,7 +10142,7 @@ To view a more detailed Next.js quick start guide for setting up QStash, refer t
 
 It's also possible to schedule a background job to run at a later time using [schedules](/docs/qstash/features/schedules).
 
-If you'd like to invoke another endpoint when the background job is complete, you can use [callbacks](/docs/qstash/features/callbacks).
+If you'd like to invoke another endpoint when the background job is complete, you can use [callbacks](/docs/qstash/features/callbacks).
 
 # Batching
 Source: https://upstash.com/docs/qstash/features/batch
@@ -10441,7 +10441,7 @@ client.message.batch_json(
     "messageId": "msg_..."
   }
 ]
-```
+```
 
 # Callbacks
 Source: https://upstash.com/docs/qstash/features/callbacks
@@ -11496,7 +11496,7 @@ from qstash import QStash
 client = QStash("<QSTASH_TOKEN>")
 client.queue.get("my-queue")
 ```
-</CodeGroup>
+</CodeGroup>
 
 # Retry
 Source: https://upstash.com/docs/qstash/features/retry

From 3d8f5a6ddd20f3119d0174343db164f671592e25 Mon Sep 17 00:00:00 2001
From: Mehmet Dogan <mehmet@dogan.io>
Date: Thu, 13 Aug 2026 09:22:14 +0300
Subject: [PATCH 03/12] more improvements

---
 llms-full.txt                                 | 1512 +++++++++++++----
 llms.txt                                      |   22 +-
 redis/commands/bitmap/bitcount.mdx            |    6 +-
 redis/commands/bitmap/bitfield-ro.mdx         |    2 +
 redis/commands/bitmap/bitfield.mdx            |   10 +-
 redis/commands/bitmap/bitop.mdx               |   10 +-
 redis/commands/bitmap/bitpos.mdx              |    6 +-
 redis/commands/bitmap/getbit.mdx              |    4 +-
 redis/commands/bitmap/setbit.mdx              |    6 +-
 redis/commands/connection/auth.mdx            |    4 +-
 redis/commands/connection/client-getname.mdx  |    4 +-
 redis/commands/connection/client-id.mdx       |    4 +-
 redis/commands/connection/client-info.mdx     |    4 +-
 redis/commands/connection/client-list.mdx     |    4 +-
 redis/commands/connection/client-setinfo.mdx  |    4 +-
 redis/commands/connection/client-setname.mdx  |    4 +-
 redis/commands/connection/echo.mdx            |    4 +-
 redis/commands/connection/hello.mdx           |    6 +-
 redis/commands/connection/ping.mdx            |    4 +-
 redis/commands/connection/quit.mdx            |    4 +-
 redis/commands/connection/reset.mdx           |    4 +-
 redis/commands/connection/select.mdx          |    4 +-
 redis/commands/functions/fcall-ro.mdx         |    6 +-
 redis/commands/functions/fcall.mdx            |    6 +-
 redis/commands/functions/function-delete.mdx  |    4 +-
 redis/commands/functions/function-flush.mdx   |    4 +-
 redis/commands/functions/function-kill.mdx    |    6 +-
 redis/commands/functions/function-list.mdx    |    4 +-
 redis/commands/functions/function-load.mdx    |    6 +-
 redis/commands/functions/function-stats.mdx   |    4 +-
 redis/commands/generic/copy.mdx               |    6 +-
 redis/commands/generic/del.mdx                |    4 +-
 redis/commands/generic/dump.mdx               |    6 +-
 redis/commands/generic/exists.mdx             |    4 +-
 redis/commands/generic/expire.mdx             |    8 +-
 redis/commands/generic/expireat.mdx           |    6 +-
 redis/commands/generic/expiretime.mdx         |    4 +-
 redis/commands/generic/keys.mdx               |    6 +-
 redis/commands/generic/memory-usage.mdx       |    6 +-
 redis/commands/generic/persist.mdx            |    4 +-
 redis/commands/generic/pexpire.mdx            |    6 +-
 redis/commands/generic/pexpireat.mdx          |    6 +-
 redis/commands/generic/pexpiretime.mdx        |    4 +-
 redis/commands/generic/pttl.mdx               |    4 +-
 redis/commands/generic/randomkey.mdx          |    4 +-
 redis/commands/generic/rename.mdx             |    6 +-
 redis/commands/generic/renamenx.mdx           |    4 +-
 redis/commands/generic/restore.mdx            |    6 +-
 redis/commands/generic/scan.mdx               |    8 +-
 redis/commands/generic/touch.mdx              |    4 +-
 redis/commands/generic/ttl.mdx                |    4 +-
 redis/commands/generic/type.mdx               |    4 +-
 redis/commands/generic/unlink.mdx             |    4 +-
 redis/commands/generic/wait.mdx               |    8 +-
 redis/commands/generic/waitaof.mdx            |    6 +-
 redis/commands/geo/geoadd.mdx                 |    6 +-
 redis/commands/geo/geodist.mdx                |    6 +-
 redis/commands/geo/geohash.mdx                |    4 +-
 redis/commands/geo/geopos.mdx                 |    4 +-
 redis/commands/geo/georadius-ro.mdx           |   10 +-
 redis/commands/geo/georadius.mdx              |   16 +-
 redis/commands/geo/georadiusbymember-ro.mdx   |   10 +-
 redis/commands/geo/georadiusbymember.mdx      |   14 +-
 redis/commands/geo/geosearch.mdx              |   14 +-
 redis/commands/geo/geosearchstore.mdx         |   12 +-
 redis/commands/geo/overview.mdx               |    4 +-
 redis/commands/hash/hdel.mdx                  |    4 +-
 redis/commands/hash/hexists.mdx               |    4 +-
 redis/commands/hash/hexpire.mdx               |    8 +-
 redis/commands/hash/hexpireat.mdx             |    8 +-
 redis/commands/hash/hexpiretime.mdx           |    4 +-
 redis/commands/hash/hget.mdx                  |    4 +-
 redis/commands/hash/hgetall.mdx               |    6 +-
 redis/commands/hash/hgetdel.mdx               |    6 +-
 redis/commands/hash/hgetex.mdx                |    8 +-
 redis/commands/hash/hincrby.mdx               |    6 +-
 redis/commands/hash/hincrbyfloat.mdx          |    6 +-
 redis/commands/hash/hkeys.mdx                 |    4 +-
 redis/commands/hash/hlen.mdx                  |    4 +-
 redis/commands/hash/hmget.mdx                 |    6 +-
 redis/commands/hash/hmset.mdx                 |    4 +-
 redis/commands/hash/hpersist.mdx              |    6 +-
 redis/commands/hash/hpexpire.mdx              |    6 +-
 redis/commands/hash/hpexpireat.mdx            |    6 +-
 redis/commands/hash/hpexpiretime.mdx          |    4 +-
 redis/commands/hash/hpttl.mdx                 |    4 +-
 redis/commands/hash/hrandfield.mdx            |    6 +-
 redis/commands/hash/hscan.mdx                 |    6 +-
 redis/commands/hash/hset.mdx                  |    6 +-
 redis/commands/hash/hsetex.mdx                |    8 +-
 redis/commands/hash/hsetnx.mdx                |    4 +-
 redis/commands/hash/hstrlen.mdx               |    4 +-
 redis/commands/hash/httl.mdx                  |    4 +-
 redis/commands/hash/hvals.mdx                 |    4 +-
 redis/commands/hyperloglog/pfadd.mdx          |    6 +-
 redis/commands/hyperloglog/pfcount.mdx        |    6 +-
 redis/commands/hyperloglog/pfmerge.mdx        |    6 +-
 redis/commands/json/json-arrappend.mdx        |    4 +-
 redis/commands/json/json-arrindex.mdx         |    4 +-
 redis/commands/json/json-arrinsert.mdx        |    4 +-
 redis/commands/json/json-arrlen.mdx           |    4 +-
 redis/commands/json/json-arrpop.mdx           |    6 +-
 redis/commands/json/json-arrtrim.mdx          |    6 +-
 redis/commands/json/json-clear.mdx            |    6 +-
 redis/commands/json/json-debug.mdx            |    6 +-
 redis/commands/json/json-del.mdx              |    6 +-
 redis/commands/json/json-forget.mdx           |    6 +-
 redis/commands/json/json-get.mdx              |    6 +-
 redis/commands/json/json-merge.mdx            |    6 +-
 redis/commands/json/json-mget.mdx             |    4 +-
 redis/commands/json/json-mset.mdx             |    4 +-
 redis/commands/json/json-numincrby.mdx        |    4 +-
 redis/commands/json/json-nummultby.mdx        |    4 +-
 redis/commands/json/json-objkeys.mdx          |    4 +-
 redis/commands/json/json-objlen.mdx           |    4 +-
 redis/commands/json/json-resp.mdx             |    6 +-
 redis/commands/json/json-set.mdx              |    6 +-
 redis/commands/json/json-strappend.mdx        |    4 +-
 redis/commands/json/json-strlen.mdx           |    4 +-
 redis/commands/json/json-toggle.mdx           |    4 +-
 redis/commands/json/json-type.mdx             |    4 +-
 redis/commands/json/overview.mdx              |    2 +-
 redis/commands/list/blmove.mdx                |    8 +-
 redis/commands/list/blmpop.mdx                |    6 +-
 redis/commands/list/blpop.mdx                 |    4 +
 redis/commands/list/brpop.mdx                 |    4 +
 redis/commands/list/brpoplpush.mdx            |    4 +
 redis/commands/list/lindex.mdx                |    4 +-
 redis/commands/list/linsert.mdx               |    8 +-
 redis/commands/list/llen.mdx                  |    4 +-
 redis/commands/list/lmove.mdx                 |   10 +-
 redis/commands/list/lmpop.mdx                 |   10 +-
 redis/commands/list/lpop.mdx                  |    6 +-
 redis/commands/list/lpos.mdx                  |    8 +-
 redis/commands/list/lpush.mdx                 |    6 +-
 redis/commands/list/lpushx.mdx                |    4 +-
 redis/commands/list/lrange.mdx                |    6 +-
 redis/commands/list/lrem.mdx                  |    6 +-
 redis/commands/list/lset.mdx                  |    4 +-
 redis/commands/list/ltrim.mdx                 |    6 +-
 redis/commands/list/overview.mdx              |    4 +-
 redis/commands/list/rpop.mdx                  |    6 +-
 redis/commands/list/rpoplpush.mdx             |    6 +-
 redis/commands/list/rpush.mdx                 |    6 +-
 redis/commands/list/rpushx.mdx                |    4 +-
 redis/commands/pub-sub/psubscribe.mdx         |    6 +-
 redis/commands/pub-sub/publish.mdx            |    6 +-
 redis/commands/pub-sub/pubsub.mdx             |    6 +-
 redis/commands/pub-sub/punsubscribe.mdx       |    6 +-
 redis/commands/pub-sub/subscribe.mdx          |    6 +-
 redis/commands/pub-sub/unsubscribe.mdx        |    6 +-
 redis/commands/scripting/eval-ro.mdx          |    4 +-
 redis/commands/scripting/eval.mdx             |    8 +-
 redis/commands/scripting/evalsha-ro.mdx       |    2 +
 redis/commands/scripting/evalsha.mdx          |    6 +-
 redis/commands/scripting/script-exists.mdx    |    4 +-
 redis/commands/scripting/script-flush.mdx     |    4 +-
 redis/commands/scripting/script-kill.mdx      |    4 +
 redis/commands/scripting/script-load.mdx      |    6 +-
 redis/commands/search/search-aggregate.mdx    |    6 +
 redis/commands/search/search-aliasadd.mdx     |    2 +
 redis/commands/search/search-aliasdel.mdx     |    2 +
 redis/commands/search/search-count.mdx        |    2 +
 redis/commands/search/search-create.mdx       |    4 +
 redis/commands/search/search-describe.mdx     |    2 +
 redis/commands/search/search-drop.mdx         |    2 +
 redis/commands/search/search-listaliases.mdx  |    2 +
 redis/commands/search/search-listindexes.mdx  |    2 +
 redis/commands/search/search-query.mdx        |    6 +
 redis/commands/server/acl.mdx                 |    8 +-
 redis/commands/server/command.mdx             |    4 +-
 redis/commands/server/config-get.mdx          |    6 +-
 redis/commands/server/config-set.mdx          |    6 +-
 redis/commands/server/dbsize.mdx              |    4 +-
 redis/commands/server/flushall.mdx            |    6 +-
 redis/commands/server/flushdb.mdx             |    6 +-
 redis/commands/server/info.mdx                |    6 +-
 redis/commands/server/monitor.mdx             |    6 +-
 redis/commands/server/time.mdx                |    4 +-
 redis/commands/set/overview.mdx               |    4 +-
 redis/commands/set/sadd.mdx                   |    4 +-
 redis/commands/set/scard.mdx                  |    4 +-
 redis/commands/set/sdiff.mdx                  |    6 +-
 redis/commands/set/sdiffstore.mdx             |    6 +-
 redis/commands/set/sinter.mdx                 |    6 +-
 redis/commands/set/sintercard.mdx             |    6 +-
 redis/commands/set/sinterstore.mdx            |    4 +-
 redis/commands/set/sismember.mdx              |    4 +-
 redis/commands/set/smembers.mdx               |    4 +-
 redis/commands/set/smismember.mdx             |    6 +-
 redis/commands/set/smove.mdx                  |    6 +-
 redis/commands/set/spop.mdx                   |    8 +-
 redis/commands/set/srandmember.mdx            |    6 +-
 redis/commands/set/srem.mdx                   |    4 +-
 redis/commands/set/sscan.mdx                  |    6 +-
 redis/commands/set/sunion.mdx                 |    4 +-
 redis/commands/set/sunionstore.mdx            |    4 +-
 redis/commands/sorted-set/bzmpop.mdx          |    6 +-
 redis/commands/sorted-set/bzpopmax.mdx        |    4 +
 redis/commands/sorted-set/bzpopmin.mdx        |    4 +
 redis/commands/sorted-set/overview.mdx        |    6 +-
 redis/commands/sorted-set/zadd.mdx            |    6 +-
 redis/commands/sorted-set/zcard.mdx           |    4 +-
 redis/commands/sorted-set/zcount.mdx          |    6 +-
 redis/commands/sorted-set/zdiff.mdx           |    6 +-
 redis/commands/sorted-set/zdiffstore.mdx      |    6 +-
 redis/commands/sorted-set/zincrby.mdx         |    6 +-
 redis/commands/sorted-set/zinter.mdx          |    6 +-
 redis/commands/sorted-set/zintercard.mdx      |    4 +-
 redis/commands/sorted-set/zinterstore.mdx     |    6 +-
 redis/commands/sorted-set/zlexcount.mdx       |    6 +-
 redis/commands/sorted-set/zmpop.mdx           |   10 +-
 redis/commands/sorted-set/zmscore.mdx         |    4 +-
 redis/commands/sorted-set/zpopmax.mdx         |    6 +-
 redis/commands/sorted-set/zpopmin.mdx         |    6 +-
 redis/commands/sorted-set/zrandmember.mdx     |    6 +-
 redis/commands/sorted-set/zrange.mdx          |   12 +-
 redis/commands/sorted-set/zrangebylex.mdx     |    8 +-
 redis/commands/sorted-set/zrangebyscore.mdx   |    6 +-
 redis/commands/sorted-set/zrangestore.mdx     |   10 +-
 redis/commands/sorted-set/zrank.mdx           |    6 +-
 redis/commands/sorted-set/zrem.mdx            |    4 +-
 redis/commands/sorted-set/zremrangebylex.mdx  |    6 +-
 redis/commands/sorted-set/zremrangebyrank.mdx |    6 +-
 .../commands/sorted-set/zremrangebyscore.mdx  |    6 +-
 redis/commands/sorted-set/zrevrange.mdx       |    6 +-
 redis/commands/sorted-set/zrevrangebylex.mdx  |    4 +
 .../commands/sorted-set/zrevrangebyscore.mdx  |    4 +
 redis/commands/sorted-set/zrevrank.mdx        |    4 +-
 redis/commands/sorted-set/zscan.mdx           |    6 +-
 redis/commands/sorted-set/zscore.mdx          |    4 +-
 redis/commands/sorted-set/zunion.mdx          |    6 +-
 redis/commands/sorted-set/zunionstore.mdx     |    6 +-
 redis/commands/streams/overview.mdx           |    2 +-
 redis/commands/streams/xack.mdx               |    6 +-
 redis/commands/streams/xackdel.mdx            |    8 +-
 redis/commands/streams/xadd.mdx               |   12 +-
 redis/commands/streams/xautoclaim.mdx         |    6 +-
 redis/commands/streams/xclaim.mdx             |    8 +-
 redis/commands/streams/xdel.mdx               |    6 +-
 redis/commands/streams/xdelex.mdx             |   10 +-
 redis/commands/streams/xgroup.mdx             |    8 +-
 redis/commands/streams/xinfo-consumers.mdx    |    4 +-
 redis/commands/streams/xinfo-groups.mdx       |    4 +-
 redis/commands/streams/xinfo-stream.mdx       |    6 +-
 redis/commands/streams/xlen.mdx               |    4 +-
 redis/commands/streams/xpending.mdx           |    8 +-
 redis/commands/streams/xrange.mdx             |    6 +-
 redis/commands/streams/xread.mdx              |    8 +-
 redis/commands/streams/xreadgroup.mdx         |    8 +-
 redis/commands/streams/xrevrange.mdx          |    6 +-
 redis/commands/streams/xtrim.mdx              |    8 +-
 redis/commands/string/append.mdx              |    4 +-
 redis/commands/string/decr.mdx                |    4 +-
 redis/commands/string/decrby.mdx              |    4 +-
 redis/commands/string/delex.mdx               |    4 +
 redis/commands/string/digest.mdx              |    4 +
 redis/commands/string/get.mdx                 |    4 +-
 redis/commands/string/getdel.mdx              |    4 +-
 redis/commands/string/getex.mdx               |    8 +-
 redis/commands/string/getrange.mdx            |    6 +-
 redis/commands/string/getset.mdx              |    6 +-
 redis/commands/string/incr.mdx                |    6 +-
 redis/commands/string/incrby.mdx              |    6 +-
 redis/commands/string/incrbyfloat.mdx         |    6 +-
 redis/commands/string/mget.mdx                |    6 +-
 redis/commands/string/mset.mdx                |    6 +-
 redis/commands/string/msetnx.mdx              |    4 +-
 redis/commands/string/psetex.mdx              |    6 +-
 redis/commands/string/set.mdx                 |    8 +-
 redis/commands/string/setex.mdx               |    6 +-
 redis/commands/string/setnx.mdx               |    6 +-
 redis/commands/string/setrange.mdx            |    6 +-
 redis/commands/string/strlen.mdx              |    4 +-
 redis/commands/transactions/discard.mdx       |    6 +-
 redis/commands/transactions/exec.mdx          |    8 +-
 redis/commands/transactions/multi.mdx         |    6 +
 redis/commands/transactions/unwatch.mdx       |    6 +-
 redis/commands/transactions/watch.mdx         |    8 +-
 279 files changed, 2460 insertions(+), 608 deletions(-)

diff --git a/llms-full.txt b/llms-full.txt
index 47a2af7a1..1e27b24e7 100644
--- a/llms-full.txt
+++ b/llms-full.txt
@@ -16967,7 +16967,11 @@ For debugging or monitoring purposes, you can use Realtime Dashboard in console.
 # BITCOUNT
 Source: https://upstash.com/docs/redis/commands/bitmap/bitcount
 
-Use `BITCOUNT` to count set bits in a string.
+Use `BITCOUNT` to count the bits set to 1 in the string stored at a key.
+
+Without a range the whole value is counted. `<start>` and `<end>` restrict the count to a part of the value and are interpreted as byte offsets by default, or as bit offsets when `BIT` is given. Both ends are inclusive and may be negative to count backwards from the end of the value, where `-1` is the last byte or bit. A missing key is treated as an empty string and returns `0`.
+
+`BITCOUNT` is the usual way to read a bitmap built with [`SETBIT`](/docs/redis/commands/bitmap/setbit), for example to count how many users were active on a given day when each user has a fixed bit position.
 
 ## Syntax
 
@@ -17131,7 +17135,13 @@ fn main() -> redis::RedisResult<()> {
 # BITFIELD
 Source: https://upstash.com/docs/redis/commands/bitmap/bitfield
 
-Use `BITFIELD` to perform arbitrary bitfield operations.
+Use `BITFIELD` to treat a string as an array of packed integers and run several operations on it in a single atomic call.
+
+Every operation names an encoding and a bit offset. The encoding is `u<bits>` for unsigned integers (up to 63 bits) or `i<bits>` for signed integers (up to 64 bits). The offset is counted in bits from the start of the value or, when prefixed with `#`, in units of the encoding width, so `#2` with `u8` addresses the third 8-bit field. The string grows automatically with zero bits when an operation addresses an offset past its current end.
+
+`GET` reads a field, `SET` writes one and returns its previous value, and `INCRBY` adds a possibly negative increment and returns the new value. `OVERFLOW` sets how the `SET` and `INCRBY` operations that follow it behave when a value does not fit the encoding: `WRAP` wraps around like modular arithmetic and is the default, `SAT` saturates at the minimum or maximum of the encoding, and `FAIL` leaves the field unchanged and returns null for that operation. The reply is an array with one entry per operation, in the order the operations were given.
+
+Packing many small counters into a single key this way saves memory and keeps the whole update atomic, which makes it a good fit for rate limiters and compact per-user counters.
 
 ## Syntax
 
@@ -17144,7 +17154,7 @@ BITFIELD <key> [GET <encoding> <offset> | [OVERFLOW WRAP | SAT | FAIL] (SET <enc
 | Argument | Required | Repeatable | Description |
 | --- | --- | --- | --- |
 | `<key>` | Yes | No | Redis key targeted by the command. |
-| `(GET <encoding> <offset> \| [OVERFLOW WRAP \| SAT \| FAIL] (SET <encoding> <offset> <value> \| INCRBY <encoding> <offset> <increment>))` | No | Yes | Choose one form: `GET` (also return the previous value); `OVERFLOW`; `WRAP`; `SAT`; `FAIL`; `SET`; `INCRBY`. |
+| `(GET <encoding> <offset> \| [OVERFLOW WRAP \| SAT \| FAIL] (SET <encoding> <offset> <value> \| INCRBY <encoding> <offset> <increment>))` | No | Yes | An operation on a field of `<encoding>` (`u<bits>` unsigned up to 63 bits, or `i<bits>` signed up to 64 bits) at `<offset>` bits, or at `#<n>` to address the n-th field of that width: `GET` reads it, `SET` writes it and returns the previous value, and `INCRBY` adds an increment and returns the new value. `OVERFLOW` sets how the `SET` and `INCRBY` operations after it handle a value that does not fit: `WRAP` wraps around (the default), `SAT` saturates at the encoding's limits, and `FAIL` leaves the field unchanged and returns null. Repeat to run several operations in one atomic call. |
 
 ## Response
 
@@ -17297,6 +17307,8 @@ Source: https://upstash.com/docs/redis/commands/bitmap/bitfield-ro
 
 Use `BITFIELD_RO` to read one or more bitfield values without modifying the key.
 
+It is the read-only form of [`BITFIELD`](/docs/redis/commands/bitmap/bitfield) and accepts `GET` operations only, so it is safe to run on replicas and from read-only scripts. Each `GET` names an encoding, `u<bits>` for unsigned or `i<bits>` for signed integers, and a bit offset that can be written as `#<n>` to address the n-th field of that width. The reply holds one integer per `GET`, and any part of a field that lies past the end of the stored string reads as zero.
+
 ## Syntax
 
 ```redis
@@ -17455,7 +17467,13 @@ fn main() -> redis::RedisResult<()> {
 # BITOP
 Source: https://upstash.com/docs/redis/commands/bitmap/bitop
 
-Use `BITOP` to perform bitwise operations between strings.
+Use `BITOP` to combine several strings with a bitwise operation and store the result in another key.
+
+Source strings are combined bit by bit, and shorter ones are treated as if they were padded with zero bits up to the length of the longest input, so the destination always ends up as long as the longest source. A missing key counts as an empty string, and if the result is empty the destination key is deleted. The reply is the length of the stored value in bytes.
+
+`AND`, `OR`, and `XOR` accept any number of source keys and `NOT` accepts exactly one. The remaining operators compare the first key with the rest: `DIFF` keeps the bits set in the first key and in none of the others, `DIFF1` keeps the bits set in at least one of the other keys but not in the first, `ANDOR` keeps the bits set in the first key and in at least one of the others, and `ONE` keeps the bits set in exactly one of the source keys. `DIFF`, `DIFF1`, and `ANDOR` each require at least two source keys.
+
+This is how bitmaps are used as sets: with one bit per user, `AND` gives users present in every bitmap and `OR` gives users present in any of them, and [`BITCOUNT`](/docs/redis/commands/bitmap/bitcount) then turns the result into a number.
 
 ## Syntax
 
@@ -17467,7 +17485,7 @@ BITOP (AND | OR | XOR | NOT | DIFF | DIFF1 | ANDOR | ONE) <destkey> <key> [<key>
 
 | Argument | Required | Repeatable | Description |
 | --- | --- | --- | --- |
-| `(AND \| OR \| XOR \| NOT \| DIFF \| DIFF1 \| ANDOR \| ONE)` | Yes | No | Choose one form: `AND`; `OR`; `XOR`; `NOT`; `DIFF`; `DIFF1`; `ANDOR`; `ONE`. |
+| `(AND \| OR \| XOR \| NOT \| DIFF \| DIFF1 \| ANDOR \| ONE)` | Yes | No | The bitwise operation to apply. `AND`, `OR`, and `XOR` combine any number of source keys and `NOT` inverts exactly one. The rest compare the first key with the others: `DIFF` keeps bits set in the first key and in none of the others, `DIFF1` keeps bits set in at least one of the others but not in the first, `ANDOR` keeps bits set in the first key and in at least one of the others, and `ONE` keeps bits set in exactly one source key. |
 | `<destkey>` | Yes | No | Redis key used as destkey. |
 | `<key>` | Yes | Yes | Redis key targeted by the command. |
 
@@ -17630,7 +17648,11 @@ fn main() -> redis::RedisResult<()> {
 # BITPOS
 Source: https://upstash.com/docs/redis/commands/bitmap/bitpos
 
-Use `BITPOS` to find first bit set or clear in a string.
+Use `BITPOS` to find the position of the first bit set to `0` or `1` in a string.
+
+The whole value is searched unless `<start>` and `<end>` are given, and those are byte offsets by default or bit offsets when `BIT` is given. Both ends are inclusive and may be negative to count backwards from the end of the value. The reply is always an absolute bit position counted from the start of the string, or `-1` when no matching bit is found.
+
+One edge case is worth remembering: when you look for a `0` in a string of all ones and give no explicit end, the reply is the position of the first bit past the end of the string, because the value is treated as if it were followed by an infinite run of zero bits. Bounding the search with an explicit range returns `-1` in the same situation.
 
 ## Syntax
 
@@ -17796,7 +17818,9 @@ fn main() -> redis::RedisResult<()> {
 # GETBIT
 Source: https://upstash.com/docs/redis/commands/bitmap/getbit
 
-Use `GETBIT` to get the bit value at offset.
+Use `GETBIT` to read a single bit of the string stored at a key.
+
+The offset is counted in bits from the start of the value, so offset `0` is the most significant bit of the first byte. When the key does not exist, or the offset lies past the end of the stored string, the bit reads as `0` rather than producing an error.
 
 ## Syntax
 
@@ -17973,7 +17997,11 @@ Source: https://upstash.com/docs/redis/commands/bitmap/overview
 # SETBIT
 Source: https://upstash.com/docs/redis/commands/bitmap/setbit
 
-Use `SETBIT` to set or clear the bit at offset.
+Use `SETBIT` to set a single bit of the string stored at a key to `0` or `1`.
+
+The offset is counted in bits from the start of the value and the reply is the bit's previous value. If the key does not exist, or the offset lies past the end of the current value, the string is first extended with zero bits, so writing to a large offset allocates every byte up to it. Keep offsets dense, for example by mapping each user to a small sequential id.
+
+Bitmaps built this way are read back with [`GETBIT`](/docs/redis/commands/bitmap/getbit), counted with [`BITCOUNT`](/docs/redis/commands/bitmap/bitcount), and combined with [`BITOP`](/docs/redis/commands/bitmap/bitop).
 
 ## Syntax
 
@@ -18138,7 +18166,9 @@ fn main() -> redis::RedisResult<()> {
 # AUTH
 Source: https://upstash.com/docs/redis/commands/connection/auth
 
-Use `AUTH` to authenticate to the server.
+Use `AUTH` to authenticate the current connection, with a password alone or with a username and password when ACL users are configured.
+
+Until the connection is authenticated the server rejects other commands with an error. Client libraries usually send `AUTH` for you as part of connecting when the credentials are part of the connection string, so applications rarely call it directly. The password is sent to the server on every connection, which is why Upstash endpoints use TLS.
 
 ## Syntax
 
@@ -18282,7 +18312,9 @@ fn main() -> redis::RedisResult<()> {
 # CLIENT GETNAME
 Source: https://upstash.com/docs/redis/commands/connection/client-getname
 
-Use `CLIENT GETNAME` to get the current connection name.
+Use `CLIENT GETNAME` to read the name assigned to the current connection with [`CLIENT SETNAME`](/docs/redis/commands/connection/client-setname).
+
+Connections start without a name and the reply is null until one is set. The name belongs to a single connection and is lost when it closes; it exists to make connections recognizable in [`CLIENT LIST`](/docs/redis/commands/connection/client-list) output when you are debugging which part of an application is doing what.
 
 ## Syntax
 
@@ -18424,7 +18456,9 @@ fn main() -> redis::RedisResult<()> {
 # CLIENT ID
 Source: https://upstash.com/docs/redis/commands/connection/client-id
 
-Use `CLIENT ID` to get the current client ID.
+Use `CLIENT ID` to get the unique identifier the server assigned to the current connection.
+
+IDs are integers that never repeat and always increase, so a larger ID means a connection that was established later. The ID identifies this connection in [`CLIENT LIST`](/docs/redis/commands/connection/client-list) output, which makes it useful when correlating application logs with server-side connection state.
 
 ## Syntax
 
@@ -18566,7 +18600,9 @@ fn main() -> redis::RedisResult<()> {
 # CLIENT INFO
 Source: https://upstash.com/docs/redis/commands/connection/client-info
 
-Use `CLIENT INFO` to get info about current connection.
+Use `CLIENT INFO` to get a line of statistics about the connection issuing the command.
+
+The reply is a single line of space-separated `field=value` pairs describing the connection: its id, name, address, age, idle time, the number of commands it has run, and the last command it executed. It reports the same fields as one line of [`CLIENT LIST`](/docs/redis/commands/connection/client-list), limited to your own connection, which makes it a cheap way to confirm what the server thinks of the connection you are on. Parse it defensively, since fields can be added over time.
 
 ## Syntax
 
@@ -18708,7 +18744,9 @@ fn main() -> redis::RedisResult<()> {
 # CLIENT LIST
 Source: https://upstash.com/docs/redis/commands/connection/client-list
 
-Use `CLIENT LIST` to list all client connections.
+Use `CLIENT LIST` to get one line of statistics for every client connection to the server.
+
+Each line holds space-separated `field=value` pairs with the connection's id, name, address, age, idle time, protocol version, and last command, so the reply gives a snapshot of who is connected and what they are doing. It is the usual starting point for tracking down connection leaks and idle connections. The reply grows with the number of clients, so avoid calling it on a hot path, and parse it defensively because fields can be added over time.
 
 ## Syntax
 
@@ -18850,7 +18888,9 @@ fn main() -> redis::RedisResult<()> {
 # CLIENT SETINFO
 Source: https://upstash.com/docs/redis/commands/connection/client-setinfo
 
-Use `CLIENT SETINFO` to set client connection attributes.
+Use `CLIENT SETINFO` to attach library identification to the current connection.
+
+`LIB-NAME` records the name of the client library and `LIB-VER` its version. Both values then appear in [`CLIENT INFO`](/docs/redis/commands/connection/client-info) and [`CLIENT LIST`](/docs/redis/commands/connection/client-list) output, which makes it possible to tell which application or SDK version owns a connection. Most client libraries send this during the handshake, so applications rarely call it themselves.
 
 ## Syntax
 
@@ -18997,7 +19037,9 @@ fn main() -> redis::RedisResult<()> {
 # CLIENT SETNAME
 Source: https://upstash.com/docs/redis/commands/connection/client-setname
 
-Use `CLIENT SETNAME` to set the connection name.
+Use `CLIENT SETNAME` to label the current connection with a name of your choice.
+
+The name shows up in [`CLIENT LIST`](/docs/redis/commands/connection/client-list) and [`CLIENT INFO`](/docs/redis/commands/connection/client-info) output, which is handy when several components of an application share one database and you want to tell their connections apart. The name may not contain spaces or newlines, each call replaces the previous name, and passing an empty string clears it. It lives only as long as the connection.
 
 ## Syntax
 
@@ -19142,7 +19184,9 @@ fn main() -> redis::RedisResult<()> {
 # ECHO
 Source: https://upstash.com/docs/redis/commands/connection/echo
 
-Use `ECHO` to echo the given string.
+Use `ECHO` to have the server send the given message back unchanged.
+
+The command performs no work beyond the round trip, which makes it a simple way to verify that a connection is alive and that values survive the client library's encoding and decoding. For plain liveness checks [`PING`](/docs/redis/commands/connection/ping) is the more common choice.
 
 ## Syntax
 
@@ -19306,7 +19350,11 @@ fn main() -> redis::RedisResult<()> {
 # HELLO
 Source: https://upstash.com/docs/redis/commands/connection/hello
 
-Use `HELLO` to handshake with Redis protocol.
+Use `HELLO` to negotiate the protocol version of the connection and read the server handshake information.
+
+Passing `<protover>` switches the connection to RESP2 or RESP3. RESP3 adds native map, set, double, and push replies, so commands such as [`HGETALL`](/docs/redis/commands/hash/hgetall) or [`CONFIG GET`](/docs/redis/commands/server/config-get) come back as maps instead of flat arrays, and pub/sub messages arrive as push replies that do not block ordinary commands. `AUTH` authenticates in the same call and `SETNAME` names the connection, which lets a client complete its handshake in one round trip.
+
+Called without arguments, `HELLO` only reports the server version, the protocol in use, the connection id, and the current role, leaving the protocol unchanged.
 
 ## Syntax
 
@@ -19470,7 +19518,9 @@ Source: https://upstash.com/docs/redis/commands/connection/overview
 # PING
 Source: https://upstash.com/docs/redis/commands/connection/ping
 
-Use `PING` to ping the server.
+Use `PING` to check that the connection and the server are alive.
+
+Without arguments the server replies `PONG`. With a message it echoes that message back instead, which lets a client match a reply to the exact request that produced it. `PING` is the standard health check for a connection pool, both to test a connection before handing it out and to keep an otherwise idle connection from being closed by intermediate proxies. It also works while the connection is subscribed to channels, where it doubles as a keepalive.
 
 ## Syntax
 
@@ -19639,7 +19689,9 @@ fn main() -> redis::RedisResult<()> {
 # QUIT
 Source: https://upstash.com/docs/redis/commands/connection/quit
 
-Use `QUIT` to close the connection.
+Use `QUIT` to ask the server to close the connection once all pending replies have been sent.
+
+The server replies `OK` and then terminates the connection, so no reply is lost and the shutdown is clean from both sides. Modern clients usually just close the socket, and pooled connections should be returned to the pool rather than closed, so `QUIT` is mostly useful in scripts and interactive sessions.
 
 ## Syntax
 
@@ -19782,7 +19834,9 @@ fn main() -> redis::RedisResult<()> {
 # RESET
 Source: https://upstash.com/docs/redis/commands/connection/reset
 
-Use `RESET` to reset the connection.
+Use `RESET` to return the connection to the state it had right after connecting.
+
+It discards an open [`MULTI`](/docs/redis/commands/transactions/multi) block, unwatches every key watched with [`WATCH`](/docs/redis/commands/transactions/watch), leaves subscriber and monitor modes, clears the connection name, re-enables replies, and de-authenticates the connection when the database requires a password. This makes it the safe way to hand a connection back to a pool after an error, since the next user cannot inherit a half-finished transaction or a leftover subscription.
 
 ## Syntax
 
@@ -19923,7 +19977,9 @@ fn main() -> redis::RedisResult<()> {
 # SELECT
 Source: https://upstash.com/docs/redis/commands/connection/select
 
-Use `SELECT` to select the database by index.
+Use `SELECT` to switch the connection to another database index.
+
+Upstash exposes a single logical database, so `0` is the only valid index and anything else returns an error. The command is accepted so that clients and frameworks that issue `SELECT 0` while setting up a connection keep working unchanged. To separate concerns inside one database, use key prefixes instead of numbered databases.
 
 ## Syntax
 
@@ -20082,7 +20138,11 @@ fn main() -> redis::RedisResult<()> {
 # FCALL
 Source: https://upstash.com/docs/redis/commands/functions/fcall
 
-Use `FCALL` to call a function.
+Use `FCALL` to invoke a function from a library loaded with [`FUNCTION LOAD`](/docs/redis/commands/functions/function-load).
+
+`<numkeys>` tells the server how many of the arguments that follow are key names. Those keys reach the function in `KEYS` and every remaining argument in `ARGV`. Passing key names as keys instead of hardcoding them in the function body matters, because Redis uses that list for routing and access checks.
+
+The function runs on the server as a single atomic step, so a sequence of reads and writes that would otherwise need several round trips and a transaction becomes one command. Use [`FCALL_RO`](/docs/redis/commands/functions/fcall-ro) when the function only reads. Functions are the successor to [`EVAL`](/docs/redis/commands/scripting/eval) scripts: they are named, registered once as part of a library, and persisted with the dataset instead of being sent or looked up by digest on every call.
 
 ## Syntax
 
@@ -20261,7 +20321,11 @@ fn main() -> redis::RedisResult<()> {
 # FCALL_RO
 Source: https://upstash.com/docs/redis/commands/functions/fcall-ro
 
-Use `FCALL_RO` to call a read-only function.
+Use `FCALL_RO` to invoke a function that is declared read-only.
+
+The function must have been registered with the `no-writes` flag; calling a function without it returns an error. In exchange the server knows the call cannot modify data, so it can serve it on replicas and reject accidental writes outright.
+
+Apart from that restriction it behaves like [`FCALL`](/docs/redis/commands/functions/fcall): `<numkeys>` splits the arguments into the keys the function receives in `KEYS` and the plain arguments it receives in `ARGV`.
 
 ## Syntax
 
@@ -20447,7 +20511,9 @@ fn main() -> redis::RedisResult<()> {
 # FUNCTION DELETE
 Source: https://upstash.com/docs/redis/commands/functions/function-delete
 
-Use `FUNCTION DELETE` to delete a library.
+Use `FUNCTION DELETE` to remove a function library and every function it registered.
+
+The argument is the library name declared when the library was loaded, not the name of a single function, and there is no way to delete one function from a library: reload the library with `REPLACE` instead. Deleting a library that does not exist returns an error, and calls to its functions fail until the library is loaded again.
 
 ## Syntax
 
@@ -20607,7 +20673,9 @@ fn main() -> redis::RedisResult<()> {
 # FUNCTION FLUSH
 Source: https://upstash.com/docs/redis/commands/functions/function-flush
 
-Use `FUNCTION FLUSH` to delete all libraries.
+Use `FUNCTION FLUSH` to remove every function library from the database.
+
+This wipes all registered libraries and functions at once and cannot be undone, so it belongs in test setup and provisioning tooling rather than application code. `ASYNC` reclaims the memory in the background and `SYNC` reclaims it before the reply is sent.
 
 ## Syntax
 
@@ -20766,7 +20834,11 @@ fn main() -> redis::RedisResult<()> {
 # FUNCTION KILL
 Source: https://upstash.com/docs/redis/commands/functions/function-kill
 
-Use `FUNCTION KILL` to kill a running function.
+Use `FUNCTION KILL` to stop a function that is currently running and has not yet written anything.
+
+A function that has already modified data cannot be killed, because stopping it halfway would leave the dataset in a state that no atomic step could produce. Check [`FUNCTION STATS`](/docs/redis/commands/functions/function-stats) to see whether a function is running before calling this.
+
+The current Upstash deployment recognizes the command but has no interruptible running-function state to act on, so it replies with a `NOTBUSY` error.
 
 ## Syntax
 
@@ -20923,7 +20995,9 @@ fn main() -> redis::RedisResult<()> {
 # FUNCTION LIST
 Source: https://upstash.com/docs/redis/commands/functions/function-list
 
-Use `FUNCTION LIST` to list all libraries.
+Use `FUNCTION LIST` to inspect the function libraries loaded in the database.
+
+The reply describes each library with its name, the engine it runs on, and the functions it registers, including each function's description and flags such as `no-writes`. `LIBRARYNAME` filters the reply to library names matching a pattern, and `WITHCODE` includes the full source of each library, which is how you recover the code of a library that is deployed but no longer at hand.
 
 ## Syntax
 
@@ -21100,7 +21174,11 @@ fn main() -> redis::RedisResult<()> {
 # FUNCTION LOAD
 Source: https://upstash.com/docs/redis/commands/functions/function-load
 
-Use `FUNCTION LOAD` to load a library.
+Use `FUNCTION LOAD` to register a library of functions in the database.
+
+The payload is the library source code. It must begin with a shebang line naming the engine and the library, such as `#!lua name=mylib`, and register each function with `redis.register_function`, giving it a name, a callback, and optional flags such as `no-writes`. The reply is the library name.
+
+Loading fails when the library name is already in use unless `REPLACE` is given, which is how you deploy a new version of a library. Once loaded, functions are called by name with [`FCALL`](/docs/redis/commands/functions/fcall) or [`FCALL_RO`](/docs/redis/commands/functions/fcall-ro). Unlike scripts cached by [`SCRIPT LOAD`](/docs/redis/commands/scripting/script-load), libraries are part of the dataset, so they survive restarts and do not need to be re-sent by clients.
 
 ## Syntax
 
@@ -21281,7 +21359,9 @@ fn main() -> redis::RedisResult<()> {
 # FUNCTION STATS
 Source: https://upstash.com/docs/redis/commands/functions/function-stats
 
-Use `FUNCTION STATS` to get function execution stats.
+Use `FUNCTION STATS` to read the current state of the function engine.
+
+The reply reports the function that is running right now, if any, together with how long it has been running and the command that started it, plus per-engine counts of loaded libraries and functions. It is the usual way to check whether a long-running function is in progress before deciding to call [`FUNCTION KILL`](/docs/redis/commands/functions/function-kill).
 
 ## Syntax
 
@@ -21462,7 +21542,11 @@ Source: https://upstash.com/docs/redis/commands/functions/overview
 # COPY
 Source: https://upstash.com/docs/redis/commands/generic/copy
 
-Use `COPY` to copy a key to another key.
+Use `COPY` to copy the value stored at one key to another key.
+
+The destination gets an independent deep copy of the value, so later changes to either key do not affect the other, and the source key's remaining time to live is copied along with it. Any type can be copied.
+
+By default the command does nothing and returns `0` when the destination key already exists; `REPLACE` overwrites it instead. `DB` selects the destination database index, which on Upstash is always `0`.
 
 ## Syntax
 
@@ -21628,7 +21712,9 @@ fn main() -> redis::RedisResult<()> {
 # DEL
 Source: https://upstash.com/docs/redis/commands/generic/del
 
-Use `DEL` to delete one or more keys.
+Use `DEL` to delete one or more keys and the values they hold, whatever their type.
+
+The reply counts only the keys that actually existed, so deleting a key that is already gone is not an error and the count tells you how many were really removed. The memory is freed as part of the command, which for very large collections can take noticeable time; [`UNLINK`](/docs/redis/commands/generic/unlink) removes the keys just as immediately but frees their memory in the background.
 
 ## Syntax
 
@@ -21791,7 +21877,11 @@ fn main() -> redis::RedisResult<()> {
 # DUMP
 Source: https://upstash.com/docs/redis/commands/generic/dump
 
-Use `DUMP` to serialize a key's value.
+Use `DUMP` to serialize the value stored at a key into a portable, Redis-specific binary blob.
+
+The blob carries the value together with a version stamp and a checksum, but not the key name and not its time to live. Feeding it to [`RESTORE`](/docs/redis/commands/generic/restore) recreates the value under any key name, in the same database or in another one, which makes the pair the standard way to move or back up individual keys. A missing key returns null.
+
+The reply is raw binary data, not text: keep it in a byte-safe container and avoid string encodings that would corrupt it.
 
 ## Syntax
 
@@ -21946,7 +22036,9 @@ fn main() -> redis::RedisResult<()> {
 # EXISTS
 Source: https://upstash.com/docs/redis/commands/generic/exists
 
-Use `EXISTS` to check if keys exist.
+Use `EXISTS` to check whether one or more keys exist.
+
+The reply is the number of the given keys that exist, so with a single key it is simply `1` or `0`. A key listed several times is counted each time it is present, which means `EXISTS k k` returns `2` when `k` exists. Checking existence never transfers the value, so it stays cheap even for large values.
 
 ## Syntax
 
@@ -22112,7 +22204,13 @@ fn main() -> redis::RedisResult<()> {
 # EXPIRE
 Source: https://upstash.com/docs/redis/commands/generic/expire
 
-Use `EXPIRE` to set a key's TTL in seconds.
+Use `EXPIRE` to give a key a lifetime in seconds, after which the key is deleted automatically.
+
+Whether the expiration survives later writes depends on the command: replacing the value with [`SET`](/docs/redis/commands/string/set) clears it, while commands that modify a value in place, such as [`INCR`](/docs/redis/commands/string/incr), [`LPUSH`](/docs/redis/commands/list/lpush) or [`HSET`](/docs/redis/commands/hash/hset), leave it untouched. A negative lifetime deletes the key immediately.
+
+The optional condition decides when the new expiration is applied: `NX` only when the key currently has none, `XX` only when it already has one, `GT` only when the new expiration is later than the current one, and `LT` only when it is earlier. Since a key without an expiration counts as living forever, `GT` never adds one and `LT` always does. The reply is `1` when the expiration was set and `0` when the key does not exist or the condition was not met.
+
+Read the remaining lifetime with [`TTL`](/docs/redis/commands/generic/ttl) and remove it again with [`PERSIST`](/docs/redis/commands/generic/persist).
 
 ## Syntax
 
@@ -22284,7 +22382,11 @@ fn main() -> redis::RedisResult<()> {
 # EXPIREAT
 Source: https://upstash.com/docs/redis/commands/generic/expireat
 
-Use `EXPIREAT` to set expiry as Unix timestamp.
+Use `EXPIREAT` to schedule a key for automatic deletion at a fixed point in time, given as a Unix timestamp in seconds.
+
+It behaves exactly like [`EXPIRE`](/docs/redis/commands/generic/expire) except that the deadline is absolute rather than relative, which is what you want when several keys must expire at the same moment, such as the end of an hour or of a billing period. Computing the deadline once and reusing it also avoids the drift that repeated relative expirations introduce. A timestamp in the past deletes the key right away.
+
+The optional condition works as it does for `EXPIRE`: `NX` only when the key has no expiration, `XX` only when it already has one, `GT` only when the new deadline is later than the current one, and `LT` only when it is earlier.
 
 ## Syntax
 
@@ -22457,7 +22559,9 @@ fn main() -> redis::RedisResult<()> {
 # EXPIRETIME
 Source: https://upstash.com/docs/redis/commands/generic/expiretime
 
-Use `EXPIRETIME` to get expiry as Unix timestamp.
+Use `EXPIRETIME` to read the absolute time at which a key will expire, as a Unix timestamp in seconds.
+
+The reply is `-1` when the key exists but has no expiration, and `-2` when the key does not exist, so the two cases can be told apart. Use [`TTL`](/docs/redis/commands/generic/ttl) when you need the remaining lifetime instead of the deadline, and [`PEXPIRETIME`](/docs/redis/commands/generic/pexpiretime) when you need millisecond precision.
 
 ## Syntax
 
@@ -22616,7 +22720,11 @@ fn main() -> redis::RedisResult<()> {
 # KEYS
 Source: https://upstash.com/docs/redis/commands/generic/keys
 
-Use `KEYS` to find keys matching a pattern.
+Use `KEYS` to list every key in the database whose name matches a glob-style pattern.
+
+The pattern supports `*` for any sequence of characters, `?` for a single character, `[...]` for character classes, and `\` to escape a literal, so `user:*:session` matches all session keys of all users and `*` matches everything.
+
+The command walks the entire keyspace and returns all matches in one reply, which on a database of any real size means a long block and a very large response. Treat it as a debugging and maintenance tool: on hot paths use [`SCAN`](/docs/redis/commands/generic/scan), which accepts the same `MATCH` patterns but walks the keyspace in small batches, or keep an index of your keys in a set instead.
 
 ## Syntax
 
@@ -22784,7 +22892,11 @@ fn main() -> redis::RedisResult<()> {
 # MEMORY USAGE
 Source: https://upstash.com/docs/redis/commands/generic/memory-usage
 
-Use `MEMORY USAGE` to estimate memory used by a key.
+Use `MEMORY USAGE` to estimate how many bytes a key and its value occupy in memory.
+
+The figure covers the stored data along with its internal overhead, so it is larger than the raw size of the value and is meant for comparing keys rather than for exact accounting. For aggregate types such as hashes, lists, sets, sorted sets, and streams the value is sampled instead of fully traversed: `SAMPLES` sets how many nested elements are inspected, and the value is clamped to the range this deployment supports, so it tunes the estimate rather than forcing an exact traversal. A missing key returns null.
+
+It is the usual way to find out which keys are responsible for memory growth before deciding what to trim or restructure.
 
 ## Syntax
 
@@ -22979,7 +23091,9 @@ Source: https://upstash.com/docs/redis/commands/generic/overview
 # PERSIST
 Source: https://upstash.com/docs/redis/commands/generic/persist
 
-Use `PERSIST` to remove the expiration from a key.
+Use `PERSIST` to remove the expiration from a key so that it stops being deleted automatically and lives until it is removed explicitly.
+
+The reply is `1` when an expiration was removed and `0` when the key does not exist or had no expiration to begin with. This is how a value gets promoted from temporary to permanent without rewriting it, for example when a trial record becomes a persistent one.
 
 ## Syntax
 
@@ -23142,7 +23256,11 @@ fn main() -> redis::RedisResult<()> {
 # PEXPIRE
 Source: https://upstash.com/docs/redis/commands/generic/pexpire
 
-Use `PEXPIRE` to set a key's TTL in milliseconds.
+Use `PEXPIRE` to give a key a lifetime in milliseconds, after which the key is deleted automatically.
+
+It is the millisecond form of [`EXPIRE`](/docs/redis/commands/generic/expire) and behaves identically otherwise: replacing the value with [`SET`](/docs/redis/commands/string/set) clears the expiration, while in-place updates keep it, and a negative lifetime deletes the key immediately. The sub-second precision matters for short-lived keys such as locks and rate limit windows.
+
+The optional condition decides when the new expiration is applied: `NX` only when the key has none, `XX` only when it already has one, `GT` only when the new expiration is later than the current one, and `LT` only when it is earlier.
 
 ## Syntax
 
@@ -23313,7 +23431,11 @@ fn main() -> redis::RedisResult<()> {
 # PEXPIREAT
 Source: https://upstash.com/docs/redis/commands/generic/pexpireat
 
-Use `PEXPIREAT` to set expiry as Unix ms timestamp.
+Use `PEXPIREAT` to schedule a key for automatic deletion at a fixed point in time, given as a Unix timestamp in milliseconds.
+
+It combines the absolute deadline of [`EXPIREAT`](/docs/redis/commands/generic/expireat) with the millisecond precision of [`PEXPIRE`](/docs/redis/commands/generic/pexpire), which is what you need when many keys must expire at exactly the same instant. A timestamp in the past deletes the key right away.
+
+The optional condition works as elsewhere: `NX` only when the key has no expiration, `XX` only when it already has one, `GT` only when the new deadline is later than the current one, and `LT` only when it is earlier.
 
 ## Syntax
 
@@ -23486,7 +23608,9 @@ fn main() -> redis::RedisResult<()> {
 # PEXPIRETIME
 Source: https://upstash.com/docs/redis/commands/generic/pexpiretime
 
-Use `PEXPIRETIME` to get expiry as Unix ms timestamp.
+Use `PEXPIRETIME` to read the absolute time at which a key will expire, as a Unix timestamp in milliseconds.
+
+The reply is `-1` when the key exists but has no expiration and `-2` when the key does not exist. It is the millisecond form of [`EXPIRETIME`](/docs/redis/commands/generic/expiretime), and it reports a deadline rather than a remaining lifetime, which makes it the value to compare against a clock when you need to know exactly when something is due.
 
 ## Syntax
 
@@ -23645,7 +23769,9 @@ fn main() -> redis::RedisResult<()> {
 # PTTL
 Source: https://upstash.com/docs/redis/commands/generic/pttl
 
-Use `PTTL` to get TTL in milliseconds.
+Use `PTTL` to read how much longer a key will live, in milliseconds.
+
+The reply is `-1` when the key exists but has no expiration and `-2` when the key does not exist, so a missing key and a permanent one are easy to tell apart. It is the millisecond form of [`TTL`](/docs/redis/commands/generic/ttl), and the extra precision matters for short-lived keys such as locks, where rounding to whole seconds hides most of the remaining lifetime.
 
 ## Syntax
 
@@ -23812,7 +23938,9 @@ fn main() -> redis::RedisResult<()> {
 # RANDOMKEY
 Source: https://upstash.com/docs/redis/commands/generic/randomkey
 
-Use `RANDOMKEY` to return a random key.
+Use `RANDOMKEY` to get the name of a random key from the database without reading its value.
+
+The reply is null when the database is empty. Keys are picked by sampling the keyspace rather than by drawing uniformly from it, and nothing prevents the same key from coming up repeatedly, so treat it as a way to look at a sample of your data while debugging rather than as a way to iterate over it. Use [`SCAN`](/docs/redis/commands/generic/scan) when you need to cover every key.
 
 ## Syntax
 
@@ -23973,7 +24101,11 @@ fn main() -> redis::RedisResult<()> {
 # RENAME
 Source: https://upstash.com/docs/redis/commands/generic/rename
 
-Use `RENAME` to rename a key.
+Use `RENAME` to give an existing key a new name.
+
+The value moves with the key and so does its remaining time to live, and the operation is atomic, so no client ever sees both names or neither. If a key with the destination name already exists it is overwritten and its old value is deleted. Renaming a key that does not exist returns an error.
+
+Use [`RENAMENX`](/docs/redis/commands/generic/renamenx) when the destination must not be overwritten. A common pattern is to build a replacement value under a temporary key and then rename it over the live key, which swaps the data in one atomic step.
 
 ## Syntax
 
@@ -24137,7 +24269,9 @@ fn main() -> redis::RedisResult<()> {
 # RENAMENX
 Source: https://upstash.com/docs/redis/commands/generic/renamenx
 
-Use `RENAMENX` to rename a key if new key doesn't exist.
+Use `RENAMENX` to rename a key only when the new name is not already in use.
+
+The reply is `1` when the rename happened and `0` when the destination already existed and nothing was changed; renaming a key that does not exist returns an error. Because the check and the rename are one atomic step, the command can serve as a way to claim a name: only one of several clients trying to rename onto the same destination succeeds.
 
 ## Syntax
 
@@ -24301,7 +24435,11 @@ fn main() -> redis::RedisResult<()> {
 # RESTORE
 Source: https://upstash.com/docs/redis/commands/generic/restore
 
-Use `RESTORE` to deserialize and restore a key.
+Use `RESTORE` to recreate a key from a payload produced by [`DUMP`](/docs/redis/commands/generic/dump).
+
+`<ttl>` gives the new key a lifetime in milliseconds, where `0` means no expiration; with `ABSTTL` the same number is read as an absolute Unix timestamp in milliseconds instead. The command fails if the key already exists unless `REPLACE` is given.
+
+The payload's version stamp and checksum are verified before anything is written, so a truncated, corrupted, or foreign payload is rejected rather than loaded. `IDLETIME` and `FREQ` seed the eviction metadata of the new key so that a restored key does not automatically look freshly used.
 
 ## Syntax
 
@@ -24469,7 +24607,13 @@ fn main() -> redis::RedisResult<()> {
 # SCAN
 Source: https://upstash.com/docs/redis/commands/generic/scan
 
-Use `SCAN` to incrementally iterate keys.
+Use `SCAN` to walk through the keys of the database incrementally, a batch at a time.
+
+Each call takes a cursor and returns the next cursor together with a batch of keys. Start with cursor `0` and keep calling with the cursor from the previous reply until the server returns `0` again, which marks the end of the iteration. Because the work is split over many short calls, `SCAN` never blocks the server the way [`KEYS`](/docs/redis/commands/generic/keys) can on a large keyspace.
+
+`MATCH` filters the returned keys with a glob-style pattern, `COUNT` hints at how much work each call should do (a hint about effort, not a page size, so batches vary in length), and `TYPE` limits the reply to keys of one type. Filtering is applied after a batch has been read, so a call can legitimately return no keys at all while the cursor is still non-zero: only the cursor tells you when the iteration is over.
+
+The guarantee is that every key present for the whole iteration is returned at least once. Keys added or removed while the scan runs may or may not show up, and a key can be returned more than once, so make the processing of each key idempotent. [`HSCAN`](/docs/redis/commands/hash/hscan), [`SSCAN`](/docs/redis/commands/set/sscan), and [`ZSCAN`](/docs/redis/commands/sorted-set/zscan) apply the same mechanism inside a single collection.
 
 ## Syntax
 
@@ -24640,7 +24784,9 @@ fn main() -> redis::RedisResult<()> {
 # TOUCH
 Source: https://upstash.com/docs/redis/commands/generic/touch
 
-Use `TOUCH` to update last access time of keys.
+Use `TOUCH` to update the last access time of one or more keys without reading their values.
+
+The reply counts how many of the given keys exist, just like [`EXISTS`](/docs/redis/commands/generic/exists), but the call also refreshes the idle time and access frequency that the LRU and LFU eviction policies rely on. That makes it a way to tell the server that a key is still in use, for example to keep a cached value from being evicted while a slower process is still going to need it. It does not change the key's expiration.
 
 ## Syntax
 
@@ -24803,7 +24949,9 @@ fn main() -> redis::RedisResult<()> {
 # TTL
 Source: https://upstash.com/docs/redis/commands/generic/ttl
 
-Use `TTL` to get TTL in seconds.
+Use `TTL` to read how much longer a key will live, in seconds.
+
+The reply is `-1` when the key exists but has no expiration and `-2` when the key does not exist, so these two are never confused with a real remaining lifetime. Values are rounded to whole seconds; use [`PTTL`](/docs/redis/commands/generic/pttl) for millisecond precision and [`EXPIRETIME`](/docs/redis/commands/generic/expiretime) when you want the absolute deadline rather than the time left.
 
 ## Syntax
 
@@ -24970,7 +25118,9 @@ fn main() -> redis::RedisResult<()> {
 # TYPE
 Source: https://upstash.com/docs/redis/commands/generic/type
 
-Use `TYPE` to get the type of a key.
+Use `TYPE` to find out which data type is stored at a key.
+
+The reply is one of `string`, `list`, `set`, `zset`, `hash`, or `stream`, and `none` when the key does not exist. It is the way to dispatch generic code over keys of mixed types, since applying a command to the wrong type fails with a `WRONGTYPE` error, and the way to inspect unfamiliar data before deciding how to read it.
 
 ## Syntax
 
@@ -25135,7 +25285,9 @@ fn main() -> redis::RedisResult<()> {
 # UNLINK
 Source: https://upstash.com/docs/redis/commands/generic/unlink
 
-Use `UNLINK` to delete keys asynchronously.
+Use `UNLINK` to delete keys without freeing their memory in the foreground.
+
+The keys are removed from the keyspace immediately, so from a client's point of view they are gone as soon as the command returns, but the memory of large values is reclaimed by a background thread. That makes it a safer alternative to [`DEL`](/docs/redis/commands/generic/del) for collections with many elements, where freeing memory synchronously can block the server for a noticeable time. The reply counts the keys that existed.
 
 ## Syntax
 
@@ -25298,7 +25450,13 @@ fn main() -> redis::RedisResult<()> {
 # WAIT
 Source: https://upstash.com/docs/redis/commands/generic/wait
 
-Use `WAIT` to wait for replica acknowledgements.
+Use `WAIT` to block until preceding writes have been acknowledged by a number of replicas, or until a timeout expires.
+
+The reply is the number of replicas that acknowledged, which can be lower than `<numreplicas>` when the timeout is reached, so callers must check it instead of assuming success. A timeout of `0` waits indefinitely.
+
+`WAIT` raises the durability you can observe for a write, which is useful right before an action that must not be undone by a failover, such as replying to a payment webhook. It does not make Redis strongly consistent: an acknowledged write can still be lost if the primary and the acknowledging replicas fail together.
+
+On Upstash the command waits for the writes enqueued before it began, including writes made by other connections, which is broader than the per-connection wording used by some Redis clients.
 
 ## Syntax
 
@@ -25461,7 +25619,11 @@ fn main() -> redis::RedisResult<()> {
 # WAITAOF
 Source: https://upstash.com/docs/redis/commands/generic/waitaof
 
-Use `WAITAOF` to wait for local and replica persistence.
+Use `WAITAOF` to block until preceding writes have been persisted to the append-only file locally and on replicas.
+
+`<numlocal>` is how many local acknowledgements to wait for and `<numreplicas>` how many replicas must have persisted the writes. The two-element reply gives the local count first and the replica count second, and either can come back lower than requested when the timeout expires, so both need checking. A timeout of `0` waits indefinitely.
+
+Where [`WAIT`](/docs/redis/commands/generic/wait) confirms only that replicas received a write, `WAITAOF` confirms that it reached persistent storage, which is the stronger guarantee to ask for before acknowledging work that must survive a restart. On Upstash it waits for the writes enqueued before it began, including writes made by other connections.
 
 ## Syntax
 
@@ -25626,7 +25788,11 @@ fn main() -> redis::RedisResult<()> {
 # GEOADD
 Source: https://upstash.com/docs/redis/commands/geo/geoadd
 
-Use `GEOADD` to add geospatial items.
+Use `GEOADD` to add longitude, latitude, and member triples to a geospatial index.
+
+Each position is encoded into a 52-bit geohash and stored as the score of the member in a sorted set, so a geospatial key is an ordinary sorted set and commands such as [`ZREM`](/docs/redis/commands/sorted-set/zrem), [`ZCARD`](/docs/redis/commands/sorted-set/zcard), and [`ZSCAN`](/docs/redis/commands/sorted-set/zscan) work on it. Longitude must be between -180 and 180 and latitude between -85.05112878 and 85.05112878; anything outside those bounds returns an error. Adding a member that is already present moves it to the new position, and the encoding means coordinates read back with [`GEOPOS`](/docs/redis/commands/geo/geopos) are very close to, but not exactly, the ones you stored.
+
+`NX` only adds members that are not there yet, `XX` only updates members that already exist, and `CH` makes the reply count every member that changed rather than only the ones that were added.
 
 ## Syntax
 
@@ -25803,7 +25969,9 @@ fn main() -> redis::RedisResult<()> {
 # GEODIST
 Source: https://upstash.com/docs/redis/commands/geo/geodist
 
-Use `GEODIST` to get distance between two members.
+Use `GEODIST` to get the distance between two members of a geospatial index.
+
+The unit defaults to meters and can be set to `m`, `km`, `ft`, or `mi`. The distance is a great-circle distance computed from the stored positions assuming the Earth is a sphere, so it carries the small error of the geohash encoding and, of course, says nothing about the distance actually travelled on roads. If either member is missing from the index the reply is null.
 
 ## Syntax
 
@@ -25818,7 +25986,7 @@ GEODIST <key> <member1> <member2> [m | km | ft | mi]
 | `<key>` | Yes | No | Redis key targeted by the command. |
 | `<member1>` | Yes | No | First member. |
 | `<member2>` | Yes | No | Second member. |
-| `(m \| km \| ft \| mi)` | No | No | Choose one form: `m`; `km`; `ft`; `mi`. |
+| `(m \| km \| ft \| mi)` | No | No | Distance unit: `m` (meters), `km` (kilometers), `ft` (feet), or `mi` (miles). Defaults to `m` when omitted. |
 
 ## Important points
 
@@ -25975,7 +26143,9 @@ fn main() -> redis::RedisResult<()> {
 # GEOHASH
 Source: https://upstash.com/docs/redis/commands/geo/geohash
 
-Use `GEOHASH` to get geohash strings for members.
+Use `GEOHASH` to get standard Geohash strings for members of a geospatial index.
+
+The reply holds one 11-character string per requested member, in the order requested, with null for members that are not in the index. These are the strings used by geohash.org and by other geospatial tools, which makes the command the right way to export positions or to share them with systems that speak Geohash. They are derived from the stored 52-bit position, so they reflect the same rounding as [`GEOPOS`](/docs/redis/commands/geo/geopos).
 
 ## Syntax
 
@@ -26139,7 +26309,9 @@ fn main() -> redis::RedisResult<()> {
 # GEOPOS
 Source: https://upstash.com/docs/redis/commands/geo/geopos
 
-Use `GEOPOS` to get coordinates of members.
+Use `GEOPOS` to get the longitude and latitude of members of a geospatial index.
+
+The reply holds one entry per requested member, in the order requested, each an array with longitude first and latitude second, and null for members that are not in the index. Positions are decoded from the stored geohash, so they are very close to but not bit-for-bit identical with the coordinates originally passed to [`GEOADD`](/docs/redis/commands/geo/geoadd).
 
 ## Syntax
 
@@ -26303,7 +26475,13 @@ fn main() -> redis::RedisResult<()> {
 # GEORADIUS
 Source: https://upstash.com/docs/redis/commands/geo/georadius
 
-Use `GEORADIUS` to query members within radius.
+Use `GEORADIUS` to find the members of a geospatial index that lie within a given radius of a longitude and latitude point.
+
+By default only member names are returned. `WITHDIST` adds each member's distance from the center in the unit of the query, `WITHCOORD` adds its coordinates, and `WITHHASH` adds its raw 52-bit geohash score. `COUNT` caps the number of results and, combined with `ANY`, lets the server stop as soon as it has enough matches instead of examining the whole area, which is faster but returns an arbitrary subset rather than the nearest ones. `ASC` and `DESC` sort the results by distance from the center.
+
+`STORE` writes the matching members into a sorted set scored by geohash, so the result stays usable as a geospatial index, while `STOREDIST` scores them by their distance from the center, which makes the result easy to page through by proximity.
+
+Redis deprecated `GEORADIUS` in favor of [`GEOSEARCH`](/docs/redis/commands/geo/geosearch) and [`GEOSEARCHSTORE`](/docs/redis/commands/geo/geosearchstore), which do the same work and additionally support rectangular areas. Use [`GEORADIUS_RO`](/docs/redis/commands/geo/georadius-ro) if you want a form that cannot write.
 
 ## Syntax
 
@@ -26319,13 +26497,13 @@ GEORADIUS <key> <longitude> <latitude> <radius> (m | km | ft | mi) [WITHCOORD] [
 | `<longitude>` | Yes | No | Longitude in degrees, from -180 to 180. |
 | `<latitude>` | Yes | No | Latitude in degrees, from -85.05112878 to 85.05112878. |
 | `<radius>` | Yes | No | Search radius, in the unit given after it. |
-| `(m \| km \| ft \| mi)` | Yes | No | Choose one form: `m`; `km`; `ft`; `mi`. |
+| `(m \| km \| ft \| mi)` | Yes | No | Distance unit: `m` (meters), `km` (kilometers), `ft` (feet), or `mi` (miles). |
 | `WITHCOORD` | No | No | Also return the longitude and latitude of each match. |
 | `WITHDIST` | No | No | Also return the distance from the center, in the requested unit. |
 | `WITHHASH` | No | No | Also return the raw 52-bit geohash score of each match. |
 | `COUNT <count> [ANY]` | No | No | Return at most `<count>` matches. `ANY` returns as soon as enough matches are found, instead of sorting every match first. |
-| `(ASC \| DESC)` | No | No | Choose one form: `ASC`; `DESC`. |
-| `(STORE <storekey> \| STOREDIST <storedistkey>)` | No | No | Choose one form: `STORE`; `STOREDIST`. |
+| `(ASC \| DESC)` | No | No | Sort the matches by distance from the center: `ASC` (nearest first) or `DESC` (farthest first). Unsorted when omitted. |
+| `(STORE <storekey> \| STOREDIST <storedistkey>)` | No | No | Store the matches in a sorted set instead of returning them: `STORE` scores them by geohash, so the destination stays a geospatial index, and `STOREDIST` scores them by their distance from the center. |
 
 ## Response
 
@@ -26476,7 +26654,11 @@ fn main() -> redis::RedisResult<()> {
 # GEORADIUS_RO
 Source: https://upstash.com/docs/redis/commands/geo/georadius-ro
 
-Use `GEORADIUS_RO` to find members within a radius of a point. It is the read-only form of `GEORADIUS`.
+Use `GEORADIUS_RO` to find members within a radius of a point. It is the read-only form of [`GEORADIUS`](/docs/redis/commands/geo/georadius).
+
+It accepts the same query and the same `WITHCOORD`, `WITHDIST`, `WITHHASH`, `COUNT`, and sorting options, but it has no `STORE` or `STOREDIST` clause, so the server knows the call cannot write and can serve it on replicas and from read-only scripts.
+
+Like `GEORADIUS`, it is deprecated in favor of [`GEOSEARCH`](/docs/redis/commands/geo/geosearch), which is read-only as well and also supports rectangular areas.
 
 ## Syntax
 
@@ -26492,12 +26674,12 @@ GEORADIUS_RO <key> <longitude> <latitude> <radius> (m | km | ft | mi) [WITHCOORD
 | `<longitude>` | Yes | No | Longitude in degrees, from -180 to 180. |
 | `<latitude>` | Yes | No | Latitude in degrees, from -85.05112878 to 85.05112878. |
 | `<radius>` | Yes | No | Search radius, in the unit given after it. |
-| `(m \| km \| ft \| mi)` | Yes | No | Choose one form: `m`; `km`; `ft`; `mi`. |
+| `(m \| km \| ft \| mi)` | Yes | No | Distance unit: `m` (meters), `km` (kilometers), `ft` (feet), or `mi` (miles). |
 | `WITHCOORD` | No | No | Also return the longitude and latitude of each match. |
 | `WITHDIST` | No | No | Also return the distance from the center, in the requested unit. |
 | `WITHHASH` | No | No | Also return the raw 52-bit geohash score of each match. |
 | `COUNT <count> [ANY]` | No | No | Return at most `<count>` matches. `ANY` returns as soon as enough matches are found, instead of sorting every match first. |
-| `(ASC \| DESC)` | No | No | Choose one form: `ASC`; `DESC`. |
+| `(ASC \| DESC)` | No | No | Sort the matches by distance from the center: `ASC` (nearest first) or `DESC` (farthest first). Unsorted when omitted. |
 
 ## Response
 
@@ -26648,7 +26830,11 @@ fn main() -> redis::RedisResult<()> {
 # GEORADIUSBYMEMBER
 Source: https://upstash.com/docs/redis/commands/geo/georadiusbymember
 
-Use `GEORADIUSBYMEMBER` to radius query centered on member.
+Use `GEORADIUSBYMEMBER` to find the members of a geospatial index that lie within a given radius of another member.
+
+It works exactly like [`GEORADIUS`](/docs/redis/commands/geo/georadius) except that the center is the stored position of a member instead of an explicit coordinate pair, which saves a lookup when the reference point is already in the index (a store, a driver, a landmark). The reference member itself always matches, since its distance from itself is zero, so remember to filter it out or ask for one result more than you need.
+
+The same `WITHCOORD`, `WITHDIST`, `WITHHASH`, `COUNT`, sorting, and `STORE` or `STOREDIST` options apply. Redis deprecated the command in favor of [`GEOSEARCH`](/docs/redis/commands/geo/geosearch) with `FROMMEMBER`.
 
 ## Syntax
 
@@ -26663,13 +26849,13 @@ GEORADIUSBYMEMBER <key> <member> <radius> (m | km | ft | mi) [WITHCOORD] [WITHDI
 | `<key>` | Yes | No | Redis key targeted by the command. |
 | `<member>` | Yes | No | Member name. |
 | `<radius>` | Yes | No | Search radius, in the unit given after it. |
-| `(m \| km \| ft \| mi)` | Yes | No | Choose one form: `m`; `km`; `ft`; `mi`. |
+| `(m \| km \| ft \| mi)` | Yes | No | Distance unit: `m` (meters), `km` (kilometers), `ft` (feet), or `mi` (miles). |
 | `WITHCOORD` | No | No | Also return the longitude and latitude of each match. |
 | `WITHDIST` | No | No | Also return the distance from the center, in the requested unit. |
 | `WITHHASH` | No | No | Also return the raw 52-bit geohash score of each match. |
 | `COUNT <count> [ANY]` | No | No | Return at most `<count>` matches. `ANY` returns as soon as enough matches are found, instead of sorting every match first. |
-| `(ASC \| DESC)` | No | No | Choose one form: `ASC`; `DESC`. |
-| `(STORE <storekey> \| STOREDIST <storedistkey>)` | No | No | Choose one form: `STORE`; `STOREDIST`. |
+| `(ASC \| DESC)` | No | No | Sort the matches by distance from the center: `ASC` (nearest first) or `DESC` (farthest first). Unsorted when omitted. |
+| `(STORE <storekey> \| STOREDIST <storedistkey>)` | No | No | Store the matches in a sorted set instead of returning them: `STORE` scores them by geohash, so the destination stays a geospatial index, and `STOREDIST` scores them by their distance from the center. |
 
 ## Response
 
@@ -26819,7 +27005,11 @@ fn main() -> redis::RedisResult<()> {
 # GEORADIUSBYMEMBER_RO
 Source: https://upstash.com/docs/redis/commands/geo/georadiusbymember-ro
 
-Use `GEORADIUSBYMEMBER_RO` to find members within a radius of another member. It is the read-only form of `GEORADIUSBYMEMBER`.
+Use `GEORADIUSBYMEMBER_RO` to find members within a radius of another member. It is the read-only form of [`GEORADIUSBYMEMBER`](/docs/redis/commands/geo/georadiusbymember).
+
+The center is the stored position of the given member, which always appears among the matches at distance zero. The command accepts the same `WITHCOORD`, `WITHDIST`, `WITHHASH`, `COUNT`, and sorting options but has no `STORE` or `STOREDIST` clause, so it can be served on replicas and used from read-only scripts.
+
+Like the writable form, it is deprecated in favor of [`GEOSEARCH`](/docs/redis/commands/geo/geosearch) with `FROMMEMBER`.
 
 ## Syntax
 
@@ -26834,12 +27024,12 @@ GEORADIUSBYMEMBER_RO <key> <member> <radius> (m | km | ft | mi) [WITHCOORD] [WIT
 | `<key>` | Yes | No | Redis key targeted by the command. |
 | `<member>` | Yes | No | Member name. |
 | `<radius>` | Yes | No | Search radius, in the unit given after it. |
-| `(m \| km \| ft \| mi)` | Yes | No | Choose one form: `m`; `km`; `ft`; `mi`. |
+| `(m \| km \| ft \| mi)` | Yes | No | Distance unit: `m` (meters), `km` (kilometers), `ft` (feet), or `mi` (miles). |
 | `WITHCOORD` | No | No | Also return the longitude and latitude of each match. |
 | `WITHDIST` | No | No | Also return the distance from the center, in the requested unit. |
 | `WITHHASH` | No | No | Also return the raw 52-bit geohash score of each match. |
 | `COUNT <count> [ANY]` | No | No | Return at most `<count>` matches. `ANY` returns as soon as enough matches are found, instead of sorting every match first. |
-| `(ASC \| DESC)` | No | No | Choose one form: `ASC`; `DESC`. |
+| `(ASC \| DESC)` | No | No | Sort the matches by distance from the center: `ASC` (nearest first) or `DESC` (farthest first). Unsorted when omitted. |
 
 ## Response
 
@@ -26989,7 +27179,13 @@ fn main() -> redis::RedisResult<()> {
 # GEOSEARCH
 Source: https://upstash.com/docs/redis/commands/geo/geosearch
 
-Use `GEOSEARCH` to search for members in an area.
+Use `GEOSEARCH` to find the members of a geospatial index that fall inside a circle or a rectangle.
+
+The center is either an existing member of the index (`FROMMEMBER`) or an explicit coordinate pair (`FROMLONLAT`). The area is either a circle of a given radius (`BYRADIUS`) or an axis-aligned box of a given width and height centered on that point (`BYBOX`), which is the shape to use when you are covering a map viewport rather than a "within N km" question.
+
+By default only member names come back. `WITHDIST` adds the distance from the center in the unit of the query, `WITHCOORD` the member's coordinates, and `WITHHASH` its raw geohash score. `ASC` and `DESC` sort by distance, and `COUNT` caps the number of results; adding `ANY` lets the server return as soon as it has enough matches, which is faster but no longer gives you the nearest ones.
+
+`GEOSEARCH` replaces the deprecated `GEORADIUS` and `GEORADIUSBYMEMBER` commands and is the command to use for new code. Use [`GEOSEARCHSTORE`](/docs/redis/commands/geo/geosearchstore) when the result should be stored instead of returned.
 
 ## Syntax
 
@@ -27002,9 +27198,9 @@ GEOSEARCH <key> (FROMMEMBER <member> | FROMLONLAT <longitude> <latitude>) (BYRAD
 | Argument | Required | Repeatable | Description |
 | --- | --- | --- | --- |
 | `<key>` | Yes | No | Redis key targeted by the command. |
-| `(FROMMEMBER <member> \| FROMLONLAT <longitude> <latitude>)` | Yes | No | Choose one form: `FROMMEMBER`; `FROMLONLAT`. |
-| `(BYRADIUS <radius> (m \| km \| ft \| mi) \| BYBOX <width> <height> (m \| km \| ft \| mi))` | Yes | No | Choose one form: `BYRADIUS`; `m`; `km`; `ft`; `mi`; `BYBOX`; `m`; `km`; `ft`; `mi`. |
-| `(ASC \| DESC)` | No | No | Choose one form: `ASC`; `DESC`. |
+| `(FROMMEMBER <member> \| FROMLONLAT <longitude> <latitude>)` | Yes | No | Where to center the search: `FROMMEMBER` uses the stored position of an existing member, `FROMLONLAT` uses the given coordinates. |
+| `(BYRADIUS <radius> (m \| km \| ft \| mi) \| BYBOX <width> <height> (m \| km \| ft \| mi))` | Yes | No | The area to search: `BYRADIUS` a circle of the given radius, `BYBOX` an axis-aligned box of the given width and height centered on the search point. The unit is `m` (meters), `km` (kilometers), `ft` (feet), or `mi` (miles). |
+| `(ASC \| DESC)` | No | No | Sort the matches by distance from the center: `ASC` (nearest first) or `DESC` (farthest first). Unsorted when omitted. |
 | `COUNT <count> [ANY]` | No | No | Return at most `<count>` matches. `ANY` returns as soon as enough matches are found, instead of sorting every match first. |
 | `WITHCOORD` | No | No | Also return the longitude and latitude of each match. |
 | `WITHDIST` | No | No | Also return the distance from the center, in the requested unit. |
@@ -27167,7 +27363,11 @@ fn main() -> redis::RedisResult<()> {
 # GEOSEARCHSTORE
 Source: https://upstash.com/docs/redis/commands/geo/geosearchstore
 
-Use `GEOSEARCHSTORE` to store geosearch results.
+Use `GEOSEARCHSTORE` to run the same query as [`GEOSEARCH`](/docs/redis/commands/geo/geosearch) and store the matching members in another key instead of returning them.
+
+The destination is a sorted set holding the matches. By default their scores are the raw geohash values, so the destination is itself a valid geospatial index that can be queried further; with `STOREDIST` the score is the distance from the center in the unit of the query, which turns the result into a proximity-ordered list you can page through with [`ZRANGE`](/docs/redis/commands/sorted-set/zrange).
+
+The destination is overwritten on every call, and it is deleted when the query matches nothing. The reply is the number of members stored. This is the usual way to materialize a "nearby" result once and then reuse it for pagination or further set operations.
 
 ## Syntax
 
@@ -27181,9 +27381,9 @@ GEOSEARCHSTORE <destination> <source> (FROMMEMBER <member> | FROMLONLAT <longitu
 | --- | --- | --- | --- |
 | `<destination>` | Yes | No | Redis key used as destination. |
 | `<source>` | Yes | No | Redis key used as source. |
-| `(FROMMEMBER <member> \| FROMLONLAT <longitude> <latitude>)` | Yes | No | Choose one form: `FROMMEMBER`; `FROMLONLAT`. |
-| `(BYRADIUS <radius> (m \| km \| ft \| mi) \| BYBOX <width> <height> (m \| km \| ft \| mi))` | Yes | No | Choose one form: `BYRADIUS`; `m`; `km`; `ft`; `mi`; `BYBOX`; `m`; `km`; `ft`; `mi`. |
-| `(ASC \| DESC)` | No | No | Choose one form: `ASC`; `DESC`. |
+| `(FROMMEMBER <member> \| FROMLONLAT <longitude> <latitude>)` | Yes | No | Where to center the search: `FROMMEMBER` uses the stored position of an existing member, `FROMLONLAT` uses the given coordinates. |
+| `(BYRADIUS <radius> (m \| km \| ft \| mi) \| BYBOX <width> <height> (m \| km \| ft \| mi))` | Yes | No | The area to search: `BYRADIUS` a circle of the given radius, `BYBOX` an axis-aligned box of the given width and height centered on the search point. The unit is `m` (meters), `km` (kilometers), `ft` (feet), or `mi` (miles). |
+| `(ASC \| DESC)` | No | No | Sort the matches by distance from the center: `ASC` (nearest first) or `DESC` (farthest first). Unsorted when omitted. |
 | `COUNT <count> [ANY]` | No | No | Return at most `<count>` matches. `ANY` returns as soon as enough matches are found, instead of sorting every match first. |
 | `STOREDIST` | No | No | Store each match's distance from the center instead of its geohash score. |
 
@@ -27351,9 +27551,9 @@ Source: https://upstash.com/docs/redis/commands/geo/overview
 <Card title="GEODIST" href="/redis/commands/geo/geodist">Get distance between two members</Card>
 <Card title="GEOHASH" href="/redis/commands/geo/geohash">Get geohash strings for members</Card>
 <Card title="GEOPOS" href="/redis/commands/geo/geopos">Get coordinates of members</Card>
-<Card title="GEORADIUS" href="/redis/commands/geo/georadius">Query members within radius</Card>
+<Card title="GEORADIUS" href="/redis/commands/geo/georadius">Find members within a radius of a point</Card>
 <Card title="GEORADIUS_RO" href="/redis/commands/geo/georadius-ro">Read-only radius query</Card>
-<Card title="GEORADIUSBYMEMBER" href="/redis/commands/geo/georadiusbymember">Radius query centered on member</Card>
+<Card title="GEORADIUSBYMEMBER" href="/redis/commands/geo/georadiusbymember">Find members within a radius of another member</Card>
 <Card title="GEORADIUSBYMEMBER_RO" href="/redis/commands/geo/georadiusbymember-ro">Read-only radius query by member</Card>
 <Card title="GEOSEARCH" href="/redis/commands/geo/geosearch">Search for members in an area</Card>
 <Card title="GEOSEARCHSTORE" href="/redis/commands/geo/geosearchstore">Store geosearch results</Card>
@@ -27362,7 +27562,9 @@ Source: https://upstash.com/docs/redis/commands/geo/overview
 # HDEL
 Source: https://upstash.com/docs/redis/commands/hash/hdel
 
-Use `HDEL` to delete one or more hash fields.
+Use `HDEL` to remove one or more fields from a hash.
+
+The reply counts only the fields that were actually present, so deleting a field that is already gone is not an error. When the last field of a hash is removed the key itself is deleted, because Redis does not keep empty collections.
 
 ## Syntax
 
@@ -27527,7 +27729,9 @@ fn main() -> redis::RedisResult<()> {
 # HEXISTS
 Source: https://upstash.com/docs/redis/commands/hash/hexists
 
-Use `HEXISTS` to check if a hash field exists.
+Use `HEXISTS` to check whether a field is present in a hash.
+
+The reply is `1` when the field exists and `0` when either the field or the key is missing. Since the value is never transferred, this is the cheap way to test for presence, and it is also how you tell a missing field apart from a field whose value happens to be empty, which [`HGET`](/docs/redis/commands/hash/hget) cannot do.
 
 ## Syntax
 
@@ -27694,7 +27898,13 @@ fn main() -> redis::RedisResult<()> {
 # HEXPIRE
 Source: https://upstash.com/docs/redis/commands/hash/hexpire
 
-Use `HEXPIRE` to set field TTL in seconds.
+Use `HEXPIRE` to give individual hash fields a lifetime in seconds, after which those fields are removed from the hash.
+
+Expiration here is per field, not per key: the hash itself stays alive as long as it still has fields, and the key is deleted automatically when the last surviving field expires. This makes it possible to keep short-lived and long-lived data in one hash, for example a user record whose verification code expires while the rest of the record stays.
+
+`FIELDS <numfields>` introduces the list of fields and the count must match the number of names that follow. The optional condition works as it does on [`EXPIRE`](/docs/redis/commands/generic/expire): `NX` only when the field has no expiration, `XX` only when it already has one, `GT` only when the new expiration is later than the current one, and `LT` only when it is earlier.
+
+The reply holds one status code per field, in order: `1` when the expiration was set, `0` when the condition prevented it, `2` when the field was deleted immediately because the given lifetime was zero or negative, and `-2` when the field does not exist.
 
 ## Syntax
 
@@ -27868,7 +28078,13 @@ fn main() -> redis::RedisResult<()> {
 # HEXPIREAT
 Source: https://upstash.com/docs/redis/commands/hash/hexpireat
 
-Use `HEXPIREAT` to set field expiry as timestamp.
+Use `HEXPIREAT` to schedule individual hash fields for deletion at a fixed point in time, given as a Unix timestamp in seconds.
+
+It is the absolute-deadline form of [`HEXPIRE`](/docs/redis/commands/hash/hexpire), which is what you want when several fields, or fields across several hashes, must expire at the same moment. A timestamp in the past removes the fields right away. The key is deleted when its last field expires.
+
+`FIELDS <numfields>` introduces the field list and the count must match. The optional condition applies the deadline only in certain cases: `NX` when the field has no expiration, `XX` when it already has one, `GT` when the new deadline is later than the current one, and `LT` when it is earlier.
+
+The reply holds one status code per field: `1` when the expiration was set, `0` when the condition prevented it, `2` when the field was deleted immediately, and `-2` when the field does not exist.
 
 ## Syntax
 
@@ -28042,7 +28258,9 @@ fn main() -> redis::RedisResult<()> {
 # HEXPIRETIME
 Source: https://upstash.com/docs/redis/commands/hash/hexpiretime
 
-Use `HEXPIRETIME` to get field expiry as timestamp.
+Use `HEXPIRETIME` to read the absolute expiration time of hash fields, as Unix timestamps in seconds.
+
+The reply holds one value per requested field, in order: the timestamp when the field expires, `-1` when the field exists but has no expiration, and `-2` when the field or the key does not exist. Use [`HTTL`](/docs/redis/commands/hash/httl) when you want the remaining lifetime instead of the deadline, and [`HPEXPIRETIME`](/docs/redis/commands/hash/hpexpiretime) for millisecond precision.
 
 ## Syntax
 
@@ -28213,7 +28431,9 @@ fn main() -> redis::RedisResult<()> {
 # HGET
 Source: https://upstash.com/docs/redis/commands/hash/hget
 
-Use `HGET` to get the value of a hash field.
+Use `HGET` to read the value of a single field of a hash.
+
+The reply is null when either the field or the whole key is missing, so the two cases cannot be told apart from the reply alone; use [`HEXISTS`](/docs/redis/commands/hash/hexists) when that difference matters. To read several fields use [`HMGET`](/docs/redis/commands/hash/hmget) rather than repeated calls, and to read all of them use [`HGETALL`](/docs/redis/commands/hash/hgetall).
 
 ## Syntax
 
@@ -28379,7 +28599,11 @@ fn main() -> redis::RedisResult<()> {
 # HGETALL
 Source: https://upstash.com/docs/redis/commands/hash/hgetall
 
-Use `HGETALL` to get all fields and values.
+Use `HGETALL` to read every field and value of a hash in one call.
+
+The reply pairs each field with its value. RESP2 flattens it into a single alternating array while RESP3 returns a map, and client libraries normally decode either form into a native dictionary. A missing key returns an empty result rather than an error.
+
+The whole hash is transferred, so on hashes with many fields prefer [`HMGET`](/docs/redis/commands/hash/hmget) when you know which fields you need, or [`HSCAN`](/docs/redis/commands/hash/hscan) to walk the hash in batches.
 
 ## Syntax
 
@@ -28551,7 +28775,11 @@ fn main() -> redis::RedisResult<()> {
 # HGETDEL
 Source: https://upstash.com/docs/redis/commands/hash/hgetdel
 
-Use `HGETDEL` to get and delete hash fields.
+Use `HGETDEL` to read hash fields and delete them in the same atomic step.
+
+The reply holds the previous value of each requested field, in the order requested, with null for fields that were not present. Reading and removing together removes the race that an [`HGET`](/docs/redis/commands/hash/hget) followed by an [`HDEL`](/docs/redis/commands/hash/hdel) would leave open, which makes the command a good fit for one-shot values such as one-time codes, claim tickets, or queued items keyed by name: exactly one caller gets the value.
+
+`FIELDS <numfields>` introduces the field list and the count must match. The key is deleted when its last field is removed.
 
 ## Syntax
 
@@ -28724,7 +28952,11 @@ fn main() -> redis::RedisResult<()> {
 # HGETEX
 Source: https://upstash.com/docs/redis/commands/hash/hgetex
 
-Use `HGETEX` to get fields and set their expiry.
+Use `HGETEX` to read hash fields and change their expiration in the same call.
+
+Without an expiration option it simply returns the values, like [`HMGET`](/docs/redis/commands/hash/hmget). `EX`, `PX`, `EXAT`, and `PXAT` give every requested field a new lifetime or deadline, and `PERSIST` removes the expiration so the fields stop expiring altogether.
+
+Doing both in one command is what makes sliding expirations possible per field: reading a session attribute can extend it, with no window in which another client sees the field without its refreshed lifetime. `FIELDS <numfields>` introduces the field list and the count must match.
 
 ## Syntax
 
@@ -28737,7 +28969,7 @@ HGETEX <key> [EX <seconds> | PX <milliseconds> | EXAT <unix-time-seconds> | PXAT
 | Argument | Required | Repeatable | Description |
 | --- | --- | --- | --- |
 | `<key>` | Yes | No | Redis key targeted by the command. |
-| `(EX <seconds> \| PX <milliseconds> \| EXAT <unix-time-seconds> \| PXAT <unix-time-milliseconds> \| PERSIST)` | No | No | Choose one form: `EX` (set a lifetime in seconds); `PX` (set a lifetime in milliseconds); `EXAT` (expire at a Unix timestamp in seconds); `PXAT` (expire at a Unix timestamp in milliseconds); `PERSIST`. |
+| `(EX <seconds> \| PX <milliseconds> \| EXAT <unix-time-seconds> \| PXAT <unix-time-milliseconds> \| PERSIST)` | No | No | Choose one form: `EX` (set a lifetime in seconds); `PX` (set a lifetime in milliseconds); `EXAT` (expire at a Unix timestamp in seconds); `PXAT` (expire at a Unix timestamp in milliseconds); `PERSIST` (remove the expiration). Left unchanged when omitted. |
 | `FIELDS <numfields> <field> [<field> ...]` | Yes | No | Fields to target. Give the field count first, then that many field names. |
 
 ## Response
@@ -28893,7 +29125,11 @@ fn main() -> redis::RedisResult<()> {
 # HINCRBY
 Source: https://upstash.com/docs/redis/commands/hash/hincrby
 
-Use `HINCRBY` to increment integer value of a field.
+Use `HINCRBY` to add an integer to the number stored in a hash field and get the result.
+
+A missing field, or a missing key, is treated as `0`, so the first call creates the hash and the field. The increment may be negative to count down. The stored value must be the string form of a 64-bit signed integer; anything else returns an error, as does an operation that would overflow the range.
+
+Reading, adding, and writing back happen as one atomic step, so concurrent callers each receive a distinct result and no update is lost. That makes hashes a compact way to keep many related counters, such as per-status counts for one entity, under a single key.
 
 ## Syntax
 
@@ -29062,7 +29298,11 @@ fn main() -> redis::RedisResult<()> {
 # HINCRBYFLOAT
 Source: https://upstash.com/docs/redis/commands/hash/hincrbyfloat
 
-Use `HINCRBYFLOAT` to increment float value of a field.
+Use `HINCRBYFLOAT` to add a floating point number to the value of a hash field and get the result.
+
+The stored value and the increment are parsed as double precision floats, and a missing field or key counts as `0`. The increment may be negative, and there is no separate decrement command. A value that is not a valid number returns an error.
+
+The reply is the new value as a string, which client libraries usually decode into a native number. Note that the result is stored in the same textual form, so repeated increments of values that cannot be represented exactly in binary floating point accumulate the usual rounding error; keep money and similar quantities in integer units and use [`HINCRBY`](/docs/redis/commands/hash/hincrby).
 
 ## Syntax
 
@@ -29235,7 +29475,9 @@ fn main() -> redis::RedisResult<()> {
 # HKEYS
 Source: https://upstash.com/docs/redis/commands/hash/hkeys
 
-Use `HKEYS` to get all fields in a hash.
+Use `HKEYS` to get the names of all the fields in a hash, without their values.
+
+A missing key returns an empty list. The whole field list is built and transferred in one reply, so on large hashes prefer [`HSCAN`](/docs/redis/commands/hash/hscan) with `NOVALUES`, which walks the field names in batches instead.
 
 ## Syntax
 
@@ -29403,7 +29645,9 @@ fn main() -> redis::RedisResult<()> {
 # HLEN
 Source: https://upstash.com/docs/redis/commands/hash/hlen
 
-Use `HLEN` to get number of fields in a hash.
+Use `HLEN` to get the number of fields in a hash.
+
+The reply is `0` when the key does not exist. The count is kept by Redis rather than computed, so it is cheap whatever the size of the hash, which makes it the right way to check how big a hash has grown before deciding to read or iterate it.
 
 ## Syntax
 
@@ -29571,7 +29815,11 @@ fn main() -> redis::RedisResult<()> {
 # HMGET
 Source: https://upstash.com/docs/redis/commands/hash/hmget
 
-Use `HMGET` to get values of multiple fields.
+Use `HMGET` to read several fields of a hash in one call.
+
+The reply holds one entry per requested field, in the order requested, with null for fields that do not exist. Asking for fields of a key that does not exist returns a list of nulls rather than an error, so the shape of the reply is always predictable and can be zipped back onto your list of field names.
+
+It saves the round trips of repeated [`HGET`](/docs/redis/commands/hash/hget) calls and transfers far less than [`HGETALL`](/docs/redis/commands/hash/hgetall) when you only need a few fields of a large hash.
 
 ## Syntax
 
@@ -29741,7 +29989,9 @@ fn main() -> redis::RedisResult<()> {
 # HMSET
 Source: https://upstash.com/docs/redis/commands/hash/hmset
 
-Use `HMSET` to set multiple hash fields.
+Use `HMSET` to set several field and value pairs of a hash in one call, creating the key if it does not exist.
+
+Existing fields are overwritten and the reply is always `OK`, so it says nothing about what changed. `HMSET` is deprecated in Redis: [`HSET`](/docs/redis/commands/hash/hset) accepts multiple pairs as well and additionally reports how many fields were new, so prefer it in new code.
 
 ## Syntax
 
@@ -29905,7 +30155,11 @@ fn main() -> redis::RedisResult<()> {
 # HPERSIST
 Source: https://upstash.com/docs/redis/commands/hash/hpersist
 
-Use `HPERSIST` to remove field expiration.
+Use `HPERSIST` to remove the expiration from hash fields so that they stop being deleted automatically.
+
+The reply holds one status code per requested field, in order: `1` when an expiration was removed, `-1` when the field exists but had no expiration, and `-2` when the field or the key does not exist. This is how a field set by [`HEXPIRE`](/docs/redis/commands/hash/hexpire) or [`HSETEX`](/docs/redis/commands/hash/hsetex) is promoted from temporary to permanent without rewriting its value.
+
+`FIELDS <numfields>` introduces the field list and the count must match.
 
 ## Syntax
 
@@ -30074,7 +30328,11 @@ fn main() -> redis::RedisResult<()> {
 # HPEXPIRE
 Source: https://upstash.com/docs/redis/commands/hash/hpexpire
 
-Use `HPEXPIRE` to set field TTL in milliseconds.
+Use `HPEXPIRE` to give individual hash fields a lifetime in milliseconds, after which those fields are removed from the hash.
+
+It is the millisecond form of [`HEXPIRE`](/docs/redis/commands/hash/hexpire) and behaves identically otherwise: expiration is per field, the hash survives as long as it has fields, and the key disappears when the last field expires. The finer precision matters for short-lived fields such as per-field locks or rate limit windows.
+
+`FIELDS <numfields>` introduces the field list and the count must match. The optional condition applies the new lifetime only in certain cases: `NX` when the field has no expiration, `XX` when it already has one, `GT` when the new expiration is later than the current one, and `LT` when it is earlier. The reply holds one status code per field: `1` when set, `0` when the condition prevented it, `2` when the field was deleted immediately, and `-2` when it does not exist.
 
 ## Syntax
 
@@ -30248,7 +30506,11 @@ fn main() -> redis::RedisResult<()> {
 # HPEXPIREAT
 Source: https://upstash.com/docs/redis/commands/hash/hpexpireat
 
-Use `HPEXPIREAT` to set field expiry as ms timestamp.
+Use `HPEXPIREAT` to schedule individual hash fields for deletion at a fixed point in time, given as a Unix timestamp in milliseconds.
+
+It combines the absolute deadline of [`HEXPIREAT`](/docs/redis/commands/hash/hexpireat) with millisecond precision, which is what you need when fields spread over several hashes have to expire at exactly the same instant. A timestamp in the past removes the fields right away, and the key is deleted when its last field expires.
+
+`FIELDS <numfields>` introduces the field list and the count must match. The optional condition applies the deadline only when the field has no expiration (`NX`), already has one (`XX`), or when the new deadline is later (`GT`) or earlier (`LT`) than the current one. The reply holds one status code per field: `1` when set, `0` when the condition prevented it, `2` when the field was deleted immediately, and `-2` when it does not exist.
 
 ## Syntax
 
@@ -30422,7 +30684,9 @@ fn main() -> redis::RedisResult<()> {
 # HPEXPIRETIME
 Source: https://upstash.com/docs/redis/commands/hash/hpexpiretime
 
-Use `HPEXPIRETIME` to get field expiry as ms timestamp.
+Use `HPEXPIRETIME` to read the absolute expiration time of hash fields, as Unix timestamps in milliseconds.
+
+The reply holds one value per requested field, in order: the timestamp at which it expires, `-1` when the field exists but has no expiration, and `-2` when the field or the key does not exist. It is the millisecond form of [`HEXPIRETIME`](/docs/redis/commands/hash/hexpiretime) and reports a deadline rather than the time left, which is the value to compare against a clock.
 
 ## Syntax
 
@@ -30594,7 +30858,9 @@ fn main() -> redis::RedisResult<()> {
 # HPTTL
 Source: https://upstash.com/docs/redis/commands/hash/hpttl
 
-Use `HPTTL` to get field TTL in milliseconds.
+Use `HPTTL` to read how much longer hash fields will live, in milliseconds.
+
+The reply holds one value per requested field, in order: the remaining lifetime, `-1` when the field exists but has no expiration, and `-2` when the field or the key does not exist. It is the millisecond form of [`HTTL`](/docs/redis/commands/hash/httl), and the extra precision matters for fields that live for less than a second.
 
 ## Syntax
 
@@ -30766,7 +31032,11 @@ fn main() -> redis::RedisResult<()> {
 # HRANDFIELD
 Source: https://upstash.com/docs/redis/commands/hash/hrandfield
 
-Use `HRANDFIELD` to get random fields from a hash.
+Use `HRANDFIELD` to get one or more random fields from a hash.
+
+Without a count a single field name is returned, or null when the key does not exist. A positive count returns up to that many distinct fields, capped at the size of the hash, while a negative count returns exactly that many fields chosen independently, so the same field can come up more than once. `WITHVALUES` returns each field together with its value.
+
+Nothing is removed from the hash, which is the difference from [`HGETDEL`](/docs/redis/commands/hash/hgetdel): use this for sampling, random selection, and quick inspection of an unfamiliar hash.
 
 ## Syntax
 
@@ -30940,7 +31210,11 @@ fn main() -> redis::RedisResult<()> {
 # HSCAN
 Source: https://upstash.com/docs/redis/commands/hash/hscan
 
-Use `HSCAN` to incrementally iterate hash fields.
+Use `HSCAN` to iterate the fields of a hash in batches instead of reading it all at once.
+
+Each call takes a cursor and returns the next cursor together with a batch of field and value pairs. Start at cursor `0` and keep calling with the cursor from the previous reply until the server returns `0`, which ends the iteration. Because each call does a bounded amount of work, this avoids the long single reply that [`HGETALL`](/docs/redis/commands/hash/hgetall) produces on a large hash.
+
+`MATCH` filters field names with a glob-style pattern, `COUNT` hints at how much work each call should do, and `NOVALUES` returns field names only, which is noticeably cheaper when values are large and you do not need them. Filtering is applied after a batch has been read, so a call can return nothing while the cursor is still non-zero: only a cursor of `0` means the iteration is over. Fields present for the whole iteration are returned at least once, and fields added or removed while it runs may or may not appear.
 
 ## Syntax
 
@@ -31120,7 +31394,11 @@ fn main() -> redis::RedisResult<()> {
 # HSET
 Source: https://upstash.com/docs/redis/commands/hash/hset
 
-Use `HSET` to set hash field values.
+Use `HSET` to set one or more fields of a hash to the given values, creating the key when it does not exist.
+
+Existing fields are overwritten, and the reply counts only the fields that were added, not those that were updated, which is how you tell an insert from an update. Setting fields does not touch the key's time to live, so a hash with an expiration keeps it as it is written to. A field's own expiration is a different matter: writing a field clears the TTL it may have been given by [`HEXPIRE`](/docs/redis/commands/hash/hexpire) or [`HSETEX`](/docs/redis/commands/hash/hsetex).
+
+Hashes are the compact way to store an object under one key: field access with `HSET` and [`HGET`](/docs/redis/commands/hash/hget) avoids reading and rewriting the whole value the way a serialized string would.
 
 ## Syntax
 
@@ -31288,7 +31566,11 @@ fn main() -> redis::RedisResult<()> {
 # HSETEX
 Source: https://upstash.com/docs/redis/commands/hash/hsetex
 
-Use `HSETEX` to set fields with expiration.
+Use `HSETEX` to write hash fields and set their expiration in the same atomic call.
+
+`FIELDS <numfields>` introduces the field and value pairs and the count must match. `EX`, `PX`, `EXAT`, and `PXAT` give the written fields a lifetime or an absolute deadline, and `KEEPTTL` keeps whatever expiration those fields already had. Without any of these options the fields are written without an expiration, so a previously set one is dropped.
+
+`FNX` writes only when none of the given fields exist and `FXX` only when all of them do, which turns the command into an atomic conditional write: create-if-absent or update-if-present, with the expiration applied in the same step. The reply is `1` when the fields were written and `0` when the condition prevented it.
 
 ## Syntax
 
@@ -31301,7 +31583,7 @@ HSETEX <key> [FNX | FXX] [EX <seconds> | PX <milliseconds> | EXAT <unix-time-sec
 | Argument | Required | Repeatable | Description |
 | --- | --- | --- | --- |
 | `<key>` | Yes | No | Redis key targeted by the command. |
-| `(FNX \| FXX)` | No | No | Choose one form: `FNX`; `FXX`. |
+| `(FNX \| FXX)` | No | No | Write only when the condition holds: `FNX` when none of the given fields exist, `FXX` when all of them do. |
 | `(EX <seconds> \| PX <milliseconds> \| EXAT <unix-time-seconds> \| PXAT <unix-time-milliseconds> \| KEEPTTL)` | No | No | Choose one form: `EX` (set a lifetime in seconds); `PX` (set a lifetime in milliseconds); `EXAT` (expire at a Unix timestamp in seconds); `PXAT` (expire at a Unix timestamp in milliseconds); `KEEPTTL` (preserve the existing key lifetime). |
 | `FIELDS <numfields> <field> <value> [<field> <value> ...]` | Yes | No | Field-value pairs to set. Give the pair count first, then that many field and value pairs. |
 
@@ -31462,7 +31744,9 @@ fn main() -> redis::RedisResult<()> {
 # HSETNX
 Source: https://upstash.com/docs/redis/commands/hash/hsetnx
 
-Use `HSETNX` to set field only if it doesn't exist.
+Use `HSETNX` to set a hash field only when it does not already exist.
+
+The reply is `1` when the field was created and `0` when it was already present and left untouched. The check and the write happen atomically, so of several clients racing to fill the same field exactly one succeeds, which makes the command a way to claim a slot inside a hash without overwriting whatever a concurrent writer put there.
 
 ## Syntax
 
@@ -31627,7 +31911,9 @@ fn main() -> redis::RedisResult<()> {
 # HSTRLEN
 Source: https://upstash.com/docs/redis/commands/hash/hstrlen
 
-Use `HSTRLEN` to get length of a field's value.
+Use `HSTRLEN` to get the length in bytes of the value stored in a hash field.
+
+The reply is `0` when either the field or the key is missing. Since the value itself is not transferred, this is how you check the size of a large field, or decide whether it is worth fetching, without paying for it.
 
 ## Syntax
 
@@ -31792,7 +32078,9 @@ fn main() -> redis::RedisResult<()> {
 # HTTL
 Source: https://upstash.com/docs/redis/commands/hash/httl
 
-Use `HTTL` to get field TTL in seconds.
+Use `HTTL` to read how much longer hash fields will live, in seconds.
+
+The reply holds one value per requested field, in order: the remaining lifetime, `-1` when the field exists but has no expiration, and `-2` when the field or the key does not exist, so a missing field is never confused with a permanent one. Use [`HPTTL`](/docs/redis/commands/hash/hpttl) for millisecond precision and [`HEXPIRETIME`](/docs/redis/commands/hash/hexpiretime) when you want the absolute deadline instead of the time left.
 
 ## Syntax
 
@@ -31964,7 +32252,9 @@ fn main() -> redis::RedisResult<()> {
 # HVALS
 Source: https://upstash.com/docs/redis/commands/hash/hvals
 
-Use `HVALS` to get all values in a hash.
+Use `HVALS` to get all the values in a hash, without their field names.
+
+A missing key returns an empty list, and values come back in no particular order. The whole hash is transferred, so on large hashes prefer [`HSCAN`](/docs/redis/commands/hash/hscan) to walk it in batches, or [`HMGET`](/docs/redis/commands/hash/hmget) when you know which fields you need.
 
 ## Syntax
 
@@ -32175,7 +32465,11 @@ Source: https://upstash.com/docs/redis/commands/hyperloglog/overview
 # PFADD
 Source: https://upstash.com/docs/redis/commands/hyperloglog/pfadd
 
-Use `PFADD` to add elements to HyperLogLog.
+Use `PFADD` to add elements to a HyperLogLog.
+
+A HyperLogLog estimates how many distinct items it has seen while using a small, fixed amount of memory (at most about 12 KB) no matter how many elements pass through it. That is the trade it makes: individual elements are not stored, so they cannot be listed, checked for membership, or removed, and the cardinality that comes back from [`PFCOUNT`](/docs/redis/commands/hyperloglog/pfcount) is an approximation with a standard error of about 0.81%.
+
+The key is created on first use, and the reply is `1` when the internal registers changed as a result of the call, which is a hint that at least one element was new, and `0` when they did not. Calling `PFADD` with no elements creates an empty HyperLogLog if the key does not exist yet. Use it for counts where the exact number does not matter, such as unique visitors per page or per day, and a set for cases where you must be able to look elements up.
 
 ## Syntax
 
@@ -32339,7 +32633,11 @@ fn main() -> redis::RedisResult<()> {
 # PFCOUNT
 Source: https://upstash.com/docs/redis/commands/hyperloglog/pfcount
 
-Use `PFCOUNT` to get estimated cardinality.
+Use `PFCOUNT` to read the estimated number of distinct elements recorded in one or more HyperLogLogs.
+
+With a single key the stored estimate is returned. With several keys the structures are merged on the fly and the cardinality of their union is returned, without modifying any of them, which is how you answer "how many unique users across these seven days" without double counting. The result is an approximation with a standard error of about 0.81%.
+
+The multi-key form does real work on every call, so when the same union is read often it is cheaper to roll the sources up into one key with [`PFMERGE`](/docs/redis/commands/hyperloglog/pfmerge) and count that.
 
 ## Syntax
 
@@ -32502,7 +32800,11 @@ fn main() -> redis::RedisResult<()> {
 # PFMERGE
 Source: https://upstash.com/docs/redis/commands/hyperloglog/pfmerge
 
-Use `PFMERGE` to merge multiple HyperLogLogs.
+Use `PFMERGE` to merge several HyperLogLogs into a single one.
+
+The destination ends up representing the union of the source structures and of whatever it already held, so merging the same sources again changes nothing and new data can be folded in as it arrives. The destination is created if it does not exist.
+
+Because the union is computed register by register and loses no accuracy compared with counting the raw data, rolling hourly keys into a daily key, or daily keys into a monthly one, gives the same estimate as if every element had been added to that key directly. That makes `PFMERGE` the building block for time-based rollups of unique counts.
 
 ## Syntax
 
@@ -32666,7 +32968,9 @@ fn main() -> redis::RedisResult<()> {
 # JSON.ARRAPPEND
 Source: https://upstash.com/docs/redis/commands/json/json-arrappend
 
-Use `JSON.ARRAPPEND` to append values to JSON array.
+Use `JSON.ARRAPPEND` to append one or more values to the end of the arrays a path selects.
+
+Values are JSON text and each one is appended as a single element, so appending an array adds a nested array rather than merging its items. The reply is the new length of each array the path matched, with null for matches that are not arrays.
 
 ## Syntax
 
@@ -32836,7 +33140,9 @@ fn main() -> redis::RedisResult<()> {
 # JSON.ARRINDEX
 Source: https://upstash.com/docs/redis/commands/json/json-arrindex
 
-Use `JSON.ARRINDEX` to find index of value in array.
+Use `JSON.ARRINDEX` to find the first position of a value inside the arrays a path selects.
+
+The value is JSON text and is compared for exact equality, so `1` does not match `"1"`. The optional `start` and `stop` bound the search: `start` is inclusive, `stop` is exclusive, both may be negative to count from the end of the array, and `0` for `stop` means "to the end". The reply is the index of the first match or `-1` when the value is not present, with one result per array the path matched.
 
 ## Syntax
 
@@ -33008,7 +33314,9 @@ fn main() -> redis::RedisResult<()> {
 # JSON.ARRINSERT
 Source: https://upstash.com/docs/redis/commands/json/json-arrinsert
 
-Use `JSON.ARRINSERT` to insert values into JSON array.
+Use `JSON.ARRINSERT` to insert one or more values into the arrays a path selects, before a given index.
+
+Elements at and after that index shift to the right, keeping the rest of the array in order. A negative index counts from the end of the array and an index equal to the array's length appends, while an index outside the array returns an error. The reply is the new length of each array the path matched.
 
 ## Syntax
 
@@ -33179,7 +33487,9 @@ fn main() -> redis::RedisResult<()> {
 # JSON.ARRLEN
 Source: https://upstash.com/docs/redis/commands/json/json-arrlen
 
-Use `JSON.ARRLEN` to get JSON array length.
+Use `JSON.ARRLEN` to get the number of elements in the arrays a path selects.
+
+Without a path the root value is used. The reply is one length per match, with null for matches that are not arrays, so it doubles as a cheap way to check that a branch of the document really is an array before working on it.
 
 ## Syntax
 
@@ -33348,7 +33658,11 @@ fn main() -> redis::RedisResult<()> {
 # JSON.ARRPOP
 Source: https://upstash.com/docs/redis/commands/json/json-arrpop
 
-Use `JSON.ARRPOP` to pop value from JSON array.
+Use `JSON.ARRPOP` to remove an element from the arrays a path selects and return it.
+
+Without an index the last element is popped, which makes the command a stack pop; index `0` pops the first element, and negative indexes count from the end. An index past the end of the array is clamped to the last element. The reply is the removed element as JSON text, or null when the array is empty.
+
+Because the read and the removal happen in one atomic step, a JSON array can be used as a small work queue without the risk of two clients taking the same element.
 
 ## Syntax
 
@@ -33518,7 +33832,11 @@ fn main() -> redis::RedisResult<()> {
 # JSON.ARRTRIM
 Source: https://upstash.com/docs/redis/commands/json/json-arrtrim
 
-Use `JSON.ARRTRIM` to trim JSON array to range.
+Use `JSON.ARRTRIM` to keep only a range of elements in the arrays a path selects and discard the rest.
+
+Both `start` and `stop` are inclusive indexes and may be negative to count from the end of the array. Indexes outside the array are clamped, and a range that selects nothing leaves an empty array. The reply is the new length of each array the path matched.
+
+It is the JSON counterpart of [`LTRIM`](/docs/redis/commands/list/ltrim): combine it with [`JSON.ARRAPPEND`](/docs/redis/commands/json/json-arrappend) to keep a capped list, such as the last N events, inside a document.
 
 ## Syntax
 
@@ -33689,7 +34007,11 @@ fn main() -> redis::RedisResult<()> {
 # JSON.CLEAR
 Source: https://upstash.com/docs/redis/commands/json/json-clear
 
-Use `JSON.CLEAR` to clear JSON values.
+Use `JSON.CLEAR` to empty the values a path selects without removing them from the document.
+
+Objects lose all their keys, arrays lose all their elements, and numbers are reset to `0`. Values of other types, such as strings and booleans, are left as they are. The reply is the number of values that were cleared.
+
+The difference from [`JSON.DEL`](/docs/redis/commands/json/json-del) is that the selected keys and slots stay in the document as empty containers, so the shape of the document is preserved and consumers that expect a field to exist keep working.
 
 ## Syntax
 
@@ -33858,7 +34180,11 @@ fn main() -> redis::RedisResult<()> {
 # JSON.DEBUG
 Source: https://upstash.com/docs/redis/commands/json/json-debug
 
-Use `JSON.DEBUG` to inspect JSON memory usage.
+Use `JSON.DEBUG` to inspect internal details of stored JSON values.
+
+`JSON.DEBUG MEMORY` reports the approximate number of bytes used by the value a key and optional path select, which is how you find out which documents, or which branches of a document, are responsible for memory growth. The figure includes internal overhead and is an estimate meant for comparison rather than exact accounting. `JSON.DEBUG HELP` lists the supported forms.
+
+It is a diagnostic aid: the details it exposes are implementation-specific and can change, so do not build application logic on them.
 
 ## Syntax
 
@@ -34024,7 +34350,11 @@ fn main() -> redis::RedisResult<()> {
 # JSON.DEL
 Source: https://upstash.com/docs/redis/commands/json/json-del
 
-Use `JSON.DEL` to delete JSON values.
+Use `JSON.DEL` to delete the value at a path in a JSON document.
+
+Without a path the entire key is deleted. The reply is the number of values that were deleted, which is `0` when the path matched nothing, and deleting the root of a document removes the key itself. With a JSONPath that matches several places, every match is removed in the same call.
+
+[`JSON.FORGET`](/docs/redis/commands/json/json-forget) is an alias with identical behavior.
 
 ## Syntax
 
@@ -34193,7 +34523,9 @@ fn main() -> redis::RedisResult<()> {
 # JSON.FORGET
 Source: https://upstash.com/docs/redis/commands/json/json-forget
 
-Use `JSON.FORGET` to alias for JSON.DEL.
+Use `JSON.FORGET` to delete the value at a path in a JSON document. It is an alias of [`JSON.DEL`](/docs/redis/commands/json/json-del) with identical behavior, kept for compatibility with clients and code that use the older name.
+
+Without a path the entire key is deleted, and the reply is the number of values that were deleted, which is `0` when the path matched nothing.
 
 ## Syntax
 
@@ -34362,7 +34694,11 @@ fn main() -> redis::RedisResult<()> {
 # JSON.GET
 Source: https://upstash.com/docs/redis/commands/json/json-get
 
-Use `JSON.GET` to get JSON values.
+Use `JSON.GET` to read one or more values from a JSON document.
+
+Without a path the whole document is returned. The reply shape depends on the path syntax: a path starting with `$` is a JSONPath and always returns an array with one entry per match, so an empty array means nothing matched, while the legacy dot syntax returns the value itself and reports an error when the path does not exist. Passing several paths returns an object keyed by the path expressions, which is a cheap way to pull a few unrelated branches of a large document in one call.
+
+`INDENT`, `NEWLINE`, and `SPACE` control the formatting of the returned JSON text, which is otherwise compact. They are meant for human-readable output; leave them out when a program parses the reply.
 
 ## Syntax
 
@@ -34534,7 +34870,11 @@ fn main() -> redis::RedisResult<()> {
 # JSON.MERGE
 Source: https://upstash.com/docs/redis/commands/json/json-merge
 
-Use `JSON.MERGE` to merge JSON values.
+Use `JSON.MERGE` to merge a JSON value into a document at a path, following the JSON Merge Patch semantics of RFC 7386.
+
+Objects are merged recursively: keys in the patch replace or create the matching keys in the target, keys set to `null` delete them, and any value that is not an object, arrays included, replaces the target outright instead of being merged element by element. The parent must already exist: merging into a missing child of an existing object creates it, but intermediate levels are not built along the way, and a key that does not exist yet can only be created by merging at the root.
+
+This is the command for partial updates of an object, where [`JSON.SET`](/docs/redis/commands/json/json-set) would replace the whole branch: one call can change a few fields, delete another, and leave the rest of the document untouched.
 
 ## Syntax
 
@@ -34706,7 +35046,9 @@ fn main() -> redis::RedisResult<()> {
 # JSON.MGET
 Source: https://upstash.com/docs/redis/commands/json/json-mget
 
-Use `JSON.MGET` to get values from multiple keys.
+Use `JSON.MGET` to read the same path from several JSON documents in one call.
+
+The reply holds one entry per key, in the order requested, containing what the path selected in that document, or null when the key does not exist or the path matches nothing. It replaces one [`JSON.GET`](/docs/redis/commands/json/json-get) per key when you are gathering the same field across many documents, for example the price of every product in a cart.
 
 ## Syntax
 
@@ -34875,7 +35217,9 @@ fn main() -> redis::RedisResult<()> {
 # JSON.MSET
 Source: https://upstash.com/docs/redis/commands/json/json-mset
 
-Use `JSON.MSET` to set values in multiple keys.
+Use `JSON.MSET` to set values at paths in several JSON documents in one atomic call.
+
+Each triple gives a key, a path, and a value, and missing keys are created. Either every write is applied or none is, with no other command running in between, which is what makes it the right tool for documents that must stay consistent with each other. The reply is `OK`.
 
 ## Syntax
 
@@ -35049,7 +35393,9 @@ fn main() -> redis::RedisResult<()> {
 # JSON.NUMINCRBY
 Source: https://upstash.com/docs/redis/commands/json/json-numincrby
 
-Use `JSON.NUMINCRBY` to increment JSON number.
+Use `JSON.NUMINCRBY` to add a number to the numeric values a path selects.
+
+The increment may be negative to count down, and it is applied atomically, so concurrent callers cannot lose an update. The reply is the new value of each match; a match that is not a number returns an error. This is how a counter kept inside a document is updated without reading and rewriting the whole document.
 
 ## Syntax
 
@@ -35219,7 +35565,9 @@ fn main() -> redis::RedisResult<()> {
 # JSON.NUMMULTBY
 Source: https://upstash.com/docs/redis/commands/json/json-nummultby
 
-Use `JSON.NUMMULTBY` to multiply JSON number.
+Use `JSON.NUMMULTBY` to multiply the numeric values a path selects by a number.
+
+The multiplier may be a fraction to scale values down, and the update is atomic. The reply is the new value of each match, and a match that is not a number returns an error. It is the multiplicative counterpart of [`JSON.NUMINCRBY`](/docs/redis/commands/json/json-numincrby), useful for applying percentage changes such as a discount to every price in a document.
 
 ## Syntax
 
@@ -35393,7 +35741,9 @@ fn main() -> redis::RedisResult<()> {
 # JSON.OBJKEYS
 Source: https://upstash.com/docs/redis/commands/json/json-objkeys
 
-Use `JSON.OBJKEYS` to get JSON object keys.
+Use `JSON.OBJKEYS` to list the field names of the objects a path selects.
+
+Without a path the root value is used. The reply holds one list of keys per match, with null for matches that are not objects. Only the field names come back, not the values, which makes it a cheap way to inspect the shape of a document before reading it.
 
 ## Syntax
 
@@ -35562,7 +35912,9 @@ fn main() -> redis::RedisResult<()> {
 # JSON.OBJLEN
 Source: https://upstash.com/docs/redis/commands/json/json-objlen
 
-Use `JSON.OBJLEN` to get JSON object size.
+Use `JSON.OBJLEN` to get the number of fields in the objects a path selects.
+
+Without a path the root value is used. The reply holds one count per match, with null for matches that are not objects. It counts only the object's own fields, not the fields of nested objects.
 
 ## Syntax
 
@@ -35731,7 +36083,11 @@ fn main() -> redis::RedisResult<()> {
 # JSON.RESP
 Source: https://upstash.com/docs/redis/commands/json/json-resp
 
-Use `JSON.RESP` to get JSON in RESP format.
+Use `JSON.RESP` to get a JSON value in RESP form instead of as JSON text.
+
+The document is translated structurally: an object becomes an array whose first element is `{` followed by alternating field names and values, an array becomes an array whose first element is `[` followed by its elements, and scalars become the corresponding RESP types. Nested values are translated the same way, recursively.
+
+This lets a client walk the structure using the protocol types it already decodes, without running a JSON parser on the reply. For ordinary use, [`JSON.GET`](/docs/redis/commands/json/json-get) is the more convenient command.
 
 ## Syntax
 
@@ -35903,7 +36259,11 @@ fn main() -> redis::RedisResult<()> {
 # JSON.SET
 Source: https://upstash.com/docs/redis/commands/json/json-set
 
-Use `JSON.SET` to set JSON value.
+Use `JSON.SET` to set a JSON value at a path inside a document, creating the key when it does not exist.
+
+The value is JSON text; the Upstash SDK helpers serialize native objects for you. With the root path (`$`) the whole document is replaced, which is also how a new document is created. For a nested path the parent must already exist: the command adds one missing child to an existing object or appends to an existing array, but it does not create intermediate levels along the way.
+
+`NX` writes only when the path does not exist yet and `XX` only when it does, which makes conditional updates atomic. When the path is a JSONPath that matches several places, every match is updated in the same call, so a single command can update all elements of an array.
 
 ## Syntax
 
@@ -36074,7 +36434,9 @@ fn main() -> redis::RedisResult<()> {
 # JSON.STRAPPEND
 Source: https://upstash.com/docs/redis/commands/json/json-strappend
 
-Use `JSON.STRAPPEND` to append to JSON string.
+Use `JSON.STRAPPEND` to append text to the string values a path selects.
+
+The value is JSON text, so the appended string must be quoted, as in `'"suffix"'`. The reply is the new length of each string the path matched, with an error for matches that are not strings. Appending in place avoids reading and rewriting the whole document just to extend one field.
 
 ## Syntax
 
@@ -36244,7 +36606,9 @@ fn main() -> redis::RedisResult<()> {
 # JSON.STRLEN
 Source: https://upstash.com/docs/redis/commands/json/json-strlen
 
-Use `JSON.STRLEN` to get JSON string length.
+Use `JSON.STRLEN` to get the length of the string values a path selects.
+
+Without a path the root value is used. The reply holds one length per match, with null for matches that are not strings, so it is also a quick way to check that a field is a string. The value itself is not transferred, which makes it cheap even for long strings.
 
 ## Syntax
 
@@ -36413,7 +36777,9 @@ fn main() -> redis::RedisResult<()> {
 # JSON.TOGGLE
 Source: https://upstash.com/docs/redis/commands/json/json-toggle
 
-Use `JSON.TOGGLE` to toggle JSON boolean.
+Use `JSON.TOGGLE` to flip the boolean values a path selects, turning `true` into `false` and back.
+
+The reply is the new value of each match, and a match that is not a boolean returns an error. Because the read and the write are one atomic step, this is the safe way to flip a flag inside a document, where reading it and writing the opposite value back would race with other clients.
 
 ## Syntax
 
@@ -36582,7 +36948,9 @@ fn main() -> redis::RedisResult<()> {
 # JSON.TYPE
 Source: https://upstash.com/docs/redis/commands/json/json-type
 
-Use `JSON.TYPE` to get JSON value type.
+Use `JSON.TYPE` to find out the JSON type of the values a path selects.
+
+The reply names one type per match, one of `object`, `array`, `string`, `integer`, `number`, `boolean`, or `null`, and is empty when the path matches nothing. Whole numbers report as `integer` and fractional ones as `number`. It is the way to inspect documents whose shape you do not control before applying type-specific commands, which would otherwise fail.
 
 ## Syntax
 
@@ -36763,7 +37131,7 @@ To query inside JSON values (full-text, fuzzy, phrase, regex), see [Upstash Redi
 <Card title="JSON.CLEAR" href="/redis/commands/json/json-clear">Clear JSON values</Card>
 <Card title="JSON.DEL" href="/redis/commands/json/json-del">Delete JSON values</Card>
 <Card title="JSON.DEBUG" href="/redis/commands/json/json-debug">Inspect JSON memory usage</Card>
-<Card title="JSON.FORGET" href="/redis/commands/json/json-forget">Alias for JSON.DEL</Card>
+<Card title="JSON.FORGET" href="/redis/commands/json/json-forget">Delete JSON values (alias of JSON.DEL)</Card>
 <Card title="JSON.GET" href="/redis/commands/json/json-get">Get JSON values</Card>
 <Card title="JSON.MERGE" href="/redis/commands/json/json-merge">Merge JSON values</Card>
 <Card title="JSON.MGET" href="/redis/commands/json/json-mget">Get values from multiple keys</Card>
@@ -36785,6 +37153,10 @@ Source: https://upstash.com/docs/redis/commands/list/blmove
 
 Use `BLMOVE` to move an element from one list to another, blocking until the source has an element or the timeout expires.
 
+It is the blocking form of [`LMOVE`](/docs/redis/commands/list/lmove): when the source list is not empty it behaves identically and returns immediately, and when it is empty the connection waits instead of returning null. The timeout is given in seconds, may be fractional, and `0` waits indefinitely. If several clients are waiting on the same key, the one that has been waiting longest is served first.
+
+Because the element is never outside a list, this is the standard way to build a reliable queue: a worker blocks until work appears, atomically moves it to a processing list, and deletes it from there when done, so an interrupted job can be recovered instead of lost.
+
 ## Syntax
 
 ```redis
@@ -36797,8 +37169,8 @@ BLMOVE <source> <destination> (LEFT | RIGHT) (LEFT | RIGHT) <timeout>
 | --- | --- | --- | --- |
 | `<source>` | Yes | No | Redis key used as source. |
 | `<destination>` | Yes | No | Redis key used as destination. |
-| `(LEFT \| RIGHT)` | Yes | No | Choose one form: `LEFT`; `RIGHT`. |
-| `(LEFT \| RIGHT)` | Yes | No | Choose one form: `LEFT`; `RIGHT`. |
+| `(LEFT \| RIGHT)` | Yes | No | Which end of the source list the element is taken from: `LEFT` (head) or `RIGHT` (tail). |
+| `(LEFT \| RIGHT)` | Yes | No | Which end of the destination list the element is pushed onto: `LEFT` (head) or `RIGHT` (tail). |
 | `<timeout>` | Yes | No | Seconds to block; `0` blocks indefinitely. |
 
 ## Important points
@@ -36953,6 +37325,10 @@ Source: https://upstash.com/docs/redis/commands/list/blmpop
 
 Use `BLMPOP` to pop elements from the first non-empty list among several, blocking until one has elements or the timeout expires.
 
+It is the blocking form of [`LMPOP`](/docs/redis/commands/list/lmpop): keys are examined in the order given, so listing a high priority queue first drains it before the others are considered, `LEFT` or `RIGHT` chooses the end, and `COUNT` sets how many elements to take. The reply names the key that was popped from along with the elements.
+
+The timeout is in seconds, may be fractional, and `0` waits indefinitely; when it expires the reply is null. This is the command to reach for when one worker serves several queues of differing priority.
+
 ## Syntax
 
 ```redis
@@ -36966,7 +37342,7 @@ BLMPOP <timeout> <numkeys> <key> [<key> ...] (LEFT | RIGHT) [COUNT <count>]
 | `<timeout>` | Yes | No | Seconds to block; `0` blocks indefinitely. |
 | `<numkeys>` | Yes | No | Number of key arguments that follow. |
 | `<key>` | Yes | Yes | Redis key targeted by the command. |
-| `(LEFT \| RIGHT)` | Yes | No | Choose one form: `LEFT`; `RIGHT`. |
+| `(LEFT \| RIGHT)` | Yes | No | Which end to pop from: `LEFT` (head) or `RIGHT` (tail). |
 | `COUNT <count>` | No | No | Maximum number of elements to pop. |
 
 ## Important points
@@ -37120,6 +37496,10 @@ Source: https://upstash.com/docs/redis/commands/list/blpop
 
 Use `BLPOP` to pop an element from the head of the first non-empty list, blocking until one has an element or the timeout expires.
 
+It is the blocking form of [`LPOP`](/docs/redis/commands/list/lpop) and it accepts several keys, which are checked in the order given, so earlier keys act as higher priority queues. The reply names the key the element came from together with the element itself, which matters when you are waiting on more than one queue.
+
+The timeout is in seconds, may be fractional, and `0` waits indefinitely; when it expires the reply is null. Blocking lets a worker wait for work without polling, which cuts both latency and wasted commands. When several clients are blocked on the same key they are served in the order they started waiting.
+
 ## Syntax
 
 ```redis
@@ -37282,6 +37662,10 @@ Source: https://upstash.com/docs/redis/commands/list/brpop
 
 Use `BRPOP` to pop an element from the tail of the first non-empty list, blocking until one has an element or the timeout expires.
 
+It is the blocking form of [`RPOP`](/docs/redis/commands/list/rpop) and behaves like [`BLPOP`](/docs/redis/commands/list/blpop) in every other respect: several keys are checked in the order given, the reply names the key the element came from, the timeout is in seconds and may be fractional with `0` meaning wait forever, and clients blocked on the same key are served in the order they started waiting.
+
+Producers pushing with [`LPUSH`](/docs/redis/commands/list/lpush) and consumers waiting with `BRPOP` form the classic first-in, first-out worker queue.
+
 ## Syntax
 
 ```redis
@@ -37444,6 +37828,10 @@ Source: https://upstash.com/docs/redis/commands/list/brpoplpush
 
 Use `BRPOPLPUSH` to pop an element from the tail of one list and push it to the head of another, blocking until the source has an element or the timeout expires.
 
+It is the blocking form of [`RPOPLPUSH`](/docs/redis/commands/list/rpoplpush). The timeout is in seconds, may be fractional, and `0` waits indefinitely; when it expires the reply is null. Since the element moves atomically into the destination, a worker that crashes after taking an item leaves it visible in the processing list, where it can be recovered.
+
+Redis deprecates this command in favor of [`BLMOVE`](/docs/redis/commands/list/blmove), which does the same thing and additionally lets you choose which end of each list to use.
+
 ## Syntax
 
 ```redis
@@ -37606,7 +37994,9 @@ fn main() -> redis::RedisResult<()> {
 # LINDEX
 Source: https://upstash.com/docs/redis/commands/list/lindex
 
-Use `LINDEX` to get element by index.
+Use `LINDEX` to read the element at a given position in a list.
+
+Indexes are zero-based from the head, and negative indexes count from the tail, so `-1` is the last element. The reply is null when the key does not exist or the index is out of range. Redis walks the list from the nearer end to reach the index, so access is fast near the head and tail and gets more expensive towards the middle of a long list.
 
 ## Syntax
 
@@ -37772,7 +38162,11 @@ fn main() -> redis::RedisResult<()> {
 # LINSERT
 Source: https://upstash.com/docs/redis/commands/list/linsert
 
-Use `LINSERT` to insert before or after pivot.
+Use `LINSERT` to insert an element immediately before or after another element of a list.
+
+The pivot is matched by value, and only its first occurrence starting from the head is used. The reply is the new length of the list, `0` when the key does not exist, and `-1` when the pivot value was not found, which is how you tell a failed insert from a successful one.
+
+Finding the pivot means scanning the list, so this is a linear operation; on long lists it is worth keeping an index elsewhere or using a sorted set instead.
 
 ## Syntax
 
@@ -37785,7 +38179,7 @@ LINSERT <key> (BEFORE | AFTER) <pivot> <element>
 | Argument | Required | Repeatable | Description |
 | --- | --- | --- | --- |
 | `<key>` | Yes | No | Redis key targeted by the command. |
-| `(BEFORE \| AFTER)` | Yes | No | Choose one form: `BEFORE`; `AFTER`. |
+| `(BEFORE \| AFTER)` | Yes | No | Where to place the new element relative to the pivot: `BEFORE` or `AFTER`. |
 | `<pivot>` | Yes | No | Existing element to insert next to. |
 | `<element>` | Yes | No | Element to insert. |
 
@@ -37939,7 +38333,9 @@ fn main() -> redis::RedisResult<()> {
 # LLEN
 Source: https://upstash.com/docs/redis/commands/list/llen
 
-Use `LLEN` to get list length.
+Use `LLEN` to get the number of elements in a list.
+
+The reply is `0` when the key does not exist. The length is maintained by Redis rather than computed on demand, so the command is cheap whatever the size of the list, which makes it the usual way to monitor a queue's backlog.
 
 ## Syntax
 
@@ -38104,7 +38500,11 @@ fn main() -> redis::RedisResult<()> {
 # LMOVE
 Source: https://upstash.com/docs/redis/commands/list/lmove
 
-Use `LMOVE` to move element between lists.
+Use `LMOVE` to atomically take an element from one end of a list and push it onto one end of another list, returning the element.
+
+The two directions are chosen independently: `LEFT RIGHT` takes from the head of the source and appends to the tail of the destination, which preserves order when transferring between queues, while `LEFT LEFT` behaves like moving between stacks. If the source is empty nothing happens and the reply is null. Source and destination may be the same key, in which case the list is rotated.
+
+Because the element is never outside a list, `LMOVE` is the building block for reliable queues: a worker moves an item into a processing list, does the work, and removes it from there, so a crash leaves the item recoverable instead of lost. It replaces the deprecated [`RPOPLPUSH`](/docs/redis/commands/list/rpoplpush), and [`BLMOVE`](/docs/redis/commands/list/blmove) is the blocking form.
 
 ## Syntax
 
@@ -38118,8 +38518,8 @@ LMOVE <source> <destination> (LEFT | RIGHT) (LEFT | RIGHT)
 | --- | --- | --- | --- |
 | `<source>` | Yes | No | Redis key used as source. |
 | `<destination>` | Yes | No | Redis key used as destination. |
-| `(LEFT \| RIGHT)` | Yes | No | Choose one form: `LEFT`; `RIGHT`. |
-| `(LEFT \| RIGHT)` | Yes | No | Choose one form: `LEFT`; `RIGHT`. |
+| `(LEFT \| RIGHT)` | Yes | No | Which end of the source list the element is taken from: `LEFT` (head) or `RIGHT` (tail). |
+| `(LEFT \| RIGHT)` | Yes | No | Which end of the destination list the element is pushed onto: `LEFT` (head) or `RIGHT` (tail). |
 
 ## Response
 
@@ -38271,7 +38671,11 @@ fn main() -> redis::RedisResult<()> {
 # LMPOP
 Source: https://upstash.com/docs/redis/commands/list/lmpop
 
-Use `LMPOP` to pop from multiple lists.
+Use `LMPOP` to pop elements from the first of several lists that is not empty.
+
+`<numkeys>` states how many keys follow, `LEFT` or `RIGHT` chooses the end to pop from, and `COUNT` sets how many elements to take, defaulting to one. Keys are examined in the order given and only the first non-empty one is touched, which is exactly what a priority queue needs: list the high priority queue first and it is drained before the others are looked at.
+
+The reply names the key that was popped from together with the elements, so a caller working with several queues knows where the work came from. When every key is empty the reply is null; use [`BLMPOP`](/docs/redis/commands/list/blmpop) to wait instead.
 
 ## Syntax
 
@@ -38285,7 +38689,7 @@ LMPOP <numkeys> <key> [<key> ...] (LEFT | RIGHT) [COUNT <count>]
 | --- | --- | --- | --- |
 | `<numkeys>` | Yes | No | Number of key arguments that follow. |
 | `<key>` | Yes | Yes | Redis key targeted by the command. |
-| `(LEFT \| RIGHT)` | Yes | No | Choose one form: `LEFT`; `RIGHT`. |
+| `(LEFT \| RIGHT)` | Yes | No | Which end to pop from: `LEFT` (head) or `RIGHT` (tail). |
 | `COUNT <count>` | No | No | Maximum number of elements to pop. |
 
 ## Response
@@ -38435,7 +38839,11 @@ fn main() -> redis::RedisResult<()> {
 # LPOP
 Source: https://upstash.com/docs/redis/commands/list/lpop
 
-Use `LPOP` to pop from list head.
+Use `LPOP` to remove and return elements from the head of a list.
+
+Without a count a single element is returned, or null when the key does not exist. With a count, up to that many elements are removed and returned in the order they were popped, and the reply is an empty array or null when the list is empty. The key is deleted once the last element is removed.
+
+Paired with [`RPUSH`](/docs/redis/commands/list/rpush) this gives a first-in, first-out queue; paired with [`LPUSH`](/docs/redis/commands/list/lpush) it gives a stack. Use [`BLPOP`](/docs/redis/commands/list/blpop) when a consumer should wait for work rather than poll.
 
 ## Syntax
 
@@ -38601,7 +39009,11 @@ fn main() -> redis::RedisResult<()> {
 # LPOS
 Source: https://upstash.com/docs/redis/commands/list/lpos
 
-Use `LPOS` to find element position.
+Use `LPOS` to find the position of an element in a list.
+
+The scan starts at the head and, by default, reports the index of the first match or null when there is none. `RANK` selects which match to report: `RANK 2` skips to the second occurrence, and a negative rank searches backwards from the tail, so `RANK -1` finds the last occurrence. `COUNT` returns that many matching indexes instead of just one, and `COUNT 0` returns all of them. `MAXLEN` limits how many elements are compared, which bounds the cost of the search on a long list at the price of possibly missing matches beyond that point.
+
+It is the read-only way to locate a value before acting on it with [`LSET`](/docs/redis/commands/list/lset) or [`LREM`](/docs/redis/commands/list/lrem).
 
 ## Syntax
 
@@ -38771,7 +39183,11 @@ fn main() -> redis::RedisResult<()> {
 # LPUSH
 Source: https://upstash.com/docs/redis/commands/list/lpush
 
-Use `LPUSH` to push to list head.
+Use `LPUSH` to add one or more elements to the head of a list, creating the list when the key does not exist.
+
+Elements are inserted one after another, so they end up in reverse order relative to the argument list: `LPUSH key a b c` leaves the list as `c`, `b`, `a`. The reply is the length of the list after the push. If the key holds a value of another type the command returns an error.
+
+Pushing to the head and popping from the tail with [`RPOP`](/docs/redis/commands/list/rpop) gives a first-in, first-out queue, while popping from the head with [`LPOP`](/docs/redis/commands/list/lpop) gives a stack. Combine with [`LTRIM`](/docs/redis/commands/list/ltrim) to keep a capped list of recent items.
 
 ## Syntax
 
@@ -38938,7 +39354,9 @@ fn main() -> redis::RedisResult<()> {
 # LPUSHX
 Source: https://upstash.com/docs/redis/commands/list/lpushx
 
-Use `LPUSHX` to push to head if list exists.
+Use `LPUSHX` to add elements to the head of a list only when the list already exists.
+
+Nothing happens and the reply is `0` when the key does not exist, and no key is created. This is the difference from [`LPUSH`](/docs/redis/commands/list/lpush), and it is what you want when a list should only be fed while a consumer is holding it open, so that stale producers do not resurrect a queue that was already drained and deleted.
 
 ## Syntax
 
@@ -39104,7 +39522,11 @@ fn main() -> redis::RedisResult<()> {
 # LRANGE
 Source: https://upstash.com/docs/redis/commands/list/lrange
 
-Use `LRANGE` to get range of elements.
+Use `LRANGE` to read a range of elements from a list.
+
+Both `<start>` and `<stop>` are zero-based, inclusive, and may be negative to count from the tail, so `LRANGE key 0 -1` returns the whole list and `LRANGE key 0 9` returns the first ten elements. Out-of-range indexes are clamped instead of producing an error, and a range that selects nothing, or a missing key, returns an empty list.
+
+The command copies the requested range into the reply, so reading a large list in one call is expensive: page through it with successive ranges when the list is big.
 
 ## Syntax
 
@@ -39271,7 +39693,11 @@ fn main() -> redis::RedisResult<()> {
 # LREM
 Source: https://upstash.com/docs/redis/commands/list/lrem
 
-Use `LREM` to remove elements by value.
+Use `LREM` to remove elements equal to a given value from a list.
+
+The count decides how many occurrences are removed and in which direction: a positive count removes that many starting from the head, a negative count removes that many starting from the tail, and `0` removes every occurrence. The reply is the number of elements actually removed, and the key is deleted when the list becomes empty.
+
+Removing by value means scanning the list, so on long lists prefer a set or a sorted set when you frequently need to delete arbitrary items.
 
 ## Syntax
 
@@ -39438,7 +39864,9 @@ fn main() -> redis::RedisResult<()> {
 # LSET
 Source: https://upstash.com/docs/redis/commands/list/lset
 
-Use `LSET` to set element at index.
+Use `LSET` to overwrite the element at a given position in a list.
+
+Indexes are zero-based from the head and negative indexes count from the tail. The command returns an error when the key does not exist or the index is out of range, since it never grows the list; use [`LPUSH`](/docs/redis/commands/list/lpush) or [`RPUSH`](/docs/redis/commands/list/rpush) to add elements. Locate the position first with [`LPOS`](/docs/redis/commands/list/lpos) when you know the value but not the index.
 
 ## Syntax
 
@@ -39606,7 +40034,11 @@ fn main() -> redis::RedisResult<()> {
 # LTRIM
 Source: https://upstash.com/docs/redis/commands/list/ltrim
 
-Use `LTRIM` to trim list to range.
+Use `LTRIM` to keep only a range of elements in a list and delete everything outside it.
+
+Both ends are inclusive, zero-based, and may be negative to count from the tail. If `<start>` is greater than `<stop>` or lies past the end of the list, every element is removed and the key is deleted. The reply is always `OK`.
+
+The classic use is a capped list: [`LPUSH`](/docs/redis/commands/list/lpush) a new item and then `LTRIM key 0 99` to keep the hundred most recent ones, which bounds memory without any separate cleanup job.
 
 ## Syntax
 
@@ -39783,9 +40215,9 @@ Source: https://upstash.com/docs/redis/commands/list/overview
 <Card title="LINSERT" href="/redis/commands/list/linsert">Insert before or after pivot</Card>
 <Card title="LLEN" href="/redis/commands/list/llen">Get list length</Card>
 <Card title="LMOVE" href="/redis/commands/list/lmove">Move element between lists</Card>
-<Card title="LMPOP" href="/redis/commands/list/lmpop">Pop from multiple lists</Card>
+<Card title="LMPOP" href="/redis/commands/list/lmpop">Pop from the first non-empty list</Card>
 <Card title="LPOP" href="/redis/commands/list/lpop">Pop from list head</Card>
-<Card title="LPOS" href="/redis/commands/list/lpos">Find element position</Card>
+<Card title="LPOS" href="/redis/commands/list/lpos">Find the position of an element</Card>
 <Card title="LPUSH" href="/redis/commands/list/lpush">Push to list head</Card>
 <Card title="LPUSHX" href="/redis/commands/list/lpushx">Push to head if list exists</Card>
 <Card title="LRANGE" href="/redis/commands/list/lrange">Get range of elements</Card>
@@ -39801,7 +40233,11 @@ Source: https://upstash.com/docs/redis/commands/list/overview
 # RPOP
 Source: https://upstash.com/docs/redis/commands/list/rpop
 
-Use `RPOP` to pop from list tail.
+Use `RPOP` to remove and return elements from the tail of a list.
+
+Without a count a single element is returned, or null when the key does not exist. With a count, up to that many elements are removed and returned in the order they were popped, and the key is deleted once the last element is gone.
+
+Combined with [`LPUSH`](/docs/redis/commands/list/lpush) this gives a first-in, first-out queue, since producers add at the head and consumers take from the tail. Use [`BRPOP`](/docs/redis/commands/list/brpop) when a consumer should wait for work instead of polling.
 
 ## Syntax
 
@@ -39967,7 +40403,11 @@ fn main() -> redis::RedisResult<()> {
 # RPOPLPUSH
 Source: https://upstash.com/docs/redis/commands/list/rpoplpush
 
-Use `RPOPLPUSH` to pop from tail and push to head.
+Use `RPOPLPUSH` to atomically move an element from the tail of one list to the head of another, returning the element.
+
+If the source is empty nothing happens and the reply is null. Source and destination may be the same key, which rotates the list: the tail element becomes the new head, so repeated calls cycle through a list of items forever, a handy pattern for round-robin scheduling.
+
+The command is deprecated in Redis in favor of [`LMOVE`](/docs/redis/commands/list/lmove), which does the same thing but lets you choose both ends. [`BRPOPLPUSH`](/docs/redis/commands/list/brpoplpush) is the blocking form.
 
 ## Syntax
 
@@ -40127,7 +40567,11 @@ fn main() -> redis::RedisResult<()> {
 # RPUSH
 Source: https://upstash.com/docs/redis/commands/list/rpush
 
-Use `RPUSH` to push to list tail.
+Use `RPUSH` to add one or more elements to the tail of a list, creating the list when the key does not exist.
+
+Elements are appended in the order given, so `RPUSH key a b c` leaves the list as `a`, `b`, `c`. The reply is the length of the list after the push, and a key holding another type returns an error.
+
+Appending with `RPUSH` and consuming from the head with [`LPOP`](/docs/redis/commands/list/lpop) is the standard first-in, first-out queue, and it is the form most job queues use because the natural reading order with [`LRANGE`](/docs/redis/commands/list/lrange) then matches the order of insertion.
 
 ## Syntax
 
@@ -40294,7 +40738,9 @@ fn main() -> redis::RedisResult<()> {
 # RPUSHX
 Source: https://upstash.com/docs/redis/commands/list/rpushx
 
-Use `RPUSHX` to push to tail if list exists.
+Use `RPUSHX` to add elements to the tail of a list only when the list already exists.
+
+Nothing happens and the reply is `0` when the key does not exist, and no key is created. Use it when producers should append to a queue only while it is alive, for example when the list is created by a consumer that is currently attached, so that writes to a queue nobody is reading do not silently pile up.
 
 ## Syntax
 
@@ -40498,7 +40944,11 @@ Source: https://upstash.com/docs/redis/commands/pub-sub/overview
 # PSUBSCRIBE
 Source: https://upstash.com/docs/redis/commands/pub-sub/psubscribe
 
-Use `PSUBSCRIBE` to subscribe to pattern channels.
+Use `PSUBSCRIBE` to subscribe the current connection to channels by glob-style pattern.
+
+A pattern such as `news.*` matches every channel that starts with `news.`, including channels created after the subscription, which is what makes patterns useful for topic hierarchies. `?` matches a single character and `[...]` a character class.
+
+Pattern subscriptions are tracked separately from the exact-channel subscriptions made with [`SUBSCRIBE`](/docs/redis/commands/pub-sub/subscribe), and a message that matches several of a connection's patterns is delivered once per matching pattern, so overlapping patterns produce duplicates. Cancel a pattern with [`PUNSUBSCRIBE`](/docs/redis/commands/pub-sub/punsubscribe), passing exactly the same pattern string.
 
 ## Syntax
 
@@ -40650,7 +41100,11 @@ fn main() -> redis::RedisResult<()> {
 # PUBLISH
 Source: https://upstash.com/docs/redis/commands/pub-sub/publish
 
-Use `PUBLISH` to publish message to channel.
+Use `PUBLISH` to send a message to a channel.
+
+The reply is the number of subscribers the message was delivered to, counting both channel and pattern subscribers, so a reply of `0` means nobody was listening. Delivery is fire and forget: messages are not stored and a client that is not connected at that moment never sees them, so use [streams](/docs/redis/commands/streams/overview) when messages must survive a disconnect or be replayed.
+
+Publishing works over both the REST API and a TCP connection, while subscribing requires a TCP connection.
 
 ## Syntax
 
@@ -40814,7 +41268,11 @@ fn main() -> redis::RedisResult<()> {
 # PUBSUB
 Source: https://upstash.com/docs/redis/commands/pub-sub/pubsub
 
-Use `PUBSUB` to inspect pub/sub state.
+Use `PUBSUB` to inspect the state of the pub/sub system without subscribing to anything.
+
+`CHANNELS` lists the channels that currently have at least one subscriber, optionally filtered by a glob-style pattern. `NUMSUB` reports the subscriber count for each channel you name, and `NUMPAT` reports how many distinct patterns are subscribed to across all clients.
+
+Only exact-channel subscriptions are counted by `CHANNELS` and `NUMSUB`: a client subscribed with [`PSUBSCRIBE`](/docs/redis/commands/pub-sub/psubscribe) will receive matching messages but does not make a channel appear as active. Use these forms for monitoring and debugging, for instance to confirm that a consumer is really attached before publishing.
 
 ## Syntax
 
@@ -40974,7 +41432,11 @@ fn main() -> redis::RedisResult<()> {
 # PUNSUBSCRIBE
 Source: https://upstash.com/docs/redis/commands/pub-sub/punsubscribe
 
-Use `PUNSUBSCRIBE` to unsubscribe from patterns.
+Use `PUNSUBSCRIBE` to cancel pattern subscriptions of the current connection.
+
+With no arguments the connection unsubscribes from every pattern it registered, otherwise only from the patterns named, which must be given exactly as they were passed to [`PSUBSCRIBE`](/docs/redis/commands/pub-sub/psubscribe), since patterns are matched literally here and not expanded. The server sends one confirmation per pattern with the number of subscriptions still active.
+
+Exact-channel subscriptions are not affected; cancel those with [`UNSUBSCRIBE`](/docs/redis/commands/pub-sub/unsubscribe).
 
 ## Syntax
 
@@ -41120,7 +41582,11 @@ fn main() -> redis::RedisResult<()> {
 # SUBSCRIBE
 Source: https://upstash.com/docs/redis/commands/pub-sub/subscribe
 
-Use `SUBSCRIBE` to subscribe to channels.
+Use `SUBSCRIBE` to subscribe the current connection to one or more channels.
+
+The server confirms each channel with its own reply carrying the running number of subscriptions this connection holds, and from then on messages published to those channels arrive on the connection as they are sent.
+
+Under RESP2 a subscribed connection may only run subscription commands plus `PING`, `RESET`, and `QUIT`, which is why subscribers normally use a dedicated connection. Under RESP3 messages arrive as push replies and ordinary commands remain usable on the same connection. Messages published while the connection is not subscribed are not delivered later, since pub/sub keeps no history.
 
 ## Syntax
 
@@ -41272,7 +41738,11 @@ fn main() -> redis::RedisResult<()> {
 # UNSUBSCRIBE
 Source: https://upstash.com/docs/redis/commands/pub-sub/unsubscribe
 
-Use `UNSUBSCRIBE` to unsubscribe from channels.
+Use `UNSUBSCRIBE` to cancel channel subscriptions of the current connection.
+
+With no arguments the connection unsubscribes from every channel it is subscribed to, otherwise only from the ones named. The server sends one confirmation per channel, each carrying the number of subscriptions still active, and the connection leaves subscriber mode once that count reaches zero.
+
+Pattern subscriptions are not affected; cancel those with [`PUNSUBSCRIBE`](/docs/redis/commands/pub-sub/punsubscribe).
 
 ## Syntax
 
@@ -41418,7 +41888,13 @@ fn main() -> redis::RedisResult<()> {
 # EVAL
 Source: https://upstash.com/docs/redis/commands/scripting/eval
 
-Use `EVAL` to execute a Lua script.
+Use `EVAL` to run a Lua script on the server.
+
+`<numkeys>` says how many of the arguments that follow are key names. The script receives those in the `KEYS` table and every remaining argument in `ARGV`. Passing key names as keys rather than hardcoding them in the script body matters, because Redis uses that list for routing and access checks. Inside the script, `redis.call` runs Redis commands and its return value is converted to a Lua value.
+
+The script runs as a single atomic step: no other command executes while it is running, which makes it the standard way to do read, decide, and write logic, such as a rate limiter or a compare-and-set update, in one round trip and without a transaction. Keep scripts short for the same reason, since a long script blocks everything else, and keep them deterministic by deriving values from `KEYS`, `ARGV`, or data read inside the script rather than from clock or random sources.
+
+Sending a script also caches it under its SHA1 digest, so later calls can use [`EVALSHA`](/docs/redis/commands/scripting/evalsha) and avoid resending the body. Use [`EVAL_RO`](/docs/redis/commands/scripting/eval-ro) for scripts that only read.
 
 ## Syntax
 
@@ -41593,7 +42069,9 @@ fn main() -> redis::RedisResult<()> {
 # EVAL_RO
 Source: https://upstash.com/docs/redis/commands/scripting/eval-ro
 
-Use `EVAL_RO` to execute read-only Lua script.
+Use `EVAL_RO` to run a Lua script that is not allowed to write.
+
+It behaves like [`EVAL`](/docs/redis/commands/scripting/eval), with `<numkeys>` splitting the arguments into the `KEYS` and `ARGV` tables, except that any write command called from the script fails with an error. Declaring the read-only intent lets the server serve the call on replicas and turns an accidental write into a clear error instead of an unexpected modification, which is worth doing for every script that only computes over existing data.
 
 ## Syntax
 
@@ -41768,7 +42246,11 @@ fn main() -> redis::RedisResult<()> {
 # EVALSHA
 Source: https://upstash.com/docs/redis/commands/scripting/evalsha
 
-Use `EVALSHA` to execute cached Lua script by SHA.
+Use `EVALSHA` to run a script that is already in the server's script cache, identified by its SHA1 digest.
+
+It behaves exactly like [`EVAL`](/docs/redis/commands/scripting/eval) but sends only the 40-character digest instead of the script body, which keeps the request small when a script is called often. The digest is what [`SCRIPT LOAD`](/docs/redis/commands/scripting/script-load) returns, and it is also computed as a side effect of any `EVAL` call.
+
+When the script is not in the cache the server replies with a `NOSCRIPT` error, and the client is expected to fall back to `EVAL`. Most client libraries do this automatically. The cache does not survive a restart and is cleared by [`SCRIPT FLUSH`](/docs/redis/commands/scripting/script-flush), so applications must always be able to resend the script body.
 
 ## Syntax
 
@@ -41942,6 +42424,8 @@ Source: https://upstash.com/docs/redis/commands/scripting/evalsha-ro
 
 Use `EVALSHA_RO` to run a script cached by its SHA1 digest. The script may not write to the database.
 
+It is the read-only form of [`EVALSHA`](/docs/redis/commands/scripting/evalsha): any write command called from the script fails, which lets the server run it on replicas. As with `EVALSHA`, a digest that is not in the cache produces a `NOSCRIPT` error, and the caller is expected to fall back to [`EVAL_RO`](/docs/redis/commands/scripting/eval-ro) with the script body.
+
 ## Syntax
 
 ```redis
@@ -42126,7 +42610,9 @@ Source: https://upstash.com/docs/redis/commands/scripting/overview
 # SCRIPT EXISTS
 Source: https://upstash.com/docs/redis/commands/scripting/script-exists
 
-Use `SCRIPT EXISTS` to check if scripts exist in cache.
+Use `SCRIPT EXISTS` to check which of the given SHA1 digests are present in the script cache.
+
+The reply holds one `1` or `0` per digest, in the order they were given. Client libraries use it to find out, in a single call, which of their scripts still need to be loaded before they can be invoked with [`EVALSHA`](/docs/redis/commands/scripting/evalsha), instead of discovering the gap through a `NOSCRIPT` error at call time.
 
 ## Syntax
 
@@ -42293,7 +42779,9 @@ fn main() -> redis::RedisResult<()> {
 # SCRIPT FLUSH
 Source: https://upstash.com/docs/redis/commands/scripting/script-flush
 
-Use `SCRIPT FLUSH` to clear the script cache.
+Use `SCRIPT FLUSH` to remove every script from the server's script cache.
+
+After the flush, [`EVALSHA`](/docs/redis/commands/scripting/evalsha) calls fail with `NOSCRIPT` until the scripts are loaded again, so run it when you want clients to resend their current script bodies, typically after deploying changed scripts. `ASYNC` reclaims the memory in the background and `SYNC` reclaims it before the reply. Cached scripts are not part of the dataset, so flushing them does not touch your data.
 
 ## Syntax
 
@@ -42458,6 +42946,10 @@ Source: https://upstash.com/docs/redis/commands/scripting/script-kill
 
 Use `SCRIPT KILL` to stop a running read-only script.
 
+Only a script that has not yet written anything can be killed: stopping one halfway through its writes would leave the dataset in a state that no atomic execution could produce, so Redis refuses and the server has to be restarted instead. This is the main reason to keep scripts short and to use [`EVAL_RO`](/docs/redis/commands/scripting/eval-ro) wherever a script only reads.
+
+The current Upstash deployment recognizes the command but has no interruptible running-script state to act on, so it replies with a `NOTBUSY` error.
+
 ## Syntax
 
 ```redis
@@ -42614,7 +43106,11 @@ fn main() -> redis::RedisResult<()> {
 # SCRIPT LOAD
 Source: https://upstash.com/docs/redis/commands/scripting/script-load
 
-Use `SCRIPT LOAD` to load script into cache.
+Use `SCRIPT LOAD` to compile a script and put it in the server's script cache without running it.
+
+The reply is the script's SHA1 digest, which is what [`EVALSHA`](/docs/redis/commands/scripting/evalsha) takes. Loading the same script twice is harmless and always yields the same digest, so applications typically load their scripts once at startup and then call them by digest.
+
+The cache is lost on restart and cleared by [`SCRIPT FLUSH`](/docs/redis/commands/scripting/script-flush), so keep the script source available and be ready to handle a `NOSCRIPT` error by loading it again.
 
 ## Syntax
 
@@ -42837,6 +43333,12 @@ Source: https://upstash.com/docs/redis/commands/search/search-aggregate
 
 Use `SEARCH.AGGREGATE` to compute metrics and buckets over matching documents.
 
+The command takes two JSON arguments. The first is a filter, in the same language as [`SEARCH.QUERY`](/docs/redis/commands/search/search-query), which selects the documents to aggregate; pass `'{}'` to cover the whole index. The second describes the aggregations to compute, as named entries such as `{"avg_price": {"$avg": {"field": "price"}}}`.
+
+Metric operators like `$avg`, `$sum`, `$min`, `$max`, `$stats`, and `$cardinality` reduce the selected documents to a single number, while bucket operators like `$terms`, `$range`, `$histogram`, and `$dateHistogram` group them and report a count per bucket. Bucket operators accept nested `$aggs`, so you can compute a metric inside each bucket, for example the average price per category, and several aggregations can be requested in one call since they all run over the same selected document set.
+
+See [Aggregations](/docs/redis/search/aggregations) for the full operator reference and examples.
+
 ## Syntax
 
 ```redis
@@ -42959,6 +43461,8 @@ Source: https://upstash.com/docs/redis/commands/search/search-aliasadd
 
 Use `SEARCH.ALIASADD` to create an alias or update an existing alias to point to a search index.
 
+An alias is a stable name that queries can use in place of a real index name, so the index behind it can be replaced without touching application code. Pointing an existing alias at a different index is atomic, which is what makes zero-downtime reindexing possible: build the new index under a fresh name, then move the alias to it in one step.
+
 See [Aliases](/docs/redis/search/aliases#adding-an-alias) for feature examples, including zero-downtime index swaps.
 
 The target name is not required to exist when the alias is created, so aliases can temporarily be dangling. Most commands resolve aliases, but [`SEARCH.DROP`](/docs/redis/commands/search/search-drop) always uses a literal index name.
@@ -43064,6 +43568,8 @@ Source: https://upstash.com/docs/redis/commands/search/search-aliasdel
 
 Use `SEARCH.ALIASDEL` to remove a search index alias.
 
+Only the alias is removed: the index it pointed to, and the documents indexed in it, are untouched and remain reachable under their real name. Queries that still use the alias fail once it is gone.
+
 See [Deleting an Alias](/docs/redis/search/aliases#deleting-an-alias) for the feature guide.
 
 ## Syntax
@@ -43155,6 +43661,8 @@ Source: https://upstash.com/docs/redis/commands/search/search-count
 
 Use `SEARCH.COUNT` to count documents matching a query without retrieving them.
 
+The filter is the same JSON object that [`SEARCH.QUERY`](/docs/redis/commands/search/search-query) takes, but only the number of matching documents is computed and returned, so nothing depends on the size of the result and no `LIMIT` gets in the way of the total. That makes it the right command for result counters, pagination totals, and cheap existence checks over a filter.
+
 See [Counting](/docs/redis/search/counting) for feature examples and common use cases.
 
 ## Syntax
@@ -43266,6 +43774,10 @@ Source: https://upstash.com/docs/redis/commands/search/search-create
 
 Use `SEARCH.CREATE` to create a search index over JSON, hash, or string values.
 
+`ON` names the type of key to index and `PREFIX` the key prefixes to watch, so the index covers exactly the keys that match both, including keys written after it was created. The `SCHEMA` then declares which fields are searchable and how: `TEXT` fields are analyzed for full-text search, with `NOSTEM` and `NOTOKENIZE` to turn parts of that off, numeric, boolean, and date fields are matched exactly and can be marked `FAST` to make them usable for sorting and scoring, and `KEYWORD` and `FACET` fields are kept whole for exact matching and faceting. `FROM` maps a schema field to a differently named field in the document.
+
+Creating an index starts an initial scan of the matching keys, which `SKIPINITIALSCAN` skips when you only want to index data written from now on; [`SEARCH.REINDEX`](/docs/redis/commands/search/search-reindex) can run that scan later. `EXISTSOK` makes the command succeed instead of failing when the index already exists.
+
 See [Index Management](/docs/redis/search/index-management#creating-an-index) for a feature-level guide to creating indexes and [Schema Definition](/docs/redis/search/schema-definition) for field types and schema design.
 
 <Note>
@@ -43430,6 +43942,8 @@ Source: https://upstash.com/docs/redis/commands/search/search-describe
 
 Use `SEARCH.DESCRIBE` to return metadata about a search index.
 
+The reply reports how the index is defined, the key type and prefixes it covers, and the fields in its schema with their types and options, along with its current state such as the number of indexed documents. It is the way to confirm what an index actually indexes before writing queries against it, and to check whether a schema change was applied.
+
 See [Describing an Index](/docs/redis/search/index-management#describing-an-index) for the feature guide.
 
 The command accepts an index name or alias. When an alias is used, the response describes its target and reports the target's index name.
@@ -43551,6 +44065,8 @@ Source: https://upstash.com/docs/redis/commands/search/search-drop
 
 Use `SEARCH.DROP` to remove a search index. The underlying Redis keys are not deleted.
 
+Only the index and its internal structures go away, so the documents themselves stay exactly as they are and can be indexed again later by creating a new index over the same prefixes. Queries against the dropped name fail from then on.
+
 See [Dropping an Index](/docs/redis/search/index-management#dropping-an-index) for the feature guide.
 
 `SEARCH.DROP` does not resolve aliases: `<name>` is always treated as the literal index name. Aliases that point to a dropped index are not removed automatically.
@@ -43648,6 +44164,8 @@ Source: https://upstash.com/docs/redis/commands/search/search-listaliases
 
 Use `SEARCH.LISTALIASES` to return all aliases and the indexes they point to.
 
+The reply pairs each alias with its target index name, which is how you check what an alias currently resolves to before or after swapping it. Aliases whose target no longer exists are still listed, since an alias may point at a name that has not been created yet.
+
 See [Listing Aliases](/docs/redis/search/aliases#listing-aliases) for the feature guide.
 
 ## Syntax
@@ -43745,6 +44263,8 @@ Source: https://upstash.com/docs/redis/commands/search/search-listindexes
 
 Use `SEARCH.LISTINDEXES` to list search indexes in the database.
 
+`MATCH` filters index names with a glob-style pattern, while `LIMIT` and `OFFSET` page through the reply, which keeps the command usable on a database with many indexes. Only index names are returned; use [`SEARCH.DESCRIBE`](/docs/redis/commands/search/search-describe) to see an index's schema and settings.
+
 See [Listing Indexes](/docs/redis/search/index-management#listing-indexes) for the feature guide.
 
 ## Syntax
@@ -43884,6 +44404,12 @@ Source: https://upstash.com/docs/redis/commands/search/search-query
 
 Use `SEARCH.QUERY` to search for documents matching a JSON filter.
 
+The filter is a JSON object naming index fields and the values to match, so `'{"name": "headphones", "inStock": true}'` combines conditions with an implicit AND. Text fields are matched with the analysis configured in the schema while other types are matched exactly, and operators such as `$fuzzy`, `$prefix`, `$range`, `$or`, and `$mustNot` cover the cases where plain field matching is not enough. Querying an index that does not exist returns null.
+
+Results come back ordered by relevance score by default. `ORDERBY` sorts by a `FAST` field instead, `LIMIT` and `OFFSET` page through the matches, `SELECT` and `NOCONTENT` cut the payload down to the fields you need, `HIGHLIGHT` wraps the matched terms in tags for display, and `SCOREFUNC` blends numeric fields such as popularity or recency into the relevance score.
+
+See [Querying and filtering](/docs/redis/search/querying) for the full filter syntax and worked examples, and [`SEARCH.COUNT`](/docs/redis/commands/search/search-count) when you only need the number of matches.
+
 ## Syntax
 
 ```redis
@@ -44198,7 +44724,13 @@ curl -X POST https://YOUR_ENDPOINT.upstash.io \
 # ACL
 Source: https://upstash.com/docs/redis/commands/server/acl
 
-Use `ACL` to manage access control list.
+Use `ACL` to inspect and manage the users, rules, and permissions of the database's access control list.
+
+`SETUSER` creates or updates a user and applies rules from left to right: rules enable or disable the user (`on`, `off`), set passwords (`>password`, `<password`), and grant or revoke access to commands (`+get`, `-@admin`) and to key patterns (`~cache:*`). `GETUSER` shows the resulting rules for one user, `USERS` and `LIST` enumerate users in short and full form, and `DELUSER` removes them. `WHOAMI` reports the user the current connection is authenticated as, `CAT` lists the command categories that can be used in rules, and `GENPASS` returns a cryptographically strong random password. `LOG` shows recent authentication and permission failures, which is where to look when a client is unexpectedly denied, and `RESET` on that subcommand clears it. `LOAD` and `SAVE` reload and persist the ACL file.
+
+Upstash adds two deployment-specific forms: `RESTTOKEN` returns the REST token of an existing user, given that user's password, and `GENTOKEN` builds a token for a username and password pair, generating a strong password when none is given, so the token can be passed to `SETUSER` as the user's password. Together they are how an ACL user is given access to the REST API alongside the TCP endpoint.
+
+Changes take effect immediately on new and existing connections, so a rule that narrows access can lock out a running application; check with `GETUSER` before applying it broadly.
 
 ## Syntax
 
@@ -44375,7 +44907,9 @@ fn main() -> redis::RedisResult<()> {
 # COMMAND
 Source: https://upstash.com/docs/redis/commands/server/command
 
-Use `COMMAND` to get command metadata.
+Use `COMMAND` to get metadata about the commands the server supports, such as their arity, flags, and key positions. Client libraries call it during connection setup to discover how to route commands and where their keys are.
+
+The current Upstash deployment accepts the command for client compatibility but returns an empty array rather than exposing the server command table, so clients fall back to their built-in command metadata.
 
 ## Syntax
 
@@ -44532,7 +45066,11 @@ fn main() -> redis::RedisResult<()> {
 # CONFIG GET
 Source: https://upstash.com/docs/redis/commands/server/config-get
 
-Use `CONFIG GET` to read runtime configuration.
+Use `CONFIG GET` to read runtime configuration parameters.
+
+Parameter names may contain glob-style patterns, so one call can fetch a family of settings, and the reply is a flat array of alternating names and values in both RESP2 and RESP3.
+
+This deployment exposes only `notify-keyspace-events`, which controls the keyspace notifications published on pub/sub. Other names simply return no matching entries rather than an error, so check the reply for the parameter you asked about instead of assuming it was present.
 
 ## Syntax
 
@@ -44694,7 +45232,11 @@ fn main() -> redis::RedisResult<()> {
 # CONFIG SET
 Source: https://upstash.com/docs/redis/commands/server/config-set
 
-Use `CONFIG SET` to change runtime configuration.
+Use `CONFIG SET` to change runtime configuration parameters without restarting.
+
+This deployment permits changes only to `notify-keyspace-events`, which selects the keyspace and keyevent notifications the server publishes: the value is a set of flag characters, such as `KEA` for everything, or `Kg$` for generic and string keyspace events. Any other parameter returns an error.
+
+Several parameter and value pairs can be given in one call, and they are processed from left to right, so if a later pair is rejected an earlier change may already have taken effect.
 
 ## Syntax
 
@@ -44858,7 +45400,9 @@ fn main() -> redis::RedisResult<()> {
 # DBSIZE
 Source: https://upstash.com/docs/redis/commands/server/dbsize
 
-Use `DBSIZE` to get number of keys in database.
+Use `DBSIZE` to get the number of keys stored in the database.
+
+The count covers keys of every type, and keys whose expiration has passed but that have not been removed yet may still be included, so treat the number as an accurate but momentary figure rather than an exact one. It is the quick way to see how a keyspace is growing, and unlike [`KEYS`](/docs/redis/commands/generic/keys) it does not build a list of key names to do so.
 
 ## Syntax
 
@@ -45024,7 +45568,11 @@ fn main() -> redis::RedisResult<()> {
 # FLUSHALL
 Source: https://upstash.com/docs/redis/commands/server/flushall
 
-Use `FLUSHALL` to delete all keys in all databases.
+Use `FLUSHALL` to delete every key in every database.
+
+Upstash exposes a single logical database, so `FLUSHALL` and [`FLUSHDB`](/docs/redis/commands/server/flushdb) have the same effect here. `ASYNC` frees the memory in a background thread, which returns faster on large datasets, while `SYNC` frees it before replying.
+
+The deletion is immediate and irreversible: there is no confirmation step and nothing to undo. Keep it out of application code, run it only against disposable databases, and require an explicit operator action wherever tooling exposes it.
 
 ## Syntax
 
@@ -45193,7 +45741,11 @@ fn main() -> redis::RedisResult<()> {
 # FLUSHDB
 Source: https://upstash.com/docs/redis/commands/server/flushdb
 
-Use `FLUSHDB` to delete all keys in current database.
+Use `FLUSHDB` to delete every key in the current database.
+
+Since Upstash exposes a single logical database, this removes everything, exactly like [`FLUSHALL`](/docs/redis/commands/server/flushall). `ASYNC` frees the memory in a background thread and `SYNC` frees it before replying.
+
+The deletion is immediate and irreversible. It is a convenient way to reset a test database between runs, and it should never be reachable from application code that runs against production data.
 
 ## Syntax
 
@@ -45362,7 +45914,11 @@ fn main() -> redis::RedisResult<()> {
 # INFO
 Source: https://upstash.com/docs/redis/commands/server/info
 
-Use `INFO` to get server statistics and information.
+Use `INFO` to get statistics and information about the server.
+
+The reply groups fields into sections such as `server`, `clients`, `memory`, `stats`, `replication`, and `keyspace`, and passing a section name limits the reply to that one. It is the usual source for operational numbers such as connected clients, memory in use, hit and miss counts, and the number of keys per database.
+
+On Upstash, `default` and `all` return the same set of sections, and a section name that is not supported produces only its heading. The reply is a CRLF-delimited text report rather than a RESP map, so parse it defensively, since fields may be added over time.
 
 ## Syntax
 
@@ -45523,7 +46079,11 @@ fn main() -> redis::RedisResult<()> {
 # MONITOR
 Source: https://upstash.com/docs/redis/commands/server/monitor
 
-Use `MONITOR` to stream all commands received.
+Use `MONITOR` to stream every command the server processes, as it happens, to the current connection.
+
+The connection turns into a continuous feed and stops accepting other commands, so it must be a dedicated one; closing it is how you stop monitoring. Each line carries a timestamp, the client that sent the command, and the command with its arguments.
+
+It is a debugging tool: it shows the traffic of all clients, arguments included, so it can expose sensitive data, and the added work costs the server throughput while it is running. Use it briefly and against non-production data where possible.
 
 ## Syntax
 
@@ -45664,7 +46224,9 @@ Source: https://upstash.com/docs/redis/commands/server/overview
 # TIME
 Source: https://upstash.com/docs/redis/commands/server/time
 
-Use `TIME` to get current server time.
+Use `TIME` to read the server's clock.
+
+The reply has two values: the Unix time in seconds and the microseconds elapsed within the current second. Because it comes from the server, every client gets the same reference regardless of its own clock drift, which makes it the value to use when computing deadlines, measuring intervals, or writing timestamps that different machines must agree on.
 
 ## Syntax
 
@@ -45835,9 +46397,9 @@ Source: https://upstash.com/docs/redis/commands/set/overview
 <Card title="SINTERSTORE" href="/redis/commands/set/sinterstore">Store set intersection</Card>
 <Card title="SISMEMBER" href="/redis/commands/set/sismember">Check if member exists in set</Card>
 <Card title="SMEMBERS" href="/redis/commands/set/smembers">Get all set members</Card>
-<Card title="SMISMEMBER" href="/redis/commands/set/smismember">Check multiple members</Card>
+<Card title="SMISMEMBER" href="/redis/commands/set/smismember">Check membership of several values</Card>
 <Card title="SMOVE" href="/redis/commands/set/smove">Move member between sets</Card>
-<Card title="SPOP" href="/redis/commands/set/spop">Remove random members</Card>
+<Card title="SPOP" href="/redis/commands/set/spop">Remove and return random members</Card>
 <Card title="SRANDMEMBER" href="/redis/commands/set/srandmember">Get random members</Card>
 <Card title="SREM" href="/redis/commands/set/srem">Remove members from a set</Card>
 <Card title="SSCAN" href="/redis/commands/set/sscan">Incrementally iterate set members</Card>
@@ -45848,7 +46410,9 @@ Source: https://upstash.com/docs/redis/commands/set/overview
 # SADD
 Source: https://upstash.com/docs/redis/commands/set/sadd
 
-Use `SADD` to add members to a set.
+Use `SADD` to add one or more members to a set, creating it when the key does not exist.
+
+A set holds unique, unordered members, so adding a member that is already there changes nothing, and the reply counts only the members that were actually new. That count is what makes the command a cheap deduplicator: a reply of `1` means this caller was the first to see the value, which is enough to decide whether to process an event or ignore it as a repeat.
 
 ## Syntax
 
@@ -46016,7 +46580,9 @@ fn main() -> redis::RedisResult<()> {
 # SCARD
 Source: https://upstash.com/docs/redis/commands/set/scard
 
-Use `SCARD` to get set cardinality.
+Use `SCARD` to get the number of members in a set.
+
+The reply is `0` when the key does not exist. The size is maintained by Redis rather than counted on demand, so the command is cheap on sets of any size, which makes it the right way to check how large a set has become before reading it with [`SMEMBERS`](/docs/redis/commands/set/smembers).
 
 ## Syntax
 
@@ -46181,7 +46747,11 @@ fn main() -> redis::RedisResult<()> {
 # SDIFF
 Source: https://upstash.com/docs/redis/commands/set/sdiff
 
-Use `SDIFF` to get set difference.
+Use `SDIFF` to get the members of the first set that are not present in any of the other sets.
+
+Keys that do not exist count as empty sets, so a missing first key yields an empty result. The difference is computed on the fly and nothing is stored; use [`SDIFFSTORE`](/docs/redis/commands/set/sdiffstore) to keep the result.
+
+It answers questions of the form "who is in A but not in B", such as users who signed up but never converted. The cost grows with the size of the sets involved, so on large sets prefer storing the result and reusing it.
 
 ## Syntax
 
@@ -46347,7 +46917,11 @@ fn main() -> redis::RedisResult<()> {
 # SDIFFSTORE
 Source: https://upstash.com/docs/redis/commands/set/sdiffstore
 
-Use `SDIFFSTORE` to store set difference.
+Use `SDIFFSTORE` to compute the difference between sets and store it in another key.
+
+The destination holds the members of the first source set that are absent from all the others. It is overwritten if it already exists, and deleted when the result is empty. The reply is the number of members stored.
+
+Storing rather than returning the result is what you want when the difference is large or is used more than once, since the destination is an ordinary set that can be paged through or fed into further set operations.
 
 ## Syntax
 
@@ -46514,7 +47088,11 @@ fn main() -> redis::RedisResult<()> {
 # SINTER
 Source: https://upstash.com/docs/redis/commands/set/sinter
 
-Use `SINTER` to get set intersection.
+Use `SINTER` to get the members present in every one of the given sets.
+
+A key that does not exist counts as an empty set, which makes the whole intersection empty. The result is computed on each call and not stored; use [`SINTERSTORE`](/docs/redis/commands/set/sinterstore) to keep it, or [`SINTERCARD`](/docs/redis/commands/set/sintercard) when only the number of common members matters.
+
+Intersections express "and" queries over sets, such as the users who are in both a campaign audience and a paying-customer set.
 
 ## Syntax
 
@@ -46680,7 +47258,11 @@ fn main() -> redis::RedisResult<()> {
 # SINTERCARD
 Source: https://upstash.com/docs/redis/commands/set/sintercard
 
-Use `SINTERCARD` to get intersection cardinality.
+Use `SINTERCARD` to get the number of members that the given sets have in common, without building the intersection.
+
+`<numkeys>` states how many keys follow. `LIMIT` stops counting once that many common members have been found and returns the limit, which turns an expensive full intersection into a cheap "do these sets share at least N members" test. `LIMIT 0` means no limit.
+
+Since nothing is transferred beyond the count, this is much lighter than running [`SINTER`](/docs/redis/commands/set/sinter) and measuring the reply.
 
 ## Syntax
 
@@ -46846,7 +47428,9 @@ fn main() -> redis::RedisResult<()> {
 # SINTERSTORE
 Source: https://upstash.com/docs/redis/commands/set/sinterstore
 
-Use `SINTERSTORE` to store set intersection.
+Use `SINTERSTORE` to compute the intersection of sets and store it in another key.
+
+The destination is overwritten if it exists and deleted when the intersection is empty, and the reply is the number of members stored. Materializing the result pays off when the same intersection is read repeatedly or feeds further set operations, since the destination is an ordinary set.
 
 ## Syntax
 
@@ -47012,7 +47596,9 @@ fn main() -> redis::RedisResult<()> {
 # SISMEMBER
 Source: https://upstash.com/docs/redis/commands/set/sismember
 
-Use `SISMEMBER` to check if member exists in set.
+Use `SISMEMBER` to check whether a value is a member of a set.
+
+The reply is `1` when it is and `0` when it is not or the key does not exist. The check is a constant-time lookup and transfers nothing but the answer, which is why sets are the right structure for membership questions such as permission or blocklist checks. Use [`SMISMEMBER`](/docs/redis/commands/set/smismember) to test several values in one call.
 
 ## Syntax
 
@@ -47178,7 +47764,9 @@ fn main() -> redis::RedisResult<()> {
 # SMEMBERS
 Source: https://upstash.com/docs/redis/commands/set/smembers
 
-Use `SMEMBERS` to get all set members.
+Use `SMEMBERS` to get every member of a set.
+
+A missing key returns an empty result, and members come back in no particular order, since sets are unordered. The whole set is transferred in one reply, so on large sets prefer [`SSCAN`](/docs/redis/commands/set/sscan), which walks the members in batches, and use [`SISMEMBER`](/docs/redis/commands/set/sismember) when you only want to test membership.
 
 ## Syntax
 
@@ -47343,7 +47931,9 @@ fn main() -> redis::RedisResult<()> {
 # SMISMEMBER
 Source: https://upstash.com/docs/redis/commands/set/smismember
 
-Use `SMISMEMBER` to check multiple members.
+Use `SMISMEMBER` to check several values for membership in a set in one call.
+
+The reply holds one `1` or `0` per value, in the order given, so it lines up with your input list. A missing key yields all zeros rather than an error. It replaces a series of [`SISMEMBER`](/docs/redis/commands/set/sismember) round trips, which matters when checking a batch of ids against a blocklist or an entitlement set.
 
 ## Syntax
 
@@ -47509,7 +48099,11 @@ fn main() -> redis::RedisResult<()> {
 # SMOVE
 Source: https://upstash.com/docs/redis/commands/set/smove
 
-Use `SMOVE` to move member between sets.
+Use `SMOVE` to move a member from one set to another atomically.
+
+The reply is `1` when the member was moved and `0` when it was not in the source set, in which case nothing changes. If the member already exists in the destination it is simply removed from the source. The destination is created when it does not exist, and the source is deleted when its last member leaves.
+
+Because the removal and the insertion happen as one step, this is the safe way to move an item between states, such as from a pending set to a done set, without a window in which it is in both or in neither.
 
 ## Syntax
 
@@ -47678,7 +48272,11 @@ fn main() -> redis::RedisResult<()> {
 # SPOP
 Source: https://upstash.com/docs/redis/commands/set/spop
 
-Use `SPOP` to remove random members.
+Use `SPOP` to remove and return random members of a set.
+
+Without a count one member is returned, or null when the key does not exist. With a count, up to that many distinct members are removed at once, capped at the size of the set, and the key is deleted when the last member is taken.
+
+Since the read and the removal are atomic, no two callers can get the same member, which makes a set usable as a pool of unique items to hand out, such as invitation codes or shard assignments. Use [`SRANDMEMBER`](/docs/redis/commands/set/srandmember) when the members should stay in the set.
 
 ## Syntax
 
@@ -47844,7 +48442,11 @@ fn main() -> redis::RedisResult<()> {
 # SRANDMEMBER
 Source: https://upstash.com/docs/redis/commands/set/srandmember
 
-Use `SRANDMEMBER` to get random members.
+Use `SRANDMEMBER` to get random members of a set without removing them.
+
+Without a count one member is returned, or null when the key does not exist. A positive count returns up to that many distinct members, capped at the size of the set, while a negative count returns exactly that many members chosen independently, so the same member can appear more than once.
+
+This is the command for sampling, random selection, and inspecting an unfamiliar set. Use [`SPOP`](/docs/redis/commands/set/spop) when the chosen members must be consumed.
 
 ## Syntax
 
@@ -48010,7 +48612,9 @@ fn main() -> redis::RedisResult<()> {
 # SREM
 Source: https://upstash.com/docs/redis/commands/set/srem
 
-Use `SREM` to remove members from a set.
+Use `SREM` to remove one or more members from a set.
+
+The reply counts only the members that were actually present, so removing something that is already gone is not an error. The key is deleted when its last member is removed, which is why a set that has been fully drained no longer exists rather than existing as an empty set.
 
 ## Syntax
 
@@ -48176,7 +48780,11 @@ fn main() -> redis::RedisResult<()> {
 # SSCAN
 Source: https://upstash.com/docs/redis/commands/set/sscan
 
-Use `SSCAN` to incrementally iterate set members.
+Use `SSCAN` to iterate the members of a set in batches instead of reading them all at once.
+
+Each call takes a cursor and returns the next cursor together with a batch of members. Start at cursor `0` and keep calling with the cursor from the previous reply until the server returns `0`, which ends the iteration. `MATCH` filters members with a glob-style pattern and `COUNT` hints at how much work each call should do.
+
+Filtering happens after a batch is read, so a call can come back empty while the cursor is still non-zero: only the cursor tells you the iteration is over. Members present for the whole iteration are returned at least once, while those added or removed while it runs may or may not appear, and a member can be returned more than once, so keep the processing idempotent.
 
 ## Syntax
 
@@ -48351,7 +48959,9 @@ fn main() -> redis::RedisResult<()> {
 # SUNION
 Source: https://upstash.com/docs/redis/commands/set/sunion
 
-Use `SUNION` to get set union.
+Use `SUNION` to get every member that appears in at least one of the given sets.
+
+Duplicates across the sources collapse, since the result is itself a set, and keys that do not exist count as empty sets. The union is computed on each call and nothing is stored; use [`SUNIONSTORE`](/docs/redis/commands/set/sunionstore) to keep the result. It answers "or" questions over sets, such as everyone reachable through any of several audiences.
 
 ## Syntax
 
@@ -48517,7 +49127,9 @@ fn main() -> redis::RedisResult<()> {
 # SUNIONSTORE
 Source: https://upstash.com/docs/redis/commands/set/sunionstore
 
-Use `SUNIONSTORE` to store set union.
+Use `SUNIONSTORE` to compute the union of sets and store it in another key.
+
+The destination is overwritten if it exists and deleted when the union is empty, and the reply is the number of members stored. Materializing the union is the usual way to build a combined audience once and then intersect or difference it with other sets, instead of recomputing it on every query.
 
 ## Syntax
 
@@ -48685,6 +49297,10 @@ Source: https://upstash.com/docs/redis/commands/sorted-set/bzmpop
 
 Use `BZMPOP` to pop members from the first non-empty sorted set among several, blocking until one has members or the timeout expires.
 
+It is the blocking form of [`ZMPOP`](/docs/redis/commands/sorted-set/zmpop): keys are examined in the order given, so earlier keys act as higher priority queues, `MIN` or `MAX` chooses whether the lowest or highest scoring members are taken, and `COUNT` sets how many. The reply names the key that was popped from along with the members and their scores.
+
+The timeout is in seconds, may be fractional, and `0` waits indefinitely; when it expires the reply is null. This is what a worker uses to wait on several priority queues at once without polling.
+
 ## Syntax
 
 ```redis
@@ -48698,7 +49314,7 @@ BZMPOP <timeout> <numkeys> <key> [<key> ...] (MIN | MAX) [COUNT <count>]
 | `<timeout>` | Yes | No | Seconds to block; `0` blocks indefinitely. |
 | `<numkeys>` | Yes | No | Number of key arguments that follow. |
 | `<key>` | Yes | Yes | Redis key targeted by the command. |
-| `(MIN \| MAX)` | Yes | No | Choose one form: `MIN`; `MAX`. |
+| `(MIN \| MAX)` | Yes | No | Which members to pop: `MIN` (lowest scores first) or `MAX` (highest scores first). |
 | `COUNT <count>` | No | No | Maximum number of members to pop. |
 
 ## Important points
@@ -48852,6 +49468,10 @@ Source: https://upstash.com/docs/redis/commands/sorted-set/bzpopmax
 
 Use `BZPOPMAX` to pop the highest-scoring member from the first non-empty sorted set, blocking until one has a member or the timeout expires.
 
+It is the blocking form of [`ZPOPMAX`](/docs/redis/commands/sorted-set/zpopmax) and accepts several keys, which are checked in the order given. The reply names the key the member came from together with the member and its score.
+
+The timeout is in seconds, may be fractional, and `0` waits indefinitely; when it expires the reply is null. With the score used as a priority, this turns a sorted set into a priority queue whose consumers wait for work instead of polling, and clients blocked on the same key are served in the order they started waiting.
+
 ## Syntax
 
 ```redis
@@ -49014,6 +49634,10 @@ Source: https://upstash.com/docs/redis/commands/sorted-set/bzpopmin
 
 Use `BZPOPMIN` to pop the lowest-scoring member from the first non-empty sorted set, blocking until one has a member or the timeout expires.
 
+It is the blocking form of [`ZPOPMIN`](/docs/redis/commands/sorted-set/zpopmin) and accepts several keys, checked in the order given, with the reply naming the key the member came from along with the member and its score.
+
+The timeout is in seconds, may be fractional, and `0` waits indefinitely; when it expires the reply is null. Since the lowest score is popped first, a set scored by timestamp or priority number becomes a queue that hands out the most urgent item to whichever worker is waiting.
+
 ## Syntax
 
 ```redis
@@ -49188,15 +49812,15 @@ Source: https://upstash.com/docs/redis/commands/sorted-set/overview
 <Card title="ZINTERCARD" href="/redis/commands/sorted-set/zintercard">Get intersection cardinality</Card>
 <Card title="ZINTERSTORE" href="/redis/commands/sorted-set/zinterstore">Store sorted set intersection</Card>
 <Card title="ZLEXCOUNT" href="/redis/commands/sorted-set/zlexcount">Count members in lex range</Card>
-<Card title="ZMPOP" href="/redis/commands/sorted-set/zmpop">Pop members from sorted sets</Card>
+<Card title="ZMPOP" href="/redis/commands/sorted-set/zmpop">Pop from the first non-empty sorted set</Card>
 <Card title="ZMSCORE" href="/redis/commands/sorted-set/zmscore">Get scores of multiple members</Card>
 <Card title="ZPOPMAX" href="/redis/commands/sorted-set/zpopmax">Pop members with highest scores</Card>
 <Card title="ZPOPMIN" href="/redis/commands/sorted-set/zpopmin">Pop members with lowest scores</Card>
 <Card title="ZRANDMEMBER" href="/redis/commands/sorted-set/zrandmember">Get random members</Card>
-<Card title="ZRANGE" href="/redis/commands/sorted-set/zrange">Get members by index range</Card>
+<Card title="ZRANGE" href="/redis/commands/sorted-set/zrange">Get members by index, score, or lex range</Card>
 <Card title="ZRANGEBYLEX" href="/redis/commands/sorted-set/zrangebylex">Get members by lex range</Card>
 <Card title="ZRANGEBYSCORE" href="/redis/commands/sorted-set/zrangebyscore">Get members by score range</Card>
-<Card title="ZRANGESTORE" href="/redis/commands/sorted-set/zrangestore">Store range result</Card>
+<Card title="ZRANGESTORE" href="/redis/commands/sorted-set/zrangestore">Store the result of a range query</Card>
 <Card title="ZRANK" href="/redis/commands/sorted-set/zrank">Get member's rank</Card>
 <Card title="ZREM" href="/redis/commands/sorted-set/zrem">Remove members</Card>
 <Card title="ZREMRANGEBYLEX" href="/redis/commands/sorted-set/zremrangebylex">Remove members by lex range</Card>
@@ -49215,7 +49839,11 @@ Source: https://upstash.com/docs/redis/commands/sorted-set/overview
 # ZADD
 Source: https://upstash.com/docs/redis/commands/sorted-set/zadd
 
-Use `ZADD` to add members with scores.
+Use `ZADD` to add members with a score to a sorted set, or to change the score of members that are already there.
+
+Members are kept ordered by score, and members with equal scores are ordered lexicographically, which is what makes range queries by score or by member name possible. Scores are double precision floats and accept `+inf` and `-inf`. The key is created on first use, and the reply counts the members that were added.
+
+`NX` only adds new members and never changes an existing score, while `XX` only updates members that already exist. `GT` and `LT` update a score only when the new one is greater or less than the current one, which is how you keep a running maximum or minimum, such as a high score or an earliest deadline, without reading the old value first. `CH` makes the reply count every member that changed, added or updated, instead of only the new ones. `INCR` treats the given score as an increment and returns the member's new score, behaving like [`ZINCRBY`](/docs/redis/commands/sorted-set/zincrby) for a single member and returning null when a condition prevented the change.
 
 ## Syntax
 
@@ -49392,7 +50020,9 @@ fn main() -> redis::RedisResult<()> {
 # ZCARD
 Source: https://upstash.com/docs/redis/commands/sorted-set/zcard
 
-Use `ZCARD` to get sorted set cardinality.
+Use `ZCARD` to get the number of members in a sorted set.
+
+The reply is `0` when the key does not exist. The size is maintained by Redis, so the command is cheap whatever the size of the set. Use [`ZCOUNT`](/docs/redis/commands/sorted-set/zcount) when you need the number of members within a score range rather than the total.
 
 ## Syntax
 
@@ -49560,7 +50190,11 @@ fn main() -> redis::RedisResult<()> {
 # ZCOUNT
 Source: https://upstash.com/docs/redis/commands/sorted-set/zcount
 
-Use `ZCOUNT` to count members in score range.
+Use `ZCOUNT` to count the members of a sorted set whose score falls in a range.
+
+Both bounds are inclusive by default; prefix a bound with `(` to make it exclusive, and use `-inf` and `+inf` for open ends, so `ZCOUNT key (5 +inf` counts everything scored above 5. Redis finds the range by rank rather than scanning the whole set, so the count is fast even on large sets.
+
+With timestamps as scores this is how you count events in a time window without transferring them.
 
 ## Syntax
 
@@ -49730,7 +50364,11 @@ fn main() -> redis::RedisResult<()> {
 # ZDIFF
 Source: https://upstash.com/docs/redis/commands/sorted-set/zdiff
 
-Use `ZDIFF` to get sorted set difference.
+Use `ZDIFF` to get the members of the first sorted set that do not appear in any of the others.
+
+`<numkeys>` states how many keys follow. Scores come from the first set and are returned only when `WITHSCORES` is given, and the result keeps the ordering of that set. Keys that do not exist count as empty.
+
+The result is computed on each call and not stored; use [`ZDIFFSTORE`](/docs/redis/commands/sorted-set/zdiffstore) to keep it. This is how you exclude one group from a ranking, for example dropping already-seen items from a scored feed.
 
 ## Syntax
 
@@ -49898,7 +50536,11 @@ fn main() -> redis::RedisResult<()> {
 # ZDIFFSTORE
 Source: https://upstash.com/docs/redis/commands/sorted-set/zdiffstore
 
-Use `ZDIFFSTORE` to store sorted set difference.
+Use `ZDIFFSTORE` to compute the difference between sorted sets and store it in another key.
+
+The destination receives the members of the first source that appear in none of the others, keeping their scores from that source. It is overwritten if it exists and deleted when the result is empty, and the reply is the number of members stored.
+
+Materializing the result is worthwhile when the same filtered ranking is read repeatedly or paged through, since the destination is an ordinary sorted set.
 
 ## Syntax
 
@@ -50069,7 +50711,11 @@ fn main() -> redis::RedisResult<()> {
 # ZINCRBY
 Source: https://upstash.com/docs/redis/commands/sorted-set/zincrby
 
-Use `ZINCRBY` to increment member's score.
+Use `ZINCRBY` to add an increment to the score of a member of a sorted set.
+
+A member that is not there yet is created with the increment as its score, and a missing key is created too, so no initialization step is needed. The increment may be negative to move a member down. The reply is the new score.
+
+Because the update is atomic and the set stays ordered, this is the core operation behind leaderboards, vote counts, and any ranking that has to reflect concurrent updates: increment a member's score and read the position back with [`ZRANK`](/docs/redis/commands/sorted-set/zrank) or the top of the ranking with [`ZRANGE`](/docs/redis/commands/sorted-set/zrange).
 
 ## Syntax
 
@@ -50240,7 +50886,11 @@ fn main() -> redis::RedisResult<()> {
 # ZINTER
 Source: https://upstash.com/docs/redis/commands/sorted-set/zinter
 
-Use `ZINTER` to get sorted set intersection.
+Use `ZINTER` to get the members that appear in every one of the given sorted sets.
+
+`<numkeys>` states how many keys follow. By default the score of each member in the result is the sum of its scores across all the inputs, which is what makes intersections useful for combining rankings. `WEIGHTS` multiplies each input's scores by a factor before they are combined, so one source can count more than another, and `AGGREGATE` replaces the sum with `MIN` or `MAX`. `WITHSCORES` returns the computed scores along with the members.
+
+The result is not stored; use [`ZINTERSTORE`](/docs/redis/commands/sorted-set/zinterstore) to keep it or [`ZINTERCARD`](/docs/redis/commands/sorted-set/zintercard) when only the size matters.
 
 ## Syntax
 
@@ -50410,7 +51060,9 @@ fn main() -> redis::RedisResult<()> {
 # ZINTERCARD
 Source: https://upstash.com/docs/redis/commands/sorted-set/zintercard
 
-Use `ZINTERCARD` to get intersection cardinality.
+Use `ZINTERCARD` to get the number of members that the given sorted sets have in common, without building the intersection.
+
+`<numkeys>` states how many keys follow. `LIMIT` stops the count once that many common members are found and returns the limit, which answers "do these sets overlap by at least N" far more cheaply than a full intersection; `LIMIT 0` means no limit. Only the count is computed and returned, so nothing is stored and no scores are transferred.
 
 ## Syntax
 
@@ -50568,7 +51220,11 @@ fn main() -> redis::RedisResult<()> {
 # ZINTERSTORE
 Source: https://upstash.com/docs/redis/commands/sorted-set/zinterstore
 
-Use `ZINTERSTORE` to store sorted set intersection.
+Use `ZINTERSTORE` to compute the intersection of sorted sets and store it in another key.
+
+The destination gets the members present in every input, scored by the sum of their scores by default, or by `MIN` or `MAX` when `AGGREGATE` is given, with `WEIGHTS` scaling each input beforehand. The destination is overwritten if it exists and deleted when the intersection is empty, and the reply is the number of members stored.
+
+This is how a combined ranking is built once, for instance blending a relevance score with a popularity score, and then paged through with [`ZRANGE`](/docs/redis/commands/sorted-set/zrange).
 
 ## Syntax
 
@@ -50750,7 +51406,11 @@ fn main() -> redis::RedisResult<()> {
 # ZLEXCOUNT
 Source: https://upstash.com/docs/redis/commands/sorted-set/zlexcount
 
-Use `ZLEXCOUNT` to count members in lex range.
+Use `ZLEXCOUNT` to count the members of a sorted set that fall in a lexicographic range.
+
+Bounds are written as `[member` for inclusive and `(member` for exclusive, with `-` and `+` standing for the lowest and highest possible members, so `ZLEXCOUNT key [a (c` counts members from `a` up to but not including `c`.
+
+Lexicographic ordering only holds when every member of the set has the same score, which is the trick behind using a sorted set as a sorted index of strings; with mixed scores the result is not meaningful. Use [`ZRANGEBYLEX`](/docs/redis/commands/sorted-set/zrangebylex) or [`ZRANGE`](/docs/redis/commands/sorted-set/zrange) with `BYLEX` to retrieve the members themselves.
 
 ## Syntax
 
@@ -50920,7 +51580,11 @@ fn main() -> redis::RedisResult<()> {
 # ZMPOP
 Source: https://upstash.com/docs/redis/commands/sorted-set/zmpop
 
-Use `ZMPOP` to pop members from sorted sets.
+Use `ZMPOP` to pop members from the first of several sorted sets that is not empty.
+
+`<numkeys>` states how many keys follow, `MIN` or `MAX` chooses whether the lowest or the highest scoring members are taken, and `COUNT` sets how many to pop. Keys are examined in the order given and only the first non-empty one is touched, so listing a high priority queue first drains it before the others are considered.
+
+The reply names the key that was popped from along with the members and their scores, which matters when a worker watches several queues. When every key is empty the reply is null; use [`BZMPOP`](/docs/redis/commands/sorted-set/bzmpop) to wait instead of returning.
 
 ## Syntax
 
@@ -50934,7 +51598,7 @@ ZMPOP <numkeys> <key> [<key> ...] (MIN | MAX) [COUNT <count>]
 | --- | --- | --- | --- |
 | `<numkeys>` | Yes | No | Number of key arguments that follow. |
 | `<key>` | Yes | Yes | Redis key targeted by the command. |
-| `(MIN \| MAX)` | Yes | No | Choose one form: `MIN`; `MAX`. |
+| `(MIN \| MAX)` | Yes | No | Which members to pop: `MIN` (lowest scores first) or `MAX` (highest scores first). |
 | `COUNT <count>` | No | No | Maximum number of members to pop. |
 
 ## Important points
@@ -51084,7 +51748,9 @@ fn main() -> redis::RedisResult<()> {
 # ZMSCORE
 Source: https://upstash.com/docs/redis/commands/sorted-set/zmscore
 
-Use `ZMSCORE` to get scores of multiple members.
+Use `ZMSCORE` to get the scores of several members of a sorted set in one call.
+
+The reply holds one score per member, in the order requested, with null for members that are not in the set, so it lines up with your input list. A missing key yields all nulls rather than an error. It replaces a series of [`ZSCORE`](/docs/redis/commands/sorted-set/zscore) round trips when you need to read a batch of scores, such as the current rating of every item on a page.
 
 ## Syntax
 
@@ -51260,7 +51926,11 @@ fn main() -> redis::RedisResult<()> {
 # ZPOPMAX
 Source: https://upstash.com/docs/redis/commands/sorted-set/zpopmax
 
-Use `ZPOPMAX` to pop members with highest scores.
+Use `ZPOPMAX` to remove and return the members with the highest scores in a sorted set.
+
+Without a count one member is returned with its score, and with a count up to that many are removed, ordered from the highest score down. A missing or empty key returns an empty result, and the key is deleted once the last member is popped.
+
+Since the read and the removal are atomic, no two workers can take the same member, which turns a sorted set into a priority queue where the score is the priority. [`BZPOPMAX`](/docs/redis/commands/sorted-set/bzpopmax) is the blocking form.
 
 ## Syntax
 
@@ -51428,7 +52098,11 @@ fn main() -> redis::RedisResult<()> {
 # ZPOPMIN
 Source: https://upstash.com/docs/redis/commands/sorted-set/zpopmin
 
-Use `ZPOPMIN` to pop members with lowest scores.
+Use `ZPOPMIN` to remove and return the members with the lowest scores in a sorted set.
+
+Without a count one member is returned with its score, and with a count up to that many are removed, ordered from the lowest score up. The key is deleted once the last member is popped.
+
+With a timestamp or a priority number as the score, this is how a sorted set becomes a scheduler or a priority queue: the next item due is always the minimum, and popping it atomically means only one worker can pick it up. [`BZPOPMIN`](/docs/redis/commands/sorted-set/bzpopmin) is the blocking form.
 
 ## Syntax
 
@@ -51596,7 +52270,11 @@ fn main() -> redis::RedisResult<()> {
 # ZRANDMEMBER
 Source: https://upstash.com/docs/redis/commands/sorted-set/zrandmember
 
-Use `ZRANDMEMBER` to get random members.
+Use `ZRANDMEMBER` to get random members of a sorted set without removing them.
+
+Without a count one member is returned, or null when the key does not exist. A positive count returns up to that many distinct members, capped at the size of the set, while a negative count returns exactly that many members chosen independently, so repeats are possible. `WITHSCORES` returns each member together with its score.
+
+Use it for sampling and random selection, and [`ZPOPMIN`](/docs/redis/commands/sorted-set/zpopmin) or [`ZPOPMAX`](/docs/redis/commands/sorted-set/zpopmax) when members should be consumed.
 
 ## Syntax
 
@@ -51760,7 +52438,13 @@ fn main() -> redis::RedisResult<()> {
 # ZRANGE
 Source: https://upstash.com/docs/redis/commands/sorted-set/zrange
 
-Use `ZRANGE` to get members by index range.
+Use `ZRANGE` to read a range of members from a sorted set.
+
+By default `<start>` and `<stop>` are zero-based indexes into the ordering, inclusive, and may be negative to count from the end, so `0 -1` returns everything and `0 9` the ten lowest scoring members.
+
+The option that follows changes what those two arguments mean. `BYSCORE` reads them as score bounds, inclusive unless prefixed with `(` and accepting `-inf` and `+inf`. `BYLEX` reads them as member bounds written `[member`, `(member`, `-`, or `+`, which is only meaningful when all members share the same score. `REV` reverses the order, and with `BYSCORE` or `BYLEX` it also means the bounds are given from the higher one to the lower one. `LIMIT <offset> <count>` pages through the result and requires `BYSCORE` or `BYLEX`. `WITHSCORES` includes each member's score.
+
+`ZRANGE` covers everything `ZRANGEBYSCORE`, `ZRANGEBYLEX`, `ZREVRANGE`, and their variants do, and it is the command Redis recommends for new code. Use [`ZRANGESTORE`](/docs/redis/commands/sorted-set/zrangestore) to store the result instead of returning it.
 
 ## Syntax
 
@@ -51775,7 +52459,7 @@ ZRANGE <key> <start> <stop> [BYSCORE | BYLEX] [REV] [LIMIT <offset> <count>] [WI
 | `<key>` | Yes | No | Redis key targeted by the command. |
 | `<start>` | Yes | No | Lower bound. Interpreted as a rank by default, as a score with `BYSCORE`, or lexicographically with `BYLEX`. |
 | `<stop>` | Yes | No | Upper bound. Interpreted as a rank by default, as a score with `BYSCORE`, or lexicographically with `BYLEX`. |
-| `(BYSCORE \| BYLEX)` | No | No | Choose one form: `BYSCORE`; `BYLEX`. |
+| `(BYSCORE \| BYLEX)` | No | No | How the two range arguments are read: `BYSCORE` as score bounds (inclusive, or exclusive with a `(` prefix, and `-inf`/`+inf` allowed), `BYLEX` as member bounds (`[member`, `(member`, `-`, or `+`), which only makes sense when every member has the same score. They are zero-based indexes when neither is given. |
 | `REV` | No | No | Reverse the result order. |
 | `LIMIT <offset> <count>` | No | No | Skip `<offset>` matches and return at most `<count>`; a `<count>` of `-1` returns all remaining. |
 | `WITHSCORES` | No | No | Include sorted-set scores. |
@@ -51939,7 +52623,13 @@ fn main() -> redis::RedisResult<()> {
 # ZRANGEBYLEX
 Source: https://upstash.com/docs/redis/commands/sorted-set/zrangebylex
 
-Use `ZRANGEBYLEX` to get members by lex range.
+Use `ZRANGEBYLEX` to list the members of a sorted set that fall in a lexicographic range.
+
+Bounds are written `[member` for inclusive and `(member` for exclusive, with `-` and `+` standing for the lowest and highest possible members. `LIMIT <offset> <count>` pages through the result.
+
+The ordering used here is the byte order of member names, which is only meaningful when every member has the same score. Giving all members score `0` turns a sorted set into a sorted string index, which is how prefix lookups and autocomplete are built on top of it.
+
+The command is deprecated in Redis in favor of [`ZRANGE`](/docs/redis/commands/sorted-set/zrange) with `BYLEX`, which accepts the same bounds.
 
 ## Syntax
 
@@ -52101,7 +52791,11 @@ fn main() -> redis::RedisResult<()> {
 # ZRANGEBYSCORE
 Source: https://upstash.com/docs/redis/commands/sorted-set/zrangebyscore
 
-Use `ZRANGEBYSCORE` to get members by score range.
+Use `ZRANGEBYSCORE` to list the members of a sorted set whose score falls in a range, from the lowest score up.
+
+Bounds are inclusive by default, become exclusive when prefixed with `(`, and accept `-inf` and `+inf` for open ends. `WITHSCORES` returns each member with its score, and `LIMIT <offset> <count>` pages through the result, which is how you take the first N above a threshold without transferring the rest.
+
+With timestamps as scores this is the natural range query over time. The command is deprecated in Redis in favor of [`ZRANGE`](/docs/redis/commands/sorted-set/zrange) with `BYSCORE`.
 
 ## Syntax
 
@@ -52268,7 +52962,11 @@ fn main() -> redis::RedisResult<()> {
 # ZRANGESTORE
 Source: https://upstash.com/docs/redis/commands/sorted-set/zrangestore
 
-Use `ZRANGESTORE` to store range result.
+Use `ZRANGESTORE` to run the same selection as [`ZRANGE`](/docs/redis/commands/sorted-set/zrange) and store the result in another sorted set instead of returning it.
+
+The selection works exactly as it does for `ZRANGE`: by index, or by score with `BYSCORE`, or by member with `BYLEX`, with `REV` and `LIMIT` available in the same way. The members keep their original scores in the destination, which is overwritten if it exists and deleted when the range is empty. The reply is the number of members stored.
+
+This is how a slice of a large ranking is materialized once, for instance the top thousand of a leaderboard, so that further intersections or repeated paging run against a small key.
 
 ## Syntax
 
@@ -52284,7 +52982,7 @@ ZRANGESTORE <dst> <src> <min> <max> [BYSCORE | BYLEX] [REV] [LIMIT <offset> <cou
 | `<src>` | Yes | No | Redis key used as src. |
 | `<min>` | Yes | No | Lower bound. Interpreted as a rank by default, as a score with `BYSCORE`, or lexicographically with `BYLEX`. |
 | `<max>` | Yes | No | Upper bound. Interpreted as a rank by default, as a score with `BYSCORE`, or lexicographically with `BYLEX`. |
-| `(BYSCORE \| BYLEX)` | No | No | Choose one form: `BYSCORE`; `BYLEX`. |
+| `(BYSCORE \| BYLEX)` | No | No | How the two range arguments are read: `BYSCORE` as score bounds (inclusive, or exclusive with a `(` prefix, and `-inf`/`+inf` allowed), `BYLEX` as member bounds (`[member`, `(member`, `-`, or `+`), which only makes sense when every member has the same score. They are zero-based indexes when neither is given. |
 | `REV` | No | No | Reverse the result order. |
 | `LIMIT <offset> <count>` | No | No | Skip `<offset>` matches and return at most `<count>`; a `<count>` of `-1` returns all remaining. |
 
@@ -52436,7 +53134,11 @@ fn main() -> redis::RedisResult<()> {
 # ZRANK
 Source: https://upstash.com/docs/redis/commands/sorted-set/zrank
 
-Use `ZRANK` to get member's rank.
+Use `ZRANK` to get the position of a member in a sorted set, counting from the lowest score.
+
+The rank is zero-based, so the lowest scoring member has rank `0`, and members with equal scores are ordered lexicographically. `WITHSCORE` returns the score alongside the rank. The reply is null when the member or the key does not exist.
+
+This is how a leaderboard reports "you are number N": increment scores with [`ZINCRBY`](/docs/redis/commands/sorted-set/zincrby) and read the position back here, using [`ZREVRANK`](/docs/redis/commands/sorted-set/zrevrank) when rank `0` should be the highest score instead.
 
 ## Syntax
 
@@ -52605,7 +53307,9 @@ fn main() -> redis::RedisResult<()> {
 # ZREM
 Source: https://upstash.com/docs/redis/commands/sorted-set/zrem
 
-Use `ZREM` to remove members.
+Use `ZREM` to remove one or more members from a sorted set.
+
+The reply counts only the members that were actually present, so removing something already gone is not an error. The key is deleted when its last member is removed. To remove members by score, rank, or member range instead of by name, use [`ZREMRANGEBYSCORE`](/docs/redis/commands/sorted-set/zremrangebyscore), [`ZREMRANGEBYRANK`](/docs/redis/commands/sorted-set/zremrangebyrank), or [`ZREMRANGEBYLEX`](/docs/redis/commands/sorted-set/zremrangebylex).
 
 ## Syntax
 
@@ -52769,7 +53473,11 @@ fn main() -> redis::RedisResult<()> {
 # ZREMRANGEBYLEX
 Source: https://upstash.com/docs/redis/commands/sorted-set/zremrangebylex
 
-Use `ZREMRANGEBYLEX` to remove members by lex range.
+Use `ZREMRANGEBYLEX` to remove the members of a sorted set that fall in a lexicographic range.
+
+Bounds are written `[member` for inclusive and `(member` for exclusive, with `-` and `+` for the extremes. As with every lexicographic operation, the result is only meaningful when all members share the same score. The reply is the number of members removed, and the key is deleted when it becomes empty.
+
+It is the bulk delete that matches [`ZRANGEBYLEX`](/docs/redis/commands/sorted-set/zrangebylex), useful for dropping a whole prefix from a sorted string index.
 
 ## Syntax
 
@@ -52934,7 +53642,11 @@ fn main() -> redis::RedisResult<()> {
 # ZREMRANGEBYRANK
 Source: https://upstash.com/docs/redis/commands/sorted-set/zremrangebyrank
 
-Use `ZREMRANGEBYRANK` to remove members by rank range.
+Use `ZREMRANGEBYRANK` to remove the members of a sorted set that occupy a range of positions.
+
+Ranks are zero-based from the lowest score and may be negative to count from the top, so `ZREMRANGEBYRANK key 0 -101` keeps only the hundred highest scoring members. The reply is the number of members removed, and the key is deleted when it becomes empty.
+
+This is the standard way to cap a leaderboard or any ranking to a fixed size after inserting into it, in the same spirit as [`LTRIM`](/docs/redis/commands/list/ltrim) for lists.
 
 ## Syntax
 
@@ -53099,7 +53811,11 @@ fn main() -> redis::RedisResult<()> {
 # ZREMRANGEBYSCORE
 Source: https://upstash.com/docs/redis/commands/sorted-set/zremrangebyscore
 
-Use `ZREMRANGEBYSCORE` to remove members by score range.
+Use `ZREMRANGEBYSCORE` to remove the members of a sorted set whose score falls in a range.
+
+Bounds are inclusive by default, become exclusive when prefixed with `(`, and accept `-inf` and `+inf`. The reply is the number of members removed, and the key is deleted when it becomes empty.
+
+With timestamps as scores this is how a sliding window is maintained: drop everything older than the cutoff in one call, which is exactly what a sorted-set rate limiter does before counting what is left.
 
 ## Syntax
 
@@ -53264,7 +53980,11 @@ fn main() -> redis::RedisResult<()> {
 # ZREVRANGE
 Source: https://upstash.com/docs/redis/commands/sorted-set/zrevrange
 
-Use `ZREVRANGE` to get members in reverse order.
+Use `ZREVRANGE` to list a range of members of a sorted set ordered from the highest score down.
+
+`<start>` and `<stop>` are zero-based, inclusive positions in that reversed ordering, so `0 9` returns the ten highest scoring members, the usual shape of a leaderboard page. Negative indexes count from the end, and `WITHSCORES` includes each member's score.
+
+The command is deprecated in Redis in favor of [`ZRANGE`](/docs/redis/commands/sorted-set/zrange) with `REV`.
 
 ## Syntax
 
@@ -53432,6 +54152,10 @@ Source: https://upstash.com/docs/redis/commands/sorted-set/zrevrangebylex
 
 Use `ZREVRANGEBYLEX` to list the members in a lexicographic range, in reverse order.
 
+The bounds are given highest first, `<max>` before `<min>`, written `[member` for inclusive and `(member` for exclusive, with `+` and `-` for the extremes. `LIMIT <offset> <count>` pages through the result.
+
+As with every lexicographic operation, the ordering is only meaningful when all members share the same score. The command is deprecated in Redis in favor of [`ZRANGE`](/docs/redis/commands/sorted-set/zrange) with `BYLEX` and `REV`.
+
 ## Syntax
 
 ```redis
@@ -53594,6 +54318,10 @@ Source: https://upstash.com/docs/redis/commands/sorted-set/zrevrangebyscore
 
 Use `ZREVRANGEBYSCORE` to list the members in a score range, ordered from the highest score down.
 
+The bounds are given highest first, `<max>` before `<min>`. They are inclusive by default, become exclusive when prefixed with `(`, and accept `+inf` and `-inf`. `WITHSCORES` returns the scores and `LIMIT <offset> <count>` pages through the result, which is the usual way to fetch "the top N above a threshold".
+
+The command is deprecated in Redis in favor of [`ZRANGE`](/docs/redis/commands/sorted-set/zrange) with `BYSCORE` and `REV`.
+
 ## Syntax
 
 ```redis
@@ -53759,7 +54487,9 @@ fn main() -> redis::RedisResult<()> {
 # ZREVRANK
 Source: https://upstash.com/docs/redis/commands/sorted-set/zrevrank
 
-Use `ZREVRANK` to get member's reverse rank.
+Use `ZREVRANK` to get the position of a member in a sorted set, counting from the highest score.
+
+The rank is zero-based, so the top scoring member has rank `0`, which is the number a leaderboard usually wants to display. `WITHSCORE` returns the score alongside the rank, and the reply is null when the member or the key does not exist. Use [`ZRANK`](/docs/redis/commands/sorted-set/zrank) to count from the lowest score instead.
 
 ## Syntax
 
@@ -53928,7 +54658,11 @@ fn main() -> redis::RedisResult<()> {
 # ZSCAN
 Source: https://upstash.com/docs/redis/commands/sorted-set/zscan
 
-Use `ZSCAN` to incrementally iterate sorted set.
+Use `ZSCAN` to iterate the members of a sorted set in batches instead of reading them all at once.
+
+Each call takes a cursor and returns the next cursor together with a batch of members and their scores. Start at cursor `0` and keep calling with the cursor from the previous reply until the server returns `0`. `MATCH` filters member names with a glob-style pattern and `COUNT` hints at how much work each call should do.
+
+Filtering happens after a batch is read, so a call can come back empty while the cursor is still non-zero. Members present for the whole iteration are returned at least once, and members added or removed while it runs may or may not appear. When you want members in score order rather than in scan order, use [`ZRANGE`](/docs/redis/commands/sorted-set/zrange).
 
 ## Syntax
 
@@ -54110,7 +54844,9 @@ fn main() -> redis::RedisResult<()> {
 # ZSCORE
 Source: https://upstash.com/docs/redis/commands/sorted-set/zscore
 
-Use `ZSCORE` to get member's score.
+Use `ZSCORE` to get the score of a member of a sorted set.
+
+The reply is null when the member or the key does not exist, so it doubles as a membership test that also tells you the value. Use [`ZMSCORE`](/docs/redis/commands/sorted-set/zmscore) to read several scores in one call, and [`ZRANK`](/docs/redis/commands/sorted-set/zrank) when you want the member's position rather than its score.
 
 ## Syntax
 
@@ -54286,7 +55022,11 @@ fn main() -> redis::RedisResult<()> {
 # ZUNION
 Source: https://upstash.com/docs/redis/commands/sorted-set/zunion
 
-Use `ZUNION` to get sorted set union.
+Use `ZUNION` to get every member that appears in at least one of the given sorted sets.
+
+`<numkeys>` states how many keys follow. A member present in several inputs gets the sum of its scores by default, which is how scores from different sources are combined; `WEIGHTS` scales each input before that, and `AGGREGATE` replaces the sum with `MIN` or `MAX`. `WITHSCORES` returns the computed scores.
+
+The result is computed on each call and not stored; use [`ZUNIONSTORE`](/docs/redis/commands/sorted-set/zunionstore) to keep it.
 
 ## Syntax
 
@@ -54459,7 +55199,11 @@ fn main() -> redis::RedisResult<()> {
 # ZUNIONSTORE
 Source: https://upstash.com/docs/redis/commands/sorted-set/zunionstore
 
-Use `ZUNIONSTORE` to store sorted set union.
+Use `ZUNIONSTORE` to compute the union of sorted sets and store it in another key.
+
+Members present in several inputs are scored by the sum of their scores by default, or by `MIN` or `MAX` when `AGGREGATE` is given, with `WEIGHTS` scaling each input first. The destination is overwritten if it exists and deleted when the union is empty, and the reply is the number of members stored.
+
+Merging per-day or per-source rankings into a combined one, weighting them as you go, is the typical use: the destination is an ordinary sorted set that can then be paged with [`ZRANGE`](/docs/redis/commands/sorted-set/zrange).
 
 ## Syntax
 
@@ -54648,7 +55392,7 @@ Source: https://upstash.com/docs/redis/commands/streams/overview
 <Card title="XAUTOCLAIM" href="/redis/commands/streams/xautoclaim">Auto-claim idle messages</Card>
 <Card title="XCLAIM" href="/redis/commands/streams/xclaim">Claim pending messages</Card>
 <Card title="XDEL" href="/redis/commands/streams/xdel">Delete stream entries</Card>
-<Card title="XDELEX" href="/redis/commands/streams/xdelex">Delete entries with expiration</Card>
+<Card title="XDELEX" href="/redis/commands/streams/xdelex">Delete entries with reference control</Card>
 <Card title="XGROUP" href="/redis/commands/streams/xgroup">Manage consumer groups</Card>
 <Card title="XINFO CONSUMERS" href="/redis/commands/streams/xinfo-consumers">List group consumers</Card>
 <Card title="XINFO GROUPS" href="/redis/commands/streams/xinfo-groups">List stream groups</Card>
@@ -54665,7 +55409,11 @@ Source: https://upstash.com/docs/redis/commands/streams/overview
 # XACK
 Source: https://upstash.com/docs/redis/commands/streams/xack
 
-Use `XACK` to acknowledge stream messages.
+Use `XACK` to tell a consumer group that entries have been processed.
+
+Acknowledged entries leave the group's pending entries list, so they are no longer counted as in flight and can no longer be claimed by another consumer. The reply counts the IDs that were actually pending, which means acknowledging twice is harmless and returns `0` the second time.
+
+Acknowledging does not delete the entry from the stream: other groups still see it, and it stays until trimmed. Use [`XACKDEL`](/docs/redis/commands/streams/xackdel) when the entry should also be removed.
 
 ## Syntax
 
@@ -54830,7 +55578,11 @@ fn main() -> redis::RedisResult<()> {
 # XACKDEL
 Source: https://upstash.com/docs/redis/commands/streams/xackdel
 
-Use `XACKDEL` to acknowledge and delete messages.
+Use `XACKDEL` to acknowledge entries in a consumer group and delete them from the stream in one atomic step.
+
+It combines what [`XACK`](/docs/redis/commands/streams/xack) and [`XDEL`](/docs/redis/commands/streams/xdel) do, which is what you want when a stream serves a single group and processed entries have no reason to stay around. `IDS <numids>` introduces the list of IDs and the count must match.
+
+The reference policy controls what happens to consumer group references of the deleted entries: `KEEPREF`, the default, leaves references in other groups' pending lists in place, `DELREF` removes them everywhere, and `ACKED` only deletes entries that every group has read and acknowledged, leaving the rest in the stream. The reply holds one status code per requested ID, in order.
 
 ## Syntax
 
@@ -54844,7 +55596,7 @@ XACKDEL <key> <group> [KEEPREF | DELREF | ACKED] IDS <numids> <id> [<id> ...]
 | --- | --- | --- | --- |
 | `<key>` | Yes | No | Redis key targeted by the command. |
 | `<group>` | Yes | No | Consumer group name. |
-| `(KEEPREF \| DELREF \| ACKED)` | No | No | Choose one form: `KEEPREF`; `DELREF`; `ACKED`. |
+| `(KEEPREF \| DELREF \| ACKED)` | No | No | What happens to consumer-group references of the deleted entries: `KEEPREF` (the default) leaves them in place, `DELREF` removes them from every group's pending list, and `ACKED` only removes entries that every group has read and acknowledged. |
 | `IDS <numids> <id> [<id> ...]` | Yes | No | Entry IDs to target. Give the ID count first, then that many IDs. |
 
 ## Response
@@ -54998,7 +55750,13 @@ fn main() -> redis::RedisResult<()> {
 # XADD
 Source: https://upstash.com/docs/redis/commands/streams/xadd
 
-Use `XADD` to add entry to stream.
+Use `XADD` to append an entry to a stream, creating the stream when it does not exist.
+
+An entry is a set of field and value pairs identified by an ID of the form `<milliseconds>-<sequence>`. Passing `*` lets the server build the ID from the current time, which guarantees that IDs only ever increase; an explicit ID must be greater than the last one in the stream. The reply is the ID the entry was stored under. `NOMKSTREAM` skips creating a stream that does not exist yet and returns null instead.
+
+The trimming options cap the stream in the same call, which is how a stream is kept from growing without bound. `MAXLEN` limits the number of entries and `MINID` drops entries with an ID below a threshold, which is the way to trim by age since IDs start with a timestamp. `~` makes the trim approximate, stopping at a convenient boundary, which is much cheaper than the exact `=` and is what most workloads should use; `LIMIT` caps how many entries a single call may evict.
+
+`KEEPREF`, `DELREF`, and `ACKED` decide what happens to consumer group references of the entries that trimming removes: `KEEPREF`, the default, leaves those references in place, `DELREF` removes them as well, and `ACKED` only removes entries that every group has read and acknowledged.
 
 ## Syntax
 
@@ -55012,9 +55770,9 @@ XADD <key> [NOMKSTREAM] [KEEPREF | DELREF | ACKED] [(MAXLEN | MINID) [= | ~] <th
 | --- | --- | --- | --- |
 | `<key>` | Yes | No | Redis key targeted by the command. |
 | `NOMKSTREAM` | No | No | Do not create a missing stream. |
-| `(KEEPREF \| DELREF \| ACKED)` | No | No | Choose one form: `KEEPREF`; `DELREF`; `ACKED`. |
+| `(KEEPREF \| DELREF \| ACKED)` | No | No | What happens to consumer-group references of the entries that trimming removes: `KEEPREF` (the default) leaves them in place, `DELREF` removes them from every group's pending list, and `ACKED` only removes entries that every group has read and acknowledged. |
 | `(MAXLEN \| MINID) [= \| ~] <threshold> [LIMIT <count>]` | No | No | Trim the stream after the entry is added. `MAXLEN` caps the number of entries; `MINID` drops entries with a lower ID. `=` trims exactly and is the default; `~` trims approximately and is required before `LIMIT`, which caps how many entries a single call evicts. |
-| `(* \| <id>)` | Yes | No | Choose one form: `*`. |
+| `(* \| <id>)` | Yes | No | Entry ID: `*` lets the server generate one from the current time, or give an explicit `<milliseconds>-<sequence>` ID, which must be greater than the stream's last one. |
 | `<field> <value>` | Yes | Yes | Field and the value to store in it. Repeat to set several fields in one call. |
 
 ## Response
@@ -55166,7 +55924,11 @@ fn main() -> redis::RedisResult<()> {
 # XAUTOCLAIM
 Source: https://upstash.com/docs/redis/commands/streams/xautoclaim
 
-Use `XAUTOCLAIM` to auto-claim idle messages.
+Use `XAUTOCLAIM` to transfer ownership of pending entries that have been idle for too long, without having to name their IDs.
+
+Starting from `<start>`, it walks the group's pending entries list and claims for `<consumer>` every entry that has been idle at least `<min-idle-time>` milliseconds, up to `COUNT` of them. The reply has three parts: a cursor to pass as `<start>` on the next call, the claimed entries themselves (or only their IDs with `JUSTID`), and the IDs that were dropped from the pending list because they no longer exist in the stream.
+
+This is the recommended way to recover work from a consumer that crashed or stalled: it replaces the older loop of [`XPENDING`](/docs/redis/commands/streams/xpending) to find idle entries followed by [`XCLAIM`](/docs/redis/commands/streams/xclaim) to take them, and it can be run repeatedly by a janitor task, since the idle threshold keeps healthy consumers' work untouched.
 
 ## Syntax
 
@@ -55346,7 +56108,13 @@ fn main() -> redis::RedisResult<()> {
 # XCLAIM
 Source: https://upstash.com/docs/redis/commands/streams/xclaim
 
-Use `XCLAIM` to claim pending messages.
+Use `XCLAIM` to change the owner of specific pending entries in a consumer group.
+
+The entries must have been idle for at least `<min-idle-time>` milliseconds, which is what keeps two recovery attempts from stealing the same work from each other: the first claim resets the idle time and the second one then finds nothing to take. Claiming resets the entry's delivery time and increments its delivery counter, unless `JUSTID` is used, which returns only the IDs and leaves the counter alone.
+
+`IDLE` and `TIME` set the new idle time or the last delivery time explicitly, `RETRYCOUNT` overrides the delivery counter, and `FORCE` creates a pending entry for IDs that exist in the stream but are not currently pending. Entries that no longer exist in the stream are removed from the pending list instead of being claimed.
+
+When you want to claim whatever is idle rather than specific IDs, use [`XAUTOCLAIM`](/docs/redis/commands/streams/xautoclaim).
 
 ## Syntax
 
@@ -55526,7 +56294,11 @@ fn main() -> redis::RedisResult<()> {
 # XDEL
 Source: https://upstash.com/docs/redis/commands/streams/xdel
 
-Use `XDEL` to delete stream entries.
+Use `XDEL` to remove entries from a stream by ID.
+
+The reply counts the entries that were actually removed. Deleting an entry does not touch consumer group state: an entry already delivered stays in a group's pending entries list until it is acknowledged, so it can still show up in [`XPENDING`](/docs/redis/commands/streams/xpending) after being deleted. Use [`XDELEX`](/docs/redis/commands/streams/xdelex) when you need control over those references.
+
+IDs are never reused, so the stream's ID sequence keeps moving forward after deletions. For bulk cleanup by size or age, [`XTRIM`](/docs/redis/commands/streams/xtrim) is the right command.
 
 ## Syntax
 
@@ -55690,7 +56462,11 @@ fn main() -> redis::RedisResult<()> {
 # XDELEX
 Source: https://upstash.com/docs/redis/commands/streams/xdelex
 
-Use `XDELEX` to delete entries with expiration.
+Use `XDELEX` to delete entries from a stream with control over what happens to consumer group references.
+
+`IDS <numids>` introduces the list of IDs and the count must match. The policy decides how consumer groups are affected: `KEEPREF`, the default, deletes the entries but leaves them in the pending entries lists of the groups that had received them, `DELREF` removes those references as well, and `ACKED` only deletes entries that every group has read and acknowledged, leaving the others in place.
+
+That last policy is what makes the command useful as a safe cleanup step: it removes exactly the entries nobody still owes work on. The reply holds one status code per requested ID. Where [`XDEL`](/docs/redis/commands/streams/xdel) always behaves like `KEEPREF`, `XDELEX` is its explicit form.
 
 ## Syntax
 
@@ -55703,7 +56479,7 @@ XDELEX <key> [KEEPREF | DELREF | ACKED] IDS <numids> <id> [<id> ...]
 | Argument | Required | Repeatable | Description |
 | --- | --- | --- | --- |
 | `<key>` | Yes | No | Redis key targeted by the command. |
-| `(KEEPREF \| DELREF \| ACKED)` | No | No | Choose one form: `KEEPREF`; `DELREF`; `ACKED`. |
+| `(KEEPREF \| DELREF \| ACKED)` | No | No | What happens to consumer-group references of the deleted entries: `KEEPREF` (the default) leaves them in place, `DELREF` removes them from every group's pending list, and `ACKED` only removes entries that every group has read and acknowledged. |
 | `IDS <numids> <id> [<id> ...]` | Yes | No | Entry IDs to target. Give the ID count first, then that many IDs. |
 
 ## Response
@@ -55857,7 +56633,13 @@ fn main() -> redis::RedisResult<()> {
 # XGROUP
 Source: https://upstash.com/docs/redis/commands/streams/xgroup
 
-Use `XGROUP` to manage consumer groups.
+Use `XGROUP` to manage the consumer groups of a stream.
+
+`CREATE` registers a group and sets the position it starts reading from: `0` replays the whole stream from the beginning, while `$` delivers only entries added after the group was created. `MKSTREAM` creates the stream too when it does not exist yet, which avoids an error on a group created before the first producer runs. `SETID` moves that position afterwards, which is how a group is rewound for a replay or fast-forwarded past a backlog.
+
+`CREATECONSUMER` and `DELCONSUMER` add and remove consumers explicitly; consumers are otherwise created on first read. Deleting a consumer returns how many pending entries went away with it, and those entries are then no longer pending for anyone, so hand them over with [`XCLAIM`](/docs/redis/commands/streams/xclaim) or [`XAUTOCLAIM`](/docs/redis/commands/streams/xautoclaim) first if the work still matters.
+
+`DESTROY` removes a group along with all of its pending state, while leaving the stream and its entries untouched.
 
 ## Syntax
 
@@ -56034,7 +56816,9 @@ fn main() -> redis::RedisResult<()> {
 # XINFO CONSUMERS
 Source: https://upstash.com/docs/redis/commands/streams/xinfo-consumers
 
-Use `XINFO CONSUMERS` to list group consumers.
+Use `XINFO CONSUMERS` to list the consumers of a consumer group.
+
+For each consumer the reply gives its name, how many entries it currently has pending, and how long it has been idle or inactive. This is the view that tells you whether workers are alive and balanced: a consumer with a growing pending count and a large idle time is one that stopped without acknowledging its work, and its entries are the ones to recover with [`XAUTOCLAIM`](/docs/redis/commands/streams/xautoclaim).
 
 ## Syntax
 
@@ -56201,7 +56985,9 @@ fn main() -> redis::RedisResult<()> {
 # XINFO GROUPS
 Source: https://upstash.com/docs/redis/commands/streams/xinfo-groups
 
-Use `XINFO GROUPS` to list stream groups.
+Use `XINFO GROUPS` to list the consumer groups defined on a stream.
+
+Each group is reported with its name, its number of consumers, how many entries are pending across the group, the ID it has delivered up to, and its lag, meaning how many entries in the stream it has not read yet. Lag and pending count together are the standard health signals for a stream consumer: a growing lag means consumers cannot keep up, while a growing pending count means they read entries but do not acknowledge them.
 
 ## Syntax
 
@@ -56364,7 +57150,11 @@ fn main() -> redis::RedisResult<()> {
 # XINFO STREAM
 Source: https://upstash.com/docs/redis/commands/streams/xinfo-stream
 
-Use `XINFO STREAM` to get stream info.
+Use `XINFO STREAM` to get information about a stream.
+
+The default reply summarizes the stream: how many entries it holds, the last generated ID, the number of consumer groups, and the first and last entries. `FULL` returns the detailed form instead, walking the entries along with every group, consumer, and pending entry, with `COUNT` limiting how many items each part of that reply contains (`COUNT 0` means no limit).
+
+Use the summary for monitoring and the full form when debugging a group that appears stuck, since it shows exactly which entries are pending and who owns them.
 
 ## Syntax
 
@@ -56520,7 +57310,9 @@ fn main() -> redis::RedisResult<()> {
 # XLEN
 Source: https://upstash.com/docs/redis/commands/streams/xlen
 
-Use `XLEN` to get stream length.
+Use `XLEN` to get the number of entries currently in a stream.
+
+Deleted and trimmed entries are not counted, and the reply is `0` when the key does not exist. The number reflects what is stored right now, not how many entries the stream has ever carried, so it is a measure of retained data rather than of throughput; a group's backlog is reported by the lag in [`XINFO GROUPS`](/docs/redis/commands/streams/xinfo-groups).
 
 ## Syntax
 
@@ -56683,7 +57475,13 @@ fn main() -> redis::RedisResult<()> {
 # XPENDING
 Source: https://upstash.com/docs/redis/commands/streams/xpending
 
-Use `XPENDING` to get pending messages info.
+Use `XPENDING` to inspect the entries that a consumer group has delivered but not yet acknowledged.
+
+With only a key and a group, the reply is a summary: how many entries are pending, the lowest and highest pending IDs, and the number of pending entries per consumer. That is the cheap form to poll for monitoring.
+
+The extended form, with a start, an end, and a count, lists the pending entries one by one with the consumer that owns each, how long it has been idle, and how many times it has been delivered. `IDLE` restricts the listing to entries idle for at least the given number of milliseconds, and a consumer name restricts it to one worker.
+
+A high delivery count points at an entry that keeps failing, and a long idle time points at a consumer that died holding work. Both are handed over to another consumer with [`XCLAIM`](/docs/redis/commands/streams/xclaim) or [`XAUTOCLAIM`](/docs/redis/commands/streams/xautoclaim).
 
 ## Syntax
 
@@ -56848,7 +57646,11 @@ fn main() -> redis::RedisResult<()> {
 # XRANGE
 Source: https://upstash.com/docs/redis/commands/streams/xrange
 
-Use `XRANGE` to get range of stream entries.
+Use `XRANGE` to read the entries of a stream within a range of IDs, from the oldest to the newest.
+
+`-` and `+` stand for the smallest and largest possible IDs, so `XRANGE key - +` reads the whole stream. An incomplete ID such as `1526985054069` is completed with the smallest possible sequence number for `<start>` and the largest for `<end>`, which makes it easy to select everything within one millisecond. Prefixing a bound with `(` makes it exclusive, and `COUNT` limits how many entries come back.
+
+Since IDs start with a timestamp, ranges are time queries: pass the milliseconds you care about and you get the entries recorded in that window. Paging works by repeating the call with the last ID you received, made exclusive with `(`. Use [`XREVRANGE`](/docs/redis/commands/streams/xrevrange) to walk the stream backwards.
 
 ## Syntax
 
@@ -57014,7 +57816,13 @@ fn main() -> redis::RedisResult<()> {
 # XREAD
 Source: https://upstash.com/docs/redis/commands/streams/xread
 
-Use `XREAD` to read stream entries.
+Use `XREAD` to read entries from one or more streams that are newer than a given ID.
+
+After `STREAMS`, all keys are listed first and then exactly one ID for each key, in the same order. Only entries with an ID greater than the one you give are returned, and the special ID `$` means "only entries added after this call", which is how a client starts tailing a live stream.
+
+`BLOCK <milliseconds>` waits for new data instead of returning an empty reply, with `0` waiting indefinitely, which turns the command into an efficient follow rather than a polling loop. `COUNT` caps how many entries per stream come back.
+
+`XREAD` keeps no server-side position: the client remembers the last ID it processed and passes it on the next call, and every reader sees every entry. When work should be split across consumers, with the server tracking what has been delivered and acknowledged, use a consumer group and [`XREADGROUP`](/docs/redis/commands/streams/xreadgroup).
 
 ## Syntax
 
@@ -57184,7 +57992,13 @@ fn main() -> redis::RedisResult<()> {
 # XREADGROUP
 Source: https://upstash.com/docs/redis/commands/streams/xreadgroup
 
-Use `XREADGROUP` to read as consumer group.
+Use `XREADGROUP` to read entries from a stream as a member of a consumer group, so that each entry goes to one consumer and Redis keeps track of what has not been acknowledged.
+
+After `STREAMS`, all keys come first and then one ID per key. The special ID `>` delivers entries that have never been delivered to the group and records them as pending for this consumer. Any other ID re-reads that consumer's own pending entries instead, starting after the given ID, which is how a consumer resumes after a restart: read from `0` first to finish old work, then switch to `>`.
+
+The consumer is created on first use. `COUNT` limits the batch size and `BLOCK <milliseconds>` waits for new entries rather than returning empty, with `0` waiting indefinitely. `NOACK` skips the pending entries list entirely, trading the delivery guarantee for speed.
+
+Entries stay pending until acknowledged with [`XACK`](/docs/redis/commands/streams/xack). That is what makes recovery possible: work left behind by a crashed consumer is visible in [`XPENDING`](/docs/redis/commands/streams/xpending) and can be taken over with [`XAUTOCLAIM`](/docs/redis/commands/streams/xautoclaim).
 
 ## Syntax
 
@@ -57361,7 +58175,11 @@ fn main() -> redis::RedisResult<()> {
 # XREVRANGE
 Source: https://upstash.com/docs/redis/commands/streams/xrevrange
 
-Use `XREVRANGE` to get range in reverse order.
+Use `XREVRANGE` to read the entries of a stream within a range of IDs, from the newest to the oldest.
+
+It is [`XRANGE`](/docs/redis/commands/streams/xrange) in reverse, and the bounds are given in reverse too: `<end>` comes before `<start>`, so `XREVRANGE key + -` walks the whole stream backwards. Incomplete IDs are completed the same way, `(` makes a bound exclusive, and `COUNT` limits the number of entries.
+
+`XREVRANGE key + - COUNT 1` is the idiomatic way to read the most recent entry of a stream.
 
 ## Syntax
 
@@ -57527,7 +58345,13 @@ fn main() -> redis::RedisResult<()> {
 # XTRIM
 Source: https://upstash.com/docs/redis/commands/streams/xtrim
 
-Use `XTRIM` to trim stream to max length.
+Use `XTRIM` to cap the size of a stream by removing old entries.
+
+`MAXLEN` keeps at most the given number of entries, dropping the oldest ones, while `MINID` drops every entry with an ID below a threshold, which is how you trim by age since IDs begin with a millisecond timestamp. The reply is the number of entries removed.
+
+`~` makes the trim approximate: the server stops at a convenient boundary and may leave a few extra entries, which is much cheaper on large streams and is the right default for background maintenance. `=` trims exactly, and `LIMIT` caps how many entries a single call may evict, which keeps one call from blocking for a long time.
+
+`KEEPREF`, `DELREF`, and `ACKED` decide what happens to consumer group references of the removed entries: `KEEPREF`, the default, leaves them in place, `DELREF` removes them from every group's pending list, and `ACKED` only removes entries that all groups have read and acknowledged. [`XADD`](/docs/redis/commands/streams/xadd) accepts the same options so a stream can be trimmed as it is written to.
 
 ## Syntax
 
@@ -57695,7 +58519,9 @@ fn main() -> redis::RedisResult<()> {
 # APPEND
 Source: https://upstash.com/docs/redis/commands/string/append
 
-Use `APPEND` to append value to a string.
+Use `APPEND` to add a value to the end of the string stored at a key.
+
+If the key does not exist it is created with the given value, so the command behaves like [`SET`](/docs/redis/commands/string/set) on a fresh key. The reply is the length of the string after the append. Redis grows the underlying buffer with room to spare, so repeated appends stay cheap, which makes this a reasonable way to accumulate log lines or serialized events into one value; [`GETRANGE`](/docs/redis/commands/string/getrange) can then read back a slice without transferring the whole thing.
 
 ## Syntax
 
@@ -57860,7 +58686,9 @@ fn main() -> redis::RedisResult<()> {
 # DECR
 Source: https://upstash.com/docs/redis/commands/string/decr
 
-Use `DECR` to decrement integer value by 1.
+Use `DECR` to subtract one from the integer stored at a key and get the result.
+
+A missing key counts as `0`, so the first call leaves `-1`. The value must be the string form of a 64-bit signed integer; anything else returns an error, as does an operation that would go below the minimum. The read, the subtraction, and the write happen atomically, so concurrent callers each get a distinct value and no decrement is lost, which is what makes it safe for counting down remaining quota or stock.
 
 ## Syntax
 
@@ -58025,7 +58853,9 @@ fn main() -> redis::RedisResult<()> {
 # DECRBY
 Source: https://upstash.com/docs/redis/commands/string/decrby
 
-Use `DECRBY` to decrement integer by amount.
+Use `DECRBY` to subtract an integer from the value stored at a key and get the result.
+
+A missing key counts as `0`. The stored value must be the string form of a 64-bit signed integer, and an operation that would exceed that range returns an error. The whole update is atomic, so concurrent callers cannot lose a decrement. Passing a negative amount adds instead, which makes [`INCRBY`](/docs/redis/commands/string/incrby) and `DECRBY` two views of the same operation.
 
 ## Syntax
 
@@ -58193,6 +59023,10 @@ Source: https://upstash.com/docs/redis/commands/string/delex
 
 Use `DELEX` to delete a string when a condition matches.
 
+`IFEQ` deletes the key only when its current value equals the given one and `IFNE` only when it differs. `IFDEQ` and `IFDNE` do the same against a digest of the value, as returned by [`DIGEST`](/docs/redis/commands/string/digest), which avoids sending a large value over the wire just to compare it.
+
+The comparison and the delete are one atomic step, which is what makes the command the correct way to release a lock or a claim: delete the key only if it still holds your token, so you never remove a lock that has expired and been taken by someone else. With no condition it simply deletes the key. The conditional forms require a string value, and a key of another type returns an error without being deleted.
+
 ## Syntax
 
 ```redis
@@ -58355,6 +59189,10 @@ Source: https://upstash.com/docs/redis/commands/string/digest
 
 Use `DIGEST` to get the digest of a string value.
 
+The reply is a 16-character lowercase hexadecimal XXH3 digest of the stored bytes, null when the key does not exist, and an error when the value is not a string. It is a fast non-cryptographic hash, meant for change detection rather than for security.
+
+Comparing digests lets a client tell whether a large value has changed without transferring it, for instance to decide whether a cached copy is still current. The same digest can be passed to the conditional forms of [`SET`](/docs/redis/commands/string/set) (`IFDEQ`, `IFDNE`) and [`DELEX`](/docs/redis/commands/string/delex), which turns it into a compact compare-and-set token for large values. `DIGEST` is an Upstash extension.
+
 ## Syntax
 
 ```redis
@@ -58513,7 +59351,9 @@ fn main() -> redis::RedisResult<()> {
 # GET
 Source: https://upstash.com/docs/redis/commands/string/get
 
-Use `GET` to get string value.
+Use `GET` to read the string value stored at a key.
+
+The reply is null when the key does not exist, and an error when the key holds a value of another type, such as a hash or a list. Strings in Redis are binary safe and can hold anything up to 512 MB, so the same command reads back text, JSON, and serialized binary alike. To read and delete in one step use [`GETDEL`](/docs/redis/commands/string/getdel), and to read and refresh the expiration use [`GETEX`](/docs/redis/commands/string/getex).
 
 ## Syntax
 
@@ -58685,7 +59525,9 @@ fn main() -> redis::RedisResult<()> {
 # GETDEL
 Source: https://upstash.com/docs/redis/commands/string/getdel
 
-Use `GETDEL` to get value and delete key.
+Use `GETDEL` to read the value of a key and delete the key in the same atomic step.
+
+The reply is the value, or null when the key does not exist, and an error when the value is not a string. Because nothing can run between the read and the delete, exactly one caller can obtain the value, which is what makes it right for one-shot data such as a one-time token, a password reset code, or a handoff between two processes. It replaces the [`GET`](/docs/redis/commands/string/get) plus [`DEL`](/docs/redis/commands/generic/del) pair and its race.
 
 ## Syntax
 
@@ -58853,7 +59695,11 @@ fn main() -> redis::RedisResult<()> {
 # GETEX
 Source: https://upstash.com/docs/redis/commands/string/getex
 
-Use `GETEX` to get value and set expiration.
+Use `GETEX` to read a value and change its expiration in the same call.
+
+`EX`, `PX`, `EXAT`, and `PXAT` set a new lifetime or deadline, and `PERSIST` removes the expiration so the key stops expiring. With no option at all the expiration is left exactly as it was, which is the difference from [`GET`](/docs/redis/commands/string/get) plus a separate [`EXPIRE`](/docs/redis/commands/generic/expire).
+
+Doing both at once is what makes a sliding expiration correct: reading a session extends it atomically, with no window in which the key could expire between the read and the refresh.
 
 ## Syntax
 
@@ -58866,7 +59712,7 @@ GETEX <key> [EX <seconds> | PX <milliseconds> | EXAT <unix-time-seconds> | PXAT
 | Argument | Required | Repeatable | Description |
 | --- | --- | --- | --- |
 | `<key>` | Yes | No | Redis key targeted by the command. |
-| `(EX <seconds> \| PX <milliseconds> \| EXAT <unix-time-seconds> \| PXAT <unix-time-milliseconds> \| PERSIST)` | No | No | Choose one form: `EX` (set a lifetime in seconds); `PX` (set a lifetime in milliseconds); `EXAT` (expire at a Unix timestamp in seconds); `PXAT` (expire at a Unix timestamp in milliseconds); `PERSIST`. |
+| `(EX <seconds> \| PX <milliseconds> \| EXAT <unix-time-seconds> \| PXAT <unix-time-milliseconds> \| PERSIST)` | No | No | Choose one form: `EX` (set a lifetime in seconds); `PX` (set a lifetime in milliseconds); `EXAT` (expire at a Unix timestamp in seconds); `PXAT` (expire at a Unix timestamp in milliseconds); `PERSIST` (remove the expiration). Left unchanged when omitted. |
 
 ## Response
 
@@ -59017,7 +59863,11 @@ fn main() -> redis::RedisResult<()> {
 # GETRANGE
 Source: https://upstash.com/docs/redis/commands/string/getrange
 
-Use `GETRANGE` to get substring of string.
+Use `GETRANGE` to read part of the string stored at a key.
+
+`<start>` and `<end>` are zero-based byte offsets, both inclusive, and may be negative to count from the end, so `GETRANGE key 0 -1` returns the whole value. Offsets outside the string are clamped rather than treated as errors, and a missing key returns an empty string.
+
+Since the range is applied on the server, this is how you read the head of a large value, or a fixed-width field inside one, without transferring the rest. `SUBSTR` is accepted as a deprecated alias with the same arguments and reply.
 
 ## Syntax
 
@@ -59186,7 +60036,11 @@ fn main() -> redis::RedisResult<()> {
 # GETSET
 Source: https://upstash.com/docs/redis/commands/string/getset
 
-Use `GETSET` to set value and return old value.
+Use `GETSET` to set a new value and get the previous one in a single atomic step.
+
+The reply is the old value, or null when the key did not exist. Note that the key's time to live is discarded, so a key with an expiration becomes permanent when written this way.
+
+The classic use is resetting a counter while reading it, where the atomicity guarantees nothing is counted twice. Redis deprecates the command in favor of [`SET`](/docs/redis/commands/string/set) with the `GET` option, which does the same thing and can additionally set or keep an expiration in the same call.
 
 ## Syntax
 
@@ -59350,7 +60204,11 @@ fn main() -> redis::RedisResult<()> {
 # INCR
 Source: https://upstash.com/docs/redis/commands/string/incr
 
-Use `INCR` to increment integer value by 1.
+Use `INCR` to add one to the integer stored at a key and get the result.
+
+A missing key counts as `0`, so the first call returns `1` and no initialization is needed. The value must be the string form of a 64-bit signed integer; anything else returns an error, as does an overflow.
+
+The read, the addition, and the write are one atomic step, so concurrent callers each receive a distinct number and no increment is lost. That property is what makes it the basis for counters, id generators, and rate limiters, usually combined with [`EXPIRE`](/docs/redis/commands/generic/expire) to reset the count for each window.
 
 ## Syntax
 
@@ -59515,7 +60373,11 @@ fn main() -> redis::RedisResult<()> {
 # INCRBY
 Source: https://upstash.com/docs/redis/commands/string/incrby
 
-Use `INCRBY` to increment integer by amount.
+Use `INCRBY` to add an integer to the value stored at a key and get the result.
+
+A missing key counts as `0`, the value must be the string form of a 64-bit signed integer, and an operation that would leave that range returns an error. A negative amount subtracts, which makes it interchangeable with [`DECRBY`](/docs/redis/commands/string/decrby).
+
+Like [`INCR`](/docs/redis/commands/string/incr), the update is atomic, so it is safe for counters that several clients update at once, such as adding a batch size to a running total.
 
 ## Syntax
 
@@ -59681,7 +60543,11 @@ fn main() -> redis::RedisResult<()> {
 # INCRBYFLOAT
 Source: https://upstash.com/docs/redis/commands/string/incrbyfloat
 
-Use `INCRBYFLOAT` to increment float by amount.
+Use `INCRBYFLOAT` to add a floating point number to the value stored at a key and get the result.
+
+The stored value and the increment are parsed as double precision floats, and a missing key counts as `0`. A negative increment subtracts, and there is no separate decrement command. A value that is not a valid number returns an error.
+
+The reply is the new value as a string, which client libraries usually decode into a native number. The result is stored in that same textual form, so repeated increments accumulate the usual binary floating point rounding error: for money and other exact quantities, count in integer units with [`INCRBY`](/docs/redis/commands/string/incrby) instead.
 
 ## Syntax
 
@@ -59851,7 +60717,11 @@ fn main() -> redis::RedisResult<()> {
 # MGET
 Source: https://upstash.com/docs/redis/commands/string/mget
 
-Use `MGET` to get values of multiple keys.
+Use `MGET` to read the values of several keys in one call.
+
+The reply holds one entry per key, in the order requested, so it can be zipped straight back onto your list of keys. Keys that do not exist, and keys holding a value that is not a string, come back as null rather than raising an error.
+
+One `MGET` replaces N round trips of [`GET`](/docs/redis/commands/string/get), which is usually the difference that matters when loading a batch of cached objects.
 
 ## Syntax
 
@@ -60019,7 +60889,11 @@ fn main() -> redis::RedisResult<()> {
 # MSET
 Source: https://upstash.com/docs/redis/commands/string/mset
 
-Use `MSET` to set multiple keys at once.
+Use `MSET` to set several keys to their values in one atomic call.
+
+All the keys are written together, with no other command running in between, so other clients never observe a state where only part of the batch has been applied. Existing values are overwritten and their expirations are discarded. The reply is always `OK`.
+
+Use [`MSETNX`](/docs/redis/commands/string/msetnx) when the write should only happen if none of the keys exist, and set keys individually with [`SET`](/docs/redis/commands/string/set) when each needs its own expiration.
 
 ## Syntax
 
@@ -60186,7 +61060,9 @@ fn main() -> redis::RedisResult<()> {
 # MSETNX
 Source: https://upstash.com/docs/redis/commands/string/msetnx
 
-Use `MSETNX` to set multiple keys if none exist.
+Use `MSETNX` to set several keys at once, but only if none of them already exists.
+
+The command is all or nothing: if even a single key is present, nothing is written and the reply is `0`; otherwise every key is written and the reply is `1`. Since the check and the writes are one atomic step, it can be used to claim a whole group of related keys, so that a partially initialized state can never be observed.
 
 ## Syntax
 
@@ -60380,7 +61256,11 @@ Source: https://upstash.com/docs/redis/commands/string/overview
 # PSETEX
 Source: https://upstash.com/docs/redis/commands/string/psetex
 
-Use `PSETEX` to set value with ms expiration.
+Use `PSETEX` to set a value together with a lifetime in milliseconds.
+
+The value and the expiration are applied in the same atomic step, so the key never exists without its expiration, which is the point of the command: setting the value and then expiring it separately leaves a window where a crash makes the key permanent. A lifetime of zero or less returns an error.
+
+It is the millisecond form of [`SETEX`](/docs/redis/commands/string/setex), and equivalent to [`SET`](/docs/redis/commands/string/set) with the `PX` option, which is the more flexible way to write the same thing.
 
 ## Syntax
 
@@ -60546,7 +61426,13 @@ fn main() -> redis::RedisResult<()> {
 # SET
 Source: https://upstash.com/docs/redis/commands/string/set
 
-Use `SET` to set string value.
+Use `SET` to store a string value at a key, replacing whatever was there before, whatever its type.
+
+By default the value is written unconditionally and the key's previous time to live is discarded. `KEEPTTL` preserves it, while `EX`, `PX`, `EXAT`, and `PXAT` attach a new lifetime in seconds or milliseconds, or an absolute deadline as a Unix timestamp. Setting the value and its expiration in one command is what keeps a key from ever existing without one.
+
+The condition decides whether the write happens at all. `NX` writes only when the key does not exist, which combined with an expiration is the standard way to acquire a lock, and `XX` writes only when it already exists, which refreshes a value without creating it. `IFEQ` and `IFNE` compare the current value with the one you supply, and `IFDEQ` and `IFDNE` compare its digest as returned by [`DIGEST`](/docs/redis/commands/string/digest), so a large value can be checked without sending it; these conditional forms are implemented by this Upstash deployment and give you compare-and-set semantics in a single command. `IFEQ` and `IFDEQ` require the key to exist, while `IFNE` and `IFDNE` also write when it does not.
+
+`GET` makes the reply the previous value instead of `OK`, which is how you swap a value and read what it replaced in one atomic step. When a condition prevents the write, the reply is null.
 
 ## Syntax
 
@@ -60719,7 +61605,11 @@ fn main() -> redis::RedisResult<()> {
 # SETEX
 Source: https://upstash.com/docs/redis/commands/string/setex
 
-Use `SETEX` to set value with expiration.
+Use `SETEX` to set a value together with a lifetime in seconds.
+
+The value and the expiration are applied atomically, so the key never exists without an expiration; writing the value and expiring it in two commands leaves a window in which a failure makes the key permanent. A lifetime of zero or less returns an error.
+
+Use [`PSETEX`](/docs/redis/commands/string/psetex) for millisecond precision. Both are equivalent to [`SET`](/docs/redis/commands/string/set) with `EX` or `PX`, which additionally supports conditions and reading the previous value.
 
 ## Syntax
 
@@ -60885,7 +61775,11 @@ fn main() -> redis::RedisResult<()> {
 # SETNX
 Source: https://upstash.com/docs/redis/commands/string/setnx
 
-Use `SETNX` to set value if key doesn't exist.
+Use `SETNX` to set a value only if the key does not already exist.
+
+The reply is `1` when the key was created and `0` when it was already there and nothing was written. The check and the write are atomic, so exactly one of several racing clients succeeds.
+
+That makes it the classic lock primitive, but on its own it is an incomplete one: a client that fails after acquiring leaves the key behind forever. Prefer `SET key value NX EX <ttl>`, which claims the key and attaches an expiration in the same step, and release the lock with [`DELEX`](/docs/redis/commands/string/delex) so you only delete it while you still own it.
 
 ## Syntax
 
@@ -61049,7 +61943,11 @@ fn main() -> redis::RedisResult<()> {
 # SETRANGE
 Source: https://upstash.com/docs/redis/commands/string/setrange
 
-Use `SETRANGE` to overwrite part of string.
+Use `SETRANGE` to overwrite part of the string stored at a key, starting at a byte offset.
+
+The key is created when it does not exist, and if the offset lies past the current end of the value the string is first padded with zero bytes, so writing at a large offset allocates everything up to it. The reply is the length of the string after the write.
+
+Together with [`GETRANGE`](/docs/redis/commands/string/getrange) this makes it possible to treat a string as a fixed-layout record and update one field in place, without reading and rewriting the whole value.
 
 ## Syntax
 
@@ -61218,7 +62116,9 @@ fn main() -> redis::RedisResult<()> {
 # STRLEN
 Source: https://upstash.com/docs/redis/commands/string/strlen
 
-Use `STRLEN` to get string length.
+Use `STRLEN` to get the length in bytes of the string stored at a key.
+
+The reply is `0` when the key does not exist, and an error when the value is not a string. Since the value itself is never transferred, it is the cheap way to check how large a value is, for instance before deciding whether to fetch it or to read only part of it with [`GETRANGE`](/docs/redis/commands/string/getrange). The count is in bytes, so multi-byte characters count more than once.
 
 ## Syntax
 
@@ -61383,7 +62283,11 @@ fn main() -> redis::RedisResult<()> {
 # DISCARD
 Source: https://upstash.com/docs/redis/commands/transactions/discard
 
-Use `DISCARD` to discard queued commands.
+Use `DISCARD` to throw away the commands queued since [`MULTI`](/docs/redis/commands/transactions/multi) and leave the transaction without running anything.
+
+It also clears every key watched with [`WATCH`](/docs/redis/commands/transactions/watch), so the connection ends up in its normal state. This is what you call when the data you read after `WATCH` turns out to make the queued update unnecessary or invalid.
+
+The raw command is TCP-only. Over HTTP, use the transaction or pipeline API of an Upstash SDK instead of sending this command directly.
 
 ## Syntax
 
@@ -61507,7 +62411,13 @@ fn main() -> redis::RedisResult<()> {
 # EXEC
 Source: https://upstash.com/docs/redis/commands/transactions/exec
 
-Use `EXEC` to execute queued commands.
+Use `EXEC` to run the commands queued since [`MULTI`](/docs/redis/commands/transactions/multi).
+
+They execute one after another with no other client's command in between, and the reply is an array holding one result per queued command, in order. Errors raised by individual commands appear in that array rather than stopping the rest, so check each entry.
+
+If any key watched with [`WATCH`](/docs/redis/commands/transactions/watch) was modified after it was watched, the transaction is not executed at all and the reply is null, which is the signal to read the data again and retry. Watches are cleared afterwards either way.
+
+The raw command is TCP-only. Over HTTP, use the transaction or pipeline API of an Upstash SDK instead of sending this command directly.
 
 ## Syntax
 
@@ -61635,6 +62545,12 @@ Source: https://upstash.com/docs/redis/commands/transactions/multi
 
 Use `MULTI` to start a transaction.
 
+Commands sent afterwards are not executed but queued, each answered with `QUEUED`, until [`EXEC`](/docs/redis/commands/transactions/exec) runs them all in order with nothing else in between, or [`DISCARD`](/docs/redis/commands/transactions/discard) throws them away.
+
+A Redis transaction is atomic in the sense that no other client sees a partial result, but it is not a rollback mechanism: a command that fails at queue time, such as one with a syntax error, aborts the whole transaction, while a command that fails at execution time, such as one applied to the wrong type, leaves the commands around it applied. Combine it with [`WATCH`](/docs/redis/commands/transactions/watch) when the transaction depends on values you read beforehand.
+
+The raw command is TCP-only. Over HTTP, use the transaction or pipeline API of an Upstash SDK instead of sending this command directly.
+
 ## Syntax
 
 ```redis
@@ -61770,7 +62686,11 @@ Source: https://upstash.com/docs/redis/commands/transactions/overview
 # UNWATCH
 Source: https://upstash.com/docs/redis/commands/transactions/unwatch
 
-Use `UNWATCH` to unwatch all keys.
+Use `UNWATCH` to forget all the keys watched with [`WATCH`](/docs/redis/commands/transactions/watch) on this connection.
+
+Afterwards the next [`EXEC`](/docs/redis/commands/transactions/exec) is no longer conditional on those keys. It is the way to abandon an optimistic locking attempt when, after reading the watched data, you decide not to run a transaction at all, so a later unrelated transaction is not aborted by a change to keys you no longer care about. [`EXEC`](/docs/redis/commands/transactions/exec) and [`DISCARD`](/docs/redis/commands/transactions/discard) clear watches on their own.
+
+The raw command is TCP-only. Over HTTP, use the transaction or pipeline API of an Upstash SDK instead of sending this command directly.
 
 ## Syntax
 
@@ -61895,7 +62815,13 @@ fn main() -> redis::RedisResult<()> {
 # WATCH
 Source: https://upstash.com/docs/redis/commands/transactions/watch
 
-Use `WATCH` to watch keys for changes.
+Use `WATCH` to mark keys whose modification should cancel the next transaction, which gives you optimistic locking.
+
+If any watched key is changed by another client between the `WATCH` and the [`EXEC`](/docs/redis/commands/transactions/exec), the transaction is not executed and `EXEC` replies with null instead. Nothing is locked in the meantime: other clients keep working normally, and the conflict is detected rather than prevented.
+
+The usual loop is: watch the keys, read them, decide what to write, open [`MULTI`](/docs/redis/commands/transactions/multi), queue the writes, and call `EXEC`, retrying from the top when the reply is null. That is how a read-modify-write cycle stays correct without holding a lock. All watches are cleared by `EXEC` and [`DISCARD`](/docs/redis/commands/transactions/discard).
+
+The raw command is TCP-only. Over HTTP, use the transaction or pipeline API of an Upstash SDK instead of sending this command directly.
 
 ## Syntax
 
diff --git a/llms.txt b/llms.txt
index 9f16941c8..ae3c4265c 100644
--- a/llms.txt
+++ b/llms.txt
@@ -342,9 +342,9 @@
 - [GEODIST](https://upstash.com/docs/redis/commands/geo/geodist.md): Get distance between two members.
 - [GEOHASH](https://upstash.com/docs/redis/commands/geo/geohash.md): Get geohash strings for members.
 - [GEOPOS](https://upstash.com/docs/redis/commands/geo/geopos.md): Get coordinates of members.
-- [GEORADIUS](https://upstash.com/docs/redis/commands/geo/georadius.md): Query members within radius.
+- [GEORADIUS](https://upstash.com/docs/redis/commands/geo/georadius.md): Find members within a radius of a point.
 - [GEORADIUS_RO](https://upstash.com/docs/redis/commands/geo/georadius-ro.md): Find members within a radius of a point.
-- [GEORADIUSBYMEMBER](https://upstash.com/docs/redis/commands/geo/georadiusbymember.md): Radius query centered on member.
+- [GEORADIUSBYMEMBER](https://upstash.com/docs/redis/commands/geo/georadiusbymember.md): Find members within a radius of another member.
 - [GEORADIUSBYMEMBER_RO](https://upstash.com/docs/redis/commands/geo/georadiusbymember-ro.md): Find members within a radius of another member.
 - [GEOSEARCH](https://upstash.com/docs/redis/commands/geo/geosearch.md): Search for members in an area.
 - [GEOSEARCHSTORE](https://upstash.com/docs/redis/commands/geo/geosearchstore.md): Store geosearch results.
@@ -391,7 +391,7 @@
 - [JSON.CLEAR](https://upstash.com/docs/redis/commands/json/json-clear.md): Clear JSON values.
 - [JSON.DEBUG](https://upstash.com/docs/redis/commands/json/json-debug.md): Inspect JSON memory usage.
 - [JSON.DEL](https://upstash.com/docs/redis/commands/json/json-del.md): Delete JSON values.
-- [JSON.FORGET](https://upstash.com/docs/redis/commands/json/json-forget.md): Alias for JSON.DEL.
+- [JSON.FORGET](https://upstash.com/docs/redis/commands/json/json-forget.md): Delete JSON values (alias of JSON.DEL).
 - [JSON.GET](https://upstash.com/docs/redis/commands/json/json-get.md): Get JSON values.
 - [JSON.MERGE](https://upstash.com/docs/redis/commands/json/json-merge.md): Merge JSON values.
 - [JSON.MGET](https://upstash.com/docs/redis/commands/json/json-mget.md): Get values from multiple keys.
@@ -416,9 +416,9 @@
 - [LINSERT](https://upstash.com/docs/redis/commands/list/linsert.md): Insert before or after pivot.
 - [LLEN](https://upstash.com/docs/redis/commands/list/llen.md): Get list length.
 - [LMOVE](https://upstash.com/docs/redis/commands/list/lmove.md): Move element between lists.
-- [LMPOP](https://upstash.com/docs/redis/commands/list/lmpop.md): Pop from multiple lists.
+- [LMPOP](https://upstash.com/docs/redis/commands/list/lmpop.md): Pop from the first non-empty list.
 - [LPOP](https://upstash.com/docs/redis/commands/list/lpop.md): Pop from list head.
-- [LPOS](https://upstash.com/docs/redis/commands/list/lpos.md): Find element position.
+- [LPOS](https://upstash.com/docs/redis/commands/list/lpos.md): Find the position of an element.
 - [LPUSH](https://upstash.com/docs/redis/commands/list/lpush.md): Push to list head.
 - [LPUSHX](https://upstash.com/docs/redis/commands/list/lpushx.md): Push to head if list exists.
 - [LRANGE](https://upstash.com/docs/redis/commands/list/lrange.md): Get range of elements.
@@ -481,9 +481,9 @@
 - [SINTERSTORE](https://upstash.com/docs/redis/commands/set/sinterstore.md): Store set intersection.
 - [SISMEMBER](https://upstash.com/docs/redis/commands/set/sismember.md): Check if member exists in set.
 - [SMEMBERS](https://upstash.com/docs/redis/commands/set/smembers.md): Get all set members.
-- [SMISMEMBER](https://upstash.com/docs/redis/commands/set/smismember.md): Check multiple members.
+- [SMISMEMBER](https://upstash.com/docs/redis/commands/set/smismember.md): Check membership of several values.
 - [SMOVE](https://upstash.com/docs/redis/commands/set/smove.md): Move member between sets.
-- [SPOP](https://upstash.com/docs/redis/commands/set/spop.md): Remove random members.
+- [SPOP](https://upstash.com/docs/redis/commands/set/spop.md): Remove and return random members.
 - [SRANDMEMBER](https://upstash.com/docs/redis/commands/set/srandmember.md): Get random members.
 - [SREM](https://upstash.com/docs/redis/commands/set/srem.md): Remove members from a set.
 - [SSCAN](https://upstash.com/docs/redis/commands/set/sscan.md): Incrementally iterate set members.
@@ -503,15 +503,15 @@
 - [ZINTERCARD](https://upstash.com/docs/redis/commands/sorted-set/zintercard.md): Get intersection cardinality.
 - [ZINTERSTORE](https://upstash.com/docs/redis/commands/sorted-set/zinterstore.md): Store sorted set intersection.
 - [ZLEXCOUNT](https://upstash.com/docs/redis/commands/sorted-set/zlexcount.md): Count members in lex range.
-- [ZMPOP](https://upstash.com/docs/redis/commands/sorted-set/zmpop.md): Pop members from sorted sets.
+- [ZMPOP](https://upstash.com/docs/redis/commands/sorted-set/zmpop.md): Pop from the first non-empty sorted set.
 - [ZMSCORE](https://upstash.com/docs/redis/commands/sorted-set/zmscore.md): Get scores of multiple members.
 - [ZPOPMAX](https://upstash.com/docs/redis/commands/sorted-set/zpopmax.md): Pop members with highest scores.
 - [ZPOPMIN](https://upstash.com/docs/redis/commands/sorted-set/zpopmin.md): Pop members with lowest scores.
 - [ZRANDMEMBER](https://upstash.com/docs/redis/commands/sorted-set/zrandmember.md): Get random members.
-- [ZRANGE](https://upstash.com/docs/redis/commands/sorted-set/zrange.md): Get members by index range.
+- [ZRANGE](https://upstash.com/docs/redis/commands/sorted-set/zrange.md): Get members by index, score, or lex range.
 - [ZRANGEBYLEX](https://upstash.com/docs/redis/commands/sorted-set/zrangebylex.md): Get members by lex range.
 - [ZRANGEBYSCORE](https://upstash.com/docs/redis/commands/sorted-set/zrangebyscore.md): Get members by score range.
-- [ZRANGESTORE](https://upstash.com/docs/redis/commands/sorted-set/zrangestore.md): Store range result.
+- [ZRANGESTORE](https://upstash.com/docs/redis/commands/sorted-set/zrangestore.md): Store the result of a range query.
 - [ZRANK](https://upstash.com/docs/redis/commands/sorted-set/zrank.md): Get member's rank.
 - [ZREM](https://upstash.com/docs/redis/commands/sorted-set/zrem.md): Remove members.
 - [ZREMRANGEBYLEX](https://upstash.com/docs/redis/commands/sorted-set/zremrangebylex.md): Remove members by lex range.
@@ -532,7 +532,7 @@
 - [XAUTOCLAIM](https://upstash.com/docs/redis/commands/streams/xautoclaim.md): Auto-claim idle messages.
 - [XCLAIM](https://upstash.com/docs/redis/commands/streams/xclaim.md): Claim pending messages.
 - [XDEL](https://upstash.com/docs/redis/commands/streams/xdel.md): Delete stream entries.
-- [XDELEX](https://upstash.com/docs/redis/commands/streams/xdelex.md): Delete entries with expiration.
+- [XDELEX](https://upstash.com/docs/redis/commands/streams/xdelex.md): Delete entries with reference control.
 - [XGROUP](https://upstash.com/docs/redis/commands/streams/xgroup.md): Manage consumer groups.
 - [XINFO CONSUMERS](https://upstash.com/docs/redis/commands/streams/xinfo-consumers.md): List group consumers.
 - [XINFO GROUPS](https://upstash.com/docs/redis/commands/streams/xinfo-groups.md): List stream groups.
diff --git a/redis/commands/bitmap/bitcount.mdx b/redis/commands/bitmap/bitcount.mdx
index 793810c34..78278f36c 100644
--- a/redis/commands/bitmap/bitcount.mdx
+++ b/redis/commands/bitmap/bitcount.mdx
@@ -3,7 +3,11 @@ title: "BITCOUNT"
 description: "Count set bits in a string."
 ---
 
-Use `BITCOUNT` to count set bits in a string.
+Use `BITCOUNT` to count the bits set to 1 in the string stored at a key.
+
+Without a range the whole value is counted. `<start>` and `<end>` restrict the count to a part of the value and are interpreted as byte offsets by default, or as bit offsets when `BIT` is given. Both ends are inclusive and may be negative to count backwards from the end of the value, where `-1` is the last byte or bit. A missing key is treated as an empty string and returns `0`.
+
+`BITCOUNT` is the usual way to read a bitmap built with [`SETBIT`](/redis/commands/bitmap/setbit), for example to count how many users were active on a given day when each user has a fixed bit position.
 
 ## Syntax
 
diff --git a/redis/commands/bitmap/bitfield-ro.mdx b/redis/commands/bitmap/bitfield-ro.mdx
index 0179345d4..26561f978 100644
--- a/redis/commands/bitmap/bitfield-ro.mdx
+++ b/redis/commands/bitmap/bitfield-ro.mdx
@@ -5,6 +5,8 @@ description: "Read bitfield values."
 
 Use `BITFIELD_RO` to read one or more bitfield values without modifying the key.
 
+It is the read-only form of [`BITFIELD`](/redis/commands/bitmap/bitfield) and accepts `GET` operations only, so it is safe to run on replicas and from read-only scripts. Each `GET` names an encoding, `u<bits>` for unsigned or `i<bits>` for signed integers, and a bit offset that can be written as `#<n>` to address the n-th field of that width. The reply holds one integer per `GET`, and any part of a field that lies past the end of the stored string reads as zero.
+
 ## Syntax
 
 ```redis
diff --git a/redis/commands/bitmap/bitfield.mdx b/redis/commands/bitmap/bitfield.mdx
index e12bc38ee..6cde68c8f 100644
--- a/redis/commands/bitmap/bitfield.mdx
+++ b/redis/commands/bitmap/bitfield.mdx
@@ -3,7 +3,13 @@ title: "BITFIELD"
 description: "Perform arbitrary bitfield operations."
 ---
 
-Use `BITFIELD` to perform arbitrary bitfield operations.
+Use `BITFIELD` to treat a string as an array of packed integers and run several operations on it in a single atomic call.
+
+Every operation names an encoding and a bit offset. The encoding is `u<bits>` for unsigned integers (up to 63 bits) or `i<bits>` for signed integers (up to 64 bits). The offset is counted in bits from the start of the value or, when prefixed with `#`, in units of the encoding width, so `#2` with `u8` addresses the third 8-bit field. The string grows automatically with zero bits when an operation addresses an offset past its current end.
+
+`GET` reads a field, `SET` writes one and returns its previous value, and `INCRBY` adds a possibly negative increment and returns the new value. `OVERFLOW` sets how the `SET` and `INCRBY` operations that follow it behave when a value does not fit the encoding: `WRAP` wraps around like modular arithmetic and is the default, `SAT` saturates at the minimum or maximum of the encoding, and `FAIL` leaves the field unchanged and returns null for that operation. The reply is an array with one entry per operation, in the order the operations were given.
+
+Packing many small counters into a single key this way saves memory and keeps the whole update atomic, which makes it a good fit for rate limiters and compact per-user counters.
 
 ## Syntax
 
@@ -16,7 +22,7 @@ BITFIELD <key> [GET <encoding> <offset> | [OVERFLOW WRAP | SAT | FAIL] (SET <enc
 | Argument | Required | Repeatable | Description |
 | --- | --- | --- | --- |
 | `<key>` | Yes | No | Redis key targeted by the command. |
-| `(GET <encoding> <offset> \| [OVERFLOW WRAP \| SAT \| FAIL] (SET <encoding> <offset> <value> \| INCRBY <encoding> <offset> <increment>))` | No | Yes | Choose one form: `GET` (also return the previous value); `OVERFLOW`; `WRAP`; `SAT`; `FAIL`; `SET`; `INCRBY`. |
+| `(GET <encoding> <offset> \| [OVERFLOW WRAP \| SAT \| FAIL] (SET <encoding> <offset> <value> \| INCRBY <encoding> <offset> <increment>))` | No | Yes | An operation on a field of `<encoding>` (`u<bits>` unsigned up to 63 bits, or `i<bits>` signed up to 64 bits) at `<offset>` bits, or at `#<n>` to address the n-th field of that width: `GET` reads it, `SET` writes it and returns the previous value, and `INCRBY` adds an increment and returns the new value. `OVERFLOW` sets how the `SET` and `INCRBY` operations after it handle a value that does not fit: `WRAP` wraps around (the default), `SAT` saturates at the encoding's limits, and `FAIL` leaves the field unchanged and returns null. Repeat to run several operations in one atomic call. |
 
 ## Response
 
diff --git a/redis/commands/bitmap/bitop.mdx b/redis/commands/bitmap/bitop.mdx
index 1e5c04557..dd98b2809 100644
--- a/redis/commands/bitmap/bitop.mdx
+++ b/redis/commands/bitmap/bitop.mdx
@@ -3,7 +3,13 @@ title: "BITOP"
 description: "Perform bitwise operations between strings."
 ---
 
-Use `BITOP` to perform bitwise operations between strings.
+Use `BITOP` to combine several strings with a bitwise operation and store the result in another key.
+
+Source strings are combined bit by bit, and shorter ones are treated as if they were padded with zero bits up to the length of the longest input, so the destination always ends up as long as the longest source. A missing key counts as an empty string, and if the result is empty the destination key is deleted. The reply is the length of the stored value in bytes.
+
+`AND`, `OR`, and `XOR` accept any number of source keys and `NOT` accepts exactly one. The remaining operators compare the first key with the rest: `DIFF` keeps the bits set in the first key and in none of the others, `DIFF1` keeps the bits set in at least one of the other keys but not in the first, `ANDOR` keeps the bits set in the first key and in at least one of the others, and `ONE` keeps the bits set in exactly one of the source keys. `DIFF`, `DIFF1`, and `ANDOR` each require at least two source keys.
+
+This is how bitmaps are used as sets: with one bit per user, `AND` gives users present in every bitmap and `OR` gives users present in any of them, and [`BITCOUNT`](/redis/commands/bitmap/bitcount) then turns the result into a number.
 
 ## Syntax
 
@@ -15,7 +21,7 @@ BITOP (AND | OR | XOR | NOT | DIFF | DIFF1 | ANDOR | ONE) <destkey> <key> [<key>
 
 | Argument | Required | Repeatable | Description |
 | --- | --- | --- | --- |
-| `(AND \| OR \| XOR \| NOT \| DIFF \| DIFF1 \| ANDOR \| ONE)` | Yes | No | Choose one form: `AND`; `OR`; `XOR`; `NOT`; `DIFF`; `DIFF1`; `ANDOR`; `ONE`. |
+| `(AND \| OR \| XOR \| NOT \| DIFF \| DIFF1 \| ANDOR \| ONE)` | Yes | No | The bitwise operation to apply. `AND`, `OR`, and `XOR` combine any number of source keys and `NOT` inverts exactly one. The rest compare the first key with the others: `DIFF` keeps bits set in the first key and in none of the others, `DIFF1` keeps bits set in at least one of the others but not in the first, `ANDOR` keeps bits set in the first key and in at least one of the others, and `ONE` keeps bits set in exactly one source key. |
 | `<destkey>` | Yes | No | Redis key used as destkey. |
 | `<key>` | Yes | Yes | Redis key targeted by the command. |
 
diff --git a/redis/commands/bitmap/bitpos.mdx b/redis/commands/bitmap/bitpos.mdx
index e8beb24be..7f0b3665c 100644
--- a/redis/commands/bitmap/bitpos.mdx
+++ b/redis/commands/bitmap/bitpos.mdx
@@ -3,7 +3,11 @@ title: "BITPOS"
 description: "Find first bit set or clear in a string."
 ---
 
-Use `BITPOS` to find first bit set or clear in a string.
+Use `BITPOS` to find the position of the first bit set to `0` or `1` in a string.
+
+The whole value is searched unless `<start>` and `<end>` are given, and those are byte offsets by default or bit offsets when `BIT` is given. Both ends are inclusive and may be negative to count backwards from the end of the value. The reply is always an absolute bit position counted from the start of the string, or `-1` when no matching bit is found.
+
+One edge case is worth remembering: when you look for a `0` in a string of all ones and give no explicit end, the reply is the position of the first bit past the end of the string, because the value is treated as if it were followed by an infinite run of zero bits. Bounding the search with an explicit range returns `-1` in the same situation.
 
 ## Syntax
 
diff --git a/redis/commands/bitmap/getbit.mdx b/redis/commands/bitmap/getbit.mdx
index 0d73d6622..2bacc8c8b 100644
--- a/redis/commands/bitmap/getbit.mdx
+++ b/redis/commands/bitmap/getbit.mdx
@@ -3,7 +3,9 @@ title: "GETBIT"
 description: "Get the bit value at offset."
 ---
 
-Use `GETBIT` to get the bit value at offset.
+Use `GETBIT` to read a single bit of the string stored at a key.
+
+The offset is counted in bits from the start of the value, so offset `0` is the most significant bit of the first byte. When the key does not exist, or the offset lies past the end of the stored string, the bit reads as `0` rather than producing an error.
 
 ## Syntax
 
diff --git a/redis/commands/bitmap/setbit.mdx b/redis/commands/bitmap/setbit.mdx
index a3d97c3d8..35403759e 100644
--- a/redis/commands/bitmap/setbit.mdx
+++ b/redis/commands/bitmap/setbit.mdx
@@ -3,7 +3,11 @@ title: "SETBIT"
 description: "Set or clear the bit at offset."
 ---
 
-Use `SETBIT` to set or clear the bit at offset.
+Use `SETBIT` to set a single bit of the string stored at a key to `0` or `1`.
+
+The offset is counted in bits from the start of the value and the reply is the bit's previous value. If the key does not exist, or the offset lies past the end of the current value, the string is first extended with zero bits, so writing to a large offset allocates every byte up to it. Keep offsets dense, for example by mapping each user to a small sequential id.
+
+Bitmaps built this way are read back with [`GETBIT`](/redis/commands/bitmap/getbit), counted with [`BITCOUNT`](/redis/commands/bitmap/bitcount), and combined with [`BITOP`](/redis/commands/bitmap/bitop).
 
 ## Syntax
 
diff --git a/redis/commands/connection/auth.mdx b/redis/commands/connection/auth.mdx
index 3f5703501..ed87cd029 100644
--- a/redis/commands/connection/auth.mdx
+++ b/redis/commands/connection/auth.mdx
@@ -3,7 +3,9 @@ title: "AUTH"
 description: "Authenticate to the server."
 ---
 
-Use `AUTH` to authenticate to the server.
+Use `AUTH` to authenticate the current connection, with a password alone or with a username and password when ACL users are configured.
+
+Until the connection is authenticated the server rejects other commands with an error. Client libraries usually send `AUTH` for you as part of connecting when the credentials are part of the connection string, so applications rarely call it directly. The password is sent to the server on every connection, which is why Upstash endpoints use TLS.
 
 ## Syntax
 
diff --git a/redis/commands/connection/client-getname.mdx b/redis/commands/connection/client-getname.mdx
index 32e97c21e..bf8ed590b 100644
--- a/redis/commands/connection/client-getname.mdx
+++ b/redis/commands/connection/client-getname.mdx
@@ -3,7 +3,9 @@ title: "CLIENT GETNAME"
 description: "Get the current connection name."
 ---
 
-Use `CLIENT GETNAME` to get the current connection name.
+Use `CLIENT GETNAME` to read the name assigned to the current connection with [`CLIENT SETNAME`](/redis/commands/connection/client-setname).
+
+Connections start without a name and the reply is null until one is set. The name belongs to a single connection and is lost when it closes; it exists to make connections recognizable in [`CLIENT LIST`](/redis/commands/connection/client-list) output when you are debugging which part of an application is doing what.
 
 ## Syntax
 
diff --git a/redis/commands/connection/client-id.mdx b/redis/commands/connection/client-id.mdx
index 11ea63524..ffa89adcc 100644
--- a/redis/commands/connection/client-id.mdx
+++ b/redis/commands/connection/client-id.mdx
@@ -3,7 +3,9 @@ title: "CLIENT ID"
 description: "Get the current client ID."
 ---
 
-Use `CLIENT ID` to get the current client ID.
+Use `CLIENT ID` to get the unique identifier the server assigned to the current connection.
+
+IDs are integers that never repeat and always increase, so a larger ID means a connection that was established later. The ID identifies this connection in [`CLIENT LIST`](/redis/commands/connection/client-list) output, which makes it useful when correlating application logs with server-side connection state.
 
 ## Syntax
 
diff --git a/redis/commands/connection/client-info.mdx b/redis/commands/connection/client-info.mdx
index a180fed2e..61f71bc35 100644
--- a/redis/commands/connection/client-info.mdx
+++ b/redis/commands/connection/client-info.mdx
@@ -3,7 +3,9 @@ title: "CLIENT INFO"
 description: "Get info about current connection."
 ---
 
-Use `CLIENT INFO` to get info about current connection.
+Use `CLIENT INFO` to get a line of statistics about the connection issuing the command.
+
+The reply is a single line of space-separated `field=value` pairs describing the connection: its id, name, address, age, idle time, the number of commands it has run, and the last command it executed. It reports the same fields as one line of [`CLIENT LIST`](/redis/commands/connection/client-list), limited to your own connection, which makes it a cheap way to confirm what the server thinks of the connection you are on. Parse it defensively, since fields can be added over time.
 
 ## Syntax
 
diff --git a/redis/commands/connection/client-list.mdx b/redis/commands/connection/client-list.mdx
index de5274532..5c0468dee 100644
--- a/redis/commands/connection/client-list.mdx
+++ b/redis/commands/connection/client-list.mdx
@@ -3,7 +3,9 @@ title: "CLIENT LIST"
 description: "List all client connections."
 ---
 
-Use `CLIENT LIST` to list all client connections.
+Use `CLIENT LIST` to get one line of statistics for every client connection to the server.
+
+Each line holds space-separated `field=value` pairs with the connection's id, name, address, age, idle time, protocol version, and last command, so the reply gives a snapshot of who is connected and what they are doing. It is the usual starting point for tracking down connection leaks and idle connections. The reply grows with the number of clients, so avoid calling it on a hot path, and parse it defensively because fields can be added over time.
 
 ## Syntax
 
diff --git a/redis/commands/connection/client-setinfo.mdx b/redis/commands/connection/client-setinfo.mdx
index 4bad31206..ea01b3a28 100644
--- a/redis/commands/connection/client-setinfo.mdx
+++ b/redis/commands/connection/client-setinfo.mdx
@@ -3,7 +3,9 @@ title: "CLIENT SETINFO"
 description: "Set client connection attributes."
 ---
 
-Use `CLIENT SETINFO` to set client connection attributes.
+Use `CLIENT SETINFO` to attach library identification to the current connection.
+
+`LIB-NAME` records the name of the client library and `LIB-VER` its version. Both values then appear in [`CLIENT INFO`](/redis/commands/connection/client-info) and [`CLIENT LIST`](/redis/commands/connection/client-list) output, which makes it possible to tell which application or SDK version owns a connection. Most client libraries send this during the handshake, so applications rarely call it themselves.
 
 ## Syntax
 
diff --git a/redis/commands/connection/client-setname.mdx b/redis/commands/connection/client-setname.mdx
index 8b185018e..a2af4780c 100644
--- a/redis/commands/connection/client-setname.mdx
+++ b/redis/commands/connection/client-setname.mdx
@@ -3,7 +3,9 @@ title: "CLIENT SETNAME"
 description: "Set the connection name."
 ---
 
-Use `CLIENT SETNAME` to set the connection name.
+Use `CLIENT SETNAME` to label the current connection with a name of your choice.
+
+The name shows up in [`CLIENT LIST`](/redis/commands/connection/client-list) and [`CLIENT INFO`](/redis/commands/connection/client-info) output, which is handy when several components of an application share one database and you want to tell their connections apart. The name may not contain spaces or newlines, each call replaces the previous name, and passing an empty string clears it. It lives only as long as the connection.
 
 ## Syntax
 
diff --git a/redis/commands/connection/echo.mdx b/redis/commands/connection/echo.mdx
index 2e417157b..6b53a8f77 100644
--- a/redis/commands/connection/echo.mdx
+++ b/redis/commands/connection/echo.mdx
@@ -3,7 +3,9 @@ title: "ECHO"
 description: "Echo the given string."
 ---
 
-Use `ECHO` to echo the given string.
+Use `ECHO` to have the server send the given message back unchanged.
+
+The command performs no work beyond the round trip, which makes it a simple way to verify that a connection is alive and that values survive the client library's encoding and decoding. For plain liveness checks [`PING`](/redis/commands/connection/ping) is the more common choice.
 
 ## Syntax
 
diff --git a/redis/commands/connection/hello.mdx b/redis/commands/connection/hello.mdx
index bda81e58a..2fa28b0e0 100644
--- a/redis/commands/connection/hello.mdx
+++ b/redis/commands/connection/hello.mdx
@@ -3,7 +3,11 @@ title: "HELLO"
 description: "Handshake with Redis protocol."
 ---
 
-Use `HELLO` to handshake with Redis protocol.
+Use `HELLO` to negotiate the protocol version of the connection and read the server handshake information.
+
+Passing `<protover>` switches the connection to RESP2 or RESP3. RESP3 adds native map, set, double, and push replies, so commands such as [`HGETALL`](/redis/commands/hash/hgetall) or [`CONFIG GET`](/redis/commands/server/config-get) come back as maps instead of flat arrays, and pub/sub messages arrive as push replies that do not block ordinary commands. `AUTH` authenticates in the same call and `SETNAME` names the connection, which lets a client complete its handshake in one round trip.
+
+Called without arguments, `HELLO` only reports the server version, the protocol in use, the connection id, and the current role, leaving the protocol unchanged.
 
 ## Syntax
 
diff --git a/redis/commands/connection/ping.mdx b/redis/commands/connection/ping.mdx
index f36ea01ba..9fe78e2b5 100644
--- a/redis/commands/connection/ping.mdx
+++ b/redis/commands/connection/ping.mdx
@@ -3,7 +3,9 @@ title: "PING"
 description: "Ping the server."
 ---
 
-Use `PING` to ping the server.
+Use `PING` to check that the connection and the server are alive.
+
+Without arguments the server replies `PONG`. With a message it echoes that message back instead, which lets a client match a reply to the exact request that produced it. `PING` is the standard health check for a connection pool, both to test a connection before handing it out and to keep an otherwise idle connection from being closed by intermediate proxies. It also works while the connection is subscribed to channels, where it doubles as a keepalive.
 
 ## Syntax
 
diff --git a/redis/commands/connection/quit.mdx b/redis/commands/connection/quit.mdx
index 4dd30581b..9f1654123 100644
--- a/redis/commands/connection/quit.mdx
+++ b/redis/commands/connection/quit.mdx
@@ -3,7 +3,9 @@ title: "QUIT"
 description: "Close the connection."
 ---
 
-Use `QUIT` to close the connection.
+Use `QUIT` to ask the server to close the connection once all pending replies have been sent.
+
+The server replies `OK` and then terminates the connection, so no reply is lost and the shutdown is clean from both sides. Modern clients usually just close the socket, and pooled connections should be returned to the pool rather than closed, so `QUIT` is mostly useful in scripts and interactive sessions.
 
 ## Syntax
 
diff --git a/redis/commands/connection/reset.mdx b/redis/commands/connection/reset.mdx
index 17f351773..42e66edba 100644
--- a/redis/commands/connection/reset.mdx
+++ b/redis/commands/connection/reset.mdx
@@ -3,7 +3,9 @@ title: "RESET"
 description: "Reset the connection."
 ---
 
-Use `RESET` to reset the connection.
+Use `RESET` to return the connection to the state it had right after connecting.
+
+It discards an open [`MULTI`](/redis/commands/transactions/multi) block, unwatches every key watched with [`WATCH`](/redis/commands/transactions/watch), leaves subscriber and monitor modes, clears the connection name, re-enables replies, and de-authenticates the connection when the database requires a password. This makes it the safe way to hand a connection back to a pool after an error, since the next user cannot inherit a half-finished transaction or a leftover subscription.
 
 ## Syntax
 
diff --git a/redis/commands/connection/select.mdx b/redis/commands/connection/select.mdx
index b442bc6a1..a9326418e 100644
--- a/redis/commands/connection/select.mdx
+++ b/redis/commands/connection/select.mdx
@@ -3,7 +3,9 @@ title: "SELECT"
 description: "Select the database by index."
 ---
 
-Use `SELECT` to select the database by index.
+Use `SELECT` to switch the connection to another database index.
+
+Upstash exposes a single logical database, so `0` is the only valid index and anything else returns an error. The command is accepted so that clients and frameworks that issue `SELECT 0` while setting up a connection keep working unchanged. To separate concerns inside one database, use key prefixes instead of numbered databases.
 
 ## Syntax
 
diff --git a/redis/commands/functions/fcall-ro.mdx b/redis/commands/functions/fcall-ro.mdx
index 008e0055c..7549ce34d 100644
--- a/redis/commands/functions/fcall-ro.mdx
+++ b/redis/commands/functions/fcall-ro.mdx
@@ -3,7 +3,11 @@ title: "FCALL_RO"
 description: "Call a read-only function."
 ---
 
-Use `FCALL_RO` to call a read-only function.
+Use `FCALL_RO` to invoke a function that is declared read-only.
+
+The function must have been registered with the `no-writes` flag; calling a function without it returns an error. In exchange the server knows the call cannot modify data, so it can serve it on replicas and reject accidental writes outright.
+
+Apart from that restriction it behaves like [`FCALL`](/redis/commands/functions/fcall): `<numkeys>` splits the arguments into the keys the function receives in `KEYS` and the plain arguments it receives in `ARGV`.
 
 ## Syntax
 
diff --git a/redis/commands/functions/fcall.mdx b/redis/commands/functions/fcall.mdx
index 8b38b129c..7991df407 100644
--- a/redis/commands/functions/fcall.mdx
+++ b/redis/commands/functions/fcall.mdx
@@ -3,7 +3,11 @@ title: "FCALL"
 description: "Call a function."
 ---
 
-Use `FCALL` to call a function.
+Use `FCALL` to invoke a function from a library loaded with [`FUNCTION LOAD`](/redis/commands/functions/function-load).
+
+`<numkeys>` tells the server how many of the arguments that follow are key names. Those keys reach the function in `KEYS` and every remaining argument in `ARGV`. Passing key names as keys instead of hardcoding them in the function body matters, because Redis uses that list for routing and access checks.
+
+The function runs on the server as a single atomic step, so a sequence of reads and writes that would otherwise need several round trips and a transaction becomes one command. Use [`FCALL_RO`](/redis/commands/functions/fcall-ro) when the function only reads. Functions are the successor to [`EVAL`](/redis/commands/scripting/eval) scripts: they are named, registered once as part of a library, and persisted with the dataset instead of being sent or looked up by digest on every call.
 
 ## Syntax
 
diff --git a/redis/commands/functions/function-delete.mdx b/redis/commands/functions/function-delete.mdx
index 60b8938b5..7beabcd92 100644
--- a/redis/commands/functions/function-delete.mdx
+++ b/redis/commands/functions/function-delete.mdx
@@ -3,7 +3,9 @@ title: "FUNCTION DELETE"
 description: "Delete a library."
 ---
 
-Use `FUNCTION DELETE` to delete a library.
+Use `FUNCTION DELETE` to remove a function library and every function it registered.
+
+The argument is the library name declared when the library was loaded, not the name of a single function, and there is no way to delete one function from a library: reload the library with `REPLACE` instead. Deleting a library that does not exist returns an error, and calls to its functions fail until the library is loaded again.
 
 ## Syntax
 
diff --git a/redis/commands/functions/function-flush.mdx b/redis/commands/functions/function-flush.mdx
index c772e84f9..018858890 100644
--- a/redis/commands/functions/function-flush.mdx
+++ b/redis/commands/functions/function-flush.mdx
@@ -3,7 +3,9 @@ title: "FUNCTION FLUSH"
 description: "Delete all libraries."
 ---
 
-Use `FUNCTION FLUSH` to delete all libraries.
+Use `FUNCTION FLUSH` to remove every function library from the database.
+
+This wipes all registered libraries and functions at once and cannot be undone, so it belongs in test setup and provisioning tooling rather than application code. `ASYNC` reclaims the memory in the background and `SYNC` reclaims it before the reply is sent.
 
 ## Syntax
 
diff --git a/redis/commands/functions/function-kill.mdx b/redis/commands/functions/function-kill.mdx
index b788c9911..498d324c0 100644
--- a/redis/commands/functions/function-kill.mdx
+++ b/redis/commands/functions/function-kill.mdx
@@ -3,7 +3,11 @@ title: "FUNCTION KILL"
 description: "Kill a running function."
 ---
 
-Use `FUNCTION KILL` to kill a running function.
+Use `FUNCTION KILL` to stop a function that is currently running and has not yet written anything.
+
+A function that has already modified data cannot be killed, because stopping it halfway would leave the dataset in a state that no atomic step could produce. Check [`FUNCTION STATS`](/redis/commands/functions/function-stats) to see whether a function is running before calling this.
+
+The current Upstash deployment recognizes the command but has no interruptible running-function state to act on, so it replies with a `NOTBUSY` error.
 
 ## Syntax
 
diff --git a/redis/commands/functions/function-list.mdx b/redis/commands/functions/function-list.mdx
index b094ddd50..e565076de 100644
--- a/redis/commands/functions/function-list.mdx
+++ b/redis/commands/functions/function-list.mdx
@@ -3,7 +3,9 @@ title: "FUNCTION LIST"
 description: "List all libraries."
 ---
 
-Use `FUNCTION LIST` to list all libraries.
+Use `FUNCTION LIST` to inspect the function libraries loaded in the database.
+
+The reply describes each library with its name, the engine it runs on, and the functions it registers, including each function's description and flags such as `no-writes`. `LIBRARYNAME` filters the reply to library names matching a pattern, and `WITHCODE` includes the full source of each library, which is how you recover the code of a library that is deployed but no longer at hand.
 
 ## Syntax
 
diff --git a/redis/commands/functions/function-load.mdx b/redis/commands/functions/function-load.mdx
index 03ddce3b7..81d79d6e4 100644
--- a/redis/commands/functions/function-load.mdx
+++ b/redis/commands/functions/function-load.mdx
@@ -3,7 +3,11 @@ title: "FUNCTION LOAD"
 description: "Load a library."
 ---
 
-Use `FUNCTION LOAD` to load a library.
+Use `FUNCTION LOAD` to register a library of functions in the database.
+
+The payload is the library source code. It must begin with a shebang line naming the engine and the library, such as `#!lua name=mylib`, and register each function with `redis.register_function`, giving it a name, a callback, and optional flags such as `no-writes`. The reply is the library name.
+
+Loading fails when the library name is already in use unless `REPLACE` is given, which is how you deploy a new version of a library. Once loaded, functions are called by name with [`FCALL`](/redis/commands/functions/fcall) or [`FCALL_RO`](/redis/commands/functions/fcall-ro). Unlike scripts cached by [`SCRIPT LOAD`](/redis/commands/scripting/script-load), libraries are part of the dataset, so they survive restarts and do not need to be re-sent by clients.
 
 ## Syntax
 
diff --git a/redis/commands/functions/function-stats.mdx b/redis/commands/functions/function-stats.mdx
index 343565af5..84995db6c 100644
--- a/redis/commands/functions/function-stats.mdx
+++ b/redis/commands/functions/function-stats.mdx
@@ -3,7 +3,9 @@ title: "FUNCTION STATS"
 description: "Get function execution stats."
 ---
 
-Use `FUNCTION STATS` to get function execution stats.
+Use `FUNCTION STATS` to read the current state of the function engine.
+
+The reply reports the function that is running right now, if any, together with how long it has been running and the command that started it, plus per-engine counts of loaded libraries and functions. It is the usual way to check whether a long-running function is in progress before deciding to call [`FUNCTION KILL`](/redis/commands/functions/function-kill).
 
 ## Syntax
 
diff --git a/redis/commands/generic/copy.mdx b/redis/commands/generic/copy.mdx
index b4c14c40e..4a0c7ada6 100644
--- a/redis/commands/generic/copy.mdx
+++ b/redis/commands/generic/copy.mdx
@@ -3,7 +3,11 @@ title: "COPY"
 description: "Copy a key to another key."
 ---
 
-Use `COPY` to copy a key to another key.
+Use `COPY` to copy the value stored at one key to another key.
+
+The destination gets an independent deep copy of the value, so later changes to either key do not affect the other, and the source key's remaining time to live is copied along with it. Any type can be copied.
+
+By default the command does nothing and returns `0` when the destination key already exists; `REPLACE` overwrites it instead. `DB` selects the destination database index, which on Upstash is always `0`.
 
 ## Syntax
 
diff --git a/redis/commands/generic/del.mdx b/redis/commands/generic/del.mdx
index 3609da3e2..a1c2124fa 100644
--- a/redis/commands/generic/del.mdx
+++ b/redis/commands/generic/del.mdx
@@ -3,7 +3,9 @@ title: "DEL"
 description: "Delete one or more keys."
 ---
 
-Use `DEL` to delete one or more keys.
+Use `DEL` to delete one or more keys and the values they hold, whatever their type.
+
+The reply counts only the keys that actually existed, so deleting a key that is already gone is not an error and the count tells you how many were really removed. The memory is freed as part of the command, which for very large collections can take noticeable time; [`UNLINK`](/redis/commands/generic/unlink) removes the keys just as immediately but frees their memory in the background.
 
 ## Syntax
 
diff --git a/redis/commands/generic/dump.mdx b/redis/commands/generic/dump.mdx
index 8b8f57b0c..edbe97881 100644
--- a/redis/commands/generic/dump.mdx
+++ b/redis/commands/generic/dump.mdx
@@ -3,7 +3,11 @@ title: "DUMP"
 description: "Serialize a key's value."
 ---
 
-Use `DUMP` to serialize a key's value.
+Use `DUMP` to serialize the value stored at a key into a portable, Redis-specific binary blob.
+
+The blob carries the value together with a version stamp and a checksum, but not the key name and not its time to live. Feeding it to [`RESTORE`](/redis/commands/generic/restore) recreates the value under any key name, in the same database or in another one, which makes the pair the standard way to move or back up individual keys. A missing key returns null.
+
+The reply is raw binary data, not text: keep it in a byte-safe container and avoid string encodings that would corrupt it.
 
 ## Syntax
 
diff --git a/redis/commands/generic/exists.mdx b/redis/commands/generic/exists.mdx
index 722dd52f1..0f7c2eb56 100644
--- a/redis/commands/generic/exists.mdx
+++ b/redis/commands/generic/exists.mdx
@@ -3,7 +3,9 @@ title: "EXISTS"
 description: "Check if keys exist."
 ---
 
-Use `EXISTS` to check if keys exist.
+Use `EXISTS` to check whether one or more keys exist.
+
+The reply is the number of the given keys that exist, so with a single key it is simply `1` or `0`. A key listed several times is counted each time it is present, which means `EXISTS k k` returns `2` when `k` exists. Checking existence never transfers the value, so it stays cheap even for large values.
 
 ## Syntax
 
diff --git a/redis/commands/generic/expire.mdx b/redis/commands/generic/expire.mdx
index c654249be..361679989 100644
--- a/redis/commands/generic/expire.mdx
+++ b/redis/commands/generic/expire.mdx
@@ -3,7 +3,13 @@ title: "EXPIRE"
 description: "Set a key's TTL in seconds."
 ---
 
-Use `EXPIRE` to set a key's TTL in seconds.
+Use `EXPIRE` to give a key a lifetime in seconds, after which the key is deleted automatically.
+
+Whether the expiration survives later writes depends on the command: replacing the value with [`SET`](/redis/commands/string/set) clears it, while commands that modify a value in place, such as [`INCR`](/redis/commands/string/incr), [`LPUSH`](/redis/commands/list/lpush) or [`HSET`](/redis/commands/hash/hset), leave it untouched. A negative lifetime deletes the key immediately.
+
+The optional condition decides when the new expiration is applied: `NX` only when the key currently has none, `XX` only when it already has one, `GT` only when the new expiration is later than the current one, and `LT` only when it is earlier. Since a key without an expiration counts as living forever, `GT` never adds one and `LT` always does. The reply is `1` when the expiration was set and `0` when the key does not exist or the condition was not met.
+
+Read the remaining lifetime with [`TTL`](/redis/commands/generic/ttl) and remove it again with [`PERSIST`](/redis/commands/generic/persist).
 
 ## Syntax
 
diff --git a/redis/commands/generic/expireat.mdx b/redis/commands/generic/expireat.mdx
index 26b0803f9..0233c1623 100644
--- a/redis/commands/generic/expireat.mdx
+++ b/redis/commands/generic/expireat.mdx
@@ -3,7 +3,11 @@ title: "EXPIREAT"
 description: "Set expiry as Unix timestamp."
 ---
 
-Use `EXPIREAT` to set expiry as Unix timestamp.
+Use `EXPIREAT` to schedule a key for automatic deletion at a fixed point in time, given as a Unix timestamp in seconds.
+
+It behaves exactly like [`EXPIRE`](/redis/commands/generic/expire) except that the deadline is absolute rather than relative, which is what you want when several keys must expire at the same moment, such as the end of an hour or of a billing period. Computing the deadline once and reusing it also avoids the drift that repeated relative expirations introduce. A timestamp in the past deletes the key right away.
+
+The optional condition works as it does for `EXPIRE`: `NX` only when the key has no expiration, `XX` only when it already has one, `GT` only when the new deadline is later than the current one, and `LT` only when it is earlier.
 
 ## Syntax
 
diff --git a/redis/commands/generic/expiretime.mdx b/redis/commands/generic/expiretime.mdx
index 1691087cf..42fdc2304 100644
--- a/redis/commands/generic/expiretime.mdx
+++ b/redis/commands/generic/expiretime.mdx
@@ -3,7 +3,9 @@ title: "EXPIRETIME"
 description: "Get expiry as Unix timestamp."
 ---
 
-Use `EXPIRETIME` to get expiry as Unix timestamp.
+Use `EXPIRETIME` to read the absolute time at which a key will expire, as a Unix timestamp in seconds.
+
+The reply is `-1` when the key exists but has no expiration, and `-2` when the key does not exist, so the two cases can be told apart. Use [`TTL`](/redis/commands/generic/ttl) when you need the remaining lifetime instead of the deadline, and [`PEXPIRETIME`](/redis/commands/generic/pexpiretime) when you need millisecond precision.
 
 ## Syntax
 
diff --git a/redis/commands/generic/keys.mdx b/redis/commands/generic/keys.mdx
index f7c47d9ba..895526580 100644
--- a/redis/commands/generic/keys.mdx
+++ b/redis/commands/generic/keys.mdx
@@ -3,7 +3,11 @@ title: "KEYS"
 description: "Find keys matching a pattern."
 ---
 
-Use `KEYS` to find keys matching a pattern.
+Use `KEYS` to list every key in the database whose name matches a glob-style pattern.
+
+The pattern supports `*` for any sequence of characters, `?` for a single character, `[...]` for character classes, and `\` to escape a literal, so `user:*:session` matches all session keys of all users and `*` matches everything.
+
+The command walks the entire keyspace and returns all matches in one reply, which on a database of any real size means a long block and a very large response. Treat it as a debugging and maintenance tool: on hot paths use [`SCAN`](/redis/commands/generic/scan), which accepts the same `MATCH` patterns but walks the keyspace in small batches, or keep an index of your keys in a set instead.
 
 ## Syntax
 
diff --git a/redis/commands/generic/memory-usage.mdx b/redis/commands/generic/memory-usage.mdx
index d5977a0c1..6cdfbf02b 100644
--- a/redis/commands/generic/memory-usage.mdx
+++ b/redis/commands/generic/memory-usage.mdx
@@ -3,7 +3,11 @@ title: "MEMORY USAGE"
 description: "Estimate memory used by a key."
 ---
 
-Use `MEMORY USAGE` to estimate memory used by a key.
+Use `MEMORY USAGE` to estimate how many bytes a key and its value occupy in memory.
+
+The figure covers the stored data along with its internal overhead, so it is larger than the raw size of the value and is meant for comparing keys rather than for exact accounting. For aggregate types such as hashes, lists, sets, sorted sets, and streams the value is sampled instead of fully traversed: `SAMPLES` sets how many nested elements are inspected, and the value is clamped to the range this deployment supports, so it tunes the estimate rather than forcing an exact traversal. A missing key returns null.
+
+It is the usual way to find out which keys are responsible for memory growth before deciding what to trim or restructure.
 
 ## Syntax
 
diff --git a/redis/commands/generic/persist.mdx b/redis/commands/generic/persist.mdx
index aa336279b..dd0ed96f7 100644
--- a/redis/commands/generic/persist.mdx
+++ b/redis/commands/generic/persist.mdx
@@ -3,7 +3,9 @@ title: "PERSIST"
 description: "Remove the expiration from a key."
 ---
 
-Use `PERSIST` to remove the expiration from a key.
+Use `PERSIST` to remove the expiration from a key so that it stops being deleted automatically and lives until it is removed explicitly.
+
+The reply is `1` when an expiration was removed and `0` when the key does not exist or had no expiration to begin with. This is how a value gets promoted from temporary to permanent without rewriting it, for example when a trial record becomes a persistent one.
 
 ## Syntax
 
diff --git a/redis/commands/generic/pexpire.mdx b/redis/commands/generic/pexpire.mdx
index 0aa4f0543..820c3489e 100644
--- a/redis/commands/generic/pexpire.mdx
+++ b/redis/commands/generic/pexpire.mdx
@@ -3,7 +3,11 @@ title: "PEXPIRE"
 description: "Set a key's TTL in milliseconds."
 ---
 
-Use `PEXPIRE` to set a key's TTL in milliseconds.
+Use `PEXPIRE` to give a key a lifetime in milliseconds, after which the key is deleted automatically.
+
+It is the millisecond form of [`EXPIRE`](/redis/commands/generic/expire) and behaves identically otherwise: replacing the value with [`SET`](/redis/commands/string/set) clears the expiration, while in-place updates keep it, and a negative lifetime deletes the key immediately. The sub-second precision matters for short-lived keys such as locks and rate limit windows.
+
+The optional condition decides when the new expiration is applied: `NX` only when the key has none, `XX` only when it already has one, `GT` only when the new expiration is later than the current one, and `LT` only when it is earlier.
 
 ## Syntax
 
diff --git a/redis/commands/generic/pexpireat.mdx b/redis/commands/generic/pexpireat.mdx
index de9f09e89..4dd2a87b3 100644
--- a/redis/commands/generic/pexpireat.mdx
+++ b/redis/commands/generic/pexpireat.mdx
@@ -3,7 +3,11 @@ title: "PEXPIREAT"
 description: "Set expiry as Unix ms timestamp."
 ---
 
-Use `PEXPIREAT` to set expiry as Unix ms timestamp.
+Use `PEXPIREAT` to schedule a key for automatic deletion at a fixed point in time, given as a Unix timestamp in milliseconds.
+
+It combines the absolute deadline of [`EXPIREAT`](/redis/commands/generic/expireat) with the millisecond precision of [`PEXPIRE`](/redis/commands/generic/pexpire), which is what you need when many keys must expire at exactly the same instant. A timestamp in the past deletes the key right away.
+
+The optional condition works as elsewhere: `NX` only when the key has no expiration, `XX` only when it already has one, `GT` only when the new deadline is later than the current one, and `LT` only when it is earlier.
 
 ## Syntax
 
diff --git a/redis/commands/generic/pexpiretime.mdx b/redis/commands/generic/pexpiretime.mdx
index 95a0cfc21..2a60fc354 100644
--- a/redis/commands/generic/pexpiretime.mdx
+++ b/redis/commands/generic/pexpiretime.mdx
@@ -3,7 +3,9 @@ title: "PEXPIRETIME"
 description: "Get expiry as Unix ms timestamp."
 ---
 
-Use `PEXPIRETIME` to get expiry as Unix ms timestamp.
+Use `PEXPIRETIME` to read the absolute time at which a key will expire, as a Unix timestamp in milliseconds.
+
+The reply is `-1` when the key exists but has no expiration and `-2` when the key does not exist. It is the millisecond form of [`EXPIRETIME`](/redis/commands/generic/expiretime), and it reports a deadline rather than a remaining lifetime, which makes it the value to compare against a clock when you need to know exactly when something is due.
 
 ## Syntax
 
diff --git a/redis/commands/generic/pttl.mdx b/redis/commands/generic/pttl.mdx
index 4db46d05c..73ce6b954 100644
--- a/redis/commands/generic/pttl.mdx
+++ b/redis/commands/generic/pttl.mdx
@@ -3,7 +3,9 @@ title: "PTTL"
 description: "Get TTL in milliseconds."
 ---
 
-Use `PTTL` to get TTL in milliseconds.
+Use `PTTL` to read how much longer a key will live, in milliseconds.
+
+The reply is `-1` when the key exists but has no expiration and `-2` when the key does not exist, so a missing key and a permanent one are easy to tell apart. It is the millisecond form of [`TTL`](/redis/commands/generic/ttl), and the extra precision matters for short-lived keys such as locks, where rounding to whole seconds hides most of the remaining lifetime.
 
 ## Syntax
 
diff --git a/redis/commands/generic/randomkey.mdx b/redis/commands/generic/randomkey.mdx
index 36f87cd68..ee68486fc 100644
--- a/redis/commands/generic/randomkey.mdx
+++ b/redis/commands/generic/randomkey.mdx
@@ -3,7 +3,9 @@ title: "RANDOMKEY"
 description: "Return a random key."
 ---
 
-Use `RANDOMKEY` to return a random key.
+Use `RANDOMKEY` to get the name of a random key from the database without reading its value.
+
+The reply is null when the database is empty. Keys are picked by sampling the keyspace rather than by drawing uniformly from it, and nothing prevents the same key from coming up repeatedly, so treat it as a way to look at a sample of your data while debugging rather than as a way to iterate over it. Use [`SCAN`](/redis/commands/generic/scan) when you need to cover every key.
 
 ## Syntax
 
diff --git a/redis/commands/generic/rename.mdx b/redis/commands/generic/rename.mdx
index c262ff19b..4a6a6a8db 100644
--- a/redis/commands/generic/rename.mdx
+++ b/redis/commands/generic/rename.mdx
@@ -3,7 +3,11 @@ title: "RENAME"
 description: "Rename a key."
 ---
 
-Use `RENAME` to rename a key.
+Use `RENAME` to give an existing key a new name.
+
+The value moves with the key and so does its remaining time to live, and the operation is atomic, so no client ever sees both names or neither. If a key with the destination name already exists it is overwritten and its old value is deleted. Renaming a key that does not exist returns an error.
+
+Use [`RENAMENX`](/redis/commands/generic/renamenx) when the destination must not be overwritten. A common pattern is to build a replacement value under a temporary key and then rename it over the live key, which swaps the data in one atomic step.
 
 ## Syntax
 
diff --git a/redis/commands/generic/renamenx.mdx b/redis/commands/generic/renamenx.mdx
index a063c6ac8..5c3f96bf5 100644
--- a/redis/commands/generic/renamenx.mdx
+++ b/redis/commands/generic/renamenx.mdx
@@ -3,7 +3,9 @@ title: "RENAMENX"
 description: "Rename a key if new key doesn't exist."
 ---
 
-Use `RENAMENX` to rename a key if new key doesn't exist.
+Use `RENAMENX` to rename a key only when the new name is not already in use.
+
+The reply is `1` when the rename happened and `0` when the destination already existed and nothing was changed; renaming a key that does not exist returns an error. Because the check and the rename are one atomic step, the command can serve as a way to claim a name: only one of several clients trying to rename onto the same destination succeeds.
 
 ## Syntax
 
diff --git a/redis/commands/generic/restore.mdx b/redis/commands/generic/restore.mdx
index 43ac3ece4..dcc8c5e4d 100644
--- a/redis/commands/generic/restore.mdx
+++ b/redis/commands/generic/restore.mdx
@@ -3,7 +3,11 @@ title: "RESTORE"
 description: "Deserialize and restore a key."
 ---
 
-Use `RESTORE` to deserialize and restore a key.
+Use `RESTORE` to recreate a key from a payload produced by [`DUMP`](/redis/commands/generic/dump).
+
+`<ttl>` gives the new key a lifetime in milliseconds, where `0` means no expiration; with `ABSTTL` the same number is read as an absolute Unix timestamp in milliseconds instead. The command fails if the key already exists unless `REPLACE` is given.
+
+The payload's version stamp and checksum are verified before anything is written, so a truncated, corrupted, or foreign payload is rejected rather than loaded. `IDLETIME` and `FREQ` seed the eviction metadata of the new key so that a restored key does not automatically look freshly used.
 
 ## Syntax
 
diff --git a/redis/commands/generic/scan.mdx b/redis/commands/generic/scan.mdx
index f0c8a5757..b95977312 100644
--- a/redis/commands/generic/scan.mdx
+++ b/redis/commands/generic/scan.mdx
@@ -3,7 +3,13 @@ title: "SCAN"
 description: "Incrementally iterate keys."
 ---
 
-Use `SCAN` to incrementally iterate keys.
+Use `SCAN` to walk through the keys of the database incrementally, a batch at a time.
+
+Each call takes a cursor and returns the next cursor together with a batch of keys. Start with cursor `0` and keep calling with the cursor from the previous reply until the server returns `0` again, which marks the end of the iteration. Because the work is split over many short calls, `SCAN` never blocks the server the way [`KEYS`](/redis/commands/generic/keys) can on a large keyspace.
+
+`MATCH` filters the returned keys with a glob-style pattern, `COUNT` hints at how much work each call should do (a hint about effort, not a page size, so batches vary in length), and `TYPE` limits the reply to keys of one type. Filtering is applied after a batch has been read, so a call can legitimately return no keys at all while the cursor is still non-zero: only the cursor tells you when the iteration is over.
+
+The guarantee is that every key present for the whole iteration is returned at least once. Keys added or removed while the scan runs may or may not show up, and a key can be returned more than once, so make the processing of each key idempotent. [`HSCAN`](/redis/commands/hash/hscan), [`SSCAN`](/redis/commands/set/sscan), and [`ZSCAN`](/redis/commands/sorted-set/zscan) apply the same mechanism inside a single collection.
 
 ## Syntax
 
diff --git a/redis/commands/generic/touch.mdx b/redis/commands/generic/touch.mdx
index 54efe07ba..d059a9cde 100644
--- a/redis/commands/generic/touch.mdx
+++ b/redis/commands/generic/touch.mdx
@@ -3,7 +3,9 @@ title: "TOUCH"
 description: "Update last access time of keys."
 ---
 
-Use `TOUCH` to update last access time of keys.
+Use `TOUCH` to update the last access time of one or more keys without reading their values.
+
+The reply counts how many of the given keys exist, just like [`EXISTS`](/redis/commands/generic/exists), but the call also refreshes the idle time and access frequency that the LRU and LFU eviction policies rely on. That makes it a way to tell the server that a key is still in use, for example to keep a cached value from being evicted while a slower process is still going to need it. It does not change the key's expiration.
 
 ## Syntax
 
diff --git a/redis/commands/generic/ttl.mdx b/redis/commands/generic/ttl.mdx
index d99a05e18..2a7a37d27 100644
--- a/redis/commands/generic/ttl.mdx
+++ b/redis/commands/generic/ttl.mdx
@@ -3,7 +3,9 @@ title: "TTL"
 description: "Get TTL in seconds."
 ---
 
-Use `TTL` to get TTL in seconds.
+Use `TTL` to read how much longer a key will live, in seconds.
+
+The reply is `-1` when the key exists but has no expiration and `-2` when the key does not exist, so these two are never confused with a real remaining lifetime. Values are rounded to whole seconds; use [`PTTL`](/redis/commands/generic/pttl) for millisecond precision and [`EXPIRETIME`](/redis/commands/generic/expiretime) when you want the absolute deadline rather than the time left.
 
 ## Syntax
 
diff --git a/redis/commands/generic/type.mdx b/redis/commands/generic/type.mdx
index a97d0580c..7ed14e2c9 100644
--- a/redis/commands/generic/type.mdx
+++ b/redis/commands/generic/type.mdx
@@ -3,7 +3,9 @@ title: "TYPE"
 description: "Get the type of a key."
 ---
 
-Use `TYPE` to get the type of a key.
+Use `TYPE` to find out which data type is stored at a key.
+
+The reply is one of `string`, `list`, `set`, `zset`, `hash`, or `stream`, and `none` when the key does not exist. It is the way to dispatch generic code over keys of mixed types, since applying a command to the wrong type fails with a `WRONGTYPE` error, and the way to inspect unfamiliar data before deciding how to read it.
 
 ## Syntax
 
diff --git a/redis/commands/generic/unlink.mdx b/redis/commands/generic/unlink.mdx
index 6ce84c42e..9940c31db 100644
--- a/redis/commands/generic/unlink.mdx
+++ b/redis/commands/generic/unlink.mdx
@@ -3,7 +3,9 @@ title: "UNLINK"
 description: "Delete keys asynchronously."
 ---
 
-Use `UNLINK` to delete keys asynchronously.
+Use `UNLINK` to delete keys without freeing their memory in the foreground.
+
+The keys are removed from the keyspace immediately, so from a client's point of view they are gone as soon as the command returns, but the memory of large values is reclaimed by a background thread. That makes it a safer alternative to [`DEL`](/redis/commands/generic/del) for collections with many elements, where freeing memory synchronously can block the server for a noticeable time. The reply counts the keys that existed.
 
 ## Syntax
 
diff --git a/redis/commands/generic/wait.mdx b/redis/commands/generic/wait.mdx
index d6932da9a..0268d5552 100644
--- a/redis/commands/generic/wait.mdx
+++ b/redis/commands/generic/wait.mdx
@@ -3,7 +3,13 @@ title: "WAIT"
 description: "Wait for replica acknowledgements."
 ---
 
-Use `WAIT` to wait for replica acknowledgements.
+Use `WAIT` to block until preceding writes have been acknowledged by a number of replicas, or until a timeout expires.
+
+The reply is the number of replicas that acknowledged, which can be lower than `<numreplicas>` when the timeout is reached, so callers must check it instead of assuming success. A timeout of `0` waits indefinitely.
+
+`WAIT` raises the durability you can observe for a write, which is useful right before an action that must not be undone by a failover, such as replying to a payment webhook. It does not make Redis strongly consistent: an acknowledged write can still be lost if the primary and the acknowledging replicas fail together.
+
+On Upstash the command waits for the writes enqueued before it began, including writes made by other connections, which is broader than the per-connection wording used by some Redis clients.
 
 ## Syntax
 
diff --git a/redis/commands/generic/waitaof.mdx b/redis/commands/generic/waitaof.mdx
index 5e8c3b65c..29f60092e 100644
--- a/redis/commands/generic/waitaof.mdx
+++ b/redis/commands/generic/waitaof.mdx
@@ -3,7 +3,11 @@ title: "WAITAOF"
 description: "Wait for local and replica persistence."
 ---
 
-Use `WAITAOF` to wait for local and replica persistence.
+Use `WAITAOF` to block until preceding writes have been persisted to the append-only file locally and on replicas.
+
+`<numlocal>` is how many local acknowledgements to wait for and `<numreplicas>` how many replicas must have persisted the writes. The two-element reply gives the local count first and the replica count second, and either can come back lower than requested when the timeout expires, so both need checking. A timeout of `0` waits indefinitely.
+
+Where [`WAIT`](/redis/commands/generic/wait) confirms only that replicas received a write, `WAITAOF` confirms that it reached persistent storage, which is the stronger guarantee to ask for before acknowledging work that must survive a restart. On Upstash it waits for the writes enqueued before it began, including writes made by other connections.
 
 ## Syntax
 
diff --git a/redis/commands/geo/geoadd.mdx b/redis/commands/geo/geoadd.mdx
index 92a32ac4d..0f4a0447e 100644
--- a/redis/commands/geo/geoadd.mdx
+++ b/redis/commands/geo/geoadd.mdx
@@ -3,7 +3,11 @@ title: "GEOADD"
 description: "Add geospatial items."
 ---
 
-Use `GEOADD` to add geospatial items.
+Use `GEOADD` to add longitude, latitude, and member triples to a geospatial index.
+
+Each position is encoded into a 52-bit geohash and stored as the score of the member in a sorted set, so a geospatial key is an ordinary sorted set and commands such as [`ZREM`](/redis/commands/sorted-set/zrem), [`ZCARD`](/redis/commands/sorted-set/zcard), and [`ZSCAN`](/redis/commands/sorted-set/zscan) work on it. Longitude must be between -180 and 180 and latitude between -85.05112878 and 85.05112878; anything outside those bounds returns an error. Adding a member that is already present moves it to the new position, and the encoding means coordinates read back with [`GEOPOS`](/redis/commands/geo/geopos) are very close to, but not exactly, the ones you stored.
+
+`NX` only adds members that are not there yet, `XX` only updates members that already exist, and `CH` makes the reply count every member that changed rather than only the ones that were added.
 
 ## Syntax
 
diff --git a/redis/commands/geo/geodist.mdx b/redis/commands/geo/geodist.mdx
index ed5b123ab..ced8f9149 100644
--- a/redis/commands/geo/geodist.mdx
+++ b/redis/commands/geo/geodist.mdx
@@ -3,7 +3,9 @@ title: "GEODIST"
 description: "Get distance between two members."
 ---
 
-Use `GEODIST` to get distance between two members.
+Use `GEODIST` to get the distance between two members of a geospatial index.
+
+The unit defaults to meters and can be set to `m`, `km`, `ft`, or `mi`. The distance is a great-circle distance computed from the stored positions assuming the Earth is a sphere, so it carries the small error of the geohash encoding and, of course, says nothing about the distance actually travelled on roads. If either member is missing from the index the reply is null.
 
 ## Syntax
 
@@ -18,7 +20,7 @@ GEODIST <key> <member1> <member2> [m | km | ft | mi]
 | `<key>` | Yes | No | Redis key targeted by the command. |
 | `<member1>` | Yes | No | First member. |
 | `<member2>` | Yes | No | Second member. |
-| `(m \| km \| ft \| mi)` | No | No | Choose one form: `m`; `km`; `ft`; `mi`. |
+| `(m \| km \| ft \| mi)` | No | No | Distance unit: `m` (meters), `km` (kilometers), `ft` (feet), or `mi` (miles). Defaults to `m` when omitted. |
 
 ## Important points
 
diff --git a/redis/commands/geo/geohash.mdx b/redis/commands/geo/geohash.mdx
index 30db2b6fc..0d1d84539 100644
--- a/redis/commands/geo/geohash.mdx
+++ b/redis/commands/geo/geohash.mdx
@@ -3,7 +3,9 @@ title: "GEOHASH"
 description: "Get geohash strings for members."
 ---
 
-Use `GEOHASH` to get geohash strings for members.
+Use `GEOHASH` to get standard Geohash strings for members of a geospatial index.
+
+The reply holds one 11-character string per requested member, in the order requested, with null for members that are not in the index. These are the strings used by geohash.org and by other geospatial tools, which makes the command the right way to export positions or to share them with systems that speak Geohash. They are derived from the stored 52-bit position, so they reflect the same rounding as [`GEOPOS`](/redis/commands/geo/geopos).
 
 ## Syntax
 
diff --git a/redis/commands/geo/geopos.mdx b/redis/commands/geo/geopos.mdx
index 2f1f14db0..fcde1aaa4 100644
--- a/redis/commands/geo/geopos.mdx
+++ b/redis/commands/geo/geopos.mdx
@@ -3,7 +3,9 @@ title: "GEOPOS"
 description: "Get coordinates of members."
 ---
 
-Use `GEOPOS` to get coordinates of members.
+Use `GEOPOS` to get the longitude and latitude of members of a geospatial index.
+
+The reply holds one entry per requested member, in the order requested, each an array with longitude first and latitude second, and null for members that are not in the index. Positions are decoded from the stored geohash, so they are very close to but not bit-for-bit identical with the coordinates originally passed to [`GEOADD`](/redis/commands/geo/geoadd).
 
 ## Syntax
 
diff --git a/redis/commands/geo/georadius-ro.mdx b/redis/commands/geo/georadius-ro.mdx
index 320ced899..9e1add85f 100644
--- a/redis/commands/geo/georadius-ro.mdx
+++ b/redis/commands/geo/georadius-ro.mdx
@@ -3,7 +3,11 @@ title: "GEORADIUS_RO"
 description: "Find members within a radius of a point."
 ---
 
-Use `GEORADIUS_RO` to find members within a radius of a point. It is the read-only form of `GEORADIUS`.
+Use `GEORADIUS_RO` to find members within a radius of a point. It is the read-only form of [`GEORADIUS`](/redis/commands/geo/georadius).
+
+It accepts the same query and the same `WITHCOORD`, `WITHDIST`, `WITHHASH`, `COUNT`, and sorting options, but it has no `STORE` or `STOREDIST` clause, so the server knows the call cannot write and can serve it on replicas and from read-only scripts.
+
+Like `GEORADIUS`, it is deprecated in favor of [`GEOSEARCH`](/redis/commands/geo/geosearch), which is read-only as well and also supports rectangular areas.
 
 ## Syntax
 
@@ -19,12 +23,12 @@ GEORADIUS_RO <key> <longitude> <latitude> <radius> (m | km | ft | mi) [WITHCOORD
 | `<longitude>` | Yes | No | Longitude in degrees, from -180 to 180. |
 | `<latitude>` | Yes | No | Latitude in degrees, from -85.05112878 to 85.05112878. |
 | `<radius>` | Yes | No | Search radius, in the unit given after it. |
-| `(m \| km \| ft \| mi)` | Yes | No | Choose one form: `m`; `km`; `ft`; `mi`. |
+| `(m \| km \| ft \| mi)` | Yes | No | Distance unit: `m` (meters), `km` (kilometers), `ft` (feet), or `mi` (miles). |
 | `WITHCOORD` | No | No | Also return the longitude and latitude of each match. |
 | `WITHDIST` | No | No | Also return the distance from the center, in the requested unit. |
 | `WITHHASH` | No | No | Also return the raw 52-bit geohash score of each match. |
 | `COUNT <count> [ANY]` | No | No | Return at most `<count>` matches. `ANY` returns as soon as enough matches are found, instead of sorting every match first. |
-| `(ASC \| DESC)` | No | No | Choose one form: `ASC`; `DESC`. |
+| `(ASC \| DESC)` | No | No | Sort the matches by distance from the center: `ASC` (nearest first) or `DESC` (farthest first). Unsorted when omitted. |
 
 ## Response
 
diff --git a/redis/commands/geo/georadius.mdx b/redis/commands/geo/georadius.mdx
index e5cae094b..7770e2649 100644
--- a/redis/commands/geo/georadius.mdx
+++ b/redis/commands/geo/georadius.mdx
@@ -1,9 +1,15 @@
 ---
 title: "GEORADIUS"
-description: "Query members within radius."
+description: "Find members within a radius of a point."
 ---
 
-Use `GEORADIUS` to query members within radius.
+Use `GEORADIUS` to find the members of a geospatial index that lie within a given radius of a longitude and latitude point.
+
+By default only member names are returned. `WITHDIST` adds each member's distance from the center in the unit of the query, `WITHCOORD` adds its coordinates, and `WITHHASH` adds its raw 52-bit geohash score. `COUNT` caps the number of results and, combined with `ANY`, lets the server stop as soon as it has enough matches instead of examining the whole area, which is faster but returns an arbitrary subset rather than the nearest ones. `ASC` and `DESC` sort the results by distance from the center.
+
+`STORE` writes the matching members into a sorted set scored by geohash, so the result stays usable as a geospatial index, while `STOREDIST` scores them by their distance from the center, which makes the result easy to page through by proximity.
+
+Redis deprecated `GEORADIUS` in favor of [`GEOSEARCH`](/redis/commands/geo/geosearch) and [`GEOSEARCHSTORE`](/redis/commands/geo/geosearchstore), which do the same work and additionally support rectangular areas. Use [`GEORADIUS_RO`](/redis/commands/geo/georadius-ro) if you want a form that cannot write.
 
 ## Syntax
 
@@ -19,13 +25,13 @@ GEORADIUS <key> <longitude> <latitude> <radius> (m | km | ft | mi) [WITHCOORD] [
 | `<longitude>` | Yes | No | Longitude in degrees, from -180 to 180. |
 | `<latitude>` | Yes | No | Latitude in degrees, from -85.05112878 to 85.05112878. |
 | `<radius>` | Yes | No | Search radius, in the unit given after it. |
-| `(m \| km \| ft \| mi)` | Yes | No | Choose one form: `m`; `km`; `ft`; `mi`. |
+| `(m \| km \| ft \| mi)` | Yes | No | Distance unit: `m` (meters), `km` (kilometers), `ft` (feet), or `mi` (miles). |
 | `WITHCOORD` | No | No | Also return the longitude and latitude of each match. |
 | `WITHDIST` | No | No | Also return the distance from the center, in the requested unit. |
 | `WITHHASH` | No | No | Also return the raw 52-bit geohash score of each match. |
 | `COUNT <count> [ANY]` | No | No | Return at most `<count>` matches. `ANY` returns as soon as enough matches are found, instead of sorting every match first. |
-| `(ASC \| DESC)` | No | No | Choose one form: `ASC`; `DESC`. |
-| `(STORE <storekey> \| STOREDIST <storedistkey>)` | No | No | Choose one form: `STORE`; `STOREDIST`. |
+| `(ASC \| DESC)` | No | No | Sort the matches by distance from the center: `ASC` (nearest first) or `DESC` (farthest first). Unsorted when omitted. |
+| `(STORE <storekey> \| STOREDIST <storedistkey>)` | No | No | Store the matches in a sorted set instead of returning them: `STORE` scores them by geohash, so the destination stays a geospatial index, and `STOREDIST` scores them by their distance from the center. |
 
 ## Response
 
diff --git a/redis/commands/geo/georadiusbymember-ro.mdx b/redis/commands/geo/georadiusbymember-ro.mdx
index e91b21305..152fcff9b 100644
--- a/redis/commands/geo/georadiusbymember-ro.mdx
+++ b/redis/commands/geo/georadiusbymember-ro.mdx
@@ -3,7 +3,11 @@ title: "GEORADIUSBYMEMBER_RO"
 description: "Find members within a radius of another member."
 ---
 
-Use `GEORADIUSBYMEMBER_RO` to find members within a radius of another member. It is the read-only form of `GEORADIUSBYMEMBER`.
+Use `GEORADIUSBYMEMBER_RO` to find members within a radius of another member. It is the read-only form of [`GEORADIUSBYMEMBER`](/redis/commands/geo/georadiusbymember).
+
+The center is the stored position of the given member, which always appears among the matches at distance zero. The command accepts the same `WITHCOORD`, `WITHDIST`, `WITHHASH`, `COUNT`, and sorting options but has no `STORE` or `STOREDIST` clause, so it can be served on replicas and used from read-only scripts.
+
+Like the writable form, it is deprecated in favor of [`GEOSEARCH`](/redis/commands/geo/geosearch) with `FROMMEMBER`.
 
 ## Syntax
 
@@ -18,12 +22,12 @@ GEORADIUSBYMEMBER_RO <key> <member> <radius> (m | km | ft | mi) [WITHCOORD] [WIT
 | `<key>` | Yes | No | Redis key targeted by the command. |
 | `<member>` | Yes | No | Member name. |
 | `<radius>` | Yes | No | Search radius, in the unit given after it. |
-| `(m \| km \| ft \| mi)` | Yes | No | Choose one form: `m`; `km`; `ft`; `mi`. |
+| `(m \| km \| ft \| mi)` | Yes | No | Distance unit: `m` (meters), `km` (kilometers), `ft` (feet), or `mi` (miles). |
 | `WITHCOORD` | No | No | Also return the longitude and latitude of each match. |
 | `WITHDIST` | No | No | Also return the distance from the center, in the requested unit. |
 | `WITHHASH` | No | No | Also return the raw 52-bit geohash score of each match. |
 | `COUNT <count> [ANY]` | No | No | Return at most `<count>` matches. `ANY` returns as soon as enough matches are found, instead of sorting every match first. |
-| `(ASC \| DESC)` | No | No | Choose one form: `ASC`; `DESC`. |
+| `(ASC \| DESC)` | No | No | Sort the matches by distance from the center: `ASC` (nearest first) or `DESC` (farthest first). Unsorted when omitted. |
 
 ## Response
 
diff --git a/redis/commands/geo/georadiusbymember.mdx b/redis/commands/geo/georadiusbymember.mdx
index f2a6990d2..90bb1adfe 100644
--- a/redis/commands/geo/georadiusbymember.mdx
+++ b/redis/commands/geo/georadiusbymember.mdx
@@ -1,9 +1,13 @@
 ---
 title: "GEORADIUSBYMEMBER"
-description: "Radius query centered on member."
+description: "Find members within a radius of another member."
 ---
 
-Use `GEORADIUSBYMEMBER` to radius query centered on member.
+Use `GEORADIUSBYMEMBER` to find the members of a geospatial index that lie within a given radius of another member.
+
+It works exactly like [`GEORADIUS`](/redis/commands/geo/georadius) except that the center is the stored position of a member instead of an explicit coordinate pair, which saves a lookup when the reference point is already in the index (a store, a driver, a landmark). The reference member itself always matches, since its distance from itself is zero, so remember to filter it out or ask for one result more than you need.
+
+The same `WITHCOORD`, `WITHDIST`, `WITHHASH`, `COUNT`, sorting, and `STORE` or `STOREDIST` options apply. Redis deprecated the command in favor of [`GEOSEARCH`](/redis/commands/geo/geosearch) with `FROMMEMBER`.
 
 ## Syntax
 
@@ -18,13 +22,13 @@ GEORADIUSBYMEMBER <key> <member> <radius> (m | km | ft | mi) [WITHCOORD] [WITHDI
 | `<key>` | Yes | No | Redis key targeted by the command. |
 | `<member>` | Yes | No | Member name. |
 | `<radius>` | Yes | No | Search radius, in the unit given after it. |
-| `(m \| km \| ft \| mi)` | Yes | No | Choose one form: `m`; `km`; `ft`; `mi`. |
+| `(m \| km \| ft \| mi)` | Yes | No | Distance unit: `m` (meters), `km` (kilometers), `ft` (feet), or `mi` (miles). |
 | `WITHCOORD` | No | No | Also return the longitude and latitude of each match. |
 | `WITHDIST` | No | No | Also return the distance from the center, in the requested unit. |
 | `WITHHASH` | No | No | Also return the raw 52-bit geohash score of each match. |
 | `COUNT <count> [ANY]` | No | No | Return at most `<count>` matches. `ANY` returns as soon as enough matches are found, instead of sorting every match first. |
-| `(ASC \| DESC)` | No | No | Choose one form: `ASC`; `DESC`. |
-| `(STORE <storekey> \| STOREDIST <storedistkey>)` | No | No | Choose one form: `STORE`; `STOREDIST`. |
+| `(ASC \| DESC)` | No | No | Sort the matches by distance from the center: `ASC` (nearest first) or `DESC` (farthest first). Unsorted when omitted. |
+| `(STORE <storekey> \| STOREDIST <storedistkey>)` | No | No | Store the matches in a sorted set instead of returning them: `STORE` scores them by geohash, so the destination stays a geospatial index, and `STOREDIST` scores them by their distance from the center. |
 
 ## Response
 
diff --git a/redis/commands/geo/geosearch.mdx b/redis/commands/geo/geosearch.mdx
index 514be6a4d..72ce8758c 100644
--- a/redis/commands/geo/geosearch.mdx
+++ b/redis/commands/geo/geosearch.mdx
@@ -3,7 +3,13 @@ title: "GEOSEARCH"
 description: "Search for members in an area."
 ---
 
-Use `GEOSEARCH` to search for members in an area.
+Use `GEOSEARCH` to find the members of a geospatial index that fall inside a circle or a rectangle.
+
+The center is either an existing member of the index (`FROMMEMBER`) or an explicit coordinate pair (`FROMLONLAT`). The area is either a circle of a given radius (`BYRADIUS`) or an axis-aligned box of a given width and height centered on that point (`BYBOX`), which is the shape to use when you are covering a map viewport rather than a "within N km" question.
+
+By default only member names come back. `WITHDIST` adds the distance from the center in the unit of the query, `WITHCOORD` the member's coordinates, and `WITHHASH` its raw geohash score. `ASC` and `DESC` sort by distance, and `COUNT` caps the number of results; adding `ANY` lets the server return as soon as it has enough matches, which is faster but no longer gives you the nearest ones.
+
+`GEOSEARCH` replaces the deprecated `GEORADIUS` and `GEORADIUSBYMEMBER` commands and is the command to use for new code. Use [`GEOSEARCHSTORE`](/redis/commands/geo/geosearchstore) when the result should be stored instead of returned.
 
 ## Syntax
 
@@ -16,9 +22,9 @@ GEOSEARCH <key> (FROMMEMBER <member> | FROMLONLAT <longitude> <latitude>) (BYRAD
 | Argument | Required | Repeatable | Description |
 | --- | --- | --- | --- |
 | `<key>` | Yes | No | Redis key targeted by the command. |
-| `(FROMMEMBER <member> \| FROMLONLAT <longitude> <latitude>)` | Yes | No | Choose one form: `FROMMEMBER`; `FROMLONLAT`. |
-| `(BYRADIUS <radius> (m \| km \| ft \| mi) \| BYBOX <width> <height> (m \| km \| ft \| mi))` | Yes | No | Choose one form: `BYRADIUS`; `m`; `km`; `ft`; `mi`; `BYBOX`; `m`; `km`; `ft`; `mi`. |
-| `(ASC \| DESC)` | No | No | Choose one form: `ASC`; `DESC`. |
+| `(FROMMEMBER <member> \| FROMLONLAT <longitude> <latitude>)` | Yes | No | Where to center the search: `FROMMEMBER` uses the stored position of an existing member, `FROMLONLAT` uses the given coordinates. |
+| `(BYRADIUS <radius> (m \| km \| ft \| mi) \| BYBOX <width> <height> (m \| km \| ft \| mi))` | Yes | No | The area to search: `BYRADIUS` a circle of the given radius, `BYBOX` an axis-aligned box of the given width and height centered on the search point. The unit is `m` (meters), `km` (kilometers), `ft` (feet), or `mi` (miles). |
+| `(ASC \| DESC)` | No | No | Sort the matches by distance from the center: `ASC` (nearest first) or `DESC` (farthest first). Unsorted when omitted. |
 | `COUNT <count> [ANY]` | No | No | Return at most `<count>` matches. `ANY` returns as soon as enough matches are found, instead of sorting every match first. |
 | `WITHCOORD` | No | No | Also return the longitude and latitude of each match. |
 | `WITHDIST` | No | No | Also return the distance from the center, in the requested unit. |
diff --git a/redis/commands/geo/geosearchstore.mdx b/redis/commands/geo/geosearchstore.mdx
index 41230e96e..bbe8898ac 100644
--- a/redis/commands/geo/geosearchstore.mdx
+++ b/redis/commands/geo/geosearchstore.mdx
@@ -3,7 +3,11 @@ title: "GEOSEARCHSTORE"
 description: "Store geosearch results."
 ---
 
-Use `GEOSEARCHSTORE` to store geosearch results.
+Use `GEOSEARCHSTORE` to run the same query as [`GEOSEARCH`](/redis/commands/geo/geosearch) and store the matching members in another key instead of returning them.
+
+The destination is a sorted set holding the matches. By default their scores are the raw geohash values, so the destination is itself a valid geospatial index that can be queried further; with `STOREDIST` the score is the distance from the center in the unit of the query, which turns the result into a proximity-ordered list you can page through with [`ZRANGE`](/redis/commands/sorted-set/zrange).
+
+The destination is overwritten on every call, and it is deleted when the query matches nothing. The reply is the number of members stored. This is the usual way to materialize a "nearby" result once and then reuse it for pagination or further set operations.
 
 ## Syntax
 
@@ -17,9 +21,9 @@ GEOSEARCHSTORE <destination> <source> (FROMMEMBER <member> | FROMLONLAT <longitu
 | --- | --- | --- | --- |
 | `<destination>` | Yes | No | Redis key used as destination. |
 | `<source>` | Yes | No | Redis key used as source. |
-| `(FROMMEMBER <member> \| FROMLONLAT <longitude> <latitude>)` | Yes | No | Choose one form: `FROMMEMBER`; `FROMLONLAT`. |
-| `(BYRADIUS <radius> (m \| km \| ft \| mi) \| BYBOX <width> <height> (m \| km \| ft \| mi))` | Yes | No | Choose one form: `BYRADIUS`; `m`; `km`; `ft`; `mi`; `BYBOX`; `m`; `km`; `ft`; `mi`. |
-| `(ASC \| DESC)` | No | No | Choose one form: `ASC`; `DESC`. |
+| `(FROMMEMBER <member> \| FROMLONLAT <longitude> <latitude>)` | Yes | No | Where to center the search: `FROMMEMBER` uses the stored position of an existing member, `FROMLONLAT` uses the given coordinates. |
+| `(BYRADIUS <radius> (m \| km \| ft \| mi) \| BYBOX <width> <height> (m \| km \| ft \| mi))` | Yes | No | The area to search: `BYRADIUS` a circle of the given radius, `BYBOX` an axis-aligned box of the given width and height centered on the search point. The unit is `m` (meters), `km` (kilometers), `ft` (feet), or `mi` (miles). |
+| `(ASC \| DESC)` | No | No | Sort the matches by distance from the center: `ASC` (nearest first) or `DESC` (farthest first). Unsorted when omitted. |
 | `COUNT <count> [ANY]` | No | No | Return at most `<count>` matches. `ANY` returns as soon as enough matches are found, instead of sorting every match first. |
 | `STOREDIST` | No | No | Store each match's distance from the center instead of its geohash score. |
 
diff --git a/redis/commands/geo/overview.mdx b/redis/commands/geo/overview.mdx
index e1a4b64fc..148444271 100644
--- a/redis/commands/geo/overview.mdx
+++ b/redis/commands/geo/overview.mdx
@@ -9,9 +9,9 @@ description: "Commands for storing and querying geospatial data."
 <Card title="GEODIST" href="/redis/commands/geo/geodist">Get distance between two members</Card>
 <Card title="GEOHASH" href="/redis/commands/geo/geohash">Get geohash strings for members</Card>
 <Card title="GEOPOS" href="/redis/commands/geo/geopos">Get coordinates of members</Card>
-<Card title="GEORADIUS" href="/redis/commands/geo/georadius">Query members within radius</Card>
+<Card title="GEORADIUS" href="/redis/commands/geo/georadius">Find members within a radius of a point</Card>
 <Card title="GEORADIUS_RO" href="/redis/commands/geo/georadius-ro">Read-only radius query</Card>
-<Card title="GEORADIUSBYMEMBER" href="/redis/commands/geo/georadiusbymember">Radius query centered on member</Card>
+<Card title="GEORADIUSBYMEMBER" href="/redis/commands/geo/georadiusbymember">Find members within a radius of another member</Card>
 <Card title="GEORADIUSBYMEMBER_RO" href="/redis/commands/geo/georadiusbymember-ro">Read-only radius query by member</Card>
 <Card title="GEOSEARCH" href="/redis/commands/geo/geosearch">Search for members in an area</Card>
 <Card title="GEOSEARCHSTORE" href="/redis/commands/geo/geosearchstore">Store geosearch results</Card>
diff --git a/redis/commands/hash/hdel.mdx b/redis/commands/hash/hdel.mdx
index c3c148701..a139d4c27 100644
--- a/redis/commands/hash/hdel.mdx
+++ b/redis/commands/hash/hdel.mdx
@@ -3,7 +3,9 @@ title: "HDEL"
 description: "Delete one or more hash fields."
 ---
 
-Use `HDEL` to delete one or more hash fields.
+Use `HDEL` to remove one or more fields from a hash.
+
+The reply counts only the fields that were actually present, so deleting a field that is already gone is not an error. When the last field of a hash is removed the key itself is deleted, because Redis does not keep empty collections.
 
 ## Syntax
 
diff --git a/redis/commands/hash/hexists.mdx b/redis/commands/hash/hexists.mdx
index d09eecd7f..850850b04 100644
--- a/redis/commands/hash/hexists.mdx
+++ b/redis/commands/hash/hexists.mdx
@@ -3,7 +3,9 @@ title: "HEXISTS"
 description: "Check if a hash field exists."
 ---
 
-Use `HEXISTS` to check if a hash field exists.
+Use `HEXISTS` to check whether a field is present in a hash.
+
+The reply is `1` when the field exists and `0` when either the field or the key is missing. Since the value is never transferred, this is the cheap way to test for presence, and it is also how you tell a missing field apart from a field whose value happens to be empty, which [`HGET`](/redis/commands/hash/hget) cannot do.
 
 ## Syntax
 
diff --git a/redis/commands/hash/hexpire.mdx b/redis/commands/hash/hexpire.mdx
index 5b94ee30f..080c94cee 100644
--- a/redis/commands/hash/hexpire.mdx
+++ b/redis/commands/hash/hexpire.mdx
@@ -3,7 +3,13 @@ title: "HEXPIRE"
 description: "Set field TTL in seconds."
 ---
 
-Use `HEXPIRE` to set field TTL in seconds.
+Use `HEXPIRE` to give individual hash fields a lifetime in seconds, after which those fields are removed from the hash.
+
+Expiration here is per field, not per key: the hash itself stays alive as long as it still has fields, and the key is deleted automatically when the last surviving field expires. This makes it possible to keep short-lived and long-lived data in one hash, for example a user record whose verification code expires while the rest of the record stays.
+
+`FIELDS <numfields>` introduces the list of fields and the count must match the number of names that follow. The optional condition works as it does on [`EXPIRE`](/redis/commands/generic/expire): `NX` only when the field has no expiration, `XX` only when it already has one, `GT` only when the new expiration is later than the current one, and `LT` only when it is earlier.
+
+The reply holds one status code per field, in order: `1` when the expiration was set, `0` when the condition prevented it, `2` when the field was deleted immediately because the given lifetime was zero or negative, and `-2` when the field does not exist.
 
 ## Syntax
 
diff --git a/redis/commands/hash/hexpireat.mdx b/redis/commands/hash/hexpireat.mdx
index b4c7ee41d..b5c5100a3 100644
--- a/redis/commands/hash/hexpireat.mdx
+++ b/redis/commands/hash/hexpireat.mdx
@@ -3,7 +3,13 @@ title: "HEXPIREAT"
 description: "Set field expiry as timestamp."
 ---
 
-Use `HEXPIREAT` to set field expiry as timestamp.
+Use `HEXPIREAT` to schedule individual hash fields for deletion at a fixed point in time, given as a Unix timestamp in seconds.
+
+It is the absolute-deadline form of [`HEXPIRE`](/redis/commands/hash/hexpire), which is what you want when several fields, or fields across several hashes, must expire at the same moment. A timestamp in the past removes the fields right away. The key is deleted when its last field expires.
+
+`FIELDS <numfields>` introduces the field list and the count must match. The optional condition applies the deadline only in certain cases: `NX` when the field has no expiration, `XX` when it already has one, `GT` when the new deadline is later than the current one, and `LT` when it is earlier.
+
+The reply holds one status code per field: `1` when the expiration was set, `0` when the condition prevented it, `2` when the field was deleted immediately, and `-2` when the field does not exist.
 
 ## Syntax
 
diff --git a/redis/commands/hash/hexpiretime.mdx b/redis/commands/hash/hexpiretime.mdx
index a49dda5e5..3e2986dd1 100644
--- a/redis/commands/hash/hexpiretime.mdx
+++ b/redis/commands/hash/hexpiretime.mdx
@@ -3,7 +3,9 @@ title: "HEXPIRETIME"
 description: "Get field expiry as timestamp."
 ---
 
-Use `HEXPIRETIME` to get field expiry as timestamp.
+Use `HEXPIRETIME` to read the absolute expiration time of hash fields, as Unix timestamps in seconds.
+
+The reply holds one value per requested field, in order: the timestamp when the field expires, `-1` when the field exists but has no expiration, and `-2` when the field or the key does not exist. Use [`HTTL`](/redis/commands/hash/httl) when you want the remaining lifetime instead of the deadline, and [`HPEXPIRETIME`](/redis/commands/hash/hpexpiretime) for millisecond precision.
 
 ## Syntax
 
diff --git a/redis/commands/hash/hget.mdx b/redis/commands/hash/hget.mdx
index 878a5b3f1..23ead3798 100644
--- a/redis/commands/hash/hget.mdx
+++ b/redis/commands/hash/hget.mdx
@@ -3,7 +3,9 @@ title: "HGET"
 description: "Get the value of a hash field."
 ---
 
-Use `HGET` to get the value of a hash field.
+Use `HGET` to read the value of a single field of a hash.
+
+The reply is null when either the field or the whole key is missing, so the two cases cannot be told apart from the reply alone; use [`HEXISTS`](/redis/commands/hash/hexists) when that difference matters. To read several fields use [`HMGET`](/redis/commands/hash/hmget) rather than repeated calls, and to read all of them use [`HGETALL`](/redis/commands/hash/hgetall).
 
 ## Syntax
 
diff --git a/redis/commands/hash/hgetall.mdx b/redis/commands/hash/hgetall.mdx
index 399421f4b..d61f30d4c 100644
--- a/redis/commands/hash/hgetall.mdx
+++ b/redis/commands/hash/hgetall.mdx
@@ -3,7 +3,11 @@ title: "HGETALL"
 description: "Get all fields and values."
 ---
 
-Use `HGETALL` to get all fields and values.
+Use `HGETALL` to read every field and value of a hash in one call.
+
+The reply pairs each field with its value. RESP2 flattens it into a single alternating array while RESP3 returns a map, and client libraries normally decode either form into a native dictionary. A missing key returns an empty result rather than an error.
+
+The whole hash is transferred, so on hashes with many fields prefer [`HMGET`](/redis/commands/hash/hmget) when you know which fields you need, or [`HSCAN`](/redis/commands/hash/hscan) to walk the hash in batches.
 
 ## Syntax
 
diff --git a/redis/commands/hash/hgetdel.mdx b/redis/commands/hash/hgetdel.mdx
index c6f398f35..acdc944da 100644
--- a/redis/commands/hash/hgetdel.mdx
+++ b/redis/commands/hash/hgetdel.mdx
@@ -3,7 +3,11 @@ title: "HGETDEL"
 description: "Get and delete hash fields."
 ---
 
-Use `HGETDEL` to get and delete hash fields.
+Use `HGETDEL` to read hash fields and delete them in the same atomic step.
+
+The reply holds the previous value of each requested field, in the order requested, with null for fields that were not present. Reading and removing together removes the race that an [`HGET`](/redis/commands/hash/hget) followed by an [`HDEL`](/redis/commands/hash/hdel) would leave open, which makes the command a good fit for one-shot values such as one-time codes, claim tickets, or queued items keyed by name: exactly one caller gets the value.
+
+`FIELDS <numfields>` introduces the field list and the count must match. The key is deleted when its last field is removed.
 
 ## Syntax
 
diff --git a/redis/commands/hash/hgetex.mdx b/redis/commands/hash/hgetex.mdx
index cbf30e21c..6a55a3d1b 100644
--- a/redis/commands/hash/hgetex.mdx
+++ b/redis/commands/hash/hgetex.mdx
@@ -3,7 +3,11 @@ title: "HGETEX"
 description: "Get fields and set their expiry."
 ---
 
-Use `HGETEX` to get fields and set their expiry.
+Use `HGETEX` to read hash fields and change their expiration in the same call.
+
+Without an expiration option it simply returns the values, like [`HMGET`](/redis/commands/hash/hmget). `EX`, `PX`, `EXAT`, and `PXAT` give every requested field a new lifetime or deadline, and `PERSIST` removes the expiration so the fields stop expiring altogether.
+
+Doing both in one command is what makes sliding expirations possible per field: reading a session attribute can extend it, with no window in which another client sees the field without its refreshed lifetime. `FIELDS <numfields>` introduces the field list and the count must match.
 
 ## Syntax
 
@@ -16,7 +20,7 @@ HGETEX <key> [EX <seconds> | PX <milliseconds> | EXAT <unix-time-seconds> | PXAT
 | Argument | Required | Repeatable | Description |
 | --- | --- | --- | --- |
 | `<key>` | Yes | No | Redis key targeted by the command. |
-| `(EX <seconds> \| PX <milliseconds> \| EXAT <unix-time-seconds> \| PXAT <unix-time-milliseconds> \| PERSIST)` | No | No | Choose one form: `EX` (set a lifetime in seconds); `PX` (set a lifetime in milliseconds); `EXAT` (expire at a Unix timestamp in seconds); `PXAT` (expire at a Unix timestamp in milliseconds); `PERSIST`. |
+| `(EX <seconds> \| PX <milliseconds> \| EXAT <unix-time-seconds> \| PXAT <unix-time-milliseconds> \| PERSIST)` | No | No | Choose one form: `EX` (set a lifetime in seconds); `PX` (set a lifetime in milliseconds); `EXAT` (expire at a Unix timestamp in seconds); `PXAT` (expire at a Unix timestamp in milliseconds); `PERSIST` (remove the expiration). Left unchanged when omitted. |
 | `FIELDS <numfields> <field> [<field> ...]` | Yes | No | Fields to target. Give the field count first, then that many field names. |
 
 ## Response
diff --git a/redis/commands/hash/hincrby.mdx b/redis/commands/hash/hincrby.mdx
index 31d0b5241..37eb487b2 100644
--- a/redis/commands/hash/hincrby.mdx
+++ b/redis/commands/hash/hincrby.mdx
@@ -3,7 +3,11 @@ title: "HINCRBY"
 description: "Increment integer value of a field."
 ---
 
-Use `HINCRBY` to increment integer value of a field.
+Use `HINCRBY` to add an integer to the number stored in a hash field and get the result.
+
+A missing field, or a missing key, is treated as `0`, so the first call creates the hash and the field. The increment may be negative to count down. The stored value must be the string form of a 64-bit signed integer; anything else returns an error, as does an operation that would overflow the range.
+
+Reading, adding, and writing back happen as one atomic step, so concurrent callers each receive a distinct result and no update is lost. That makes hashes a compact way to keep many related counters, such as per-status counts for one entity, under a single key.
 
 ## Syntax
 
diff --git a/redis/commands/hash/hincrbyfloat.mdx b/redis/commands/hash/hincrbyfloat.mdx
index 4fdaae54b..ff12110a4 100644
--- a/redis/commands/hash/hincrbyfloat.mdx
+++ b/redis/commands/hash/hincrbyfloat.mdx
@@ -3,7 +3,11 @@ title: "HINCRBYFLOAT"
 description: "Increment float value of a field."
 ---
 
-Use `HINCRBYFLOAT` to increment float value of a field.
+Use `HINCRBYFLOAT` to add a floating point number to the value of a hash field and get the result.
+
+The stored value and the increment are parsed as double precision floats, and a missing field or key counts as `0`. The increment may be negative, and there is no separate decrement command. A value that is not a valid number returns an error.
+
+The reply is the new value as a string, which client libraries usually decode into a native number. Note that the result is stored in the same textual form, so repeated increments of values that cannot be represented exactly in binary floating point accumulate the usual rounding error; keep money and similar quantities in integer units and use [`HINCRBY`](/redis/commands/hash/hincrby).
 
 ## Syntax
 
diff --git a/redis/commands/hash/hkeys.mdx b/redis/commands/hash/hkeys.mdx
index 62be5b473..1bbd689d5 100644
--- a/redis/commands/hash/hkeys.mdx
+++ b/redis/commands/hash/hkeys.mdx
@@ -3,7 +3,9 @@ title: "HKEYS"
 description: "Get all fields in a hash."
 ---
 
-Use `HKEYS` to get all fields in a hash.
+Use `HKEYS` to get the names of all the fields in a hash, without their values.
+
+A missing key returns an empty list. The whole field list is built and transferred in one reply, so on large hashes prefer [`HSCAN`](/redis/commands/hash/hscan) with `NOVALUES`, which walks the field names in batches instead.
 
 ## Syntax
 
diff --git a/redis/commands/hash/hlen.mdx b/redis/commands/hash/hlen.mdx
index a212ef54c..7bb6b2f58 100644
--- a/redis/commands/hash/hlen.mdx
+++ b/redis/commands/hash/hlen.mdx
@@ -3,7 +3,9 @@ title: "HLEN"
 description: "Get number of fields in a hash."
 ---
 
-Use `HLEN` to get number of fields in a hash.
+Use `HLEN` to get the number of fields in a hash.
+
+The reply is `0` when the key does not exist. The count is kept by Redis rather than computed, so it is cheap whatever the size of the hash, which makes it the right way to check how big a hash has grown before deciding to read or iterate it.
 
 ## Syntax
 
diff --git a/redis/commands/hash/hmget.mdx b/redis/commands/hash/hmget.mdx
index 2896d7126..5fef1c4b4 100644
--- a/redis/commands/hash/hmget.mdx
+++ b/redis/commands/hash/hmget.mdx
@@ -3,7 +3,11 @@ title: "HMGET"
 description: "Get values of multiple fields."
 ---
 
-Use `HMGET` to get values of multiple fields.
+Use `HMGET` to read several fields of a hash in one call.
+
+The reply holds one entry per requested field, in the order requested, with null for fields that do not exist. Asking for fields of a key that does not exist returns a list of nulls rather than an error, so the shape of the reply is always predictable and can be zipped back onto your list of field names.
+
+It saves the round trips of repeated [`HGET`](/redis/commands/hash/hget) calls and transfers far less than [`HGETALL`](/redis/commands/hash/hgetall) when you only need a few fields of a large hash.
 
 ## Syntax
 
diff --git a/redis/commands/hash/hmset.mdx b/redis/commands/hash/hmset.mdx
index a03dc7453..1ec1a6c2d 100644
--- a/redis/commands/hash/hmset.mdx
+++ b/redis/commands/hash/hmset.mdx
@@ -3,7 +3,9 @@ title: "HMSET"
 description: "Set multiple hash fields."
 ---
 
-Use `HMSET` to set multiple hash fields.
+Use `HMSET` to set several field and value pairs of a hash in one call, creating the key if it does not exist.
+
+Existing fields are overwritten and the reply is always `OK`, so it says nothing about what changed. `HMSET` is deprecated in Redis: [`HSET`](/redis/commands/hash/hset) accepts multiple pairs as well and additionally reports how many fields were new, so prefer it in new code.
 
 ## Syntax
 
diff --git a/redis/commands/hash/hpersist.mdx b/redis/commands/hash/hpersist.mdx
index 5ee8e3d11..dbc1e1b45 100644
--- a/redis/commands/hash/hpersist.mdx
+++ b/redis/commands/hash/hpersist.mdx
@@ -3,7 +3,11 @@ title: "HPERSIST"
 description: "Remove field expiration."
 ---
 
-Use `HPERSIST` to remove field expiration.
+Use `HPERSIST` to remove the expiration from hash fields so that they stop being deleted automatically.
+
+The reply holds one status code per requested field, in order: `1` when an expiration was removed, `-1` when the field exists but had no expiration, and `-2` when the field or the key does not exist. This is how a field set by [`HEXPIRE`](/redis/commands/hash/hexpire) or [`HSETEX`](/redis/commands/hash/hsetex) is promoted from temporary to permanent without rewriting its value.
+
+`FIELDS <numfields>` introduces the field list and the count must match.
 
 ## Syntax
 
diff --git a/redis/commands/hash/hpexpire.mdx b/redis/commands/hash/hpexpire.mdx
index d248ee7e0..27ef5766d 100644
--- a/redis/commands/hash/hpexpire.mdx
+++ b/redis/commands/hash/hpexpire.mdx
@@ -3,7 +3,11 @@ title: "HPEXPIRE"
 description: "Set field TTL in milliseconds."
 ---
 
-Use `HPEXPIRE` to set field TTL in milliseconds.
+Use `HPEXPIRE` to give individual hash fields a lifetime in milliseconds, after which those fields are removed from the hash.
+
+It is the millisecond form of [`HEXPIRE`](/redis/commands/hash/hexpire) and behaves identically otherwise: expiration is per field, the hash survives as long as it has fields, and the key disappears when the last field expires. The finer precision matters for short-lived fields such as per-field locks or rate limit windows.
+
+`FIELDS <numfields>` introduces the field list and the count must match. The optional condition applies the new lifetime only in certain cases: `NX` when the field has no expiration, `XX` when it already has one, `GT` when the new expiration is later than the current one, and `LT` when it is earlier. The reply holds one status code per field: `1` when set, `0` when the condition prevented it, `2` when the field was deleted immediately, and `-2` when it does not exist.
 
 ## Syntax
 
diff --git a/redis/commands/hash/hpexpireat.mdx b/redis/commands/hash/hpexpireat.mdx
index f1cc73bf9..8637c6f64 100644
--- a/redis/commands/hash/hpexpireat.mdx
+++ b/redis/commands/hash/hpexpireat.mdx
@@ -3,7 +3,11 @@ title: "HPEXPIREAT"
 description: "Set field expiry as ms timestamp."
 ---
 
-Use `HPEXPIREAT` to set field expiry as ms timestamp.
+Use `HPEXPIREAT` to schedule individual hash fields for deletion at a fixed point in time, given as a Unix timestamp in milliseconds.
+
+It combines the absolute deadline of [`HEXPIREAT`](/redis/commands/hash/hexpireat) with millisecond precision, which is what you need when fields spread over several hashes have to expire at exactly the same instant. A timestamp in the past removes the fields right away, and the key is deleted when its last field expires.
+
+`FIELDS <numfields>` introduces the field list and the count must match. The optional condition applies the deadline only when the field has no expiration (`NX`), already has one (`XX`), or when the new deadline is later (`GT`) or earlier (`LT`) than the current one. The reply holds one status code per field: `1` when set, `0` when the condition prevented it, `2` when the field was deleted immediately, and `-2` when it does not exist.
 
 ## Syntax
 
diff --git a/redis/commands/hash/hpexpiretime.mdx b/redis/commands/hash/hpexpiretime.mdx
index 6a33bd761..6583633d8 100644
--- a/redis/commands/hash/hpexpiretime.mdx
+++ b/redis/commands/hash/hpexpiretime.mdx
@@ -3,7 +3,9 @@ title: "HPEXPIRETIME"
 description: "Get field expiry as ms timestamp."
 ---
 
-Use `HPEXPIRETIME` to get field expiry as ms timestamp.
+Use `HPEXPIRETIME` to read the absolute expiration time of hash fields, as Unix timestamps in milliseconds.
+
+The reply holds one value per requested field, in order: the timestamp at which it expires, `-1` when the field exists but has no expiration, and `-2` when the field or the key does not exist. It is the millisecond form of [`HEXPIRETIME`](/redis/commands/hash/hexpiretime) and reports a deadline rather than the time left, which is the value to compare against a clock.
 
 ## Syntax
 
diff --git a/redis/commands/hash/hpttl.mdx b/redis/commands/hash/hpttl.mdx
index e5fe97277..4b5337c3a 100644
--- a/redis/commands/hash/hpttl.mdx
+++ b/redis/commands/hash/hpttl.mdx
@@ -3,7 +3,9 @@ title: "HPTTL"
 description: "Get field TTL in milliseconds."
 ---
 
-Use `HPTTL` to get field TTL in milliseconds.
+Use `HPTTL` to read how much longer hash fields will live, in milliseconds.
+
+The reply holds one value per requested field, in order: the remaining lifetime, `-1` when the field exists but has no expiration, and `-2` when the field or the key does not exist. It is the millisecond form of [`HTTL`](/redis/commands/hash/httl), and the extra precision matters for fields that live for less than a second.
 
 ## Syntax
 
diff --git a/redis/commands/hash/hrandfield.mdx b/redis/commands/hash/hrandfield.mdx
index 406a79257..60a347db1 100644
--- a/redis/commands/hash/hrandfield.mdx
+++ b/redis/commands/hash/hrandfield.mdx
@@ -3,7 +3,11 @@ title: "HRANDFIELD"
 description: "Get random fields from a hash."
 ---
 
-Use `HRANDFIELD` to get random fields from a hash.
+Use `HRANDFIELD` to get one or more random fields from a hash.
+
+Without a count a single field name is returned, or null when the key does not exist. A positive count returns up to that many distinct fields, capped at the size of the hash, while a negative count returns exactly that many fields chosen independently, so the same field can come up more than once. `WITHVALUES` returns each field together with its value.
+
+Nothing is removed from the hash, which is the difference from [`HGETDEL`](/redis/commands/hash/hgetdel): use this for sampling, random selection, and quick inspection of an unfamiliar hash.
 
 ## Syntax
 
diff --git a/redis/commands/hash/hscan.mdx b/redis/commands/hash/hscan.mdx
index 078ea959b..2bbe04bb7 100644
--- a/redis/commands/hash/hscan.mdx
+++ b/redis/commands/hash/hscan.mdx
@@ -3,7 +3,11 @@ title: "HSCAN"
 description: "Incrementally iterate hash fields."
 ---
 
-Use `HSCAN` to incrementally iterate hash fields.
+Use `HSCAN` to iterate the fields of a hash in batches instead of reading it all at once.
+
+Each call takes a cursor and returns the next cursor together with a batch of field and value pairs. Start at cursor `0` and keep calling with the cursor from the previous reply until the server returns `0`, which ends the iteration. Because each call does a bounded amount of work, this avoids the long single reply that [`HGETALL`](/redis/commands/hash/hgetall) produces on a large hash.
+
+`MATCH` filters field names with a glob-style pattern, `COUNT` hints at how much work each call should do, and `NOVALUES` returns field names only, which is noticeably cheaper when values are large and you do not need them. Filtering is applied after a batch has been read, so a call can return nothing while the cursor is still non-zero: only a cursor of `0` means the iteration is over. Fields present for the whole iteration are returned at least once, and fields added or removed while it runs may or may not appear.
 
 ## Syntax
 
diff --git a/redis/commands/hash/hset.mdx b/redis/commands/hash/hset.mdx
index 137c51da1..31f8ca13c 100644
--- a/redis/commands/hash/hset.mdx
+++ b/redis/commands/hash/hset.mdx
@@ -3,7 +3,11 @@ title: "HSET"
 description: "Set hash field values."
 ---
 
-Use `HSET` to set hash field values.
+Use `HSET` to set one or more fields of a hash to the given values, creating the key when it does not exist.
+
+Existing fields are overwritten, and the reply counts only the fields that were added, not those that were updated, which is how you tell an insert from an update. Setting fields does not touch the key's time to live, so a hash with an expiration keeps it as it is written to. A field's own expiration is a different matter: writing a field clears the TTL it may have been given by [`HEXPIRE`](/redis/commands/hash/hexpire) or [`HSETEX`](/redis/commands/hash/hsetex).
+
+Hashes are the compact way to store an object under one key: field access with `HSET` and [`HGET`](/redis/commands/hash/hget) avoids reading and rewriting the whole value the way a serialized string would.
 
 ## Syntax
 
diff --git a/redis/commands/hash/hsetex.mdx b/redis/commands/hash/hsetex.mdx
index 59fe51c45..e3054a98a 100644
--- a/redis/commands/hash/hsetex.mdx
+++ b/redis/commands/hash/hsetex.mdx
@@ -3,7 +3,11 @@ title: "HSETEX"
 description: "Set fields with expiration."
 ---
 
-Use `HSETEX` to set fields with expiration.
+Use `HSETEX` to write hash fields and set their expiration in the same atomic call.
+
+`FIELDS <numfields>` introduces the field and value pairs and the count must match. `EX`, `PX`, `EXAT`, and `PXAT` give the written fields a lifetime or an absolute deadline, and `KEEPTTL` keeps whatever expiration those fields already had. Without any of these options the fields are written without an expiration, so a previously set one is dropped.
+
+`FNX` writes only when none of the given fields exist and `FXX` only when all of them do, which turns the command into an atomic conditional write: create-if-absent or update-if-present, with the expiration applied in the same step. The reply is `1` when the fields were written and `0` when the condition prevented it.
 
 ## Syntax
 
@@ -16,7 +20,7 @@ HSETEX <key> [FNX | FXX] [EX <seconds> | PX <milliseconds> | EXAT <unix-time-sec
 | Argument | Required | Repeatable | Description |
 | --- | --- | --- | --- |
 | `<key>` | Yes | No | Redis key targeted by the command. |
-| `(FNX \| FXX)` | No | No | Choose one form: `FNX`; `FXX`. |
+| `(FNX \| FXX)` | No | No | Write only when the condition holds: `FNX` when none of the given fields exist, `FXX` when all of them do. |
 | `(EX <seconds> \| PX <milliseconds> \| EXAT <unix-time-seconds> \| PXAT <unix-time-milliseconds> \| KEEPTTL)` | No | No | Choose one form: `EX` (set a lifetime in seconds); `PX` (set a lifetime in milliseconds); `EXAT` (expire at a Unix timestamp in seconds); `PXAT` (expire at a Unix timestamp in milliseconds); `KEEPTTL` (preserve the existing key lifetime). |
 | `FIELDS <numfields> <field> <value> [<field> <value> ...]` | Yes | No | Field-value pairs to set. Give the pair count first, then that many field and value pairs. |
 
diff --git a/redis/commands/hash/hsetnx.mdx b/redis/commands/hash/hsetnx.mdx
index 70a359a97..c55a52492 100644
--- a/redis/commands/hash/hsetnx.mdx
+++ b/redis/commands/hash/hsetnx.mdx
@@ -3,7 +3,9 @@ title: "HSETNX"
 description: "Set field only if it doesn't exist."
 ---
 
-Use `HSETNX` to set field only if it doesn't exist.
+Use `HSETNX` to set a hash field only when it does not already exist.
+
+The reply is `1` when the field was created and `0` when it was already present and left untouched. The check and the write happen atomically, so of several clients racing to fill the same field exactly one succeeds, which makes the command a way to claim a slot inside a hash without overwriting whatever a concurrent writer put there.
 
 ## Syntax
 
diff --git a/redis/commands/hash/hstrlen.mdx b/redis/commands/hash/hstrlen.mdx
index 0baa104eb..3f3dfc4f2 100644
--- a/redis/commands/hash/hstrlen.mdx
+++ b/redis/commands/hash/hstrlen.mdx
@@ -3,7 +3,9 @@ title: "HSTRLEN"
 description: "Get length of a field's value."
 ---
 
-Use `HSTRLEN` to get length of a field's value.
+Use `HSTRLEN` to get the length in bytes of the value stored in a hash field.
+
+The reply is `0` when either the field or the key is missing. Since the value itself is not transferred, this is how you check the size of a large field, or decide whether it is worth fetching, without paying for it.
 
 ## Syntax
 
diff --git a/redis/commands/hash/httl.mdx b/redis/commands/hash/httl.mdx
index ecff590a6..a67b79d5c 100644
--- a/redis/commands/hash/httl.mdx
+++ b/redis/commands/hash/httl.mdx
@@ -3,7 +3,9 @@ title: "HTTL"
 description: "Get field TTL in seconds."
 ---
 
-Use `HTTL` to get field TTL in seconds.
+Use `HTTL` to read how much longer hash fields will live, in seconds.
+
+The reply holds one value per requested field, in order: the remaining lifetime, `-1` when the field exists but has no expiration, and `-2` when the field or the key does not exist, so a missing field is never confused with a permanent one. Use [`HPTTL`](/redis/commands/hash/hpttl) for millisecond precision and [`HEXPIRETIME`](/redis/commands/hash/hexpiretime) when you want the absolute deadline instead of the time left.
 
 ## Syntax
 
diff --git a/redis/commands/hash/hvals.mdx b/redis/commands/hash/hvals.mdx
index a5203f676..685eeb6db 100644
--- a/redis/commands/hash/hvals.mdx
+++ b/redis/commands/hash/hvals.mdx
@@ -3,7 +3,9 @@ title: "HVALS"
 description: "Get all values in a hash."
 ---
 
-Use `HVALS` to get all values in a hash.
+Use `HVALS` to get all the values in a hash, without their field names.
+
+A missing key returns an empty list, and values come back in no particular order. The whole hash is transferred, so on large hashes prefer [`HSCAN`](/redis/commands/hash/hscan) to walk it in batches, or [`HMGET`](/redis/commands/hash/hmget) when you know which fields you need.
 
 ## Syntax
 
diff --git a/redis/commands/hyperloglog/pfadd.mdx b/redis/commands/hyperloglog/pfadd.mdx
index a3cda9b5b..0044bda1f 100644
--- a/redis/commands/hyperloglog/pfadd.mdx
+++ b/redis/commands/hyperloglog/pfadd.mdx
@@ -3,7 +3,11 @@ title: "PFADD"
 description: "Add elements to HyperLogLog."
 ---
 
-Use `PFADD` to add elements to HyperLogLog.
+Use `PFADD` to add elements to a HyperLogLog.
+
+A HyperLogLog estimates how many distinct items it has seen while using a small, fixed amount of memory (at most about 12 KB) no matter how many elements pass through it. That is the trade it makes: individual elements are not stored, so they cannot be listed, checked for membership, or removed, and the cardinality that comes back from [`PFCOUNT`](/redis/commands/hyperloglog/pfcount) is an approximation with a standard error of about 0.81%.
+
+The key is created on first use, and the reply is `1` when the internal registers changed as a result of the call, which is a hint that at least one element was new, and `0` when they did not. Calling `PFADD` with no elements creates an empty HyperLogLog if the key does not exist yet. Use it for counts where the exact number does not matter, such as unique visitors per page or per day, and a set for cases where you must be able to look elements up.
 
 ## Syntax
 
diff --git a/redis/commands/hyperloglog/pfcount.mdx b/redis/commands/hyperloglog/pfcount.mdx
index adc886b1a..e9c761ac7 100644
--- a/redis/commands/hyperloglog/pfcount.mdx
+++ b/redis/commands/hyperloglog/pfcount.mdx
@@ -3,7 +3,11 @@ title: "PFCOUNT"
 description: "Get estimated cardinality."
 ---
 
-Use `PFCOUNT` to get estimated cardinality.
+Use `PFCOUNT` to read the estimated number of distinct elements recorded in one or more HyperLogLogs.
+
+With a single key the stored estimate is returned. With several keys the structures are merged on the fly and the cardinality of their union is returned, without modifying any of them, which is how you answer "how many unique users across these seven days" without double counting. The result is an approximation with a standard error of about 0.81%.
+
+The multi-key form does real work on every call, so when the same union is read often it is cheaper to roll the sources up into one key with [`PFMERGE`](/redis/commands/hyperloglog/pfmerge) and count that.
 
 ## Syntax
 
diff --git a/redis/commands/hyperloglog/pfmerge.mdx b/redis/commands/hyperloglog/pfmerge.mdx
index 5e1cbd3c7..2c53d3ae9 100644
--- a/redis/commands/hyperloglog/pfmerge.mdx
+++ b/redis/commands/hyperloglog/pfmerge.mdx
@@ -3,7 +3,11 @@ title: "PFMERGE"
 description: "Merge multiple HyperLogLogs."
 ---
 
-Use `PFMERGE` to merge multiple HyperLogLogs.
+Use `PFMERGE` to merge several HyperLogLogs into a single one.
+
+The destination ends up representing the union of the source structures and of whatever it already held, so merging the same sources again changes nothing and new data can be folded in as it arrives. The destination is created if it does not exist.
+
+Because the union is computed register by register and loses no accuracy compared with counting the raw data, rolling hourly keys into a daily key, or daily keys into a monthly one, gives the same estimate as if every element had been added to that key directly. That makes `PFMERGE` the building block for time-based rollups of unique counts.
 
 ## Syntax
 
diff --git a/redis/commands/json/json-arrappend.mdx b/redis/commands/json/json-arrappend.mdx
index 52cebfd40..5b15695f6 100644
--- a/redis/commands/json/json-arrappend.mdx
+++ b/redis/commands/json/json-arrappend.mdx
@@ -3,7 +3,9 @@ title: "JSON.ARRAPPEND"
 description: "Append values to JSON array."
 ---
 
-Use `JSON.ARRAPPEND` to append values to JSON array.
+Use `JSON.ARRAPPEND` to append one or more values to the end of the arrays a path selects.
+
+Values are JSON text and each one is appended as a single element, so appending an array adds a nested array rather than merging its items. The reply is the new length of each array the path matched, with null for matches that are not arrays.
 
 ## Syntax
 
diff --git a/redis/commands/json/json-arrindex.mdx b/redis/commands/json/json-arrindex.mdx
index 5ebfebeb8..9bd1fdeea 100644
--- a/redis/commands/json/json-arrindex.mdx
+++ b/redis/commands/json/json-arrindex.mdx
@@ -3,7 +3,9 @@ title: "JSON.ARRINDEX"
 description: "Find index of value in array."
 ---
 
-Use `JSON.ARRINDEX` to find index of value in array.
+Use `JSON.ARRINDEX` to find the first position of a value inside the arrays a path selects.
+
+The value is JSON text and is compared for exact equality, so `1` does not match `"1"`. The optional `start` and `stop` bound the search: `start` is inclusive, `stop` is exclusive, both may be negative to count from the end of the array, and `0` for `stop` means "to the end". The reply is the index of the first match or `-1` when the value is not present, with one result per array the path matched.
 
 ## Syntax
 
diff --git a/redis/commands/json/json-arrinsert.mdx b/redis/commands/json/json-arrinsert.mdx
index 4ee00277a..5818e6acd 100644
--- a/redis/commands/json/json-arrinsert.mdx
+++ b/redis/commands/json/json-arrinsert.mdx
@@ -3,7 +3,9 @@ title: "JSON.ARRINSERT"
 description: "Insert values into JSON array."
 ---
 
-Use `JSON.ARRINSERT` to insert values into JSON array.
+Use `JSON.ARRINSERT` to insert one or more values into the arrays a path selects, before a given index.
+
+Elements at and after that index shift to the right, keeping the rest of the array in order. A negative index counts from the end of the array and an index equal to the array's length appends, while an index outside the array returns an error. The reply is the new length of each array the path matched.
 
 ## Syntax
 
diff --git a/redis/commands/json/json-arrlen.mdx b/redis/commands/json/json-arrlen.mdx
index b20916421..623fc9d80 100644
--- a/redis/commands/json/json-arrlen.mdx
+++ b/redis/commands/json/json-arrlen.mdx
@@ -3,7 +3,9 @@ title: "JSON.ARRLEN"
 description: "Get JSON array length."
 ---
 
-Use `JSON.ARRLEN` to get JSON array length.
+Use `JSON.ARRLEN` to get the number of elements in the arrays a path selects.
+
+Without a path the root value is used. The reply is one length per match, with null for matches that are not arrays, so it doubles as a cheap way to check that a branch of the document really is an array before working on it.
 
 ## Syntax
 
diff --git a/redis/commands/json/json-arrpop.mdx b/redis/commands/json/json-arrpop.mdx
index 8d549bd8e..ec88ef6c5 100644
--- a/redis/commands/json/json-arrpop.mdx
+++ b/redis/commands/json/json-arrpop.mdx
@@ -3,7 +3,11 @@ title: "JSON.ARRPOP"
 description: "Pop value from JSON array."
 ---
 
-Use `JSON.ARRPOP` to pop value from JSON array.
+Use `JSON.ARRPOP` to remove an element from the arrays a path selects and return it.
+
+Without an index the last element is popped, which makes the command a stack pop; index `0` pops the first element, and negative indexes count from the end. An index past the end of the array is clamped to the last element. The reply is the removed element as JSON text, or null when the array is empty.
+
+Because the read and the removal happen in one atomic step, a JSON array can be used as a small work queue without the risk of two clients taking the same element.
 
 ## Syntax
 
diff --git a/redis/commands/json/json-arrtrim.mdx b/redis/commands/json/json-arrtrim.mdx
index b96952495..55c1d368d 100644
--- a/redis/commands/json/json-arrtrim.mdx
+++ b/redis/commands/json/json-arrtrim.mdx
@@ -3,7 +3,11 @@ title: "JSON.ARRTRIM"
 description: "Trim JSON array to range."
 ---
 
-Use `JSON.ARRTRIM` to trim JSON array to range.
+Use `JSON.ARRTRIM` to keep only a range of elements in the arrays a path selects and discard the rest.
+
+Both `start` and `stop` are inclusive indexes and may be negative to count from the end of the array. Indexes outside the array are clamped, and a range that selects nothing leaves an empty array. The reply is the new length of each array the path matched.
+
+It is the JSON counterpart of [`LTRIM`](/redis/commands/list/ltrim): combine it with [`JSON.ARRAPPEND`](/redis/commands/json/json-arrappend) to keep a capped list, such as the last N events, inside a document.
 
 ## Syntax
 
diff --git a/redis/commands/json/json-clear.mdx b/redis/commands/json/json-clear.mdx
index d2c3dd212..ebc018bdf 100644
--- a/redis/commands/json/json-clear.mdx
+++ b/redis/commands/json/json-clear.mdx
@@ -3,7 +3,11 @@ title: "JSON.CLEAR"
 description: "Clear JSON values."
 ---
 
-Use `JSON.CLEAR` to clear JSON values.
+Use `JSON.CLEAR` to empty the values a path selects without removing them from the document.
+
+Objects lose all their keys, arrays lose all their elements, and numbers are reset to `0`. Values of other types, such as strings and booleans, are left as they are. The reply is the number of values that were cleared.
+
+The difference from [`JSON.DEL`](/redis/commands/json/json-del) is that the selected keys and slots stay in the document as empty containers, so the shape of the document is preserved and consumers that expect a field to exist keep working.
 
 ## Syntax
 
diff --git a/redis/commands/json/json-debug.mdx b/redis/commands/json/json-debug.mdx
index 1443580b0..39f94ce78 100644
--- a/redis/commands/json/json-debug.mdx
+++ b/redis/commands/json/json-debug.mdx
@@ -3,7 +3,11 @@ title: "JSON.DEBUG"
 description: "Inspect JSON memory usage."
 ---
 
-Use `JSON.DEBUG` to inspect JSON memory usage.
+Use `JSON.DEBUG` to inspect internal details of stored JSON values.
+
+`JSON.DEBUG MEMORY` reports the approximate number of bytes used by the value a key and optional path select, which is how you find out which documents, or which branches of a document, are responsible for memory growth. The figure includes internal overhead and is an estimate meant for comparison rather than exact accounting. `JSON.DEBUG HELP` lists the supported forms.
+
+It is a diagnostic aid: the details it exposes are implementation-specific and can change, so do not build application logic on them.
 
 ## Syntax
 
diff --git a/redis/commands/json/json-del.mdx b/redis/commands/json/json-del.mdx
index ed66ab693..0504d4638 100644
--- a/redis/commands/json/json-del.mdx
+++ b/redis/commands/json/json-del.mdx
@@ -3,7 +3,11 @@ title: "JSON.DEL"
 description: "Delete JSON values."
 ---
 
-Use `JSON.DEL` to delete JSON values.
+Use `JSON.DEL` to delete the value at a path in a JSON document.
+
+Without a path the entire key is deleted. The reply is the number of values that were deleted, which is `0` when the path matched nothing, and deleting the root of a document removes the key itself. With a JSONPath that matches several places, every match is removed in the same call.
+
+[`JSON.FORGET`](/redis/commands/json/json-forget) is an alias with identical behavior.
 
 ## Syntax
 
diff --git a/redis/commands/json/json-forget.mdx b/redis/commands/json/json-forget.mdx
index 7fd5da321..5d1b08e90 100644
--- a/redis/commands/json/json-forget.mdx
+++ b/redis/commands/json/json-forget.mdx
@@ -1,9 +1,11 @@
 ---
 title: "JSON.FORGET"
-description: "Alias for JSON.DEL."
+description: "Delete JSON values (alias of JSON.DEL)."
 ---
 
-Use `JSON.FORGET` to alias for JSON.DEL.
+Use `JSON.FORGET` to delete the value at a path in a JSON document. It is an alias of [`JSON.DEL`](/redis/commands/json/json-del) with identical behavior, kept for compatibility with clients and code that use the older name.
+
+Without a path the entire key is deleted, and the reply is the number of values that were deleted, which is `0` when the path matched nothing.
 
 ## Syntax
 
diff --git a/redis/commands/json/json-get.mdx b/redis/commands/json/json-get.mdx
index 7b365d10b..5e8dc14eb 100644
--- a/redis/commands/json/json-get.mdx
+++ b/redis/commands/json/json-get.mdx
@@ -3,7 +3,11 @@ title: "JSON.GET"
 description: "Get JSON values."
 ---
 
-Use `JSON.GET` to get JSON values.
+Use `JSON.GET` to read one or more values from a JSON document.
+
+Without a path the whole document is returned. The reply shape depends on the path syntax: a path starting with `$` is a JSONPath and always returns an array with one entry per match, so an empty array means nothing matched, while the legacy dot syntax returns the value itself and reports an error when the path does not exist. Passing several paths returns an object keyed by the path expressions, which is a cheap way to pull a few unrelated branches of a large document in one call.
+
+`INDENT`, `NEWLINE`, and `SPACE` control the formatting of the returned JSON text, which is otherwise compact. They are meant for human-readable output; leave them out when a program parses the reply.
 
 ## Syntax
 
diff --git a/redis/commands/json/json-merge.mdx b/redis/commands/json/json-merge.mdx
index 7792d31b4..fb9f2691a 100644
--- a/redis/commands/json/json-merge.mdx
+++ b/redis/commands/json/json-merge.mdx
@@ -3,7 +3,11 @@ title: "JSON.MERGE"
 description: "Merge JSON values."
 ---
 
-Use `JSON.MERGE` to merge JSON values.
+Use `JSON.MERGE` to merge a JSON value into a document at a path, following the JSON Merge Patch semantics of RFC 7386.
+
+Objects are merged recursively: keys in the patch replace or create the matching keys in the target, keys set to `null` delete them, and any value that is not an object, arrays included, replaces the target outright instead of being merged element by element. The parent must already exist: merging into a missing child of an existing object creates it, but intermediate levels are not built along the way, and a key that does not exist yet can only be created by merging at the root.
+
+This is the command for partial updates of an object, where [`JSON.SET`](/redis/commands/json/json-set) would replace the whole branch: one call can change a few fields, delete another, and leave the rest of the document untouched.
 
 ## Syntax
 
diff --git a/redis/commands/json/json-mget.mdx b/redis/commands/json/json-mget.mdx
index 62378e27a..8b3c33520 100644
--- a/redis/commands/json/json-mget.mdx
+++ b/redis/commands/json/json-mget.mdx
@@ -3,7 +3,9 @@ title: "JSON.MGET"
 description: "Get values from multiple keys."
 ---
 
-Use `JSON.MGET` to get values from multiple keys.
+Use `JSON.MGET` to read the same path from several JSON documents in one call.
+
+The reply holds one entry per key, in the order requested, containing what the path selected in that document, or null when the key does not exist or the path matches nothing. It replaces one [`JSON.GET`](/redis/commands/json/json-get) per key when you are gathering the same field across many documents, for example the price of every product in a cart.
 
 ## Syntax
 
diff --git a/redis/commands/json/json-mset.mdx b/redis/commands/json/json-mset.mdx
index ab7f3a196..d17bff529 100644
--- a/redis/commands/json/json-mset.mdx
+++ b/redis/commands/json/json-mset.mdx
@@ -3,7 +3,9 @@ title: "JSON.MSET"
 description: "Set values in multiple keys."
 ---
 
-Use `JSON.MSET` to set values in multiple keys.
+Use `JSON.MSET` to set values at paths in several JSON documents in one atomic call.
+
+Each triple gives a key, a path, and a value, and missing keys are created. Either every write is applied or none is, with no other command running in between, which is what makes it the right tool for documents that must stay consistent with each other. The reply is `OK`.
 
 ## Syntax
 
diff --git a/redis/commands/json/json-numincrby.mdx b/redis/commands/json/json-numincrby.mdx
index 7aea132a0..9e4167744 100644
--- a/redis/commands/json/json-numincrby.mdx
+++ b/redis/commands/json/json-numincrby.mdx
@@ -3,7 +3,9 @@ title: "JSON.NUMINCRBY"
 description: "Increment JSON number."
 ---
 
-Use `JSON.NUMINCRBY` to increment JSON number.
+Use `JSON.NUMINCRBY` to add a number to the numeric values a path selects.
+
+The increment may be negative to count down, and it is applied atomically, so concurrent callers cannot lose an update. The reply is the new value of each match; a match that is not a number returns an error. This is how a counter kept inside a document is updated without reading and rewriting the whole document.
 
 ## Syntax
 
diff --git a/redis/commands/json/json-nummultby.mdx b/redis/commands/json/json-nummultby.mdx
index e4557dd7b..22d250289 100644
--- a/redis/commands/json/json-nummultby.mdx
+++ b/redis/commands/json/json-nummultby.mdx
@@ -3,7 +3,9 @@ title: "JSON.NUMMULTBY"
 description: "Multiply JSON number."
 ---
 
-Use `JSON.NUMMULTBY` to multiply JSON number.
+Use `JSON.NUMMULTBY` to multiply the numeric values a path selects by a number.
+
+The multiplier may be a fraction to scale values down, and the update is atomic. The reply is the new value of each match, and a match that is not a number returns an error. It is the multiplicative counterpart of [`JSON.NUMINCRBY`](/redis/commands/json/json-numincrby), useful for applying percentage changes such as a discount to every price in a document.
 
 ## Syntax
 
diff --git a/redis/commands/json/json-objkeys.mdx b/redis/commands/json/json-objkeys.mdx
index aa67aa2c4..9aef6d23a 100644
--- a/redis/commands/json/json-objkeys.mdx
+++ b/redis/commands/json/json-objkeys.mdx
@@ -3,7 +3,9 @@ title: "JSON.OBJKEYS"
 description: "Get JSON object keys."
 ---
 
-Use `JSON.OBJKEYS` to get JSON object keys.
+Use `JSON.OBJKEYS` to list the field names of the objects a path selects.
+
+Without a path the root value is used. The reply holds one list of keys per match, with null for matches that are not objects. Only the field names come back, not the values, which makes it a cheap way to inspect the shape of a document before reading it.
 
 ## Syntax
 
diff --git a/redis/commands/json/json-objlen.mdx b/redis/commands/json/json-objlen.mdx
index 3c5176463..031d5a435 100644
--- a/redis/commands/json/json-objlen.mdx
+++ b/redis/commands/json/json-objlen.mdx
@@ -3,7 +3,9 @@ title: "JSON.OBJLEN"
 description: "Get JSON object size."
 ---
 
-Use `JSON.OBJLEN` to get JSON object size.
+Use `JSON.OBJLEN` to get the number of fields in the objects a path selects.
+
+Without a path the root value is used. The reply holds one count per match, with null for matches that are not objects. It counts only the object's own fields, not the fields of nested objects.
 
 ## Syntax
 
diff --git a/redis/commands/json/json-resp.mdx b/redis/commands/json/json-resp.mdx
index 06af1f2ac..0871c9d24 100644
--- a/redis/commands/json/json-resp.mdx
+++ b/redis/commands/json/json-resp.mdx
@@ -3,7 +3,11 @@ title: "JSON.RESP"
 description: "Get JSON in RESP format."
 ---
 
-Use `JSON.RESP` to get JSON in RESP format.
+Use `JSON.RESP` to get a JSON value in RESP form instead of as JSON text.
+
+The document is translated structurally: an object becomes an array whose first element is `{` followed by alternating field names and values, an array becomes an array whose first element is `[` followed by its elements, and scalars become the corresponding RESP types. Nested values are translated the same way, recursively.
+
+This lets a client walk the structure using the protocol types it already decodes, without running a JSON parser on the reply. For ordinary use, [`JSON.GET`](/redis/commands/json/json-get) is the more convenient command.
 
 ## Syntax
 
diff --git a/redis/commands/json/json-set.mdx b/redis/commands/json/json-set.mdx
index 9f58cda2e..7800a3170 100644
--- a/redis/commands/json/json-set.mdx
+++ b/redis/commands/json/json-set.mdx
@@ -3,7 +3,11 @@ title: "JSON.SET"
 description: "Set JSON value."
 ---
 
-Use `JSON.SET` to set JSON value.
+Use `JSON.SET` to set a JSON value at a path inside a document, creating the key when it does not exist.
+
+The value is JSON text; the Upstash SDK helpers serialize native objects for you. With the root path (`$`) the whole document is replaced, which is also how a new document is created. For a nested path the parent must already exist: the command adds one missing child to an existing object or appends to an existing array, but it does not create intermediate levels along the way.
+
+`NX` writes only when the path does not exist yet and `XX` only when it does, which makes conditional updates atomic. When the path is a JSONPath that matches several places, every match is updated in the same call, so a single command can update all elements of an array.
 
 ## Syntax
 
diff --git a/redis/commands/json/json-strappend.mdx b/redis/commands/json/json-strappend.mdx
index 407000b60..f7dbb3a04 100644
--- a/redis/commands/json/json-strappend.mdx
+++ b/redis/commands/json/json-strappend.mdx
@@ -3,7 +3,9 @@ title: "JSON.STRAPPEND"
 description: "Append to JSON string."
 ---
 
-Use `JSON.STRAPPEND` to append to JSON string.
+Use `JSON.STRAPPEND` to append text to the string values a path selects.
+
+The value is JSON text, so the appended string must be quoted, as in `'"suffix"'`. The reply is the new length of each string the path matched, with an error for matches that are not strings. Appending in place avoids reading and rewriting the whole document just to extend one field.
 
 ## Syntax
 
diff --git a/redis/commands/json/json-strlen.mdx b/redis/commands/json/json-strlen.mdx
index 06a821119..70733ec9b 100644
--- a/redis/commands/json/json-strlen.mdx
+++ b/redis/commands/json/json-strlen.mdx
@@ -3,7 +3,9 @@ title: "JSON.STRLEN"
 description: "Get JSON string length."
 ---
 
-Use `JSON.STRLEN` to get JSON string length.
+Use `JSON.STRLEN` to get the length of the string values a path selects.
+
+Without a path the root value is used. The reply holds one length per match, with null for matches that are not strings, so it is also a quick way to check that a field is a string. The value itself is not transferred, which makes it cheap even for long strings.
 
 ## Syntax
 
diff --git a/redis/commands/json/json-toggle.mdx b/redis/commands/json/json-toggle.mdx
index 22c48f16e..62e584d90 100644
--- a/redis/commands/json/json-toggle.mdx
+++ b/redis/commands/json/json-toggle.mdx
@@ -3,7 +3,9 @@ title: "JSON.TOGGLE"
 description: "Toggle JSON boolean."
 ---
 
-Use `JSON.TOGGLE` to toggle JSON boolean.
+Use `JSON.TOGGLE` to flip the boolean values a path selects, turning `true` into `false` and back.
+
+The reply is the new value of each match, and a match that is not a boolean returns an error. Because the read and the write are one atomic step, this is the safe way to flip a flag inside a document, where reading it and writing the opposite value back would race with other clients.
 
 ## Syntax
 
diff --git a/redis/commands/json/json-type.mdx b/redis/commands/json/json-type.mdx
index e71c424b6..d19eb0f51 100644
--- a/redis/commands/json/json-type.mdx
+++ b/redis/commands/json/json-type.mdx
@@ -3,7 +3,9 @@ title: "JSON.TYPE"
 description: "Get JSON value type."
 ---
 
-Use `JSON.TYPE` to get JSON value type.
+Use `JSON.TYPE` to find out the JSON type of the values a path selects.
+
+The reply names one type per match, one of `object`, `array`, `string`, `integer`, `number`, `boolean`, or `null`, and is empty when the path matches nothing. Whole numbers report as `integer` and fractional ones as `number`. It is the way to inspect documents whose shape you do not control before applying type-specific commands, which would otherwise fail.
 
 ## Syntax
 
diff --git a/redis/commands/json/overview.mdx b/redis/commands/json/overview.mdx
index 85b6b8501..29ea87fc0 100644
--- a/redis/commands/json/overview.mdx
+++ b/redis/commands/json/overview.mdx
@@ -16,7 +16,7 @@ To query inside JSON values (full-text, fuzzy, phrase, regex), see [Upstash Redi
 <Card title="JSON.CLEAR" href="/redis/commands/json/json-clear">Clear JSON values</Card>
 <Card title="JSON.DEL" href="/redis/commands/json/json-del">Delete JSON values</Card>
 <Card title="JSON.DEBUG" href="/redis/commands/json/json-debug">Inspect JSON memory usage</Card>
-<Card title="JSON.FORGET" href="/redis/commands/json/json-forget">Alias for JSON.DEL</Card>
+<Card title="JSON.FORGET" href="/redis/commands/json/json-forget">Delete JSON values (alias of JSON.DEL)</Card>
 <Card title="JSON.GET" href="/redis/commands/json/json-get">Get JSON values</Card>
 <Card title="JSON.MERGE" href="/redis/commands/json/json-merge">Merge JSON values</Card>
 <Card title="JSON.MGET" href="/redis/commands/json/json-mget">Get values from multiple keys</Card>
diff --git a/redis/commands/list/blmove.mdx b/redis/commands/list/blmove.mdx
index 4029f254f..8621053c3 100644
--- a/redis/commands/list/blmove.mdx
+++ b/redis/commands/list/blmove.mdx
@@ -5,6 +5,10 @@ description: "Move an element between lists, blocking until one arrives."
 
 Use `BLMOVE` to move an element from one list to another, blocking until the source has an element or the timeout expires.
 
+It is the blocking form of [`LMOVE`](/redis/commands/list/lmove): when the source list is not empty it behaves identically and returns immediately, and when it is empty the connection waits instead of returning null. The timeout is given in seconds, may be fractional, and `0` waits indefinitely. If several clients are waiting on the same key, the one that has been waiting longest is served first.
+
+Because the element is never outside a list, this is the standard way to build a reliable queue: a worker blocks until work appears, atomically moves it to a processing list, and deletes it from there when done, so an interrupted job can be recovered instead of lost.
+
 ## Syntax
 
 ```redis
@@ -17,8 +21,8 @@ BLMOVE <source> <destination> (LEFT | RIGHT) (LEFT | RIGHT) <timeout>
 | --- | --- | --- | --- |
 | `<source>` | Yes | No | Redis key used as source. |
 | `<destination>` | Yes | No | Redis key used as destination. |
-| `(LEFT \| RIGHT)` | Yes | No | Choose one form: `LEFT`; `RIGHT`. |
-| `(LEFT \| RIGHT)` | Yes | No | Choose one form: `LEFT`; `RIGHT`. |
+| `(LEFT \| RIGHT)` | Yes | No | Which end of the source list the element is taken from: `LEFT` (head) or `RIGHT` (tail). |
+| `(LEFT \| RIGHT)` | Yes | No | Which end of the destination list the element is pushed onto: `LEFT` (head) or `RIGHT` (tail). |
 | `<timeout>` | Yes | No | Seconds to block; `0` blocks indefinitely. |
 
 ## Important points
diff --git a/redis/commands/list/blmpop.mdx b/redis/commands/list/blmpop.mdx
index a3e44cd55..6116bcba8 100644
--- a/redis/commands/list/blmpop.mdx
+++ b/redis/commands/list/blmpop.mdx
@@ -5,6 +5,10 @@ description: "Pop from the first non-empty list, blocking until one arrives."
 
 Use `BLMPOP` to pop elements from the first non-empty list among several, blocking until one has elements or the timeout expires.
 
+It is the blocking form of [`LMPOP`](/redis/commands/list/lmpop): keys are examined in the order given, so listing a high priority queue first drains it before the others are considered, `LEFT` or `RIGHT` chooses the end, and `COUNT` sets how many elements to take. The reply names the key that was popped from along with the elements.
+
+The timeout is in seconds, may be fractional, and `0` waits indefinitely; when it expires the reply is null. This is the command to reach for when one worker serves several queues of differing priority.
+
 ## Syntax
 
 ```redis
@@ -18,7 +22,7 @@ BLMPOP <timeout> <numkeys> <key> [<key> ...] (LEFT | RIGHT) [COUNT <count>]
 | `<timeout>` | Yes | No | Seconds to block; `0` blocks indefinitely. |
 | `<numkeys>` | Yes | No | Number of key arguments that follow. |
 | `<key>` | Yes | Yes | Redis key targeted by the command. |
-| `(LEFT \| RIGHT)` | Yes | No | Choose one form: `LEFT`; `RIGHT`. |
+| `(LEFT \| RIGHT)` | Yes | No | Which end to pop from: `LEFT` (head) or `RIGHT` (tail). |
 | `COUNT <count>` | No | No | Maximum number of elements to pop. |
 
 ## Important points
diff --git a/redis/commands/list/blpop.mdx b/redis/commands/list/blpop.mdx
index 0daab6bf5..1dade6609 100644
--- a/redis/commands/list/blpop.mdx
+++ b/redis/commands/list/blpop.mdx
@@ -5,6 +5,10 @@ description: "Pop from the head of a list, blocking until an element arrives."
 
 Use `BLPOP` to pop an element from the head of the first non-empty list, blocking until one has an element or the timeout expires.
 
+It is the blocking form of [`LPOP`](/redis/commands/list/lpop) and it accepts several keys, which are checked in the order given, so earlier keys act as higher priority queues. The reply names the key the element came from together with the element itself, which matters when you are waiting on more than one queue.
+
+The timeout is in seconds, may be fractional, and `0` waits indefinitely; when it expires the reply is null. Blocking lets a worker wait for work without polling, which cuts both latency and wasted commands. When several clients are blocked on the same key they are served in the order they started waiting.
+
 ## Syntax
 
 ```redis
diff --git a/redis/commands/list/brpop.mdx b/redis/commands/list/brpop.mdx
index 47d344da0..33bead8ad 100644
--- a/redis/commands/list/brpop.mdx
+++ b/redis/commands/list/brpop.mdx
@@ -5,6 +5,10 @@ description: "Pop from the tail of a list, blocking until an element arrives."
 
 Use `BRPOP` to pop an element from the tail of the first non-empty list, blocking until one has an element or the timeout expires.
 
+It is the blocking form of [`RPOP`](/redis/commands/list/rpop) and behaves like [`BLPOP`](/redis/commands/list/blpop) in every other respect: several keys are checked in the order given, the reply names the key the element came from, the timeout is in seconds and may be fractional with `0` meaning wait forever, and clients blocked on the same key are served in the order they started waiting.
+
+Producers pushing with [`LPUSH`](/redis/commands/list/lpush) and consumers waiting with `BRPOP` form the classic first-in, first-out worker queue.
+
 ## Syntax
 
 ```redis
diff --git a/redis/commands/list/brpoplpush.mdx b/redis/commands/list/brpoplpush.mdx
index aee6d0995..dc04ae70e 100644
--- a/redis/commands/list/brpoplpush.mdx
+++ b/redis/commands/list/brpoplpush.mdx
@@ -5,6 +5,10 @@ description: "Pop from a list's tail and push it to another, blocking until an e
 
 Use `BRPOPLPUSH` to pop an element from the tail of one list and push it to the head of another, blocking until the source has an element or the timeout expires.
 
+It is the blocking form of [`RPOPLPUSH`](/redis/commands/list/rpoplpush). The timeout is in seconds, may be fractional, and `0` waits indefinitely; when it expires the reply is null. Since the element moves atomically into the destination, a worker that crashes after taking an item leaves it visible in the processing list, where it can be recovered.
+
+Redis deprecates this command in favor of [`BLMOVE`](/redis/commands/list/blmove), which does the same thing and additionally lets you choose which end of each list to use.
+
 ## Syntax
 
 ```redis
diff --git a/redis/commands/list/lindex.mdx b/redis/commands/list/lindex.mdx
index c6fe12061..b544a5b10 100644
--- a/redis/commands/list/lindex.mdx
+++ b/redis/commands/list/lindex.mdx
@@ -3,7 +3,9 @@ title: "LINDEX"
 description: "Get element by index."
 ---
 
-Use `LINDEX` to get element by index.
+Use `LINDEX` to read the element at a given position in a list.
+
+Indexes are zero-based from the head, and negative indexes count from the tail, so `-1` is the last element. The reply is null when the key does not exist or the index is out of range. Redis walks the list from the nearer end to reach the index, so access is fast near the head and tail and gets more expensive towards the middle of a long list.
 
 ## Syntax
 
diff --git a/redis/commands/list/linsert.mdx b/redis/commands/list/linsert.mdx
index ec8e6b7fe..d044cdc40 100644
--- a/redis/commands/list/linsert.mdx
+++ b/redis/commands/list/linsert.mdx
@@ -3,7 +3,11 @@ title: "LINSERT"
 description: "Insert before or after pivot."
 ---
 
-Use `LINSERT` to insert before or after pivot.
+Use `LINSERT` to insert an element immediately before or after another element of a list.
+
+The pivot is matched by value, and only its first occurrence starting from the head is used. The reply is the new length of the list, `0` when the key does not exist, and `-1` when the pivot value was not found, which is how you tell a failed insert from a successful one.
+
+Finding the pivot means scanning the list, so this is a linear operation; on long lists it is worth keeping an index elsewhere or using a sorted set instead.
 
 ## Syntax
 
@@ -16,7 +20,7 @@ LINSERT <key> (BEFORE | AFTER) <pivot> <element>
 | Argument | Required | Repeatable | Description |
 | --- | --- | --- | --- |
 | `<key>` | Yes | No | Redis key targeted by the command. |
-| `(BEFORE \| AFTER)` | Yes | No | Choose one form: `BEFORE`; `AFTER`. |
+| `(BEFORE \| AFTER)` | Yes | No | Where to place the new element relative to the pivot: `BEFORE` or `AFTER`. |
 | `<pivot>` | Yes | No | Existing element to insert next to. |
 | `<element>` | Yes | No | Element to insert. |
 
diff --git a/redis/commands/list/llen.mdx b/redis/commands/list/llen.mdx
index 06e5c5204..82975c27d 100644
--- a/redis/commands/list/llen.mdx
+++ b/redis/commands/list/llen.mdx
@@ -3,7 +3,9 @@ title: "LLEN"
 description: "Get list length."
 ---
 
-Use `LLEN` to get list length.
+Use `LLEN` to get the number of elements in a list.
+
+The reply is `0` when the key does not exist. The length is maintained by Redis rather than computed on demand, so the command is cheap whatever the size of the list, which makes it the usual way to monitor a queue's backlog.
 
 ## Syntax
 
diff --git a/redis/commands/list/lmove.mdx b/redis/commands/list/lmove.mdx
index abc0d8fde..ea66c9f51 100644
--- a/redis/commands/list/lmove.mdx
+++ b/redis/commands/list/lmove.mdx
@@ -3,7 +3,11 @@ title: "LMOVE"
 description: "Move element between lists."
 ---
 
-Use `LMOVE` to move element between lists.
+Use `LMOVE` to atomically take an element from one end of a list and push it onto one end of another list, returning the element.
+
+The two directions are chosen independently: `LEFT RIGHT` takes from the head of the source and appends to the tail of the destination, which preserves order when transferring between queues, while `LEFT LEFT` behaves like moving between stacks. If the source is empty nothing happens and the reply is null. Source and destination may be the same key, in which case the list is rotated.
+
+Because the element is never outside a list, `LMOVE` is the building block for reliable queues: a worker moves an item into a processing list, does the work, and removes it from there, so a crash leaves the item recoverable instead of lost. It replaces the deprecated [`RPOPLPUSH`](/redis/commands/list/rpoplpush), and [`BLMOVE`](/redis/commands/list/blmove) is the blocking form.
 
 ## Syntax
 
@@ -17,8 +21,8 @@ LMOVE <source> <destination> (LEFT | RIGHT) (LEFT | RIGHT)
 | --- | --- | --- | --- |
 | `<source>` | Yes | No | Redis key used as source. |
 | `<destination>` | Yes | No | Redis key used as destination. |
-| `(LEFT \| RIGHT)` | Yes | No | Choose one form: `LEFT`; `RIGHT`. |
-| `(LEFT \| RIGHT)` | Yes | No | Choose one form: `LEFT`; `RIGHT`. |
+| `(LEFT \| RIGHT)` | Yes | No | Which end of the source list the element is taken from: `LEFT` (head) or `RIGHT` (tail). |
+| `(LEFT \| RIGHT)` | Yes | No | Which end of the destination list the element is pushed onto: `LEFT` (head) or `RIGHT` (tail). |
 
 ## Response
 
diff --git a/redis/commands/list/lmpop.mdx b/redis/commands/list/lmpop.mdx
index 79883544b..d4f2a6f3a 100644
--- a/redis/commands/list/lmpop.mdx
+++ b/redis/commands/list/lmpop.mdx
@@ -1,9 +1,13 @@
 ---
 title: "LMPOP"
-description: "Pop from multiple lists."
+description: "Pop from the first non-empty list."
 ---
 
-Use `LMPOP` to pop from multiple lists.
+Use `LMPOP` to pop elements from the first of several lists that is not empty.
+
+`<numkeys>` states how many keys follow, `LEFT` or `RIGHT` chooses the end to pop from, and `COUNT` sets how many elements to take, defaulting to one. Keys are examined in the order given and only the first non-empty one is touched, which is exactly what a priority queue needs: list the high priority queue first and it is drained before the others are looked at.
+
+The reply names the key that was popped from together with the elements, so a caller working with several queues knows where the work came from. When every key is empty the reply is null; use [`BLMPOP`](/redis/commands/list/blmpop) to wait instead.
 
 ## Syntax
 
@@ -17,7 +21,7 @@ LMPOP <numkeys> <key> [<key> ...] (LEFT | RIGHT) [COUNT <count>]
 | --- | --- | --- | --- |
 | `<numkeys>` | Yes | No | Number of key arguments that follow. |
 | `<key>` | Yes | Yes | Redis key targeted by the command. |
-| `(LEFT \| RIGHT)` | Yes | No | Choose one form: `LEFT`; `RIGHT`. |
+| `(LEFT \| RIGHT)` | Yes | No | Which end to pop from: `LEFT` (head) or `RIGHT` (tail). |
 | `COUNT <count>` | No | No | Maximum number of elements to pop. |
 
 ## Response
diff --git a/redis/commands/list/lpop.mdx b/redis/commands/list/lpop.mdx
index 6dd2f2d09..692cf261a 100644
--- a/redis/commands/list/lpop.mdx
+++ b/redis/commands/list/lpop.mdx
@@ -3,7 +3,11 @@ title: "LPOP"
 description: "Pop from list head."
 ---
 
-Use `LPOP` to pop from list head.
+Use `LPOP` to remove and return elements from the head of a list.
+
+Without a count a single element is returned, or null when the key does not exist. With a count, up to that many elements are removed and returned in the order they were popped, and the reply is an empty array or null when the list is empty. The key is deleted once the last element is removed.
+
+Paired with [`RPUSH`](/redis/commands/list/rpush) this gives a first-in, first-out queue; paired with [`LPUSH`](/redis/commands/list/lpush) it gives a stack. Use [`BLPOP`](/redis/commands/list/blpop) when a consumer should wait for work rather than poll.
 
 ## Syntax
 
diff --git a/redis/commands/list/lpos.mdx b/redis/commands/list/lpos.mdx
index b3e667222..573ad9a19 100644
--- a/redis/commands/list/lpos.mdx
+++ b/redis/commands/list/lpos.mdx
@@ -1,9 +1,13 @@
 ---
 title: "LPOS"
-description: "Find element position."
+description: "Find the position of an element."
 ---
 
-Use `LPOS` to find element position.
+Use `LPOS` to find the position of an element in a list.
+
+The scan starts at the head and, by default, reports the index of the first match or null when there is none. `RANK` selects which match to report: `RANK 2` skips to the second occurrence, and a negative rank searches backwards from the tail, so `RANK -1` finds the last occurrence. `COUNT` returns that many matching indexes instead of just one, and `COUNT 0` returns all of them. `MAXLEN` limits how many elements are compared, which bounds the cost of the search on a long list at the price of possibly missing matches beyond that point.
+
+It is the read-only way to locate a value before acting on it with [`LSET`](/redis/commands/list/lset) or [`LREM`](/redis/commands/list/lrem).
 
 ## Syntax
 
diff --git a/redis/commands/list/lpush.mdx b/redis/commands/list/lpush.mdx
index 8dbbbcce6..1d988b578 100644
--- a/redis/commands/list/lpush.mdx
+++ b/redis/commands/list/lpush.mdx
@@ -3,7 +3,11 @@ title: "LPUSH"
 description: "Push to list head."
 ---
 
-Use `LPUSH` to push to list head.
+Use `LPUSH` to add one or more elements to the head of a list, creating the list when the key does not exist.
+
+Elements are inserted one after another, so they end up in reverse order relative to the argument list: `LPUSH key a b c` leaves the list as `c`, `b`, `a`. The reply is the length of the list after the push. If the key holds a value of another type the command returns an error.
+
+Pushing to the head and popping from the tail with [`RPOP`](/redis/commands/list/rpop) gives a first-in, first-out queue, while popping from the head with [`LPOP`](/redis/commands/list/lpop) gives a stack. Combine with [`LTRIM`](/redis/commands/list/ltrim) to keep a capped list of recent items.
 
 ## Syntax
 
diff --git a/redis/commands/list/lpushx.mdx b/redis/commands/list/lpushx.mdx
index f6ce11a9c..7395e4530 100644
--- a/redis/commands/list/lpushx.mdx
+++ b/redis/commands/list/lpushx.mdx
@@ -3,7 +3,9 @@ title: "LPUSHX"
 description: "Push to head if list exists."
 ---
 
-Use `LPUSHX` to push to head if list exists.
+Use `LPUSHX` to add elements to the head of a list only when the list already exists.
+
+Nothing happens and the reply is `0` when the key does not exist, and no key is created. This is the difference from [`LPUSH`](/redis/commands/list/lpush), and it is what you want when a list should only be fed while a consumer is holding it open, so that stale producers do not resurrect a queue that was already drained and deleted.
 
 ## Syntax
 
diff --git a/redis/commands/list/lrange.mdx b/redis/commands/list/lrange.mdx
index 6309cff7c..2b8a62275 100644
--- a/redis/commands/list/lrange.mdx
+++ b/redis/commands/list/lrange.mdx
@@ -3,7 +3,11 @@ title: "LRANGE"
 description: "Get range of elements."
 ---
 
-Use `LRANGE` to get range of elements.
+Use `LRANGE` to read a range of elements from a list.
+
+Both `<start>` and `<stop>` are zero-based, inclusive, and may be negative to count from the tail, so `LRANGE key 0 -1` returns the whole list and `LRANGE key 0 9` returns the first ten elements. Out-of-range indexes are clamped instead of producing an error, and a range that selects nothing, or a missing key, returns an empty list.
+
+The command copies the requested range into the reply, so reading a large list in one call is expensive: page through it with successive ranges when the list is big.
 
 ## Syntax
 
diff --git a/redis/commands/list/lrem.mdx b/redis/commands/list/lrem.mdx
index d9b6bf354..ebbb8d43a 100644
--- a/redis/commands/list/lrem.mdx
+++ b/redis/commands/list/lrem.mdx
@@ -3,7 +3,11 @@ title: "LREM"
 description: "Remove elements by value."
 ---
 
-Use `LREM` to remove elements by value.
+Use `LREM` to remove elements equal to a given value from a list.
+
+The count decides how many occurrences are removed and in which direction: a positive count removes that many starting from the head, a negative count removes that many starting from the tail, and `0` removes every occurrence. The reply is the number of elements actually removed, and the key is deleted when the list becomes empty.
+
+Removing by value means scanning the list, so on long lists prefer a set or a sorted set when you frequently need to delete arbitrary items.
 
 ## Syntax
 
diff --git a/redis/commands/list/lset.mdx b/redis/commands/list/lset.mdx
index 44b253136..a38c0049a 100644
--- a/redis/commands/list/lset.mdx
+++ b/redis/commands/list/lset.mdx
@@ -3,7 +3,9 @@ title: "LSET"
 description: "Set element at index."
 ---
 
-Use `LSET` to set element at index.
+Use `LSET` to overwrite the element at a given position in a list.
+
+Indexes are zero-based from the head and negative indexes count from the tail. The command returns an error when the key does not exist or the index is out of range, since it never grows the list; use [`LPUSH`](/redis/commands/list/lpush) or [`RPUSH`](/redis/commands/list/rpush) to add elements. Locate the position first with [`LPOS`](/redis/commands/list/lpos) when you know the value but not the index.
 
 ## Syntax
 
diff --git a/redis/commands/list/ltrim.mdx b/redis/commands/list/ltrim.mdx
index 68abb714c..d49175eb2 100644
--- a/redis/commands/list/ltrim.mdx
+++ b/redis/commands/list/ltrim.mdx
@@ -3,7 +3,11 @@ title: "LTRIM"
 description: "Trim list to range."
 ---
 
-Use `LTRIM` to trim list to range.
+Use `LTRIM` to keep only a range of elements in a list and delete everything outside it.
+
+Both ends are inclusive, zero-based, and may be negative to count from the tail. If `<start>` is greater than `<stop>` or lies past the end of the list, every element is removed and the key is deleted. The reply is always `OK`.
+
+The classic use is a capped list: [`LPUSH`](/redis/commands/list/lpush) a new item and then `LTRIM key 0 99` to keep the hundred most recent ones, which bounds memory without any separate cleanup job.
 
 ## Syntax
 
diff --git a/redis/commands/list/overview.mdx b/redis/commands/list/overview.mdx
index 40b8d6ad2..2770d8f1a 100644
--- a/redis/commands/list/overview.mdx
+++ b/redis/commands/list/overview.mdx
@@ -14,9 +14,9 @@ description: "Commands for storing and manipulating ordered collections."
 <Card title="LINSERT" href="/redis/commands/list/linsert">Insert before or after pivot</Card>
 <Card title="LLEN" href="/redis/commands/list/llen">Get list length</Card>
 <Card title="LMOVE" href="/redis/commands/list/lmove">Move element between lists</Card>
-<Card title="LMPOP" href="/redis/commands/list/lmpop">Pop from multiple lists</Card>
+<Card title="LMPOP" href="/redis/commands/list/lmpop">Pop from the first non-empty list</Card>
 <Card title="LPOP" href="/redis/commands/list/lpop">Pop from list head</Card>
-<Card title="LPOS" href="/redis/commands/list/lpos">Find element position</Card>
+<Card title="LPOS" href="/redis/commands/list/lpos">Find the position of an element</Card>
 <Card title="LPUSH" href="/redis/commands/list/lpush">Push to list head</Card>
 <Card title="LPUSHX" href="/redis/commands/list/lpushx">Push to head if list exists</Card>
 <Card title="LRANGE" href="/redis/commands/list/lrange">Get range of elements</Card>
diff --git a/redis/commands/list/rpop.mdx b/redis/commands/list/rpop.mdx
index f5fec43ed..20a167f1d 100644
--- a/redis/commands/list/rpop.mdx
+++ b/redis/commands/list/rpop.mdx
@@ -3,7 +3,11 @@ title: "RPOP"
 description: "Pop from list tail."
 ---
 
-Use `RPOP` to pop from list tail.
+Use `RPOP` to remove and return elements from the tail of a list.
+
+Without a count a single element is returned, or null when the key does not exist. With a count, up to that many elements are removed and returned in the order they were popped, and the key is deleted once the last element is gone.
+
+Combined with [`LPUSH`](/redis/commands/list/lpush) this gives a first-in, first-out queue, since producers add at the head and consumers take from the tail. Use [`BRPOP`](/redis/commands/list/brpop) when a consumer should wait for work instead of polling.
 
 ## Syntax
 
diff --git a/redis/commands/list/rpoplpush.mdx b/redis/commands/list/rpoplpush.mdx
index da40f419b..652c941df 100644
--- a/redis/commands/list/rpoplpush.mdx
+++ b/redis/commands/list/rpoplpush.mdx
@@ -3,7 +3,11 @@ title: "RPOPLPUSH"
 description: "Pop from tail and push to head."
 ---
 
-Use `RPOPLPUSH` to pop from tail and push to head.
+Use `RPOPLPUSH` to atomically move an element from the tail of one list to the head of another, returning the element.
+
+If the source is empty nothing happens and the reply is null. Source and destination may be the same key, which rotates the list: the tail element becomes the new head, so repeated calls cycle through a list of items forever, a handy pattern for round-robin scheduling.
+
+The command is deprecated in Redis in favor of [`LMOVE`](/redis/commands/list/lmove), which does the same thing but lets you choose both ends. [`BRPOPLPUSH`](/redis/commands/list/brpoplpush) is the blocking form.
 
 ## Syntax
 
diff --git a/redis/commands/list/rpush.mdx b/redis/commands/list/rpush.mdx
index cd82718f4..9486a802c 100644
--- a/redis/commands/list/rpush.mdx
+++ b/redis/commands/list/rpush.mdx
@@ -3,7 +3,11 @@ title: "RPUSH"
 description: "Push to list tail."
 ---
 
-Use `RPUSH` to push to list tail.
+Use `RPUSH` to add one or more elements to the tail of a list, creating the list when the key does not exist.
+
+Elements are appended in the order given, so `RPUSH key a b c` leaves the list as `a`, `b`, `c`. The reply is the length of the list after the push, and a key holding another type returns an error.
+
+Appending with `RPUSH` and consuming from the head with [`LPOP`](/redis/commands/list/lpop) is the standard first-in, first-out queue, and it is the form most job queues use because the natural reading order with [`LRANGE`](/redis/commands/list/lrange) then matches the order of insertion.
 
 ## Syntax
 
diff --git a/redis/commands/list/rpushx.mdx b/redis/commands/list/rpushx.mdx
index 917b532fd..31f1a5263 100644
--- a/redis/commands/list/rpushx.mdx
+++ b/redis/commands/list/rpushx.mdx
@@ -3,7 +3,9 @@ title: "RPUSHX"
 description: "Push to tail if list exists."
 ---
 
-Use `RPUSHX` to push to tail if list exists.
+Use `RPUSHX` to add elements to the tail of a list only when the list already exists.
+
+Nothing happens and the reply is `0` when the key does not exist, and no key is created. Use it when producers should append to a queue only while it is alive, for example when the list is created by a consumer that is currently attached, so that writes to a queue nobody is reading do not silently pile up.
 
 ## Syntax
 
diff --git a/redis/commands/pub-sub/psubscribe.mdx b/redis/commands/pub-sub/psubscribe.mdx
index d6b957277..6e70a86ec 100644
--- a/redis/commands/pub-sub/psubscribe.mdx
+++ b/redis/commands/pub-sub/psubscribe.mdx
@@ -3,7 +3,11 @@ title: "PSUBSCRIBE"
 description: "Subscribe to pattern channels."
 ---
 
-Use `PSUBSCRIBE` to subscribe to pattern channels.
+Use `PSUBSCRIBE` to subscribe the current connection to channels by glob-style pattern.
+
+A pattern such as `news.*` matches every channel that starts with `news.`, including channels created after the subscription, which is what makes patterns useful for topic hierarchies. `?` matches a single character and `[...]` a character class.
+
+Pattern subscriptions are tracked separately from the exact-channel subscriptions made with [`SUBSCRIBE`](/redis/commands/pub-sub/subscribe), and a message that matches several of a connection's patterns is delivered once per matching pattern, so overlapping patterns produce duplicates. Cancel a pattern with [`PUNSUBSCRIBE`](/redis/commands/pub-sub/punsubscribe), passing exactly the same pattern string.
 
 ## Syntax
 
diff --git a/redis/commands/pub-sub/publish.mdx b/redis/commands/pub-sub/publish.mdx
index 147814aee..3960390fb 100644
--- a/redis/commands/pub-sub/publish.mdx
+++ b/redis/commands/pub-sub/publish.mdx
@@ -3,7 +3,11 @@ title: "PUBLISH"
 description: "Publish message to channel."
 ---
 
-Use `PUBLISH` to publish message to channel.
+Use `PUBLISH` to send a message to a channel.
+
+The reply is the number of subscribers the message was delivered to, counting both channel and pattern subscribers, so a reply of `0` means nobody was listening. Delivery is fire and forget: messages are not stored and a client that is not connected at that moment never sees them, so use [streams](/redis/commands/streams/overview) when messages must survive a disconnect or be replayed.
+
+Publishing works over both the REST API and a TCP connection, while subscribing requires a TCP connection.
 
 ## Syntax
 
diff --git a/redis/commands/pub-sub/pubsub.mdx b/redis/commands/pub-sub/pubsub.mdx
index b4f5dce2b..76d808d90 100644
--- a/redis/commands/pub-sub/pubsub.mdx
+++ b/redis/commands/pub-sub/pubsub.mdx
@@ -3,7 +3,11 @@ title: "PUBSUB"
 description: "Inspect pub/sub state."
 ---
 
-Use `PUBSUB` to inspect pub/sub state.
+Use `PUBSUB` to inspect the state of the pub/sub system without subscribing to anything.
+
+`CHANNELS` lists the channels that currently have at least one subscriber, optionally filtered by a glob-style pattern. `NUMSUB` reports the subscriber count for each channel you name, and `NUMPAT` reports how many distinct patterns are subscribed to across all clients.
+
+Only exact-channel subscriptions are counted by `CHANNELS` and `NUMSUB`: a client subscribed with [`PSUBSCRIBE`](/redis/commands/pub-sub/psubscribe) will receive matching messages but does not make a channel appear as active. Use these forms for monitoring and debugging, for instance to confirm that a consumer is really attached before publishing.
 
 ## Syntax
 
diff --git a/redis/commands/pub-sub/punsubscribe.mdx b/redis/commands/pub-sub/punsubscribe.mdx
index 5e841d04f..430eb2dca 100644
--- a/redis/commands/pub-sub/punsubscribe.mdx
+++ b/redis/commands/pub-sub/punsubscribe.mdx
@@ -3,7 +3,11 @@ title: "PUNSUBSCRIBE"
 description: "Unsubscribe from patterns."
 ---
 
-Use `PUNSUBSCRIBE` to unsubscribe from patterns.
+Use `PUNSUBSCRIBE` to cancel pattern subscriptions of the current connection.
+
+With no arguments the connection unsubscribes from every pattern it registered, otherwise only from the patterns named, which must be given exactly as they were passed to [`PSUBSCRIBE`](/redis/commands/pub-sub/psubscribe), since patterns are matched literally here and not expanded. The server sends one confirmation per pattern with the number of subscriptions still active.
+
+Exact-channel subscriptions are not affected; cancel those with [`UNSUBSCRIBE`](/redis/commands/pub-sub/unsubscribe).
 
 ## Syntax
 
diff --git a/redis/commands/pub-sub/subscribe.mdx b/redis/commands/pub-sub/subscribe.mdx
index 09fcff185..4df32e34a 100644
--- a/redis/commands/pub-sub/subscribe.mdx
+++ b/redis/commands/pub-sub/subscribe.mdx
@@ -3,7 +3,11 @@ title: "SUBSCRIBE"
 description: "Subscribe to channels."
 ---
 
-Use `SUBSCRIBE` to subscribe to channels.
+Use `SUBSCRIBE` to subscribe the current connection to one or more channels.
+
+The server confirms each channel with its own reply carrying the running number of subscriptions this connection holds, and from then on messages published to those channels arrive on the connection as they are sent.
+
+Under RESP2 a subscribed connection may only run subscription commands plus `PING`, `RESET`, and `QUIT`, which is why subscribers normally use a dedicated connection. Under RESP3 messages arrive as push replies and ordinary commands remain usable on the same connection. Messages published while the connection is not subscribed are not delivered later, since pub/sub keeps no history.
 
 ## Syntax
 
diff --git a/redis/commands/pub-sub/unsubscribe.mdx b/redis/commands/pub-sub/unsubscribe.mdx
index 59796fece..c563163d9 100644
--- a/redis/commands/pub-sub/unsubscribe.mdx
+++ b/redis/commands/pub-sub/unsubscribe.mdx
@@ -3,7 +3,11 @@ title: "UNSUBSCRIBE"
 description: "Unsubscribe from channels."
 ---
 
-Use `UNSUBSCRIBE` to unsubscribe from channels.
+Use `UNSUBSCRIBE` to cancel channel subscriptions of the current connection.
+
+With no arguments the connection unsubscribes from every channel it is subscribed to, otherwise only from the ones named. The server sends one confirmation per channel, each carrying the number of subscriptions still active, and the connection leaves subscriber mode once that count reaches zero.
+
+Pattern subscriptions are not affected; cancel those with [`PUNSUBSCRIBE`](/redis/commands/pub-sub/punsubscribe).
 
 ## Syntax
 
diff --git a/redis/commands/scripting/eval-ro.mdx b/redis/commands/scripting/eval-ro.mdx
index cc6f1628d..8073fab22 100644
--- a/redis/commands/scripting/eval-ro.mdx
+++ b/redis/commands/scripting/eval-ro.mdx
@@ -3,7 +3,9 @@ title: "EVAL_RO"
 description: "Execute read-only Lua script."
 ---
 
-Use `EVAL_RO` to execute read-only Lua script.
+Use `EVAL_RO` to run a Lua script that is not allowed to write.
+
+It behaves like [`EVAL`](/redis/commands/scripting/eval), with `<numkeys>` splitting the arguments into the `KEYS` and `ARGV` tables, except that any write command called from the script fails with an error. Declaring the read-only intent lets the server serve the call on replicas and turns an accidental write into a clear error instead of an unexpected modification, which is worth doing for every script that only computes over existing data.
 
 ## Syntax
 
diff --git a/redis/commands/scripting/eval.mdx b/redis/commands/scripting/eval.mdx
index 1ca37b1bf..baaa345fe 100644
--- a/redis/commands/scripting/eval.mdx
+++ b/redis/commands/scripting/eval.mdx
@@ -3,7 +3,13 @@ title: "EVAL"
 description: "Execute a Lua script."
 ---
 
-Use `EVAL` to execute a Lua script.
+Use `EVAL` to run a Lua script on the server.
+
+`<numkeys>` says how many of the arguments that follow are key names. The script receives those in the `KEYS` table and every remaining argument in `ARGV`. Passing key names as keys rather than hardcoding them in the script body matters, because Redis uses that list for routing and access checks. Inside the script, `redis.call` runs Redis commands and its return value is converted to a Lua value.
+
+The script runs as a single atomic step: no other command executes while it is running, which makes it the standard way to do read, decide, and write logic, such as a rate limiter or a compare-and-set update, in one round trip and without a transaction. Keep scripts short for the same reason, since a long script blocks everything else, and keep them deterministic by deriving values from `KEYS`, `ARGV`, or data read inside the script rather than from clock or random sources.
+
+Sending a script also caches it under its SHA1 digest, so later calls can use [`EVALSHA`](/redis/commands/scripting/evalsha) and avoid resending the body. Use [`EVAL_RO`](/redis/commands/scripting/eval-ro) for scripts that only read.
 
 ## Syntax
 
diff --git a/redis/commands/scripting/evalsha-ro.mdx b/redis/commands/scripting/evalsha-ro.mdx
index e1b978a50..ee6d7721c 100644
--- a/redis/commands/scripting/evalsha-ro.mdx
+++ b/redis/commands/scripting/evalsha-ro.mdx
@@ -5,6 +5,8 @@ description: "Run a cached script that does not write."
 
 Use `EVALSHA_RO` to run a script cached by its SHA1 digest. The script may not write to the database.
 
+It is the read-only form of [`EVALSHA`](/redis/commands/scripting/evalsha): any write command called from the script fails, which lets the server run it on replicas. As with `EVALSHA`, a digest that is not in the cache produces a `NOSCRIPT` error, and the caller is expected to fall back to [`EVAL_RO`](/redis/commands/scripting/eval-ro) with the script body.
+
 ## Syntax
 
 ```redis
diff --git a/redis/commands/scripting/evalsha.mdx b/redis/commands/scripting/evalsha.mdx
index bff7e4c37..6ef5d0ad3 100644
--- a/redis/commands/scripting/evalsha.mdx
+++ b/redis/commands/scripting/evalsha.mdx
@@ -3,7 +3,11 @@ title: "EVALSHA"
 description: "Execute cached Lua script by SHA."
 ---
 
-Use `EVALSHA` to execute cached Lua script by SHA.
+Use `EVALSHA` to run a script that is already in the server's script cache, identified by its SHA1 digest.
+
+It behaves exactly like [`EVAL`](/redis/commands/scripting/eval) but sends only the 40-character digest instead of the script body, which keeps the request small when a script is called often. The digest is what [`SCRIPT LOAD`](/redis/commands/scripting/script-load) returns, and it is also computed as a side effect of any `EVAL` call.
+
+When the script is not in the cache the server replies with a `NOSCRIPT` error, and the client is expected to fall back to `EVAL`. Most client libraries do this automatically. The cache does not survive a restart and is cleared by [`SCRIPT FLUSH`](/redis/commands/scripting/script-flush), so applications must always be able to resend the script body.
 
 ## Syntax
 
diff --git a/redis/commands/scripting/script-exists.mdx b/redis/commands/scripting/script-exists.mdx
index 31256dd47..0449a8124 100644
--- a/redis/commands/scripting/script-exists.mdx
+++ b/redis/commands/scripting/script-exists.mdx
@@ -3,7 +3,9 @@ title: "SCRIPT EXISTS"
 description: "Check if scripts exist in cache."
 ---
 
-Use `SCRIPT EXISTS` to check if scripts exist in cache.
+Use `SCRIPT EXISTS` to check which of the given SHA1 digests are present in the script cache.
+
+The reply holds one `1` or `0` per digest, in the order they were given. Client libraries use it to find out, in a single call, which of their scripts still need to be loaded before they can be invoked with [`EVALSHA`](/redis/commands/scripting/evalsha), instead of discovering the gap through a `NOSCRIPT` error at call time.
 
 ## Syntax
 
diff --git a/redis/commands/scripting/script-flush.mdx b/redis/commands/scripting/script-flush.mdx
index 0a3555c10..e62e3db2b 100644
--- a/redis/commands/scripting/script-flush.mdx
+++ b/redis/commands/scripting/script-flush.mdx
@@ -3,7 +3,9 @@ title: "SCRIPT FLUSH"
 description: "Clear the script cache."
 ---
 
-Use `SCRIPT FLUSH` to clear the script cache.
+Use `SCRIPT FLUSH` to remove every script from the server's script cache.
+
+After the flush, [`EVALSHA`](/redis/commands/scripting/evalsha) calls fail with `NOSCRIPT` until the scripts are loaded again, so run it when you want clients to resend their current script bodies, typically after deploying changed scripts. `ASYNC` reclaims the memory in the background and `SYNC` reclaims it before the reply. Cached scripts are not part of the dataset, so flushing them does not touch your data.
 
 ## Syntax
 
diff --git a/redis/commands/scripting/script-kill.mdx b/redis/commands/scripting/script-kill.mdx
index 3c3e24084..6a865533b 100644
--- a/redis/commands/scripting/script-kill.mdx
+++ b/redis/commands/scripting/script-kill.mdx
@@ -5,6 +5,10 @@ description: "Stop a running read-only script."
 
 Use `SCRIPT KILL` to stop a running read-only script.
 
+Only a script that has not yet written anything can be killed: stopping one halfway through its writes would leave the dataset in a state that no atomic execution could produce, so Redis refuses and the server has to be restarted instead. This is the main reason to keep scripts short and to use [`EVAL_RO`](/redis/commands/scripting/eval-ro) wherever a script only reads.
+
+The current Upstash deployment recognizes the command but has no interruptible running-script state to act on, so it replies with a `NOTBUSY` error.
+
 ## Syntax
 
 ```redis
diff --git a/redis/commands/scripting/script-load.mdx b/redis/commands/scripting/script-load.mdx
index e673c3a8c..0f8de9b16 100644
--- a/redis/commands/scripting/script-load.mdx
+++ b/redis/commands/scripting/script-load.mdx
@@ -3,7 +3,11 @@ title: "SCRIPT LOAD"
 description: "Load script into cache."
 ---
 
-Use `SCRIPT LOAD` to load script into cache.
+Use `SCRIPT LOAD` to compile a script and put it in the server's script cache without running it.
+
+The reply is the script's SHA1 digest, which is what [`EVALSHA`](/redis/commands/scripting/evalsha) takes. Loading the same script twice is harmless and always yields the same digest, so applications typically load their scripts once at startup and then call them by digest.
+
+The cache is lost on restart and cleared by [`SCRIPT FLUSH`](/redis/commands/scripting/script-flush), so keep the script source available and be ready to handle a `NOSCRIPT` error by loading it again.
 
 ## Syntax
 
diff --git a/redis/commands/search/search-aggregate.mdx b/redis/commands/search/search-aggregate.mdx
index 90a40bec7..4139058d2 100644
--- a/redis/commands/search/search-aggregate.mdx
+++ b/redis/commands/search/search-aggregate.mdx
@@ -5,6 +5,12 @@ description: "Compute analytics over matching documents."
 
 Use `SEARCH.AGGREGATE` to compute metrics and buckets over matching documents.
 
+The command takes two JSON arguments. The first is a filter, in the same language as [`SEARCH.QUERY`](/redis/commands/search/search-query), which selects the documents to aggregate; pass `'{}'` to cover the whole index. The second describes the aggregations to compute, as named entries such as `{"avg_price": {"$avg": {"field": "price"}}}`.
+
+Metric operators like `$avg`, `$sum`, `$min`, `$max`, `$stats`, and `$cardinality` reduce the selected documents to a single number, while bucket operators like `$terms`, `$range`, `$histogram`, and `$dateHistogram` group them and report a count per bucket. Bucket operators accept nested `$aggs`, so you can compute a metric inside each bucket, for example the average price per category, and several aggregations can be requested in one call since they all run over the same selected document set.
+
+See [Aggregations](/redis/search/aggregations) for the full operator reference and examples.
+
 ## Syntax
 
 ```redis
diff --git a/redis/commands/search/search-aliasadd.mdx b/redis/commands/search/search-aliasadd.mdx
index 7baecf1d8..7e7959fbb 100644
--- a/redis/commands/search/search-aliasadd.mdx
+++ b/redis/commands/search/search-aliasadd.mdx
@@ -5,6 +5,8 @@ description: "Create or update a search index alias."
 
 Use `SEARCH.ALIASADD` to create an alias or update an existing alias to point to a search index.
 
+An alias is a stable name that queries can use in place of a real index name, so the index behind it can be replaced without touching application code. Pointing an existing alias at a different index is atomic, which is what makes zero-downtime reindexing possible: build the new index under a fresh name, then move the alias to it in one step.
+
 See [Aliases](/redis/search/aliases#adding-an-alias) for feature examples, including zero-downtime index swaps.
 
 The target name is not required to exist when the alias is created, so aliases can temporarily be dangling. Most commands resolve aliases, but [`SEARCH.DROP`](/redis/commands/search/search-drop) always uses a literal index name.
diff --git a/redis/commands/search/search-aliasdel.mdx b/redis/commands/search/search-aliasdel.mdx
index e081a67f3..712b748d6 100644
--- a/redis/commands/search/search-aliasdel.mdx
+++ b/redis/commands/search/search-aliasdel.mdx
@@ -5,6 +5,8 @@ description: "Delete a search index alias."
 
 Use `SEARCH.ALIASDEL` to remove a search index alias.
 
+Only the alias is removed: the index it pointed to, and the documents indexed in it, are untouched and remain reachable under their real name. Queries that still use the alias fail once it is gone.
+
 See [Deleting an Alias](/redis/search/aliases#deleting-an-alias) for the feature guide.
 
 ## Syntax
diff --git a/redis/commands/search/search-count.mdx b/redis/commands/search/search-count.mdx
index 0d5f25e5e..cb202342d 100644
--- a/redis/commands/search/search-count.mdx
+++ b/redis/commands/search/search-count.mdx
@@ -5,6 +5,8 @@ description: "Count documents matching a query."
 
 Use `SEARCH.COUNT` to count documents matching a query without retrieving them.
 
+The filter is the same JSON object that [`SEARCH.QUERY`](/redis/commands/search/search-query) takes, but only the number of matching documents is computed and returned, so nothing depends on the size of the result and no `LIMIT` gets in the way of the total. That makes it the right command for result counters, pagination totals, and cheap existence checks over a filter.
+
 See [Counting](/redis/search/counting) for feature examples and common use cases.
 
 ## Syntax
diff --git a/redis/commands/search/search-create.mdx b/redis/commands/search/search-create.mdx
index 87559c3c2..7b2114199 100644
--- a/redis/commands/search/search-create.mdx
+++ b/redis/commands/search/search-create.mdx
@@ -5,6 +5,10 @@ description: "Create a search index."
 
 Use `SEARCH.CREATE` to create a search index over JSON, hash, or string values.
 
+`ON` names the type of key to index and `PREFIX` the key prefixes to watch, so the index covers exactly the keys that match both, including keys written after it was created. The `SCHEMA` then declares which fields are searchable and how: `TEXT` fields are analyzed for full-text search, with `NOSTEM` and `NOTOKENIZE` to turn parts of that off, numeric, boolean, and date fields are matched exactly and can be marked `FAST` to make them usable for sorting and scoring, and `KEYWORD` and `FACET` fields are kept whole for exact matching and faceting. `FROM` maps a schema field to a differently named field in the document.
+
+Creating an index starts an initial scan of the matching keys, which `SKIPINITIALSCAN` skips when you only want to index data written from now on; [`SEARCH.REINDEX`](/redis/commands/search/search-reindex) can run that scan later. `EXISTSOK` makes the command succeed instead of failing when the index already exists.
+
 See [Index Management](/redis/search/index-management#creating-an-index) for a feature-level guide to creating indexes and [Schema Definition](/redis/search/schema-definition) for field types and schema design.
 
 <Note>
diff --git a/redis/commands/search/search-describe.mdx b/redis/commands/search/search-describe.mdx
index 21526a295..b0e9b9c5a 100644
--- a/redis/commands/search/search-describe.mdx
+++ b/redis/commands/search/search-describe.mdx
@@ -5,6 +5,8 @@ description: "Return metadata about a search index."
 
 Use `SEARCH.DESCRIBE` to return metadata about a search index.
 
+The reply reports how the index is defined, the key type and prefixes it covers, and the fields in its schema with their types and options, along with its current state such as the number of indexed documents. It is the way to confirm what an index actually indexes before writing queries against it, and to check whether a schema change was applied.
+
 See [Describing an Index](/redis/search/index-management#describing-an-index) for the feature guide.
 
 The command accepts an index name or alias. When an alias is used, the response describes its target and reports the target's index name.
diff --git a/redis/commands/search/search-drop.mdx b/redis/commands/search/search-drop.mdx
index fa68fe86c..70b9ec5e8 100644
--- a/redis/commands/search/search-drop.mdx
+++ b/redis/commands/search/search-drop.mdx
@@ -5,6 +5,8 @@ description: "Drop a search index without deleting its keys."
 
 Use `SEARCH.DROP` to remove a search index. The underlying Redis keys are not deleted.
 
+Only the index and its internal structures go away, so the documents themselves stay exactly as they are and can be indexed again later by creating a new index over the same prefixes. Queries against the dropped name fail from then on.
+
 See [Dropping an Index](/redis/search/index-management#dropping-an-index) for the feature guide.
 
 `SEARCH.DROP` does not resolve aliases: `<name>` is always treated as the literal index name. Aliases that point to a dropped index are not removed automatically.
diff --git a/redis/commands/search/search-listaliases.mdx b/redis/commands/search/search-listaliases.mdx
index c9cc35296..10b5e8504 100644
--- a/redis/commands/search/search-listaliases.mdx
+++ b/redis/commands/search/search-listaliases.mdx
@@ -5,6 +5,8 @@ description: "List search index aliases."
 
 Use `SEARCH.LISTALIASES` to return all aliases and the indexes they point to.
 
+The reply pairs each alias with its target index name, which is how you check what an alias currently resolves to before or after swapping it. Aliases whose target no longer exists are still listed, since an alias may point at a name that has not been created yet.
+
 See [Listing Aliases](/redis/search/aliases#listing-aliases) for the feature guide.
 
 ## Syntax
diff --git a/redis/commands/search/search-listindexes.mdx b/redis/commands/search/search-listindexes.mdx
index 404233bc1..f3a81cca0 100644
--- a/redis/commands/search/search-listindexes.mdx
+++ b/redis/commands/search/search-listindexes.mdx
@@ -5,6 +5,8 @@ description: "List search indexes in the database."
 
 Use `SEARCH.LISTINDEXES` to list search indexes in the database.
 
+`MATCH` filters index names with a glob-style pattern, while `LIMIT` and `OFFSET` page through the reply, which keeps the command usable on a database with many indexes. Only index names are returned; use [`SEARCH.DESCRIBE`](/redis/commands/search/search-describe) to see an index's schema and settings.
+
 See [Listing Indexes](/redis/search/index-management#listing-indexes) for the feature guide.
 
 ## Syntax
diff --git a/redis/commands/search/search-query.mdx b/redis/commands/search/search-query.mdx
index 5d5ad6497..f111b6125 100644
--- a/redis/commands/search/search-query.mdx
+++ b/redis/commands/search/search-query.mdx
@@ -5,6 +5,12 @@ description: "Search documents with a JSON filter."
 
 Use `SEARCH.QUERY` to search for documents matching a JSON filter.
 
+The filter is a JSON object naming index fields and the values to match, so `'{"name": "headphones", "inStock": true}'` combines conditions with an implicit AND. Text fields are matched with the analysis configured in the schema while other types are matched exactly, and operators such as `$fuzzy`, `$prefix`, `$range`, `$or`, and `$mustNot` cover the cases where plain field matching is not enough. Querying an index that does not exist returns null.
+
+Results come back ordered by relevance score by default. `ORDERBY` sorts by a `FAST` field instead, `LIMIT` and `OFFSET` page through the matches, `SELECT` and `NOCONTENT` cut the payload down to the fields you need, `HIGHLIGHT` wraps the matched terms in tags for display, and `SCOREFUNC` blends numeric fields such as popularity or recency into the relevance score.
+
+See [Querying and filtering](/redis/search/querying) for the full filter syntax and worked examples, and [`SEARCH.COUNT`](/redis/commands/search/search-count) when you only need the number of matches.
+
 ## Syntax
 
 ```redis
diff --git a/redis/commands/server/acl.mdx b/redis/commands/server/acl.mdx
index a8b40a2f8..98786a1dd 100644
--- a/redis/commands/server/acl.mdx
+++ b/redis/commands/server/acl.mdx
@@ -3,7 +3,13 @@ title: "ACL"
 description: "Manage access control list."
 ---
 
-Use `ACL` to manage access control list.
+Use `ACL` to inspect and manage the users, rules, and permissions of the database's access control list.
+
+`SETUSER` creates or updates a user and applies rules from left to right: rules enable or disable the user (`on`, `off`), set passwords (`>password`, `<password`), and grant or revoke access to commands (`+get`, `-@admin`) and to key patterns (`~cache:*`). `GETUSER` shows the resulting rules for one user, `USERS` and `LIST` enumerate users in short and full form, and `DELUSER` removes them. `WHOAMI` reports the user the current connection is authenticated as, `CAT` lists the command categories that can be used in rules, and `GENPASS` returns a cryptographically strong random password. `LOG` shows recent authentication and permission failures, which is where to look when a client is unexpectedly denied, and `RESET` on that subcommand clears it. `LOAD` and `SAVE` reload and persist the ACL file.
+
+Upstash adds two deployment-specific forms: `RESTTOKEN` returns the REST token of an existing user, given that user's password, and `GENTOKEN` builds a token for a username and password pair, generating a strong password when none is given, so the token can be passed to `SETUSER` as the user's password. Together they are how an ACL user is given access to the REST API alongside the TCP endpoint.
+
+Changes take effect immediately on new and existing connections, so a rule that narrows access can lock out a running application; check with `GETUSER` before applying it broadly.
 
 ## Syntax
 
diff --git a/redis/commands/server/command.mdx b/redis/commands/server/command.mdx
index 5362f62a5..80e854d01 100644
--- a/redis/commands/server/command.mdx
+++ b/redis/commands/server/command.mdx
@@ -3,7 +3,9 @@ title: "COMMAND"
 description: "Get command metadata."
 ---
 
-Use `COMMAND` to get command metadata.
+Use `COMMAND` to get metadata about the commands the server supports, such as their arity, flags, and key positions. Client libraries call it during connection setup to discover how to route commands and where their keys are.
+
+The current Upstash deployment accepts the command for client compatibility but returns an empty array rather than exposing the server command table, so clients fall back to their built-in command metadata.
 
 ## Syntax
 
diff --git a/redis/commands/server/config-get.mdx b/redis/commands/server/config-get.mdx
index 58b7b8b7f..468b44020 100644
--- a/redis/commands/server/config-get.mdx
+++ b/redis/commands/server/config-get.mdx
@@ -3,7 +3,11 @@ title: "CONFIG GET"
 description: "Read runtime configuration."
 ---
 
-Use `CONFIG GET` to read runtime configuration.
+Use `CONFIG GET` to read runtime configuration parameters.
+
+Parameter names may contain glob-style patterns, so one call can fetch a family of settings, and the reply is a flat array of alternating names and values in both RESP2 and RESP3.
+
+This deployment exposes only `notify-keyspace-events`, which controls the keyspace notifications published on pub/sub. Other names simply return no matching entries rather than an error, so check the reply for the parameter you asked about instead of assuming it was present.
 
 ## Syntax
 
diff --git a/redis/commands/server/config-set.mdx b/redis/commands/server/config-set.mdx
index a7fbf04c2..894d8acdc 100644
--- a/redis/commands/server/config-set.mdx
+++ b/redis/commands/server/config-set.mdx
@@ -3,7 +3,11 @@ title: "CONFIG SET"
 description: "Change runtime configuration."
 ---
 
-Use `CONFIG SET` to change runtime configuration.
+Use `CONFIG SET` to change runtime configuration parameters without restarting.
+
+This deployment permits changes only to `notify-keyspace-events`, which selects the keyspace and keyevent notifications the server publishes: the value is a set of flag characters, such as `KEA` for everything, or `Kg$` for generic and string keyspace events. Any other parameter returns an error.
+
+Several parameter and value pairs can be given in one call, and they are processed from left to right, so if a later pair is rejected an earlier change may already have taken effect.
 
 ## Syntax
 
diff --git a/redis/commands/server/dbsize.mdx b/redis/commands/server/dbsize.mdx
index 931a9092e..450e0e58c 100644
--- a/redis/commands/server/dbsize.mdx
+++ b/redis/commands/server/dbsize.mdx
@@ -3,7 +3,9 @@ title: "DBSIZE"
 description: "Get number of keys in database."
 ---
 
-Use `DBSIZE` to get number of keys in database.
+Use `DBSIZE` to get the number of keys stored in the database.
+
+The count covers keys of every type, and keys whose expiration has passed but that have not been removed yet may still be included, so treat the number as an accurate but momentary figure rather than an exact one. It is the quick way to see how a keyspace is growing, and unlike [`KEYS`](/redis/commands/generic/keys) it does not build a list of key names to do so.
 
 ## Syntax
 
diff --git a/redis/commands/server/flushall.mdx b/redis/commands/server/flushall.mdx
index dfced8b51..9e555371d 100644
--- a/redis/commands/server/flushall.mdx
+++ b/redis/commands/server/flushall.mdx
@@ -3,7 +3,11 @@ title: "FLUSHALL"
 description: "Delete all keys in all databases."
 ---
 
-Use `FLUSHALL` to delete all keys in all databases.
+Use `FLUSHALL` to delete every key in every database.
+
+Upstash exposes a single logical database, so `FLUSHALL` and [`FLUSHDB`](/redis/commands/server/flushdb) have the same effect here. `ASYNC` frees the memory in a background thread, which returns faster on large datasets, while `SYNC` frees it before replying.
+
+The deletion is immediate and irreversible: there is no confirmation step and nothing to undo. Keep it out of application code, run it only against disposable databases, and require an explicit operator action wherever tooling exposes it.
 
 ## Syntax
 
diff --git a/redis/commands/server/flushdb.mdx b/redis/commands/server/flushdb.mdx
index 9224d5227..b682701f2 100644
--- a/redis/commands/server/flushdb.mdx
+++ b/redis/commands/server/flushdb.mdx
@@ -3,7 +3,11 @@ title: "FLUSHDB"
 description: "Delete all keys in current database."
 ---
 
-Use `FLUSHDB` to delete all keys in current database.
+Use `FLUSHDB` to delete every key in the current database.
+
+Since Upstash exposes a single logical database, this removes everything, exactly like [`FLUSHALL`](/redis/commands/server/flushall). `ASYNC` frees the memory in a background thread and `SYNC` frees it before replying.
+
+The deletion is immediate and irreversible. It is a convenient way to reset a test database between runs, and it should never be reachable from application code that runs against production data.
 
 ## Syntax
 
diff --git a/redis/commands/server/info.mdx b/redis/commands/server/info.mdx
index a7c5929e8..a6f717bf8 100644
--- a/redis/commands/server/info.mdx
+++ b/redis/commands/server/info.mdx
@@ -3,7 +3,11 @@ title: "INFO"
 description: "Get server statistics and information."
 ---
 
-Use `INFO` to get server statistics and information.
+Use `INFO` to get statistics and information about the server.
+
+The reply groups fields into sections such as `server`, `clients`, `memory`, `stats`, `replication`, and `keyspace`, and passing a section name limits the reply to that one. It is the usual source for operational numbers such as connected clients, memory in use, hit and miss counts, and the number of keys per database.
+
+On Upstash, `default` and `all` return the same set of sections, and a section name that is not supported produces only its heading. The reply is a CRLF-delimited text report rather than a RESP map, so parse it defensively, since fields may be added over time.
 
 ## Syntax
 
diff --git a/redis/commands/server/monitor.mdx b/redis/commands/server/monitor.mdx
index e1e76d8b6..1b1a85659 100644
--- a/redis/commands/server/monitor.mdx
+++ b/redis/commands/server/monitor.mdx
@@ -3,7 +3,11 @@ title: "MONITOR"
 description: "Stream all commands received."
 ---
 
-Use `MONITOR` to stream all commands received.
+Use `MONITOR` to stream every command the server processes, as it happens, to the current connection.
+
+The connection turns into a continuous feed and stops accepting other commands, so it must be a dedicated one; closing it is how you stop monitoring. Each line carries a timestamp, the client that sent the command, and the command with its arguments.
+
+It is a debugging tool: it shows the traffic of all clients, arguments included, so it can expose sensitive data, and the added work costs the server throughput while it is running. Use it briefly and against non-production data where possible.
 
 ## Syntax
 
diff --git a/redis/commands/server/time.mdx b/redis/commands/server/time.mdx
index f2bf97543..28e9d6d70 100644
--- a/redis/commands/server/time.mdx
+++ b/redis/commands/server/time.mdx
@@ -3,7 +3,9 @@ title: "TIME"
 description: "Get current server time."
 ---
 
-Use `TIME` to get current server time.
+Use `TIME` to read the server's clock.
+
+The reply has two values: the Unix time in seconds and the microseconds elapsed within the current second. Because it comes from the server, every client gets the same reference regardless of its own clock drift, which makes it the value to use when computing deadlines, measuring intervals, or writing timestamps that different machines must agree on.
 
 ## Syntax
 
diff --git a/redis/commands/set/overview.mdx b/redis/commands/set/overview.mdx
index 5ccf6426e..1fdfcc4a3 100644
--- a/redis/commands/set/overview.mdx
+++ b/redis/commands/set/overview.mdx
@@ -14,9 +14,9 @@ description: "Commands for storing and manipulating unordered collections of uni
 <Card title="SINTERSTORE" href="/redis/commands/set/sinterstore">Store set intersection</Card>
 <Card title="SISMEMBER" href="/redis/commands/set/sismember">Check if member exists in set</Card>
 <Card title="SMEMBERS" href="/redis/commands/set/smembers">Get all set members</Card>
-<Card title="SMISMEMBER" href="/redis/commands/set/smismember">Check multiple members</Card>
+<Card title="SMISMEMBER" href="/redis/commands/set/smismember">Check membership of several values</Card>
 <Card title="SMOVE" href="/redis/commands/set/smove">Move member between sets</Card>
-<Card title="SPOP" href="/redis/commands/set/spop">Remove random members</Card>
+<Card title="SPOP" href="/redis/commands/set/spop">Remove and return random members</Card>
 <Card title="SRANDMEMBER" href="/redis/commands/set/srandmember">Get random members</Card>
 <Card title="SREM" href="/redis/commands/set/srem">Remove members from a set</Card>
 <Card title="SSCAN" href="/redis/commands/set/sscan">Incrementally iterate set members</Card>
diff --git a/redis/commands/set/sadd.mdx b/redis/commands/set/sadd.mdx
index 7806abfea..cded33de3 100644
--- a/redis/commands/set/sadd.mdx
+++ b/redis/commands/set/sadd.mdx
@@ -3,7 +3,9 @@ title: "SADD"
 description: "Add members to a set."
 ---
 
-Use `SADD` to add members to a set.
+Use `SADD` to add one or more members to a set, creating it when the key does not exist.
+
+A set holds unique, unordered members, so adding a member that is already there changes nothing, and the reply counts only the members that were actually new. That count is what makes the command a cheap deduplicator: a reply of `1` means this caller was the first to see the value, which is enough to decide whether to process an event or ignore it as a repeat.
 
 ## Syntax
 
diff --git a/redis/commands/set/scard.mdx b/redis/commands/set/scard.mdx
index 8b7e0db80..51b20138b 100644
--- a/redis/commands/set/scard.mdx
+++ b/redis/commands/set/scard.mdx
@@ -3,7 +3,9 @@ title: "SCARD"
 description: "Get set cardinality."
 ---
 
-Use `SCARD` to get set cardinality.
+Use `SCARD` to get the number of members in a set.
+
+The reply is `0` when the key does not exist. The size is maintained by Redis rather than counted on demand, so the command is cheap on sets of any size, which makes it the right way to check how large a set has become before reading it with [`SMEMBERS`](/redis/commands/set/smembers).
 
 ## Syntax
 
diff --git a/redis/commands/set/sdiff.mdx b/redis/commands/set/sdiff.mdx
index 270b761ab..890467f98 100644
--- a/redis/commands/set/sdiff.mdx
+++ b/redis/commands/set/sdiff.mdx
@@ -3,7 +3,11 @@ title: "SDIFF"
 description: "Get set difference."
 ---
 
-Use `SDIFF` to get set difference.
+Use `SDIFF` to get the members of the first set that are not present in any of the other sets.
+
+Keys that do not exist count as empty sets, so a missing first key yields an empty result. The difference is computed on the fly and nothing is stored; use [`SDIFFSTORE`](/redis/commands/set/sdiffstore) to keep the result.
+
+It answers questions of the form "who is in A but not in B", such as users who signed up but never converted. The cost grows with the size of the sets involved, so on large sets prefer storing the result and reusing it.
 
 ## Syntax
 
diff --git a/redis/commands/set/sdiffstore.mdx b/redis/commands/set/sdiffstore.mdx
index ff1044cab..d9b45a9c7 100644
--- a/redis/commands/set/sdiffstore.mdx
+++ b/redis/commands/set/sdiffstore.mdx
@@ -3,7 +3,11 @@ title: "SDIFFSTORE"
 description: "Store set difference."
 ---
 
-Use `SDIFFSTORE` to store set difference.
+Use `SDIFFSTORE` to compute the difference between sets and store it in another key.
+
+The destination holds the members of the first source set that are absent from all the others. It is overwritten if it already exists, and deleted when the result is empty. The reply is the number of members stored.
+
+Storing rather than returning the result is what you want when the difference is large or is used more than once, since the destination is an ordinary set that can be paged through or fed into further set operations.
 
 ## Syntax
 
diff --git a/redis/commands/set/sinter.mdx b/redis/commands/set/sinter.mdx
index f85f64ac1..f68c093dd 100644
--- a/redis/commands/set/sinter.mdx
+++ b/redis/commands/set/sinter.mdx
@@ -3,7 +3,11 @@ title: "SINTER"
 description: "Get set intersection."
 ---
 
-Use `SINTER` to get set intersection.
+Use `SINTER` to get the members present in every one of the given sets.
+
+A key that does not exist counts as an empty set, which makes the whole intersection empty. The result is computed on each call and not stored; use [`SINTERSTORE`](/redis/commands/set/sinterstore) to keep it, or [`SINTERCARD`](/redis/commands/set/sintercard) when only the number of common members matters.
+
+Intersections express "and" queries over sets, such as the users who are in both a campaign audience and a paying-customer set.
 
 ## Syntax
 
diff --git a/redis/commands/set/sintercard.mdx b/redis/commands/set/sintercard.mdx
index 2e7af9bdb..b0faaa274 100644
--- a/redis/commands/set/sintercard.mdx
+++ b/redis/commands/set/sintercard.mdx
@@ -3,7 +3,11 @@ title: "SINTERCARD"
 description: "Get intersection cardinality."
 ---
 
-Use `SINTERCARD` to get intersection cardinality.
+Use `SINTERCARD` to get the number of members that the given sets have in common, without building the intersection.
+
+`<numkeys>` states how many keys follow. `LIMIT` stops counting once that many common members have been found and returns the limit, which turns an expensive full intersection into a cheap "do these sets share at least N members" test. `LIMIT 0` means no limit.
+
+Since nothing is transferred beyond the count, this is much lighter than running [`SINTER`](/redis/commands/set/sinter) and measuring the reply.
 
 ## Syntax
 
diff --git a/redis/commands/set/sinterstore.mdx b/redis/commands/set/sinterstore.mdx
index 2ca7eb1a5..5fb596989 100644
--- a/redis/commands/set/sinterstore.mdx
+++ b/redis/commands/set/sinterstore.mdx
@@ -3,7 +3,9 @@ title: "SINTERSTORE"
 description: "Store set intersection."
 ---
 
-Use `SINTERSTORE` to store set intersection.
+Use `SINTERSTORE` to compute the intersection of sets and store it in another key.
+
+The destination is overwritten if it exists and deleted when the intersection is empty, and the reply is the number of members stored. Materializing the result pays off when the same intersection is read repeatedly or feeds further set operations, since the destination is an ordinary set.
 
 ## Syntax
 
diff --git a/redis/commands/set/sismember.mdx b/redis/commands/set/sismember.mdx
index 5b91af3c2..03c76ced5 100644
--- a/redis/commands/set/sismember.mdx
+++ b/redis/commands/set/sismember.mdx
@@ -3,7 +3,9 @@ title: "SISMEMBER"
 description: "Check if member exists in set."
 ---
 
-Use `SISMEMBER` to check if member exists in set.
+Use `SISMEMBER` to check whether a value is a member of a set.
+
+The reply is `1` when it is and `0` when it is not or the key does not exist. The check is a constant-time lookup and transfers nothing but the answer, which is why sets are the right structure for membership questions such as permission or blocklist checks. Use [`SMISMEMBER`](/redis/commands/set/smismember) to test several values in one call.
 
 ## Syntax
 
diff --git a/redis/commands/set/smembers.mdx b/redis/commands/set/smembers.mdx
index 079b0d69e..a3626c0f3 100644
--- a/redis/commands/set/smembers.mdx
+++ b/redis/commands/set/smembers.mdx
@@ -3,7 +3,9 @@ title: "SMEMBERS"
 description: "Get all set members."
 ---
 
-Use `SMEMBERS` to get all set members.
+Use `SMEMBERS` to get every member of a set.
+
+A missing key returns an empty result, and members come back in no particular order, since sets are unordered. The whole set is transferred in one reply, so on large sets prefer [`SSCAN`](/redis/commands/set/sscan), which walks the members in batches, and use [`SISMEMBER`](/redis/commands/set/sismember) when you only want to test membership.
 
 ## Syntax
 
diff --git a/redis/commands/set/smismember.mdx b/redis/commands/set/smismember.mdx
index 444443f10..fba424b96 100644
--- a/redis/commands/set/smismember.mdx
+++ b/redis/commands/set/smismember.mdx
@@ -1,9 +1,11 @@
 ---
 title: "SMISMEMBER"
-description: "Check multiple members."
+description: "Check membership of several values."
 ---
 
-Use `SMISMEMBER` to check multiple members.
+Use `SMISMEMBER` to check several values for membership in a set in one call.
+
+The reply holds one `1` or `0` per value, in the order given, so it lines up with your input list. A missing key yields all zeros rather than an error. It replaces a series of [`SISMEMBER`](/redis/commands/set/sismember) round trips, which matters when checking a batch of ids against a blocklist or an entitlement set.
 
 ## Syntax
 
diff --git a/redis/commands/set/smove.mdx b/redis/commands/set/smove.mdx
index 9d0d69f62..ae13f4e39 100644
--- a/redis/commands/set/smove.mdx
+++ b/redis/commands/set/smove.mdx
@@ -3,7 +3,11 @@ title: "SMOVE"
 description: "Move member between sets."
 ---
 
-Use `SMOVE` to move member between sets.
+Use `SMOVE` to move a member from one set to another atomically.
+
+The reply is `1` when the member was moved and `0` when it was not in the source set, in which case nothing changes. If the member already exists in the destination it is simply removed from the source. The destination is created when it does not exist, and the source is deleted when its last member leaves.
+
+Because the removal and the insertion happen as one step, this is the safe way to move an item between states, such as from a pending set to a done set, without a window in which it is in both or in neither.
 
 ## Syntax
 
diff --git a/redis/commands/set/spop.mdx b/redis/commands/set/spop.mdx
index dcdd326c3..b8c94ce23 100644
--- a/redis/commands/set/spop.mdx
+++ b/redis/commands/set/spop.mdx
@@ -1,9 +1,13 @@
 ---
 title: "SPOP"
-description: "Remove random members."
+description: "Remove and return random members."
 ---
 
-Use `SPOP` to remove random members.
+Use `SPOP` to remove and return random members of a set.
+
+Without a count one member is returned, or null when the key does not exist. With a count, up to that many distinct members are removed at once, capped at the size of the set, and the key is deleted when the last member is taken.
+
+Since the read and the removal are atomic, no two callers can get the same member, which makes a set usable as a pool of unique items to hand out, such as invitation codes or shard assignments. Use [`SRANDMEMBER`](/redis/commands/set/srandmember) when the members should stay in the set.
 
 ## Syntax
 
diff --git a/redis/commands/set/srandmember.mdx b/redis/commands/set/srandmember.mdx
index a5a9e02db..aafa3a73b 100644
--- a/redis/commands/set/srandmember.mdx
+++ b/redis/commands/set/srandmember.mdx
@@ -3,7 +3,11 @@ title: "SRANDMEMBER"
 description: "Get random members."
 ---
 
-Use `SRANDMEMBER` to get random members.
+Use `SRANDMEMBER` to get random members of a set without removing them.
+
+Without a count one member is returned, or null when the key does not exist. A positive count returns up to that many distinct members, capped at the size of the set, while a negative count returns exactly that many members chosen independently, so the same member can appear more than once.
+
+This is the command for sampling, random selection, and inspecting an unfamiliar set. Use [`SPOP`](/redis/commands/set/spop) when the chosen members must be consumed.
 
 ## Syntax
 
diff --git a/redis/commands/set/srem.mdx b/redis/commands/set/srem.mdx
index a26b5ff7e..74cdd57ab 100644
--- a/redis/commands/set/srem.mdx
+++ b/redis/commands/set/srem.mdx
@@ -3,7 +3,9 @@ title: "SREM"
 description: "Remove members from a set."
 ---
 
-Use `SREM` to remove members from a set.
+Use `SREM` to remove one or more members from a set.
+
+The reply counts only the members that were actually present, so removing something that is already gone is not an error. The key is deleted when its last member is removed, which is why a set that has been fully drained no longer exists rather than existing as an empty set.
 
 ## Syntax
 
diff --git a/redis/commands/set/sscan.mdx b/redis/commands/set/sscan.mdx
index 10cd7a1ea..09f1f6b03 100644
--- a/redis/commands/set/sscan.mdx
+++ b/redis/commands/set/sscan.mdx
@@ -3,7 +3,11 @@ title: "SSCAN"
 description: "Incrementally iterate set members."
 ---
 
-Use `SSCAN` to incrementally iterate set members.
+Use `SSCAN` to iterate the members of a set in batches instead of reading them all at once.
+
+Each call takes a cursor and returns the next cursor together with a batch of members. Start at cursor `0` and keep calling with the cursor from the previous reply until the server returns `0`, which ends the iteration. `MATCH` filters members with a glob-style pattern and `COUNT` hints at how much work each call should do.
+
+Filtering happens after a batch is read, so a call can come back empty while the cursor is still non-zero: only the cursor tells you the iteration is over. Members present for the whole iteration are returned at least once, while those added or removed while it runs may or may not appear, and a member can be returned more than once, so keep the processing idempotent.
 
 ## Syntax
 
diff --git a/redis/commands/set/sunion.mdx b/redis/commands/set/sunion.mdx
index bbcc7c9d7..a01819d6d 100644
--- a/redis/commands/set/sunion.mdx
+++ b/redis/commands/set/sunion.mdx
@@ -3,7 +3,9 @@ title: "SUNION"
 description: "Get set union."
 ---
 
-Use `SUNION` to get set union.
+Use `SUNION` to get every member that appears in at least one of the given sets.
+
+Duplicates across the sources collapse, since the result is itself a set, and keys that do not exist count as empty sets. The union is computed on each call and nothing is stored; use [`SUNIONSTORE`](/redis/commands/set/sunionstore) to keep the result. It answers "or" questions over sets, such as everyone reachable through any of several audiences.
 
 ## Syntax
 
diff --git a/redis/commands/set/sunionstore.mdx b/redis/commands/set/sunionstore.mdx
index 60d189e39..57be47736 100644
--- a/redis/commands/set/sunionstore.mdx
+++ b/redis/commands/set/sunionstore.mdx
@@ -3,7 +3,9 @@ title: "SUNIONSTORE"
 description: "Store set union."
 ---
 
-Use `SUNIONSTORE` to store set union.
+Use `SUNIONSTORE` to compute the union of sets and store it in another key.
+
+The destination is overwritten if it exists and deleted when the union is empty, and the reply is the number of members stored. Materializing the union is the usual way to build a combined audience once and then intersect or difference it with other sets, instead of recomputing it on every query.
 
 ## Syntax
 
diff --git a/redis/commands/sorted-set/bzmpop.mdx b/redis/commands/sorted-set/bzmpop.mdx
index 850016718..5083edf9a 100644
--- a/redis/commands/sorted-set/bzmpop.mdx
+++ b/redis/commands/sorted-set/bzmpop.mdx
@@ -5,6 +5,10 @@ description: "Pop from the first non-empty sorted set, blocking until one arrive
 
 Use `BZMPOP` to pop members from the first non-empty sorted set among several, blocking until one has members or the timeout expires.
 
+It is the blocking form of [`ZMPOP`](/redis/commands/sorted-set/zmpop): keys are examined in the order given, so earlier keys act as higher priority queues, `MIN` or `MAX` chooses whether the lowest or highest scoring members are taken, and `COUNT` sets how many. The reply names the key that was popped from along with the members and their scores.
+
+The timeout is in seconds, may be fractional, and `0` waits indefinitely; when it expires the reply is null. This is what a worker uses to wait on several priority queues at once without polling.
+
 ## Syntax
 
 ```redis
@@ -18,7 +22,7 @@ BZMPOP <timeout> <numkeys> <key> [<key> ...] (MIN | MAX) [COUNT <count>]
 | `<timeout>` | Yes | No | Seconds to block; `0` blocks indefinitely. |
 | `<numkeys>` | Yes | No | Number of key arguments that follow. |
 | `<key>` | Yes | Yes | Redis key targeted by the command. |
-| `(MIN \| MAX)` | Yes | No | Choose one form: `MIN`; `MAX`. |
+| `(MIN \| MAX)` | Yes | No | Which members to pop: `MIN` (lowest scores first) or `MAX` (highest scores first). |
 | `COUNT <count>` | No | No | Maximum number of members to pop. |
 
 ## Important points
diff --git a/redis/commands/sorted-set/bzpopmax.mdx b/redis/commands/sorted-set/bzpopmax.mdx
index c5b97a869..666b36b87 100644
--- a/redis/commands/sorted-set/bzpopmax.mdx
+++ b/redis/commands/sorted-set/bzpopmax.mdx
@@ -5,6 +5,10 @@ description: "Pop the highest-scoring member, blocking until one arrives."
 
 Use `BZPOPMAX` to pop the highest-scoring member from the first non-empty sorted set, blocking until one has a member or the timeout expires.
 
+It is the blocking form of [`ZPOPMAX`](/redis/commands/sorted-set/zpopmax) and accepts several keys, which are checked in the order given. The reply names the key the member came from together with the member and its score.
+
+The timeout is in seconds, may be fractional, and `0` waits indefinitely; when it expires the reply is null. With the score used as a priority, this turns a sorted set into a priority queue whose consumers wait for work instead of polling, and clients blocked on the same key are served in the order they started waiting.
+
 ## Syntax
 
 ```redis
diff --git a/redis/commands/sorted-set/bzpopmin.mdx b/redis/commands/sorted-set/bzpopmin.mdx
index 45d560114..9e4d44f4f 100644
--- a/redis/commands/sorted-set/bzpopmin.mdx
+++ b/redis/commands/sorted-set/bzpopmin.mdx
@@ -5,6 +5,10 @@ description: "Pop the lowest-scoring member, blocking until one arrives."
 
 Use `BZPOPMIN` to pop the lowest-scoring member from the first non-empty sorted set, blocking until one has a member or the timeout expires.
 
+It is the blocking form of [`ZPOPMIN`](/redis/commands/sorted-set/zpopmin) and accepts several keys, checked in the order given, with the reply naming the key the member came from along with the member and its score.
+
+The timeout is in seconds, may be fractional, and `0` waits indefinitely; when it expires the reply is null. Since the lowest score is popped first, a set scored by timestamp or priority number becomes a queue that hands out the most urgent item to whichever worker is waiting.
+
 ## Syntax
 
 ```redis
diff --git a/redis/commands/sorted-set/overview.mdx b/redis/commands/sorted-set/overview.mdx
index 4ed7fbeed..8cbabe64c 100644
--- a/redis/commands/sorted-set/overview.mdx
+++ b/redis/commands/sorted-set/overview.mdx
@@ -18,15 +18,15 @@ description: "Commands for storing and manipulating scored collections."
 <Card title="ZINTERCARD" href="/redis/commands/sorted-set/zintercard">Get intersection cardinality</Card>
 <Card title="ZINTERSTORE" href="/redis/commands/sorted-set/zinterstore">Store sorted set intersection</Card>
 <Card title="ZLEXCOUNT" href="/redis/commands/sorted-set/zlexcount">Count members in lex range</Card>
-<Card title="ZMPOP" href="/redis/commands/sorted-set/zmpop">Pop members from sorted sets</Card>
+<Card title="ZMPOP" href="/redis/commands/sorted-set/zmpop">Pop from the first non-empty sorted set</Card>
 <Card title="ZMSCORE" href="/redis/commands/sorted-set/zmscore">Get scores of multiple members</Card>
 <Card title="ZPOPMAX" href="/redis/commands/sorted-set/zpopmax">Pop members with highest scores</Card>
 <Card title="ZPOPMIN" href="/redis/commands/sorted-set/zpopmin">Pop members with lowest scores</Card>
 <Card title="ZRANDMEMBER" href="/redis/commands/sorted-set/zrandmember">Get random members</Card>
-<Card title="ZRANGE" href="/redis/commands/sorted-set/zrange">Get members by index range</Card>
+<Card title="ZRANGE" href="/redis/commands/sorted-set/zrange">Get members by index, score, or lex range</Card>
 <Card title="ZRANGEBYLEX" href="/redis/commands/sorted-set/zrangebylex">Get members by lex range</Card>
 <Card title="ZRANGEBYSCORE" href="/redis/commands/sorted-set/zrangebyscore">Get members by score range</Card>
-<Card title="ZRANGESTORE" href="/redis/commands/sorted-set/zrangestore">Store range result</Card>
+<Card title="ZRANGESTORE" href="/redis/commands/sorted-set/zrangestore">Store the result of a range query</Card>
 <Card title="ZRANK" href="/redis/commands/sorted-set/zrank">Get member's rank</Card>
 <Card title="ZREM" href="/redis/commands/sorted-set/zrem">Remove members</Card>
 <Card title="ZREMRANGEBYLEX" href="/redis/commands/sorted-set/zremrangebylex">Remove members by lex range</Card>
diff --git a/redis/commands/sorted-set/zadd.mdx b/redis/commands/sorted-set/zadd.mdx
index c8979f823..a7afca0bf 100644
--- a/redis/commands/sorted-set/zadd.mdx
+++ b/redis/commands/sorted-set/zadd.mdx
@@ -3,7 +3,11 @@ title: "ZADD"
 description: "Add members with scores."
 ---
 
-Use `ZADD` to add members with scores.
+Use `ZADD` to add members with a score to a sorted set, or to change the score of members that are already there.
+
+Members are kept ordered by score, and members with equal scores are ordered lexicographically, which is what makes range queries by score or by member name possible. Scores are double precision floats and accept `+inf` and `-inf`. The key is created on first use, and the reply counts the members that were added.
+
+`NX` only adds new members and never changes an existing score, while `XX` only updates members that already exist. `GT` and `LT` update a score only when the new one is greater or less than the current one, which is how you keep a running maximum or minimum, such as a high score or an earliest deadline, without reading the old value first. `CH` makes the reply count every member that changed, added or updated, instead of only the new ones. `INCR` treats the given score as an increment and returns the member's new score, behaving like [`ZINCRBY`](/redis/commands/sorted-set/zincrby) for a single member and returning null when a condition prevented the change.
 
 ## Syntax
 
diff --git a/redis/commands/sorted-set/zcard.mdx b/redis/commands/sorted-set/zcard.mdx
index c796615db..f11148574 100644
--- a/redis/commands/sorted-set/zcard.mdx
+++ b/redis/commands/sorted-set/zcard.mdx
@@ -3,7 +3,9 @@ title: "ZCARD"
 description: "Get sorted set cardinality."
 ---
 
-Use `ZCARD` to get sorted set cardinality.
+Use `ZCARD` to get the number of members in a sorted set.
+
+The reply is `0` when the key does not exist. The size is maintained by Redis, so the command is cheap whatever the size of the set. Use [`ZCOUNT`](/redis/commands/sorted-set/zcount) when you need the number of members within a score range rather than the total.
 
 ## Syntax
 
diff --git a/redis/commands/sorted-set/zcount.mdx b/redis/commands/sorted-set/zcount.mdx
index d79be3b26..d7a73391a 100644
--- a/redis/commands/sorted-set/zcount.mdx
+++ b/redis/commands/sorted-set/zcount.mdx
@@ -3,7 +3,11 @@ title: "ZCOUNT"
 description: "Count members in score range."
 ---
 
-Use `ZCOUNT` to count members in score range.
+Use `ZCOUNT` to count the members of a sorted set whose score falls in a range.
+
+Both bounds are inclusive by default; prefix a bound with `(` to make it exclusive, and use `-inf` and `+inf` for open ends, so `ZCOUNT key (5 +inf` counts everything scored above 5. Redis finds the range by rank rather than scanning the whole set, so the count is fast even on large sets.
+
+With timestamps as scores this is how you count events in a time window without transferring them.
 
 ## Syntax
 
diff --git a/redis/commands/sorted-set/zdiff.mdx b/redis/commands/sorted-set/zdiff.mdx
index dc20c131a..a4fb6ff44 100644
--- a/redis/commands/sorted-set/zdiff.mdx
+++ b/redis/commands/sorted-set/zdiff.mdx
@@ -3,7 +3,11 @@ title: "ZDIFF"
 description: "Get sorted set difference."
 ---
 
-Use `ZDIFF` to get sorted set difference.
+Use `ZDIFF` to get the members of the first sorted set that do not appear in any of the others.
+
+`<numkeys>` states how many keys follow. Scores come from the first set and are returned only when `WITHSCORES` is given, and the result keeps the ordering of that set. Keys that do not exist count as empty.
+
+The result is computed on each call and not stored; use [`ZDIFFSTORE`](/redis/commands/sorted-set/zdiffstore) to keep it. This is how you exclude one group from a ranking, for example dropping already-seen items from a scored feed.
 
 ## Syntax
 
diff --git a/redis/commands/sorted-set/zdiffstore.mdx b/redis/commands/sorted-set/zdiffstore.mdx
index 24135e2e1..5a749fa4f 100644
--- a/redis/commands/sorted-set/zdiffstore.mdx
+++ b/redis/commands/sorted-set/zdiffstore.mdx
@@ -3,7 +3,11 @@ title: "ZDIFFSTORE"
 description: "Store sorted set difference."
 ---
 
-Use `ZDIFFSTORE` to store sorted set difference.
+Use `ZDIFFSTORE` to compute the difference between sorted sets and store it in another key.
+
+The destination receives the members of the first source that appear in none of the others, keeping their scores from that source. It is overwritten if it exists and deleted when the result is empty, and the reply is the number of members stored.
+
+Materializing the result is worthwhile when the same filtered ranking is read repeatedly or paged through, since the destination is an ordinary sorted set.
 
 ## Syntax
 
diff --git a/redis/commands/sorted-set/zincrby.mdx b/redis/commands/sorted-set/zincrby.mdx
index b4c0b277f..619ed4649 100644
--- a/redis/commands/sorted-set/zincrby.mdx
+++ b/redis/commands/sorted-set/zincrby.mdx
@@ -3,7 +3,11 @@ title: "ZINCRBY"
 description: "Increment member's score."
 ---
 
-Use `ZINCRBY` to increment member's score.
+Use `ZINCRBY` to add an increment to the score of a member of a sorted set.
+
+A member that is not there yet is created with the increment as its score, and a missing key is created too, so no initialization step is needed. The increment may be negative to move a member down. The reply is the new score.
+
+Because the update is atomic and the set stays ordered, this is the core operation behind leaderboards, vote counts, and any ranking that has to reflect concurrent updates: increment a member's score and read the position back with [`ZRANK`](/redis/commands/sorted-set/zrank) or the top of the ranking with [`ZRANGE`](/redis/commands/sorted-set/zrange).
 
 ## Syntax
 
diff --git a/redis/commands/sorted-set/zinter.mdx b/redis/commands/sorted-set/zinter.mdx
index f59f4c9ac..c929ccba9 100644
--- a/redis/commands/sorted-set/zinter.mdx
+++ b/redis/commands/sorted-set/zinter.mdx
@@ -3,7 +3,11 @@ title: "ZINTER"
 description: "Get sorted set intersection."
 ---
 
-Use `ZINTER` to get sorted set intersection.
+Use `ZINTER` to get the members that appear in every one of the given sorted sets.
+
+`<numkeys>` states how many keys follow. By default the score of each member in the result is the sum of its scores across all the inputs, which is what makes intersections useful for combining rankings. `WEIGHTS` multiplies each input's scores by a factor before they are combined, so one source can count more than another, and `AGGREGATE` replaces the sum with `MIN` or `MAX`. `WITHSCORES` returns the computed scores along with the members.
+
+The result is not stored; use [`ZINTERSTORE`](/redis/commands/sorted-set/zinterstore) to keep it or [`ZINTERCARD`](/redis/commands/sorted-set/zintercard) when only the size matters.
 
 ## Syntax
 
diff --git a/redis/commands/sorted-set/zintercard.mdx b/redis/commands/sorted-set/zintercard.mdx
index c7f47fa4a..0a77eb9f5 100644
--- a/redis/commands/sorted-set/zintercard.mdx
+++ b/redis/commands/sorted-set/zintercard.mdx
@@ -3,7 +3,9 @@ title: "ZINTERCARD"
 description: "Get intersection cardinality."
 ---
 
-Use `ZINTERCARD` to get intersection cardinality.
+Use `ZINTERCARD` to get the number of members that the given sorted sets have in common, without building the intersection.
+
+`<numkeys>` states how many keys follow. `LIMIT` stops the count once that many common members are found and returns the limit, which answers "do these sets overlap by at least N" far more cheaply than a full intersection; `LIMIT 0` means no limit. Only the count is computed and returned, so nothing is stored and no scores are transferred.
 
 ## Syntax
 
diff --git a/redis/commands/sorted-set/zinterstore.mdx b/redis/commands/sorted-set/zinterstore.mdx
index 915c1ddc9..0460fb414 100644
--- a/redis/commands/sorted-set/zinterstore.mdx
+++ b/redis/commands/sorted-set/zinterstore.mdx
@@ -3,7 +3,11 @@ title: "ZINTERSTORE"
 description: "Store sorted set intersection."
 ---
 
-Use `ZINTERSTORE` to store sorted set intersection.
+Use `ZINTERSTORE` to compute the intersection of sorted sets and store it in another key.
+
+The destination gets the members present in every input, scored by the sum of their scores by default, or by `MIN` or `MAX` when `AGGREGATE` is given, with `WEIGHTS` scaling each input beforehand. The destination is overwritten if it exists and deleted when the intersection is empty, and the reply is the number of members stored.
+
+This is how a combined ranking is built once, for instance blending a relevance score with a popularity score, and then paged through with [`ZRANGE`](/redis/commands/sorted-set/zrange).
 
 ## Syntax
 
diff --git a/redis/commands/sorted-set/zlexcount.mdx b/redis/commands/sorted-set/zlexcount.mdx
index 678f29be3..8c6e2b6cd 100644
--- a/redis/commands/sorted-set/zlexcount.mdx
+++ b/redis/commands/sorted-set/zlexcount.mdx
@@ -3,7 +3,11 @@ title: "ZLEXCOUNT"
 description: "Count members in lex range."
 ---
 
-Use `ZLEXCOUNT` to count members in lex range.
+Use `ZLEXCOUNT` to count the members of a sorted set that fall in a lexicographic range.
+
+Bounds are written as `[member` for inclusive and `(member` for exclusive, with `-` and `+` standing for the lowest and highest possible members, so `ZLEXCOUNT key [a (c` counts members from `a` up to but not including `c`.
+
+Lexicographic ordering only holds when every member of the set has the same score, which is the trick behind using a sorted set as a sorted index of strings; with mixed scores the result is not meaningful. Use [`ZRANGEBYLEX`](/redis/commands/sorted-set/zrangebylex) or [`ZRANGE`](/redis/commands/sorted-set/zrange) with `BYLEX` to retrieve the members themselves.
 
 ## Syntax
 
diff --git a/redis/commands/sorted-set/zmpop.mdx b/redis/commands/sorted-set/zmpop.mdx
index 0b1e0ddcd..c71c6f588 100644
--- a/redis/commands/sorted-set/zmpop.mdx
+++ b/redis/commands/sorted-set/zmpop.mdx
@@ -1,9 +1,13 @@
 ---
 title: "ZMPOP"
-description: "Pop members from sorted sets."
+description: "Pop from the first non-empty sorted set."
 ---
 
-Use `ZMPOP` to pop members from sorted sets.
+Use `ZMPOP` to pop members from the first of several sorted sets that is not empty.
+
+`<numkeys>` states how many keys follow, `MIN` or `MAX` chooses whether the lowest or the highest scoring members are taken, and `COUNT` sets how many to pop. Keys are examined in the order given and only the first non-empty one is touched, so listing a high priority queue first drains it before the others are considered.
+
+The reply names the key that was popped from along with the members and their scores, which matters when a worker watches several queues. When every key is empty the reply is null; use [`BZMPOP`](/redis/commands/sorted-set/bzmpop) to wait instead of returning.
 
 ## Syntax
 
@@ -17,7 +21,7 @@ ZMPOP <numkeys> <key> [<key> ...] (MIN | MAX) [COUNT <count>]
 | --- | --- | --- | --- |
 | `<numkeys>` | Yes | No | Number of key arguments that follow. |
 | `<key>` | Yes | Yes | Redis key targeted by the command. |
-| `(MIN \| MAX)` | Yes | No | Choose one form: `MIN`; `MAX`. |
+| `(MIN \| MAX)` | Yes | No | Which members to pop: `MIN` (lowest scores first) or `MAX` (highest scores first). |
 | `COUNT <count>` | No | No | Maximum number of members to pop. |
 
 ## Important points
diff --git a/redis/commands/sorted-set/zmscore.mdx b/redis/commands/sorted-set/zmscore.mdx
index 5a45f26cb..6a339293d 100644
--- a/redis/commands/sorted-set/zmscore.mdx
+++ b/redis/commands/sorted-set/zmscore.mdx
@@ -3,7 +3,9 @@ title: "ZMSCORE"
 description: "Get scores of multiple members."
 ---
 
-Use `ZMSCORE` to get scores of multiple members.
+Use `ZMSCORE` to get the scores of several members of a sorted set in one call.
+
+The reply holds one score per member, in the order requested, with null for members that are not in the set, so it lines up with your input list. A missing key yields all nulls rather than an error. It replaces a series of [`ZSCORE`](/redis/commands/sorted-set/zscore) round trips when you need to read a batch of scores, such as the current rating of every item on a page.
 
 ## Syntax
 
diff --git a/redis/commands/sorted-set/zpopmax.mdx b/redis/commands/sorted-set/zpopmax.mdx
index 056d93903..1d89f688e 100644
--- a/redis/commands/sorted-set/zpopmax.mdx
+++ b/redis/commands/sorted-set/zpopmax.mdx
@@ -3,7 +3,11 @@ title: "ZPOPMAX"
 description: "Pop members with highest scores."
 ---
 
-Use `ZPOPMAX` to pop members with highest scores.
+Use `ZPOPMAX` to remove and return the members with the highest scores in a sorted set.
+
+Without a count one member is returned with its score, and with a count up to that many are removed, ordered from the highest score down. A missing or empty key returns an empty result, and the key is deleted once the last member is popped.
+
+Since the read and the removal are atomic, no two workers can take the same member, which turns a sorted set into a priority queue where the score is the priority. [`BZPOPMAX`](/redis/commands/sorted-set/bzpopmax) is the blocking form.
 
 ## Syntax
 
diff --git a/redis/commands/sorted-set/zpopmin.mdx b/redis/commands/sorted-set/zpopmin.mdx
index 5993444cb..331cbc415 100644
--- a/redis/commands/sorted-set/zpopmin.mdx
+++ b/redis/commands/sorted-set/zpopmin.mdx
@@ -3,7 +3,11 @@ title: "ZPOPMIN"
 description: "Pop members with lowest scores."
 ---
 
-Use `ZPOPMIN` to pop members with lowest scores.
+Use `ZPOPMIN` to remove and return the members with the lowest scores in a sorted set.
+
+Without a count one member is returned with its score, and with a count up to that many are removed, ordered from the lowest score up. The key is deleted once the last member is popped.
+
+With a timestamp or a priority number as the score, this is how a sorted set becomes a scheduler or a priority queue: the next item due is always the minimum, and popping it atomically means only one worker can pick it up. [`BZPOPMIN`](/redis/commands/sorted-set/bzpopmin) is the blocking form.
 
 ## Syntax
 
diff --git a/redis/commands/sorted-set/zrandmember.mdx b/redis/commands/sorted-set/zrandmember.mdx
index f7a424646..7555a4981 100644
--- a/redis/commands/sorted-set/zrandmember.mdx
+++ b/redis/commands/sorted-set/zrandmember.mdx
@@ -3,7 +3,11 @@ title: "ZRANDMEMBER"
 description: "Get random members."
 ---
 
-Use `ZRANDMEMBER` to get random members.
+Use `ZRANDMEMBER` to get random members of a sorted set without removing them.
+
+Without a count one member is returned, or null when the key does not exist. A positive count returns up to that many distinct members, capped at the size of the set, while a negative count returns exactly that many members chosen independently, so repeats are possible. `WITHSCORES` returns each member together with its score.
+
+Use it for sampling and random selection, and [`ZPOPMIN`](/redis/commands/sorted-set/zpopmin) or [`ZPOPMAX`](/redis/commands/sorted-set/zpopmax) when members should be consumed.
 
 ## Syntax
 
diff --git a/redis/commands/sorted-set/zrange.mdx b/redis/commands/sorted-set/zrange.mdx
index 9e66f27d8..9fd11b2b5 100644
--- a/redis/commands/sorted-set/zrange.mdx
+++ b/redis/commands/sorted-set/zrange.mdx
@@ -1,9 +1,15 @@
 ---
 title: "ZRANGE"
-description: "Get members by index range."
+description: "Get members by index, score, or lex range."
 ---
 
-Use `ZRANGE` to get members by index range.
+Use `ZRANGE` to read a range of members from a sorted set.
+
+By default `<start>` and `<stop>` are zero-based indexes into the ordering, inclusive, and may be negative to count from the end, so `0 -1` returns everything and `0 9` the ten lowest scoring members.
+
+The option that follows changes what those two arguments mean. `BYSCORE` reads them as score bounds, inclusive unless prefixed with `(` and accepting `-inf` and `+inf`. `BYLEX` reads them as member bounds written `[member`, `(member`, `-`, or `+`, which is only meaningful when all members share the same score. `REV` reverses the order, and with `BYSCORE` or `BYLEX` it also means the bounds are given from the higher one to the lower one. `LIMIT <offset> <count>` pages through the result and requires `BYSCORE` or `BYLEX`. `WITHSCORES` includes each member's score.
+
+`ZRANGE` covers everything `ZRANGEBYSCORE`, `ZRANGEBYLEX`, `ZREVRANGE`, and their variants do, and it is the command Redis recommends for new code. Use [`ZRANGESTORE`](/redis/commands/sorted-set/zrangestore) to store the result instead of returning it.
 
 ## Syntax
 
@@ -18,7 +24,7 @@ ZRANGE <key> <start> <stop> [BYSCORE | BYLEX] [REV] [LIMIT <offset> <count>] [WI
 | `<key>` | Yes | No | Redis key targeted by the command. |
 | `<start>` | Yes | No | Lower bound. Interpreted as a rank by default, as a score with `BYSCORE`, or lexicographically with `BYLEX`. |
 | `<stop>` | Yes | No | Upper bound. Interpreted as a rank by default, as a score with `BYSCORE`, or lexicographically with `BYLEX`. |
-| `(BYSCORE \| BYLEX)` | No | No | Choose one form: `BYSCORE`; `BYLEX`. |
+| `(BYSCORE \| BYLEX)` | No | No | How the two range arguments are read: `BYSCORE` as score bounds (inclusive, or exclusive with a `(` prefix, and `-inf`/`+inf` allowed), `BYLEX` as member bounds (`[member`, `(member`, `-`, or `+`), which only makes sense when every member has the same score. They are zero-based indexes when neither is given. |
 | `REV` | No | No | Reverse the result order. |
 | `LIMIT <offset> <count>` | No | No | Skip `<offset>` matches and return at most `<count>`; a `<count>` of `-1` returns all remaining. |
 | `WITHSCORES` | No | No | Include sorted-set scores. |
diff --git a/redis/commands/sorted-set/zrangebylex.mdx b/redis/commands/sorted-set/zrangebylex.mdx
index aaf53d08d..d24b42edb 100644
--- a/redis/commands/sorted-set/zrangebylex.mdx
+++ b/redis/commands/sorted-set/zrangebylex.mdx
@@ -3,7 +3,13 @@ title: "ZRANGEBYLEX"
 description: "Get members by lex range."
 ---
 
-Use `ZRANGEBYLEX` to get members by lex range.
+Use `ZRANGEBYLEX` to list the members of a sorted set that fall in a lexicographic range.
+
+Bounds are written `[member` for inclusive and `(member` for exclusive, with `-` and `+` standing for the lowest and highest possible members. `LIMIT <offset> <count>` pages through the result.
+
+The ordering used here is the byte order of member names, which is only meaningful when every member has the same score. Giving all members score `0` turns a sorted set into a sorted string index, which is how prefix lookups and autocomplete are built on top of it.
+
+The command is deprecated in Redis in favor of [`ZRANGE`](/redis/commands/sorted-set/zrange) with `BYLEX`, which accepts the same bounds.
 
 ## Syntax
 
diff --git a/redis/commands/sorted-set/zrangebyscore.mdx b/redis/commands/sorted-set/zrangebyscore.mdx
index 866dc88da..6f0eedcd1 100644
--- a/redis/commands/sorted-set/zrangebyscore.mdx
+++ b/redis/commands/sorted-set/zrangebyscore.mdx
@@ -3,7 +3,11 @@ title: "ZRANGEBYSCORE"
 description: "Get members by score range."
 ---
 
-Use `ZRANGEBYSCORE` to get members by score range.
+Use `ZRANGEBYSCORE` to list the members of a sorted set whose score falls in a range, from the lowest score up.
+
+Bounds are inclusive by default, become exclusive when prefixed with `(`, and accept `-inf` and `+inf` for open ends. `WITHSCORES` returns each member with its score, and `LIMIT <offset> <count>` pages through the result, which is how you take the first N above a threshold without transferring the rest.
+
+With timestamps as scores this is the natural range query over time. The command is deprecated in Redis in favor of [`ZRANGE`](/redis/commands/sorted-set/zrange) with `BYSCORE`.
 
 ## Syntax
 
diff --git a/redis/commands/sorted-set/zrangestore.mdx b/redis/commands/sorted-set/zrangestore.mdx
index d765ff21c..d9d6b824e 100644
--- a/redis/commands/sorted-set/zrangestore.mdx
+++ b/redis/commands/sorted-set/zrangestore.mdx
@@ -1,9 +1,13 @@
 ---
 title: "ZRANGESTORE"
-description: "Store range result."
+description: "Store the result of a range query."
 ---
 
-Use `ZRANGESTORE` to store range result.
+Use `ZRANGESTORE` to run the same selection as [`ZRANGE`](/redis/commands/sorted-set/zrange) and store the result in another sorted set instead of returning it.
+
+The selection works exactly as it does for `ZRANGE`: by index, or by score with `BYSCORE`, or by member with `BYLEX`, with `REV` and `LIMIT` available in the same way. The members keep their original scores in the destination, which is overwritten if it exists and deleted when the range is empty. The reply is the number of members stored.
+
+This is how a slice of a large ranking is materialized once, for instance the top thousand of a leaderboard, so that further intersections or repeated paging run against a small key.
 
 ## Syntax
 
@@ -19,7 +23,7 @@ ZRANGESTORE <dst> <src> <min> <max> [BYSCORE | BYLEX] [REV] [LIMIT <offset> <cou
 | `<src>` | Yes | No | Redis key used as src. |
 | `<min>` | Yes | No | Lower bound. Interpreted as a rank by default, as a score with `BYSCORE`, or lexicographically with `BYLEX`. |
 | `<max>` | Yes | No | Upper bound. Interpreted as a rank by default, as a score with `BYSCORE`, or lexicographically with `BYLEX`. |
-| `(BYSCORE \| BYLEX)` | No | No | Choose one form: `BYSCORE`; `BYLEX`. |
+| `(BYSCORE \| BYLEX)` | No | No | How the two range arguments are read: `BYSCORE` as score bounds (inclusive, or exclusive with a `(` prefix, and `-inf`/`+inf` allowed), `BYLEX` as member bounds (`[member`, `(member`, `-`, or `+`), which only makes sense when every member has the same score. They are zero-based indexes when neither is given. |
 | `REV` | No | No | Reverse the result order. |
 | `LIMIT <offset> <count>` | No | No | Skip `<offset>` matches and return at most `<count>`; a `<count>` of `-1` returns all remaining. |
 
diff --git a/redis/commands/sorted-set/zrank.mdx b/redis/commands/sorted-set/zrank.mdx
index 85ebb0092..9b1418c51 100644
--- a/redis/commands/sorted-set/zrank.mdx
+++ b/redis/commands/sorted-set/zrank.mdx
@@ -3,7 +3,11 @@ title: "ZRANK"
 description: "Get member's rank."
 ---
 
-Use `ZRANK` to get member's rank.
+Use `ZRANK` to get the position of a member in a sorted set, counting from the lowest score.
+
+The rank is zero-based, so the lowest scoring member has rank `0`, and members with equal scores are ordered lexicographically. `WITHSCORE` returns the score alongside the rank. The reply is null when the member or the key does not exist.
+
+This is how a leaderboard reports "you are number N": increment scores with [`ZINCRBY`](/redis/commands/sorted-set/zincrby) and read the position back here, using [`ZREVRANK`](/redis/commands/sorted-set/zrevrank) when rank `0` should be the highest score instead.
 
 ## Syntax
 
diff --git a/redis/commands/sorted-set/zrem.mdx b/redis/commands/sorted-set/zrem.mdx
index 902c0cc24..227e9ca49 100644
--- a/redis/commands/sorted-set/zrem.mdx
+++ b/redis/commands/sorted-set/zrem.mdx
@@ -3,7 +3,9 @@ title: "ZREM"
 description: "Remove members."
 ---
 
-Use `ZREM` to remove members.
+Use `ZREM` to remove one or more members from a sorted set.
+
+The reply counts only the members that were actually present, so removing something already gone is not an error. The key is deleted when its last member is removed. To remove members by score, rank, or member range instead of by name, use [`ZREMRANGEBYSCORE`](/redis/commands/sorted-set/zremrangebyscore), [`ZREMRANGEBYRANK`](/redis/commands/sorted-set/zremrangebyrank), or [`ZREMRANGEBYLEX`](/redis/commands/sorted-set/zremrangebylex).
 
 ## Syntax
 
diff --git a/redis/commands/sorted-set/zremrangebylex.mdx b/redis/commands/sorted-set/zremrangebylex.mdx
index c3eb1433e..ac2227d34 100644
--- a/redis/commands/sorted-set/zremrangebylex.mdx
+++ b/redis/commands/sorted-set/zremrangebylex.mdx
@@ -3,7 +3,11 @@ title: "ZREMRANGEBYLEX"
 description: "Remove members by lex range."
 ---
 
-Use `ZREMRANGEBYLEX` to remove members by lex range.
+Use `ZREMRANGEBYLEX` to remove the members of a sorted set that fall in a lexicographic range.
+
+Bounds are written `[member` for inclusive and `(member` for exclusive, with `-` and `+` for the extremes. As with every lexicographic operation, the result is only meaningful when all members share the same score. The reply is the number of members removed, and the key is deleted when it becomes empty.
+
+It is the bulk delete that matches [`ZRANGEBYLEX`](/redis/commands/sorted-set/zrangebylex), useful for dropping a whole prefix from a sorted string index.
 
 ## Syntax
 
diff --git a/redis/commands/sorted-set/zremrangebyrank.mdx b/redis/commands/sorted-set/zremrangebyrank.mdx
index cb9dd110b..842ba81bd 100644
--- a/redis/commands/sorted-set/zremrangebyrank.mdx
+++ b/redis/commands/sorted-set/zremrangebyrank.mdx
@@ -3,7 +3,11 @@ title: "ZREMRANGEBYRANK"
 description: "Remove members by rank range."
 ---
 
-Use `ZREMRANGEBYRANK` to remove members by rank range.
+Use `ZREMRANGEBYRANK` to remove the members of a sorted set that occupy a range of positions.
+
+Ranks are zero-based from the lowest score and may be negative to count from the top, so `ZREMRANGEBYRANK key 0 -101` keeps only the hundred highest scoring members. The reply is the number of members removed, and the key is deleted when it becomes empty.
+
+This is the standard way to cap a leaderboard or any ranking to a fixed size after inserting into it, in the same spirit as [`LTRIM`](/redis/commands/list/ltrim) for lists.
 
 ## Syntax
 
diff --git a/redis/commands/sorted-set/zremrangebyscore.mdx b/redis/commands/sorted-set/zremrangebyscore.mdx
index ccf5ba923..57e2b3229 100644
--- a/redis/commands/sorted-set/zremrangebyscore.mdx
+++ b/redis/commands/sorted-set/zremrangebyscore.mdx
@@ -3,7 +3,11 @@ title: "ZREMRANGEBYSCORE"
 description: "Remove members by score range."
 ---
 
-Use `ZREMRANGEBYSCORE` to remove members by score range.
+Use `ZREMRANGEBYSCORE` to remove the members of a sorted set whose score falls in a range.
+
+Bounds are inclusive by default, become exclusive when prefixed with `(`, and accept `-inf` and `+inf`. The reply is the number of members removed, and the key is deleted when it becomes empty.
+
+With timestamps as scores this is how a sliding window is maintained: drop everything older than the cutoff in one call, which is exactly what a sorted-set rate limiter does before counting what is left.
 
 ## Syntax
 
diff --git a/redis/commands/sorted-set/zrevrange.mdx b/redis/commands/sorted-set/zrevrange.mdx
index 737ce1736..60340d920 100644
--- a/redis/commands/sorted-set/zrevrange.mdx
+++ b/redis/commands/sorted-set/zrevrange.mdx
@@ -3,7 +3,11 @@ title: "ZREVRANGE"
 description: "Get members in reverse order."
 ---
 
-Use `ZREVRANGE` to get members in reverse order.
+Use `ZREVRANGE` to list a range of members of a sorted set ordered from the highest score down.
+
+`<start>` and `<stop>` are zero-based, inclusive positions in that reversed ordering, so `0 9` returns the ten highest scoring members, the usual shape of a leaderboard page. Negative indexes count from the end, and `WITHSCORES` includes each member's score.
+
+The command is deprecated in Redis in favor of [`ZRANGE`](/redis/commands/sorted-set/zrange) with `REV`.
 
 ## Syntax
 
diff --git a/redis/commands/sorted-set/zrevrangebylex.mdx b/redis/commands/sorted-set/zrevrangebylex.mdx
index 09e8edf38..0eec65723 100644
--- a/redis/commands/sorted-set/zrevrangebylex.mdx
+++ b/redis/commands/sorted-set/zrevrangebylex.mdx
@@ -5,6 +5,10 @@ description: "List members in a lexicographic range, in reverse order."
 
 Use `ZREVRANGEBYLEX` to list the members in a lexicographic range, in reverse order.
 
+The bounds are given highest first, `<max>` before `<min>`, written `[member` for inclusive and `(member` for exclusive, with `+` and `-` for the extremes. `LIMIT <offset> <count>` pages through the result.
+
+As with every lexicographic operation, the ordering is only meaningful when all members share the same score. The command is deprecated in Redis in favor of [`ZRANGE`](/redis/commands/sorted-set/zrange) with `BYLEX` and `REV`.
+
 ## Syntax
 
 ```redis
diff --git a/redis/commands/sorted-set/zrevrangebyscore.mdx b/redis/commands/sorted-set/zrevrangebyscore.mdx
index feebc90c2..670cf47ec 100644
--- a/redis/commands/sorted-set/zrevrangebyscore.mdx
+++ b/redis/commands/sorted-set/zrevrangebyscore.mdx
@@ -5,6 +5,10 @@ description: "List members in a score range, highest score first."
 
 Use `ZREVRANGEBYSCORE` to list the members in a score range, ordered from the highest score down.
 
+The bounds are given highest first, `<max>` before `<min>`. They are inclusive by default, become exclusive when prefixed with `(`, and accept `+inf` and `-inf`. `WITHSCORES` returns the scores and `LIMIT <offset> <count>` pages through the result, which is the usual way to fetch "the top N above a threshold".
+
+The command is deprecated in Redis in favor of [`ZRANGE`](/redis/commands/sorted-set/zrange) with `BYSCORE` and `REV`.
+
 ## Syntax
 
 ```redis
diff --git a/redis/commands/sorted-set/zrevrank.mdx b/redis/commands/sorted-set/zrevrank.mdx
index e4d6e089b..a29c546e5 100644
--- a/redis/commands/sorted-set/zrevrank.mdx
+++ b/redis/commands/sorted-set/zrevrank.mdx
@@ -3,7 +3,9 @@ title: "ZREVRANK"
 description: "Get member's reverse rank."
 ---
 
-Use `ZREVRANK` to get member's reverse rank.
+Use `ZREVRANK` to get the position of a member in a sorted set, counting from the highest score.
+
+The rank is zero-based, so the top scoring member has rank `0`, which is the number a leaderboard usually wants to display. `WITHSCORE` returns the score alongside the rank, and the reply is null when the member or the key does not exist. Use [`ZRANK`](/redis/commands/sorted-set/zrank) to count from the lowest score instead.
 
 ## Syntax
 
diff --git a/redis/commands/sorted-set/zscan.mdx b/redis/commands/sorted-set/zscan.mdx
index d10ff7557..899bd33db 100644
--- a/redis/commands/sorted-set/zscan.mdx
+++ b/redis/commands/sorted-set/zscan.mdx
@@ -3,7 +3,11 @@ title: "ZSCAN"
 description: "Incrementally iterate sorted set."
 ---
 
-Use `ZSCAN` to incrementally iterate sorted set.
+Use `ZSCAN` to iterate the members of a sorted set in batches instead of reading them all at once.
+
+Each call takes a cursor and returns the next cursor together with a batch of members and their scores. Start at cursor `0` and keep calling with the cursor from the previous reply until the server returns `0`. `MATCH` filters member names with a glob-style pattern and `COUNT` hints at how much work each call should do.
+
+Filtering happens after a batch is read, so a call can come back empty while the cursor is still non-zero. Members present for the whole iteration are returned at least once, and members added or removed while it runs may or may not appear. When you want members in score order rather than in scan order, use [`ZRANGE`](/redis/commands/sorted-set/zrange).
 
 ## Syntax
 
diff --git a/redis/commands/sorted-set/zscore.mdx b/redis/commands/sorted-set/zscore.mdx
index 20cf2af29..451fc8049 100644
--- a/redis/commands/sorted-set/zscore.mdx
+++ b/redis/commands/sorted-set/zscore.mdx
@@ -3,7 +3,9 @@ title: "ZSCORE"
 description: "Get member's score."
 ---
 
-Use `ZSCORE` to get member's score.
+Use `ZSCORE` to get the score of a member of a sorted set.
+
+The reply is null when the member or the key does not exist, so it doubles as a membership test that also tells you the value. Use [`ZMSCORE`](/redis/commands/sorted-set/zmscore) to read several scores in one call, and [`ZRANK`](/redis/commands/sorted-set/zrank) when you want the member's position rather than its score.
 
 ## Syntax
 
diff --git a/redis/commands/sorted-set/zunion.mdx b/redis/commands/sorted-set/zunion.mdx
index a9133d2fb..4471bc598 100644
--- a/redis/commands/sorted-set/zunion.mdx
+++ b/redis/commands/sorted-set/zunion.mdx
@@ -3,7 +3,11 @@ title: "ZUNION"
 description: "Get sorted set union."
 ---
 
-Use `ZUNION` to get sorted set union.
+Use `ZUNION` to get every member that appears in at least one of the given sorted sets.
+
+`<numkeys>` states how many keys follow. A member present in several inputs gets the sum of its scores by default, which is how scores from different sources are combined; `WEIGHTS` scales each input before that, and `AGGREGATE` replaces the sum with `MIN` or `MAX`. `WITHSCORES` returns the computed scores.
+
+The result is computed on each call and not stored; use [`ZUNIONSTORE`](/redis/commands/sorted-set/zunionstore) to keep it.
 
 ## Syntax
 
diff --git a/redis/commands/sorted-set/zunionstore.mdx b/redis/commands/sorted-set/zunionstore.mdx
index e14aa254d..dc6c1065a 100644
--- a/redis/commands/sorted-set/zunionstore.mdx
+++ b/redis/commands/sorted-set/zunionstore.mdx
@@ -3,7 +3,11 @@ title: "ZUNIONSTORE"
 description: "Store sorted set union."
 ---
 
-Use `ZUNIONSTORE` to store sorted set union.
+Use `ZUNIONSTORE` to compute the union of sorted sets and store it in another key.
+
+Members present in several inputs are scored by the sum of their scores by default, or by `MIN` or `MAX` when `AGGREGATE` is given, with `WEIGHTS` scaling each input first. The destination is overwritten if it exists and deleted when the union is empty, and the reply is the number of members stored.
+
+Merging per-day or per-source rankings into a combined one, weighting them as you go, is the typical use: the destination is an ordinary sorted set that can then be paged with [`ZRANGE`](/redis/commands/sorted-set/zrange).
 
 ## Syntax
 
diff --git a/redis/commands/streams/overview.mdx b/redis/commands/streams/overview.mdx
index 9d5f9bca7..279af403d 100644
--- a/redis/commands/streams/overview.mdx
+++ b/redis/commands/streams/overview.mdx
@@ -11,7 +11,7 @@ description: "Commands for append-only logs, consumer groups, and message proces
 <Card title="XAUTOCLAIM" href="/redis/commands/streams/xautoclaim">Auto-claim idle messages</Card>
 <Card title="XCLAIM" href="/redis/commands/streams/xclaim">Claim pending messages</Card>
 <Card title="XDEL" href="/redis/commands/streams/xdel">Delete stream entries</Card>
-<Card title="XDELEX" href="/redis/commands/streams/xdelex">Delete entries with expiration</Card>
+<Card title="XDELEX" href="/redis/commands/streams/xdelex">Delete entries with reference control</Card>
 <Card title="XGROUP" href="/redis/commands/streams/xgroup">Manage consumer groups</Card>
 <Card title="XINFO CONSUMERS" href="/redis/commands/streams/xinfo-consumers">List group consumers</Card>
 <Card title="XINFO GROUPS" href="/redis/commands/streams/xinfo-groups">List stream groups</Card>
diff --git a/redis/commands/streams/xack.mdx b/redis/commands/streams/xack.mdx
index 1f07233b0..63a600ff8 100644
--- a/redis/commands/streams/xack.mdx
+++ b/redis/commands/streams/xack.mdx
@@ -3,7 +3,11 @@ title: "XACK"
 description: "Acknowledge stream messages."
 ---
 
-Use `XACK` to acknowledge stream messages.
+Use `XACK` to tell a consumer group that entries have been processed.
+
+Acknowledged entries leave the group's pending entries list, so they are no longer counted as in flight and can no longer be claimed by another consumer. The reply counts the IDs that were actually pending, which means acknowledging twice is harmless and returns `0` the second time.
+
+Acknowledging does not delete the entry from the stream: other groups still see it, and it stays until trimmed. Use [`XACKDEL`](/redis/commands/streams/xackdel) when the entry should also be removed.
 
 ## Syntax
 
diff --git a/redis/commands/streams/xackdel.mdx b/redis/commands/streams/xackdel.mdx
index 677fe5c4a..787e62d22 100644
--- a/redis/commands/streams/xackdel.mdx
+++ b/redis/commands/streams/xackdel.mdx
@@ -3,7 +3,11 @@ title: "XACKDEL"
 description: "Acknowledge and delete messages."
 ---
 
-Use `XACKDEL` to acknowledge and delete messages.
+Use `XACKDEL` to acknowledge entries in a consumer group and delete them from the stream in one atomic step.
+
+It combines what [`XACK`](/redis/commands/streams/xack) and [`XDEL`](/redis/commands/streams/xdel) do, which is what you want when a stream serves a single group and processed entries have no reason to stay around. `IDS <numids>` introduces the list of IDs and the count must match.
+
+The reference policy controls what happens to consumer group references of the deleted entries: `KEEPREF`, the default, leaves references in other groups' pending lists in place, `DELREF` removes them everywhere, and `ACKED` only deletes entries that every group has read and acknowledged, leaving the rest in the stream. The reply holds one status code per requested ID, in order.
 
 ## Syntax
 
@@ -17,7 +21,7 @@ XACKDEL <key> <group> [KEEPREF | DELREF | ACKED] IDS <numids> <id> [<id> ...]
 | --- | --- | --- | --- |
 | `<key>` | Yes | No | Redis key targeted by the command. |
 | `<group>` | Yes | No | Consumer group name. |
-| `(KEEPREF \| DELREF \| ACKED)` | No | No | Choose one form: `KEEPREF`; `DELREF`; `ACKED`. |
+| `(KEEPREF \| DELREF \| ACKED)` | No | No | What happens to consumer-group references of the deleted entries: `KEEPREF` (the default) leaves them in place, `DELREF` removes them from every group's pending list, and `ACKED` only removes entries that every group has read and acknowledged. |
 | `IDS <numids> <id> [<id> ...]` | Yes | No | Entry IDs to target. Give the ID count first, then that many IDs. |
 
 ## Response
diff --git a/redis/commands/streams/xadd.mdx b/redis/commands/streams/xadd.mdx
index 2b19b7847..2c7b713f4 100644
--- a/redis/commands/streams/xadd.mdx
+++ b/redis/commands/streams/xadd.mdx
@@ -3,7 +3,13 @@ title: "XADD"
 description: "Add entry to stream."
 ---
 
-Use `XADD` to add entry to stream.
+Use `XADD` to append an entry to a stream, creating the stream when it does not exist.
+
+An entry is a set of field and value pairs identified by an ID of the form `<milliseconds>-<sequence>`. Passing `*` lets the server build the ID from the current time, which guarantees that IDs only ever increase; an explicit ID must be greater than the last one in the stream. The reply is the ID the entry was stored under. `NOMKSTREAM` skips creating a stream that does not exist yet and returns null instead.
+
+The trimming options cap the stream in the same call, which is how a stream is kept from growing without bound. `MAXLEN` limits the number of entries and `MINID` drops entries with an ID below a threshold, which is the way to trim by age since IDs start with a timestamp. `~` makes the trim approximate, stopping at a convenient boundary, which is much cheaper than the exact `=` and is what most workloads should use; `LIMIT` caps how many entries a single call may evict.
+
+`KEEPREF`, `DELREF`, and `ACKED` decide what happens to consumer group references of the entries that trimming removes: `KEEPREF`, the default, leaves those references in place, `DELREF` removes them as well, and `ACKED` only removes entries that every group has read and acknowledged.
 
 ## Syntax
 
@@ -17,9 +23,9 @@ XADD <key> [NOMKSTREAM] [KEEPREF | DELREF | ACKED] [(MAXLEN | MINID) [= | ~] <th
 | --- | --- | --- | --- |
 | `<key>` | Yes | No | Redis key targeted by the command. |
 | `NOMKSTREAM` | No | No | Do not create a missing stream. |
-| `(KEEPREF \| DELREF \| ACKED)` | No | No | Choose one form: `KEEPREF`; `DELREF`; `ACKED`. |
+| `(KEEPREF \| DELREF \| ACKED)` | No | No | What happens to consumer-group references of the entries that trimming removes: `KEEPREF` (the default) leaves them in place, `DELREF` removes them from every group's pending list, and `ACKED` only removes entries that every group has read and acknowledged. |
 | `(MAXLEN \| MINID) [= \| ~] <threshold> [LIMIT <count>]` | No | No | Trim the stream after the entry is added. `MAXLEN` caps the number of entries; `MINID` drops entries with a lower ID. `=` trims exactly and is the default; `~` trims approximately and is required before `LIMIT`, which caps how many entries a single call evicts. |
-| `(* \| <id>)` | Yes | No | Choose one form: `*`. |
+| `(* \| <id>)` | Yes | No | Entry ID: `*` lets the server generate one from the current time, or give an explicit `<milliseconds>-<sequence>` ID, which must be greater than the stream's last one. |
 | `<field> <value>` | Yes | Yes | Field and the value to store in it. Repeat to set several fields in one call. |
 
 ## Response
diff --git a/redis/commands/streams/xautoclaim.mdx b/redis/commands/streams/xautoclaim.mdx
index 3cc2abf82..34575fc9f 100644
--- a/redis/commands/streams/xautoclaim.mdx
+++ b/redis/commands/streams/xautoclaim.mdx
@@ -3,7 +3,11 @@ title: "XAUTOCLAIM"
 description: "Auto-claim idle messages."
 ---
 
-Use `XAUTOCLAIM` to auto-claim idle messages.
+Use `XAUTOCLAIM` to transfer ownership of pending entries that have been idle for too long, without having to name their IDs.
+
+Starting from `<start>`, it walks the group's pending entries list and claims for `<consumer>` every entry that has been idle at least `<min-idle-time>` milliseconds, up to `COUNT` of them. The reply has three parts: a cursor to pass as `<start>` on the next call, the claimed entries themselves (or only their IDs with `JUSTID`), and the IDs that were dropped from the pending list because they no longer exist in the stream.
+
+This is the recommended way to recover work from a consumer that crashed or stalled: it replaces the older loop of [`XPENDING`](/redis/commands/streams/xpending) to find idle entries followed by [`XCLAIM`](/redis/commands/streams/xclaim) to take them, and it can be run repeatedly by a janitor task, since the idle threshold keeps healthy consumers' work untouched.
 
 ## Syntax
 
diff --git a/redis/commands/streams/xclaim.mdx b/redis/commands/streams/xclaim.mdx
index 95d389a29..b701e2c9d 100644
--- a/redis/commands/streams/xclaim.mdx
+++ b/redis/commands/streams/xclaim.mdx
@@ -3,7 +3,13 @@ title: "XCLAIM"
 description: "Claim pending messages."
 ---
 
-Use `XCLAIM` to claim pending messages.
+Use `XCLAIM` to change the owner of specific pending entries in a consumer group.
+
+The entries must have been idle for at least `<min-idle-time>` milliseconds, which is what keeps two recovery attempts from stealing the same work from each other: the first claim resets the idle time and the second one then finds nothing to take. Claiming resets the entry's delivery time and increments its delivery counter, unless `JUSTID` is used, which returns only the IDs and leaves the counter alone.
+
+`IDLE` and `TIME` set the new idle time or the last delivery time explicitly, `RETRYCOUNT` overrides the delivery counter, and `FORCE` creates a pending entry for IDs that exist in the stream but are not currently pending. Entries that no longer exist in the stream are removed from the pending list instead of being claimed.
+
+When you want to claim whatever is idle rather than specific IDs, use [`XAUTOCLAIM`](/redis/commands/streams/xautoclaim).
 
 ## Syntax
 
diff --git a/redis/commands/streams/xdel.mdx b/redis/commands/streams/xdel.mdx
index cab4afb6b..c326dddbf 100644
--- a/redis/commands/streams/xdel.mdx
+++ b/redis/commands/streams/xdel.mdx
@@ -3,7 +3,11 @@ title: "XDEL"
 description: "Delete stream entries."
 ---
 
-Use `XDEL` to delete stream entries.
+Use `XDEL` to remove entries from a stream by ID.
+
+The reply counts the entries that were actually removed. Deleting an entry does not touch consumer group state: an entry already delivered stays in a group's pending entries list until it is acknowledged, so it can still show up in [`XPENDING`](/redis/commands/streams/xpending) after being deleted. Use [`XDELEX`](/redis/commands/streams/xdelex) when you need control over those references.
+
+IDs are never reused, so the stream's ID sequence keeps moving forward after deletions. For bulk cleanup by size or age, [`XTRIM`](/redis/commands/streams/xtrim) is the right command.
 
 ## Syntax
 
diff --git a/redis/commands/streams/xdelex.mdx b/redis/commands/streams/xdelex.mdx
index e4a690276..de151ba29 100644
--- a/redis/commands/streams/xdelex.mdx
+++ b/redis/commands/streams/xdelex.mdx
@@ -1,9 +1,13 @@
 ---
 title: "XDELEX"
-description: "Delete entries with expiration."
+description: "Delete entries with reference control."
 ---
 
-Use `XDELEX` to delete entries with expiration.
+Use `XDELEX` to delete entries from a stream with control over what happens to consumer group references.
+
+`IDS <numids>` introduces the list of IDs and the count must match. The policy decides how consumer groups are affected: `KEEPREF`, the default, deletes the entries but leaves them in the pending entries lists of the groups that had received them, `DELREF` removes those references as well, and `ACKED` only deletes entries that every group has read and acknowledged, leaving the others in place.
+
+That last policy is what makes the command useful as a safe cleanup step: it removes exactly the entries nobody still owes work on. The reply holds one status code per requested ID. Where [`XDEL`](/redis/commands/streams/xdel) always behaves like `KEEPREF`, `XDELEX` is its explicit form.
 
 ## Syntax
 
@@ -16,7 +20,7 @@ XDELEX <key> [KEEPREF | DELREF | ACKED] IDS <numids> <id> [<id> ...]
 | Argument | Required | Repeatable | Description |
 | --- | --- | --- | --- |
 | `<key>` | Yes | No | Redis key targeted by the command. |
-| `(KEEPREF \| DELREF \| ACKED)` | No | No | Choose one form: `KEEPREF`; `DELREF`; `ACKED`. |
+| `(KEEPREF \| DELREF \| ACKED)` | No | No | What happens to consumer-group references of the deleted entries: `KEEPREF` (the default) leaves them in place, `DELREF` removes them from every group's pending list, and `ACKED` only removes entries that every group has read and acknowledged. |
 | `IDS <numids> <id> [<id> ...]` | Yes | No | Entry IDs to target. Give the ID count first, then that many IDs. |
 
 ## Response
diff --git a/redis/commands/streams/xgroup.mdx b/redis/commands/streams/xgroup.mdx
index c63dd66ad..71e43ca3b 100644
--- a/redis/commands/streams/xgroup.mdx
+++ b/redis/commands/streams/xgroup.mdx
@@ -3,7 +3,13 @@ title: "XGROUP"
 description: "Manage consumer groups."
 ---
 
-Use `XGROUP` to manage consumer groups.
+Use `XGROUP` to manage the consumer groups of a stream.
+
+`CREATE` registers a group and sets the position it starts reading from: `0` replays the whole stream from the beginning, while `$` delivers only entries added after the group was created. `MKSTREAM` creates the stream too when it does not exist yet, which avoids an error on a group created before the first producer runs. `SETID` moves that position afterwards, which is how a group is rewound for a replay or fast-forwarded past a backlog.
+
+`CREATECONSUMER` and `DELCONSUMER` add and remove consumers explicitly; consumers are otherwise created on first read. Deleting a consumer returns how many pending entries went away with it, and those entries are then no longer pending for anyone, so hand them over with [`XCLAIM`](/redis/commands/streams/xclaim) or [`XAUTOCLAIM`](/redis/commands/streams/xautoclaim) first if the work still matters.
+
+`DESTROY` removes a group along with all of its pending state, while leaving the stream and its entries untouched.
 
 ## Syntax
 
diff --git a/redis/commands/streams/xinfo-consumers.mdx b/redis/commands/streams/xinfo-consumers.mdx
index 5b2152b0b..0111d8cdb 100644
--- a/redis/commands/streams/xinfo-consumers.mdx
+++ b/redis/commands/streams/xinfo-consumers.mdx
@@ -3,7 +3,9 @@ title: "XINFO CONSUMERS"
 description: "List group consumers."
 ---
 
-Use `XINFO CONSUMERS` to list group consumers.
+Use `XINFO CONSUMERS` to list the consumers of a consumer group.
+
+For each consumer the reply gives its name, how many entries it currently has pending, and how long it has been idle or inactive. This is the view that tells you whether workers are alive and balanced: a consumer with a growing pending count and a large idle time is one that stopped without acknowledging its work, and its entries are the ones to recover with [`XAUTOCLAIM`](/redis/commands/streams/xautoclaim).
 
 ## Syntax
 
diff --git a/redis/commands/streams/xinfo-groups.mdx b/redis/commands/streams/xinfo-groups.mdx
index 432563f3a..75b2c5519 100644
--- a/redis/commands/streams/xinfo-groups.mdx
+++ b/redis/commands/streams/xinfo-groups.mdx
@@ -3,7 +3,9 @@ title: "XINFO GROUPS"
 description: "List stream groups."
 ---
 
-Use `XINFO GROUPS` to list stream groups.
+Use `XINFO GROUPS` to list the consumer groups defined on a stream.
+
+Each group is reported with its name, its number of consumers, how many entries are pending across the group, the ID it has delivered up to, and its lag, meaning how many entries in the stream it has not read yet. Lag and pending count together are the standard health signals for a stream consumer: a growing lag means consumers cannot keep up, while a growing pending count means they read entries but do not acknowledge them.
 
 ## Syntax
 
diff --git a/redis/commands/streams/xinfo-stream.mdx b/redis/commands/streams/xinfo-stream.mdx
index 6a57c858f..7e114eccb 100644
--- a/redis/commands/streams/xinfo-stream.mdx
+++ b/redis/commands/streams/xinfo-stream.mdx
@@ -3,7 +3,11 @@ title: "XINFO STREAM"
 description: "Get stream info."
 ---
 
-Use `XINFO STREAM` to get stream info.
+Use `XINFO STREAM` to get information about a stream.
+
+The default reply summarizes the stream: how many entries it holds, the last generated ID, the number of consumer groups, and the first and last entries. `FULL` returns the detailed form instead, walking the entries along with every group, consumer, and pending entry, with `COUNT` limiting how many items each part of that reply contains (`COUNT 0` means no limit).
+
+Use the summary for monitoring and the full form when debugging a group that appears stuck, since it shows exactly which entries are pending and who owns them.
 
 ## Syntax
 
diff --git a/redis/commands/streams/xlen.mdx b/redis/commands/streams/xlen.mdx
index 5f2cdc242..6bea4045e 100644
--- a/redis/commands/streams/xlen.mdx
+++ b/redis/commands/streams/xlen.mdx
@@ -3,7 +3,9 @@ title: "XLEN"
 description: "Get stream length."
 ---
 
-Use `XLEN` to get stream length.
+Use `XLEN` to get the number of entries currently in a stream.
+
+Deleted and trimmed entries are not counted, and the reply is `0` when the key does not exist. The number reflects what is stored right now, not how many entries the stream has ever carried, so it is a measure of retained data rather than of throughput; a group's backlog is reported by the lag in [`XINFO GROUPS`](/redis/commands/streams/xinfo-groups).
 
 ## Syntax
 
diff --git a/redis/commands/streams/xpending.mdx b/redis/commands/streams/xpending.mdx
index 51385326b..dad47f63f 100644
--- a/redis/commands/streams/xpending.mdx
+++ b/redis/commands/streams/xpending.mdx
@@ -3,7 +3,13 @@ title: "XPENDING"
 description: "Get pending messages info."
 ---
 
-Use `XPENDING` to get pending messages info.
+Use `XPENDING` to inspect the entries that a consumer group has delivered but not yet acknowledged.
+
+With only a key and a group, the reply is a summary: how many entries are pending, the lowest and highest pending IDs, and the number of pending entries per consumer. That is the cheap form to poll for monitoring.
+
+The extended form, with a start, an end, and a count, lists the pending entries one by one with the consumer that owns each, how long it has been idle, and how many times it has been delivered. `IDLE` restricts the listing to entries idle for at least the given number of milliseconds, and a consumer name restricts it to one worker.
+
+A high delivery count points at an entry that keeps failing, and a long idle time points at a consumer that died holding work. Both are handed over to another consumer with [`XCLAIM`](/redis/commands/streams/xclaim) or [`XAUTOCLAIM`](/redis/commands/streams/xautoclaim).
 
 ## Syntax
 
diff --git a/redis/commands/streams/xrange.mdx b/redis/commands/streams/xrange.mdx
index b944a564c..0bc243755 100644
--- a/redis/commands/streams/xrange.mdx
+++ b/redis/commands/streams/xrange.mdx
@@ -3,7 +3,11 @@ title: "XRANGE"
 description: "Get range of stream entries."
 ---
 
-Use `XRANGE` to get range of stream entries.
+Use `XRANGE` to read the entries of a stream within a range of IDs, from the oldest to the newest.
+
+`-` and `+` stand for the smallest and largest possible IDs, so `XRANGE key - +` reads the whole stream. An incomplete ID such as `1526985054069` is completed with the smallest possible sequence number for `<start>` and the largest for `<end>`, which makes it easy to select everything within one millisecond. Prefixing a bound with `(` makes it exclusive, and `COUNT` limits how many entries come back.
+
+Since IDs start with a timestamp, ranges are time queries: pass the milliseconds you care about and you get the entries recorded in that window. Paging works by repeating the call with the last ID you received, made exclusive with `(`. Use [`XREVRANGE`](/redis/commands/streams/xrevrange) to walk the stream backwards.
 
 ## Syntax
 
diff --git a/redis/commands/streams/xread.mdx b/redis/commands/streams/xread.mdx
index 6c5ed1148..5b1f28f94 100644
--- a/redis/commands/streams/xread.mdx
+++ b/redis/commands/streams/xread.mdx
@@ -3,7 +3,13 @@ title: "XREAD"
 description: "Read stream entries."
 ---
 
-Use `XREAD` to read stream entries.
+Use `XREAD` to read entries from one or more streams that are newer than a given ID.
+
+After `STREAMS`, all keys are listed first and then exactly one ID for each key, in the same order. Only entries with an ID greater than the one you give are returned, and the special ID `$` means "only entries added after this call", which is how a client starts tailing a live stream.
+
+`BLOCK <milliseconds>` waits for new data instead of returning an empty reply, with `0` waiting indefinitely, which turns the command into an efficient follow rather than a polling loop. `COUNT` caps how many entries per stream come back.
+
+`XREAD` keeps no server-side position: the client remembers the last ID it processed and passes it on the next call, and every reader sees every entry. When work should be split across consumers, with the server tracking what has been delivered and acknowledged, use a consumer group and [`XREADGROUP`](/redis/commands/streams/xreadgroup).
 
 ## Syntax
 
diff --git a/redis/commands/streams/xreadgroup.mdx b/redis/commands/streams/xreadgroup.mdx
index 73f3dca6e..595a84f88 100644
--- a/redis/commands/streams/xreadgroup.mdx
+++ b/redis/commands/streams/xreadgroup.mdx
@@ -3,7 +3,13 @@ title: "XREADGROUP"
 description: "Read as consumer group."
 ---
 
-Use `XREADGROUP` to read as consumer group.
+Use `XREADGROUP` to read entries from a stream as a member of a consumer group, so that each entry goes to one consumer and Redis keeps track of what has not been acknowledged.
+
+After `STREAMS`, all keys come first and then one ID per key. The special ID `>` delivers entries that have never been delivered to the group and records them as pending for this consumer. Any other ID re-reads that consumer's own pending entries instead, starting after the given ID, which is how a consumer resumes after a restart: read from `0` first to finish old work, then switch to `>`.
+
+The consumer is created on first use. `COUNT` limits the batch size and `BLOCK <milliseconds>` waits for new entries rather than returning empty, with `0` waiting indefinitely. `NOACK` skips the pending entries list entirely, trading the delivery guarantee for speed.
+
+Entries stay pending until acknowledged with [`XACK`](/redis/commands/streams/xack). That is what makes recovery possible: work left behind by a crashed consumer is visible in [`XPENDING`](/redis/commands/streams/xpending) and can be taken over with [`XAUTOCLAIM`](/redis/commands/streams/xautoclaim).
 
 ## Syntax
 
diff --git a/redis/commands/streams/xrevrange.mdx b/redis/commands/streams/xrevrange.mdx
index b05c5408f..3b75491d2 100644
--- a/redis/commands/streams/xrevrange.mdx
+++ b/redis/commands/streams/xrevrange.mdx
@@ -3,7 +3,11 @@ title: "XREVRANGE"
 description: "Get range in reverse order."
 ---
 
-Use `XREVRANGE` to get range in reverse order.
+Use `XREVRANGE` to read the entries of a stream within a range of IDs, from the newest to the oldest.
+
+It is [`XRANGE`](/redis/commands/streams/xrange) in reverse, and the bounds are given in reverse too: `<end>` comes before `<start>`, so `XREVRANGE key + -` walks the whole stream backwards. Incomplete IDs are completed the same way, `(` makes a bound exclusive, and `COUNT` limits the number of entries.
+
+`XREVRANGE key + - COUNT 1` is the idiomatic way to read the most recent entry of a stream.
 
 ## Syntax
 
diff --git a/redis/commands/streams/xtrim.mdx b/redis/commands/streams/xtrim.mdx
index b3f3d6e9b..377e21089 100644
--- a/redis/commands/streams/xtrim.mdx
+++ b/redis/commands/streams/xtrim.mdx
@@ -3,7 +3,13 @@ title: "XTRIM"
 description: "Trim stream to max length."
 ---
 
-Use `XTRIM` to trim stream to max length.
+Use `XTRIM` to cap the size of a stream by removing old entries.
+
+`MAXLEN` keeps at most the given number of entries, dropping the oldest ones, while `MINID` drops every entry with an ID below a threshold, which is how you trim by age since IDs begin with a millisecond timestamp. The reply is the number of entries removed.
+
+`~` makes the trim approximate: the server stops at a convenient boundary and may leave a few extra entries, which is much cheaper on large streams and is the right default for background maintenance. `=` trims exactly, and `LIMIT` caps how many entries a single call may evict, which keeps one call from blocking for a long time.
+
+`KEEPREF`, `DELREF`, and `ACKED` decide what happens to consumer group references of the removed entries: `KEEPREF`, the default, leaves them in place, `DELREF` removes them from every group's pending list, and `ACKED` only removes entries that all groups have read and acknowledged. [`XADD`](/redis/commands/streams/xadd) accepts the same options so a stream can be trimmed as it is written to.
 
 ## Syntax
 
diff --git a/redis/commands/string/append.mdx b/redis/commands/string/append.mdx
index 2c41069c3..b42702e65 100644
--- a/redis/commands/string/append.mdx
+++ b/redis/commands/string/append.mdx
@@ -3,7 +3,9 @@ title: "APPEND"
 description: "Append value to a string."
 ---
 
-Use `APPEND` to append value to a string.
+Use `APPEND` to add a value to the end of the string stored at a key.
+
+If the key does not exist it is created with the given value, so the command behaves like [`SET`](/redis/commands/string/set) on a fresh key. The reply is the length of the string after the append. Redis grows the underlying buffer with room to spare, so repeated appends stay cheap, which makes this a reasonable way to accumulate log lines or serialized events into one value; [`GETRANGE`](/redis/commands/string/getrange) can then read back a slice without transferring the whole thing.
 
 ## Syntax
 
diff --git a/redis/commands/string/decr.mdx b/redis/commands/string/decr.mdx
index 6d60f809f..51030fbb0 100644
--- a/redis/commands/string/decr.mdx
+++ b/redis/commands/string/decr.mdx
@@ -3,7 +3,9 @@ title: "DECR"
 description: "Decrement integer value by 1."
 ---
 
-Use `DECR` to decrement integer value by 1.
+Use `DECR` to subtract one from the integer stored at a key and get the result.
+
+A missing key counts as `0`, so the first call leaves `-1`. The value must be the string form of a 64-bit signed integer; anything else returns an error, as does an operation that would go below the minimum. The read, the subtraction, and the write happen atomically, so concurrent callers each get a distinct value and no decrement is lost, which is what makes it safe for counting down remaining quota or stock.
 
 ## Syntax
 
diff --git a/redis/commands/string/decrby.mdx b/redis/commands/string/decrby.mdx
index 3fc38b3c9..a087fae28 100644
--- a/redis/commands/string/decrby.mdx
+++ b/redis/commands/string/decrby.mdx
@@ -3,7 +3,9 @@ title: "DECRBY"
 description: "Decrement integer by amount."
 ---
 
-Use `DECRBY` to decrement integer by amount.
+Use `DECRBY` to subtract an integer from the value stored at a key and get the result.
+
+A missing key counts as `0`. The stored value must be the string form of a 64-bit signed integer, and an operation that would exceed that range returns an error. The whole update is atomic, so concurrent callers cannot lose a decrement. Passing a negative amount adds instead, which makes [`INCRBY`](/redis/commands/string/incrby) and `DECRBY` two views of the same operation.
 
 ## Syntax
 
diff --git a/redis/commands/string/delex.mdx b/redis/commands/string/delex.mdx
index 0d13e8b38..a9a4edb1e 100644
--- a/redis/commands/string/delex.mdx
+++ b/redis/commands/string/delex.mdx
@@ -5,6 +5,10 @@ description: "Delete a string when a condition matches."
 
 Use `DELEX` to delete a string when a condition matches.
 
+`IFEQ` deletes the key only when its current value equals the given one and `IFNE` only when it differs. `IFDEQ` and `IFDNE` do the same against a digest of the value, as returned by [`DIGEST`](/redis/commands/string/digest), which avoids sending a large value over the wire just to compare it.
+
+The comparison and the delete are one atomic step, which is what makes the command the correct way to release a lock or a claim: delete the key only if it still holds your token, so you never remove a lock that has expired and been taken by someone else. With no condition it simply deletes the key. The conditional forms require a string value, and a key of another type returns an error without being deleted.
+
 ## Syntax
 
 ```redis
diff --git a/redis/commands/string/digest.mdx b/redis/commands/string/digest.mdx
index aec43d312..b573069d0 100644
--- a/redis/commands/string/digest.mdx
+++ b/redis/commands/string/digest.mdx
@@ -5,6 +5,10 @@ description: "Get the digest of a string value."
 
 Use `DIGEST` to get the digest of a string value.
 
+The reply is a 16-character lowercase hexadecimal XXH3 digest of the stored bytes, null when the key does not exist, and an error when the value is not a string. It is a fast non-cryptographic hash, meant for change detection rather than for security.
+
+Comparing digests lets a client tell whether a large value has changed without transferring it, for instance to decide whether a cached copy is still current. The same digest can be passed to the conditional forms of [`SET`](/redis/commands/string/set) (`IFDEQ`, `IFDNE`) and [`DELEX`](/redis/commands/string/delex), which turns it into a compact compare-and-set token for large values. `DIGEST` is an Upstash extension.
+
 ## Syntax
 
 ```redis
diff --git a/redis/commands/string/get.mdx b/redis/commands/string/get.mdx
index 929f8c251..d64f4f879 100644
--- a/redis/commands/string/get.mdx
+++ b/redis/commands/string/get.mdx
@@ -3,7 +3,9 @@ title: "GET"
 description: "Get string value."
 ---
 
-Use `GET` to get string value.
+Use `GET` to read the string value stored at a key.
+
+The reply is null when the key does not exist, and an error when the key holds a value of another type, such as a hash or a list. Strings in Redis are binary safe and can hold anything up to 512 MB, so the same command reads back text, JSON, and serialized binary alike. To read and delete in one step use [`GETDEL`](/redis/commands/string/getdel), and to read and refresh the expiration use [`GETEX`](/redis/commands/string/getex).
 
 ## Syntax
 
diff --git a/redis/commands/string/getdel.mdx b/redis/commands/string/getdel.mdx
index 0c810eaf4..34f7ac8ca 100644
--- a/redis/commands/string/getdel.mdx
+++ b/redis/commands/string/getdel.mdx
@@ -3,7 +3,9 @@ title: "GETDEL"
 description: "Get value and delete key."
 ---
 
-Use `GETDEL` to get value and delete key.
+Use `GETDEL` to read the value of a key and delete the key in the same atomic step.
+
+The reply is the value, or null when the key does not exist, and an error when the value is not a string. Because nothing can run between the read and the delete, exactly one caller can obtain the value, which is what makes it right for one-shot data such as a one-time token, a password reset code, or a handoff between two processes. It replaces the [`GET`](/redis/commands/string/get) plus [`DEL`](/redis/commands/generic/del) pair and its race.
 
 ## Syntax
 
diff --git a/redis/commands/string/getex.mdx b/redis/commands/string/getex.mdx
index 817b4cf74..486e74ce0 100644
--- a/redis/commands/string/getex.mdx
+++ b/redis/commands/string/getex.mdx
@@ -3,7 +3,11 @@ title: "GETEX"
 description: "Get value and set expiration."
 ---
 
-Use `GETEX` to get value and set expiration.
+Use `GETEX` to read a value and change its expiration in the same call.
+
+`EX`, `PX`, `EXAT`, and `PXAT` set a new lifetime or deadline, and `PERSIST` removes the expiration so the key stops expiring. With no option at all the expiration is left exactly as it was, which is the difference from [`GET`](/redis/commands/string/get) plus a separate [`EXPIRE`](/redis/commands/generic/expire).
+
+Doing both at once is what makes a sliding expiration correct: reading a session extends it atomically, with no window in which the key could expire between the read and the refresh.
 
 ## Syntax
 
@@ -16,7 +20,7 @@ GETEX <key> [EX <seconds> | PX <milliseconds> | EXAT <unix-time-seconds> | PXAT
 | Argument | Required | Repeatable | Description |
 | --- | --- | --- | --- |
 | `<key>` | Yes | No | Redis key targeted by the command. |
-| `(EX <seconds> \| PX <milliseconds> \| EXAT <unix-time-seconds> \| PXAT <unix-time-milliseconds> \| PERSIST)` | No | No | Choose one form: `EX` (set a lifetime in seconds); `PX` (set a lifetime in milliseconds); `EXAT` (expire at a Unix timestamp in seconds); `PXAT` (expire at a Unix timestamp in milliseconds); `PERSIST`. |
+| `(EX <seconds> \| PX <milliseconds> \| EXAT <unix-time-seconds> \| PXAT <unix-time-milliseconds> \| PERSIST)` | No | No | Choose one form: `EX` (set a lifetime in seconds); `PX` (set a lifetime in milliseconds); `EXAT` (expire at a Unix timestamp in seconds); `PXAT` (expire at a Unix timestamp in milliseconds); `PERSIST` (remove the expiration). Left unchanged when omitted. |
 
 ## Response
 
diff --git a/redis/commands/string/getrange.mdx b/redis/commands/string/getrange.mdx
index 994aea1d9..8746a7f2c 100644
--- a/redis/commands/string/getrange.mdx
+++ b/redis/commands/string/getrange.mdx
@@ -3,7 +3,11 @@ title: "GETRANGE"
 description: "Get substring of string."
 ---
 
-Use `GETRANGE` to get substring of string.
+Use `GETRANGE` to read part of the string stored at a key.
+
+`<start>` and `<end>` are zero-based byte offsets, both inclusive, and may be negative to count from the end, so `GETRANGE key 0 -1` returns the whole value. Offsets outside the string are clamped rather than treated as errors, and a missing key returns an empty string.
+
+Since the range is applied on the server, this is how you read the head of a large value, or a fixed-width field inside one, without transferring the rest. `SUBSTR` is accepted as a deprecated alias with the same arguments and reply.
 
 ## Syntax
 
diff --git a/redis/commands/string/getset.mdx b/redis/commands/string/getset.mdx
index f5a053e88..4db970d2d 100644
--- a/redis/commands/string/getset.mdx
+++ b/redis/commands/string/getset.mdx
@@ -3,7 +3,11 @@ title: "GETSET"
 description: "Set value and return old value."
 ---
 
-Use `GETSET` to set value and return old value.
+Use `GETSET` to set a new value and get the previous one in a single atomic step.
+
+The reply is the old value, or null when the key did not exist. Note that the key's time to live is discarded, so a key with an expiration becomes permanent when written this way.
+
+The classic use is resetting a counter while reading it, where the atomicity guarantees nothing is counted twice. Redis deprecates the command in favor of [`SET`](/redis/commands/string/set) with the `GET` option, which does the same thing and can additionally set or keep an expiration in the same call.
 
 ## Syntax
 
diff --git a/redis/commands/string/incr.mdx b/redis/commands/string/incr.mdx
index 0dc60886a..c2d71c960 100644
--- a/redis/commands/string/incr.mdx
+++ b/redis/commands/string/incr.mdx
@@ -3,7 +3,11 @@ title: "INCR"
 description: "Increment integer value by 1."
 ---
 
-Use `INCR` to increment integer value by 1.
+Use `INCR` to add one to the integer stored at a key and get the result.
+
+A missing key counts as `0`, so the first call returns `1` and no initialization is needed. The value must be the string form of a 64-bit signed integer; anything else returns an error, as does an overflow.
+
+The read, the addition, and the write are one atomic step, so concurrent callers each receive a distinct number and no increment is lost. That property is what makes it the basis for counters, id generators, and rate limiters, usually combined with [`EXPIRE`](/redis/commands/generic/expire) to reset the count for each window.
 
 ## Syntax
 
diff --git a/redis/commands/string/incrby.mdx b/redis/commands/string/incrby.mdx
index 0c8d74bbf..d46933881 100644
--- a/redis/commands/string/incrby.mdx
+++ b/redis/commands/string/incrby.mdx
@@ -3,7 +3,11 @@ title: "INCRBY"
 description: "Increment integer by amount."
 ---
 
-Use `INCRBY` to increment integer by amount.
+Use `INCRBY` to add an integer to the value stored at a key and get the result.
+
+A missing key counts as `0`, the value must be the string form of a 64-bit signed integer, and an operation that would leave that range returns an error. A negative amount subtracts, which makes it interchangeable with [`DECRBY`](/redis/commands/string/decrby).
+
+Like [`INCR`](/redis/commands/string/incr), the update is atomic, so it is safe for counters that several clients update at once, such as adding a batch size to a running total.
 
 ## Syntax
 
diff --git a/redis/commands/string/incrbyfloat.mdx b/redis/commands/string/incrbyfloat.mdx
index 3f255268c..14ea0909f 100644
--- a/redis/commands/string/incrbyfloat.mdx
+++ b/redis/commands/string/incrbyfloat.mdx
@@ -3,7 +3,11 @@ title: "INCRBYFLOAT"
 description: "Increment float by amount."
 ---
 
-Use `INCRBYFLOAT` to increment float by amount.
+Use `INCRBYFLOAT` to add a floating point number to the value stored at a key and get the result.
+
+The stored value and the increment are parsed as double precision floats, and a missing key counts as `0`. A negative increment subtracts, and there is no separate decrement command. A value that is not a valid number returns an error.
+
+The reply is the new value as a string, which client libraries usually decode into a native number. The result is stored in that same textual form, so repeated increments accumulate the usual binary floating point rounding error: for money and other exact quantities, count in integer units with [`INCRBY`](/redis/commands/string/incrby) instead.
 
 ## Syntax
 
diff --git a/redis/commands/string/mget.mdx b/redis/commands/string/mget.mdx
index 91d943bdd..5df53bef9 100644
--- a/redis/commands/string/mget.mdx
+++ b/redis/commands/string/mget.mdx
@@ -3,7 +3,11 @@ title: "MGET"
 description: "Get values of multiple keys."
 ---
 
-Use `MGET` to get values of multiple keys.
+Use `MGET` to read the values of several keys in one call.
+
+The reply holds one entry per key, in the order requested, so it can be zipped straight back onto your list of keys. Keys that do not exist, and keys holding a value that is not a string, come back as null rather than raising an error.
+
+One `MGET` replaces N round trips of [`GET`](/redis/commands/string/get), which is usually the difference that matters when loading a batch of cached objects.
 
 ## Syntax
 
diff --git a/redis/commands/string/mset.mdx b/redis/commands/string/mset.mdx
index c4cbd1d79..444266c64 100644
--- a/redis/commands/string/mset.mdx
+++ b/redis/commands/string/mset.mdx
@@ -3,7 +3,11 @@ title: "MSET"
 description: "Set multiple keys at once."
 ---
 
-Use `MSET` to set multiple keys at once.
+Use `MSET` to set several keys to their values in one atomic call.
+
+All the keys are written together, with no other command running in between, so other clients never observe a state where only part of the batch has been applied. Existing values are overwritten and their expirations are discarded. The reply is always `OK`.
+
+Use [`MSETNX`](/redis/commands/string/msetnx) when the write should only happen if none of the keys exist, and set keys individually with [`SET`](/redis/commands/string/set) when each needs its own expiration.
 
 ## Syntax
 
diff --git a/redis/commands/string/msetnx.mdx b/redis/commands/string/msetnx.mdx
index d5d91331b..47fcb2bb0 100644
--- a/redis/commands/string/msetnx.mdx
+++ b/redis/commands/string/msetnx.mdx
@@ -3,7 +3,9 @@ title: "MSETNX"
 description: "Set multiple keys if none exist."
 ---
 
-Use `MSETNX` to set multiple keys if none exist.
+Use `MSETNX` to set several keys at once, but only if none of them already exists.
+
+The command is all or nothing: if even a single key is present, nothing is written and the reply is `0`; otherwise every key is written and the reply is `1`. Since the check and the writes are one atomic step, it can be used to claim a whole group of related keys, so that a partially initialized state can never be observed.
 
 ## Syntax
 
diff --git a/redis/commands/string/psetex.mdx b/redis/commands/string/psetex.mdx
index b2b78cce7..7394e816c 100644
--- a/redis/commands/string/psetex.mdx
+++ b/redis/commands/string/psetex.mdx
@@ -3,7 +3,11 @@ title: "PSETEX"
 description: "Set value with ms expiration."
 ---
 
-Use `PSETEX` to set value with ms expiration.
+Use `PSETEX` to set a value together with a lifetime in milliseconds.
+
+The value and the expiration are applied in the same atomic step, so the key never exists without its expiration, which is the point of the command: setting the value and then expiring it separately leaves a window where a crash makes the key permanent. A lifetime of zero or less returns an error.
+
+It is the millisecond form of [`SETEX`](/redis/commands/string/setex), and equivalent to [`SET`](/redis/commands/string/set) with the `PX` option, which is the more flexible way to write the same thing.
 
 ## Syntax
 
diff --git a/redis/commands/string/set.mdx b/redis/commands/string/set.mdx
index c078be4a2..5c1210a25 100644
--- a/redis/commands/string/set.mdx
+++ b/redis/commands/string/set.mdx
@@ -3,7 +3,13 @@ title: "SET"
 description: "Set string value."
 ---
 
-Use `SET` to set string value.
+Use `SET` to store a string value at a key, replacing whatever was there before, whatever its type.
+
+By default the value is written unconditionally and the key's previous time to live is discarded. `KEEPTTL` preserves it, while `EX`, `PX`, `EXAT`, and `PXAT` attach a new lifetime in seconds or milliseconds, or an absolute deadline as a Unix timestamp. Setting the value and its expiration in one command is what keeps a key from ever existing without one.
+
+The condition decides whether the write happens at all. `NX` writes only when the key does not exist, which combined with an expiration is the standard way to acquire a lock, and `XX` writes only when it already exists, which refreshes a value without creating it. `IFEQ` and `IFNE` compare the current value with the one you supply, and `IFDEQ` and `IFDNE` compare its digest as returned by [`DIGEST`](/redis/commands/string/digest), so a large value can be checked without sending it; these conditional forms are implemented by this Upstash deployment and give you compare-and-set semantics in a single command. `IFEQ` and `IFDEQ` require the key to exist, while `IFNE` and `IFDNE` also write when it does not.
+
+`GET` makes the reply the previous value instead of `OK`, which is how you swap a value and read what it replaced in one atomic step. When a condition prevents the write, the reply is null.
 
 ## Syntax
 
diff --git a/redis/commands/string/setex.mdx b/redis/commands/string/setex.mdx
index a258c4727..367e01406 100644
--- a/redis/commands/string/setex.mdx
+++ b/redis/commands/string/setex.mdx
@@ -3,7 +3,11 @@ title: "SETEX"
 description: "Set value with expiration."
 ---
 
-Use `SETEX` to set value with expiration.
+Use `SETEX` to set a value together with a lifetime in seconds.
+
+The value and the expiration are applied atomically, so the key never exists without an expiration; writing the value and expiring it in two commands leaves a window in which a failure makes the key permanent. A lifetime of zero or less returns an error.
+
+Use [`PSETEX`](/redis/commands/string/psetex) for millisecond precision. Both are equivalent to [`SET`](/redis/commands/string/set) with `EX` or `PX`, which additionally supports conditions and reading the previous value.
 
 ## Syntax
 
diff --git a/redis/commands/string/setnx.mdx b/redis/commands/string/setnx.mdx
index 0d0d2aee0..4df699e4c 100644
--- a/redis/commands/string/setnx.mdx
+++ b/redis/commands/string/setnx.mdx
@@ -3,7 +3,11 @@ title: "SETNX"
 description: "Set value if key doesn't exist."
 ---
 
-Use `SETNX` to set value if key doesn't exist.
+Use `SETNX` to set a value only if the key does not already exist.
+
+The reply is `1` when the key was created and `0` when it was already there and nothing was written. The check and the write are atomic, so exactly one of several racing clients succeeds.
+
+That makes it the classic lock primitive, but on its own it is an incomplete one: a client that fails after acquiring leaves the key behind forever. Prefer `SET key value NX EX <ttl>`, which claims the key and attaches an expiration in the same step, and release the lock with [`DELEX`](/redis/commands/string/delex) so you only delete it while you still own it.
 
 ## Syntax
 
diff --git a/redis/commands/string/setrange.mdx b/redis/commands/string/setrange.mdx
index 1516cda30..4aedf935a 100644
--- a/redis/commands/string/setrange.mdx
+++ b/redis/commands/string/setrange.mdx
@@ -3,7 +3,11 @@ title: "SETRANGE"
 description: "Overwrite part of string."
 ---
 
-Use `SETRANGE` to overwrite part of string.
+Use `SETRANGE` to overwrite part of the string stored at a key, starting at a byte offset.
+
+The key is created when it does not exist, and if the offset lies past the current end of the value the string is first padded with zero bytes, so writing at a large offset allocates everything up to it. The reply is the length of the string after the write.
+
+Together with [`GETRANGE`](/redis/commands/string/getrange) this makes it possible to treat a string as a fixed-layout record and update one field in place, without reading and rewriting the whole value.
 
 ## Syntax
 
diff --git a/redis/commands/string/strlen.mdx b/redis/commands/string/strlen.mdx
index 61b8848a1..d85d81b8b 100644
--- a/redis/commands/string/strlen.mdx
+++ b/redis/commands/string/strlen.mdx
@@ -3,7 +3,9 @@ title: "STRLEN"
 description: "Get string length."
 ---
 
-Use `STRLEN` to get string length.
+Use `STRLEN` to get the length in bytes of the string stored at a key.
+
+The reply is `0` when the key does not exist, and an error when the value is not a string. Since the value itself is never transferred, it is the cheap way to check how large a value is, for instance before deciding whether to fetch it or to read only part of it with [`GETRANGE`](/redis/commands/string/getrange). The count is in bytes, so multi-byte characters count more than once.
 
 ## Syntax
 
diff --git a/redis/commands/transactions/discard.mdx b/redis/commands/transactions/discard.mdx
index e604464a0..bd811ebc8 100644
--- a/redis/commands/transactions/discard.mdx
+++ b/redis/commands/transactions/discard.mdx
@@ -3,7 +3,11 @@ title: "DISCARD"
 description: "Discard queued commands."
 ---
 
-Use `DISCARD` to discard queued commands.
+Use `DISCARD` to throw away the commands queued since [`MULTI`](/redis/commands/transactions/multi) and leave the transaction without running anything.
+
+It also clears every key watched with [`WATCH`](/redis/commands/transactions/watch), so the connection ends up in its normal state. This is what you call when the data you read after `WATCH` turns out to make the queued update unnecessary or invalid.
+
+The raw command is TCP-only. Over HTTP, use the transaction or pipeline API of an Upstash SDK instead of sending this command directly.
 
 ## Syntax
 
diff --git a/redis/commands/transactions/exec.mdx b/redis/commands/transactions/exec.mdx
index 26d5e111c..0b0e2c2a5 100644
--- a/redis/commands/transactions/exec.mdx
+++ b/redis/commands/transactions/exec.mdx
@@ -3,7 +3,13 @@ title: "EXEC"
 description: "Execute queued commands."
 ---
 
-Use `EXEC` to execute queued commands.
+Use `EXEC` to run the commands queued since [`MULTI`](/redis/commands/transactions/multi).
+
+They execute one after another with no other client's command in between, and the reply is an array holding one result per queued command, in order. Errors raised by individual commands appear in that array rather than stopping the rest, so check each entry.
+
+If any key watched with [`WATCH`](/redis/commands/transactions/watch) was modified after it was watched, the transaction is not executed at all and the reply is null, which is the signal to read the data again and retry. Watches are cleared afterwards either way.
+
+The raw command is TCP-only. Over HTTP, use the transaction or pipeline API of an Upstash SDK instead of sending this command directly.
 
 ## Syntax
 
diff --git a/redis/commands/transactions/multi.mdx b/redis/commands/transactions/multi.mdx
index 36614c7a8..149f2abb2 100644
--- a/redis/commands/transactions/multi.mdx
+++ b/redis/commands/transactions/multi.mdx
@@ -5,6 +5,12 @@ description: "Start a transaction."
 
 Use `MULTI` to start a transaction.
 
+Commands sent afterwards are not executed but queued, each answered with `QUEUED`, until [`EXEC`](/redis/commands/transactions/exec) runs them all in order with nothing else in between, or [`DISCARD`](/redis/commands/transactions/discard) throws them away.
+
+A Redis transaction is atomic in the sense that no other client sees a partial result, but it is not a rollback mechanism: a command that fails at queue time, such as one with a syntax error, aborts the whole transaction, while a command that fails at execution time, such as one applied to the wrong type, leaves the commands around it applied. Combine it with [`WATCH`](/redis/commands/transactions/watch) when the transaction depends on values you read beforehand.
+
+The raw command is TCP-only. Over HTTP, use the transaction or pipeline API of an Upstash SDK instead of sending this command directly.
+
 ## Syntax
 
 ```redis
diff --git a/redis/commands/transactions/unwatch.mdx b/redis/commands/transactions/unwatch.mdx
index b13db9a03..457bd1ac0 100644
--- a/redis/commands/transactions/unwatch.mdx
+++ b/redis/commands/transactions/unwatch.mdx
@@ -3,7 +3,11 @@ title: "UNWATCH"
 description: "Unwatch all keys."
 ---
 
-Use `UNWATCH` to unwatch all keys.
+Use `UNWATCH` to forget all the keys watched with [`WATCH`](/redis/commands/transactions/watch) on this connection.
+
+Afterwards the next [`EXEC`](/redis/commands/transactions/exec) is no longer conditional on those keys. It is the way to abandon an optimistic locking attempt when, after reading the watched data, you decide not to run a transaction at all, so a later unrelated transaction is not aborted by a change to keys you no longer care about. [`EXEC`](/redis/commands/transactions/exec) and [`DISCARD`](/redis/commands/transactions/discard) clear watches on their own.
+
+The raw command is TCP-only. Over HTTP, use the transaction or pipeline API of an Upstash SDK instead of sending this command directly.
 
 ## Syntax
 
diff --git a/redis/commands/transactions/watch.mdx b/redis/commands/transactions/watch.mdx
index aa4865d80..0c10e2b6e 100644
--- a/redis/commands/transactions/watch.mdx
+++ b/redis/commands/transactions/watch.mdx
@@ -3,7 +3,13 @@ title: "WATCH"
 description: "Watch keys for changes."
 ---
 
-Use `WATCH` to watch keys for changes.
+Use `WATCH` to mark keys whose modification should cancel the next transaction, which gives you optimistic locking.
+
+If any watched key is changed by another client between the `WATCH` and the [`EXEC`](/redis/commands/transactions/exec), the transaction is not executed and `EXEC` replies with null instead. Nothing is locked in the meantime: other clients keep working normally, and the conflict is detected rather than prevented.
+
+The usual loop is: watch the keys, read them, decide what to write, open [`MULTI`](/redis/commands/transactions/multi), queue the writes, and call `EXEC`, retrying from the top when the reply is null. That is how a read-modify-write cycle stays correct without holding a lock. All watches are cleared by `EXEC` and [`DISCARD`](/redis/commands/transactions/discard).
+
+The raw command is TCP-only. Over HTTP, use the transaction or pipeline API of an Upstash SDK instead of sending this command directly.
 
 ## Syntax
 

From 65e5f80b3a49df26f3fee28f9b94f3c9cc730983 Mon Sep 17 00:00:00 2001
From: Mehmet Dogan <mehmet@dogan.io>
Date: Thu, 13 Aug 2026 09:43:19 +0300
Subject: [PATCH 04/12] Improve Lua script commands

---
 llms-full.txt                              | 150 +++++++++++++++++++--
 redis/commands/functions/fcall-ro.mdx      |   4 +
 redis/commands/functions/fcall.mdx         |  24 ++++
 redis/commands/functions/function-list.mdx |   2 +-
 redis/commands/functions/function-load.mdx |   4 +
 redis/commands/functions/overview.mdx      |   1 -
 redis/commands/scripting/eval-ro.mdx       |   4 +
 redis/commands/scripting/eval.mdx          |  26 +++-
 redis/commands/scripting/evalsha-ro.mdx    |   4 +
 redis/commands/scripting/evalsha.mdx       |   5 +
 redis/commands/scripting/overview.mdx      |   1 -
 redis/commands/scripting/script-load.mdx   |   4 +
 redis/features/key-locking.mdx             |  57 +++++++-
 13 files changed, 266 insertions(+), 20 deletions(-)

diff --git a/llms-full.txt b/llms-full.txt
index 1e27b24e7..876f7f525 100644
--- a/llms-full.txt
+++ b/llms-full.txt
@@ -20144,6 +20144,28 @@ Use `FCALL` to invoke a function from a library loaded with [`FUNCTION LOAD`](/d
 
 The function runs on the server as a single atomic step, so a sequence of reads and writes that would otherwise need several round trips and a transaction becomes one command. Use [`FCALL_RO`](/docs/redis/commands/functions/fcall-ro) when the function only reads. Functions are the successor to [`EVAL`](/docs/redis/commands/scripting/eval) scripts: they are named, registered once as part of a library, and persisted with the dataset instead of being sent or looked up by digest on every call.
 
+Upstash runs a function under the global lock by default, since the engine cannot know in advance which keys it will touch. Registering the function with the `allow-key-locking` flag makes the call lock only the keys passed in the key list, so calls that work on disjoint keys run in parallel:
+
+```lua
+redis.register_function{
+  function_name='incr_quota',
+  callback=incr_quota,
+  flags={'allow-key-locking'}
+}
+```
+
+Unlike Lua scripts, where the flag goes on the library shebang, this flag is set per registered function. With it set, every key the function touches must be passed as a key in the `FCALL` call: keys sent as ordinary arguments are not locked, and commands that need database-wide access, such as `FLUSHDB`, are rejected. See [Key-Based Locking](/docs/redis/features/key-locking) for the full rules.
+
+<Warning>
+  Pass every key the function touches in the key list, even when it runs under
+  the global lock. Upstash keeps idle entries
+  [on disk](/docs/redis/features/durability): keys given in the key list are loaded
+  before the function starts and the lock is released during that read, but a
+  key that the function builds from `ARGV` while it runs is read from disk with
+  the lock held, stalling every command waiting on it. See
+  [Dynamic Keys and Latency](/docs/redis/features/key-locking#dynamic-keys-and-latency).
+</Warning>
+
 ## Syntax
 
 ```redis
@@ -20162,6 +20184,8 @@ FCALL <function> <numkeys> [<key> [<key> ...]] [<arg> [<arg> ...]]
 ## Important points
 
 * `numkeys` must equal the number of key arguments that immediately follow it; remaining arguments are available to the script or function as ordinary arguments.
+* The function takes the global lock unless it was registered with the `allow-key-locking` flag, in which case only the keys passed in the key list are locked. See [Key-Based Locking](/docs/redis/features/key-locking).
+* Pass every key the function touches in the key list whether or not `allow-key-locking` is set. A key built inside the function is read from disk under the lock when it is not in memory, and it is rejected outright when the flag is set. See [Dynamic Keys and Latency](/docs/redis/features/key-locking#dynamic-keys-and-latency).
 
 ## Response
 
@@ -20327,6 +20351,8 @@ The function must have been registered with the `no-writes` flag; calling a func
 
 Apart from that restriction it behaves like [`FCALL`](/docs/redis/commands/functions/fcall): `<numkeys>` splits the arguments into the keys the function receives in `KEYS` and the plain arguments it receives in `ARGV`.
 
+Being read-only does not by itself make the call concurrent with others. The function takes the global lock unless it was also registered with the `allow-key-locking` flag, as in `flags={'no-writes', 'allow-key-locking'}`. With both flags, the call takes shared read locks on the keys passed in the key list, so several readers of the same key proceed together. See [Key-Based Locking](/docs/redis/features/key-locking).
+
 ## Syntax
 
 ```redis
@@ -20345,6 +20371,8 @@ FCALL_RO <function> <numkeys> [<key> [<key> ...]] [<arg> [<arg> ...]]
 ## Important points
 
 * `numkeys` must equal the number of key arguments that immediately follow it; remaining arguments are available to the script or function as ordinary arguments.
+* A `no-writes` function still takes the global lock unless it was also registered with the `allow-key-locking` flag. See [Key-Based Locking](/docs/redis/features/key-locking).
+* Pass every key the function reads in the key list whether or not `allow-key-locking` is set. A key built inside the function is read from disk under the lock when it is not in memory, and it is rejected outright when the flag is set. See [Dynamic Keys and Latency](/docs/redis/features/key-locking#dynamic-keys-and-latency).
 
 ## Response
 
@@ -20997,7 +21025,7 @@ Source: https://upstash.com/docs/redis/commands/functions/function-list
 
 Use `FUNCTION LIST` to inspect the function libraries loaded in the database.
 
-The reply describes each library with its name, the engine it runs on, and the functions it registers, including each function's description and flags such as `no-writes`. `LIBRARYNAME` filters the reply to library names matching a pattern, and `WITHCODE` includes the full source of each library, which is how you recover the code of a library that is deployed but no longer at hand.
+The reply describes each library with its name, the engine it runs on, and the functions it registers, including each function's description and flags such as `no-writes` and [`allow-key-locking`](/docs/redis/features/key-locking), which is the way to check whether a deployed function locks only its keys or the whole database. `LIBRARYNAME` filters the reply to library names matching a pattern, and `WITHCODE` includes the full source of each library, which is how you recover the code of a library that is deployed but no longer at hand.
 
 ## Syntax
 
@@ -21178,6 +21206,10 @@ Use `FUNCTION LOAD` to register a library of functions in the database.
 
 The payload is the library source code. It must begin with a shebang line naming the engine and the library, such as `#!lua name=mylib`, and register each function with `redis.register_function`, giving it a name, a callback, and optional flags such as `no-writes`. The reply is the library name.
 
+`allow-key-locking` is one of those flags. It opts a function out of the global lock so that a call locks only the keys passed in its key list, which lets calls on disjoint keys run in parallel. Unlike Lua scripts, where the flag goes on the shebang line, it is declared per function in `redis.register_function`, and it is fixed until the library is loaded again. See [Key-Based Locking](/docs/redis/features/key-locking).
+
+Whether or not you set that flag, write functions so that every key they touch arrives in the key list rather than being assembled from `ARGV` inside the function, since an undeclared key can force a disk read while the lock is held. See [Dynamic Keys and Latency](/docs/redis/features/key-locking#dynamic-keys-and-latency).
+
 Loading fails when the library name is already in use unless `REPLACE` is given, which is how you deploy a new version of a library. Once loaded, functions are called by name with [`FCALL`](/docs/redis/commands/functions/fcall) or [`FCALL_RO`](/docs/redis/commands/functions/fcall-ro). Unlike scripts cached by [`SCRIPT LOAD`](/docs/redis/commands/scripting/script-load), libraries are part of the dataset, so they survive restarts and do not need to be re-sent by clients.
 
 ## Syntax
@@ -21539,6 +21571,14 @@ Source: https://upstash.com/docs/redis/commands/functions/overview
 <Card title="FUNCTION STATS" href="/redis/commands/functions/function-stats">Get function execution stats</Card>
 </CardGroup>
 
+Functions run under the database's global lock by default. To let calls that
+touch disjoint keys run in parallel, register the function with the
+`allow-key-locking` flag, as described in
+[Key-Based Locking](/docs/redis/features/key-locking). Either way, pass every key a
+function touches in its key list instead of building it inside the function, so
+that a key that is not in memory is not read from disk while the lock is held.
+See [Dynamic Keys and Latency](/docs/redis/features/key-locking#dynamic-keys-and-latency).
+
 # COPY
 Source: https://upstash.com/docs/redis/commands/generic/copy
 
@@ -41892,7 +41932,28 @@ Use `EVAL` to run a Lua script on the server.
 
 `<numkeys>` says how many of the arguments that follow are key names. The script receives those in the `KEYS` table and every remaining argument in `ARGV`. Passing key names as keys rather than hardcoding them in the script body matters, because Redis uses that list for routing and access checks. Inside the script, `redis.call` runs Redis commands and its return value is converted to a Lua value.
 
-The script runs as a single atomic step: no other command executes while it is running, which makes it the standard way to do read, decide, and write logic, such as a rate limiter or a compare-and-set update, in one round trip and without a transaction. Keep scripts short for the same reason, since a long script blocks everything else, and keep them deterministic by deriving values from `KEYS`, `ARGV`, or data read inside the script rather than from clock or random sources.
+The script runs as a single atomic step, which makes it the standard way to do read, decide, and write logic, such as a rate limiter or a compare-and-set update, in one round trip and without a transaction. Keep scripts short, since a script that holds the database blocks everything else, and keep them deterministic by deriving values from `KEYS`, `ARGV`, or data read inside the script rather than from clock or random sources.
+
+Upstash isolates a script with a lock. By default that is the global lock, because the engine cannot know in advance which keys the script will touch, so no other command runs while the script does. Adding the `allow-key-locking` flag to the script's shebang line makes it lock only the keys passed in `KEYS` instead, so calls that work on disjoint keys run in parallel:
+
+```lua
+#!lua flags=allow-key-locking
+
+redis.call('INCR', KEYS[1])
+return 1
+```
+
+With the flag set, every key the script touches must appear in `KEYS`, and commands that need database-wide access, such as `FLUSHDB`, are rejected. See [Key-Based Locking](/docs/redis/features/key-locking) for the full rules.
+
+<Warning>
+  Pass every key the script touches through `KEYS`, even when the script runs
+  under the global lock. Upstash keeps idle entries
+  [on disk](/docs/redis/features/durability): declared keys are loaded before the
+  script starts and the lock is released during that read, but a key that the
+  script builds while it runs is read from disk with the lock held, stalling
+  every command waiting on it. See
+  [Dynamic Keys and Latency](/docs/redis/features/key-locking#dynamic-keys-and-latency).
+</Warning>
 
 Sending a script also caches it under its SHA1 digest, so later calls can use [`EVALSHA`](/docs/redis/commands/scripting/evalsha) and avoid resending the body. Use [`EVAL_RO`](/docs/redis/commands/scripting/eval-ro) for scripts that only read.
 
@@ -41914,6 +41975,9 @@ EVAL <script> <numkeys> [<key> [<key> ...]] [<arg> [<arg> ...]]
 ## Important points
 
 * `numkeys` must equal the number of key arguments that immediately follow it; remaining arguments are available to the script or function as ordinary arguments.
+* The script takes the global lock unless its shebang sets the `allow-key-locking` flag, in which case it locks only the keys passed in `KEYS`. See [Key-Based Locking](/docs/redis/features/key-locking).
+* A script queued inside a `MULTI`/`EXEC` transaction always runs under the global lock, even when it sets `allow-key-locking`. Call it directly if you want per-key locking.
+* Pass every key the script touches through `KEYS` whether or not `allow-key-locking` is set. A key built inside the script is read from disk under the lock when it is not in memory, and it is rejected outright when the flag is set. See [Dynamic Keys and Latency](/docs/redis/features/key-locking#dynamic-keys-and-latency).
 
 ## Response
 
@@ -42073,6 +42137,8 @@ Use `EVAL_RO` to run a Lua script that is not allowed to write.
 
 It behaves like [`EVAL`](/docs/redis/commands/scripting/eval), with `<numkeys>` splitting the arguments into the `KEYS` and `ARGV` tables, except that any write command called from the script fails with an error. Declaring the read-only intent lets the server serve the call on replicas and turns an accidental write into a clear error instead of an unexpected modification, which is worth doing for every script that only computes over existing data.
 
+Being read-only is not by itself enough to run concurrently with other commands: like `EVAL`, this command takes the global lock unless the script's shebang sets the `allow-key-locking` flag. With the flag, the script takes shared read locks on the keys passed in `KEYS`, so several readers of the same key proceed together. Combine the two flags with a comma, as in `#!lua flags=no-writes,allow-key-locking`, and see [Key-Based Locking](/docs/redis/features/key-locking) for the full rules.
+
 ## Syntax
 
 ```redis
@@ -42091,6 +42157,8 @@ EVAL_RO <script> <numkeys> [<key> [<key> ...]] [<arg> [<arg> ...]]
 ## Important points
 
 * `numkeys` must equal the number of key arguments that immediately follow it; remaining arguments are available to the script or function as ordinary arguments.
+* A read-only script still takes the global lock unless its shebang sets the `allow-key-locking` flag. See [Key-Based Locking](/docs/redis/features/key-locking).
+* Pass every key the script reads through `KEYS` whether or not `allow-key-locking` is set. A key built inside the script is read from disk under the lock when it is not in memory, and it is rejected outright when the flag is set. See [Dynamic Keys and Latency](/docs/redis/features/key-locking#dynamic-keys-and-latency).
 
 ## Response
 
@@ -42250,6 +42318,8 @@ Use `EVALSHA` to run a script that is already in the server's script cache, iden
 
 It behaves exactly like [`EVAL`](/docs/redis/commands/scripting/eval) but sends only the 40-character digest instead of the script body, which keeps the request small when a script is called often. The digest is what [`SCRIPT LOAD`](/docs/redis/commands/scripting/script-load) returns, and it is also computed as a side effect of any `EVAL` call.
 
+Locking behaviour comes from the cached script body, not from the call: the script takes the global lock unless its shebang sets the `allow-key-locking` flag, in which case only the keys passed in `KEYS` are locked. Because the flag lives in the body, changing it means loading a new script and calling the new digest. See [Key-Based Locking](/docs/redis/features/key-locking).
+
 When the script is not in the cache the server replies with a `NOSCRIPT` error, and the client is expected to fall back to `EVAL`. Most client libraries do this automatically. The cache does not survive a restart and is cleared by [`SCRIPT FLUSH`](/docs/redis/commands/scripting/script-flush), so applications must always be able to resend the script body.
 
 ## Syntax
@@ -42270,6 +42340,9 @@ EVALSHA <sha1> <numkeys> [<key> [<key> ...]] [<arg> [<arg> ...]]
 ## Important points
 
 * `numkeys` must equal the number of key arguments that immediately follow it; remaining arguments are available to the script or function as ordinary arguments.
+* The cached script takes the global lock unless its shebang sets the `allow-key-locking` flag. See [Key-Based Locking](/docs/redis/features/key-locking).
+* A script queued inside a `MULTI`/`EXEC` transaction always runs under the global lock, even when it sets `allow-key-locking`. Call it directly if you want per-key locking.
+* Pass every key the script touches through `KEYS` whether or not `allow-key-locking` is set. A key built inside the script is read from disk under the lock when it is not in memory, and it is rejected outright when the flag is set. See [Dynamic Keys and Latency](/docs/redis/features/key-locking#dynamic-keys-and-latency).
 
 ## Response
 
@@ -42426,6 +42499,8 @@ Use `EVALSHA_RO` to run a script cached by its SHA1 digest. The script may not w
 
 It is the read-only form of [`EVALSHA`](/docs/redis/commands/scripting/evalsha): any write command called from the script fails, which lets the server run it on replicas. As with `EVALSHA`, a digest that is not in the cache produces a `NOSCRIPT` error, and the caller is expected to fall back to [`EVAL_RO`](/docs/redis/commands/scripting/eval-ro) with the script body.
 
+Read-only scripts take the global lock like any other script unless the cached body's shebang sets the `allow-key-locking` flag, for example `#!lua flags=no-writes,allow-key-locking`. With the flag, the call takes shared read locks on the keys passed in `KEYS`. See [Key-Based Locking](/docs/redis/features/key-locking).
+
 ## Syntax
 
 ```redis
@@ -42444,6 +42519,8 @@ EVALSHA_RO <sha1> <numkeys> [<key> [<key> ...]] [<arg> [<arg> ...]]
 ## Important points
 
 * `numkeys` must equal the number of key arguments that immediately follow it; remaining arguments are available to the script or function as ordinary arguments.
+* A read-only script still takes the global lock unless the cached body's shebang sets the `allow-key-locking` flag. See [Key-Based Locking](/docs/redis/features/key-locking).
+* Pass every key the script reads through `KEYS` whether or not `allow-key-locking` is set. A key built inside the script is read from disk under the lock when it is not in memory, and it is rejected outright when the flag is set. See [Dynamic Keys and Latency](/docs/redis/features/key-locking#dynamic-keys-and-latency).
 
 ## Response
 
@@ -42607,6 +42684,14 @@ Source: https://upstash.com/docs/redis/commands/scripting/overview
 <Card title="SCRIPT LOAD" href="/redis/commands/scripting/script-load">Load script into cache</Card>
 </CardGroup>
 
+Lua scripts run under the database's global lock by default. To let scripts that
+touch disjoint keys run in parallel, add the `allow-key-locking` flag to the
+script's shebang line, as described in
+[Key-Based Locking](/docs/redis/features/key-locking). Either way, pass every key a
+script touches through `KEYS` instead of building it inside the script, so that
+a key that is not in memory is not read from disk while the lock is held. See
+[Dynamic Keys and Latency](/docs/redis/features/key-locking#dynamic-keys-and-latency).
+
 # SCRIPT EXISTS
 Source: https://upstash.com/docs/redis/commands/scripting/script-exists
 
@@ -43112,6 +43197,10 @@ The reply is the script's SHA1 digest, which is what [`EVALSHA`](/docs/redis/com
 
 The cache is lost on restart and cleared by [`SCRIPT FLUSH`](/docs/redis/commands/scripting/script-flush), so keep the script source available and be ready to handle a `NOSCRIPT` error by loading it again.
 
+Shebang flags are part of the source, so they are fixed at load time and a change to them produces a different digest. This includes `allow-key-locking`, which opts the script out of the global lock and into locking only the keys passed in `KEYS`; see [Key-Based Locking](/docs/redis/features/key-locking).
+
+Whether or not you set that flag, write the script so that every key it touches arrives through `KEYS` rather than being assembled from `ARGV` inside the script, since an undeclared key can force a disk read while the lock is held. See [Dynamic Keys and Latency](/docs/redis/features/key-locking#dynamic-keys-and-latency).
+
 ## Syntax
 
 ```redis
@@ -63413,12 +63502,16 @@ the global lock. This includes commands such as `FLUSHDB` and `FLUSHALL`.
 
 Lua scripts queued inside a transaction always execute under the global lock,
 even if the script declares [`allow-key-locking`](#lua-scripts). If you want
-script-level key locking, run the script directly with `EVAL`/`EVALSHA`
-outside of a transaction.
+script-level key locking, run the script directly with
+[`EVAL`](/docs/redis/commands/scripting/eval) /
+[`EVALSHA`](/docs/redis/commands/scripting/evalsha) outside of a transaction.
 
 ## Lua Scripts
 
-Lua scripts (`EVAL`, `EVALSHA`, `EVAL_RO`, `EVALSHA_RO`) default to the global
+Lua scripts ([`EVAL`](/docs/redis/commands/scripting/eval),
+[`EVALSHA`](/docs/redis/commands/scripting/evalsha),
+[`EVAL_RO`](/docs/redis/commands/scripting/eval-ro),
+[`EVALSHA_RO`](/docs/redis/commands/scripting/evalsha-ro)) default to the global
 lock because the engine cannot know in advance which keys the script will use.
 To opt into key-based locking, add the `allow-key-locking` flag to the script's
 shebang line:
@@ -63447,7 +63540,10 @@ keys can run in parallel.
   ```
 
   In practice, this means you should pass fully resolved keys through `KEYS`
-  rather than reconstructing them from `ARGV` inside the script.
+  rather than reconstructing them from `ARGV` inside the script. This is worth
+  doing even for scripts that run under the global lock, because an undeclared
+  key can force a disk read while the lock is held. See
+  [Dynamic Keys and Latency](#dynamic-keys-and-latency).
 
 * **Database-wide writes are not allowed.** Commands that require database-wide
   exclusive access, such as `FLUSHDB` and `FLUSHALL`, cannot be called from a
@@ -63495,9 +63591,11 @@ concurrently, each holding a lock only on its own `user:<id>:quota` key.
 
 ## Redis Functions
 
-Redis functions (`FCALL`, `FCALL_RO`) also default to the global lock. For
-functions, `allow-key-locking` is set on each registered function, not on the
-library shebang:
+Redis functions ([`FCALL`](/docs/redis/commands/functions/fcall),
+[`FCALL_RO`](/docs/redis/commands/functions/fcall-ro)) also default to the global
+lock. For functions, `allow-key-locking` is set on each registered function,
+not on the library shebang, and takes effect when the library is loaded with
+[`FUNCTION LOAD`](/docs/redis/commands/functions/function-load):
 
 ```lua
 #!lua name=locks
@@ -63536,6 +63634,40 @@ registration:
 flags={'no-writes', 'allow-key-locking'}
 ```
 
+## Dynamic Keys and Latency
+
+Pass every key a script or function touches through the key list of the call,
+where it arrives as `KEYS`, even when you are not using `allow-key-locking`.
+With the flag set, a key that was not declared is rejected outright. Without it
+the call still succeeds, but it can be slow, and the slowdown is not limited to
+the caller.
+
+Upstash keeps data [in memory and on disk](/docs/redis/features/durability), and an
+entry that has been idle long enough to be evicted from memory is read back from
+disk on the next access. Declared keys are loaded before the script body starts
+running, and the engine releases the lock while it waits for that read, so other
+commands keep making progress. A key that only becomes known in the middle of
+the script cannot be handled that way: script execution has to stay atomic, so
+the engine holds the lock across the disk read. Under the global lock, that
+means the whole database waits for a disk read in the middle of your script.
+It is also why dynamic keys are rejected when `allow-key-locking` is set: a key
+the engine was never told about can be neither locked nor loaded up front.
+
+```lua
+-- Dynamic key: resolved inside the script, may be read from disk under the lock
+local key = 'user:' .. ARGV[1] .. ':quota'
+redis.call('INCR', key)
+```
+
+```lua
+-- Declared key: loaded before the script runs, outside the locked section
+redis.call('INCR', KEYS[1])
+```
+
+The cost only appears when the key is not already in memory, so it is easy to
+miss against a small, warm test dataset and easy to hit in production against a
+large one. Resolve key names in your application and pass them in the key list.
+
 # Replication
 Source: https://upstash.com/docs/redis/features/replication
 
diff --git a/redis/commands/functions/fcall-ro.mdx b/redis/commands/functions/fcall-ro.mdx
index 7549ce34d..eb643f9d7 100644
--- a/redis/commands/functions/fcall-ro.mdx
+++ b/redis/commands/functions/fcall-ro.mdx
@@ -9,6 +9,8 @@ The function must have been registered with the `no-writes` flag; calling a func
 
 Apart from that restriction it behaves like [`FCALL`](/redis/commands/functions/fcall): `<numkeys>` splits the arguments into the keys the function receives in `KEYS` and the plain arguments it receives in `ARGV`.
 
+Being read-only does not by itself make the call concurrent with others. The function takes the global lock unless it was also registered with the `allow-key-locking` flag, as in `flags={'no-writes', 'allow-key-locking'}`. With both flags, the call takes shared read locks on the keys passed in the key list, so several readers of the same key proceed together. See [Key-Based Locking](/redis/features/key-locking).
+
 ## Syntax
 
 ```redis
@@ -27,6 +29,8 @@ FCALL_RO <function> <numkeys> [<key> [<key> ...]] [<arg> [<arg> ...]]
 ## Important points
 
 - `numkeys` must equal the number of key arguments that immediately follow it; remaining arguments are available to the script or function as ordinary arguments.
+- A `no-writes` function still takes the global lock unless it was also registered with the `allow-key-locking` flag. See [Key-Based Locking](/redis/features/key-locking).
+- Pass every key the function reads in the key list whether or not `allow-key-locking` is set. A key built inside the function is read from disk under the lock when it is not in memory, and it is rejected outright when the flag is set. See [Dynamic Keys and Latency](/redis/features/key-locking#dynamic-keys-and-latency).
 
 ## Response
 
diff --git a/redis/commands/functions/fcall.mdx b/redis/commands/functions/fcall.mdx
index 7991df407..56e17b844 100644
--- a/redis/commands/functions/fcall.mdx
+++ b/redis/commands/functions/fcall.mdx
@@ -9,6 +9,28 @@ Use `FCALL` to invoke a function from a library loaded with [`FUNCTION LOAD`](/r
 
 The function runs on the server as a single atomic step, so a sequence of reads and writes that would otherwise need several round trips and a transaction becomes one command. Use [`FCALL_RO`](/redis/commands/functions/fcall-ro) when the function only reads. Functions are the successor to [`EVAL`](/redis/commands/scripting/eval) scripts: they are named, registered once as part of a library, and persisted with the dataset instead of being sent or looked up by digest on every call.
 
+Upstash runs a function under the global lock by default, since the engine cannot know in advance which keys it will touch. Registering the function with the `allow-key-locking` flag makes the call lock only the keys passed in the key list, so calls that work on disjoint keys run in parallel:
+
+```lua
+redis.register_function{
+  function_name='incr_quota',
+  callback=incr_quota,
+  flags={'allow-key-locking'}
+}
+```
+
+Unlike Lua scripts, where the flag goes on the library shebang, this flag is set per registered function. With it set, every key the function touches must be passed as a key in the `FCALL` call: keys sent as ordinary arguments are not locked, and commands that need database-wide access, such as `FLUSHDB`, are rejected. See [Key-Based Locking](/redis/features/key-locking) for the full rules.
+
+<Warning>
+  Pass every key the function touches in the key list, even when it runs under
+  the global lock. Upstash keeps idle entries
+  [on disk](/redis/features/durability): keys given in the key list are loaded
+  before the function starts and the lock is released during that read, but a
+  key that the function builds from `ARGV` while it runs is read from disk with
+  the lock held, stalling every command waiting on it. See
+  [Dynamic Keys and Latency](/redis/features/key-locking#dynamic-keys-and-latency).
+</Warning>
+
 ## Syntax
 
 ```redis
@@ -27,6 +49,8 @@ FCALL <function> <numkeys> [<key> [<key> ...]] [<arg> [<arg> ...]]
 ## Important points
 
 - `numkeys` must equal the number of key arguments that immediately follow it; remaining arguments are available to the script or function as ordinary arguments.
+- The function takes the global lock unless it was registered with the `allow-key-locking` flag, in which case only the keys passed in the key list are locked. See [Key-Based Locking](/redis/features/key-locking).
+- Pass every key the function touches in the key list whether or not `allow-key-locking` is set. A key built inside the function is read from disk under the lock when it is not in memory, and it is rejected outright when the flag is set. See [Dynamic Keys and Latency](/redis/features/key-locking#dynamic-keys-and-latency).
 
 ## Response
 
diff --git a/redis/commands/functions/function-list.mdx b/redis/commands/functions/function-list.mdx
index e565076de..2e772f6e4 100644
--- a/redis/commands/functions/function-list.mdx
+++ b/redis/commands/functions/function-list.mdx
@@ -5,7 +5,7 @@ description: "List all libraries."
 
 Use `FUNCTION LIST` to inspect the function libraries loaded in the database.
 
-The reply describes each library with its name, the engine it runs on, and the functions it registers, including each function's description and flags such as `no-writes`. `LIBRARYNAME` filters the reply to library names matching a pattern, and `WITHCODE` includes the full source of each library, which is how you recover the code of a library that is deployed but no longer at hand.
+The reply describes each library with its name, the engine it runs on, and the functions it registers, including each function's description and flags such as `no-writes` and [`allow-key-locking`](/redis/features/key-locking), which is the way to check whether a deployed function locks only its keys or the whole database. `LIBRARYNAME` filters the reply to library names matching a pattern, and `WITHCODE` includes the full source of each library, which is how you recover the code of a library that is deployed but no longer at hand.
 
 ## Syntax
 
diff --git a/redis/commands/functions/function-load.mdx b/redis/commands/functions/function-load.mdx
index 81d79d6e4..da49d81bf 100644
--- a/redis/commands/functions/function-load.mdx
+++ b/redis/commands/functions/function-load.mdx
@@ -7,6 +7,10 @@ Use `FUNCTION LOAD` to register a library of functions in the database.
 
 The payload is the library source code. It must begin with a shebang line naming the engine and the library, such as `#!lua name=mylib`, and register each function with `redis.register_function`, giving it a name, a callback, and optional flags such as `no-writes`. The reply is the library name.
 
+`allow-key-locking` is one of those flags. It opts a function out of the global lock so that a call locks only the keys passed in its key list, which lets calls on disjoint keys run in parallel. Unlike Lua scripts, where the flag goes on the shebang line, it is declared per function in `redis.register_function`, and it is fixed until the library is loaded again. See [Key-Based Locking](/redis/features/key-locking).
+
+Whether or not you set that flag, write functions so that every key they touch arrives in the key list rather than being assembled from `ARGV` inside the function, since an undeclared key can force a disk read while the lock is held. See [Dynamic Keys and Latency](/redis/features/key-locking#dynamic-keys-and-latency).
+
 Loading fails when the library name is already in use unless `REPLACE` is given, which is how you deploy a new version of a library. Once loaded, functions are called by name with [`FCALL`](/redis/commands/functions/fcall) or [`FCALL_RO`](/redis/commands/functions/fcall-ro). Unlike scripts cached by [`SCRIPT LOAD`](/redis/commands/scripting/script-load), libraries are part of the dataset, so they survive restarts and do not need to be re-sent by clients.
 
 ## Syntax
diff --git a/redis/commands/functions/overview.mdx b/redis/commands/functions/overview.mdx
index 8f0f517f6..0958a9313 100644
--- a/redis/commands/functions/overview.mdx
+++ b/redis/commands/functions/overview.mdx
@@ -14,4 +14,3 @@ description: "Commands for loading, managing, and invoking Redis functions."
 <Card title="FUNCTION LOAD" href="/redis/commands/functions/function-load">Load a library</Card>
 <Card title="FUNCTION STATS" href="/redis/commands/functions/function-stats">Get function execution stats</Card>
 </CardGroup>
-
diff --git a/redis/commands/scripting/eval-ro.mdx b/redis/commands/scripting/eval-ro.mdx
index 8073fab22..060df654a 100644
--- a/redis/commands/scripting/eval-ro.mdx
+++ b/redis/commands/scripting/eval-ro.mdx
@@ -7,6 +7,8 @@ Use `EVAL_RO` to run a Lua script that is not allowed to write.
 
 It behaves like [`EVAL`](/redis/commands/scripting/eval), with `<numkeys>` splitting the arguments into the `KEYS` and `ARGV` tables, except that any write command called from the script fails with an error. Declaring the read-only intent lets the server serve the call on replicas and turns an accidental write into a clear error instead of an unexpected modification, which is worth doing for every script that only computes over existing data.
 
+Being read-only is not by itself enough to run concurrently with other commands: like `EVAL`, this command takes the global lock unless the script's shebang sets the `allow-key-locking` flag. With the flag, the script takes shared read locks on the keys passed in `KEYS`, so several readers of the same key proceed together. Combine the two flags with a comma, as in `#!lua flags=no-writes,allow-key-locking`, and see [Key-Based Locking](/redis/features/key-locking) for the full rules.
+
 ## Syntax
 
 ```redis
@@ -25,6 +27,8 @@ EVAL_RO <script> <numkeys> [<key> [<key> ...]] [<arg> [<arg> ...]]
 ## Important points
 
 - `numkeys` must equal the number of key arguments that immediately follow it; remaining arguments are available to the script or function as ordinary arguments.
+- A read-only script still takes the global lock unless its shebang sets the `allow-key-locking` flag. See [Key-Based Locking](/redis/features/key-locking).
+- Pass every key the script reads through `KEYS` whether or not `allow-key-locking` is set. A key built inside the script is read from disk under the lock when it is not in memory, and it is rejected outright when the flag is set. See [Dynamic Keys and Latency](/redis/features/key-locking#dynamic-keys-and-latency).
 
 ## Response
 
diff --git a/redis/commands/scripting/eval.mdx b/redis/commands/scripting/eval.mdx
index baaa345fe..7cd750128 100644
--- a/redis/commands/scripting/eval.mdx
+++ b/redis/commands/scripting/eval.mdx
@@ -7,7 +7,28 @@ Use `EVAL` to run a Lua script on the server.
 
 `<numkeys>` says how many of the arguments that follow are key names. The script receives those in the `KEYS` table and every remaining argument in `ARGV`. Passing key names as keys rather than hardcoding them in the script body matters, because Redis uses that list for routing and access checks. Inside the script, `redis.call` runs Redis commands and its return value is converted to a Lua value.
 
-The script runs as a single atomic step: no other command executes while it is running, which makes it the standard way to do read, decide, and write logic, such as a rate limiter or a compare-and-set update, in one round trip and without a transaction. Keep scripts short for the same reason, since a long script blocks everything else, and keep them deterministic by deriving values from `KEYS`, `ARGV`, or data read inside the script rather than from clock or random sources.
+The script runs as a single atomic step, which makes it the standard way to do read, decide, and write logic, such as a rate limiter or a compare-and-set update, in one round trip and without a transaction. Keep scripts short, since a script that holds the database blocks everything else, and keep them deterministic by deriving values from `KEYS`, `ARGV`, or data read inside the script rather than from clock or random sources.
+
+Upstash isolates a script with a lock. By default that is the global lock, because the engine cannot know in advance which keys the script will touch, so no other command runs while the script does. Adding the `allow-key-locking` flag to the script's shebang line makes it lock only the keys passed in `KEYS` instead, so calls that work on disjoint keys run in parallel:
+
+```lua
+#!lua flags=allow-key-locking
+
+redis.call('INCR', KEYS[1])
+return 1
+```
+
+With the flag set, every key the script touches must appear in `KEYS`, and commands that need database-wide access, such as `FLUSHDB`, are rejected. See [Key-Based Locking](/redis/features/key-locking) for the full rules.
+
+<Warning>
+  Pass every key the script touches through `KEYS`, even when the script runs
+  under the global lock. Upstash keeps idle entries
+  [on disk](/redis/features/durability): declared keys are loaded before the
+  script starts and the lock is released during that read, but a key that the
+  script builds while it runs is read from disk with the lock held, stalling
+  every command waiting on it. See
+  [Dynamic Keys and Latency](/redis/features/key-locking#dynamic-keys-and-latency).
+</Warning>
 
 Sending a script also caches it under its SHA1 digest, so later calls can use [`EVALSHA`](/redis/commands/scripting/evalsha) and avoid resending the body. Use [`EVAL_RO`](/redis/commands/scripting/eval-ro) for scripts that only read.
 
@@ -29,6 +50,9 @@ EVAL <script> <numkeys> [<key> [<key> ...]] [<arg> [<arg> ...]]
 ## Important points
 
 - `numkeys` must equal the number of key arguments that immediately follow it; remaining arguments are available to the script or function as ordinary arguments.
+- The script takes the global lock unless its shebang sets the `allow-key-locking` flag, in which case it locks only the keys passed in `KEYS`. See [Key-Based Locking](/redis/features/key-locking).
+- A script queued inside a `MULTI`/`EXEC` transaction always runs under the global lock, even when it sets `allow-key-locking`. Call it directly if you want per-key locking.
+- Pass every key the script touches through `KEYS` whether or not `allow-key-locking` is set. A key built inside the script is read from disk under the lock when it is not in memory, and it is rejected outright when the flag is set. See [Dynamic Keys and Latency](/redis/features/key-locking#dynamic-keys-and-latency).
 
 ## Response
 
diff --git a/redis/commands/scripting/evalsha-ro.mdx b/redis/commands/scripting/evalsha-ro.mdx
index ee6d7721c..811a94532 100644
--- a/redis/commands/scripting/evalsha-ro.mdx
+++ b/redis/commands/scripting/evalsha-ro.mdx
@@ -7,6 +7,8 @@ Use `EVALSHA_RO` to run a script cached by its SHA1 digest. The script may not w
 
 It is the read-only form of [`EVALSHA`](/redis/commands/scripting/evalsha): any write command called from the script fails, which lets the server run it on replicas. As with `EVALSHA`, a digest that is not in the cache produces a `NOSCRIPT` error, and the caller is expected to fall back to [`EVAL_RO`](/redis/commands/scripting/eval-ro) with the script body.
 
+Read-only scripts take the global lock like any other script unless the cached body's shebang sets the `allow-key-locking` flag, for example `#!lua flags=no-writes,allow-key-locking`. With the flag, the call takes shared read locks on the keys passed in `KEYS`. See [Key-Based Locking](/redis/features/key-locking).
+
 ## Syntax
 
 ```redis
@@ -25,6 +27,8 @@ EVALSHA_RO <sha1> <numkeys> [<key> [<key> ...]] [<arg> [<arg> ...]]
 ## Important points
 
 - `numkeys` must equal the number of key arguments that immediately follow it; remaining arguments are available to the script or function as ordinary arguments.
+- A read-only script still takes the global lock unless the cached body's shebang sets the `allow-key-locking` flag. See [Key-Based Locking](/redis/features/key-locking).
+- Pass every key the script reads through `KEYS` whether or not `allow-key-locking` is set. A key built inside the script is read from disk under the lock when it is not in memory, and it is rejected outright when the flag is set. See [Dynamic Keys and Latency](/redis/features/key-locking#dynamic-keys-and-latency).
 
 ## Response
 
diff --git a/redis/commands/scripting/evalsha.mdx b/redis/commands/scripting/evalsha.mdx
index 6ef5d0ad3..df677c938 100644
--- a/redis/commands/scripting/evalsha.mdx
+++ b/redis/commands/scripting/evalsha.mdx
@@ -7,6 +7,8 @@ Use `EVALSHA` to run a script that is already in the server's script cache, iden
 
 It behaves exactly like [`EVAL`](/redis/commands/scripting/eval) but sends only the 40-character digest instead of the script body, which keeps the request small when a script is called often. The digest is what [`SCRIPT LOAD`](/redis/commands/scripting/script-load) returns, and it is also computed as a side effect of any `EVAL` call.
 
+Locking behaviour comes from the cached script body, not from the call: the script takes the global lock unless its shebang sets the `allow-key-locking` flag, in which case only the keys passed in `KEYS` are locked. Because the flag lives in the body, changing it means loading a new script and calling the new digest. See [Key-Based Locking](/redis/features/key-locking).
+
 When the script is not in the cache the server replies with a `NOSCRIPT` error, and the client is expected to fall back to `EVAL`. Most client libraries do this automatically. The cache does not survive a restart and is cleared by [`SCRIPT FLUSH`](/redis/commands/scripting/script-flush), so applications must always be able to resend the script body.
 
 ## Syntax
@@ -27,6 +29,9 @@ EVALSHA <sha1> <numkeys> [<key> [<key> ...]] [<arg> [<arg> ...]]
 ## Important points
 
 - `numkeys` must equal the number of key arguments that immediately follow it; remaining arguments are available to the script or function as ordinary arguments.
+- The cached script takes the global lock unless its shebang sets the `allow-key-locking` flag. See [Key-Based Locking](/redis/features/key-locking).
+- A script queued inside a `MULTI`/`EXEC` transaction always runs under the global lock, even when it sets `allow-key-locking`. Call it directly if you want per-key locking.
+- Pass every key the script touches through `KEYS` whether or not `allow-key-locking` is set. A key built inside the script is read from disk under the lock when it is not in memory, and it is rejected outright when the flag is set. See [Dynamic Keys and Latency](/redis/features/key-locking#dynamic-keys-and-latency).
 
 ## Response
 
diff --git a/redis/commands/scripting/overview.mdx b/redis/commands/scripting/overview.mdx
index 2dfa7a84c..7b9d5019e 100644
--- a/redis/commands/scripting/overview.mdx
+++ b/redis/commands/scripting/overview.mdx
@@ -14,4 +14,3 @@ description: "Commands for loading and executing Lua scripts."
 <Card title="SCRIPT KILL" href="/redis/commands/scripting/script-kill">Stop a running read-only script</Card>
 <Card title="SCRIPT LOAD" href="/redis/commands/scripting/script-load">Load script into cache</Card>
 </CardGroup>
-
diff --git a/redis/commands/scripting/script-load.mdx b/redis/commands/scripting/script-load.mdx
index 0f8de9b16..d141e9352 100644
--- a/redis/commands/scripting/script-load.mdx
+++ b/redis/commands/scripting/script-load.mdx
@@ -9,6 +9,10 @@ The reply is the script's SHA1 digest, which is what [`EVALSHA`](/redis/commands
 
 The cache is lost on restart and cleared by [`SCRIPT FLUSH`](/redis/commands/scripting/script-flush), so keep the script source available and be ready to handle a `NOSCRIPT` error by loading it again.
 
+Shebang flags are part of the source, so they are fixed at load time and a change to them produces a different digest. This includes `allow-key-locking`, which opts the script out of the global lock and into locking only the keys passed in `KEYS`; see [Key-Based Locking](/redis/features/key-locking).
+
+Whether or not you set that flag, write the script so that every key it touches arrives through `KEYS` rather than being assembled from `ARGV` inside the script, since an undeclared key can force a disk read while the lock is held. See [Dynamic Keys and Latency](/redis/features/key-locking#dynamic-keys-and-latency).
+
 ## Syntax
 
 ```redis
diff --git a/redis/features/key-locking.mdx b/redis/features/key-locking.mdx
index 39cc9a3c6..fbe89d11b 100644
--- a/redis/features/key-locking.mdx
+++ b/redis/features/key-locking.mdx
@@ -48,12 +48,16 @@ the global lock. This includes commands such as `FLUSHDB` and `FLUSHALL`.
 
 Lua scripts queued inside a transaction always execute under the global lock,
 even if the script declares [`allow-key-locking`](#lua-scripts). If you want
-script-level key locking, run the script directly with `EVAL`/`EVALSHA`
-outside of a transaction.
+script-level key locking, run the script directly with
+[`EVAL`](/redis/commands/scripting/eval) /
+[`EVALSHA`](/redis/commands/scripting/evalsha) outside of a transaction.
 
 ## Lua Scripts
 
-Lua scripts (`EVAL`, `EVALSHA`, `EVAL_RO`, `EVALSHA_RO`) default to the global
+Lua scripts ([`EVAL`](/redis/commands/scripting/eval),
+[`EVALSHA`](/redis/commands/scripting/evalsha),
+[`EVAL_RO`](/redis/commands/scripting/eval-ro),
+[`EVALSHA_RO`](/redis/commands/scripting/evalsha-ro)) default to the global
 lock because the engine cannot know in advance which keys the script will use.
 To opt into key-based locking, add the `allow-key-locking` flag to the script's
 shebang line:
@@ -82,7 +86,10 @@ keys can run in parallel.
   ```
 
   In practice, this means you should pass fully resolved keys through `KEYS`
-  rather than reconstructing them from `ARGV` inside the script.
+  rather than reconstructing them from `ARGV` inside the script. This is worth
+  doing even for scripts that run under the global lock, because an undeclared
+  key can force a disk read while the lock is held. See
+  [Dynamic Keys and Latency](#dynamic-keys-and-latency).
 
 - **Database-wide writes are not allowed.** Commands that require database-wide
   exclusive access, such as `FLUSHDB` and `FLUSHALL`, cannot be called from a
@@ -130,9 +137,11 @@ concurrently, each holding a lock only on its own `user:<id>:quota` key.
 
 ## Redis Functions
 
-Redis functions (`FCALL`, `FCALL_RO`) also default to the global lock. For
-functions, `allow-key-locking` is set on each registered function, not on the
-library shebang:
+Redis functions ([`FCALL`](/redis/commands/functions/fcall),
+[`FCALL_RO`](/redis/commands/functions/fcall-ro)) also default to the global
+lock. For functions, `allow-key-locking` is set on each registered function,
+not on the library shebang, and takes effect when the library is loaded with
+[`FUNCTION LOAD`](/redis/commands/functions/function-load):
 
 ```lua
 #!lua name=locks
@@ -170,3 +179,37 @@ registration:
 ```lua
 flags={'no-writes', 'allow-key-locking'}
 ```
+
+## Dynamic Keys and Latency
+
+Pass every key a script or function touches through the key list of the call,
+where it arrives as `KEYS`, even when you are not using `allow-key-locking`.
+With the flag set, a key that was not declared is rejected outright. Without it
+the call still succeeds, but it can be slow, and the slowdown is not limited to
+the caller.
+
+Upstash keeps data [in memory and on disk](/redis/features/durability), and an
+entry that has been idle long enough to be evicted from memory is read back from
+disk on the next access. Declared keys are loaded before the script body starts
+running, and the engine releases the lock while it waits for that read, so other
+commands keep making progress. A key that only becomes known in the middle of
+the script cannot be handled that way: script execution has to stay atomic, so
+the engine holds the lock across the disk read. Under the global lock, that
+means the whole database waits for a disk read in the middle of your script.
+It is also why dynamic keys are rejected when `allow-key-locking` is set: a key
+the engine was never told about can be neither locked nor loaded up front.
+
+```lua
+-- Dynamic key: resolved inside the script, may be read from disk under the lock
+local key = 'user:' .. ARGV[1] .. ':quota'
+redis.call('INCR', key)
+```
+
+```lua
+-- Declared key: loaded before the script runs, outside the locked section
+redis.call('INCR', KEYS[1])
+```
+
+The cost only appears when the key is not already in memory, so it is easy to
+miss against a small, warm test dataset and easy to hit in production against a
+large one. Resolve key names in your application and pass them in the key list.

From a8748c87492198028b5e3d22d5837978da739757 Mon Sep 17 00:00:00 2001
From: Mehmet Dogan <mehmet@dogan.io>
Date: Thu, 13 Aug 2026 09:52:09 +0300
Subject: [PATCH 05/12] Visual improvements

---
 redis/commands/bitmap/bitfield.mdx          | 11 ++++++++++-
 redis/commands/connection/hello.mdx         |  5 ++++-
 redis/commands/generic/restore.mdx          |  6 +++++-
 redis/commands/geo/geoadd.mdx               |  6 +++++-
 redis/commands/geo/georadius-ro.mdx         |  7 ++++++-
 redis/commands/geo/georadius.mdx            |  8 +++++++-
 redis/commands/geo/georadiusbymember-ro.mdx |  7 ++++++-
 redis/commands/geo/georadiusbymember.mdx    |  8 +++++++-
 redis/commands/geo/geosearch.mdx            | 10 +++++++++-
 redis/commands/geo/geosearchstore.mdx       |  8 +++++++-
 redis/commands/hash/hexpire.mdx             |  4 +++-
 redis/commands/hash/hexpireat.mdx           |  4 +++-
 redis/commands/hash/hgetex.mdx              |  5 ++++-
 redis/commands/hash/hpexpire.mdx            |  4 +++-
 redis/commands/hash/hpexpireat.mdx          |  4 +++-
 redis/commands/hash/hsetex.mdx              |  6 +++++-
 redis/commands/json/json-get.mdx            |  6 +++++-
 redis/commands/sorted-set/zinter.mdx        |  5 ++++-
 redis/commands/sorted-set/zinterstore.mdx   |  4 +++-
 redis/commands/sorted-set/zrange.mdx        |  6 +++++-
 redis/commands/sorted-set/zrangestore.mdx   |  5 ++++-
 redis/commands/sorted-set/zunion.mdx        |  5 ++++-
 redis/commands/sorted-set/zunionstore.mdx   |  4 +++-
 redis/commands/streams/xackdel.mdx          |  4 +++-
 redis/commands/streams/xadd.mdx             |  6 +++++-
 redis/commands/streams/xclaim.mdx           |  8 +++++++-
 redis/commands/streams/xdelex.mdx           |  4 +++-
 redis/commands/streams/xpending.mdx         |  5 ++++-
 redis/commands/streams/xread.mdx            |  5 ++++-
 redis/commands/streams/xreadgroup.mdx       |  6 +++++-
 redis/commands/streams/xtrim.mdx            |  5 ++++-
 redis/commands/string/getex.mdx             |  4 +++-
 redis/commands/string/set.mdx               |  7 ++++++-
 33 files changed, 159 insertions(+), 33 deletions(-)

diff --git a/redis/commands/bitmap/bitfield.mdx b/redis/commands/bitmap/bitfield.mdx
index 6cde68c8f..e9bb52a61 100644
--- a/redis/commands/bitmap/bitfield.mdx
+++ b/redis/commands/bitmap/bitfield.mdx
@@ -14,7 +14,16 @@ Packing many small counters into a single key this way saves memory and keeps th
 ## Syntax
 
 ```redis
-BITFIELD <key> [GET <encoding> <offset> | [OVERFLOW WRAP | SAT | FAIL] (SET <encoding> <offset> <value> | INCRBY <encoding> <offset> <increment>) [GET <encoding> <offset> | [OVERFLOW WRAP | SAT | FAIL] (SET <encoding> <offset> <value> | INCRBY <encoding> <offset> <increment>) ...]]
+BITFIELD <key>
+  [GET <encoding> <offset> |
+    [OVERFLOW WRAP | SAT | FAIL]
+    (SET <encoding> <offset> <value> |
+      INCRBY <encoding> <offset> <increment>)
+    [GET <encoding> <offset> |
+      [OVERFLOW WRAP | SAT | FAIL]
+      (SET <encoding> <offset> <value> |
+        INCRBY <encoding> <offset> <increment>)
+      ...]]
 ```
 
 ## Arguments
diff --git a/redis/commands/connection/hello.mdx b/redis/commands/connection/hello.mdx
index 2fa28b0e0..3ecc767d8 100644
--- a/redis/commands/connection/hello.mdx
+++ b/redis/commands/connection/hello.mdx
@@ -12,7 +12,10 @@ Called without arguments, `HELLO` only reports the server version, the protocol
 ## Syntax
 
 ```redis
-HELLO [<protover> [AUTH <username> <password>] [SETNAME <clientname>]]
+HELLO
+  [<protover>
+    [AUTH <username> <password>]
+    [SETNAME <clientname>]]
 ```
 
 ## Arguments
diff --git a/redis/commands/generic/restore.mdx b/redis/commands/generic/restore.mdx
index dcc8c5e4d..6d1bcae25 100644
--- a/redis/commands/generic/restore.mdx
+++ b/redis/commands/generic/restore.mdx
@@ -12,7 +12,11 @@ The payload's version stamp and checksum are verified before anything is written
 ## Syntax
 
 ```redis
-RESTORE <key> <ttl> <serialized-value> [REPLACE] [ABSTTL] [IDLETIME <seconds>] [FREQ <frequency>]
+RESTORE <key> <ttl> <serialized-value>
+  [REPLACE]
+  [ABSTTL]
+  [IDLETIME <seconds>]
+  [FREQ <frequency>]
 ```
 
 ## Arguments
diff --git a/redis/commands/geo/geoadd.mdx b/redis/commands/geo/geoadd.mdx
index 0f4a0447e..2b27052e7 100644
--- a/redis/commands/geo/geoadd.mdx
+++ b/redis/commands/geo/geoadd.mdx
@@ -12,7 +12,11 @@ Each position is encoded into a 52-bit geohash and stored as the score of the me
 ## Syntax
 
 ```redis
-GEOADD <key> [NX | XX] [CH] <longitude> <latitude> <member> [<longitude> <latitude> <member> ...]
+GEOADD <key>
+  [NX | XX]
+  [CH]
+  <longitude> <latitude> <member>
+  [<longitude> <latitude> <member> ...]
 ```
 
 ## Arguments
diff --git a/redis/commands/geo/georadius-ro.mdx b/redis/commands/geo/georadius-ro.mdx
index 9e1add85f..d754330d7 100644
--- a/redis/commands/geo/georadius-ro.mdx
+++ b/redis/commands/geo/georadius-ro.mdx
@@ -12,7 +12,12 @@ Like `GEORADIUS`, it is deprecated in favor of [`GEOSEARCH`](/redis/commands/geo
 ## Syntax
 
 ```redis
-GEORADIUS_RO <key> <longitude> <latitude> <radius> (m | km | ft | mi) [WITHCOORD] [WITHDIST] [WITHHASH] [COUNT <count> [ANY]] [ASC | DESC]
+GEORADIUS_RO <key> <longitude> <latitude> <radius> (m | km | ft | mi)
+  [WITHCOORD]
+  [WITHDIST]
+  [WITHHASH]
+  [COUNT <count> [ANY]]
+  [ASC | DESC]
 ```
 
 ## Arguments
diff --git a/redis/commands/geo/georadius.mdx b/redis/commands/geo/georadius.mdx
index 7770e2649..32d9e2367 100644
--- a/redis/commands/geo/georadius.mdx
+++ b/redis/commands/geo/georadius.mdx
@@ -14,7 +14,13 @@ Redis deprecated `GEORADIUS` in favor of [`GEOSEARCH`](/redis/commands/geo/geose
 ## Syntax
 
 ```redis
-GEORADIUS <key> <longitude> <latitude> <radius> (m | km | ft | mi) [WITHCOORD] [WITHDIST] [WITHHASH] [COUNT <count> [ANY]] [ASC | DESC] [STORE <storekey> | STOREDIST <storedistkey>]
+GEORADIUS <key> <longitude> <latitude> <radius> (m | km | ft | mi)
+  [WITHCOORD]
+  [WITHDIST]
+  [WITHHASH]
+  [COUNT <count> [ANY]]
+  [ASC | DESC]
+  [STORE <storekey> | STOREDIST <storedistkey>]
 ```
 
 ## Arguments
diff --git a/redis/commands/geo/georadiusbymember-ro.mdx b/redis/commands/geo/georadiusbymember-ro.mdx
index 152fcff9b..7e94720be 100644
--- a/redis/commands/geo/georadiusbymember-ro.mdx
+++ b/redis/commands/geo/georadiusbymember-ro.mdx
@@ -12,7 +12,12 @@ Like the writable form, it is deprecated in favor of [`GEOSEARCH`](/redis/comman
 ## Syntax
 
 ```redis
-GEORADIUSBYMEMBER_RO <key> <member> <radius> (m | km | ft | mi) [WITHCOORD] [WITHDIST] [WITHHASH] [COUNT <count> [ANY]] [ASC | DESC]
+GEORADIUSBYMEMBER_RO <key> <member> <radius> (m | km | ft | mi)
+  [WITHCOORD]
+  [WITHDIST]
+  [WITHHASH]
+  [COUNT <count> [ANY]]
+  [ASC | DESC]
 ```
 
 ## Arguments
diff --git a/redis/commands/geo/georadiusbymember.mdx b/redis/commands/geo/georadiusbymember.mdx
index 90bb1adfe..5c943a257 100644
--- a/redis/commands/geo/georadiusbymember.mdx
+++ b/redis/commands/geo/georadiusbymember.mdx
@@ -12,7 +12,13 @@ The same `WITHCOORD`, `WITHDIST`, `WITHHASH`, `COUNT`, sorting, and `STORE` or `
 ## Syntax
 
 ```redis
-GEORADIUSBYMEMBER <key> <member> <radius> (m | km | ft | mi) [WITHCOORD] [WITHDIST] [WITHHASH] [COUNT <count> [ANY]] [ASC | DESC] [STORE <storekey> | STOREDIST <storedistkey>]
+GEORADIUSBYMEMBER <key> <member> <radius> (m | km | ft | mi)
+  [WITHCOORD]
+  [WITHDIST]
+  [WITHHASH]
+  [COUNT <count> [ANY]]
+  [ASC | DESC]
+  [STORE <storekey> | STOREDIST <storedistkey>]
 ```
 
 ## Arguments
diff --git a/redis/commands/geo/geosearch.mdx b/redis/commands/geo/geosearch.mdx
index 72ce8758c..a74b3d3a8 100644
--- a/redis/commands/geo/geosearch.mdx
+++ b/redis/commands/geo/geosearch.mdx
@@ -14,7 +14,15 @@ By default only member names come back. `WITHDIST` adds the distance from the ce
 ## Syntax
 
 ```redis
-GEOSEARCH <key> (FROMMEMBER <member> | FROMLONLAT <longitude> <latitude>) (BYRADIUS <radius> (m | km | ft | mi) | BYBOX <width> <height> (m | km | ft | mi)) [ASC | DESC] [COUNT <count> [ANY]] [WITHCOORD] [WITHDIST] [WITHHASH]
+GEOSEARCH <key>
+  (FROMMEMBER <member> | FROMLONLAT <longitude> <latitude>)
+  (BYRADIUS <radius> (m | km | ft | mi) |
+    BYBOX <width> <height> (m | km | ft | mi))
+  [ASC | DESC]
+  [COUNT <count> [ANY]]
+  [WITHCOORD]
+  [WITHDIST]
+  [WITHHASH]
 ```
 
 ## Arguments
diff --git a/redis/commands/geo/geosearchstore.mdx b/redis/commands/geo/geosearchstore.mdx
index bbe8898ac..8bf4189b7 100644
--- a/redis/commands/geo/geosearchstore.mdx
+++ b/redis/commands/geo/geosearchstore.mdx
@@ -12,7 +12,13 @@ The destination is overwritten on every call, and it is deleted when the query m
 ## Syntax
 
 ```redis
-GEOSEARCHSTORE <destination> <source> (FROMMEMBER <member> | FROMLONLAT <longitude> <latitude>) (BYRADIUS <radius> (m | km | ft | mi) | BYBOX <width> <height> (m | km | ft | mi)) [ASC | DESC] [COUNT <count> [ANY]] [STOREDIST]
+GEOSEARCHSTORE <destination> <source>
+  (FROMMEMBER <member> | FROMLONLAT <longitude> <latitude>)
+  (BYRADIUS <radius> (m | km | ft | mi) |
+    BYBOX <width> <height> (m | km | ft | mi))
+  [ASC | DESC]
+  [COUNT <count> [ANY]]
+  [STOREDIST]
 ```
 
 ## Arguments
diff --git a/redis/commands/hash/hexpire.mdx b/redis/commands/hash/hexpire.mdx
index 080c94cee..72120ad7a 100644
--- a/redis/commands/hash/hexpire.mdx
+++ b/redis/commands/hash/hexpire.mdx
@@ -14,7 +14,9 @@ The reply holds one status code per field, in order: `1` when the expiration was
 ## Syntax
 
 ```redis
-HEXPIRE <key> <seconds> [NX | XX | GT | LT] FIELDS <numfields> <field> [<field> ...]
+HEXPIRE <key> <seconds>
+  [NX | XX | GT | LT]
+  FIELDS <numfields> <field> [<field> ...]
 ```
 
 ## Arguments
diff --git a/redis/commands/hash/hexpireat.mdx b/redis/commands/hash/hexpireat.mdx
index b5c5100a3..b24b34e08 100644
--- a/redis/commands/hash/hexpireat.mdx
+++ b/redis/commands/hash/hexpireat.mdx
@@ -14,7 +14,9 @@ The reply holds one status code per field: `1` when the expiration was set, `0`
 ## Syntax
 
 ```redis
-HEXPIREAT <key> <unix-time-seconds> [NX | XX | GT | LT] FIELDS <numfields> <field> [<field> ...]
+HEXPIREAT <key> <unix-time-seconds>
+  [NX | XX | GT | LT]
+  FIELDS <numfields> <field> [<field> ...]
 ```
 
 ## Arguments
diff --git a/redis/commands/hash/hgetex.mdx b/redis/commands/hash/hgetex.mdx
index 6a55a3d1b..882255eea 100644
--- a/redis/commands/hash/hgetex.mdx
+++ b/redis/commands/hash/hgetex.mdx
@@ -12,7 +12,10 @@ Doing both in one command is what makes sliding expirations possible per field:
 ## Syntax
 
 ```redis
-HGETEX <key> [EX <seconds> | PX <milliseconds> | EXAT <unix-time-seconds> | PXAT <unix-time-milliseconds> | PERSIST] FIELDS <numfields> <field> [<field> ...]
+HGETEX <key>
+  [EX <seconds> | PX <milliseconds> | EXAT <unix-time-seconds> |
+    PXAT <unix-time-milliseconds> | PERSIST]
+  FIELDS <numfields> <field> [<field> ...]
 ```
 
 ## Arguments
diff --git a/redis/commands/hash/hpexpire.mdx b/redis/commands/hash/hpexpire.mdx
index 27ef5766d..a8ff75a6d 100644
--- a/redis/commands/hash/hpexpire.mdx
+++ b/redis/commands/hash/hpexpire.mdx
@@ -12,7 +12,9 @@ It is the millisecond form of [`HEXPIRE`](/redis/commands/hash/hexpire) and beha
 ## Syntax
 
 ```redis
-HPEXPIRE <key> <milliseconds> [NX | XX | GT | LT] FIELDS <numfields> <field> [<field> ...]
+HPEXPIRE <key> <milliseconds>
+  [NX | XX | GT | LT]
+  FIELDS <numfields> <field> [<field> ...]
 ```
 
 ## Arguments
diff --git a/redis/commands/hash/hpexpireat.mdx b/redis/commands/hash/hpexpireat.mdx
index 8637c6f64..14181f602 100644
--- a/redis/commands/hash/hpexpireat.mdx
+++ b/redis/commands/hash/hpexpireat.mdx
@@ -12,7 +12,9 @@ It combines the absolute deadline of [`HEXPIREAT`](/redis/commands/hash/hexpirea
 ## Syntax
 
 ```redis
-HPEXPIREAT <key> <unix-time-milliseconds> [NX | XX | GT | LT] FIELDS <numfields> <field> [<field> ...]
+HPEXPIREAT <key> <unix-time-milliseconds>
+  [NX | XX | GT | LT]
+  FIELDS <numfields> <field> [<field> ...]
 ```
 
 ## Arguments
diff --git a/redis/commands/hash/hsetex.mdx b/redis/commands/hash/hsetex.mdx
index e3054a98a..6f351bf18 100644
--- a/redis/commands/hash/hsetex.mdx
+++ b/redis/commands/hash/hsetex.mdx
@@ -12,7 +12,11 @@ Use `HSETEX` to write hash fields and set their expiration in the same atomic ca
 ## Syntax
 
 ```redis
-HSETEX <key> [FNX | FXX] [EX <seconds> | PX <milliseconds> | EXAT <unix-time-seconds> | PXAT <unix-time-milliseconds> | KEEPTTL] FIELDS <numfields> <field> <value> [<field> <value> ...]
+HSETEX <key>
+  [FNX | FXX]
+  [EX <seconds> | PX <milliseconds> | EXAT <unix-time-seconds> |
+    PXAT <unix-time-milliseconds> | KEEPTTL]
+  FIELDS <numfields> <field> <value> [<field> <value> ...]
 ```
 
 ## Arguments
diff --git a/redis/commands/json/json-get.mdx b/redis/commands/json/json-get.mdx
index 5e8dc14eb..ca11b8271 100644
--- a/redis/commands/json/json-get.mdx
+++ b/redis/commands/json/json-get.mdx
@@ -12,7 +12,11 @@ Without a path the whole document is returned. The reply shape depends on the pa
 ## Syntax
 
 ```redis
-JSON.GET <key> [INDENT indent] [NEWLINE newline] [SPACE space] [path [path ...]]
+JSON.GET <key>
+  [INDENT indent]
+  [NEWLINE newline]
+  [SPACE space]
+  [path [path ...]]
 ```
 
 ## Arguments
diff --git a/redis/commands/sorted-set/zinter.mdx b/redis/commands/sorted-set/zinter.mdx
index c929ccba9..500f8aa35 100644
--- a/redis/commands/sorted-set/zinter.mdx
+++ b/redis/commands/sorted-set/zinter.mdx
@@ -12,7 +12,10 @@ The result is not stored; use [`ZINTERSTORE`](/redis/commands/sorted-set/zinters
 ## Syntax
 
 ```redis
-ZINTER <numkeys> <key> [<key> ...] [WEIGHTS <weight> [<weight> ...]] [AGGREGATE SUM | MIN | MAX] [WITHSCORES]
+ZINTER <numkeys> <key> [<key> ...]
+  [WEIGHTS <weight> [<weight> ...]]
+  [AGGREGATE SUM | MIN | MAX]
+  [WITHSCORES]
 ```
 
 ## Arguments
diff --git a/redis/commands/sorted-set/zinterstore.mdx b/redis/commands/sorted-set/zinterstore.mdx
index 0460fb414..ace6f2d90 100644
--- a/redis/commands/sorted-set/zinterstore.mdx
+++ b/redis/commands/sorted-set/zinterstore.mdx
@@ -12,7 +12,9 @@ This is how a combined ranking is built once, for instance blending a relevance
 ## Syntax
 
 ```redis
-ZINTERSTORE <destination> <numkeys> <key> [<key> ...] [WEIGHTS <weight> [<weight> ...]] [AGGREGATE SUM | MIN | MAX]
+ZINTERSTORE <destination> <numkeys> <key> [<key> ...]
+  [WEIGHTS <weight> [<weight> ...]]
+  [AGGREGATE SUM | MIN | MAX]
 ```
 
 ## Arguments
diff --git a/redis/commands/sorted-set/zrange.mdx b/redis/commands/sorted-set/zrange.mdx
index 9fd11b2b5..10e4f62dd 100644
--- a/redis/commands/sorted-set/zrange.mdx
+++ b/redis/commands/sorted-set/zrange.mdx
@@ -14,7 +14,11 @@ The option that follows changes what those two arguments mean. `BYSCORE` reads t
 ## Syntax
 
 ```redis
-ZRANGE <key> <start> <stop> [BYSCORE | BYLEX] [REV] [LIMIT <offset> <count>] [WITHSCORES]
+ZRANGE <key> <start> <stop>
+  [BYSCORE | BYLEX]
+  [REV]
+  [LIMIT <offset> <count>]
+  [WITHSCORES]
 ```
 
 ## Arguments
diff --git a/redis/commands/sorted-set/zrangestore.mdx b/redis/commands/sorted-set/zrangestore.mdx
index d9d6b824e..2163b323b 100644
--- a/redis/commands/sorted-set/zrangestore.mdx
+++ b/redis/commands/sorted-set/zrangestore.mdx
@@ -12,7 +12,10 @@ This is how a slice of a large ranking is materialized once, for instance the to
 ## Syntax
 
 ```redis
-ZRANGESTORE <dst> <src> <min> <max> [BYSCORE | BYLEX] [REV] [LIMIT <offset> <count>]
+ZRANGESTORE <dst> <src> <min> <max>
+  [BYSCORE | BYLEX]
+  [REV]
+  [LIMIT <offset> <count>]
 ```
 
 ## Arguments
diff --git a/redis/commands/sorted-set/zunion.mdx b/redis/commands/sorted-set/zunion.mdx
index 4471bc598..e56f3c02a 100644
--- a/redis/commands/sorted-set/zunion.mdx
+++ b/redis/commands/sorted-set/zunion.mdx
@@ -12,7 +12,10 @@ The result is computed on each call and not stored; use [`ZUNIONSTORE`](/redis/c
 ## Syntax
 
 ```redis
-ZUNION <numkeys> <key> [<key> ...] [WEIGHTS <weight> [<weight> ...]] [AGGREGATE SUM | MIN | MAX] [WITHSCORES]
+ZUNION <numkeys> <key> [<key> ...]
+  [WEIGHTS <weight> [<weight> ...]]
+  [AGGREGATE SUM | MIN | MAX]
+  [WITHSCORES]
 ```
 
 ## Arguments
diff --git a/redis/commands/sorted-set/zunionstore.mdx b/redis/commands/sorted-set/zunionstore.mdx
index dc6c1065a..d00bcce89 100644
--- a/redis/commands/sorted-set/zunionstore.mdx
+++ b/redis/commands/sorted-set/zunionstore.mdx
@@ -12,7 +12,9 @@ Merging per-day or per-source rankings into a combined one, weighting them as yo
 ## Syntax
 
 ```redis
-ZUNIONSTORE <destination> <numkeys> <key> [<key> ...] [WEIGHTS <weight> [<weight> ...]] [AGGREGATE SUM | MIN | MAX]
+ZUNIONSTORE <destination> <numkeys> <key> [<key> ...]
+  [WEIGHTS <weight> [<weight> ...]]
+  [AGGREGATE SUM | MIN | MAX]
 ```
 
 ## Arguments
diff --git a/redis/commands/streams/xackdel.mdx b/redis/commands/streams/xackdel.mdx
index 787e62d22..8dc299487 100644
--- a/redis/commands/streams/xackdel.mdx
+++ b/redis/commands/streams/xackdel.mdx
@@ -12,7 +12,9 @@ The reference policy controls what happens to consumer group references of the d
 ## Syntax
 
 ```redis
-XACKDEL <key> <group> [KEEPREF | DELREF | ACKED] IDS <numids> <id> [<id> ...]
+XACKDEL <key> <group>
+  [KEEPREF | DELREF | ACKED]
+  IDS <numids> <id> [<id> ...]
 ```
 
 ## Arguments
diff --git a/redis/commands/streams/xadd.mdx b/redis/commands/streams/xadd.mdx
index 2c7b713f4..bf14ccc2d 100644
--- a/redis/commands/streams/xadd.mdx
+++ b/redis/commands/streams/xadd.mdx
@@ -14,7 +14,11 @@ The trimming options cap the stream in the same call, which is how a stream is k
 ## Syntax
 
 ```redis
-XADD <key> [NOMKSTREAM] [KEEPREF | DELREF | ACKED] [(MAXLEN | MINID) [= | ~] <threshold> [LIMIT <count>]] (* | <id>) <field> <value> [<field> <value> ...]
+XADD <key>
+  [NOMKSTREAM]
+  [KEEPREF | DELREF | ACKED]
+  [(MAXLEN | MINID) [= | ~] <threshold> [LIMIT <count>]]
+  (* | <id>) <field> <value> [<field> <value> ...]
 ```
 
 ## Arguments
diff --git a/redis/commands/streams/xclaim.mdx b/redis/commands/streams/xclaim.mdx
index b701e2c9d..ba44fafaa 100644
--- a/redis/commands/streams/xclaim.mdx
+++ b/redis/commands/streams/xclaim.mdx
@@ -14,7 +14,13 @@ When you want to claim whatever is idle rather than specific IDs, use [`XAUTOCLA
 ## Syntax
 
 ```redis
-XCLAIM <key> <group> <consumer> <min-idle-time> <ID> [<ID> ...] [IDLE <ms>] [TIME <unix-time-milliseconds>] [RETRYCOUNT <count>] [FORCE] [JUSTID] [LASTID <lastid>]
+XCLAIM <key> <group> <consumer> <min-idle-time> <ID> [<ID> ...]
+  [IDLE <ms>]
+  [TIME <unix-time-milliseconds>]
+  [RETRYCOUNT <count>]
+  [FORCE]
+  [JUSTID]
+  [LASTID <lastid>]
 ```
 
 ## Arguments
diff --git a/redis/commands/streams/xdelex.mdx b/redis/commands/streams/xdelex.mdx
index de151ba29..e9079f269 100644
--- a/redis/commands/streams/xdelex.mdx
+++ b/redis/commands/streams/xdelex.mdx
@@ -12,7 +12,9 @@ That last policy is what makes the command useful as a safe cleanup step: it rem
 ## Syntax
 
 ```redis
-XDELEX <key> [KEEPREF | DELREF | ACKED] IDS <numids> <id> [<id> ...]
+XDELEX <key>
+  [KEEPREF | DELREF | ACKED]
+  IDS <numids> <id> [<id> ...]
 ```
 
 ## Arguments
diff --git a/redis/commands/streams/xpending.mdx b/redis/commands/streams/xpending.mdx
index dad47f63f..7cd99f90d 100644
--- a/redis/commands/streams/xpending.mdx
+++ b/redis/commands/streams/xpending.mdx
@@ -14,7 +14,10 @@ A high delivery count points at an entry that keeps failing, and a long idle tim
 ## Syntax
 
 ```redis
-XPENDING <key> <group> [[IDLE <min-idle-time>] <start> <end> <count> [<consumer>]]
+XPENDING <key> <group>
+  [[IDLE <min-idle-time>]
+    <start> <end> <count>
+    [<consumer>]]
 ```
 
 ## Arguments
diff --git a/redis/commands/streams/xread.mdx b/redis/commands/streams/xread.mdx
index 5b1f28f94..6cf6b0c7c 100644
--- a/redis/commands/streams/xread.mdx
+++ b/redis/commands/streams/xread.mdx
@@ -14,7 +14,10 @@ After `STREAMS`, all keys are listed first and then exactly one ID for each key,
 ## Syntax
 
 ```redis
-XREAD [COUNT <count>] [BLOCK <milliseconds>] STREAMS <key> [<key> ...] <ID> [<ID> ...]
+XREAD
+  [COUNT <count>]
+  [BLOCK <milliseconds>]
+  STREAMS <key> [<key> ...] <ID> [<ID> ...]
 ```
 
 ## Arguments
diff --git a/redis/commands/streams/xreadgroup.mdx b/redis/commands/streams/xreadgroup.mdx
index 595a84f88..981c8f362 100644
--- a/redis/commands/streams/xreadgroup.mdx
+++ b/redis/commands/streams/xreadgroup.mdx
@@ -14,7 +14,11 @@ Entries stay pending until acknowledged with [`XACK`](/redis/commands/streams/xa
 ## Syntax
 
 ```redis
-XREADGROUP GROUP <group> <consumer> [COUNT <count>] [BLOCK <milliseconds>] [NOACK] STREAMS <key> [<key> ...] <ID> [<ID> ...]
+XREADGROUP GROUP <group> <consumer>
+  [COUNT <count>]
+  [BLOCK <milliseconds>]
+  [NOACK]
+  STREAMS <key> [<key> ...] <ID> [<ID> ...]
 ```
 
 ## Arguments
diff --git a/redis/commands/streams/xtrim.mdx b/redis/commands/streams/xtrim.mdx
index 377e21089..07c44996f 100644
--- a/redis/commands/streams/xtrim.mdx
+++ b/redis/commands/streams/xtrim.mdx
@@ -14,7 +14,10 @@ Use `XTRIM` to cap the size of a stream by removing old entries.
 ## Syntax
 
 ```redis
-XTRIM <key> (MAXLEN | MINID) [= | ~] <threshold> [LIMIT <count>] [KEEPREF | DELREF | ACKED]
+XTRIM <key>
+  (MAXLEN | MINID) [= | ~] <threshold>
+  [LIMIT <count>]
+  [KEEPREF | DELREF | ACKED]
 ```
 
 ## Arguments
diff --git a/redis/commands/string/getex.mdx b/redis/commands/string/getex.mdx
index 486e74ce0..85327b234 100644
--- a/redis/commands/string/getex.mdx
+++ b/redis/commands/string/getex.mdx
@@ -12,7 +12,9 @@ Doing both at once is what makes a sliding expiration correct: reading a session
 ## Syntax
 
 ```redis
-GETEX <key> [EX <seconds> | PX <milliseconds> | EXAT <unix-time-seconds> | PXAT <unix-time-milliseconds> | PERSIST]
+GETEX <key>
+  [EX <seconds> | PX <milliseconds> | EXAT <unix-time-seconds> |
+    PXAT <unix-time-milliseconds> | PERSIST]
 ```
 
 ## Arguments
diff --git a/redis/commands/string/set.mdx b/redis/commands/string/set.mdx
index 5c1210a25..363247282 100644
--- a/redis/commands/string/set.mdx
+++ b/redis/commands/string/set.mdx
@@ -14,7 +14,12 @@ The condition decides whether the write happens at all. `NX` writes only when th
 ## Syntax
 
 ```redis
-SET <key> <value> [NX | XX | IFEQ <ifeq-value> | IFNE <ifne-value> | IFDEQ <ifdeq-digest> | IFDNE <ifdne-digest>] [GET] [EX <seconds> | PX <milliseconds> | EXAT <unix-time-seconds> | PXAT <unix-time-milliseconds> | KEEPTTL]
+SET <key> <value>
+  [NX | XX | IFEQ <ifeq-value> | IFNE <ifne-value> |
+    IFDEQ <ifdeq-digest> | IFDNE <ifdne-digest>]
+  [GET]
+  [EX <seconds> | PX <milliseconds> | EXAT <unix-time-seconds> |
+    PXAT <unix-time-milliseconds> | KEEPTTL]
 ```
 
 ## Arguments

From 04996aee22769371b1450028d9f013c4f4a26cd8 Mon Sep 17 00:00:00 2001
From: Mehmet Dogan <mehmet@dogan.io>
Date: Thu, 13 Aug 2026 09:58:39 +0300
Subject: [PATCH 06/12] Add replacement command info

---
 llms-full.txt                                 | 306 ++++++++++++++----
 redis/commands/connection/quit.mdx            |   4 +
 redis/commands/geo/georadius-ro.mdx           |   6 +-
 redis/commands/geo/georadius.mdx              |   6 +-
 redis/commands/geo/georadiusbymember-ro.mdx   |   6 +-
 redis/commands/geo/georadiusbymember.mdx      |   6 +-
 redis/commands/hash/hmset.mdx                 |   6 +-
 redis/commands/list/brpoplpush.mdx            |   6 +-
 redis/commands/list/rpoplpush.mdx             |   6 +-
 redis/commands/sorted-set/zrangebylex.mdx     |   6 +-
 redis/commands/sorted-set/zrangebyscore.mdx   |   6 +-
 redis/commands/sorted-set/zrevrange.mdx       |   6 +-
 redis/commands/sorted-set/zrevrangebylex.mdx  |   6 +-
 .../commands/sorted-set/zrevrangebyscore.mdx  |   6 +-
 redis/commands/string/getset.mdx              |   6 +-
 redis/commands/string/psetex.mdx              |   6 +-
 redis/commands/string/setex.mdx               |   6 +-
 redis/commands/string/setnx.mdx               |   4 +
 18 files changed, 317 insertions(+), 87 deletions(-)

diff --git a/llms-full.txt b/llms-full.txt
index 876f7f525..0568bb4c4 100644
--- a/llms-full.txt
+++ b/llms-full.txt
@@ -17146,7 +17146,16 @@ Packing many small counters into a single key this way saves memory and keeps th
 ## Syntax
 
 ```redis
-BITFIELD <key> [GET <encoding> <offset> | [OVERFLOW WRAP | SAT | FAIL] (SET <encoding> <offset> <value> | INCRBY <encoding> <offset> <increment>) [GET <encoding> <offset> | [OVERFLOW WRAP | SAT | FAIL] (SET <encoding> <offset> <value> | INCRBY <encoding> <offset> <increment>) ...]]
+BITFIELD <key>
+  [GET <encoding> <offset> |
+    [OVERFLOW WRAP | SAT | FAIL]
+    (SET <encoding> <offset> <value> |
+      INCRBY <encoding> <offset> <increment>)
+    [GET <encoding> <offset> |
+      [OVERFLOW WRAP | SAT | FAIL]
+      (SET <encoding> <offset> <value> |
+        INCRBY <encoding> <offset> <increment>)
+      ...]]
 ```
 
 ## Arguments
@@ -19359,7 +19368,10 @@ Called without arguments, `HELLO` only reports the server version, the protocol
 ## Syntax
 
 ```redis
-HELLO [<protover> [AUTH <username> <password>] [SETNAME <clientname>]]
+HELLO
+  [<protover>
+    [AUTH <username> <password>]
+    [SETNAME <clientname>]]
 ```
 
 ## Arguments
@@ -19689,6 +19701,10 @@ fn main() -> redis::RedisResult<()> {
 # QUIT
 Source: https://upstash.com/docs/redis/commands/connection/quit
 
+<Warning>
+  Prefer closing the connection from the client in new code, which avoids leaving `TIME_WAIT` sockets on the server. `QUIT` has no replacement command; it is deprecated in Redis but still supported by Upstash.
+</Warning>
+
 Use `QUIT` to ask the server to close the connection once all pending replies have been sent.
 
 The server replies `OK` and then terminates the connection, so no reply is lost and the shutdown is clean from both sides. Modern clients usually just close the socket, and pooled connections should be returned to the pool rather than closed, so `QUIT` is mostly useful in scripts and interactive sessions.
@@ -21571,14 +21587,6 @@ Source: https://upstash.com/docs/redis/commands/functions/overview
 <Card title="FUNCTION STATS" href="/redis/commands/functions/function-stats">Get function execution stats</Card>
 </CardGroup>
 
-Functions run under the database's global lock by default. To let calls that
-touch disjoint keys run in parallel, register the function with the
-`allow-key-locking` flag, as described in
-[Key-Based Locking](/docs/redis/features/key-locking). Either way, pass every key a
-function touches in its key list instead of building it inside the function, so
-that a key that is not in memory is not read from disk while the lock is held.
-See [Dynamic Keys and Latency](/docs/redis/features/key-locking#dynamic-keys-and-latency).
-
 # COPY
 Source: https://upstash.com/docs/redis/commands/generic/copy
 
@@ -24484,7 +24492,11 @@ The payload's version stamp and checksum are verified before anything is written
 ## Syntax
 
 ```redis
-RESTORE <key> <ttl> <serialized-value> [REPLACE] [ABSTTL] [IDLETIME <seconds>] [FREQ <frequency>]
+RESTORE <key> <ttl> <serialized-value>
+  [REPLACE]
+  [ABSTTL]
+  [IDLETIME <seconds>]
+  [FREQ <frequency>]
 ```
 
 ## Arguments
@@ -25837,7 +25849,11 @@ Each position is encoded into a 52-bit geohash and stored as the score of the me
 ## Syntax
 
 ```redis
-GEOADD <key> [NX | XX] [CH] <longitude> <latitude> <member> [<longitude> <latitude> <member> ...]
+GEOADD <key>
+  [NX | XX]
+  [CH]
+  <longitude> <latitude> <member>
+  [<longitude> <latitude> <member> ...]
 ```
 
 ## Arguments
@@ -26515,18 +26531,28 @@ fn main() -> redis::RedisResult<()> {
 # GEORADIUS
 Source: https://upstash.com/docs/redis/commands/geo/georadius
 
+<Warning>
+  Prefer [`GEOSEARCH`](/docs/redis/commands/geo/geosearch) with `FROMLONLAT` and `BYRADIUS` in new code: `GEOSEARCH <key> FROMLONLAT <longitude> <latitude> BYRADIUS <radius> (m | km | ft | mi)`. In place of `STORE` and `STOREDIST`, use [`GEOSEARCHSTORE`](/docs/redis/commands/geo/geosearchstore) with the same query. `GEORADIUS` is deprecated in Redis but still supported by Upstash.
+</Warning>
+
 Use `GEORADIUS` to find the members of a geospatial index that lie within a given radius of a longitude and latitude point.
 
 By default only member names are returned. `WITHDIST` adds each member's distance from the center in the unit of the query, `WITHCOORD` adds its coordinates, and `WITHHASH` adds its raw 52-bit geohash score. `COUNT` caps the number of results and, combined with `ANY`, lets the server stop as soon as it has enough matches instead of examining the whole area, which is faster but returns an arbitrary subset rather than the nearest ones. `ASC` and `DESC` sort the results by distance from the center.
 
 `STORE` writes the matching members into a sorted set scored by geohash, so the result stays usable as a geospatial index, while `STOREDIST` scores them by their distance from the center, which makes the result easy to page through by proximity.
 
-Redis deprecated `GEORADIUS` in favor of [`GEOSEARCH`](/docs/redis/commands/geo/geosearch) and [`GEOSEARCHSTORE`](/docs/redis/commands/geo/geosearchstore), which do the same work and additionally support rectangular areas. Use [`GEORADIUS_RO`](/docs/redis/commands/geo/georadius-ro) if you want a form that cannot write.
+[`GEOSEARCH`](/docs/redis/commands/geo/geosearch) and [`GEOSEARCHSTORE`](/docs/redis/commands/geo/geosearchstore) do the same work and additionally support rectangular areas. Use [`GEORADIUS_RO`](/docs/redis/commands/geo/georadius-ro) if you want a form that cannot write.
 
 ## Syntax
 
 ```redis
-GEORADIUS <key> <longitude> <latitude> <radius> (m | km | ft | mi) [WITHCOORD] [WITHDIST] [WITHHASH] [COUNT <count> [ANY]] [ASC | DESC] [STORE <storekey> | STOREDIST <storedistkey>]
+GEORADIUS <key> <longitude> <latitude> <radius> (m | km | ft | mi)
+  [WITHCOORD]
+  [WITHDIST]
+  [WITHHASH]
+  [COUNT <count> [ANY]]
+  [ASC | DESC]
+  [STORE <storekey> | STOREDIST <storedistkey>]
 ```
 
 ## Arguments
@@ -26694,16 +26720,25 @@ fn main() -> redis::RedisResult<()> {
 # GEORADIUS_RO
 Source: https://upstash.com/docs/redis/commands/geo/georadius-ro
 
+<Warning>
+  Prefer [`GEOSEARCH`](/docs/redis/commands/geo/geosearch) with `FROMLONLAT` and `BYRADIUS` in new code: `GEOSEARCH <key> FROMLONLAT <longitude> <latitude> BYRADIUS <radius> (m | km | ft | mi)`. `GEORADIUS_RO` is deprecated in Redis but still supported by Upstash.
+</Warning>
+
 Use `GEORADIUS_RO` to find members within a radius of a point. It is the read-only form of [`GEORADIUS`](/docs/redis/commands/geo/georadius).
 
 It accepts the same query and the same `WITHCOORD`, `WITHDIST`, `WITHHASH`, `COUNT`, and sorting options, but it has no `STORE` or `STOREDIST` clause, so the server knows the call cannot write and can serve it on replicas and from read-only scripts.
 
-Like `GEORADIUS`, it is deprecated in favor of [`GEOSEARCH`](/docs/redis/commands/geo/geosearch), which is read-only as well and also supports rectangular areas.
+[`GEOSEARCH`](/docs/redis/commands/geo/geosearch) is read-only as well and also supports rectangular areas.
 
 ## Syntax
 
 ```redis
-GEORADIUS_RO <key> <longitude> <latitude> <radius> (m | km | ft | mi) [WITHCOORD] [WITHDIST] [WITHHASH] [COUNT <count> [ANY]] [ASC | DESC]
+GEORADIUS_RO <key> <longitude> <latitude> <radius> (m | km | ft | mi)
+  [WITHCOORD]
+  [WITHDIST]
+  [WITHHASH]
+  [COUNT <count> [ANY]]
+  [ASC | DESC]
 ```
 
 ## Arguments
@@ -26870,16 +26905,26 @@ fn main() -> redis::RedisResult<()> {
 # GEORADIUSBYMEMBER
 Source: https://upstash.com/docs/redis/commands/geo/georadiusbymember
 
+<Warning>
+  Prefer [`GEOSEARCH`](/docs/redis/commands/geo/geosearch) with `FROMMEMBER` and `BYRADIUS` in new code: `GEOSEARCH <key> FROMMEMBER <member> BYRADIUS <radius> (m | km | ft | mi)`. In place of `STORE` and `STOREDIST`, use [`GEOSEARCHSTORE`](/docs/redis/commands/geo/geosearchstore) with the same query. `GEORADIUSBYMEMBER` is deprecated in Redis but still supported by Upstash.
+</Warning>
+
 Use `GEORADIUSBYMEMBER` to find the members of a geospatial index that lie within a given radius of another member.
 
 It works exactly like [`GEORADIUS`](/docs/redis/commands/geo/georadius) except that the center is the stored position of a member instead of an explicit coordinate pair, which saves a lookup when the reference point is already in the index (a store, a driver, a landmark). The reference member itself always matches, since its distance from itself is zero, so remember to filter it out or ask for one result more than you need.
 
-The same `WITHCOORD`, `WITHDIST`, `WITHHASH`, `COUNT`, sorting, and `STORE` or `STOREDIST` options apply. Redis deprecated the command in favor of [`GEOSEARCH`](/docs/redis/commands/geo/geosearch) with `FROMMEMBER`.
+The same `WITHCOORD`, `WITHDIST`, `WITHHASH`, `COUNT`, sorting, and `STORE` or `STOREDIST` options apply.
 
 ## Syntax
 
 ```redis
-GEORADIUSBYMEMBER <key> <member> <radius> (m | km | ft | mi) [WITHCOORD] [WITHDIST] [WITHHASH] [COUNT <count> [ANY]] [ASC | DESC] [STORE <storekey> | STOREDIST <storedistkey>]
+GEORADIUSBYMEMBER <key> <member> <radius> (m | km | ft | mi)
+  [WITHCOORD]
+  [WITHDIST]
+  [WITHHASH]
+  [COUNT <count> [ANY]]
+  [ASC | DESC]
+  [STORE <storekey> | STOREDIST <storedistkey>]
 ```
 
 ## Arguments
@@ -27045,16 +27090,23 @@ fn main() -> redis::RedisResult<()> {
 # GEORADIUSBYMEMBER_RO
 Source: https://upstash.com/docs/redis/commands/geo/georadiusbymember-ro
 
+<Warning>
+  Prefer [`GEOSEARCH`](/docs/redis/commands/geo/geosearch) with `FROMMEMBER` and `BYRADIUS` in new code: `GEOSEARCH <key> FROMMEMBER <member> BYRADIUS <radius> (m | km | ft | mi)`. `GEORADIUSBYMEMBER_RO` is deprecated in Redis but still supported by Upstash.
+</Warning>
+
 Use `GEORADIUSBYMEMBER_RO` to find members within a radius of another member. It is the read-only form of [`GEORADIUSBYMEMBER`](/docs/redis/commands/geo/georadiusbymember).
 
 The center is the stored position of the given member, which always appears among the matches at distance zero. The command accepts the same `WITHCOORD`, `WITHDIST`, `WITHHASH`, `COUNT`, and sorting options but has no `STORE` or `STOREDIST` clause, so it can be served on replicas and used from read-only scripts.
 
-Like the writable form, it is deprecated in favor of [`GEOSEARCH`](/docs/redis/commands/geo/geosearch) with `FROMMEMBER`.
-
 ## Syntax
 
 ```redis
-GEORADIUSBYMEMBER_RO <key> <member> <radius> (m | km | ft | mi) [WITHCOORD] [WITHDIST] [WITHHASH] [COUNT <count> [ANY]] [ASC | DESC]
+GEORADIUSBYMEMBER_RO <key> <member> <radius> (m | km | ft | mi)
+  [WITHCOORD]
+  [WITHDIST]
+  [WITHHASH]
+  [COUNT <count> [ANY]]
+  [ASC | DESC]
 ```
 
 ## Arguments
@@ -27230,7 +27282,15 @@ By default only member names come back. `WITHDIST` adds the distance from the ce
 ## Syntax
 
 ```redis
-GEOSEARCH <key> (FROMMEMBER <member> | FROMLONLAT <longitude> <latitude>) (BYRADIUS <radius> (m | km | ft | mi) | BYBOX <width> <height> (m | km | ft | mi)) [ASC | DESC] [COUNT <count> [ANY]] [WITHCOORD] [WITHDIST] [WITHHASH]
+GEOSEARCH <key>
+  (FROMMEMBER <member> | FROMLONLAT <longitude> <latitude>)
+  (BYRADIUS <radius> (m | km | ft | mi) |
+    BYBOX <width> <height> (m | km | ft | mi))
+  [ASC | DESC]
+  [COUNT <count> [ANY]]
+  [WITHCOORD]
+  [WITHDIST]
+  [WITHHASH]
 ```
 
 ## Arguments
@@ -27412,7 +27472,13 @@ The destination is overwritten on every call, and it is deleted when the query m
 ## Syntax
 
 ```redis
-GEOSEARCHSTORE <destination> <source> (FROMMEMBER <member> | FROMLONLAT <longitude> <latitude>) (BYRADIUS <radius> (m | km | ft | mi) | BYBOX <width> <height> (m | km | ft | mi)) [ASC | DESC] [COUNT <count> [ANY]] [STOREDIST]
+GEOSEARCHSTORE <destination> <source>
+  (FROMMEMBER <member> | FROMLONLAT <longitude> <latitude>)
+  (BYRADIUS <radius> (m | km | ft | mi) |
+    BYBOX <width> <height> (m | km | ft | mi))
+  [ASC | DESC]
+  [COUNT <count> [ANY]]
+  [STOREDIST]
 ```
 
 ## Arguments
@@ -27949,7 +28015,9 @@ The reply holds one status code per field, in order: `1` when the expiration was
 ## Syntax
 
 ```redis
-HEXPIRE <key> <seconds> [NX | XX | GT | LT] FIELDS <numfields> <field> [<field> ...]
+HEXPIRE <key> <seconds>
+  [NX | XX | GT | LT]
+  FIELDS <numfields> <field> [<field> ...]
 ```
 
 ## Arguments
@@ -28129,7 +28197,9 @@ The reply holds one status code per field: `1` when the expiration was set, `0`
 ## Syntax
 
 ```redis
-HEXPIREAT <key> <unix-time-seconds> [NX | XX | GT | LT] FIELDS <numfields> <field> [<field> ...]
+HEXPIREAT <key> <unix-time-seconds>
+  [NX | XX | GT | LT]
+  FIELDS <numfields> <field> [<field> ...]
 ```
 
 ## Arguments
@@ -29001,7 +29071,10 @@ Doing both in one command is what makes sliding expirations possible per field:
 ## Syntax
 
 ```redis
-HGETEX <key> [EX <seconds> | PX <milliseconds> | EXAT <unix-time-seconds> | PXAT <unix-time-milliseconds> | PERSIST] FIELDS <numfields> <field> [<field> ...]
+HGETEX <key>
+  [EX <seconds> | PX <milliseconds> | EXAT <unix-time-seconds> |
+    PXAT <unix-time-milliseconds> | PERSIST]
+  FIELDS <numfields> <field> [<field> ...]
 ```
 
 ## Arguments
@@ -30029,9 +30102,13 @@ fn main() -> redis::RedisResult<()> {
 # HMSET
 Source: https://upstash.com/docs/redis/commands/hash/hmset
 
+<Warning>
+  Prefer [`HSET`](/docs/redis/commands/hash/hset) with multiple field-value pairs in new code: `HSET <key> <field> <value> [<field> <value> ...]`. `HMSET` is deprecated in Redis but still supported by Upstash.
+</Warning>
+
 Use `HMSET` to set several field and value pairs of a hash in one call, creating the key if it does not exist.
 
-Existing fields are overwritten and the reply is always `OK`, so it says nothing about what changed. `HMSET` is deprecated in Redis: [`HSET`](/docs/redis/commands/hash/hset) accepts multiple pairs as well and additionally reports how many fields were new, so prefer it in new code.
+Existing fields are overwritten and the reply is always `OK`, so it says nothing about what changed. [`HSET`](/docs/redis/commands/hash/hset) accepts multiple pairs as well and additionally reports how many fields were new, so prefer it in new code.
 
 ## Syntax
 
@@ -30377,7 +30454,9 @@ It is the millisecond form of [`HEXPIRE`](/docs/redis/commands/hash/hexpire) and
 ## Syntax
 
 ```redis
-HPEXPIRE <key> <milliseconds> [NX | XX | GT | LT] FIELDS <numfields> <field> [<field> ...]
+HPEXPIRE <key> <milliseconds>
+  [NX | XX | GT | LT]
+  FIELDS <numfields> <field> [<field> ...]
 ```
 
 ## Arguments
@@ -30555,7 +30634,9 @@ It combines the absolute deadline of [`HEXPIREAT`](/docs/redis/commands/hash/hex
 ## Syntax
 
 ```redis
-HPEXPIREAT <key> <unix-time-milliseconds> [NX | XX | GT | LT] FIELDS <numfields> <field> [<field> ...]
+HPEXPIREAT <key> <unix-time-milliseconds>
+  [NX | XX | GT | LT]
+  FIELDS <numfields> <field> [<field> ...]
 ```
 
 ## Arguments
@@ -31615,7 +31696,11 @@ Use `HSETEX` to write hash fields and set their expiration in the same atomic ca
 ## Syntax
 
 ```redis
-HSETEX <key> [FNX | FXX] [EX <seconds> | PX <milliseconds> | EXAT <unix-time-seconds> | PXAT <unix-time-milliseconds> | KEEPTTL] FIELDS <numfields> <field> <value> [<field> <value> ...]
+HSETEX <key>
+  [FNX | FXX]
+  [EX <seconds> | PX <milliseconds> | EXAT <unix-time-seconds> |
+    PXAT <unix-time-milliseconds> | KEEPTTL]
+  FIELDS <numfields> <field> <value> [<field> <value> ...]
 ```
 
 ## Arguments
@@ -34743,7 +34828,11 @@ Without a path the whole document is returned. The reply shape depends on the pa
 ## Syntax
 
 ```redis
-JSON.GET <key> [INDENT indent] [NEWLINE newline] [SPACE space] [path [path ...]]
+JSON.GET <key>
+  [INDENT indent]
+  [NEWLINE newline]
+  [SPACE space]
+  [path [path ...]]
 ```
 
 ## Arguments
@@ -37866,11 +37955,15 @@ fn main() -> redis::RedisResult<()> {
 # BRPOPLPUSH
 Source: https://upstash.com/docs/redis/commands/list/brpoplpush
 
+<Warning>
+  Prefer [`BLMOVE`](/docs/redis/commands/list/blmove) with `RIGHT` and `LEFT` in new code: `BLMOVE <source> <destination> RIGHT LEFT <timeout>`. `BRPOPLPUSH` is deprecated in Redis but still supported by Upstash.
+</Warning>
+
 Use `BRPOPLPUSH` to pop an element from the tail of one list and push it to the head of another, blocking until the source has an element or the timeout expires.
 
 It is the blocking form of [`RPOPLPUSH`](/docs/redis/commands/list/rpoplpush). The timeout is in seconds, may be fractional, and `0` waits indefinitely; when it expires the reply is null. Since the element moves atomically into the destination, a worker that crashes after taking an item leaves it visible in the processing list, where it can be recovered.
 
-Redis deprecates this command in favor of [`BLMOVE`](/docs/redis/commands/list/blmove), which does the same thing and additionally lets you choose which end of each list to use.
+[`BLMOVE`](/docs/redis/commands/list/blmove) does the same thing and additionally lets you choose which end of each list to use.
 
 ## Syntax
 
@@ -40443,11 +40536,15 @@ fn main() -> redis::RedisResult<()> {
 # RPOPLPUSH
 Source: https://upstash.com/docs/redis/commands/list/rpoplpush
 
+<Warning>
+  Prefer [`LMOVE`](/docs/redis/commands/list/lmove) with `RIGHT` and `LEFT` in new code: `LMOVE <source> <destination> RIGHT LEFT`. `RPOPLPUSH` is deprecated in Redis but still supported by Upstash.
+</Warning>
+
 Use `RPOPLPUSH` to atomically move an element from the tail of one list to the head of another, returning the element.
 
 If the source is empty nothing happens and the reply is null. Source and destination may be the same key, which rotates the list: the tail element becomes the new head, so repeated calls cycle through a list of items forever, a handy pattern for round-robin scheduling.
 
-The command is deprecated in Redis in favor of [`LMOVE`](/docs/redis/commands/list/lmove), which does the same thing but lets you choose both ends. [`BRPOPLPUSH`](/docs/redis/commands/list/brpoplpush) is the blocking form.
+[`LMOVE`](/docs/redis/commands/list/lmove) does the same thing but lets you choose both ends, and [`BRPOPLPUSH`](/docs/redis/commands/list/brpoplpush) is the blocking form.
 
 ## Syntax
 
@@ -42684,14 +42781,6 @@ Source: https://upstash.com/docs/redis/commands/scripting/overview
 <Card title="SCRIPT LOAD" href="/redis/commands/scripting/script-load">Load script into cache</Card>
 </CardGroup>
 
-Lua scripts run under the database's global lock by default. To let scripts that
-touch disjoint keys run in parallel, add the `allow-key-locking` flag to the
-script's shebang line, as described in
-[Key-Based Locking](/docs/redis/features/key-locking). Either way, pass every key a
-script touches through `KEYS` instead of building it inside the script, so that
-a key that is not in memory is not read from disk while the lock is held. See
-[Dynamic Keys and Latency](/docs/redis/features/key-locking#dynamic-keys-and-latency).
-
 # SCRIPT EXISTS
 Source: https://upstash.com/docs/redis/commands/scripting/script-exists
 
@@ -50984,7 +51073,10 @@ The result is not stored; use [`ZINTERSTORE`](/docs/redis/commands/sorted-set/zi
 ## Syntax
 
 ```redis
-ZINTER <numkeys> <key> [<key> ...] [WEIGHTS <weight> [<weight> ...]] [AGGREGATE SUM | MIN | MAX] [WITHSCORES]
+ZINTER <numkeys> <key> [<key> ...]
+  [WEIGHTS <weight> [<weight> ...]]
+  [AGGREGATE SUM | MIN | MAX]
+  [WITHSCORES]
 ```
 
 ## Arguments
@@ -51318,7 +51410,9 @@ This is how a combined ranking is built once, for instance blending a relevance
 ## Syntax
 
 ```redis
-ZINTERSTORE <destination> <numkeys> <key> [<key> ...] [WEIGHTS <weight> [<weight> ...]] [AGGREGATE SUM | MIN | MAX]
+ZINTERSTORE <destination> <numkeys> <key> [<key> ...]
+  [WEIGHTS <weight> [<weight> ...]]
+  [AGGREGATE SUM | MIN | MAX]
 ```
 
 ## Arguments
@@ -52538,7 +52632,11 @@ The option that follows changes what those two arguments mean. `BYSCORE` reads t
 ## Syntax
 
 ```redis
-ZRANGE <key> <start> <stop> [BYSCORE | BYLEX] [REV] [LIMIT <offset> <count>] [WITHSCORES]
+ZRANGE <key> <start> <stop>
+  [BYSCORE | BYLEX]
+  [REV]
+  [LIMIT <offset> <count>]
+  [WITHSCORES]
 ```
 
 ## Arguments
@@ -52712,14 +52810,16 @@ fn main() -> redis::RedisResult<()> {
 # ZRANGEBYLEX
 Source: https://upstash.com/docs/redis/commands/sorted-set/zrangebylex
 
+<Warning>
+  Prefer [`ZRANGE`](/docs/redis/commands/sorted-set/zrange) with `BYLEX` in new code: `ZRANGE <key> <min> <max> BYLEX [LIMIT <offset> <count>]`. `ZRANGEBYLEX` is deprecated in Redis but still supported by Upstash.
+</Warning>
+
 Use `ZRANGEBYLEX` to list the members of a sorted set that fall in a lexicographic range.
 
 Bounds are written `[member` for inclusive and `(member` for exclusive, with `-` and `+` standing for the lowest and highest possible members. `LIMIT <offset> <count>` pages through the result.
 
 The ordering used here is the byte order of member names, which is only meaningful when every member has the same score. Giving all members score `0` turns a sorted set into a sorted string index, which is how prefix lookups and autocomplete are built on top of it.
 
-The command is deprecated in Redis in favor of [`ZRANGE`](/docs/redis/commands/sorted-set/zrange) with `BYLEX`, which accepts the same bounds.
-
 ## Syntax
 
 ```redis
@@ -52880,11 +52980,15 @@ fn main() -> redis::RedisResult<()> {
 # ZRANGEBYSCORE
 Source: https://upstash.com/docs/redis/commands/sorted-set/zrangebyscore
 
+<Warning>
+  Prefer [`ZRANGE`](/docs/redis/commands/sorted-set/zrange) with `BYSCORE` in new code: `ZRANGE <key> <min> <max> BYSCORE [LIMIT <offset> <count>] [WITHSCORES]`. `ZRANGEBYSCORE` is deprecated in Redis but still supported by Upstash.
+</Warning>
+
 Use `ZRANGEBYSCORE` to list the members of a sorted set whose score falls in a range, from the lowest score up.
 
 Bounds are inclusive by default, become exclusive when prefixed with `(`, and accept `-inf` and `+inf` for open ends. `WITHSCORES` returns each member with its score, and `LIMIT <offset> <count>` pages through the result, which is how you take the first N above a threshold without transferring the rest.
 
-With timestamps as scores this is the natural range query over time. The command is deprecated in Redis in favor of [`ZRANGE`](/docs/redis/commands/sorted-set/zrange) with `BYSCORE`.
+With timestamps as scores this is the natural range query over time.
 
 ## Syntax
 
@@ -53060,7 +53164,10 @@ This is how a slice of a large ranking is materialized once, for instance the to
 ## Syntax
 
 ```redis
-ZRANGESTORE <dst> <src> <min> <max> [BYSCORE | BYLEX] [REV] [LIMIT <offset> <count>]
+ZRANGESTORE <dst> <src> <min> <max>
+  [BYSCORE | BYLEX]
+  [REV]
+  [LIMIT <offset> <count>]
 ```
 
 ## Arguments
@@ -54069,12 +54176,14 @@ fn main() -> redis::RedisResult<()> {
 # ZREVRANGE
 Source: https://upstash.com/docs/redis/commands/sorted-set/zrevrange
 
+<Warning>
+  Prefer [`ZRANGE`](/docs/redis/commands/sorted-set/zrange) with `REV` in new code: `ZRANGE <key> <start> <stop> REV [WITHSCORES]`. `ZREVRANGE` is deprecated in Redis but still supported by Upstash.
+</Warning>
+
 Use `ZREVRANGE` to list a range of members of a sorted set ordered from the highest score down.
 
 `<start>` and `<stop>` are zero-based, inclusive positions in that reversed ordering, so `0 9` returns the ten highest scoring members, the usual shape of a leaderboard page. Negative indexes count from the end, and `WITHSCORES` includes each member's score.
 
-The command is deprecated in Redis in favor of [`ZRANGE`](/docs/redis/commands/sorted-set/zrange) with `REV`.
-
 ## Syntax
 
 ```redis
@@ -54239,11 +54348,15 @@ fn main() -> redis::RedisResult<()> {
 # ZREVRANGEBYLEX
 Source: https://upstash.com/docs/redis/commands/sorted-set/zrevrangebylex
 
+<Warning>
+  Prefer [`ZRANGE`](/docs/redis/commands/sorted-set/zrange) with `BYLEX` and `REV` in new code: `ZRANGE <key> <max> <min> BYLEX REV [LIMIT <offset> <count>]`. `ZREVRANGEBYLEX` is deprecated in Redis but still supported by Upstash.
+</Warning>
+
 Use `ZREVRANGEBYLEX` to list the members in a lexicographic range, in reverse order.
 
 The bounds are given highest first, `<max>` before `<min>`, written `[member` for inclusive and `(member` for exclusive, with `+` and `-` for the extremes. `LIMIT <offset> <count>` pages through the result.
 
-As with every lexicographic operation, the ordering is only meaningful when all members share the same score. The command is deprecated in Redis in favor of [`ZRANGE`](/docs/redis/commands/sorted-set/zrange) with `BYLEX` and `REV`.
+As with every lexicographic operation, the ordering is only meaningful when all members share the same score.
 
 ## Syntax
 
@@ -54405,12 +54518,14 @@ fn main() -> redis::RedisResult<()> {
 # ZREVRANGEBYSCORE
 Source: https://upstash.com/docs/redis/commands/sorted-set/zrevrangebyscore
 
+<Warning>
+  Prefer [`ZRANGE`](/docs/redis/commands/sorted-set/zrange) with `BYSCORE` and `REV` in new code: `ZRANGE <key> <max> <min> BYSCORE REV [LIMIT <offset> <count>] [WITHSCORES]`. `ZREVRANGEBYSCORE` is deprecated in Redis but still supported by Upstash.
+</Warning>
+
 Use `ZREVRANGEBYSCORE` to list the members in a score range, ordered from the highest score down.
 
 The bounds are given highest first, `<max>` before `<min>`. They are inclusive by default, become exclusive when prefixed with `(`, and accept `+inf` and `-inf`. `WITHSCORES` returns the scores and `LIMIT <offset> <count>` pages through the result, which is the usual way to fetch "the top N above a threshold".
 
-The command is deprecated in Redis in favor of [`ZRANGE`](/docs/redis/commands/sorted-set/zrange) with `BYSCORE` and `REV`.
-
 ## Syntax
 
 ```redis
@@ -55120,7 +55235,10 @@ The result is computed on each call and not stored; use [`ZUNIONSTORE`](/docs/re
 ## Syntax
 
 ```redis
-ZUNION <numkeys> <key> [<key> ...] [WEIGHTS <weight> [<weight> ...]] [AGGREGATE SUM | MIN | MAX] [WITHSCORES]
+ZUNION <numkeys> <key> [<key> ...]
+  [WEIGHTS <weight> [<weight> ...]]
+  [AGGREGATE SUM | MIN | MAX]
+  [WITHSCORES]
 ```
 
 ## Arguments
@@ -55297,7 +55415,9 @@ Merging per-day or per-source rankings into a combined one, weighting them as yo
 ## Syntax
 
 ```redis
-ZUNIONSTORE <destination> <numkeys> <key> [<key> ...] [WEIGHTS <weight> [<weight> ...]] [AGGREGATE SUM | MIN | MAX]
+ZUNIONSTORE <destination> <numkeys> <key> [<key> ...]
+  [WEIGHTS <weight> [<weight> ...]]
+  [AGGREGATE SUM | MIN | MAX]
 ```
 
 ## Arguments
@@ -55676,7 +55796,9 @@ The reference policy controls what happens to consumer group references of the d
 ## Syntax
 
 ```redis
-XACKDEL <key> <group> [KEEPREF | DELREF | ACKED] IDS <numids> <id> [<id> ...]
+XACKDEL <key> <group>
+  [KEEPREF | DELREF | ACKED]
+  IDS <numids> <id> [<id> ...]
 ```
 
 ## Arguments
@@ -55850,7 +55972,11 @@ The trimming options cap the stream in the same call, which is how a stream is k
 ## Syntax
 
 ```redis
-XADD <key> [NOMKSTREAM] [KEEPREF | DELREF | ACKED] [(MAXLEN | MINID) [= | ~] <threshold> [LIMIT <count>]] (* | <id>) <field> <value> [<field> <value> ...]
+XADD <key>
+  [NOMKSTREAM]
+  [KEEPREF | DELREF | ACKED]
+  [(MAXLEN | MINID) [= | ~] <threshold> [LIMIT <count>]]
+  (* | <id>) <field> <value> [<field> <value> ...]
 ```
 
 ## Arguments
@@ -56208,7 +56334,13 @@ When you want to claim whatever is idle rather than specific IDs, use [`XAUTOCLA
 ## Syntax
 
 ```redis
-XCLAIM <key> <group> <consumer> <min-idle-time> <ID> [<ID> ...] [IDLE <ms>] [TIME <unix-time-milliseconds>] [RETRYCOUNT <count>] [FORCE] [JUSTID] [LASTID <lastid>]
+XCLAIM <key> <group> <consumer> <min-idle-time> <ID> [<ID> ...]
+  [IDLE <ms>]
+  [TIME <unix-time-milliseconds>]
+  [RETRYCOUNT <count>]
+  [FORCE]
+  [JUSTID]
+  [LASTID <lastid>]
 ```
 
 ## Arguments
@@ -56560,7 +56692,9 @@ That last policy is what makes the command useful as a safe cleanup step: it rem
 ## Syntax
 
 ```redis
-XDELEX <key> [KEEPREF | DELREF | ACKED] IDS <numids> <id> [<id> ...]
+XDELEX <key>
+  [KEEPREF | DELREF | ACKED]
+  IDS <numids> <id> [<id> ...]
 ```
 
 ## Arguments
@@ -57575,7 +57709,10 @@ A high delivery count points at an entry that keeps failing, and a long idle tim
 ## Syntax
 
 ```redis
-XPENDING <key> <group> [[IDLE <min-idle-time>] <start> <end> <count> [<consumer>]]
+XPENDING <key> <group>
+  [[IDLE <min-idle-time>]
+    <start> <end> <count>
+    [<consumer>]]
 ```
 
 ## Arguments
@@ -57916,7 +58053,10 @@ After `STREAMS`, all keys are listed first and then exactly one ID for each key,
 ## Syntax
 
 ```redis
-XREAD [COUNT <count>] [BLOCK <milliseconds>] STREAMS <key> [<key> ...] <ID> [<ID> ...]
+XREAD
+  [COUNT <count>]
+  [BLOCK <milliseconds>]
+  STREAMS <key> [<key> ...] <ID> [<ID> ...]
 ```
 
 ## Arguments
@@ -58092,7 +58232,11 @@ Entries stay pending until acknowledged with [`XACK`](/docs/redis/commands/strea
 ## Syntax
 
 ```redis
-XREADGROUP GROUP <group> <consumer> [COUNT <count>] [BLOCK <milliseconds>] [NOACK] STREAMS <key> [<key> ...] <ID> [<ID> ...]
+XREADGROUP GROUP <group> <consumer>
+  [COUNT <count>]
+  [BLOCK <milliseconds>]
+  [NOACK]
+  STREAMS <key> [<key> ...] <ID> [<ID> ...]
 ```
 
 ## Arguments
@@ -58445,7 +58589,10 @@ Use `XTRIM` to cap the size of a stream by removing old entries.
 ## Syntax
 
 ```redis
-XTRIM <key> (MAXLEN | MINID) [= | ~] <threshold> [LIMIT <count>] [KEEPREF | DELREF | ACKED]
+XTRIM <key>
+  (MAXLEN | MINID) [= | ~] <threshold>
+  [LIMIT <count>]
+  [KEEPREF | DELREF | ACKED]
 ```
 
 ## Arguments
@@ -59793,7 +59940,9 @@ Doing both at once is what makes a sliding expiration correct: reading a session
 ## Syntax
 
 ```redis
-GETEX <key> [EX <seconds> | PX <milliseconds> | EXAT <unix-time-seconds> | PXAT <unix-time-milliseconds> | PERSIST]
+GETEX <key>
+  [EX <seconds> | PX <milliseconds> | EXAT <unix-time-seconds> |
+    PXAT <unix-time-milliseconds> | PERSIST]
 ```
 
 ## Arguments
@@ -60125,11 +60274,15 @@ fn main() -> redis::RedisResult<()> {
 # GETSET
 Source: https://upstash.com/docs/redis/commands/string/getset
 
+<Warning>
+  Prefer [`SET`](/docs/redis/commands/string/set) with the `GET` argument in new code: `SET <key> <value> GET`. `GETSET` is deprecated in Redis but still supported by Upstash.
+</Warning>
+
 Use `GETSET` to set a new value and get the previous one in a single atomic step.
 
 The reply is the old value, or null when the key did not exist. Note that the key's time to live is discarded, so a key with an expiration becomes permanent when written this way.
 
-The classic use is resetting a counter while reading it, where the atomicity guarantees nothing is counted twice. Redis deprecates the command in favor of [`SET`](/docs/redis/commands/string/set) with the `GET` option, which does the same thing and can additionally set or keep an expiration in the same call.
+The classic use is resetting a counter while reading it, where the atomicity guarantees nothing is counted twice. [`SET`](/docs/redis/commands/string/set) with the `GET` option does the same thing and can additionally set or keep an expiration in the same call.
 
 ## Syntax
 
@@ -61345,11 +61498,15 @@ Source: https://upstash.com/docs/redis/commands/string/overview
 # PSETEX
 Source: https://upstash.com/docs/redis/commands/string/psetex
 
+<Warning>
+  Prefer [`SET`](/docs/redis/commands/string/set) with the `PX` argument in new code: `SET <key> <value> PX <milliseconds>`. `PSETEX` is deprecated in Redis but still supported by Upstash.
+</Warning>
+
 Use `PSETEX` to set a value together with a lifetime in milliseconds.
 
 The value and the expiration are applied in the same atomic step, so the key never exists without its expiration, which is the point of the command: setting the value and then expiring it separately leaves a window where a crash makes the key permanent. A lifetime of zero or less returns an error.
 
-It is the millisecond form of [`SETEX`](/docs/redis/commands/string/setex), and equivalent to [`SET`](/docs/redis/commands/string/set) with the `PX` option, which is the more flexible way to write the same thing.
+It is the millisecond form of [`SETEX`](/docs/redis/commands/string/setex), and [`SET`](/docs/redis/commands/string/set) with the `PX` option is the more flexible way to write the same thing.
 
 ## Syntax
 
@@ -61526,7 +61683,12 @@ The condition decides whether the write happens at all. `NX` writes only when th
 ## Syntax
 
 ```redis
-SET <key> <value> [NX | XX | IFEQ <ifeq-value> | IFNE <ifne-value> | IFDEQ <ifdeq-digest> | IFDNE <ifdne-digest>] [GET] [EX <seconds> | PX <milliseconds> | EXAT <unix-time-seconds> | PXAT <unix-time-milliseconds> | KEEPTTL]
+SET <key> <value>
+  [NX | XX | IFEQ <ifeq-value> | IFNE <ifne-value> |
+    IFDEQ <ifdeq-digest> | IFDNE <ifdne-digest>]
+  [GET]
+  [EX <seconds> | PX <milliseconds> | EXAT <unix-time-seconds> |
+    PXAT <unix-time-milliseconds> | KEEPTTL]
 ```
 
 ## Arguments
@@ -61694,11 +61856,15 @@ fn main() -> redis::RedisResult<()> {
 # SETEX
 Source: https://upstash.com/docs/redis/commands/string/setex
 
+<Warning>
+  Prefer [`SET`](/docs/redis/commands/string/set) with the `EX` argument in new code: `SET <key> <value> EX <seconds>`. `SETEX` is deprecated in Redis but still supported by Upstash.
+</Warning>
+
 Use `SETEX` to set a value together with a lifetime in seconds.
 
 The value and the expiration are applied atomically, so the key never exists without an expiration; writing the value and expiring it in two commands leaves a window in which a failure makes the key permanent. A lifetime of zero or less returns an error.
 
-Use [`PSETEX`](/docs/redis/commands/string/psetex) for millisecond precision. Both are equivalent to [`SET`](/docs/redis/commands/string/set) with `EX` or `PX`, which additionally supports conditions and reading the previous value.
+Use [`PSETEX`](/docs/redis/commands/string/psetex) for millisecond precision. [`SET`](/docs/redis/commands/string/set) with `EX` or `PX` does the same thing and additionally supports conditions and reading the previous value.
 
 ## Syntax
 
@@ -61864,6 +62030,10 @@ fn main() -> redis::RedisResult<()> {
 # SETNX
 Source: https://upstash.com/docs/redis/commands/string/setnx
 
+<Warning>
+  Prefer [`SET`](/docs/redis/commands/string/set) with the `NX` argument in new code: `SET <key> <value> NX`. `SETNX` is deprecated in Redis but still supported by Upstash.
+</Warning>
+
 Use `SETNX` to set a value only if the key does not already exist.
 
 The reply is `1` when the key was created and `0` when it was already there and nothing was written. The check and the write are atomic, so exactly one of several racing clients succeeds.
diff --git a/redis/commands/connection/quit.mdx b/redis/commands/connection/quit.mdx
index 9f1654123..ac317fd55 100644
--- a/redis/commands/connection/quit.mdx
+++ b/redis/commands/connection/quit.mdx
@@ -3,6 +3,10 @@ title: "QUIT"
 description: "Close the connection."
 ---
 
+<Warning>
+  Prefer closing the connection from the client in new code, which avoids leaving `TIME_WAIT` sockets on the server. `QUIT` has no replacement command; it is deprecated in Redis but still supported by Upstash.
+</Warning>
+
 Use `QUIT` to ask the server to close the connection once all pending replies have been sent.
 
 The server replies `OK` and then terminates the connection, so no reply is lost and the shutdown is clean from both sides. Modern clients usually just close the socket, and pooled connections should be returned to the pool rather than closed, so `QUIT` is mostly useful in scripts and interactive sessions.
diff --git a/redis/commands/geo/georadius-ro.mdx b/redis/commands/geo/georadius-ro.mdx
index d754330d7..d76159ba2 100644
--- a/redis/commands/geo/georadius-ro.mdx
+++ b/redis/commands/geo/georadius-ro.mdx
@@ -3,11 +3,15 @@ title: "GEORADIUS_RO"
 description: "Find members within a radius of a point."
 ---
 
+<Warning>
+  Prefer [`GEOSEARCH`](/redis/commands/geo/geosearch) with `FROMLONLAT` and `BYRADIUS` in new code: `GEOSEARCH <key> FROMLONLAT <longitude> <latitude> BYRADIUS <radius> (m | km | ft | mi)`. `GEORADIUS_RO` is deprecated in Redis but still supported by Upstash.
+</Warning>
+
 Use `GEORADIUS_RO` to find members within a radius of a point. It is the read-only form of [`GEORADIUS`](/redis/commands/geo/georadius).
 
 It accepts the same query and the same `WITHCOORD`, `WITHDIST`, `WITHHASH`, `COUNT`, and sorting options, but it has no `STORE` or `STOREDIST` clause, so the server knows the call cannot write and can serve it on replicas and from read-only scripts.
 
-Like `GEORADIUS`, it is deprecated in favor of [`GEOSEARCH`](/redis/commands/geo/geosearch), which is read-only as well and also supports rectangular areas.
+[`GEOSEARCH`](/redis/commands/geo/geosearch) is read-only as well and also supports rectangular areas.
 
 ## Syntax
 
diff --git a/redis/commands/geo/georadius.mdx b/redis/commands/geo/georadius.mdx
index 32d9e2367..4346df771 100644
--- a/redis/commands/geo/georadius.mdx
+++ b/redis/commands/geo/georadius.mdx
@@ -3,13 +3,17 @@ title: "GEORADIUS"
 description: "Find members within a radius of a point."
 ---
 
+<Warning>
+  Prefer [`GEOSEARCH`](/redis/commands/geo/geosearch) with `FROMLONLAT` and `BYRADIUS` in new code: `GEOSEARCH <key> FROMLONLAT <longitude> <latitude> BYRADIUS <radius> (m | km | ft | mi)`. In place of `STORE` and `STOREDIST`, use [`GEOSEARCHSTORE`](/redis/commands/geo/geosearchstore) with the same query. `GEORADIUS` is deprecated in Redis but still supported by Upstash.
+</Warning>
+
 Use `GEORADIUS` to find the members of a geospatial index that lie within a given radius of a longitude and latitude point.
 
 By default only member names are returned. `WITHDIST` adds each member's distance from the center in the unit of the query, `WITHCOORD` adds its coordinates, and `WITHHASH` adds its raw 52-bit geohash score. `COUNT` caps the number of results and, combined with `ANY`, lets the server stop as soon as it has enough matches instead of examining the whole area, which is faster but returns an arbitrary subset rather than the nearest ones. `ASC` and `DESC` sort the results by distance from the center.
 
 `STORE` writes the matching members into a sorted set scored by geohash, so the result stays usable as a geospatial index, while `STOREDIST` scores them by their distance from the center, which makes the result easy to page through by proximity.
 
-Redis deprecated `GEORADIUS` in favor of [`GEOSEARCH`](/redis/commands/geo/geosearch) and [`GEOSEARCHSTORE`](/redis/commands/geo/geosearchstore), which do the same work and additionally support rectangular areas. Use [`GEORADIUS_RO`](/redis/commands/geo/georadius-ro) if you want a form that cannot write.
+[`GEOSEARCH`](/redis/commands/geo/geosearch) and [`GEOSEARCHSTORE`](/redis/commands/geo/geosearchstore) do the same work and additionally support rectangular areas. Use [`GEORADIUS_RO`](/redis/commands/geo/georadius-ro) if you want a form that cannot write.
 
 ## Syntax
 
diff --git a/redis/commands/geo/georadiusbymember-ro.mdx b/redis/commands/geo/georadiusbymember-ro.mdx
index 7e94720be..317f075b7 100644
--- a/redis/commands/geo/georadiusbymember-ro.mdx
+++ b/redis/commands/geo/georadiusbymember-ro.mdx
@@ -3,12 +3,14 @@ title: "GEORADIUSBYMEMBER_RO"
 description: "Find members within a radius of another member."
 ---
 
+<Warning>
+  Prefer [`GEOSEARCH`](/redis/commands/geo/geosearch) with `FROMMEMBER` and `BYRADIUS` in new code: `GEOSEARCH <key> FROMMEMBER <member> BYRADIUS <radius> (m | km | ft | mi)`. `GEORADIUSBYMEMBER_RO` is deprecated in Redis but still supported by Upstash.
+</Warning>
+
 Use `GEORADIUSBYMEMBER_RO` to find members within a radius of another member. It is the read-only form of [`GEORADIUSBYMEMBER`](/redis/commands/geo/georadiusbymember).
 
 The center is the stored position of the given member, which always appears among the matches at distance zero. The command accepts the same `WITHCOORD`, `WITHDIST`, `WITHHASH`, `COUNT`, and sorting options but has no `STORE` or `STOREDIST` clause, so it can be served on replicas and used from read-only scripts.
 
-Like the writable form, it is deprecated in favor of [`GEOSEARCH`](/redis/commands/geo/geosearch) with `FROMMEMBER`.
-
 ## Syntax
 
 ```redis
diff --git a/redis/commands/geo/georadiusbymember.mdx b/redis/commands/geo/georadiusbymember.mdx
index 5c943a257..0e89d10fa 100644
--- a/redis/commands/geo/georadiusbymember.mdx
+++ b/redis/commands/geo/georadiusbymember.mdx
@@ -3,11 +3,15 @@ title: "GEORADIUSBYMEMBER"
 description: "Find members within a radius of another member."
 ---
 
+<Warning>
+  Prefer [`GEOSEARCH`](/redis/commands/geo/geosearch) with `FROMMEMBER` and `BYRADIUS` in new code: `GEOSEARCH <key> FROMMEMBER <member> BYRADIUS <radius> (m | km | ft | mi)`. In place of `STORE` and `STOREDIST`, use [`GEOSEARCHSTORE`](/redis/commands/geo/geosearchstore) with the same query. `GEORADIUSBYMEMBER` is deprecated in Redis but still supported by Upstash.
+</Warning>
+
 Use `GEORADIUSBYMEMBER` to find the members of a geospatial index that lie within a given radius of another member.
 
 It works exactly like [`GEORADIUS`](/redis/commands/geo/georadius) except that the center is the stored position of a member instead of an explicit coordinate pair, which saves a lookup when the reference point is already in the index (a store, a driver, a landmark). The reference member itself always matches, since its distance from itself is zero, so remember to filter it out or ask for one result more than you need.
 
-The same `WITHCOORD`, `WITHDIST`, `WITHHASH`, `COUNT`, sorting, and `STORE` or `STOREDIST` options apply. Redis deprecated the command in favor of [`GEOSEARCH`](/redis/commands/geo/geosearch) with `FROMMEMBER`.
+The same `WITHCOORD`, `WITHDIST`, `WITHHASH`, `COUNT`, sorting, and `STORE` or `STOREDIST` options apply.
 
 ## Syntax
 
diff --git a/redis/commands/hash/hmset.mdx b/redis/commands/hash/hmset.mdx
index 1ec1a6c2d..654e03370 100644
--- a/redis/commands/hash/hmset.mdx
+++ b/redis/commands/hash/hmset.mdx
@@ -3,9 +3,13 @@ title: "HMSET"
 description: "Set multiple hash fields."
 ---
 
+<Warning>
+  Prefer [`HSET`](/redis/commands/hash/hset) with multiple field-value pairs in new code: `HSET <key> <field> <value> [<field> <value> ...]`. `HMSET` is deprecated in Redis but still supported by Upstash.
+</Warning>
+
 Use `HMSET` to set several field and value pairs of a hash in one call, creating the key if it does not exist.
 
-Existing fields are overwritten and the reply is always `OK`, so it says nothing about what changed. `HMSET` is deprecated in Redis: [`HSET`](/redis/commands/hash/hset) accepts multiple pairs as well and additionally reports how many fields were new, so prefer it in new code.
+Existing fields are overwritten and the reply is always `OK`, so it says nothing about what changed. [`HSET`](/redis/commands/hash/hset) accepts multiple pairs as well and additionally reports how many fields were new, so prefer it in new code.
 
 ## Syntax
 
diff --git a/redis/commands/list/brpoplpush.mdx b/redis/commands/list/brpoplpush.mdx
index dc04ae70e..32f58af78 100644
--- a/redis/commands/list/brpoplpush.mdx
+++ b/redis/commands/list/brpoplpush.mdx
@@ -3,11 +3,15 @@ title: "BRPOPLPUSH"
 description: "Pop from a list's tail and push it to another, blocking until an element arrives."
 ---
 
+<Warning>
+  Prefer [`BLMOVE`](/redis/commands/list/blmove) with `RIGHT` and `LEFT` in new code: `BLMOVE <source> <destination> RIGHT LEFT <timeout>`. `BRPOPLPUSH` is deprecated in Redis but still supported by Upstash.
+</Warning>
+
 Use `BRPOPLPUSH` to pop an element from the tail of one list and push it to the head of another, blocking until the source has an element or the timeout expires.
 
 It is the blocking form of [`RPOPLPUSH`](/redis/commands/list/rpoplpush). The timeout is in seconds, may be fractional, and `0` waits indefinitely; when it expires the reply is null. Since the element moves atomically into the destination, a worker that crashes after taking an item leaves it visible in the processing list, where it can be recovered.
 
-Redis deprecates this command in favor of [`BLMOVE`](/redis/commands/list/blmove), which does the same thing and additionally lets you choose which end of each list to use.
+[`BLMOVE`](/redis/commands/list/blmove) does the same thing and additionally lets you choose which end of each list to use.
 
 ## Syntax
 
diff --git a/redis/commands/list/rpoplpush.mdx b/redis/commands/list/rpoplpush.mdx
index 652c941df..7579d77fa 100644
--- a/redis/commands/list/rpoplpush.mdx
+++ b/redis/commands/list/rpoplpush.mdx
@@ -3,11 +3,15 @@ title: "RPOPLPUSH"
 description: "Pop from tail and push to head."
 ---
 
+<Warning>
+  Prefer [`LMOVE`](/redis/commands/list/lmove) with `RIGHT` and `LEFT` in new code: `LMOVE <source> <destination> RIGHT LEFT`. `RPOPLPUSH` is deprecated in Redis but still supported by Upstash.
+</Warning>
+
 Use `RPOPLPUSH` to atomically move an element from the tail of one list to the head of another, returning the element.
 
 If the source is empty nothing happens and the reply is null. Source and destination may be the same key, which rotates the list: the tail element becomes the new head, so repeated calls cycle through a list of items forever, a handy pattern for round-robin scheduling.
 
-The command is deprecated in Redis in favor of [`LMOVE`](/redis/commands/list/lmove), which does the same thing but lets you choose both ends. [`BRPOPLPUSH`](/redis/commands/list/brpoplpush) is the blocking form.
+[`LMOVE`](/redis/commands/list/lmove) does the same thing but lets you choose both ends, and [`BRPOPLPUSH`](/redis/commands/list/brpoplpush) is the blocking form.
 
 ## Syntax
 
diff --git a/redis/commands/sorted-set/zrangebylex.mdx b/redis/commands/sorted-set/zrangebylex.mdx
index d24b42edb..b779ce4ac 100644
--- a/redis/commands/sorted-set/zrangebylex.mdx
+++ b/redis/commands/sorted-set/zrangebylex.mdx
@@ -3,14 +3,16 @@ title: "ZRANGEBYLEX"
 description: "Get members by lex range."
 ---
 
+<Warning>
+  Prefer [`ZRANGE`](/redis/commands/sorted-set/zrange) with `BYLEX` in new code: `ZRANGE <key> <min> <max> BYLEX [LIMIT <offset> <count>]`. `ZRANGEBYLEX` is deprecated in Redis but still supported by Upstash.
+</Warning>
+
 Use `ZRANGEBYLEX` to list the members of a sorted set that fall in a lexicographic range.
 
 Bounds are written `[member` for inclusive and `(member` for exclusive, with `-` and `+` standing for the lowest and highest possible members. `LIMIT <offset> <count>` pages through the result.
 
 The ordering used here is the byte order of member names, which is only meaningful when every member has the same score. Giving all members score `0` turns a sorted set into a sorted string index, which is how prefix lookups and autocomplete are built on top of it.
 
-The command is deprecated in Redis in favor of [`ZRANGE`](/redis/commands/sorted-set/zrange) with `BYLEX`, which accepts the same bounds.
-
 ## Syntax
 
 ```redis
diff --git a/redis/commands/sorted-set/zrangebyscore.mdx b/redis/commands/sorted-set/zrangebyscore.mdx
index 6f0eedcd1..5a88798de 100644
--- a/redis/commands/sorted-set/zrangebyscore.mdx
+++ b/redis/commands/sorted-set/zrangebyscore.mdx
@@ -3,11 +3,15 @@ title: "ZRANGEBYSCORE"
 description: "Get members by score range."
 ---
 
+<Warning>
+  Prefer [`ZRANGE`](/redis/commands/sorted-set/zrange) with `BYSCORE` in new code: `ZRANGE <key> <min> <max> BYSCORE [LIMIT <offset> <count>] [WITHSCORES]`. `ZRANGEBYSCORE` is deprecated in Redis but still supported by Upstash.
+</Warning>
+
 Use `ZRANGEBYSCORE` to list the members of a sorted set whose score falls in a range, from the lowest score up.
 
 Bounds are inclusive by default, become exclusive when prefixed with `(`, and accept `-inf` and `+inf` for open ends. `WITHSCORES` returns each member with its score, and `LIMIT <offset> <count>` pages through the result, which is how you take the first N above a threshold without transferring the rest.
 
-With timestamps as scores this is the natural range query over time. The command is deprecated in Redis in favor of [`ZRANGE`](/redis/commands/sorted-set/zrange) with `BYSCORE`.
+With timestamps as scores this is the natural range query over time.
 
 ## Syntax
 
diff --git a/redis/commands/sorted-set/zrevrange.mdx b/redis/commands/sorted-set/zrevrange.mdx
index 60340d920..41fa046ca 100644
--- a/redis/commands/sorted-set/zrevrange.mdx
+++ b/redis/commands/sorted-set/zrevrange.mdx
@@ -3,12 +3,14 @@ title: "ZREVRANGE"
 description: "Get members in reverse order."
 ---
 
+<Warning>
+  Prefer [`ZRANGE`](/redis/commands/sorted-set/zrange) with `REV` in new code: `ZRANGE <key> <start> <stop> REV [WITHSCORES]`. `ZREVRANGE` is deprecated in Redis but still supported by Upstash.
+</Warning>
+
 Use `ZREVRANGE` to list a range of members of a sorted set ordered from the highest score down.
 
 `<start>` and `<stop>` are zero-based, inclusive positions in that reversed ordering, so `0 9` returns the ten highest scoring members, the usual shape of a leaderboard page. Negative indexes count from the end, and `WITHSCORES` includes each member's score.
 
-The command is deprecated in Redis in favor of [`ZRANGE`](/redis/commands/sorted-set/zrange) with `REV`.
-
 ## Syntax
 
 ```redis
diff --git a/redis/commands/sorted-set/zrevrangebylex.mdx b/redis/commands/sorted-set/zrevrangebylex.mdx
index 0eec65723..2d454655a 100644
--- a/redis/commands/sorted-set/zrevrangebylex.mdx
+++ b/redis/commands/sorted-set/zrevrangebylex.mdx
@@ -3,11 +3,15 @@ title: "ZREVRANGEBYLEX"
 description: "List members in a lexicographic range, in reverse order."
 ---
 
+<Warning>
+  Prefer [`ZRANGE`](/redis/commands/sorted-set/zrange) with `BYLEX` and `REV` in new code: `ZRANGE <key> <max> <min> BYLEX REV [LIMIT <offset> <count>]`. `ZREVRANGEBYLEX` is deprecated in Redis but still supported by Upstash.
+</Warning>
+
 Use `ZREVRANGEBYLEX` to list the members in a lexicographic range, in reverse order.
 
 The bounds are given highest first, `<max>` before `<min>`, written `[member` for inclusive and `(member` for exclusive, with `+` and `-` for the extremes. `LIMIT <offset> <count>` pages through the result.
 
-As with every lexicographic operation, the ordering is only meaningful when all members share the same score. The command is deprecated in Redis in favor of [`ZRANGE`](/redis/commands/sorted-set/zrange) with `BYLEX` and `REV`.
+As with every lexicographic operation, the ordering is only meaningful when all members share the same score.
 
 ## Syntax
 
diff --git a/redis/commands/sorted-set/zrevrangebyscore.mdx b/redis/commands/sorted-set/zrevrangebyscore.mdx
index 670cf47ec..0ac32b789 100644
--- a/redis/commands/sorted-set/zrevrangebyscore.mdx
+++ b/redis/commands/sorted-set/zrevrangebyscore.mdx
@@ -3,12 +3,14 @@ title: "ZREVRANGEBYSCORE"
 description: "List members in a score range, highest score first."
 ---
 
+<Warning>
+  Prefer [`ZRANGE`](/redis/commands/sorted-set/zrange) with `BYSCORE` and `REV` in new code: `ZRANGE <key> <max> <min> BYSCORE REV [LIMIT <offset> <count>] [WITHSCORES]`. `ZREVRANGEBYSCORE` is deprecated in Redis but still supported by Upstash.
+</Warning>
+
 Use `ZREVRANGEBYSCORE` to list the members in a score range, ordered from the highest score down.
 
 The bounds are given highest first, `<max>` before `<min>`. They are inclusive by default, become exclusive when prefixed with `(`, and accept `+inf` and `-inf`. `WITHSCORES` returns the scores and `LIMIT <offset> <count>` pages through the result, which is the usual way to fetch "the top N above a threshold".
 
-The command is deprecated in Redis in favor of [`ZRANGE`](/redis/commands/sorted-set/zrange) with `BYSCORE` and `REV`.
-
 ## Syntax
 
 ```redis
diff --git a/redis/commands/string/getset.mdx b/redis/commands/string/getset.mdx
index 4db970d2d..e69e07d76 100644
--- a/redis/commands/string/getset.mdx
+++ b/redis/commands/string/getset.mdx
@@ -3,11 +3,15 @@ title: "GETSET"
 description: "Set value and return old value."
 ---
 
+<Warning>
+  Prefer [`SET`](/redis/commands/string/set) with the `GET` argument in new code: `SET <key> <value> GET`. `GETSET` is deprecated in Redis but still supported by Upstash.
+</Warning>
+
 Use `GETSET` to set a new value and get the previous one in a single atomic step.
 
 The reply is the old value, or null when the key did not exist. Note that the key's time to live is discarded, so a key with an expiration becomes permanent when written this way.
 
-The classic use is resetting a counter while reading it, where the atomicity guarantees nothing is counted twice. Redis deprecates the command in favor of [`SET`](/redis/commands/string/set) with the `GET` option, which does the same thing and can additionally set or keep an expiration in the same call.
+The classic use is resetting a counter while reading it, where the atomicity guarantees nothing is counted twice. [`SET`](/redis/commands/string/set) with the `GET` option does the same thing and can additionally set or keep an expiration in the same call.
 
 ## Syntax
 
diff --git a/redis/commands/string/psetex.mdx b/redis/commands/string/psetex.mdx
index 7394e816c..609b497a1 100644
--- a/redis/commands/string/psetex.mdx
+++ b/redis/commands/string/psetex.mdx
@@ -3,11 +3,15 @@ title: "PSETEX"
 description: "Set value with ms expiration."
 ---
 
+<Warning>
+  Prefer [`SET`](/redis/commands/string/set) with the `PX` argument in new code: `SET <key> <value> PX <milliseconds>`. `PSETEX` is deprecated in Redis but still supported by Upstash.
+</Warning>
+
 Use `PSETEX` to set a value together with a lifetime in milliseconds.
 
 The value and the expiration are applied in the same atomic step, so the key never exists without its expiration, which is the point of the command: setting the value and then expiring it separately leaves a window where a crash makes the key permanent. A lifetime of zero or less returns an error.
 
-It is the millisecond form of [`SETEX`](/redis/commands/string/setex), and equivalent to [`SET`](/redis/commands/string/set) with the `PX` option, which is the more flexible way to write the same thing.
+It is the millisecond form of [`SETEX`](/redis/commands/string/setex), and [`SET`](/redis/commands/string/set) with the `PX` option is the more flexible way to write the same thing.
 
 ## Syntax
 
diff --git a/redis/commands/string/setex.mdx b/redis/commands/string/setex.mdx
index 367e01406..ba81fae21 100644
--- a/redis/commands/string/setex.mdx
+++ b/redis/commands/string/setex.mdx
@@ -3,11 +3,15 @@ title: "SETEX"
 description: "Set value with expiration."
 ---
 
+<Warning>
+  Prefer [`SET`](/redis/commands/string/set) with the `EX` argument in new code: `SET <key> <value> EX <seconds>`. `SETEX` is deprecated in Redis but still supported by Upstash.
+</Warning>
+
 Use `SETEX` to set a value together with a lifetime in seconds.
 
 The value and the expiration are applied atomically, so the key never exists without an expiration; writing the value and expiring it in two commands leaves a window in which a failure makes the key permanent. A lifetime of zero or less returns an error.
 
-Use [`PSETEX`](/redis/commands/string/psetex) for millisecond precision. Both are equivalent to [`SET`](/redis/commands/string/set) with `EX` or `PX`, which additionally supports conditions and reading the previous value.
+Use [`PSETEX`](/redis/commands/string/psetex) for millisecond precision. [`SET`](/redis/commands/string/set) with `EX` or `PX` does the same thing and additionally supports conditions and reading the previous value.
 
 ## Syntax
 
diff --git a/redis/commands/string/setnx.mdx b/redis/commands/string/setnx.mdx
index 4df699e4c..64d076bf2 100644
--- a/redis/commands/string/setnx.mdx
+++ b/redis/commands/string/setnx.mdx
@@ -3,6 +3,10 @@ title: "SETNX"
 description: "Set value if key doesn't exist."
 ---
 
+<Warning>
+  Prefer [`SET`](/redis/commands/string/set) with the `NX` argument in new code: `SET <key> <value> NX`. `SETNX` is deprecated in Redis but still supported by Upstash.
+</Warning>
+
 Use `SETNX` to set a value only if the key does not already exist.
 
 The reply is `1` when the key was created and `0` when it was already there and nothing was written. The check and the write are atomic, so exactly one of several racing clients succeeds.

From 77090a2142f4f651d592df3a04edc776ab4dca8c Mon Sep 17 00:00:00 2001
From: Mehmet Dogan <mehmet@dogan.io>
Date: Thu, 13 Aug 2026 14:01:51 +0300
Subject: [PATCH 07/12] cleanup

---
 redis/commands/connection/quit.mdx             | 2 +-
 redis/commands/geo/georadius-ro.mdx            | 2 +-
 redis/commands/geo/georadius.mdx               | 2 +-
 redis/commands/geo/georadiusbymember-ro.mdx    | 2 +-
 redis/commands/geo/georadiusbymember.mdx       | 2 +-
 redis/commands/hash/hmset.mdx                  | 2 +-
 redis/commands/list/brpoplpush.mdx             | 2 +-
 redis/commands/list/rpoplpush.mdx              | 2 +-
 redis/commands/sorted-set/zrangebylex.mdx      | 2 +-
 redis/commands/sorted-set/zrangebyscore.mdx    | 2 +-
 redis/commands/sorted-set/zrevrange.mdx        | 2 +-
 redis/commands/sorted-set/zrevrangebylex.mdx   | 2 +-
 redis/commands/sorted-set/zrevrangebyscore.mdx | 2 +-
 redis/commands/string/getset.mdx               | 2 +-
 redis/commands/string/psetex.mdx               | 2 +-
 redis/commands/string/setex.mdx                | 2 +-
 redis/commands/string/setnx.mdx                | 2 +-
 17 files changed, 17 insertions(+), 17 deletions(-)

diff --git a/redis/commands/connection/quit.mdx b/redis/commands/connection/quit.mdx
index ac317fd55..d66fca2f3 100644
--- a/redis/commands/connection/quit.mdx
+++ b/redis/commands/connection/quit.mdx
@@ -4,7 +4,7 @@ description: "Close the connection."
 ---
 
 <Warning>
-  Prefer closing the connection from the client in new code, which avoids leaving `TIME_WAIT` sockets on the server. `QUIT` has no replacement command; it is deprecated in Redis but still supported by Upstash.
+  Prefer closing the connection from the client in new code, which avoids leaving `TIME_WAIT` sockets on the server.
 </Warning>
 
 Use `QUIT` to ask the server to close the connection once all pending replies have been sent.
diff --git a/redis/commands/geo/georadius-ro.mdx b/redis/commands/geo/georadius-ro.mdx
index d76159ba2..242b11c53 100644
--- a/redis/commands/geo/georadius-ro.mdx
+++ b/redis/commands/geo/georadius-ro.mdx
@@ -4,7 +4,7 @@ description: "Find members within a radius of a point."
 ---
 
 <Warning>
-  Prefer [`GEOSEARCH`](/redis/commands/geo/geosearch) with `FROMLONLAT` and `BYRADIUS` in new code: `GEOSEARCH <key> FROMLONLAT <longitude> <latitude> BYRADIUS <radius> (m | km | ft | mi)`. `GEORADIUS_RO` is deprecated in Redis but still supported by Upstash.
+  Prefer [`GEOSEARCH`](/redis/commands/geo/geosearch) with `FROMLONLAT` and `BYRADIUS` in new code: `GEOSEARCH <key> FROMLONLAT <longitude> <latitude> BYRADIUS <radius> (m | km | ft | mi)`. 
 </Warning>
 
 Use `GEORADIUS_RO` to find members within a radius of a point. It is the read-only form of [`GEORADIUS`](/redis/commands/geo/georadius).
diff --git a/redis/commands/geo/georadius.mdx b/redis/commands/geo/georadius.mdx
index 4346df771..3cdacc9e2 100644
--- a/redis/commands/geo/georadius.mdx
+++ b/redis/commands/geo/georadius.mdx
@@ -4,7 +4,7 @@ description: "Find members within a radius of a point."
 ---
 
 <Warning>
-  Prefer [`GEOSEARCH`](/redis/commands/geo/geosearch) with `FROMLONLAT` and `BYRADIUS` in new code: `GEOSEARCH <key> FROMLONLAT <longitude> <latitude> BYRADIUS <radius> (m | km | ft | mi)`. In place of `STORE` and `STOREDIST`, use [`GEOSEARCHSTORE`](/redis/commands/geo/geosearchstore) with the same query. `GEORADIUS` is deprecated in Redis but still supported by Upstash.
+  Prefer [`GEOSEARCH`](/redis/commands/geo/geosearch) with `FROMLONLAT` and `BYRADIUS` in new code: `GEOSEARCH <key> FROMLONLAT <longitude> <latitude> BYRADIUS <radius> (m | km | ft | mi)`. In place of `STORE` and `STOREDIST`, use [`GEOSEARCHSTORE`](/redis/commands/geo/geosearchstore) with the same query.
 </Warning>
 
 Use `GEORADIUS` to find the members of a geospatial index that lie within a given radius of a longitude and latitude point.
diff --git a/redis/commands/geo/georadiusbymember-ro.mdx b/redis/commands/geo/georadiusbymember-ro.mdx
index 317f075b7..12e8e29c2 100644
--- a/redis/commands/geo/georadiusbymember-ro.mdx
+++ b/redis/commands/geo/georadiusbymember-ro.mdx
@@ -4,7 +4,7 @@ description: "Find members within a radius of another member."
 ---
 
 <Warning>
-  Prefer [`GEOSEARCH`](/redis/commands/geo/geosearch) with `FROMMEMBER` and `BYRADIUS` in new code: `GEOSEARCH <key> FROMMEMBER <member> BYRADIUS <radius> (m | km | ft | mi)`. `GEORADIUSBYMEMBER_RO` is deprecated in Redis but still supported by Upstash.
+  Prefer [`GEOSEARCH`](/redis/commands/geo/geosearch) with `FROMMEMBER` and `BYRADIUS` in new code: `GEOSEARCH <key> FROMMEMBER <member> BYRADIUS <radius> (m | km | ft | mi)`.
 </Warning>
 
 Use `GEORADIUSBYMEMBER_RO` to find members within a radius of another member. It is the read-only form of [`GEORADIUSBYMEMBER`](/redis/commands/geo/georadiusbymember).
diff --git a/redis/commands/geo/georadiusbymember.mdx b/redis/commands/geo/georadiusbymember.mdx
index 0e89d10fa..436d78626 100644
--- a/redis/commands/geo/georadiusbymember.mdx
+++ b/redis/commands/geo/georadiusbymember.mdx
@@ -4,7 +4,7 @@ description: "Find members within a radius of another member."
 ---
 
 <Warning>
-  Prefer [`GEOSEARCH`](/redis/commands/geo/geosearch) with `FROMMEMBER` and `BYRADIUS` in new code: `GEOSEARCH <key> FROMMEMBER <member> BYRADIUS <radius> (m | km | ft | mi)`. In place of `STORE` and `STOREDIST`, use [`GEOSEARCHSTORE`](/redis/commands/geo/geosearchstore) with the same query. `GEORADIUSBYMEMBER` is deprecated in Redis but still supported by Upstash.
+  Prefer [`GEOSEARCH`](/redis/commands/geo/geosearch) with `FROMMEMBER` and `BYRADIUS` in new code: `GEOSEARCH <key> FROMMEMBER <member> BYRADIUS <radius> (m | km | ft | mi)`. In place of `STORE` and `STOREDIST`, use [`GEOSEARCHSTORE`](/redis/commands/geo/geosearchstore) with the same query.
 </Warning>
 
 Use `GEORADIUSBYMEMBER` to find the members of a geospatial index that lie within a given radius of another member.
diff --git a/redis/commands/hash/hmset.mdx b/redis/commands/hash/hmset.mdx
index 654e03370..c243e3d1c 100644
--- a/redis/commands/hash/hmset.mdx
+++ b/redis/commands/hash/hmset.mdx
@@ -4,7 +4,7 @@ description: "Set multiple hash fields."
 ---
 
 <Warning>
-  Prefer [`HSET`](/redis/commands/hash/hset) with multiple field-value pairs in new code: `HSET <key> <field> <value> [<field> <value> ...]`. `HMSET` is deprecated in Redis but still supported by Upstash.
+  Prefer [`HSET`](/redis/commands/hash/hset) with multiple field-value pairs in new code: `HSET <key> <field> <value> [<field> <value> ...]`.
 </Warning>
 
 Use `HMSET` to set several field and value pairs of a hash in one call, creating the key if it does not exist.
diff --git a/redis/commands/list/brpoplpush.mdx b/redis/commands/list/brpoplpush.mdx
index 32f58af78..64b029503 100644
--- a/redis/commands/list/brpoplpush.mdx
+++ b/redis/commands/list/brpoplpush.mdx
@@ -4,7 +4,7 @@ description: "Pop from a list's tail and push it to another, blocking until an e
 ---
 
 <Warning>
-  Prefer [`BLMOVE`](/redis/commands/list/blmove) with `RIGHT` and `LEFT` in new code: `BLMOVE <source> <destination> RIGHT LEFT <timeout>`. `BRPOPLPUSH` is deprecated in Redis but still supported by Upstash.
+  Prefer [`BLMOVE`](/redis/commands/list/blmove) with `RIGHT` and `LEFT` in new code: `BLMOVE <source> <destination> RIGHT LEFT <timeout>`. 
 </Warning>
 
 Use `BRPOPLPUSH` to pop an element from the tail of one list and push it to the head of another, blocking until the source has an element or the timeout expires.
diff --git a/redis/commands/list/rpoplpush.mdx b/redis/commands/list/rpoplpush.mdx
index 7579d77fa..0efdaa35a 100644
--- a/redis/commands/list/rpoplpush.mdx
+++ b/redis/commands/list/rpoplpush.mdx
@@ -4,7 +4,7 @@ description: "Pop from tail and push to head."
 ---
 
 <Warning>
-  Prefer [`LMOVE`](/redis/commands/list/lmove) with `RIGHT` and `LEFT` in new code: `LMOVE <source> <destination> RIGHT LEFT`. `RPOPLPUSH` is deprecated in Redis but still supported by Upstash.
+  Prefer [`LMOVE`](/redis/commands/list/lmove) with `RIGHT` and `LEFT` in new code: `LMOVE <source> <destination> RIGHT LEFT`. 
 </Warning>
 
 Use `RPOPLPUSH` to atomically move an element from the tail of one list to the head of another, returning the element.
diff --git a/redis/commands/sorted-set/zrangebylex.mdx b/redis/commands/sorted-set/zrangebylex.mdx
index b779ce4ac..6542f3ed3 100644
--- a/redis/commands/sorted-set/zrangebylex.mdx
+++ b/redis/commands/sorted-set/zrangebylex.mdx
@@ -4,7 +4,7 @@ description: "Get members by lex range."
 ---
 
 <Warning>
-  Prefer [`ZRANGE`](/redis/commands/sorted-set/zrange) with `BYLEX` in new code: `ZRANGE <key> <min> <max> BYLEX [LIMIT <offset> <count>]`. `ZRANGEBYLEX` is deprecated in Redis but still supported by Upstash.
+  Prefer [`ZRANGE`](/redis/commands/sorted-set/zrange) with `BYLEX` in new code: `ZRANGE <key> <min> <max> BYLEX [LIMIT <offset> <count>]`. 
 </Warning>
 
 Use `ZRANGEBYLEX` to list the members of a sorted set that fall in a lexicographic range.
diff --git a/redis/commands/sorted-set/zrangebyscore.mdx b/redis/commands/sorted-set/zrangebyscore.mdx
index 5a88798de..9ad74832f 100644
--- a/redis/commands/sorted-set/zrangebyscore.mdx
+++ b/redis/commands/sorted-set/zrangebyscore.mdx
@@ -4,7 +4,7 @@ description: "Get members by score range."
 ---
 
 <Warning>
-  Prefer [`ZRANGE`](/redis/commands/sorted-set/zrange) with `BYSCORE` in new code: `ZRANGE <key> <min> <max> BYSCORE [LIMIT <offset> <count>] [WITHSCORES]`. `ZRANGEBYSCORE` is deprecated in Redis but still supported by Upstash.
+  Prefer [`ZRANGE`](/redis/commands/sorted-set/zrange) with `BYSCORE` in new code: `ZRANGE <key> <min> <max> BYSCORE [LIMIT <offset> <count>] [WITHSCORES]`. 
 </Warning>
 
 Use `ZRANGEBYSCORE` to list the members of a sorted set whose score falls in a range, from the lowest score up.
diff --git a/redis/commands/sorted-set/zrevrange.mdx b/redis/commands/sorted-set/zrevrange.mdx
index 41fa046ca..9dab6557d 100644
--- a/redis/commands/sorted-set/zrevrange.mdx
+++ b/redis/commands/sorted-set/zrevrange.mdx
@@ -4,7 +4,7 @@ description: "Get members in reverse order."
 ---
 
 <Warning>
-  Prefer [`ZRANGE`](/redis/commands/sorted-set/zrange) with `REV` in new code: `ZRANGE <key> <start> <stop> REV [WITHSCORES]`. `ZREVRANGE` is deprecated in Redis but still supported by Upstash.
+  Prefer [`ZRANGE`](/redis/commands/sorted-set/zrange) with `REV` in new code: `ZRANGE <key> <start> <stop> REV [WITHSCORES]`.
 </Warning>
 
 Use `ZREVRANGE` to list a range of members of a sorted set ordered from the highest score down.
diff --git a/redis/commands/sorted-set/zrevrangebylex.mdx b/redis/commands/sorted-set/zrevrangebylex.mdx
index 2d454655a..e4d378c2e 100644
--- a/redis/commands/sorted-set/zrevrangebylex.mdx
+++ b/redis/commands/sorted-set/zrevrangebylex.mdx
@@ -4,7 +4,7 @@ description: "List members in a lexicographic range, in reverse order."
 ---
 
 <Warning>
-  Prefer [`ZRANGE`](/redis/commands/sorted-set/zrange) with `BYLEX` and `REV` in new code: `ZRANGE <key> <max> <min> BYLEX REV [LIMIT <offset> <count>]`. `ZREVRANGEBYLEX` is deprecated in Redis but still supported by Upstash.
+  Prefer [`ZRANGE`](/redis/commands/sorted-set/zrange) with `BYLEX` and `REV` in new code: `ZRANGE <key> <max> <min> BYLEX REV [LIMIT <offset> <count>]`. 
 </Warning>
 
 Use `ZREVRANGEBYLEX` to list the members in a lexicographic range, in reverse order.
diff --git a/redis/commands/sorted-set/zrevrangebyscore.mdx b/redis/commands/sorted-set/zrevrangebyscore.mdx
index 0ac32b789..e00e0583b 100644
--- a/redis/commands/sorted-set/zrevrangebyscore.mdx
+++ b/redis/commands/sorted-set/zrevrangebyscore.mdx
@@ -4,7 +4,7 @@ description: "List members in a score range, highest score first."
 ---
 
 <Warning>
-  Prefer [`ZRANGE`](/redis/commands/sorted-set/zrange) with `BYSCORE` and `REV` in new code: `ZRANGE <key> <max> <min> BYSCORE REV [LIMIT <offset> <count>] [WITHSCORES]`. `ZREVRANGEBYSCORE` is deprecated in Redis but still supported by Upstash.
+  Prefer [`ZRANGE`](/redis/commands/sorted-set/zrange) with `BYSCORE` and `REV` in new code: `ZRANGE <key> <max> <min> BYSCORE REV [LIMIT <offset> <count>] [WITHSCORES]`. 
 </Warning>
 
 Use `ZREVRANGEBYSCORE` to list the members in a score range, ordered from the highest score down.
diff --git a/redis/commands/string/getset.mdx b/redis/commands/string/getset.mdx
index e69e07d76..d28c0b720 100644
--- a/redis/commands/string/getset.mdx
+++ b/redis/commands/string/getset.mdx
@@ -4,7 +4,7 @@ description: "Set value and return old value."
 ---
 
 <Warning>
-  Prefer [`SET`](/redis/commands/string/set) with the `GET` argument in new code: `SET <key> <value> GET`. `GETSET` is deprecated in Redis but still supported by Upstash.
+  Prefer [`SET`](/redis/commands/string/set) with the `GET` argument in new code: `SET <key> <value> GET`. 
 </Warning>
 
 Use `GETSET` to set a new value and get the previous one in a single atomic step.
diff --git a/redis/commands/string/psetex.mdx b/redis/commands/string/psetex.mdx
index 609b497a1..898aa696d 100644
--- a/redis/commands/string/psetex.mdx
+++ b/redis/commands/string/psetex.mdx
@@ -4,7 +4,7 @@ description: "Set value with ms expiration."
 ---
 
 <Warning>
-  Prefer [`SET`](/redis/commands/string/set) with the `PX` argument in new code: `SET <key> <value> PX <milliseconds>`. `PSETEX` is deprecated in Redis but still supported by Upstash.
+  Prefer [`SET`](/redis/commands/string/set) with the `PX` argument in new code: `SET <key> <value> PX <milliseconds>`. 
 </Warning>
 
 Use `PSETEX` to set a value together with a lifetime in milliseconds.
diff --git a/redis/commands/string/setex.mdx b/redis/commands/string/setex.mdx
index ba81fae21..bfb2bcc15 100644
--- a/redis/commands/string/setex.mdx
+++ b/redis/commands/string/setex.mdx
@@ -4,7 +4,7 @@ description: "Set value with expiration."
 ---
 
 <Warning>
-  Prefer [`SET`](/redis/commands/string/set) with the `EX` argument in new code: `SET <key> <value> EX <seconds>`. `SETEX` is deprecated in Redis but still supported by Upstash.
+  Prefer [`SET`](/redis/commands/string/set) with the `EX` argument in new code: `SET <key> <value> EX <seconds>`. 
 </Warning>
 
 Use `SETEX` to set a value together with a lifetime in seconds.
diff --git a/redis/commands/string/setnx.mdx b/redis/commands/string/setnx.mdx
index 64d076bf2..10ea6f02e 100644
--- a/redis/commands/string/setnx.mdx
+++ b/redis/commands/string/setnx.mdx
@@ -4,7 +4,7 @@ description: "Set value if key doesn't exist."
 ---
 
 <Warning>
-  Prefer [`SET`](/redis/commands/string/set) with the `NX` argument in new code: `SET <key> <value> NX`. `SETNX` is deprecated in Redis but still supported by Upstash.
+  Prefer [`SET`](/redis/commands/string/set) with the `NX` argument in new code: `SET <key> <value> NX`.
 </Warning>
 
 Use `SETNX` to set a value only if the key does not already exist.

From d25e5d38eb2fc37a410087db882ca8a11fc83607 Mon Sep 17 00:00:00 2001
From: Mehmet Dogan <mehmet@dogan.io>
Date: Thu, 13 Aug 2026 14:32:47 +0300
Subject: [PATCH 08/12] improve redis-rs examples

---
 redis/commands/connection/client-getname.mdx |  6 +++---
 redis/commands/connection/client-id.mdx      |  6 +++---
 redis/commands/connection/client-setname.mdx |  7 +++----
 redis/commands/connection/ping.mdx           |  6 +++---
 redis/commands/generic/scan.mdx              | 10 ++++++----
 redis/commands/geo/geoadd.mdx                |  9 +++------
 redis/commands/geo/geodist.mdx               |  9 ++++-----
 redis/commands/geo/geohash.mdx               |  6 +++---
 redis/commands/geo/geopos.mdx                |  6 +++---
 redis/commands/geo/georadius.mdx             | 18 +++++++++++-------
 redis/commands/geo/georadiusbymember.mdx     | 16 ++++++++++------
 redis/commands/hash/hscan.mdx                | 11 ++++++-----
 redis/commands/hash/hsetex.mdx               | 14 +++++++-------
 redis/commands/list/blmove.mdx               | 16 +++++++++-------
 redis/commands/list/blmpop.mdx               |  9 +++------
 redis/commands/list/blpop.mdx                |  7 +++----
 redis/commands/list/brpop.mdx                |  7 +++----
 redis/commands/list/brpoplpush.mdx           |  8 +++-----
 redis/commands/list/lmpop.mdx                |  8 +++-----
 redis/commands/list/lpos.mdx                 |  7 +++----
 redis/commands/scripting/script-load.mdx     |  8 ++++----
 redis/commands/server/flushall.mdx           |  6 +++---
 redis/commands/server/flushdb.mdx            |  6 +++---
 redis/commands/set/sscan.mdx                 | 11 ++++++-----
 redis/commands/sorted-set/bzmpop.mdx         |  9 +++------
 redis/commands/sorted-set/bzpopmax.mdx       |  7 +++----
 redis/commands/sorted-set/bzpopmin.mdx       |  7 +++----
 redis/commands/sorted-set/zmpop.mdx          |  8 +++-----
 redis/commands/sorted-set/zscan.mdx          | 11 ++++++-----
 redis/commands/streams/xautoclaim.mdx        | 18 +++++++++++-------
 30 files changed, 137 insertions(+), 140 deletions(-)

diff --git a/redis/commands/connection/client-getname.mdx b/redis/commands/connection/client-getname.mdx
index bf8ed590b..145935e88 100644
--- a/redis/commands/connection/client-getname.mdx
+++ b/redis/commands/connection/client-getname.mdx
@@ -127,14 +127,14 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 <Tab title="redis-rs">
 
 ```rust
+use redis::TypedCommands;
+
 fn main() -> redis::RedisResult<()> {
     let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
     let client = redis::Client::open(url)?;
     let mut connection = client.get_connection()?;
 
-    let mut command = redis::cmd("CLIENT");
-    command.arg("GETNAME");
-    let result: redis::Value = command.query(&mut connection)?;
+    let result = connection.client_getname()?;
     println!("{result:?}");
     Ok(())
 }
diff --git a/redis/commands/connection/client-id.mdx b/redis/commands/connection/client-id.mdx
index ffa89adcc..179c0bcb1 100644
--- a/redis/commands/connection/client-id.mdx
+++ b/redis/commands/connection/client-id.mdx
@@ -127,14 +127,14 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 <Tab title="redis-rs">
 
 ```rust
+use redis::TypedCommands;
+
 fn main() -> redis::RedisResult<()> {
     let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
     let client = redis::Client::open(url)?;
     let mut connection = client.get_connection()?;
 
-    let mut command = redis::cmd("CLIENT");
-    command.arg("ID");
-    let result: redis::Value = command.query(&mut connection)?;
+    let result = connection.client_id()?;
     println!("{result:?}");
     Ok(())
 }
diff --git a/redis/commands/connection/client-setname.mdx b/redis/commands/connection/client-setname.mdx
index a2af4780c..f05629b3f 100644
--- a/redis/commands/connection/client-setname.mdx
+++ b/redis/commands/connection/client-setname.mdx
@@ -129,15 +129,14 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 <Tab title="redis-rs">
 
 ```rust
+use redis::TypedCommands;
+
 fn main() -> redis::RedisResult<()> {
     let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
     let client = redis::Client::open(url)?;
     let mut connection = client.get_connection()?;
 
-    let mut command = redis::cmd("CLIENT");
-    command.arg("SETNAME");
-    command.arg("worker-1");
-    let result: redis::Value = command.query(&mut connection)?;
+    let result = connection.client_setname("worker-1")?;
     println!("{result:?}");
     Ok(())
 }
diff --git a/redis/commands/connection/ping.mdx b/redis/commands/connection/ping.mdx
index 9fe78e2b5..48fcb33d5 100644
--- a/redis/commands/connection/ping.mdx
+++ b/redis/commands/connection/ping.mdx
@@ -154,14 +154,14 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 <Tab title="redis-rs">
 
 ```rust
+use redis::TypedCommands;
+
 fn main() -> redis::RedisResult<()> {
     let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
     let client = redis::Client::open(url)?;
     let mut connection = client.get_connection()?;
 
-    let mut command = redis::cmd("PING");
-
-    let result: redis::Value = command.query(&mut connection)?;
+    let result = connection.ping()?;
     println!("{result:?}");
     Ok(())
 }
diff --git a/redis/commands/generic/scan.mdx b/redis/commands/generic/scan.mdx
index b95977312..96f0825e3 100644
--- a/redis/commands/generic/scan.mdx
+++ b/redis/commands/generic/scan.mdx
@@ -160,15 +160,17 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 <Tab title="redis-rs">
 
 ```rust
+use redis::TypedCommands;
+
 fn main() -> redis::RedisResult<()> {
     let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
     let client = redis::Client::open(url)?;
     let mut connection = client.get_connection()?;
 
-    let mut command = redis::cmd("SCAN");
-    command.arg("0");
-    let result: redis::Value = command.query(&mut connection)?;
-    println!("{result:?}");
+    let iter: redis::Iter<String> = connection.scan()?;
+    for key in iter {
+        println!("{key}");
+    }
     Ok(())
 }
 ```
diff --git a/redis/commands/geo/geoadd.mdx b/redis/commands/geo/geoadd.mdx
index 2b27052e7..718b23869 100644
--- a/redis/commands/geo/geoadd.mdx
+++ b/redis/commands/geo/geoadd.mdx
@@ -165,17 +165,14 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 <Tab title="redis-rs">
 
 ```rust
+use redis::TypedCommands;
+
 fn main() -> redis::RedisResult<()> {
     let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
     let client = redis::Client::open(url)?;
     let mut connection = client.get_connection()?;
 
-    let mut command = redis::cmd("GEOADD");
-    command.arg("my-key");
-    command.arg("29.0");
-    command.arg("41.0");
-    command.arg("member");
-    let result: redis::Value = command.query(&mut connection)?;
+    let result = connection.geo_add("my-key", (29.0, 41.0, "member"))?;
     println!("{result:?}");
     Ok(())
 }
diff --git a/redis/commands/geo/geodist.mdx b/redis/commands/geo/geodist.mdx
index ced8f9149..cfeef4614 100644
--- a/redis/commands/geo/geodist.mdx
+++ b/redis/commands/geo/geodist.mdx
@@ -155,16 +155,15 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 <Tab title="redis-rs">
 
 ```rust
+use redis::geo::Unit;
+use redis::TypedCommands;
+
 fn main() -> redis::RedisResult<()> {
     let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
     let client = redis::Client::open(url)?;
     let mut connection = client.get_connection()?;
 
-    let mut command = redis::cmd("GEODIST");
-    command.arg("my-key");
-    command.arg("member1");
-    command.arg("member2");
-    let result: redis::Value = command.query(&mut connection)?;
+    let result = connection.geo_dist("my-key", "member1", "member2", Unit::Meters)?;
     println!("{result:?}");
     Ok(())
 }
diff --git a/redis/commands/geo/geohash.mdx b/redis/commands/geo/geohash.mdx
index 0d1d84539..7a9acf96f 100644
--- a/redis/commands/geo/geohash.mdx
+++ b/redis/commands/geo/geohash.mdx
@@ -149,14 +149,14 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 <Tab title="redis-rs">
 
 ```rust
+use redis::TypedCommands;
+
 fn main() -> redis::RedisResult<()> {
     let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
     let client = redis::Client::open(url)?;
     let mut connection = client.get_connection()?;
 
-    let mut command = redis::cmd("GEOHASH");
-    command.arg("my-key");
-    let result: redis::Value = command.query(&mut connection)?;
+    let result = connection.geo_hash("my-key", "member")?;
     println!("{result:?}");
     Ok(())
 }
diff --git a/redis/commands/geo/geopos.mdx b/redis/commands/geo/geopos.mdx
index fcde1aaa4..b7d4fabaf 100644
--- a/redis/commands/geo/geopos.mdx
+++ b/redis/commands/geo/geopos.mdx
@@ -149,14 +149,14 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 <Tab title="redis-rs">
 
 ```rust
+use redis::TypedCommands;
+
 fn main() -> redis::RedisResult<()> {
     let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
     let client = redis::Client::open(url)?;
     let mut connection = client.get_connection()?;
 
-    let mut command = redis::cmd("GEOPOS");
-    command.arg("my-key");
-    let result: redis::Value = command.query(&mut connection)?;
+    let result = connection.geo_pos("my-key", "member")?;
     println!("{result:?}");
     Ok(())
 }
diff --git a/redis/commands/geo/georadius.mdx b/redis/commands/geo/georadius.mdx
index 3cdacc9e2..4e9d3eb04 100644
--- a/redis/commands/geo/georadius.mdx
+++ b/redis/commands/geo/georadius.mdx
@@ -168,18 +168,22 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 <Tab title="redis-rs">
 
 ```rust
+use redis::geo::{RadiusOptions, Unit};
+use redis::TypedCommands;
+
 fn main() -> redis::RedisResult<()> {
     let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
     let client = redis::Client::open(url)?;
     let mut connection = client.get_connection()?;
 
-    let mut command = redis::cmd("GEORADIUS");
-    command.arg("my-key");
-    command.arg("29.0");
-    command.arg("41.0");
-    command.arg("1.5");
-    command.arg("m");
-    let result: redis::Value = command.query(&mut connection)?;
+    let result = connection.geo_radius(
+        "my-key",
+        29.0,
+        41.0,
+        1.5,
+        Unit::Meters,
+        RadiusOptions::default(),
+    )?;
     println!("{result:?}");
     Ok(())
 }
diff --git a/redis/commands/geo/georadiusbymember.mdx b/redis/commands/geo/georadiusbymember.mdx
index 436d78626..78ce11470 100644
--- a/redis/commands/geo/georadiusbymember.mdx
+++ b/redis/commands/geo/georadiusbymember.mdx
@@ -165,17 +165,21 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 <Tab title="redis-rs">
 
 ```rust
+use redis::geo::{RadiusOptions, Unit};
+use redis::TypedCommands;
+
 fn main() -> redis::RedisResult<()> {
     let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
     let client = redis::Client::open(url)?;
     let mut connection = client.get_connection()?;
 
-    let mut command = redis::cmd("GEORADIUSBYMEMBER");
-    command.arg("my-key");
-    command.arg("member");
-    command.arg("1.5");
-    command.arg("m");
-    let result: redis::Value = command.query(&mut connection)?;
+    let result = connection.geo_radius_by_member(
+        "my-key",
+        "member",
+        1.5,
+        Unit::Meters,
+        RadiusOptions::default(),
+    )?;
     println!("{result:?}");
     Ok(())
 }
diff --git a/redis/commands/hash/hscan.mdx b/redis/commands/hash/hscan.mdx
index 2bbe04bb7..f9e7db835 100644
--- a/redis/commands/hash/hscan.mdx
+++ b/redis/commands/hash/hscan.mdx
@@ -166,16 +166,17 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 <Tab title="redis-rs">
 
 ```rust
+use redis::TypedCommands;
+
 fn main() -> redis::RedisResult<()> {
     let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
     let client = redis::Client::open(url)?;
     let mut connection = client.get_connection()?;
 
-    let mut command = redis::cmd("HSCAN");
-    command.arg("my-key");
-    command.arg("0");
-    let result: redis::Value = command.query(&mut connection)?;
-    println!("{result:?}");
+    let iter: redis::Iter<(String, String)> = connection.hscan("my-key")?;
+    for (field, value) in iter {
+        println!("{field}: {value}");
+    }
     Ok(())
 }
 ```
diff --git a/redis/commands/hash/hsetex.mdx b/redis/commands/hash/hsetex.mdx
index 6f351bf18..22e22b99d 100644
--- a/redis/commands/hash/hsetex.mdx
+++ b/redis/commands/hash/hsetex.mdx
@@ -161,18 +161,18 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 <Tab title="redis-rs">
 
 ```rust
+use redis::{HashFieldExpirationOptions, TypedCommands};
+
 fn main() -> redis::RedisResult<()> {
     let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
     let client = redis::Client::open(url)?;
     let mut connection = client.get_connection()?;
 
-    let mut command = redis::cmd("HSETEX");
-    command.arg("my-key");
-    command.arg("FIELDS");
-    command.arg("1");
-    command.arg("field");
-    command.arg("value");
-    let result: redis::Value = command.query(&mut connection)?;
+    let result = connection.hset_ex(
+        "my-key",
+        &HashFieldExpirationOptions::default(),
+        &[("field", "value")],
+    )?;
     println!("{result:?}");
     Ok(())
 }
diff --git a/redis/commands/list/blmove.mdx b/redis/commands/list/blmove.mdx
index 8621053c3..b37038086 100644
--- a/redis/commands/list/blmove.mdx
+++ b/redis/commands/list/blmove.mdx
@@ -151,18 +151,20 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 <Tab title="redis-rs">
 
 ```rust
+use redis::{Direction, TypedCommands};
+
 fn main() -> redis::RedisResult<()> {
     let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
     let client = redis::Client::open(url)?;
     let mut connection = client.get_connection()?;
 
-    let mut command = redis::cmd("BLMOVE");
-    command.arg("source-key");
-    command.arg("destination-key");
-    command.arg("LEFT");
-    command.arg("LEFT");
-    command.arg("1.5");
-    let result: redis::Value = command.query(&mut connection)?;
+    let result = connection.blmove(
+        "source-key",
+        "destination-key",
+        Direction::Left,
+        Direction::Left,
+        1.5,
+    )?;
     println!("{result:?}");
     Ok(())
 }
diff --git a/redis/commands/list/blmpop.mdx b/redis/commands/list/blmpop.mdx
index 6116bcba8..ad9eadeed 100644
--- a/redis/commands/list/blmpop.mdx
+++ b/redis/commands/list/blmpop.mdx
@@ -151,17 +151,14 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 <Tab title="redis-rs">
 
 ```rust
+use redis::{Direction, TypedCommands};
+
 fn main() -> redis::RedisResult<()> {
     let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
     let client = redis::Client::open(url)?;
     let mut connection = client.get_connection()?;
 
-    let mut command = redis::cmd("BLMPOP");
-    command.arg("1.5");
-    command.arg("1");
-    command.arg("my-key");
-    command.arg("LEFT");
-    let result: redis::Value = command.query(&mut connection)?;
+    let result = connection.blmpop(1.5, 1, "my-key", Direction::Left, 1)?;
     println!("{result:?}");
     Ok(())
 }
diff --git a/redis/commands/list/blpop.mdx b/redis/commands/list/blpop.mdx
index 1dade6609..c0a1ffb70 100644
--- a/redis/commands/list/blpop.mdx
+++ b/redis/commands/list/blpop.mdx
@@ -148,15 +148,14 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 <Tab title="redis-rs">
 
 ```rust
+use redis::TypedCommands;
+
 fn main() -> redis::RedisResult<()> {
     let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
     let client = redis::Client::open(url)?;
     let mut connection = client.get_connection()?;
 
-    let mut command = redis::cmd("BLPOP");
-    command.arg("my-key");
-    command.arg("1.5");
-    let result: redis::Value = command.query(&mut connection)?;
+    let result = connection.blpop("my-key", 1.5)?;
     println!("{result:?}");
     Ok(())
 }
diff --git a/redis/commands/list/brpop.mdx b/redis/commands/list/brpop.mdx
index 33bead8ad..54570be0e 100644
--- a/redis/commands/list/brpop.mdx
+++ b/redis/commands/list/brpop.mdx
@@ -148,15 +148,14 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 <Tab title="redis-rs">
 
 ```rust
+use redis::TypedCommands;
+
 fn main() -> redis::RedisResult<()> {
     let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
     let client = redis::Client::open(url)?;
     let mut connection = client.get_connection()?;
 
-    let mut command = redis::cmd("BRPOP");
-    command.arg("my-key");
-    command.arg("1.5");
-    let result: redis::Value = command.query(&mut connection)?;
+    let result = connection.brpop("my-key", 1.5)?;
     println!("{result:?}");
     Ok(())
 }
diff --git a/redis/commands/list/brpoplpush.mdx b/redis/commands/list/brpoplpush.mdx
index 64b029503..d1e210dee 100644
--- a/redis/commands/list/brpoplpush.mdx
+++ b/redis/commands/list/brpoplpush.mdx
@@ -153,16 +153,14 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 <Tab title="redis-rs">
 
 ```rust
+use redis::TypedCommands;
+
 fn main() -> redis::RedisResult<()> {
     let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
     let client = redis::Client::open(url)?;
     let mut connection = client.get_connection()?;
 
-    let mut command = redis::cmd("BRPOPLPUSH");
-    command.arg("source-key");
-    command.arg("destination-key");
-    command.arg("1.5");
-    let result: redis::Value = command.query(&mut connection)?;
+    let result = connection.brpoplpush("source-key", "destination-key", 1.5)?;
     println!("{result:?}");
     Ok(())
 }
diff --git a/redis/commands/list/lmpop.mdx b/redis/commands/list/lmpop.mdx
index d4f2a6f3a..b01ad131a 100644
--- a/redis/commands/list/lmpop.mdx
+++ b/redis/commands/list/lmpop.mdx
@@ -149,16 +149,14 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 <Tab title="redis-rs">
 
 ```rust
+use redis::{Direction, TypedCommands};
+
 fn main() -> redis::RedisResult<()> {
     let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
     let client = redis::Client::open(url)?;
     let mut connection = client.get_connection()?;
 
-    let mut command = redis::cmd("LMPOP");
-    command.arg("1");
-    command.arg("my-key");
-    command.arg("LEFT");
-    let result: redis::Value = command.query(&mut connection)?;
+    let result = connection.lmpop(1, "my-key", Direction::Left, 1)?;
     println!("{result:?}");
     Ok(())
 }
diff --git a/redis/commands/list/lpos.mdx b/redis/commands/list/lpos.mdx
index 573ad9a19..19d923f5d 100644
--- a/redis/commands/list/lpos.mdx
+++ b/redis/commands/list/lpos.mdx
@@ -156,15 +156,14 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 <Tab title="redis-rs">
 
 ```rust
+use redis::{LposOptions, TypedCommands};
+
 fn main() -> redis::RedisResult<()> {
     let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
     let client = redis::Client::open(url)?;
     let mut connection = client.get_connection()?;
 
-    let mut command = redis::cmd("LPOS");
-    command.arg("my-key");
-    command.arg("element");
-    let result: redis::Value = command.query(&mut connection)?;
+    let result: Option<isize> = connection.lpos("my-key", "element", LposOptions::default())?;
     println!("{result:?}");
     Ok(())
 }
diff --git a/redis/commands/scripting/script-load.mdx b/redis/commands/scripting/script-load.mdx
index d141e9352..b5695cd18 100644
--- a/redis/commands/scripting/script-load.mdx
+++ b/redis/commands/scripting/script-load.mdx
@@ -158,15 +158,15 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 <Tab title="redis-rs">
 
 ```rust
+use redis::{Script, TypedCommands};
+
 fn main() -> redis::RedisResult<()> {
     let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
     let client = redis::Client::open(url)?;
     let mut connection = client.get_connection()?;
 
-    let mut command = redis::cmd("SCRIPT");
-    command.arg("LOAD");
-    command.arg("return ARGV[1]");
-    let result: redis::Value = command.query(&mut connection)?;
+    let script = Script::new("return ARGV[1]");
+    let result: String = connection.load_script(&script)?;
     println!("{result:?}");
     Ok(())
 }
diff --git a/redis/commands/server/flushall.mdx b/redis/commands/server/flushall.mdx
index 9e555371d..3d518e806 100644
--- a/redis/commands/server/flushall.mdx
+++ b/redis/commands/server/flushall.mdx
@@ -156,14 +156,14 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 <Tab title="redis-rs">
 
 ```rust
+use redis::TypedCommands;
+
 fn main() -> redis::RedisResult<()> {
     let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
     let client = redis::Client::open(url)?;
     let mut connection = client.get_connection()?;
 
-    let mut command = redis::cmd("FLUSHALL");
-
-    let result: redis::Value = command.query(&mut connection)?;
+    let result = connection.flushall()?;
     println!("{result:?}");
     Ok(())
 }
diff --git a/redis/commands/server/flushdb.mdx b/redis/commands/server/flushdb.mdx
index b682701f2..cf4b5e999 100644
--- a/redis/commands/server/flushdb.mdx
+++ b/redis/commands/server/flushdb.mdx
@@ -156,14 +156,14 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 <Tab title="redis-rs">
 
 ```rust
+use redis::TypedCommands;
+
 fn main() -> redis::RedisResult<()> {
     let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
     let client = redis::Client::open(url)?;
     let mut connection = client.get_connection()?;
 
-    let mut command = redis::cmd("FLUSHDB");
-
-    let result: redis::Value = command.query(&mut connection)?;
+    let result = connection.flushdb()?;
     println!("{result:?}");
     Ok(())
 }
diff --git a/redis/commands/set/sscan.mdx b/redis/commands/set/sscan.mdx
index 09f1f6b03..cbd504384 100644
--- a/redis/commands/set/sscan.mdx
+++ b/redis/commands/set/sscan.mdx
@@ -161,16 +161,17 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 <Tab title="redis-rs">
 
 ```rust
+use redis::TypedCommands;
+
 fn main() -> redis::RedisResult<()> {
     let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
     let client = redis::Client::open(url)?;
     let mut connection = client.get_connection()?;
 
-    let mut command = redis::cmd("SSCAN");
-    command.arg("my-key");
-    command.arg("0");
-    let result: redis::Value = command.query(&mut connection)?;
-    println!("{result:?}");
+    let iter: redis::Iter<String> = connection.sscan("my-key")?;
+    for member in iter {
+        println!("{member}");
+    }
     Ok(())
 }
 ```
diff --git a/redis/commands/sorted-set/bzmpop.mdx b/redis/commands/sorted-set/bzmpop.mdx
index 5083edf9a..21a73f5b0 100644
--- a/redis/commands/sorted-set/bzmpop.mdx
+++ b/redis/commands/sorted-set/bzmpop.mdx
@@ -151,17 +151,14 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 <Tab title="redis-rs">
 
 ```rust
+use redis::TypedCommands;
+
 fn main() -> redis::RedisResult<()> {
     let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
     let client = redis::Client::open(url)?;
     let mut connection = client.get_connection()?;
 
-    let mut command = redis::cmd("BZMPOP");
-    command.arg("1.5");
-    command.arg("1");
-    command.arg("my-key");
-    command.arg("MIN");
-    let result: redis::Value = command.query(&mut connection)?;
+    let result = connection.bzmpop_min(1.5, "my-key", 1)?;
     println!("{result:?}");
     Ok(())
 }
diff --git a/redis/commands/sorted-set/bzpopmax.mdx b/redis/commands/sorted-set/bzpopmax.mdx
index 666b36b87..ee916accb 100644
--- a/redis/commands/sorted-set/bzpopmax.mdx
+++ b/redis/commands/sorted-set/bzpopmax.mdx
@@ -148,15 +148,14 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 <Tab title="redis-rs">
 
 ```rust
+use redis::TypedCommands;
+
 fn main() -> redis::RedisResult<()> {
     let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
     let client = redis::Client::open(url)?;
     let mut connection = client.get_connection()?;
 
-    let mut command = redis::cmd("BZPOPMAX");
-    command.arg("my-key");
-    command.arg("1.5");
-    let result: redis::Value = command.query(&mut connection)?;
+    let result = connection.bzpopmax("my-key", 1.5)?;
     println!("{result:?}");
     Ok(())
 }
diff --git a/redis/commands/sorted-set/bzpopmin.mdx b/redis/commands/sorted-set/bzpopmin.mdx
index 9e4d44f4f..023b8c554 100644
--- a/redis/commands/sorted-set/bzpopmin.mdx
+++ b/redis/commands/sorted-set/bzpopmin.mdx
@@ -148,15 +148,14 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 <Tab title="redis-rs">
 
 ```rust
+use redis::TypedCommands;
+
 fn main() -> redis::RedisResult<()> {
     let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
     let client = redis::Client::open(url)?;
     let mut connection = client.get_connection()?;
 
-    let mut command = redis::cmd("BZPOPMIN");
-    command.arg("my-key");
-    command.arg("1.5");
-    let result: redis::Value = command.query(&mut connection)?;
+    let result = connection.bzpopmin("my-key", 1.5)?;
     println!("{result:?}");
     Ok(())
 }
diff --git a/redis/commands/sorted-set/zmpop.mdx b/redis/commands/sorted-set/zmpop.mdx
index c71c6f588..3d9d16b1e 100644
--- a/redis/commands/sorted-set/zmpop.mdx
+++ b/redis/commands/sorted-set/zmpop.mdx
@@ -149,16 +149,14 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 <Tab title="redis-rs">
 
 ```rust
+use redis::TypedCommands;
+
 fn main() -> redis::RedisResult<()> {
     let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
     let client = redis::Client::open(url)?;
     let mut connection = client.get_connection()?;
 
-    let mut command = redis::cmd("ZMPOP");
-    command.arg("1");
-    command.arg("my-key");
-    command.arg("MIN");
-    let result: redis::Value = command.query(&mut connection)?;
+    let result = connection.zmpop_min("my-key", 1)?;
     println!("{result:?}");
     Ok(())
 }
diff --git a/redis/commands/sorted-set/zscan.mdx b/redis/commands/sorted-set/zscan.mdx
index 899bd33db..f6317d42e 100644
--- a/redis/commands/sorted-set/zscan.mdx
+++ b/redis/commands/sorted-set/zscan.mdx
@@ -168,16 +168,17 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 <Tab title="redis-rs">
 
 ```rust
+use redis::TypedCommands;
+
 fn main() -> redis::RedisResult<()> {
     let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
     let client = redis::Client::open(url)?;
     let mut connection = client.get_connection()?;
 
-    let mut command = redis::cmd("ZSCAN");
-    command.arg("my-key");
-    command.arg("0");
-    let result: redis::Value = command.query(&mut connection)?;
-    println!("{result:?}");
+    let iter: redis::Iter<(String, f64)> = connection.zscan("my-key")?;
+    for (member, score) in iter {
+        println!("{member}: {score}");
+    }
     Ok(())
 }
 ```
diff --git a/redis/commands/streams/xautoclaim.mdx b/redis/commands/streams/xautoclaim.mdx
index 34575fc9f..c7a1f3230 100644
--- a/redis/commands/streams/xautoclaim.mdx
+++ b/redis/commands/streams/xautoclaim.mdx
@@ -163,18 +163,22 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 <Tab title="redis-rs">
 
 ```rust
+use redis::streams::StreamAutoClaimOptions;
+use redis::TypedCommands;
+
 fn main() -> redis::RedisResult<()> {
     let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
     let client = redis::Client::open(url)?;
     let mut connection = client.get_connection()?;
 
-    let mut command = redis::cmd("XAUTOCLAIM");
-    command.arg("my-key");
-    command.arg("workers");
-    command.arg("worker-1");
-    command.arg("min-idle-time");
-    command.arg("start");
-    let result: redis::Value = command.query(&mut connection)?;
+    let result = connection.xautoclaim_options(
+        "my-key",
+        "workers",
+        "worker-1",
+        60000,
+        "0-0",
+        StreamAutoClaimOptions::default(),
+    )?;
     println!("{result:?}");
     Ok(())
 }

From b61d3235f7858b385b59f501a77e99d3bca06638 Mon Sep 17 00:00:00 2001
From: Mehmet Dogan <mehmet@dogan.io>
Date: Thu, 13 Aug 2026 14:55:01 +0300
Subject: [PATCH 09/12] Tab -> Accordion

---
 redis/commands/bitmap/bitcount.mdx            | 36 +++++++++----------
 redis/commands/bitmap/bitfield-ro.mdx         | 36 +++++++++----------
 redis/commands/bitmap/bitfield.mdx            | 36 +++++++++----------
 redis/commands/bitmap/bitop.mdx               | 36 +++++++++----------
 redis/commands/bitmap/bitpos.mdx              | 36 +++++++++----------
 redis/commands/bitmap/getbit.mdx              | 36 +++++++++----------
 redis/commands/bitmap/setbit.mdx              | 36 +++++++++----------
 redis/commands/connection/auth.mdx            | 28 +++++++--------
 redis/commands/connection/client-getname.mdx  | 28 +++++++--------
 redis/commands/connection/client-id.mdx       | 28 +++++++--------
 redis/commands/connection/client-info.mdx     | 28 +++++++--------
 redis/commands/connection/client-list.mdx     | 28 +++++++--------
 redis/commands/connection/client-setinfo.mdx  | 28 +++++++--------
 redis/commands/connection/client-setname.mdx  | 28 +++++++--------
 redis/commands/connection/echo.mdx            | 36 +++++++++----------
 redis/commands/connection/hello.mdx           | 28 +++++++--------
 redis/commands/connection/ping.mdx            | 36 +++++++++----------
 redis/commands/connection/quit.mdx            | 28 +++++++--------
 redis/commands/connection/reset.mdx           | 28 +++++++--------
 redis/commands/connection/select.mdx          | 36 +++++++++----------
 redis/commands/functions/fcall-ro.mdx         | 36 +++++++++----------
 redis/commands/functions/fcall.mdx            | 36 +++++++++----------
 redis/commands/functions/function-delete.mdx  | 36 +++++++++----------
 redis/commands/functions/function-flush.mdx   | 36 +++++++++----------
 redis/commands/functions/function-kill.mdx    | 36 +++++++++----------
 redis/commands/functions/function-list.mdx    | 36 +++++++++----------
 redis/commands/functions/function-load.mdx    | 36 +++++++++----------
 redis/commands/functions/function-stats.mdx   | 36 +++++++++----------
 redis/commands/generic/copy.mdx               | 36 +++++++++----------
 redis/commands/generic/del.mdx                | 36 +++++++++----------
 redis/commands/generic/dump.mdx               | 36 +++++++++----------
 redis/commands/generic/exists.mdx             | 36 +++++++++----------
 redis/commands/generic/expire.mdx             | 36 +++++++++----------
 redis/commands/generic/expireat.mdx           | 36 +++++++++----------
 redis/commands/generic/expiretime.mdx         | 36 +++++++++----------
 redis/commands/generic/keys.mdx               | 36 +++++++++----------
 redis/commands/generic/memory-usage.mdx       | 36 +++++++++----------
 redis/commands/generic/persist.mdx            | 36 +++++++++----------
 redis/commands/generic/pexpire.mdx            | 36 +++++++++----------
 redis/commands/generic/pexpireat.mdx          | 36 +++++++++----------
 redis/commands/generic/pexpiretime.mdx        | 36 +++++++++----------
 redis/commands/generic/pttl.mdx               | 36 +++++++++----------
 redis/commands/generic/randomkey.mdx          | 36 +++++++++----------
 redis/commands/generic/rename.mdx             | 36 +++++++++----------
 redis/commands/generic/renamenx.mdx           | 36 +++++++++----------
 redis/commands/generic/restore.mdx            | 36 +++++++++----------
 redis/commands/generic/scan.mdx               | 36 +++++++++----------
 redis/commands/generic/touch.mdx              | 36 +++++++++----------
 redis/commands/generic/ttl.mdx                | 36 +++++++++----------
 redis/commands/generic/type.mdx               | 36 +++++++++----------
 redis/commands/generic/unlink.mdx             | 36 +++++++++----------
 redis/commands/generic/wait.mdx               | 36 +++++++++----------
 redis/commands/generic/waitaof.mdx            | 36 +++++++++----------
 redis/commands/geo/geoadd.mdx                 | 36 +++++++++----------
 redis/commands/geo/geodist.mdx                | 36 +++++++++----------
 redis/commands/geo/geohash.mdx                | 36 +++++++++----------
 redis/commands/geo/geopos.mdx                 | 36 +++++++++----------
 redis/commands/geo/georadius-ro.mdx           | 36 +++++++++----------
 redis/commands/geo/georadius.mdx              | 36 +++++++++----------
 redis/commands/geo/georadiusbymember-ro.mdx   | 36 +++++++++----------
 redis/commands/geo/georadiusbymember.mdx      | 36 +++++++++----------
 redis/commands/geo/geosearch.mdx              | 36 +++++++++----------
 redis/commands/geo/geosearchstore.mdx         | 36 +++++++++----------
 redis/commands/hash/hdel.mdx                  | 36 +++++++++----------
 redis/commands/hash/hexists.mdx               | 36 +++++++++----------
 redis/commands/hash/hexpire.mdx               | 36 +++++++++----------
 redis/commands/hash/hexpireat.mdx             | 36 +++++++++----------
 redis/commands/hash/hexpiretime.mdx           | 36 +++++++++----------
 redis/commands/hash/hget.mdx                  | 36 +++++++++----------
 redis/commands/hash/hgetall.mdx               | 36 +++++++++----------
 redis/commands/hash/hgetdel.mdx               | 36 +++++++++----------
 redis/commands/hash/hgetex.mdx                | 36 +++++++++----------
 redis/commands/hash/hincrby.mdx               | 36 +++++++++----------
 redis/commands/hash/hincrbyfloat.mdx          | 36 +++++++++----------
 redis/commands/hash/hkeys.mdx                 | 36 +++++++++----------
 redis/commands/hash/hlen.mdx                  | 36 +++++++++----------
 redis/commands/hash/hmget.mdx                 | 36 +++++++++----------
 redis/commands/hash/hmset.mdx                 | 36 +++++++++----------
 redis/commands/hash/hpersist.mdx              | 36 +++++++++----------
 redis/commands/hash/hpexpire.mdx              | 36 +++++++++----------
 redis/commands/hash/hpexpireat.mdx            | 36 +++++++++----------
 redis/commands/hash/hpexpiretime.mdx          | 36 +++++++++----------
 redis/commands/hash/hpttl.mdx                 | 36 +++++++++----------
 redis/commands/hash/hrandfield.mdx            | 36 +++++++++----------
 redis/commands/hash/hscan.mdx                 | 36 +++++++++----------
 redis/commands/hash/hset.mdx                  | 36 +++++++++----------
 redis/commands/hash/hsetex.mdx                | 36 +++++++++----------
 redis/commands/hash/hsetnx.mdx                | 36 +++++++++----------
 redis/commands/hash/hstrlen.mdx               | 36 +++++++++----------
 redis/commands/hash/httl.mdx                  | 36 +++++++++----------
 redis/commands/hash/hvals.mdx                 | 36 +++++++++----------
 redis/commands/hyperloglog/pfadd.mdx          | 36 +++++++++----------
 redis/commands/hyperloglog/pfcount.mdx        | 36 +++++++++----------
 redis/commands/hyperloglog/pfmerge.mdx        | 36 +++++++++----------
 redis/commands/json/json-arrappend.mdx        | 36 +++++++++----------
 redis/commands/json/json-arrindex.mdx         | 36 +++++++++----------
 redis/commands/json/json-arrinsert.mdx        | 36 +++++++++----------
 redis/commands/json/json-arrlen.mdx           | 36 +++++++++----------
 redis/commands/json/json-arrpop.mdx           | 36 +++++++++----------
 redis/commands/json/json-arrtrim.mdx          | 36 +++++++++----------
 redis/commands/json/json-clear.mdx            | 36 +++++++++----------
 redis/commands/json/json-debug.mdx            | 36 +++++++++----------
 redis/commands/json/json-del.mdx              | 36 +++++++++----------
 redis/commands/json/json-forget.mdx           | 36 +++++++++----------
 redis/commands/json/json-get.mdx              | 36 +++++++++----------
 redis/commands/json/json-merge.mdx            | 36 +++++++++----------
 redis/commands/json/json-mget.mdx             | 36 +++++++++----------
 redis/commands/json/json-mset.mdx             | 36 +++++++++----------
 redis/commands/json/json-numincrby.mdx        | 36 +++++++++----------
 redis/commands/json/json-nummultby.mdx        | 36 +++++++++----------
 redis/commands/json/json-objkeys.mdx          | 36 +++++++++----------
 redis/commands/json/json-objlen.mdx           | 36 +++++++++----------
 redis/commands/json/json-resp.mdx             | 36 +++++++++----------
 redis/commands/json/json-set.mdx              | 36 +++++++++----------
 redis/commands/json/json-strappend.mdx        | 36 +++++++++----------
 redis/commands/json/json-strlen.mdx           | 36 +++++++++----------
 redis/commands/json/json-toggle.mdx           | 36 +++++++++----------
 redis/commands/json/json-type.mdx             | 36 +++++++++----------
 redis/commands/list/blmove.mdx                | 36 +++++++++----------
 redis/commands/list/blmpop.mdx                | 36 +++++++++----------
 redis/commands/list/blpop.mdx                 | 36 +++++++++----------
 redis/commands/list/brpop.mdx                 | 36 +++++++++----------
 redis/commands/list/brpoplpush.mdx            | 36 +++++++++----------
 redis/commands/list/lindex.mdx                | 36 +++++++++----------
 redis/commands/list/linsert.mdx               | 36 +++++++++----------
 redis/commands/list/llen.mdx                  | 36 +++++++++----------
 redis/commands/list/lmove.mdx                 | 36 +++++++++----------
 redis/commands/list/lmpop.mdx                 | 36 +++++++++----------
 redis/commands/list/lpop.mdx                  | 36 +++++++++----------
 redis/commands/list/lpos.mdx                  | 36 +++++++++----------
 redis/commands/list/lpush.mdx                 | 36 +++++++++----------
 redis/commands/list/lpushx.mdx                | 36 +++++++++----------
 redis/commands/list/lrange.mdx                | 36 +++++++++----------
 redis/commands/list/lrem.mdx                  | 36 +++++++++----------
 redis/commands/list/lset.mdx                  | 36 +++++++++----------
 redis/commands/list/ltrim.mdx                 | 36 +++++++++----------
 redis/commands/list/rpop.mdx                  | 36 +++++++++----------
 redis/commands/list/rpoplpush.mdx             | 36 +++++++++----------
 redis/commands/list/rpush.mdx                 | 36 +++++++++----------
 redis/commands/list/rpushx.mdx                | 36 +++++++++----------
 redis/commands/pub-sub/psubscribe.mdx         | 28 +++++++--------
 redis/commands/pub-sub/publish.mdx            | 36 +++++++++----------
 redis/commands/pub-sub/pubsub.mdx             | 36 +++++++++----------
 redis/commands/pub-sub/punsubscribe.mdx       | 28 +++++++--------
 redis/commands/pub-sub/subscribe.mdx          | 28 +++++++--------
 redis/commands/pub-sub/unsubscribe.mdx        | 28 +++++++--------
 redis/commands/scripting/eval-ro.mdx          | 36 +++++++++----------
 redis/commands/scripting/eval.mdx             | 36 +++++++++----------
 redis/commands/scripting/evalsha-ro.mdx       | 36 +++++++++----------
 redis/commands/scripting/evalsha.mdx          | 36 +++++++++----------
 redis/commands/scripting/script-exists.mdx    | 36 +++++++++----------
 redis/commands/scripting/script-flush.mdx     | 36 +++++++++----------
 redis/commands/scripting/script-kill.mdx      | 36 +++++++++----------
 redis/commands/scripting/script-load.mdx      | 36 +++++++++----------
 redis/commands/search/search-aggregate.mdx    | 28 +++++++--------
 redis/commands/search/search-aliasadd.mdx     | 28 +++++++--------
 redis/commands/search/search-aliasdel.mdx     | 28 +++++++--------
 redis/commands/search/search-count.mdx        | 28 +++++++--------
 redis/commands/search/search-create.mdx       | 28 +++++++--------
 redis/commands/search/search-describe.mdx     | 28 +++++++--------
 redis/commands/search/search-drop.mdx         | 28 +++++++--------
 redis/commands/search/search-listaliases.mdx  | 28 +++++++--------
 redis/commands/search/search-listindexes.mdx  | 28 +++++++--------
 redis/commands/search/search-query.mdx        | 28 +++++++--------
 redis/commands/search/search-reindex.mdx      | 12 +++----
 redis/commands/search/search-waitindexing.mdx | 28 +++++++--------
 redis/commands/server/acl.mdx                 | 36 +++++++++----------
 redis/commands/server/command.mdx             | 36 +++++++++----------
 redis/commands/server/config-get.mdx          | 36 +++++++++----------
 redis/commands/server/config-set.mdx          | 36 +++++++++----------
 redis/commands/server/dbsize.mdx              | 36 +++++++++----------
 redis/commands/server/flushall.mdx            | 36 +++++++++----------
 redis/commands/server/flushdb.mdx             | 36 +++++++++----------
 redis/commands/server/info.mdx                | 36 +++++++++----------
 redis/commands/server/monitor.mdx             | 24 ++++++-------
 redis/commands/server/time.mdx                | 36 +++++++++----------
 redis/commands/set/sadd.mdx                   | 36 +++++++++----------
 redis/commands/set/scard.mdx                  | 36 +++++++++----------
 redis/commands/set/sdiff.mdx                  | 36 +++++++++----------
 redis/commands/set/sdiffstore.mdx             | 36 +++++++++----------
 redis/commands/set/sinter.mdx                 | 36 +++++++++----------
 redis/commands/set/sintercard.mdx             | 36 +++++++++----------
 redis/commands/set/sinterstore.mdx            | 36 +++++++++----------
 redis/commands/set/sismember.mdx              | 36 +++++++++----------
 redis/commands/set/smembers.mdx               | 36 +++++++++----------
 redis/commands/set/smismember.mdx             | 36 +++++++++----------
 redis/commands/set/smove.mdx                  | 36 +++++++++----------
 redis/commands/set/spop.mdx                   | 36 +++++++++----------
 redis/commands/set/srandmember.mdx            | 36 +++++++++----------
 redis/commands/set/srem.mdx                   | 36 +++++++++----------
 redis/commands/set/sscan.mdx                  | 36 +++++++++----------
 redis/commands/set/sunion.mdx                 | 36 +++++++++----------
 redis/commands/set/sunionstore.mdx            | 36 +++++++++----------
 redis/commands/sorted-set/bzmpop.mdx          | 36 +++++++++----------
 redis/commands/sorted-set/bzpopmax.mdx        | 36 +++++++++----------
 redis/commands/sorted-set/bzpopmin.mdx        | 36 +++++++++----------
 redis/commands/sorted-set/zadd.mdx            | 36 +++++++++----------
 redis/commands/sorted-set/zcard.mdx           | 36 +++++++++----------
 redis/commands/sorted-set/zcount.mdx          | 36 +++++++++----------
 redis/commands/sorted-set/zdiff.mdx           | 36 +++++++++----------
 redis/commands/sorted-set/zdiffstore.mdx      | 36 +++++++++----------
 redis/commands/sorted-set/zincrby.mdx         | 36 +++++++++----------
 redis/commands/sorted-set/zinter.mdx          | 36 +++++++++----------
 redis/commands/sorted-set/zintercard.mdx      | 36 +++++++++----------
 redis/commands/sorted-set/zinterstore.mdx     | 36 +++++++++----------
 redis/commands/sorted-set/zlexcount.mdx       | 36 +++++++++----------
 redis/commands/sorted-set/zmpop.mdx           | 36 +++++++++----------
 redis/commands/sorted-set/zmscore.mdx         | 36 +++++++++----------
 redis/commands/sorted-set/zpopmax.mdx         | 36 +++++++++----------
 redis/commands/sorted-set/zpopmin.mdx         | 36 +++++++++----------
 redis/commands/sorted-set/zrandmember.mdx     | 36 +++++++++----------
 redis/commands/sorted-set/zrange.mdx          | 36 +++++++++----------
 redis/commands/sorted-set/zrangebylex.mdx     | 36 +++++++++----------
 redis/commands/sorted-set/zrangebyscore.mdx   | 36 +++++++++----------
 redis/commands/sorted-set/zrangestore.mdx     | 36 +++++++++----------
 redis/commands/sorted-set/zrank.mdx           | 36 +++++++++----------
 redis/commands/sorted-set/zrem.mdx            | 36 +++++++++----------
 redis/commands/sorted-set/zremrangebylex.mdx  | 36 +++++++++----------
 redis/commands/sorted-set/zremrangebyrank.mdx | 36 +++++++++----------
 .../commands/sorted-set/zremrangebyscore.mdx  | 36 +++++++++----------
 redis/commands/sorted-set/zrevrange.mdx       | 36 +++++++++----------
 redis/commands/sorted-set/zrevrangebylex.mdx  | 36 +++++++++----------
 .../commands/sorted-set/zrevrangebyscore.mdx  | 36 +++++++++----------
 redis/commands/sorted-set/zrevrank.mdx        | 36 +++++++++----------
 redis/commands/sorted-set/zscan.mdx           | 36 +++++++++----------
 redis/commands/sorted-set/zscore.mdx          | 36 +++++++++----------
 redis/commands/sorted-set/zunion.mdx          | 36 +++++++++----------
 redis/commands/sorted-set/zunionstore.mdx     | 36 +++++++++----------
 redis/commands/streams/xack.mdx               | 36 +++++++++----------
 redis/commands/streams/xackdel.mdx            | 36 +++++++++----------
 redis/commands/streams/xadd.mdx               | 36 +++++++++----------
 redis/commands/streams/xautoclaim.mdx         | 36 +++++++++----------
 redis/commands/streams/xclaim.mdx             | 36 +++++++++----------
 redis/commands/streams/xdel.mdx               | 36 +++++++++----------
 redis/commands/streams/xdelex.mdx             | 36 +++++++++----------
 redis/commands/streams/xgroup.mdx             | 36 +++++++++----------
 redis/commands/streams/xinfo-consumers.mdx    | 36 +++++++++----------
 redis/commands/streams/xinfo-groups.mdx       | 36 +++++++++----------
 redis/commands/streams/xinfo-stream.mdx       | 36 +++++++++----------
 redis/commands/streams/xlen.mdx               | 36 +++++++++----------
 redis/commands/streams/xpending.mdx           | 36 +++++++++----------
 redis/commands/streams/xrange.mdx             | 36 +++++++++----------
 redis/commands/streams/xread.mdx              | 36 +++++++++----------
 redis/commands/streams/xreadgroup.mdx         | 36 +++++++++----------
 redis/commands/streams/xrevrange.mdx          | 36 +++++++++----------
 redis/commands/streams/xtrim.mdx              | 36 +++++++++----------
 redis/commands/string/append.mdx              | 36 +++++++++----------
 redis/commands/string/decr.mdx                | 36 +++++++++----------
 redis/commands/string/decrby.mdx              | 36 +++++++++----------
 redis/commands/string/delex.mdx               | 36 +++++++++----------
 redis/commands/string/digest.mdx              | 36 +++++++++----------
 redis/commands/string/get.mdx                 | 36 +++++++++----------
 redis/commands/string/getdel.mdx              | 36 +++++++++----------
 redis/commands/string/getex.mdx               | 36 +++++++++----------
 redis/commands/string/getrange.mdx            | 36 +++++++++----------
 redis/commands/string/getset.mdx              | 36 +++++++++----------
 redis/commands/string/incr.mdx                | 36 +++++++++----------
 redis/commands/string/incrby.mdx              | 36 +++++++++----------
 redis/commands/string/incrbyfloat.mdx         | 36 +++++++++----------
 redis/commands/string/mget.mdx                | 36 +++++++++----------
 redis/commands/string/mset.mdx                | 36 +++++++++----------
 redis/commands/string/msetnx.mdx              | 36 +++++++++----------
 redis/commands/string/psetex.mdx              | 36 +++++++++----------
 redis/commands/string/set.mdx                 | 36 +++++++++----------
 redis/commands/string/setex.mdx               | 36 +++++++++----------
 redis/commands/string/setnx.mdx               | 36 +++++++++----------
 redis/commands/string/setrange.mdx            | 36 +++++++++----------
 redis/commands/string/strlen.mdx              | 36 +++++++++----------
 redis/commands/transactions/discard.mdx       | 28 +++++++--------
 redis/commands/transactions/exec.mdx          | 28 +++++++--------
 redis/commands/transactions/multi.mdx         | 28 +++++++--------
 redis/commands/transactions/unwatch.mdx       | 28 +++++++--------
 redis/commands/transactions/watch.mdx         | 28 +++++++--------
 273 files changed, 4776 insertions(+), 4776 deletions(-)

diff --git a/redis/commands/bitmap/bitcount.mdx b/redis/commands/bitmap/bitcount.mdx
index 78278f36c..a529b8f0e 100644
--- a/redis/commands/bitmap/bitcount.mdx
+++ b/redis/commands/bitmap/bitcount.mdx
@@ -39,9 +39,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -51,9 +51,9 @@ const redis = Redis.fromEnv();
 const bits = await redis.bitcount(key);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -63,9 +63,9 @@ result = redis.bitcount("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -75,9 +75,9 @@ const result = await redis.bitcount("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -89,9 +89,9 @@ const result = await client.bitCount("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -102,9 +102,9 @@ result = client.bitcount("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -131,9 +131,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -146,9 +146,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -164,6 +164,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/bitmap/bitfield-ro.mdx b/redis/commands/bitmap/bitfield-ro.mdx
index 26561f978..68f9a01cf 100644
--- a/redis/commands/bitmap/bitfield-ro.mdx
+++ b/redis/commands/bitmap/bitfield-ro.mdx
@@ -37,17 +37,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -57,9 +57,9 @@ result = redis.bitfield_ro("my-key").get("u8", 0).execute()
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -69,9 +69,9 @@ const result = await redis.bitfield_ro("my-key", "GET", "u8", "0");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -83,9 +83,9 @@ const result = await client.bitFieldRo("my-key", [{ encoding: "u8", offset: 0 }]
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -96,9 +96,9 @@ result = client.bitfield_ro("my-key", "u8", 0)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -125,9 +125,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -140,9 +140,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -158,6 +158,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/bitmap/bitfield.mdx b/redis/commands/bitmap/bitfield.mdx
index e9bb52a61..ece8c18d9 100644
--- a/redis/commands/bitmap/bitfield.mdx
+++ b/redis/commands/bitmap/bitfield.mdx
@@ -50,9 +50,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -62,9 +62,9 @@ const result = await redis.bitfield("my-key").get("u8", 0).exec();
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -74,9 +74,9 @@ result = redis.bitfield("my-key").get("u8", 0).execute()
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -86,9 +86,9 @@ const result = await redis.bitfield("my-key", "GET", "u8", "0");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -100,9 +100,9 @@ const result = await client.bitField("my-key", [{ operation: "GET", encoding: "u
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -113,9 +113,9 @@ result = client.bitfield("my-key").get("u8", 0).execute()
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -142,9 +142,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -157,9 +157,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -175,6 +175,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/bitmap/bitop.mdx b/redis/commands/bitmap/bitop.mdx
index dd98b2809..d42da5c34 100644
--- a/redis/commands/bitmap/bitop.mdx
+++ b/redis/commands/bitmap/bitop.mdx
@@ -42,9 +42,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -64,9 +64,9 @@ await redis.bitop("xor", "destKey", "sourceKey1", "sourceKey2");
 await redis.bitop("not", "destKey", "sourceKey");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -76,9 +76,9 @@ result = redis.bitop("AND", "destination-key", "source-key-1", "source-key-2")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -88,9 +88,9 @@ const result = await redis.bitop("AND", "destination-key", "source-key-1", "sour
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -102,9 +102,9 @@ const result = await client.bitOp("AND", "destination-key", ["source-key-1", "so
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -115,9 +115,9 @@ result = client.bitop("AND", "destination-key", "source-key-1", "source-key-2")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -144,9 +144,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -159,9 +159,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -177,6 +177,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/bitmap/bitpos.mdx b/redis/commands/bitmap/bitpos.mdx
index 7f0b3665c..a5e775f9f 100644
--- a/redis/commands/bitmap/bitpos.mdx
+++ b/redis/commands/bitmap/bitpos.mdx
@@ -40,9 +40,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -52,9 +52,9 @@ const redis = Redis.fromEnv();
 await redis.bitpos("key", 1);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -64,9 +64,9 @@ result = redis.bitpos("my-key", 1)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -76,9 +76,9 @@ const result = await redis.bitpos("my-key", "1");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -90,9 +90,9 @@ const result = await client.bitPos("my-key", 1);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -103,9 +103,9 @@ result = client.bitpos("my-key", 1)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -132,9 +132,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -147,9 +147,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -166,6 +166,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/bitmap/getbit.mdx b/redis/commands/bitmap/getbit.mdx
index 2bacc8c8b..dc35cef63 100644
--- a/redis/commands/bitmap/getbit.mdx
+++ b/redis/commands/bitmap/getbit.mdx
@@ -37,9 +37,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -49,9 +49,9 @@ const redis = Redis.fromEnv();
 const bit = await redis.getbit(key, 4);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -61,9 +61,9 @@ result = redis.getbit("my-key", 0)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -73,9 +73,9 @@ const result = await redis.getbit("my-key", "0");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -87,9 +87,9 @@ const result = await client.getBit("my-key", 0);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -100,9 +100,9 @@ result = client.getbit("my-key", 0)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -129,9 +129,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -144,9 +144,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -162,6 +162,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/bitmap/setbit.mdx b/redis/commands/bitmap/setbit.mdx
index 35403759e..1c51b9177 100644
--- a/redis/commands/bitmap/setbit.mdx
+++ b/redis/commands/bitmap/setbit.mdx
@@ -40,9 +40,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -52,9 +52,9 @@ const redis = Redis.fromEnv();
 const originalBit = await redis.setbit(key, 4, 1);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -64,9 +64,9 @@ result = redis.setbit("my-key", 0, 1)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -76,9 +76,9 @@ const result = await redis.setbit("my-key", "0", "1");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -90,9 +90,9 @@ const result = await client.setBit("my-key", 0, 1);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -103,9 +103,9 @@ result = client.setbit("my-key", 0, 1)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -132,9 +132,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -147,9 +147,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -165,6 +165,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/connection/auth.mdx b/redis/commands/connection/auth.mdx
index ed87cd029..8f75eff82 100644
--- a/redis/commands/connection/auth.mdx
+++ b/redis/commands/connection/auth.mdx
@@ -41,9 +41,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -53,9 +53,9 @@ const result = await redis.auth("password");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -67,9 +67,9 @@ const result = await client.auth({ password: "password" });
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -80,9 +80,9 @@ result = client.auth("password")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -109,9 +109,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -124,9 +124,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -142,6 +142,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/connection/client-getname.mdx b/redis/commands/connection/client-getname.mdx
index 145935e88..1be19f851 100644
--- a/redis/commands/connection/client-getname.mdx
+++ b/redis/commands/connection/client-getname.mdx
@@ -39,9 +39,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -51,9 +51,9 @@ const result = await redis.client("GETNAME");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -65,9 +65,9 @@ const result = await client.clientGetName();
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -78,9 +78,9 @@ result = client.client_getname()
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -107,9 +107,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -122,9 +122,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -140,6 +140,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/connection/client-id.mdx b/redis/commands/connection/client-id.mdx
index 179c0bcb1..89ce44a60 100644
--- a/redis/commands/connection/client-id.mdx
+++ b/redis/commands/connection/client-id.mdx
@@ -39,9 +39,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -51,9 +51,9 @@ const result = await redis.client("ID");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -65,9 +65,9 @@ const result = await client.clientId();
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -78,9 +78,9 @@ result = client.client_id()
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -107,9 +107,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -122,9 +122,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -140,6 +140,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/connection/client-info.mdx b/redis/commands/connection/client-info.mdx
index 61f71bc35..fd7d33881 100644
--- a/redis/commands/connection/client-info.mdx
+++ b/redis/commands/connection/client-info.mdx
@@ -39,9 +39,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -51,9 +51,9 @@ const result = await redis.client("INFO");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -65,9 +65,9 @@ const result = await client.clientInfo();
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -78,9 +78,9 @@ result = client.client_info()
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -107,9 +107,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -122,9 +122,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -140,6 +140,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/connection/client-list.mdx b/redis/commands/connection/client-list.mdx
index 5c0468dee..23e58f705 100644
--- a/redis/commands/connection/client-list.mdx
+++ b/redis/commands/connection/client-list.mdx
@@ -39,9 +39,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -51,9 +51,9 @@ const result = await redis.client("LIST");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -65,9 +65,9 @@ const result = await client.clientList();
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -78,9 +78,9 @@ result = client.client_list()
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -107,9 +107,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -122,9 +122,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -140,6 +140,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/connection/client-setinfo.mdx b/redis/commands/connection/client-setinfo.mdx
index ea01b3a28..88134d015 100644
--- a/redis/commands/connection/client-setinfo.mdx
+++ b/redis/commands/connection/client-setinfo.mdx
@@ -42,9 +42,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -54,9 +54,9 @@ const result = await redis.call("CLIENT", "SETINFO", "LIB-NAME", "my-client");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -68,9 +68,9 @@ const result = await client.sendCommand(["CLIENT", "SETINFO", "LIB-NAME", "my-cl
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -81,9 +81,9 @@ result = client.client_setinfo("LIB-NAME", "my-client")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -110,9 +110,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -125,9 +125,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -145,6 +145,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/connection/client-setname.mdx b/redis/commands/connection/client-setname.mdx
index f05629b3f..6c0c8f06c 100644
--- a/redis/commands/connection/client-setname.mdx
+++ b/redis/commands/connection/client-setname.mdx
@@ -41,9 +41,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -53,9 +53,9 @@ const result = await redis.client("SETNAME", "worker-1");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -67,9 +67,9 @@ const result = await client.clientSetName("worker-1");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -80,9 +80,9 @@ result = client.client_setname("worker-1")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -109,9 +109,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -124,9 +124,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -142,6 +142,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/connection/echo.mdx b/redis/commands/connection/echo.mdx
index 6b53a8f77..7b0e6a314 100644
--- a/redis/commands/connection/echo.mdx
+++ b/redis/commands/connection/echo.mdx
@@ -36,9 +36,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -49,9 +49,9 @@ const response = await redis.echo("hello world");
 console.log(response); // "hello world"
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -61,9 +61,9 @@ result = redis.echo("hello")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -73,9 +73,9 @@ const result = await redis.echo("hello");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -87,9 +87,9 @@ const result = await client.echo("hello");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -100,9 +100,9 @@ result = client.echo("hello")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -129,9 +129,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -144,9 +144,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -162,6 +162,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/connection/hello.mdx b/redis/commands/connection/hello.mdx
index 3ecc767d8..b149fe969 100644
--- a/redis/commands/connection/hello.mdx
+++ b/redis/commands/connection/hello.mdx
@@ -45,9 +45,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -57,9 +57,9 @@ const result = await redis.hello();
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -71,9 +71,9 @@ const result = await client.hello();
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -84,9 +84,9 @@ result = client.hello()
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -113,9 +113,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -130,9 +130,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -148,6 +148,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/connection/ping.mdx b/redis/commands/connection/ping.mdx
index 48fcb33d5..7778d5daa 100644
--- a/redis/commands/connection/ping.mdx
+++ b/redis/commands/connection/ping.mdx
@@ -41,9 +41,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -54,9 +54,9 @@ const response = await redis.ping();
 console.log(response); // "PONG"
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -66,9 +66,9 @@ result = redis.ping()
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -78,9 +78,9 @@ const result = await redis.ping();
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -92,9 +92,9 @@ const result = await client.ping();
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -105,9 +105,9 @@ result = client.ping()
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -134,9 +134,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -149,9 +149,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -167,6 +167,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/connection/quit.mdx b/redis/commands/connection/quit.mdx
index d66fca2f3..3fd9fe9b2 100644
--- a/redis/commands/connection/quit.mdx
+++ b/redis/commands/connection/quit.mdx
@@ -42,9 +42,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -54,9 +54,9 @@ const result = await redis.quit();
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -68,9 +68,9 @@ const result = await client.sendCommand(["QUIT"]);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -81,9 +81,9 @@ result = client.quit()
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -110,9 +110,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -127,9 +127,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -145,6 +145,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/connection/reset.mdx b/redis/commands/connection/reset.mdx
index 42e66edba..c210a27e1 100644
--- a/redis/commands/connection/reset.mdx
+++ b/redis/commands/connection/reset.mdx
@@ -38,9 +38,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -50,9 +50,9 @@ const result = await redis.reset();
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -64,9 +64,9 @@ const result = await client.sendCommand(["RESET"]);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -77,9 +77,9 @@ result = client.reset()
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -106,9 +106,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -121,9 +121,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -139,6 +139,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/connection/select.mdx b/redis/commands/connection/select.mdx
index a9326418e..9b969a582 100644
--- a/redis/commands/connection/select.mdx
+++ b/redis/commands/connection/select.mdx
@@ -40,25 +40,25 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 <Note>
   This command is not supported yet in `upstash_redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -68,9 +68,9 @@ const result = await redis.select("0");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -82,9 +82,9 @@ const result = await client.sendCommand(["SELECT", "0"]);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -95,9 +95,9 @@ result = client.select("0")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -124,9 +124,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -139,9 +139,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -157,6 +157,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/functions/fcall-ro.mdx b/redis/commands/functions/fcall-ro.mdx
index eb643f9d7..6d8c2233b 100644
--- a/redis/commands/functions/fcall-ro.mdx
+++ b/redis/commands/functions/fcall-ro.mdx
@@ -49,9 +49,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -80,17 +80,17 @@ await redis.functions.load({ code, replace: true });
 const value = await redis.functions.callRo("get_value", ["mykey"])
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 <Note>
   This command is not supported yet in `upstash_redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -100,9 +100,9 @@ const result = await redis.fcall_ro("my_function", "1", "my-key", "value");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -114,9 +114,9 @@ const result = await client.fCallRo("my_function", { keys: ["my-key"], arguments
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -127,9 +127,9 @@ result = client.fcall_ro("my_function", 1, "my-key", "value")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -156,9 +156,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -171,9 +171,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -190,6 +190,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/functions/fcall.mdx b/redis/commands/functions/fcall.mdx
index 56e17b844..41f47f2e0 100644
--- a/redis/commands/functions/fcall.mdx
+++ b/redis/commands/functions/fcall.mdx
@@ -69,9 +69,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -93,17 +93,17 @@ const res = await redis.functions.call("helloworld");
 console.log(res); // "Hello World!"
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 <Note>
   This command is not supported yet in `upstash_redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -113,9 +113,9 @@ const result = await redis.fcall("my_function", "1", "my-key", "value");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -127,9 +127,9 @@ const result = await client.fCall("my_function", { keys: ["my-key"], arguments:
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -140,9 +140,9 @@ result = client.fcall("my_function", 1, "my-key", "value")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -169,9 +169,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -184,9 +184,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -203,6 +203,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/functions/function-delete.mdx b/redis/commands/functions/function-delete.mdx
index 7beabcd92..e59772543 100644
--- a/redis/commands/functions/function-delete.mdx
+++ b/redis/commands/functions/function-delete.mdx
@@ -36,9 +36,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -48,17 +48,17 @@ const redis = Redis.fromEnv();
 await redis.functions.delete("mylib")
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 <Note>
   This command is not supported yet in `upstash_redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -68,9 +68,9 @@ const result = await redis.function("DELETE", "library-name");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -82,9 +82,9 @@ const result = await client.functionDelete("library-name");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -95,9 +95,9 @@ result = client.function_delete("library-name")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -124,9 +124,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -139,9 +139,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -158,6 +158,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/functions/function-flush.mdx b/redis/commands/functions/function-flush.mdx
index 018858890..1d6d4cf7a 100644
--- a/redis/commands/functions/function-flush.mdx
+++ b/redis/commands/functions/function-flush.mdx
@@ -36,9 +36,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -48,17 +48,17 @@ const redis = Redis.fromEnv();
 await redis.functions.flush()
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 <Note>
   This command is not supported yet in `upstash_redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -68,9 +68,9 @@ const result = await redis.function("FLUSH");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -82,9 +82,9 @@ const result = await client.functionFlush();
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -95,9 +95,9 @@ result = client.function_flush()
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -124,9 +124,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -139,9 +139,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -157,6 +157,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/functions/function-kill.mdx b/redis/commands/functions/function-kill.mdx
index 498d324c0..05e601c73 100644
--- a/redis/commands/functions/function-kill.mdx
+++ b/redis/commands/functions/function-kill.mdx
@@ -40,25 +40,25 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 <Note>
   This command is not supported yet in `upstash_redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -68,9 +68,9 @@ const result = await redis.function("KILL");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -82,9 +82,9 @@ const result = await client.functionKill();
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -95,9 +95,9 @@ result = client.function_kill()
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -124,9 +124,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -139,9 +139,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -157,6 +157,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/functions/function-list.mdx b/redis/commands/functions/function-list.mdx
index 2e772f6e4..e7d4259f4 100644
--- a/redis/commands/functions/function-list.mdx
+++ b/redis/commands/functions/function-list.mdx
@@ -37,9 +37,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -66,17 +66,17 @@ console.log(libs)
 // ]
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 <Note>
   This command is not supported yet in `upstash_redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -86,9 +86,9 @@ const result = await redis.function("LIST");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -100,9 +100,9 @@ const result = await client.functionList();
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -113,9 +113,9 @@ result = client.function_list()
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -142,9 +142,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -157,9 +157,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -175,6 +175,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/functions/function-load.mdx b/redis/commands/functions/function-load.mdx
index da49d81bf..95cc817c4 100644
--- a/redis/commands/functions/function-load.mdx
+++ b/redis/commands/functions/function-load.mdx
@@ -43,9 +43,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -75,17 +75,17 @@ const libraryName = await redis.functions.load({ code, replace: true });
 console.log(libraryName); // "mylib"
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 <Note>
   This command is not supported yet in `upstash_redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -95,9 +95,9 @@ const result = await redis.function("LOAD", "function-code");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -109,9 +109,9 @@ const result = await client.functionLoad("function-code");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -122,9 +122,9 @@ result = client.function_load("function-code")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -151,9 +151,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -166,9 +166,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -185,6 +185,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/functions/function-stats.mdx b/redis/commands/functions/function-stats.mdx
index 84995db6c..5099fcf2d 100644
--- a/redis/commands/functions/function-stats.mdx
+++ b/redis/commands/functions/function-stats.mdx
@@ -34,9 +34,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -56,17 +56,17 @@ console.log(stats)
 // }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 <Note>
   This command is not supported yet in `upstash_redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -76,9 +76,9 @@ const result = await redis.function("STATS");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -90,9 +90,9 @@ const result = await client.functionStats();
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -103,9 +103,9 @@ result = client.function_stats()
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -132,9 +132,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -147,9 +147,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -165,6 +165,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/generic/copy.mdx b/redis/commands/generic/copy.mdx
index 4a0c7ada6..c5200578f 100644
--- a/redis/commands/generic/copy.mdx
+++ b/redis/commands/generic/copy.mdx
@@ -41,9 +41,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -53,9 +53,9 @@ const result = await redis.copy("source-key", "destination-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -65,9 +65,9 @@ result = redis.copy("source-key", "destination-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -77,9 +77,9 @@ const result = await redis.copy("source-key", "destination-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -91,9 +91,9 @@ const result = await client.copy("source-key", "destination-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -104,9 +104,9 @@ result = client.copy("source-key", "destination-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -133,9 +133,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -148,9 +148,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -166,6 +166,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/generic/del.mdx b/redis/commands/generic/del.mdx
index a1c2124fa..c4d48adb0 100644
--- a/redis/commands/generic/del.mdx
+++ b/redis/commands/generic/del.mdx
@@ -36,9 +36,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -48,9 +48,9 @@ const redis = Redis.fromEnv();
 await redis.del("key1", "key2");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -60,9 +60,9 @@ result = redis.delete("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -72,9 +72,9 @@ const result = await redis.del("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -86,9 +86,9 @@ const result = await client.del("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -99,9 +99,9 @@ result = client.delete("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -128,9 +128,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -143,9 +143,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -161,6 +161,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/generic/dump.mdx b/redis/commands/generic/dump.mdx
index edbe97881..7697ef3f7 100644
--- a/redis/commands/generic/dump.mdx
+++ b/redis/commands/generic/dump.mdx
@@ -38,25 +38,25 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 <Note>
   This command is not supported yet in `upstash_redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -66,9 +66,9 @@ const result = await redis.dump("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -80,9 +80,9 @@ const result = await client.dump("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -93,9 +93,9 @@ result = client.dump("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -122,9 +122,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -137,9 +137,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -155,6 +155,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/generic/exists.mdx b/redis/commands/generic/exists.mdx
index 0f7c2eb56..73999203f 100644
--- a/redis/commands/generic/exists.mdx
+++ b/redis/commands/generic/exists.mdx
@@ -36,9 +36,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -51,9 +51,9 @@ const keys = await redis.exists("key1", "key2", "key3");
 console.log(keys) // 2
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -63,9 +63,9 @@ result = redis.exists("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -75,9 +75,9 @@ const result = await redis.exists("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -89,9 +89,9 @@ const result = await client.exists("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -102,9 +102,9 @@ result = client.exists("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -131,9 +131,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -146,9 +146,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -164,6 +164,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/generic/expire.mdx b/redis/commands/generic/expire.mdx
index 361679989..c2d8e94bb 100644
--- a/redis/commands/generic/expire.mdx
+++ b/redis/commands/generic/expire.mdx
@@ -47,9 +47,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -60,9 +60,9 @@ await redis.set("mykey", "Hello");
 await redis.expire("mykey", 10);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -72,9 +72,9 @@ result = redis.expire("my-key", 1000)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -84,9 +84,9 @@ const result = await redis.expire("my-key", "1000");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -98,9 +98,9 @@ const result = await client.expire("my-key", 1000);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -111,9 +111,9 @@ result = client.expire("my-key", 1000)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -141,9 +141,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -156,9 +156,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -174,6 +174,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/generic/expireat.mdx b/redis/commands/generic/expireat.mdx
index 0233c1623..695a99931 100644
--- a/redis/commands/generic/expireat.mdx
+++ b/redis/commands/generic/expireat.mdx
@@ -45,9 +45,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -59,9 +59,9 @@ const tenSecondsFromNow = Math.floor(Date.now() / 1000) + 10;
 await redis.expireat("mykey", tenSecondsFromNow);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -71,9 +71,9 @@ result = redis.expireat("my-key", 1735689600)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -83,9 +83,9 @@ const result = await redis.expireat("my-key", "1735689600");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -97,9 +97,9 @@ const result = await client.expireAt("my-key", 1735689600);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -110,9 +110,9 @@ result = client.expireat("my-key", 1735689600)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -140,9 +140,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -155,9 +155,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -173,6 +173,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/generic/expiretime.mdx b/redis/commands/generic/expiretime.mdx
index 42fdc2304..d15c39c7b 100644
--- a/redis/commands/generic/expiretime.mdx
+++ b/redis/commands/generic/expiretime.mdx
@@ -40,25 +40,25 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 <Note>
   This command is not supported yet in `upstash_redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -68,9 +68,9 @@ const result = await redis.expiretime("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -82,9 +82,9 @@ const result = await client.expireTime("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -95,9 +95,9 @@ result = client.expiretime("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -124,9 +124,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -139,9 +139,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -157,6 +157,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/generic/keys.mdx b/redis/commands/generic/keys.mdx
index 895526580..85a1662f0 100644
--- a/redis/commands/generic/keys.mdx
+++ b/redis/commands/generic/keys.mdx
@@ -43,9 +43,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -55,9 +55,9 @@ const redis = Redis.fromEnv();
 const keys = await redis.keys("prefix*");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -67,9 +67,9 @@ result = redis.keys("*")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -79,9 +79,9 @@ const result = await redis.keys("*");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -93,9 +93,9 @@ const result = await client.keys("*");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -106,9 +106,9 @@ result = client.keys("*")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -135,9 +135,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -150,9 +150,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -168,6 +168,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/generic/memory-usage.mdx b/redis/commands/generic/memory-usage.mdx
index 6cdfbf02b..ddeac1d62 100644
--- a/redis/commands/generic/memory-usage.mdx
+++ b/redis/commands/generic/memory-usage.mdx
@@ -44,25 +44,25 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 <Note>
   This command is not supported yet in `upstash_redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -72,9 +72,9 @@ const result = await redis.memory("USAGE", "my-key", "SAMPLES", "10");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -86,9 +86,9 @@ const result = await client.memoryUsage("my-key", { SAMPLES: 10 });
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -99,9 +99,9 @@ result = client.memory_usage("my-key", samples=10)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -128,9 +128,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -143,9 +143,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -164,6 +164,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/generic/persist.mdx b/redis/commands/generic/persist.mdx
index dd0ed96f7..fc09e18c8 100644
--- a/redis/commands/generic/persist.mdx
+++ b/redis/commands/generic/persist.mdx
@@ -36,9 +36,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -48,9 +48,9 @@ const redis = Redis.fromEnv();
 await redis.persist(key);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -60,9 +60,9 @@ result = redis.persist("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -72,9 +72,9 @@ const result = await redis.persist("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -86,9 +86,9 @@ const result = await client.persist("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -99,9 +99,9 @@ result = client.persist("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -128,9 +128,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -143,9 +143,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -161,6 +161,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/generic/pexpire.mdx b/redis/commands/generic/pexpire.mdx
index 820c3489e..bdef6080a 100644
--- a/redis/commands/generic/pexpire.mdx
+++ b/redis/commands/generic/pexpire.mdx
@@ -45,9 +45,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -57,9 +57,9 @@ const redis = Redis.fromEnv();
 await redis.pexpire(key, 60_000); // 1 minute
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -69,9 +69,9 @@ result = redis.pexpire("my-key", 1000)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -81,9 +81,9 @@ const result = await redis.pexpire("my-key", "1000");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -95,9 +95,9 @@ const result = await client.pExpire("my-key", 1000);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -108,9 +108,9 @@ result = client.pexpire("my-key", 1000)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -138,9 +138,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -153,9 +153,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -171,6 +171,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/generic/pexpireat.mdx b/redis/commands/generic/pexpireat.mdx
index 4dd2a87b3..96712b50e 100644
--- a/redis/commands/generic/pexpireat.mdx
+++ b/redis/commands/generic/pexpireat.mdx
@@ -45,9 +45,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -59,9 +59,9 @@ const tenMinutesFromNow = Date.now() + 10 * 60 * 1000;
 await redis.pexpireat("mykey", tenMinutesFromNow);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -71,9 +71,9 @@ result = redis.pexpireat("my-key", 1735689600)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -83,9 +83,9 @@ const result = await redis.pexpireat("my-key", "1735689600");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -97,9 +97,9 @@ const result = await client.pExpireAt("my-key", 1735689600);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -110,9 +110,9 @@ result = client.pexpireat("my-key", 1735689600)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -140,9 +140,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -155,9 +155,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -173,6 +173,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/generic/pexpiretime.mdx b/redis/commands/generic/pexpiretime.mdx
index 2a60fc354..1beea429e 100644
--- a/redis/commands/generic/pexpiretime.mdx
+++ b/redis/commands/generic/pexpiretime.mdx
@@ -40,25 +40,25 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 <Note>
   This command is not supported yet in `upstash_redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -68,9 +68,9 @@ const result = await redis.pexpiretime("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -82,9 +82,9 @@ const result = await client.pExpireTime("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -95,9 +95,9 @@ result = client.pexpiretime("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -124,9 +124,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -139,9 +139,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -157,6 +157,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/generic/pttl.mdx b/redis/commands/generic/pttl.mdx
index 73ce6b954..dafb341cf 100644
--- a/redis/commands/generic/pttl.mdx
+++ b/redis/commands/generic/pttl.mdx
@@ -40,9 +40,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -52,9 +52,9 @@ const redis = Redis.fromEnv();
 const millis = await redis.pttl(key);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -64,9 +64,9 @@ result = redis.pttl("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -76,9 +76,9 @@ const result = await redis.pttl("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -90,9 +90,9 @@ const result = await client.pTTL("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -103,9 +103,9 @@ result = client.pttl("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -132,9 +132,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -147,9 +147,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -165,6 +165,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/generic/randomkey.mdx b/redis/commands/generic/randomkey.mdx
index ee68486fc..af3d38c94 100644
--- a/redis/commands/generic/randomkey.mdx
+++ b/redis/commands/generic/randomkey.mdx
@@ -34,9 +34,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -46,9 +46,9 @@ const redis = Redis.fromEnv();
 const key = await redis.randomkey();
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -58,9 +58,9 @@ result = redis.randomkey()
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -70,9 +70,9 @@ const result = await redis.randomkey();
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -84,9 +84,9 @@ const result = await client.randomKey();
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -97,9 +97,9 @@ result = client.randomkey()
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -126,9 +126,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -141,9 +141,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -159,6 +159,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/generic/rename.mdx b/redis/commands/generic/rename.mdx
index 4a6a6a8db..6c1c33178 100644
--- a/redis/commands/generic/rename.mdx
+++ b/redis/commands/generic/rename.mdx
@@ -39,9 +39,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -51,9 +51,9 @@ const redis = Redis.fromEnv();
 await redis.rename("old", "new");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -63,9 +63,9 @@ result = redis.rename("old-key", "new-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -75,9 +75,9 @@ const result = await redis.rename("old-key", "new-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -89,9 +89,9 @@ const result = await client.rename("old-key", "new-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -102,9 +102,9 @@ result = client.rename("old-key", "new-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -131,9 +131,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -146,9 +146,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -164,6 +164,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/generic/renamenx.mdx b/redis/commands/generic/renamenx.mdx
index 5c3f96bf5..80ac14b34 100644
--- a/redis/commands/generic/renamenx.mdx
+++ b/redis/commands/generic/renamenx.mdx
@@ -37,9 +37,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -49,9 +49,9 @@ const redis = Redis.fromEnv();
 const renamed = await redis.renamenx("old", "new");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -61,9 +61,9 @@ result = redis.renamenx("old-key", "new-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -73,9 +73,9 @@ const result = await redis.renamenx("old-key", "new-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -87,9 +87,9 @@ const result = await client.renameNX("old-key", "new-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -100,9 +100,9 @@ result = client.renamenx("old-key", "new-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -129,9 +129,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -144,9 +144,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -162,6 +162,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/generic/restore.mdx b/redis/commands/generic/restore.mdx
index 6d1bcae25..95fa6ce45 100644
--- a/redis/commands/generic/restore.mdx
+++ b/redis/commands/generic/restore.mdx
@@ -52,25 +52,25 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 <Note>
   This command is not supported yet in `upstash_redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -80,9 +80,9 @@ const result = await redis.restore("my-key", "1", "serialized-value");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -94,9 +94,9 @@ const result = await client.restore("my-key", 1, "serialized-value");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -107,9 +107,9 @@ result = client.restore("my-key", 1, "serialized-value")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -137,9 +137,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -152,9 +152,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -172,6 +172,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/generic/scan.mdx b/redis/commands/generic/scan.mdx
index 96f0825e3..c684546df 100644
--- a/redis/commands/generic/scan.mdx
+++ b/redis/commands/generic/scan.mdx
@@ -48,9 +48,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -60,9 +60,9 @@ const redis = Redis.fromEnv();
 const [cursor, keys] = await redis.scan(0, { match: "*" });
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -72,9 +72,9 @@ result = redis.scan(0)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -84,9 +84,9 @@ const result = await redis.scan("0");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -98,9 +98,9 @@ const result = await client.scan("0");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -111,9 +111,9 @@ result = client.scan(0)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -140,9 +140,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -155,9 +155,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -175,6 +175,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/generic/touch.mdx b/redis/commands/generic/touch.mdx
index d059a9cde..cc6d1edcf 100644
--- a/redis/commands/generic/touch.mdx
+++ b/redis/commands/generic/touch.mdx
@@ -36,9 +36,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -48,9 +48,9 @@ const redis = Redis.fromEnv();
 await redis.touch("key1", "key2", "key3");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -60,9 +60,9 @@ result = redis.touch("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -72,9 +72,9 @@ const result = await redis.touch("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -86,9 +86,9 @@ const result = await client.touch("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -99,9 +99,9 @@ result = client.touch("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -128,9 +128,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -143,9 +143,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -161,6 +161,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/generic/ttl.mdx b/redis/commands/generic/ttl.mdx
index 2a7a37d27..f34c2d927 100644
--- a/redis/commands/generic/ttl.mdx
+++ b/redis/commands/generic/ttl.mdx
@@ -40,9 +40,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -52,9 +52,9 @@ const redis = Redis.fromEnv();
 const seconds = await redis.ttl(key);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -64,9 +64,9 @@ result = redis.ttl("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -76,9 +76,9 @@ const result = await redis.ttl("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -90,9 +90,9 @@ const result = await client.ttl("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -103,9 +103,9 @@ result = client.ttl("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -132,9 +132,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -147,9 +147,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -165,6 +165,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/generic/type.mdx b/redis/commands/generic/type.mdx
index 7ed14e2c9..194ca3667 100644
--- a/redis/commands/generic/type.mdx
+++ b/redis/commands/generic/type.mdx
@@ -36,9 +36,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -50,9 +50,9 @@ const t = await redis.type("key");
 console.log(t) // "string"
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -62,9 +62,9 @@ result = redis.type("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -74,9 +74,9 @@ const result = await redis.type("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -88,9 +88,9 @@ const result = await client.type("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -101,9 +101,9 @@ result = client.type("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -130,9 +130,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -145,9 +145,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -163,6 +163,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/generic/unlink.mdx b/redis/commands/generic/unlink.mdx
index 9940c31db..f06b620fe 100644
--- a/redis/commands/generic/unlink.mdx
+++ b/redis/commands/generic/unlink.mdx
@@ -36,9 +36,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -48,9 +48,9 @@ const redis = Redis.fromEnv();
 await redis.unlink("key1", "key2");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -60,9 +60,9 @@ result = redis.unlink("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -72,9 +72,9 @@ const result = await redis.unlink("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -86,9 +86,9 @@ const result = await client.unlink("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -99,9 +99,9 @@ result = client.unlink("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -128,9 +128,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -143,9 +143,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -161,6 +161,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/generic/wait.mdx b/redis/commands/generic/wait.mdx
index 0268d5552..a3a272f5d 100644
--- a/redis/commands/generic/wait.mdx
+++ b/redis/commands/generic/wait.mdx
@@ -46,25 +46,25 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 <Note>
   This command is not supported yet in `upstash_redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -74,9 +74,9 @@ const result = await redis.wait("1", "1000");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -88,9 +88,9 @@ const result = await client.wait(1, 1000);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -101,9 +101,9 @@ result = client.wait("1", "1000")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -131,9 +131,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -146,9 +146,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -165,6 +165,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/generic/waitaof.mdx b/redis/commands/generic/waitaof.mdx
index 29f60092e..c7a1cdbaa 100644
--- a/redis/commands/generic/waitaof.mdx
+++ b/redis/commands/generic/waitaof.mdx
@@ -45,25 +45,25 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 <Note>
   This command is not supported yet in `upstash_redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -73,9 +73,9 @@ const result = await redis.call("WAITAOF", "1", "1", "1000");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -87,9 +87,9 @@ const result = await client.sendCommand(["WAITAOF", "1", "1", "1000"]);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -100,9 +100,9 @@ result = client.waitaof("1", "1", "1000")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -130,9 +130,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -145,9 +145,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -165,6 +165,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/geo/geoadd.mdx b/redis/commands/geo/geoadd.mdx
index 718b23869..9f9852fc2 100644
--- a/redis/commands/geo/geoadd.mdx
+++ b/redis/commands/geo/geoadd.mdx
@@ -49,9 +49,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -65,9 +65,9 @@ const result = await redis.geoadd("my-key", {
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -77,9 +77,9 @@ result = redis.geoadd("my-key", (29.0, 41.0, "member"))
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -89,9 +89,9 @@ const result = await redis.geoadd("my-key", "29.0", "41.0", "member");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -103,9 +103,9 @@ const result = await client.geoAdd("my-key", { longitude: 29, latitude: 41, memb
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -116,9 +116,9 @@ result = client.geoadd("my-key", (29.0, 41.0, "member"))
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -145,9 +145,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -160,9 +160,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -178,6 +178,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/geo/geodist.mdx b/redis/commands/geo/geodist.mdx
index cfeef4614..b33db1d4f 100644
--- a/redis/commands/geo/geodist.mdx
+++ b/redis/commands/geo/geodist.mdx
@@ -43,9 +43,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -55,9 +55,9 @@ const result = await redis.geodist("my-key", "member1", "member2");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -67,9 +67,9 @@ result = redis.geodist("my-key", "member1", "member2")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -79,9 +79,9 @@ const result = await redis.geodist("my-key", "member1", "member2");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -93,9 +93,9 @@ const result = await client.geoDist("my-key", "member1", "member2");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -106,9 +106,9 @@ result = client.geodist("my-key", "member1", "member2")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -135,9 +135,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -150,9 +150,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::geo::Unit;
@@ -169,6 +169,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/geo/geohash.mdx b/redis/commands/geo/geohash.mdx
index 7a9acf96f..701053fd1 100644
--- a/redis/commands/geo/geohash.mdx
+++ b/redis/commands/geo/geohash.mdx
@@ -37,9 +37,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -49,9 +49,9 @@ const result = await redis.geohash("my-key", "member");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -61,9 +61,9 @@ result = redis.geohash("my-key", "member")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -73,9 +73,9 @@ const result = await redis.geohash("my-key", "member");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -87,9 +87,9 @@ const result = await client.geoHash("my-key", "member");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -100,9 +100,9 @@ result = client.geohash("my-key", "member")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -129,9 +129,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -144,9 +144,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -162,6 +162,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/geo/geopos.mdx b/redis/commands/geo/geopos.mdx
index b7d4fabaf..0e2d4dcca 100644
--- a/redis/commands/geo/geopos.mdx
+++ b/redis/commands/geo/geopos.mdx
@@ -37,9 +37,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -49,9 +49,9 @@ const result = await redis.geopos("my-key", "member");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -61,9 +61,9 @@ result = redis.geopos("my-key", "member")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -73,9 +73,9 @@ const result = await redis.geopos("my-key", "member");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -87,9 +87,9 @@ const result = await client.geoPos("my-key", "member");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -100,9 +100,9 @@ result = client.geopos("my-key", "member")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -129,9 +129,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -144,9 +144,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -162,6 +162,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/geo/georadius-ro.mdx b/redis/commands/geo/georadius-ro.mdx
index 242b11c53..55c288462 100644
--- a/redis/commands/geo/georadius-ro.mdx
+++ b/redis/commands/geo/georadius-ro.mdx
@@ -56,17 +56,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -76,9 +76,9 @@ result = redis.georadius_ro("my-key", 29.0, 41.0, 1.5, "M")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -88,9 +88,9 @@ const result = await redis.georadius_ro("my-key", "29.0", "41.0", "1.5", "m");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -102,9 +102,9 @@ const result = await client.geoRadiusRo("my-key", { longitude: 29, latitude: 41
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -115,9 +115,9 @@ result = client.execute_command("GEORADIUS_RO", "my-key", "29.0", "41.0", "1.5",
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -144,9 +144,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -159,9 +159,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -181,6 +181,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/geo/georadius.mdx b/redis/commands/geo/georadius.mdx
index 4e9d3eb04..d00a83a47 100644
--- a/redis/commands/geo/georadius.mdx
+++ b/redis/commands/geo/georadius.mdx
@@ -60,17 +60,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -80,9 +80,9 @@ result = redis.georadius("my-key", 29.0, 41.0, 1.5, "M")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -92,9 +92,9 @@ const result = await redis.georadius("my-key", "29.0", "41.0", "1.5", "m");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -106,9 +106,9 @@ const result = await client.geoRadius("my-key", { longitude: 29, latitude: 41 },
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -119,9 +119,9 @@ result = client.georadius("my-key", 29.0, 41.0, 1.5, "m")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -148,9 +148,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -163,9 +163,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::geo::{RadiusOptions, Unit};
@@ -189,6 +189,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/geo/georadiusbymember-ro.mdx b/redis/commands/geo/georadiusbymember-ro.mdx
index 12e8e29c2..a78a4ab7e 100644
--- a/redis/commands/geo/georadiusbymember-ro.mdx
+++ b/redis/commands/geo/georadiusbymember-ro.mdx
@@ -53,17 +53,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -73,9 +73,9 @@ result = redis.georadiusbymember_ro("my-key", "member", 1.5, "M")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -85,9 +85,9 @@ const result = await redis.georadiusbymember_ro("my-key", "member", "1.5", "m");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -99,9 +99,9 @@ const result = await client.geoRadiusByMemberRo("my-key", "member", 1.5, "m");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -112,9 +112,9 @@ result = client.execute_command("GEORADIUSBYMEMBER_RO", "my-key", "member", "1.5
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -141,9 +141,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -156,9 +156,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -177,6 +177,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/geo/georadiusbymember.mdx b/redis/commands/geo/georadiusbymember.mdx
index 78ce11470..d9125cadb 100644
--- a/redis/commands/geo/georadiusbymember.mdx
+++ b/redis/commands/geo/georadiusbymember.mdx
@@ -57,17 +57,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -77,9 +77,9 @@ result = redis.georadiusbymember("my-key", "member", 1.5, "M")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -89,9 +89,9 @@ const result = await redis.georadiusbymember("my-key", "member", "1.5", "m");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -103,9 +103,9 @@ const result = await client.geoRadiusByMember("my-key", "member", 1.5, "m");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -116,9 +116,9 @@ result = client.georadiusbymember("my-key", "member", 1.5, "m")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -145,9 +145,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -160,9 +160,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::geo::{RadiusOptions, Unit};
@@ -185,6 +185,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/geo/geosearch.mdx b/redis/commands/geo/geosearch.mdx
index a74b3d3a8..b77e02fb8 100644
--- a/redis/commands/geo/geosearch.mdx
+++ b/redis/commands/geo/geosearch.mdx
@@ -55,9 +55,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -72,9 +72,9 @@ const result = await redis.geosearch(
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -84,9 +84,9 @@ result = redis.geosearch("my-key", member="member", radius=1.5, unit="M")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -96,9 +96,9 @@ const result = await redis.geosearch("my-key", "FROMMEMBER", "member", "BYRADIUS
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -110,9 +110,9 @@ const result = await client.geoSearch("my-key", "member", { radius: 1.5, unit: "
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -123,9 +123,9 @@ result = client.geosearch("my-key", member="member", radius=1.5, unit="m")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -152,9 +152,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -167,9 +167,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -188,6 +188,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/geo/geosearchstore.mdx b/redis/commands/geo/geosearchstore.mdx
index 8bf4189b7..852f1580e 100644
--- a/redis/commands/geo/geosearchstore.mdx
+++ b/redis/commands/geo/geosearchstore.mdx
@@ -50,9 +50,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -68,9 +68,9 @@ const result = await redis.geosearchstore(
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -80,9 +80,9 @@ result = redis.geosearchstore("destination-key", "source-key", member="member",
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -92,9 +92,9 @@ const result = await redis.geosearchstore("destination-key", "source-key", "FROM
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -106,9 +106,9 @@ const result = await client.geoSearchStore("destination-key", "source-key", "mem
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -119,9 +119,9 @@ result = client.geosearchstore("destination-key", "source-key", member="member",
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -148,9 +148,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -163,9 +163,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -185,6 +185,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/hash/hdel.mdx b/redis/commands/hash/hdel.mdx
index a139d4c27..ac2b8ee28 100644
--- a/redis/commands/hash/hdel.mdx
+++ b/redis/commands/hash/hdel.mdx
@@ -37,9 +37,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -50,9 +50,9 @@ await redis.hdel(key, 'field1', 'field2');
 // returns 5
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -62,9 +62,9 @@ result = redis.hdel("my-key", "field")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -74,9 +74,9 @@ const result = await redis.hdel("my-key", "field");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -88,9 +88,9 @@ const result = await client.hDel("my-key", "field");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -101,9 +101,9 @@ result = client.hdel("my-key", "field")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -130,9 +130,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -145,9 +145,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -163,6 +163,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/hash/hexists.mdx b/redis/commands/hash/hexists.mdx
index 850850b04..1f72786e5 100644
--- a/redis/commands/hash/hexists.mdx
+++ b/redis/commands/hash/hexists.mdx
@@ -37,9 +37,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -52,9 +52,9 @@ const exists = await redis.hexists("key", "field");
 console.log(exists); // 1
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -64,9 +64,9 @@ result = redis.hexists("my-key", "field")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -76,9 +76,9 @@ const result = await redis.hexists("my-key", "field");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -90,9 +90,9 @@ const result = await client.hExists("my-key", "field");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -103,9 +103,9 @@ result = client.hexists("my-key", "field")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -132,9 +132,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -147,9 +147,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -165,6 +165,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/hash/hexpire.mdx b/redis/commands/hash/hexpire.mdx
index 72120ad7a..d96e2f993 100644
--- a/redis/commands/hash/hexpire.mdx
+++ b/redis/commands/hash/hexpire.mdx
@@ -50,9 +50,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -65,9 +65,9 @@ const expirationSet = await redis.hexpire("my-key", "my-field", 1);
 console.log(expirationSet); // 1
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -77,9 +77,9 @@ result = redis.hexpire("my-key", "field", 1000)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -89,9 +89,9 @@ const result = await redis.hexpire("my-key", "1000", "FIELDS", "1", "field");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -103,9 +103,9 @@ const result = await client.hExpire("my-key", "field", 1000);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -116,9 +116,9 @@ result = client.hexpire("my-key", 1000, "field")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -145,9 +145,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -160,9 +160,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -178,6 +178,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/hash/hexpireat.mdx b/redis/commands/hash/hexpireat.mdx
index b24b34e08..131e83032 100644
--- a/redis/commands/hash/hexpireat.mdx
+++ b/redis/commands/hash/hexpireat.mdx
@@ -50,9 +50,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -65,9 +65,9 @@ const expirationSet = await redis.hexpireat("my-key", "my-field", Math.floor(Dat
 console.log(expirationSet); // [1]
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -77,9 +77,9 @@ result = redis.hexpireat("my-key", "field", 1735689600)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -89,9 +89,9 @@ const result = await redis.hexpireat("my-key", "1735689600", "FIELDS", "1", "fie
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -103,9 +103,9 @@ const result = await client.hExpireAt("my-key", "field", 1735689600);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -116,9 +116,9 @@ result = client.hexpireat("my-key", 1735689600, "field")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -145,9 +145,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -160,9 +160,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -178,6 +178,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/hash/hexpiretime.mdx b/redis/commands/hash/hexpiretime.mdx
index 3e2986dd1..25aa7a707 100644
--- a/redis/commands/hash/hexpiretime.mdx
+++ b/redis/commands/hash/hexpiretime.mdx
@@ -41,9 +41,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -57,9 +57,9 @@ const expireTime = await redis.hexpiretime("my-key", "my-field");
 console.log(expireTime); // e.g., [1697059200]
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -69,9 +69,9 @@ result = redis.hexpiretime("my-key", "field")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -81,9 +81,9 @@ const result = await redis.hexpiretime("my-key", "FIELDS", "1", "field");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -95,9 +95,9 @@ const result = await client.hExpireTime("my-key", "field");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -108,9 +108,9 @@ result = client.hexpiretime("my-key", "field")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -137,9 +137,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -151,9 +151,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -169,6 +169,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/hash/hget.mdx b/redis/commands/hash/hget.mdx
index 23ead3798..e67f3de6f 100644
--- a/redis/commands/hash/hget.mdx
+++ b/redis/commands/hash/hget.mdx
@@ -37,9 +37,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -51,9 +51,9 @@ const field = await redis.hget("key", "field");
 console.log(field); // "value"
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -63,9 +63,9 @@ result = redis.hget("my-key", "field")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -75,9 +75,9 @@ const result = await redis.hget("my-key", "field");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -89,9 +89,9 @@ const result = await client.hGet("my-key", "field");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -102,9 +102,9 @@ result = client.hget("my-key", "field")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -131,9 +131,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -146,9 +146,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -164,6 +164,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/hash/hgetall.mdx b/redis/commands/hash/hgetall.mdx
index d61f30d4c..59d65ba31 100644
--- a/redis/commands/hash/hgetall.mdx
+++ b/redis/commands/hash/hgetall.mdx
@@ -42,9 +42,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -59,9 +59,9 @@ const hash = await redis.hgetall("key");
 console.log(hash); // { field1: "value1", field2: "value2" }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -71,9 +71,9 @@ result = redis.hgetall("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -83,9 +83,9 @@ const result = await redis.hgetall("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -97,9 +97,9 @@ const result = await client.hGetAll("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -110,9 +110,9 @@ result = client.hgetall("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -139,9 +139,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -154,9 +154,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -172,6 +172,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/hash/hgetdel.mdx b/redis/commands/hash/hgetdel.mdx
index acdc944da..25e31741f 100644
--- a/redis/commands/hash/hgetdel.mdx
+++ b/redis/commands/hash/hgetdel.mdx
@@ -39,9 +39,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -60,9 +60,9 @@ const name = await redis.hget("user:123", "name");
 console.log(name); // null
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -72,9 +72,9 @@ result = redis.hgetdel("my-key", "field")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -84,9 +84,9 @@ const result = await redis.hgetdel("my-key", "FIELDS", "1", "field");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -98,9 +98,9 @@ const result = await client.hGetDel("my-key", "field");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -111,9 +111,9 @@ result = client.hgetdel("my-key", "field")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -140,9 +140,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -155,9 +155,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -173,6 +173,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/hash/hgetex.mdx b/redis/commands/hash/hgetex.mdx
index 882255eea..9d19a8397 100644
--- a/redis/commands/hash/hgetex.mdx
+++ b/redis/commands/hash/hgetex.mdx
@@ -43,9 +43,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -59,9 +59,9 @@ const result = await redis.hgetex("user:123", { ex: 60 }, "name", "email");
 console.log(result); // { name: "John", email: "john@example.com" }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -71,9 +71,9 @@ result = redis.hgetex("my-key", "field")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -83,9 +83,9 @@ const result = await redis.hgetex("my-key", "FIELDS", "1", "field");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -97,9 +97,9 @@ const result = await client.hGetEx("my-key", "field");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -110,9 +110,9 @@ result = client.hgetex("my-key", "field")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -139,9 +139,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -154,9 +154,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -172,6 +172,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/hash/hincrby.mdx b/redis/commands/hash/hincrby.mdx
index 37eb487b2..37045a8c5 100644
--- a/redis/commands/hash/hincrby.mdx
+++ b/redis/commands/hash/hincrby.mdx
@@ -40,9 +40,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -56,9 +56,9 @@ const after = await redis.hincrby("key", "field", 2);
 console.log(after); // 22
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -68,9 +68,9 @@ result = redis.hincrby("my-key", "field", 1)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -80,9 +80,9 @@ const result = await redis.hincrby("my-key", "field", "1");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -94,9 +94,9 @@ const result = await client.hIncrBy("my-key", "field", 1);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -107,9 +107,9 @@ result = client.hincrby("my-key", "field", 1)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -136,9 +136,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -151,9 +151,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -169,6 +169,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/hash/hincrbyfloat.mdx b/redis/commands/hash/hincrbyfloat.mdx
index ff12110a4..7a0f33901 100644
--- a/redis/commands/hash/hincrbyfloat.mdx
+++ b/redis/commands/hash/hincrbyfloat.mdx
@@ -44,9 +44,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -60,9 +60,9 @@ const after = await redis.hincrby("key", "field", 2.5);
 console.log(after); // 22.5
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -72,9 +72,9 @@ result = redis.hincrbyfloat("my-key", "field", 1.5)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -84,9 +84,9 @@ const result = await redis.hincrbyfloat("my-key", "field", "1.5");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -98,9 +98,9 @@ const result = await client.hIncrByFloat("my-key", "field", 1.5);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -111,9 +111,9 @@ result = client.hincrbyfloat("my-key", "field", 1.5)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -140,9 +140,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -155,9 +155,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -173,6 +173,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/hash/hkeys.mdx b/redis/commands/hash/hkeys.mdx
index 1bbd689d5..ab3b2aede 100644
--- a/redis/commands/hash/hkeys.mdx
+++ b/redis/commands/hash/hkeys.mdx
@@ -36,9 +36,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -53,9 +53,9 @@ const fields = await redis.hkeys("key");
 console.log(fields); // ["id", "username"]
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -65,9 +65,9 @@ result = redis.hkeys("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -77,9 +77,9 @@ const result = await redis.hkeys("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -91,9 +91,9 @@ const result = await client.hKeys("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -104,9 +104,9 @@ result = client.hkeys("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -133,9 +133,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -148,9 +148,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -166,6 +166,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/hash/hlen.mdx b/redis/commands/hash/hlen.mdx
index 7bb6b2f58..46f321cc6 100644
--- a/redis/commands/hash/hlen.mdx
+++ b/redis/commands/hash/hlen.mdx
@@ -36,9 +36,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -53,9 +53,9 @@ const fields = await redis.hlen("key");
 console.log(fields); // 2
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -65,9 +65,9 @@ result = redis.hlen("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -77,9 +77,9 @@ const result = await redis.hlen("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -91,9 +91,9 @@ const result = await client.hLen("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -104,9 +104,9 @@ result = client.hlen("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -133,9 +133,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -148,9 +148,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -166,6 +166,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/hash/hmget.mdx b/redis/commands/hash/hmget.mdx
index 5fef1c4b4..d38002c64 100644
--- a/redis/commands/hash/hmget.mdx
+++ b/redis/commands/hash/hmget.mdx
@@ -39,9 +39,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -57,9 +57,9 @@ const fields = await redis.hmget("key", "username", "name");
 console.log(fields); // { username: "chronark", name: "andreas" }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -69,9 +69,9 @@ result = redis.hmget("my-key", "field")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -81,9 +81,9 @@ const result = await redis.hmget("my-key", "field");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -95,9 +95,9 @@ const result = await client.hmGet("my-key", "field");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -108,9 +108,9 @@ result = client.hmget("my-key", ["field"])
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -137,9 +137,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -152,9 +152,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -170,6 +170,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/hash/hmset.mdx b/redis/commands/hash/hmset.mdx
index c243e3d1c..2f9daebe4 100644
--- a/redis/commands/hash/hmset.mdx
+++ b/redis/commands/hash/hmset.mdx
@@ -41,9 +41,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -53,9 +53,9 @@ const result = await redis.hmset("my-key", { field: "value" });
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -65,9 +65,9 @@ result = redis.hmset("my-key", {"field": "value"})
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -77,9 +77,9 @@ const result = await redis.hmset("my-key", "field", "value");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -91,9 +91,9 @@ const result = await client.hSet("my-key", { field: "value" });
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -104,9 +104,9 @@ result = client.hset("my-key", mapping={"field": "value"})
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -133,9 +133,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -148,9 +148,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -166,6 +166,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/hash/hpersist.mdx b/redis/commands/hash/hpersist.mdx
index dbc1e1b45..bcff168b0 100644
--- a/redis/commands/hash/hpersist.mdx
+++ b/redis/commands/hash/hpersist.mdx
@@ -39,9 +39,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -56,9 +56,9 @@ const expirationRemoved = await redis.hpersist("my-key", "my-field");
 console.log(expirationRemoved); // [1]
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -68,9 +68,9 @@ result = redis.hpersist("my-key", "field")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -80,9 +80,9 @@ const result = await redis.hpersist("my-key", "FIELDS", "1", "field");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -94,9 +94,9 @@ const result = await client.hPersist("my-key", "field");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -107,9 +107,9 @@ result = client.hpersist("my-key", "field")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -136,9 +136,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -151,9 +151,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -169,6 +169,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/hash/hpexpire.mdx b/redis/commands/hash/hpexpire.mdx
index a8ff75a6d..5a71ac953 100644
--- a/redis/commands/hash/hpexpire.mdx
+++ b/redis/commands/hash/hpexpire.mdx
@@ -48,9 +48,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -63,9 +63,9 @@ const expirationSet = await redis.hpexpire("my-key", "my-field", 1000);
 console.log(expirationSet); // [1]
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -75,9 +75,9 @@ result = redis.hpexpire("my-key", "field", 1000)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -87,9 +87,9 @@ const result = await redis.hpexpire("my-key", "1000", "FIELDS", "1", "field");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -101,9 +101,9 @@ const result = await client.hpExpire("my-key", "field", 1000);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -114,9 +114,9 @@ result = client.hpexpire("my-key", 1000, "field")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -143,9 +143,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -158,9 +158,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -176,6 +176,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/hash/hpexpireat.mdx b/redis/commands/hash/hpexpireat.mdx
index 14181f602..dffbaf483 100644
--- a/redis/commands/hash/hpexpireat.mdx
+++ b/redis/commands/hash/hpexpireat.mdx
@@ -48,9 +48,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -63,9 +63,9 @@ const expirationSet = await redis.hpexpireat("my-key", "my-field", Date.now() +
 console.log(expirationSet); // [1]
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -75,9 +75,9 @@ result = redis.hpexpireat("my-key", "field", 1735689600)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -87,9 +87,9 @@ const result = await redis.hpexpireat("my-key", "1735689600", "FIELDS", "1", "fi
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -101,9 +101,9 @@ const result = await client.hpExpireAt("my-key", "field", 1735689600);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -114,9 +114,9 @@ result = client.hpexpireat("my-key", 1735689600, "field")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -143,9 +143,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -158,9 +158,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -176,6 +176,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/hash/hpexpiretime.mdx b/redis/commands/hash/hpexpiretime.mdx
index 6583633d8..7a64e0616 100644
--- a/redis/commands/hash/hpexpiretime.mdx
+++ b/redis/commands/hash/hpexpiretime.mdx
@@ -41,9 +41,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -57,9 +57,9 @@ const expireTime = await redis.hpexpiretime("my-key", "my-field");
 console.log(expireTime); // e.g., 1697059200000
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -69,9 +69,9 @@ result = redis.hpexpiretime("my-key", "field")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -81,9 +81,9 @@ const result = await redis.hpexpiretime("my-key", "FIELDS", "1", "field");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -95,9 +95,9 @@ const result = await client.hpExpireTime("my-key", "field");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -108,9 +108,9 @@ result = client.hpexpiretime("my-key", "field")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -137,9 +137,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -152,9 +152,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -170,6 +170,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/hash/hpttl.mdx b/redis/commands/hash/hpttl.mdx
index 4b5337c3a..f4bba8a36 100644
--- a/redis/commands/hash/hpttl.mdx
+++ b/redis/commands/hash/hpttl.mdx
@@ -41,9 +41,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -57,9 +57,9 @@ const ttl = await redis.hpttl("my-key", "my-field");
 console.log(ttl); // e.g., [950]
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -69,9 +69,9 @@ result = redis.hpttl("my-key", "field")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -81,9 +81,9 @@ const result = await redis.hpttl("my-key", "FIELDS", "1", "field");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -95,9 +95,9 @@ const result = await client.hpTTL("my-key", "field");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -108,9 +108,9 @@ result = client.hpttl("my-key", "field")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -137,9 +137,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -152,9 +152,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -170,6 +170,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/hash/hrandfield.mdx b/redis/commands/hash/hrandfield.mdx
index 60a347db1..f319bcfac 100644
--- a/redis/commands/hash/hrandfield.mdx
+++ b/redis/commands/hash/hrandfield.mdx
@@ -43,9 +43,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -61,9 +61,9 @@ const randomField = await redis.hrandfield("key");
 console.log(randomField); // one of "id", "username" or  "name"
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -73,9 +73,9 @@ result = redis.hrandfield("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -85,9 +85,9 @@ const result = await redis.hrandfield("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -99,9 +99,9 @@ const result = await client.hRandField("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -112,9 +112,9 @@ result = client.hrandfield("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -141,9 +141,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -156,9 +156,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -174,6 +174,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/hash/hscan.mdx b/redis/commands/hash/hscan.mdx
index f9e7db835..49cdf4258 100644
--- a/redis/commands/hash/hscan.mdx
+++ b/redis/commands/hash/hscan.mdx
@@ -47,9 +47,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -66,9 +66,9 @@ console.log(newCursor); // likely `0` since this is a very small hash
 console.log(fields); // ["id", 1, "username", "chronark", "name", "andreas"]
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -78,9 +78,9 @@ result = redis.hscan("my-key", 0)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -90,9 +90,9 @@ const result = await redis.hscan("my-key", "0");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -104,9 +104,9 @@ const result = await client.hScan("my-key", "0");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -117,9 +117,9 @@ result = client.hscan("my-key", 0)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -146,9 +146,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -161,9 +161,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -181,6 +181,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/hash/hset.mdx b/redis/commands/hash/hset.mdx
index 31f8ca13c..b685da061 100644
--- a/redis/commands/hash/hset.mdx
+++ b/redis/commands/hash/hset.mdx
@@ -39,9 +39,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -55,9 +55,9 @@ await redis.hset("key", {
   });
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -67,9 +67,9 @@ result = redis.hset("my-key", "field", "value")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -79,9 +79,9 @@ const result = await redis.hset("my-key", "field", "value");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -93,9 +93,9 @@ const result = await client.hSet("my-key", "field", "value");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -106,9 +106,9 @@ result = client.hset("my-key", "field", "value")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -135,9 +135,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -150,9 +150,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -168,6 +168,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/hash/hsetex.mdx b/redis/commands/hash/hsetex.mdx
index 22e22b99d..e6d7d46e2 100644
--- a/redis/commands/hash/hsetex.mdx
+++ b/redis/commands/hash/hsetex.mdx
@@ -45,9 +45,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -61,9 +61,9 @@ await redis.hsetex("user:123", { expiration: { ex: 3600 } }, {
 });
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -73,9 +73,9 @@ result = redis.hsetex("my-key", field="field", value="value")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -85,9 +85,9 @@ const result = await redis.hsetex("my-key", "FIELDS", "1", "field", "value");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -99,9 +99,9 @@ const result = await client.hSetEx("my-key", { field: "value" });
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -112,9 +112,9 @@ result = client.hsetex("my-key", mapping={"field": "value"})
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -141,9 +141,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -156,9 +156,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::{HashFieldExpirationOptions, TypedCommands};
@@ -178,6 +178,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/hash/hsetnx.mdx b/redis/commands/hash/hsetnx.mdx
index c55a52492..39e6d1540 100644
--- a/redis/commands/hash/hsetnx.mdx
+++ b/redis/commands/hash/hsetnx.mdx
@@ -38,9 +38,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -50,9 +50,9 @@ const redis = Redis.fromEnv();
 await redis.hsetnx("key", "id", 1)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -62,9 +62,9 @@ result = redis.hsetnx("my-key", "field", "value")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -74,9 +74,9 @@ const result = await redis.hsetnx("my-key", "field", "value");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -88,9 +88,9 @@ const result = await client.hSetNX("my-key", "field", "value");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -101,9 +101,9 @@ result = client.hsetnx("my-key", "field", "value")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -130,9 +130,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -145,9 +145,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -163,6 +163,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/hash/hstrlen.mdx b/redis/commands/hash/hstrlen.mdx
index 3f3dfc4f2..73b81f5f7 100644
--- a/redis/commands/hash/hstrlen.mdx
+++ b/redis/commands/hash/hstrlen.mdx
@@ -37,9 +37,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -49,9 +49,9 @@ const redis = Redis.fromEnv();
 const length = await redis.hstrlen("key", "field")
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -61,9 +61,9 @@ result = redis.hstrlen("my-key", "field")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -73,9 +73,9 @@ const result = await redis.hstrlen("my-key", "field");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -87,9 +87,9 @@ const result = await client.hStrLen("my-key", "field");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -100,9 +100,9 @@ result = client.hstrlen("my-key", "field")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -129,9 +129,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -144,9 +144,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -163,6 +163,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/hash/httl.mdx b/redis/commands/hash/httl.mdx
index a67b79d5c..21f0c23ae 100644
--- a/redis/commands/hash/httl.mdx
+++ b/redis/commands/hash/httl.mdx
@@ -41,9 +41,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -57,9 +57,9 @@ const ttl = await redis.httl("my-key", "my-field");
 console.log(ttl); // e.g., [9]
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -69,9 +69,9 @@ result = redis.httl("my-key", "field")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -81,9 +81,9 @@ const result = await redis.httl("my-key", "FIELDS", "1", "field");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -95,9 +95,9 @@ const result = await client.hTTL("my-key", "field");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -108,9 +108,9 @@ result = client.httl("my-key", "field")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -137,9 +137,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -152,9 +152,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -170,6 +170,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/hash/hvals.mdx b/redis/commands/hash/hvals.mdx
index 685eeb6db..962b4981e 100644
--- a/redis/commands/hash/hvals.mdx
+++ b/redis/commands/hash/hvals.mdx
@@ -36,9 +36,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -53,9 +53,9 @@ const values = await redis.hvals("key")
 console.log(values) // ["Hello", "World"]
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -65,9 +65,9 @@ result = redis.hvals("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -77,9 +77,9 @@ const result = await redis.hvals("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -91,9 +91,9 @@ const result = await client.hVals("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -104,9 +104,9 @@ result = client.hvals("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -133,9 +133,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -148,9 +148,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -166,6 +166,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/hyperloglog/pfadd.mdx b/redis/commands/hyperloglog/pfadd.mdx
index 0044bda1f..113a4d5c1 100644
--- a/redis/commands/hyperloglog/pfadd.mdx
+++ b/redis/commands/hyperloglog/pfadd.mdx
@@ -39,9 +39,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -51,9 +51,9 @@ const result = await redis.pfadd("my-key", "element");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -63,9 +63,9 @@ result = redis.pfadd("my-key", "member")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -75,9 +75,9 @@ const result = await redis.pfadd("my-key", "element");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -89,9 +89,9 @@ const result = await client.pfAdd("my-key", "element");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -102,9 +102,9 @@ result = client.pfadd("my-key", "member")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -131,9 +131,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -146,9 +146,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -164,6 +164,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/hyperloglog/pfcount.mdx b/redis/commands/hyperloglog/pfcount.mdx
index e9c761ac7..5c6efcf50 100644
--- a/redis/commands/hyperloglog/pfcount.mdx
+++ b/redis/commands/hyperloglog/pfcount.mdx
@@ -38,9 +38,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -50,9 +50,9 @@ const result = await redis.pfcount("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -62,9 +62,9 @@ result = redis.pfcount("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -74,9 +74,9 @@ const result = await redis.pfcount("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -88,9 +88,9 @@ const result = await client.pfCount("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -101,9 +101,9 @@ result = client.pfcount("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -130,9 +130,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -145,9 +145,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -163,6 +163,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/hyperloglog/pfmerge.mdx b/redis/commands/hyperloglog/pfmerge.mdx
index 2c53d3ae9..13d78860e 100644
--- a/redis/commands/hyperloglog/pfmerge.mdx
+++ b/redis/commands/hyperloglog/pfmerge.mdx
@@ -39,9 +39,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -51,9 +51,9 @@ const result = await redis.pfmerge("destination-key", "source-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -63,9 +63,9 @@ result = redis.pfmerge("destination-key", "source-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -75,9 +75,9 @@ const result = await redis.pfmerge("destination-key", "source-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -89,9 +89,9 @@ const result = await client.pfMerge("destination-key", "source-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -102,9 +102,9 @@ result = client.pfmerge("destination-key", "source-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -131,9 +131,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -146,9 +146,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -164,6 +164,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/json/json-arrappend.mdx b/redis/commands/json/json-arrappend.mdx
index 5b15695f6..0b2bcbfc3 100644
--- a/redis/commands/json/json-arrappend.mdx
+++ b/redis/commands/json/json-arrappend.mdx
@@ -43,9 +43,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -55,9 +55,9 @@ const redis = Redis.fromEnv();
 await redis.json.arrappend("key", "$.path.to.array", "a");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -67,9 +67,9 @@ result = redis.json().arrappend("profile", "$.tags", "new")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -79,9 +79,9 @@ const result = await redis.call("JSON.ARRAPPEND", "profile", "$.tags", "\"new\""
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -93,9 +93,9 @@ const result = await client.json.arrAppend("profile", "$.tags", "new");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -106,9 +106,9 @@ result = client.json().arrappend("profile", "$.tags", "new")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -135,9 +135,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -150,9 +150,9 @@ try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::JsonCommands;
@@ -168,6 +168,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/json/json-arrindex.mdx b/redis/commands/json/json-arrindex.mdx
index 9bd1fdeea..0dad49384 100644
--- a/redis/commands/json/json-arrindex.mdx
+++ b/redis/commands/json/json-arrindex.mdx
@@ -45,9 +45,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -57,9 +57,9 @@ const redis = Redis.fromEnv();
 const index = await redis.json.arrindex("key", "$.path.to.array", "a");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -69,9 +69,9 @@ result = redis.json().arrindex("profile", "$.tags", "new")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -81,9 +81,9 @@ const result = await redis.call("JSON.ARRINDEX", "profile", "$.tags", "\"new\"")
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -95,9 +95,9 @@ const result = await client.json.arrIndex("profile", "$.tags", "new");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -108,9 +108,9 @@ result = client.json().arrindex("profile", "$.tags", "new")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -137,9 +137,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -152,9 +152,9 @@ try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::JsonCommands;
@@ -170,6 +170,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/json/json-arrinsert.mdx b/redis/commands/json/json-arrinsert.mdx
index 5818e6acd..5e2c48cb9 100644
--- a/redis/commands/json/json-arrinsert.mdx
+++ b/redis/commands/json/json-arrinsert.mdx
@@ -44,9 +44,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -56,9 +56,9 @@ const redis = Redis.fromEnv();
 const length = await redis.json.arrinsert("key", "$.path.to.array", 2, "a", "b");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -68,9 +68,9 @@ result = redis.json().arrinsert("profile", "$.tags", 0, "first")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -80,9 +80,9 @@ const result = await redis.call("JSON.ARRINSERT", "profile", "$.tags", "0", "\"f
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -94,9 +94,9 @@ const result = await client.json.arrInsert("profile", "$.tags", 0, "first");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -107,9 +107,9 @@ result = client.json().arrinsert("profile", "$.tags", 0, "first")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -136,9 +136,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -151,9 +151,9 @@ try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::JsonCommands;
@@ -169,6 +169,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/json/json-arrlen.mdx b/redis/commands/json/json-arrlen.mdx
index 623fc9d80..07c13a3e8 100644
--- a/redis/commands/json/json-arrlen.mdx
+++ b/redis/commands/json/json-arrlen.mdx
@@ -42,9 +42,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -54,9 +54,9 @@ const redis = Redis.fromEnv();
 const length = await redis.json.arrlen("key", "$.path.to.array");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -66,9 +66,9 @@ result = redis.json().arrlen("profile", "$.tags")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -78,9 +78,9 @@ const result = await redis.call("JSON.ARRLEN", "profile", "$.tags");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -92,9 +92,9 @@ const result = await client.json.arrLen("profile", { path: "$.tags" });
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -105,9 +105,9 @@ result = client.json().arrlen("profile", "$.tags")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -134,9 +134,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -149,9 +149,9 @@ try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::JsonCommands;
@@ -167,6 +167,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/json/json-arrpop.mdx b/redis/commands/json/json-arrpop.mdx
index ec88ef6c5..f9687b989 100644
--- a/redis/commands/json/json-arrpop.mdx
+++ b/redis/commands/json/json-arrpop.mdx
@@ -45,9 +45,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -57,9 +57,9 @@ const redis = Redis.fromEnv();
 const element = await redis.json.arrpop("key", "$.path.to.array");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -69,9 +69,9 @@ result = redis.json().arrpop("profile", "$.tags", -1)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -81,9 +81,9 @@ const result = await redis.call("JSON.ARRPOP", "profile", "$.tags", "-1");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -95,9 +95,9 @@ const result = await client.json.arrPop("profile", { path: "$.tags", index: -1 }
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -108,9 +108,9 @@ result = client.json().arrpop("profile", "$.tags", -1)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -137,9 +137,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -152,9 +152,9 @@ try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::JsonCommands;
@@ -170,6 +170,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/json/json-arrtrim.mdx b/redis/commands/json/json-arrtrim.mdx
index 55c1d368d..7447ac017 100644
--- a/redis/commands/json/json-arrtrim.mdx
+++ b/redis/commands/json/json-arrtrim.mdx
@@ -46,9 +46,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -58,9 +58,9 @@ const redis = Redis.fromEnv();
 const length = await redis.json.arrtrim("key", "$.path.to.array", 2, 10);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -70,9 +70,9 @@ result = redis.json().arrtrim("profile", "$.tags", 0, 9)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -82,9 +82,9 @@ const result = await redis.call("JSON.ARRTRIM", "profile", "$.tags", "0", "9");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -96,9 +96,9 @@ const result = await client.json.arrTrim("profile", "$.tags", 0, 9);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -109,9 +109,9 @@ result = client.json().arrtrim("profile", "$.tags", 0, 9)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -138,9 +138,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -153,9 +153,9 @@ try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::JsonCommands;
@@ -171,6 +171,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/json/json-clear.mdx b/redis/commands/json/json-clear.mdx
index ebc018bdf..ed95f5b6a 100644
--- a/redis/commands/json/json-clear.mdx
+++ b/redis/commands/json/json-clear.mdx
@@ -44,9 +44,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -56,9 +56,9 @@ const redis = Redis.fromEnv();
 await redis.json.clear("key");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -68,9 +68,9 @@ result = redis.json().clear("profile", "$.stats")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -80,9 +80,9 @@ const result = await redis.call("JSON.CLEAR", "profile", "$.stats");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -94,9 +94,9 @@ const result = await client.json.clear("profile", { path: "$.stats" });
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -107,9 +107,9 @@ result = client.json().clear("profile", "$.stats")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -136,9 +136,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -151,9 +151,9 @@ try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::JsonCommands;
@@ -169,6 +169,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/json/json-debug.mdx b/redis/commands/json/json-debug.mdx
index 39f94ce78..f9f68de29 100644
--- a/redis/commands/json/json-debug.mdx
+++ b/redis/commands/json/json-debug.mdx
@@ -47,25 +47,25 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 <Note>
   This command is not supported yet in `upstash_redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -75,9 +75,9 @@ const result = await redis.call("JSON.DEBUG", "MEMORY", "profile", "$.stats");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -89,9 +89,9 @@ const result = await client.json.debugMemory("profile", { path: "$.stats" });
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -102,9 +102,9 @@ result = client.json().debug("MEMORY", "profile", "$.stats")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -131,9 +131,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -146,9 +146,9 @@ try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -166,6 +166,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/json/json-del.mdx b/redis/commands/json/json-del.mdx
index 0504d4638..33868ebf3 100644
--- a/redis/commands/json/json-del.mdx
+++ b/redis/commands/json/json-del.mdx
@@ -44,9 +44,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -56,9 +56,9 @@ const redis = Redis.fromEnv();
 await redis.json.del("key", "$.path.to.value");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -68,9 +68,9 @@ result = redis.json().delete("profile", "$.temporary")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -80,9 +80,9 @@ const result = await redis.call("JSON.DEL", "profile", "$.temporary");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -94,9 +94,9 @@ const result = await client.json.del("profile", { path: "$.temporary" });
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -107,9 +107,9 @@ result = client.json().delete("profile", "$.temporary")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -136,9 +136,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -151,9 +151,9 @@ try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::JsonCommands;
@@ -169,6 +169,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/json/json-forget.mdx b/redis/commands/json/json-forget.mdx
index 5d1b08e90..3332644e2 100644
--- a/redis/commands/json/json-forget.mdx
+++ b/redis/commands/json/json-forget.mdx
@@ -42,9 +42,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -54,9 +54,9 @@ const redis = Redis.fromEnv();
 await redis.json.forget("key", "$.path.to.value");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -66,9 +66,9 @@ result = redis.json().forget("profile", "$.temporary")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -78,9 +78,9 @@ const result = await redis.call("JSON.FORGET", "profile", "$.temporary");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -92,9 +92,9 @@ const result = await client.json.forget("profile", { path: "$.temporary" });
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -105,9 +105,9 @@ result = client.json().forget("profile", "$.temporary")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -134,9 +134,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -149,9 +149,9 @@ try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::JsonCommands;
@@ -167,6 +167,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/json/json-get.mdx b/redis/commands/json/json-get.mdx
index ca11b8271..d32521d80 100644
--- a/redis/commands/json/json-get.mdx
+++ b/redis/commands/json/json-get.mdx
@@ -51,9 +51,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -63,9 +63,9 @@ const redis = Redis.fromEnv();
 const value = await redis.json.get("key", "$.path.to.somewhere");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -75,9 +75,9 @@ result = redis.json().get("profile", "$.name")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -87,9 +87,9 @@ const result = await redis.call("JSON.GET", "profile", "$.name");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -101,9 +101,9 @@ const result = await client.json.get("profile", { path: "$.name" });
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -114,9 +114,9 @@ result = client.json().get("profile", "$.name")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -143,9 +143,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -158,9 +158,9 @@ try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::JsonCommands;
@@ -176,6 +176,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/json/json-merge.mdx b/redis/commands/json/json-merge.mdx
index fb9f2691a..f98d6d8e6 100644
--- a/redis/commands/json/json-merge.mdx
+++ b/redis/commands/json/json-merge.mdx
@@ -45,9 +45,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -57,9 +57,9 @@ const redis = Redis.fromEnv();
 await redis.json.merge("key", "$.path.to.value", {"new": "value"})
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -69,9 +69,9 @@ result = redis.json().merge("profile", "$", {"active": True})
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -81,9 +81,9 @@ const result = await redis.call("JSON.MERGE", "profile", "$", "{\"active\":true}
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -95,9 +95,9 @@ const result = await client.json.merge("profile", "$", { active: true });
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -108,9 +108,9 @@ result = client.json().merge("profile", "$", {"active": True})
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -137,9 +137,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -152,9 +152,9 @@ try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -172,6 +172,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/json/json-mget.mdx b/redis/commands/json/json-mget.mdx
index 8b3c33520..e6d9b0f5a 100644
--- a/redis/commands/json/json-mget.mdx
+++ b/redis/commands/json/json-mget.mdx
@@ -42,9 +42,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -54,9 +54,9 @@ const redis = Redis.fromEnv();
 const values = await redis.json.mget(["key1", "key2"],  "$.path.to.somewhere");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -66,9 +66,9 @@ result = redis.json().mget(["profile:1", "profile:2"], "$.name")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -78,9 +78,9 @@ const result = await redis.call("JSON.MGET", "profile:1", "profile:2", "$.name")
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -92,9 +92,9 @@ const result = await client.json.mGet(["profile:1", "profile:2"], "$.name");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -105,9 +105,9 @@ result = client.json().mget(["profile:1", "profile:2"], "$.name")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -134,9 +134,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -149,9 +149,9 @@ try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::JsonCommands;
@@ -167,6 +167,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/json/json-mset.mdx b/redis/commands/json/json-mset.mdx
index d17bff529..2833f61cd 100644
--- a/redis/commands/json/json-mset.mdx
+++ b/redis/commands/json/json-mset.mdx
@@ -41,9 +41,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -55,9 +55,9 @@ const result = await redis.json.mset([
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -67,9 +67,9 @@ result = redis.json().mset([("profile:1", "$", {"name": "Ada"})])
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -79,9 +79,9 @@ const result = await redis.call("JSON.MSET", "profile:1", "$", "{\"name\":\"Ada\
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -93,9 +93,9 @@ const result = await client.json.mSet([{ key: "profile:1", path: "$", value: { n
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -106,9 +106,9 @@ result = client.json().mset([("profile:1", "$", {"name": "Ada"})])
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -135,9 +135,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -152,9 +152,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -172,6 +172,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/json/json-numincrby.mdx b/redis/commands/json/json-numincrby.mdx
index 9e4167744..688c6caad 100644
--- a/redis/commands/json/json-numincrby.mdx
+++ b/redis/commands/json/json-numincrby.mdx
@@ -43,9 +43,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -55,9 +55,9 @@ const redis = Redis.fromEnv();
 const newValue = await redis.json.numincrby("key", "$.path.to.value", 2);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -67,9 +67,9 @@ result = redis.json().numincrby("profile", "$.visits", 1)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -79,9 +79,9 @@ const result = await redis.call("JSON.NUMINCRBY", "profile", "$.visits", "1");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -93,9 +93,9 @@ const result = await client.json.numIncrBy("profile", "$.visits", 1);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -106,9 +106,9 @@ result = client.json().numincrby("profile", "$.visits", 1)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -135,9 +135,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -150,9 +150,9 @@ try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::JsonCommands;
@@ -168,6 +168,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/json/json-nummultby.mdx b/redis/commands/json/json-nummultby.mdx
index 22d250289..47dd498b7 100644
--- a/redis/commands/json/json-nummultby.mdx
+++ b/redis/commands/json/json-nummultby.mdx
@@ -43,9 +43,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -55,9 +55,9 @@ const redis = Redis.fromEnv();
 const newValue = await redis.json.nummultby("key", "$.path.to.value", 2);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -67,9 +67,9 @@ result = redis.json().nummultby("profile", "$.score", 2)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -79,9 +79,9 @@ const result = await redis.call("JSON.NUMMULTBY", "profile", "$.score", "2");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -93,9 +93,9 @@ const result = await client.json.numMultBy("profile", "$.score", 2);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -106,9 +106,9 @@ result = client.json().nummultby("profile", "$.score", 2)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -135,9 +135,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -152,9 +152,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -172,6 +172,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/json/json-objkeys.mdx b/redis/commands/json/json-objkeys.mdx
index 9aef6d23a..69bb38221 100644
--- a/redis/commands/json/json-objkeys.mdx
+++ b/redis/commands/json/json-objkeys.mdx
@@ -42,9 +42,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -54,9 +54,9 @@ const redis = Redis.fromEnv();
 const keys = await redis.json.objkeys("key", "$.path");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -66,9 +66,9 @@ result = redis.json().objkeys("profile", "$")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -78,9 +78,9 @@ const result = await redis.call("JSON.OBJKEYS", "profile", "$");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -92,9 +92,9 @@ const result = await client.json.objKeys("profile", { path: "$" });
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -105,9 +105,9 @@ result = client.json().objkeys("profile", "$")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -134,9 +134,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -149,9 +149,9 @@ try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::JsonCommands;
@@ -167,6 +167,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/json/json-objlen.mdx b/redis/commands/json/json-objlen.mdx
index 031d5a435..4162e657a 100644
--- a/redis/commands/json/json-objlen.mdx
+++ b/redis/commands/json/json-objlen.mdx
@@ -42,9 +42,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -54,9 +54,9 @@ const redis = Redis.fromEnv();
 const lengths = await redis.json.objlen("key", "$.path");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -66,9 +66,9 @@ result = redis.json().objlen("profile", "$")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -78,9 +78,9 @@ const result = await redis.call("JSON.OBJLEN", "profile", "$");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -92,9 +92,9 @@ const result = await client.json.objLen("profile", { path: "$" });
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -105,9 +105,9 @@ result = client.json().objlen("profile", "$")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -134,9 +134,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -149,9 +149,9 @@ try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::JsonCommands;
@@ -167,6 +167,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/json/json-resp.mdx b/redis/commands/json/json-resp.mdx
index 0871c9d24..63af81215 100644
--- a/redis/commands/json/json-resp.mdx
+++ b/redis/commands/json/json-resp.mdx
@@ -44,9 +44,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -56,9 +56,9 @@ const result = await redis.json.resp("profile", "$");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -68,9 +68,9 @@ result = redis.json().resp("profile", "$")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -80,9 +80,9 @@ const result = await redis.call("JSON.RESP", "profile", "$");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -94,9 +94,9 @@ const result = await client.sendCommand(["JSON.RESP", "profile", "$"]);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -107,9 +107,9 @@ result = client.json().resp("profile", "$")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -136,9 +136,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -153,9 +153,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -172,6 +172,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/json/json-set.mdx b/redis/commands/json/json-set.mdx
index 7800a3170..6466fe68f 100644
--- a/redis/commands/json/json-set.mdx
+++ b/redis/commands/json/json-set.mdx
@@ -46,9 +46,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -58,9 +58,9 @@ const redis = Redis.fromEnv();
 redis.json.set(key, "$.path", value);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -70,9 +70,9 @@ result = redis.json().set("profile", "$", {"name": "Ada"})
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -82,9 +82,9 @@ const result = await redis.call("JSON.SET", "profile", "$", "{\"name\":\"Ada\"}"
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -96,9 +96,9 @@ const result = await client.json.set("profile", "$", { name: "Ada" });
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -109,9 +109,9 @@ result = client.json().set("profile", "$", {"name": "Ada"})
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -138,9 +138,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -153,9 +153,9 @@ try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::JsonCommands;
@@ -171,6 +171,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/json/json-strappend.mdx b/redis/commands/json/json-strappend.mdx
index f7dbb3a04..cda2316a5 100644
--- a/redis/commands/json/json-strappend.mdx
+++ b/redis/commands/json/json-strappend.mdx
@@ -43,9 +43,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -55,9 +55,9 @@ const redis = Redis.fromEnv();
 await redis.json.strappend("key", "$.path.to.str", "abc");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -67,9 +67,9 @@ result = redis.json().strappend("profile", "$.name", " Lovelace")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -79,9 +79,9 @@ const result = await redis.call("JSON.STRAPPEND", "profile", "$.name", "\" Lovel
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -93,9 +93,9 @@ const result = await client.json.strAppend("profile", " Lovelace", { path: "$.na
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -106,9 +106,9 @@ result = client.json().strappend("profile", " Lovelace", "$.name")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -135,9 +135,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -150,9 +150,9 @@ try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::JsonCommands;
@@ -168,6 +168,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/json/json-strlen.mdx b/redis/commands/json/json-strlen.mdx
index 70733ec9b..f5c557f50 100644
--- a/redis/commands/json/json-strlen.mdx
+++ b/redis/commands/json/json-strlen.mdx
@@ -42,9 +42,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -54,9 +54,9 @@ const redis = Redis.fromEnv();
 await redis.json.strlen("key", "$.path.to.str", "a");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -66,9 +66,9 @@ result = redis.json().strlen("profile", "$.name")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -78,9 +78,9 @@ const result = await redis.call("JSON.STRLEN", "profile", "$.name");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -92,9 +92,9 @@ const result = await client.json.strLen("profile", { path: "$.name" });
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -105,9 +105,9 @@ result = client.json().strlen("profile", "$.name")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -134,9 +134,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -149,9 +149,9 @@ try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::JsonCommands;
@@ -167,6 +167,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/json/json-toggle.mdx b/redis/commands/json/json-toggle.mdx
index 62e584d90..d26a6f7f2 100644
--- a/redis/commands/json/json-toggle.mdx
+++ b/redis/commands/json/json-toggle.mdx
@@ -42,9 +42,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -54,9 +54,9 @@ const redis = Redis.fromEnv();
 const bool = await redis.json.toggle("key", "$.path.to.bool");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -66,9 +66,9 @@ result = redis.json().toggle("profile", "$.active")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -78,9 +78,9 @@ const result = await redis.call("JSON.TOGGLE", "profile", "$.active");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -92,9 +92,9 @@ const result = await client.json.toggle("profile", "$.active");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -105,9 +105,9 @@ result = client.json().toggle("profile", "$.active")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -134,9 +134,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -149,9 +149,9 @@ try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::JsonCommands;
@@ -167,6 +167,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/json/json-type.mdx b/redis/commands/json/json-type.mdx
index d19eb0f51..a63e125db 100644
--- a/redis/commands/json/json-type.mdx
+++ b/redis/commands/json/json-type.mdx
@@ -42,9 +42,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -54,9 +54,9 @@ const redis = Redis.fromEnv();
 const myType = await redis.json.type("key", "$.path.to.value");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -66,9 +66,9 @@ result = redis.json().type("profile", "$.name")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -78,9 +78,9 @@ const result = await redis.call("JSON.TYPE", "profile", "$.name");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -92,9 +92,9 @@ const result = await client.json.type("profile", { path: "$.name" });
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -105,9 +105,9 @@ result = client.json().type("profile", "$.name")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -134,9 +134,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -149,9 +149,9 @@ try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::JsonCommands;
@@ -167,6 +167,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/list/blmove.mdx b/redis/commands/list/blmove.mdx
index b37038086..d741698dc 100644
--- a/redis/commands/list/blmove.mdx
+++ b/redis/commands/list/blmove.mdx
@@ -46,25 +46,25 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 <Note>
   This command is not supported yet in `upstash_redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -74,9 +74,9 @@ const result = await redis.blmove("source-key", "destination-key", "LEFT", "LEFT
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -88,9 +88,9 @@ const result = await client.blMove("source-key", "destination-key", "LEFT", "LEF
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -101,9 +101,9 @@ result = client.blmove("source-key", "destination-key", 1.5, "LEFT", "LEFT")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -131,9 +131,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -146,9 +146,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::{Direction, TypedCommands};
@@ -170,6 +170,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/list/blmpop.mdx b/redis/commands/list/blmpop.mdx
index ad9eadeed..286084b66 100644
--- a/redis/commands/list/blmpop.mdx
+++ b/redis/commands/list/blmpop.mdx
@@ -46,25 +46,25 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 <Note>
   This command is not supported yet in `upstash_redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -74,9 +74,9 @@ const result = await redis.blmpop("1.5", "1", "my-key", "LEFT");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -88,9 +88,9 @@ const result = await client.blmPop(1.5, "my-key", "LEFT");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -101,9 +101,9 @@ result = client.blmpop(1.5, 1, "my-key", direction="LEFT")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -131,9 +131,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -146,9 +146,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::{Direction, TypedCommands};
@@ -164,6 +164,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/list/blpop.mdx b/redis/commands/list/blpop.mdx
index c0a1ffb70..d18dc7fe1 100644
--- a/redis/commands/list/blpop.mdx
+++ b/redis/commands/list/blpop.mdx
@@ -43,25 +43,25 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 <Note>
   This command is not supported yet in `upstash_redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -71,9 +71,9 @@ const result = await redis.blpop("my-key", "1.5");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -85,9 +85,9 @@ const result = await client.blPop("my-key", 1.5);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -98,9 +98,9 @@ result = client.blpop(["my-key"], timeout=1.5)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -128,9 +128,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -143,9 +143,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -161,6 +161,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/list/brpop.mdx b/redis/commands/list/brpop.mdx
index 54570be0e..2fe0917c0 100644
--- a/redis/commands/list/brpop.mdx
+++ b/redis/commands/list/brpop.mdx
@@ -43,25 +43,25 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 <Note>
   This command is not supported yet in `upstash_redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -71,9 +71,9 @@ const result = await redis.brpop("my-key", "1.5");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -85,9 +85,9 @@ const result = await client.brPop("my-key", 1.5);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -98,9 +98,9 @@ result = client.brpop(["my-key"], timeout=1.5)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -128,9 +128,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -143,9 +143,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -161,6 +161,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/list/brpoplpush.mdx b/redis/commands/list/brpoplpush.mdx
index d1e210dee..09c337966 100644
--- a/redis/commands/list/brpoplpush.mdx
+++ b/redis/commands/list/brpoplpush.mdx
@@ -48,25 +48,25 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 <Note>
   This command is not supported yet in `upstash_redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -76,9 +76,9 @@ const result = await redis.brpoplpush("source-key", "destination-key", "1.5");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -90,9 +90,9 @@ const result = await client.brPopLPush("source-key", "destination-key", 1.5);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -103,9 +103,9 @@ result = client.brpoplpush("source-key", "destination-key", timeout=1.5)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -133,9 +133,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -148,9 +148,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -166,6 +166,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/list/lindex.mdx b/redis/commands/list/lindex.mdx
index b544a5b10..e1b8c1f61 100644
--- a/redis/commands/list/lindex.mdx
+++ b/redis/commands/list/lindex.mdx
@@ -37,9 +37,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -51,9 +51,9 @@ const element = await redis.lindex("key", 0);
 console.log(element); // "a"
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -63,9 +63,9 @@ result = redis.lindex("my-key", 0)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -75,9 +75,9 @@ const result = await redis.lindex("my-key", "0");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -89,9 +89,9 @@ const result = await client.lIndex("my-key", 0);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -102,9 +102,9 @@ result = client.lindex("my-key", 0)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -131,9 +131,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -146,9 +146,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -164,6 +164,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/list/linsert.mdx b/redis/commands/list/linsert.mdx
index d044cdc40..cf259be12 100644
--- a/redis/commands/list/linsert.mdx
+++ b/redis/commands/list/linsert.mdx
@@ -41,9 +41,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -54,9 +54,9 @@ await redis.rpush("key", "a", "b", "c");
 await redis.linsert("key", "before", "b", "x");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -66,9 +66,9 @@ result = redis.linsert("my-key", "BEFORE", "pivot", "element")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -78,9 +78,9 @@ const result = await redis.linsert("my-key", "BEFORE", "pivot", "element");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -92,9 +92,9 @@ const result = await client.lInsert("my-key", "BEFORE", "pivot", "element");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -105,9 +105,9 @@ result = client.linsert("my-key", "BEFORE", "pivot", "element")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -134,9 +134,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -149,9 +149,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -167,6 +167,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/list/llen.mdx b/redis/commands/list/llen.mdx
index 82975c27d..11ec9ac8d 100644
--- a/redis/commands/list/llen.mdx
+++ b/redis/commands/list/llen.mdx
@@ -36,9 +36,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -50,9 +50,9 @@ const length = await redis.llen("key");
 console.log(length); // 3
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -62,9 +62,9 @@ result = redis.llen("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -74,9 +74,9 @@ const result = await redis.llen("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -88,9 +88,9 @@ const result = await client.lLen("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -101,9 +101,9 @@ result = client.llen("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -130,9 +130,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -145,9 +145,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -163,6 +163,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/list/lmove.mdx b/redis/commands/list/lmove.mdx
index ea66c9f51..1840d1d54 100644
--- a/redis/commands/list/lmove.mdx
+++ b/redis/commands/list/lmove.mdx
@@ -41,9 +41,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -54,9 +54,9 @@ await redis.rpush("source", "a", "b", "c");
 const element = await redis.lmove("source", "destination", "left", "left");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -66,9 +66,9 @@ result = redis.lmove("source-key", "destination-key", "LEFT", "LEFT")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -78,9 +78,9 @@ const result = await redis.lmove("source-key", "destination-key", "LEFT", "LEFT"
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -92,9 +92,9 @@ const result = await client.lMove("source-key", "destination-key", "LEFT", "LEFT
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -105,9 +105,9 @@ result = client.lmove("source-key", "destination-key", "LEFT", "LEFT")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -134,9 +134,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -149,9 +149,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -167,6 +167,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/list/lmpop.mdx b/redis/commands/list/lmpop.mdx
index b01ad131a..e482e036d 100644
--- a/redis/commands/list/lmpop.mdx
+++ b/redis/commands/list/lmpop.mdx
@@ -41,9 +41,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -53,17 +53,17 @@ const result = await redis.lmpop(1, ["my-key"], "LEFT");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 <Note>
   This command is not supported yet in `upstash_redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -73,9 +73,9 @@ const result = await redis.lmpop("1", "my-key", "LEFT");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -87,9 +87,9 @@ const result = await client.lmPop("my-key", "LEFT");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -100,9 +100,9 @@ result = client.lmpop(1, "my-key", direction="LEFT")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -129,9 +129,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -144,9 +144,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::{Direction, TypedCommands};
@@ -162,6 +162,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/list/lpop.mdx b/redis/commands/list/lpop.mdx
index 692cf261a..09e66416f 100644
--- a/redis/commands/list/lpop.mdx
+++ b/redis/commands/list/lpop.mdx
@@ -39,9 +39,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -53,9 +53,9 @@ const element = await redis.lpop("key");
 console.log(element); // "a"
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -65,9 +65,9 @@ result = redis.lpop("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -77,9 +77,9 @@ const result = await redis.lpop("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -91,9 +91,9 @@ const result = await client.lPop("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -104,9 +104,9 @@ result = client.lpop("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -133,9 +133,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -148,9 +148,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -166,6 +166,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/list/lpos.mdx b/redis/commands/list/lpos.mdx
index 19d923f5d..168d8d32a 100644
--- a/redis/commands/list/lpos.mdx
+++ b/redis/commands/list/lpos.mdx
@@ -42,9 +42,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -56,9 +56,9 @@ const index = await redis.lpos("key", "b");
 console.log(index); // 1
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -68,9 +68,9 @@ result = redis.lpos("my-key", "element")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -80,9 +80,9 @@ const result = await redis.lpos("my-key", "element");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -94,9 +94,9 @@ const result = await client.lPos("my-key", "element");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -107,9 +107,9 @@ result = client.lpos("my-key", "element")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -136,9 +136,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -151,9 +151,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::{LposOptions, TypedCommands};
@@ -169,6 +169,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/list/lpush.mdx b/redis/commands/list/lpush.mdx
index 1d988b578..d1603b8be 100644
--- a/redis/commands/list/lpush.mdx
+++ b/redis/commands/list/lpush.mdx
@@ -39,9 +39,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -54,9 +54,9 @@ const length2 = await redis.lpush("key", "d");
 console.log(length2); // 4
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -66,9 +66,9 @@ result = redis.lpush("my-key", "element")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -78,9 +78,9 @@ const result = await redis.lpush("my-key", "element");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -92,9 +92,9 @@ const result = await client.lPush("my-key", "element");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -105,9 +105,9 @@ result = client.lpush("my-key", "element")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -134,9 +134,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -149,9 +149,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -167,6 +167,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/list/lpushx.mdx b/redis/commands/list/lpushx.mdx
index 7395e4530..b6d9fe4e1 100644
--- a/redis/commands/list/lpushx.mdx
+++ b/redis/commands/list/lpushx.mdx
@@ -37,9 +37,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -51,9 +51,9 @@ const length = await redis.lpushx("key", "d");
 console.log(length); // 4
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -63,9 +63,9 @@ result = redis.lpushx("my-key", "element")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -75,9 +75,9 @@ const result = await redis.lpushx("my-key", "element");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -89,9 +89,9 @@ const result = await client.lPushX("my-key", "element");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -102,9 +102,9 @@ result = client.lpushx("my-key", "element")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -131,9 +131,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -146,9 +146,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -164,6 +164,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/list/lrange.mdx b/redis/commands/list/lrange.mdx
index 2b8a62275..d6517bfa7 100644
--- a/redis/commands/list/lrange.mdx
+++ b/redis/commands/list/lrange.mdx
@@ -40,9 +40,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -54,9 +54,9 @@ const elements = await redis.lrange("key", 1, 2);
 console.log(elements) // ["b", "c"]
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -66,9 +66,9 @@ result = redis.lrange("my-key", 0, 0)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -78,9 +78,9 @@ const result = await redis.lrange("my-key", "0", "0");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -92,9 +92,9 @@ const result = await client.lRange("my-key", 0, 0);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -105,9 +105,9 @@ result = client.lrange("my-key", 0, 0)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -134,9 +134,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -149,9 +149,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -167,6 +167,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/list/lrem.mdx b/redis/commands/list/lrem.mdx
index ebbb8d43a..d4467fe53 100644
--- a/redis/commands/list/lrem.mdx
+++ b/redis/commands/list/lrem.mdx
@@ -40,9 +40,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -54,9 +54,9 @@ const removed = await redis.lrem("key", 4, "b");
 console.log(removed) // 2
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -66,9 +66,9 @@ result = redis.lrem("my-key", 1, "element")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -78,9 +78,9 @@ const result = await redis.lrem("my-key", "1", "element");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -92,9 +92,9 @@ const result = await client.lRem("my-key", 1, "element");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -105,9 +105,9 @@ result = client.lrem("my-key", 1, "element")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -134,9 +134,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -149,9 +149,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -167,6 +167,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/list/lset.mdx b/redis/commands/list/lset.mdx
index a38c0049a..34f7aba1f 100644
--- a/redis/commands/list/lset.mdx
+++ b/redis/commands/list/lset.mdx
@@ -38,9 +38,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -53,9 +53,9 @@ await redis.lset("key", 1, "d");
 // list is now ["a", "d", "c"]
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -65,9 +65,9 @@ result = redis.lset("my-key", 0, "element")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -77,9 +77,9 @@ const result = await redis.lset("my-key", "0", "element");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -91,9 +91,9 @@ const result = await client.lSet("my-key", 0, "element");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -104,9 +104,9 @@ result = client.lset("my-key", 0, "element")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -133,9 +133,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -148,9 +148,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -166,6 +166,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/list/ltrim.mdx b/redis/commands/list/ltrim.mdx
index d49175eb2..1ce397075 100644
--- a/redis/commands/list/ltrim.mdx
+++ b/redis/commands/list/ltrim.mdx
@@ -40,9 +40,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -54,9 +54,9 @@ await redis.ltrim("key", 1, 2);
 // the list is now ["b", "c"]
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -66,9 +66,9 @@ result = redis.ltrim("my-key", 0, 0)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -78,9 +78,9 @@ const result = await redis.ltrim("my-key", "0", "0");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -92,9 +92,9 @@ const result = await client.lTrim("my-key", 0, 0);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -105,9 +105,9 @@ result = client.ltrim("my-key", 0, 0)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -134,9 +134,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -149,9 +149,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -167,6 +167,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/list/rpop.mdx b/redis/commands/list/rpop.mdx
index 20a167f1d..b97cb2962 100644
--- a/redis/commands/list/rpop.mdx
+++ b/redis/commands/list/rpop.mdx
@@ -39,9 +39,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -53,9 +53,9 @@ const element = await redis.rpop("key");
 console.log(element); // "c"
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -65,9 +65,9 @@ result = redis.rpop("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -77,9 +77,9 @@ const result = await redis.rpop("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -91,9 +91,9 @@ const result = await client.rPop("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -104,9 +104,9 @@ result = client.rpop("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -133,9 +133,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -148,9 +148,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -166,6 +166,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/list/rpoplpush.mdx b/redis/commands/list/rpoplpush.mdx
index 0efdaa35a..8fd3d9f1a 100644
--- a/redis/commands/list/rpoplpush.mdx
+++ b/redis/commands/list/rpoplpush.mdx
@@ -43,17 +43,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -63,9 +63,9 @@ result = redis.rpoplpush("source-key", "destination-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -75,9 +75,9 @@ const result = await redis.rpoplpush("source-key", "destination-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -89,9 +89,9 @@ const result = await client.rPopLPush("source-key", "destination-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -102,9 +102,9 @@ result = client.rpoplpush("source-key", "destination-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -131,9 +131,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -146,9 +146,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -164,6 +164,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/list/rpush.mdx b/redis/commands/list/rpush.mdx
index 9486a802c..937666d1e 100644
--- a/redis/commands/list/rpush.mdx
+++ b/redis/commands/list/rpush.mdx
@@ -39,9 +39,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -54,9 +54,9 @@ const length2 = await redis.rpush("key", "d");
 console.log(length2); // 4
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -66,9 +66,9 @@ result = redis.rpush("my-key", "element")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -78,9 +78,9 @@ const result = await redis.rpush("my-key", "element");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -92,9 +92,9 @@ const result = await client.rPush("my-key", "element");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -105,9 +105,9 @@ result = client.rpush("my-key", "element")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -134,9 +134,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -149,9 +149,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -167,6 +167,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/list/rpushx.mdx b/redis/commands/list/rpushx.mdx
index 31f1a5263..3fa250384 100644
--- a/redis/commands/list/rpushx.mdx
+++ b/redis/commands/list/rpushx.mdx
@@ -37,9 +37,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -51,9 +51,9 @@ const length = await redis.rpushx("key", "d");
 console.log(length); // 4
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -63,9 +63,9 @@ result = redis.rpushx("my-key", "element")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -75,9 +75,9 @@ const result = await redis.rpushx("my-key", "element");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -89,9 +89,9 @@ const result = await client.rPushX("my-key", "element");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -102,9 +102,9 @@ result = client.rpushx("my-key", "element")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -131,9 +131,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -146,9 +146,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -164,6 +164,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/pub-sub/psubscribe.mdx b/redis/commands/pub-sub/psubscribe.mdx
index 6e70a86ec..0e33d651f 100644
--- a/redis/commands/pub-sub/psubscribe.mdx
+++ b/redis/commands/pub-sub/psubscribe.mdx
@@ -43,9 +43,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -55,9 +55,9 @@ await subscriber.psubscribe("events:*");
 subscriber.on("message", (channel, message) => console.log(channel, message));
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -68,9 +68,9 @@ await subscriber.pSubscribe("events:*", (message, channel) => {
 });
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -83,9 +83,9 @@ for message in pubsub.listen():
     print(message)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -112,9 +112,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -131,9 +131,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -152,6 +152,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/pub-sub/publish.mdx b/redis/commands/pub-sub/publish.mdx
index 3960390fb..7c868a59e 100644
--- a/redis/commands/pub-sub/publish.mdx
+++ b/redis/commands/pub-sub/publish.mdx
@@ -39,9 +39,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -51,9 +51,9 @@ const redis = Redis.fromEnv();
 const listeners = await redis.publish("my-channel", "my-message");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -63,9 +63,9 @@ result = redis.publish("events", "hello")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -75,9 +75,9 @@ const result = await redis.publish("events", "hello");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -89,9 +89,9 @@ const result = await client.publish("events", "hello");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -102,9 +102,9 @@ result = client.publish("events", "hello")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -131,9 +131,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -146,9 +146,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -164,6 +164,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/pub-sub/pubsub.mdx b/redis/commands/pub-sub/pubsub.mdx
index 76d808d90..248096f06 100644
--- a/redis/commands/pub-sub/pubsub.mdx
+++ b/redis/commands/pub-sub/pubsub.mdx
@@ -42,25 +42,25 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 <Note>
   This command is not supported yet in `upstash_redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -70,9 +70,9 @@ const result = await redis.pubsub("CHANNELS", "events:*");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -84,9 +84,9 @@ const result = await client.pubSubChannels("events:*");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -97,9 +97,9 @@ result = client.pubsub_channels("events:*")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -126,9 +126,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -141,9 +141,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -160,6 +160,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/pub-sub/punsubscribe.mdx b/redis/commands/pub-sub/punsubscribe.mdx
index 430eb2dca..4a516f424 100644
--- a/redis/commands/pub-sub/punsubscribe.mdx
+++ b/redis/commands/pub-sub/punsubscribe.mdx
@@ -43,9 +43,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -55,9 +55,9 @@ await subscriber.psubscribe("events:*");
 await subscriber.punsubscribe("events:*");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -67,9 +67,9 @@ await subscriber.pSubscribe("events:*", console.log);
 await subscriber.pUnsubscribe("events:*");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -81,9 +81,9 @@ pubsub.psubscribe("events:*")
 pubsub.punsubscribe("events:*")
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -110,9 +110,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -129,9 +129,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -146,6 +146,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/pub-sub/subscribe.mdx b/redis/commands/pub-sub/subscribe.mdx
index 4df32e34a..c980e9cff 100644
--- a/redis/commands/pub-sub/subscribe.mdx
+++ b/redis/commands/pub-sub/subscribe.mdx
@@ -43,9 +43,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -55,9 +55,9 @@ await subscriber.subscribe("events");
 subscriber.on("message", (channel, message) => console.log(channel, message));
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -68,9 +68,9 @@ await subscriber.subscribe("events", (message, channel) => {
 });
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -83,9 +83,9 @@ for message in pubsub.listen():
     print(message)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -112,9 +112,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -131,9 +131,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -152,6 +152,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/pub-sub/unsubscribe.mdx b/redis/commands/pub-sub/unsubscribe.mdx
index c563163d9..db0d3cebd 100644
--- a/redis/commands/pub-sub/unsubscribe.mdx
+++ b/redis/commands/pub-sub/unsubscribe.mdx
@@ -43,9 +43,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -55,9 +55,9 @@ await subscriber.subscribe("events");
 await subscriber.unsubscribe("events");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -67,9 +67,9 @@ await subscriber.subscribe("events", console.log);
 await subscriber.unsubscribe("events");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -81,9 +81,9 @@ pubsub.subscribe("events")
 pubsub.unsubscribe("events")
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -110,9 +110,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -129,9 +129,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -146,6 +146,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/scripting/eval-ro.mdx b/redis/commands/scripting/eval-ro.mdx
index 060df654a..aa532cf16 100644
--- a/redis/commands/scripting/eval-ro.mdx
+++ b/redis/commands/scripting/eval-ro.mdx
@@ -47,9 +47,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -63,9 +63,9 @@ const result = await redis.evalRo(script, [], ["hello"]);
 console.log(result) // "hello"
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -75,9 +75,9 @@ result = redis.eval_ro("return ARGV[1]", args=["value"])
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -87,9 +87,9 @@ const result = await redis.eval_ro("return ARGV[1]", "0", "value");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -101,9 +101,9 @@ const result = await client.evalRo("return ARGV[1]", { arguments: ["value"] });
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -114,9 +114,9 @@ result = client.eval_ro("return ARGV[1]", 0, "value")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -143,9 +143,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -158,9 +158,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -177,6 +177,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/scripting/eval.mdx b/redis/commands/scripting/eval.mdx
index 7cd750128..441e6dd0c 100644
--- a/redis/commands/scripting/eval.mdx
+++ b/redis/commands/scripting/eval.mdx
@@ -71,9 +71,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -87,9 +87,9 @@ const result = await redis.eval(script, [], ["hello"]);
 console.log(result) // "hello"
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -99,9 +99,9 @@ result = redis.eval("return ARGV[1]", args=["value"])
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -111,9 +111,9 @@ const result = await redis.eval("return ARGV[1]", "0", "value");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -125,9 +125,9 @@ const result = await client.eval("return ARGV[1]", { arguments: ["value"] });
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -138,9 +138,9 @@ result = client.eval("return ARGV[1]", 0, "value")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -167,9 +167,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -182,9 +182,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -201,6 +201,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/scripting/evalsha-ro.mdx b/redis/commands/scripting/evalsha-ro.mdx
index 811a94532..dfffd91f9 100644
--- a/redis/commands/scripting/evalsha-ro.mdx
+++ b/redis/commands/scripting/evalsha-ro.mdx
@@ -47,9 +47,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -60,9 +60,9 @@ const result = await redis.evalshaRo("fb67a0c03b48ddbf8b4c9b011e779563bdbc28cb",
 console.log(result) // "hello"
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -72,9 +72,9 @@ result = redis.evalsha_ro("<sha1>", args=["value"])
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -84,9 +84,9 @@ const result = await redis.evalsha_ro("<sha1>", "0", "value");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -98,9 +98,9 @@ const result = await client.evalShaRo("<sha1>", { arguments: ["value"] });
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -111,9 +111,9 @@ result = client.evalsha_ro("<sha1>", 0, "value")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -140,9 +140,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -155,9 +155,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -174,6 +174,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/scripting/evalsha.mdx b/redis/commands/scripting/evalsha.mdx
index df677c938..fc83a4286 100644
--- a/redis/commands/scripting/evalsha.mdx
+++ b/redis/commands/scripting/evalsha.mdx
@@ -50,9 +50,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -63,9 +63,9 @@ const result = await redis.evalsha("fb67a0c03b48ddbf8b4c9b011e779563bdbc28cb", [
 console.log(result) // "hello"
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -75,9 +75,9 @@ result = redis.evalsha("<sha1>", args=["value"])
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -87,9 +87,9 @@ const result = await redis.evalsha("<sha1>", "0", "value");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -101,9 +101,9 @@ const result = await client.evalSha("<sha1>", { arguments: ["value"] });
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -114,9 +114,9 @@ result = client.evalsha("<sha1>", 0, "value")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -143,9 +143,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -158,9 +158,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -177,6 +177,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/scripting/script-exists.mdx b/redis/commands/scripting/script-exists.mdx
index 0449a8124..9dc0b0637 100644
--- a/redis/commands/scripting/script-exists.mdx
+++ b/redis/commands/scripting/script-exists.mdx
@@ -36,9 +36,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -51,9 +51,9 @@ await redis.scriptExists("<sha1>", "<sha2>")
 // [1, 0]
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -63,9 +63,9 @@ result = redis.script_exists("<sha1>")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -75,9 +75,9 @@ const result = await redis.script("EXISTS", "<sha1>");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -89,9 +89,9 @@ const result = await client.scriptExists("<sha1>");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -102,9 +102,9 @@ result = client.script_exists("<sha1>")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -131,9 +131,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -146,9 +146,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -165,6 +165,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/scripting/script-flush.mdx b/redis/commands/scripting/script-flush.mdx
index e62e3db2b..e1defb7bb 100644
--- a/redis/commands/scripting/script-flush.mdx
+++ b/redis/commands/scripting/script-flush.mdx
@@ -36,9 +36,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -48,9 +48,9 @@ const redis = Redis.fromEnv();
 await redis.scriptFlush();
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -60,9 +60,9 @@ result = redis.script_flush()
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -72,9 +72,9 @@ const result = await redis.script("FLUSH");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -86,9 +86,9 @@ const result = await client.scriptFlush();
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -99,9 +99,9 @@ result = client.script_flush()
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -128,9 +128,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -143,9 +143,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -161,6 +161,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/scripting/script-kill.mdx b/redis/commands/scripting/script-kill.mdx
index 6a865533b..40560dff4 100644
--- a/redis/commands/scripting/script-kill.mdx
+++ b/redis/commands/scripting/script-kill.mdx
@@ -41,25 +41,25 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 <Note>
   This command is not supported yet in `upstash_redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -69,9 +69,9 @@ const result = await redis.script("KILL");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -83,9 +83,9 @@ const result = await client.scriptKill();
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -96,9 +96,9 @@ result = client.script_kill()
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -125,9 +125,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -140,9 +140,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -158,6 +158,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/scripting/script-load.mdx b/redis/commands/scripting/script-load.mdx
index b5695cd18..95f2363d5 100644
--- a/redis/commands/scripting/script-load.mdx
+++ b/redis/commands/scripting/script-load.mdx
@@ -42,9 +42,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -58,9 +58,9 @@ const script = `
 const sha1 = await redis.scriptLoad(script);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -70,9 +70,9 @@ result = redis.script_load("return ARGV[1]")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -82,9 +82,9 @@ const result = await redis.script("LOAD", "return ARGV[1]");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -96,9 +96,9 @@ const result = await client.scriptLoad("return ARGV[1]");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -109,9 +109,9 @@ result = client.script_load("return ARGV[1]")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -138,9 +138,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -153,9 +153,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::{Script, TypedCommands};
@@ -172,6 +172,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/search/search-aggregate.mdx b/redis/commands/search/search-aggregate.mdx
index 4139058d2..a8f9f260d 100644
--- a/redis/commands/search/search-aggregate.mdx
+++ b/redis/commands/search/search-aggregate.mdx
@@ -34,9 +34,9 @@ Raw RESP output may be rendered differently by client or protocol settings, but
 
 ## Examples
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -51,9 +51,9 @@ const result = await products.aggregate({
 });
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -66,9 +66,9 @@ result = products.aggregate(
 )
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import IORedis from "ioredis";
@@ -85,9 +85,9 @@ const result = await products.aggregate({
 });
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -106,17 +106,17 @@ const result = await products.aggregate({
 });
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="Redis CLI">
+<Accordion title="Redis CLI">
 
 ```bash
 SEARCH.AGGREGATE products '{}' '{"avg_price": {"$avg": {"field": "price"}}}'
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="curl">
+<Accordion title="curl">
 
 ```bash
 curl -X POST https://YOUR_ENDPOINT.upstash.io \
@@ -124,6 +124,6 @@ curl -X POST https://YOUR_ENDPOINT.upstash.io \
   -d '["SEARCH.AGGREGATE", "products", "{}", "{\"avg_price\": {\"$avg\": {\"field\": \"price\"}}}"]'
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/search/search-aliasadd.mdx b/redis/commands/search/search-aliasadd.mdx
index 7e7959fbb..7829cf99e 100644
--- a/redis/commands/search/search-aliasadd.mdx
+++ b/redis/commands/search/search-aliasadd.mdx
@@ -23,9 +23,9 @@ Returns `1` if a new alias was created or `2` if an existing alias was updated,
 
 ## Examples
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -37,9 +37,9 @@ const result = await redis.search.alias.add({
 });
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -51,9 +51,9 @@ result = redis.search.alias.add(
 )
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import IORedis from "ioredis";
@@ -67,9 +67,9 @@ const result = await search.alias.add({
 });
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -85,17 +85,17 @@ const result = await search.alias.add({
 });
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="Redis CLI">
+<Accordion title="Redis CLI">
 
 ```bash
 SEARCH.ALIASADD products products-v2
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="curl">
+<Accordion title="curl">
 
 ```bash
 curl -X POST https://YOUR_ENDPOINT.upstash.io \
@@ -103,6 +103,6 @@ curl -X POST https://YOUR_ENDPOINT.upstash.io \
   -d '["SEARCH.ALIASADD", "products", "products-v2"]'
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/search/search-aliasdel.mdx b/redis/commands/search/search-aliasdel.mdx
index 712b748d6..90c4825d4 100644
--- a/redis/commands/search/search-aliasdel.mdx
+++ b/redis/commands/search/search-aliasdel.mdx
@@ -21,9 +21,9 @@ Returns `1` if the alias was deleted or `0` if the alias was not found.
 
 ## Examples
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -32,9 +32,9 @@ const redis = Redis.fromEnv();
 const result = await redis.search.alias.delete({ alias: "products" });
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -43,9 +43,9 @@ redis = Redis.from_env()
 result = redis.search.alias.delete(alias="products")
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import IORedis from "ioredis";
@@ -56,9 +56,9 @@ const search = createSearch(redis);
 const result = await search.alias.delete({ alias: "products" });
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -71,17 +71,17 @@ const search = createSearch(client);
 const result = await search.alias.delete({ alias: "products" });
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="Redis CLI">
+<Accordion title="Redis CLI">
 
 ```bash
 SEARCH.ALIASDEL products
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="curl">
+<Accordion title="curl">
 
 ```bash
 curl -X POST https://YOUR_ENDPOINT.upstash.io \
@@ -89,6 +89,6 @@ curl -X POST https://YOUR_ENDPOINT.upstash.io \
   -d '["SEARCH.ALIASDEL", "products"]'
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/search/search-count.mdx b/redis/commands/search/search-count.mdx
index cb202342d..7edfbc467 100644
--- a/redis/commands/search/search-count.mdx
+++ b/redis/commands/search/search-count.mdx
@@ -23,9 +23,9 @@ Returns the number of matching documents as an integer. Returns `-1` if the inde
 
 ## Examples
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -39,9 +39,9 @@ const result = await products.count({
 console.log(result.count);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -53,9 +53,9 @@ result = products.count(filter={"inStock": True})
 print(result.count)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import IORedis from "ioredis";
@@ -71,9 +71,9 @@ const result = await products.count({
 console.log(result.count);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -91,17 +91,17 @@ const result = await products.count({
 console.log(result.count);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="Redis CLI">
+<Accordion title="Redis CLI">
 
 ```bash
 SEARCH.COUNT products '{"inStock": true}'
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="curl">
+<Accordion title="curl">
 
 ```bash
 curl -X POST https://YOUR_ENDPOINT.upstash.io \
@@ -109,6 +109,6 @@ curl -X POST https://YOUR_ENDPOINT.upstash.io \
   -d '["SEARCH.COUNT", "products", "{\"inStock\": true}"]'
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/search/search-create.mdx b/redis/commands/search/search-create.mdx
index 7b2114199..b16b41fb2 100644
--- a/redis/commands/search/search-create.mdx
+++ b/redis/commands/search/search-create.mdx
@@ -56,9 +56,9 @@ Returns `1` when the index is created. With `EXISTSOK`, returns `0` if the exist
 
 ## Examples
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis, s } from "@upstash/redis";
@@ -77,9 +77,9 @@ const products = await redis.search.createIndex({
 });
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -98,9 +98,9 @@ products = redis.search.create_index(
 )
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import IORedis from "ioredis";
@@ -121,9 +121,9 @@ const products = await search.createIndex({
 });
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -146,17 +146,17 @@ const products = await search.createIndex({
 });
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="Redis CLI">
+<Accordion title="Redis CLI">
 
 ```bash
 SEARCH.CREATE products ON JSON PREFIX 1 product: SCHEMA name TEXT price F64 FAST inStock BOOL
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="curl">
+<Accordion title="curl">
 
 ```bash
 curl -X POST https://YOUR_ENDPOINT.upstash.io \
@@ -164,6 +164,6 @@ curl -X POST https://YOUR_ENDPOINT.upstash.io \
   -d '["SEARCH.CREATE", "products", "ON", "JSON", "PREFIX", "1", "product:", "SCHEMA", "name", "TEXT", "price", "F64", "FAST", "inStock", "BOOL"]'
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/search/search-describe.mdx b/redis/commands/search/search-describe.mdx
index b0e9b9c5a..d36fc311d 100644
--- a/redis/commands/search/search-describe.mdx
+++ b/redis/commands/search/search-describe.mdx
@@ -47,9 +47,9 @@ Returns `null` if the index does not exist.
 
 ## Examples
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -59,9 +59,9 @@ const products = redis.search.index({ name: "products" });
 const description = await products.describe();
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -71,9 +71,9 @@ products = redis.search.index(name="products")
 description = products.describe()
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import IORedis from "ioredis";
@@ -85,9 +85,9 @@ const products = search.index({ name: "products" });
 const description = await products.describe();
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -101,17 +101,17 @@ const products = search.index({ name: "products" });
 const description = await products.describe();
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="Redis CLI">
+<Accordion title="Redis CLI">
 
 ```bash
 SEARCH.DESCRIBE products
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="curl">
+<Accordion title="curl">
 
 ```bash
 curl -X POST https://YOUR_ENDPOINT.upstash.io \
@@ -119,6 +119,6 @@ curl -X POST https://YOUR_ENDPOINT.upstash.io \
   -d '["SEARCH.DESCRIBE", "products"]'
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/search/search-drop.mdx b/redis/commands/search/search-drop.mdx
index 70b9ec5e8..28df1861a 100644
--- a/redis/commands/search/search-drop.mdx
+++ b/redis/commands/search/search-drop.mdx
@@ -23,9 +23,9 @@ Returns `1` if the index was dropped or `0` if the index was not found.
 
 ## Examples
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -35,9 +35,9 @@ const products = redis.search.index({ name: "products" });
 const result = await products.drop();
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -47,9 +47,9 @@ products = redis.search.index(name="products")
 result = products.drop()
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import IORedis from "ioredis";
@@ -61,9 +61,9 @@ const products = search.index({ name: "products" });
 const result = await products.drop();
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -77,17 +77,17 @@ const products = search.index({ name: "products" });
 const result = await products.drop();
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="Redis CLI">
+<Accordion title="Redis CLI">
 
 ```bash
 SEARCH.DROP products
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="curl">
+<Accordion title="curl">
 
 ```bash
 curl -X POST https://YOUR_ENDPOINT.upstash.io \
@@ -95,6 +95,6 @@ curl -X POST https://YOUR_ENDPOINT.upstash.io \
   -d '["SEARCH.DROP", "products"]'
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/search/search-listaliases.mdx b/redis/commands/search/search-listaliases.mdx
index 10b5e8504..762e9728f 100644
--- a/redis/commands/search/search-listaliases.mdx
+++ b/redis/commands/search/search-listaliases.mdx
@@ -23,9 +23,9 @@ The SDKs below decode the pairs into an object or dictionary that maps each alia
 
 ## Examples
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -35,9 +35,9 @@ const aliases = await redis.search.alias.list();
 // { products: "products-v2" }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -47,9 +47,9 @@ aliases = redis.search.alias.list()
 # {"products": "products-v2"}
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import IORedis from "ioredis";
@@ -61,9 +61,9 @@ const aliases = await search.alias.list();
 // { products: "products-v2" }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -77,17 +77,17 @@ const aliases = await search.alias.list();
 // { products: "products-v2" }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="Redis CLI">
+<Accordion title="Redis CLI">
 
 ```bash
 SEARCH.LISTALIASES
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="curl">
+<Accordion title="curl">
 
 ```bash
 curl -X POST https://YOUR_ENDPOINT.upstash.io \
@@ -95,6 +95,6 @@ curl -X POST https://YOUR_ENDPOINT.upstash.io \
   -d '["SEARCH.LISTALIASES"]'
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/search/search-listindexes.mdx b/redis/commands/search/search-listindexes.mdx
index f3a81cca0..7fcd975cf 100644
--- a/redis/commands/search/search-listindexes.mdx
+++ b/redis/commands/search/search-listindexes.mdx
@@ -41,9 +41,9 @@ Returns one entry per index, sorted by index name. Each entry is a map containin
   The high-level Search APIs do not currently expose `SEARCH.LISTINDEXES`. Use each client's generic command method for this command.
 </Note>
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -60,9 +60,9 @@ const indexes = await redis.exec<string[][]>([
 ]);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -79,9 +79,9 @@ indexes = redis.execute([
 ])
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import IORedis from "ioredis";
@@ -98,9 +98,9 @@ const indexes = await redis.call(
 );
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -119,17 +119,17 @@ const indexes = await client.sendCommand([
 ]);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="Redis CLI">
+<Accordion title="Redis CLI">
 
 ```bash
 SEARCH.LISTINDEXES MATCH 'product*' LIMIT 10 OFFSET 0
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="curl">
+<Accordion title="curl">
 
 ```bash
 curl -X POST https://YOUR_ENDPOINT.upstash.io \
@@ -137,6 +137,6 @@ curl -X POST https://YOUR_ENDPOINT.upstash.io \
   -d '["SEARCH.LISTINDEXES", "MATCH", "product*", "LIMIT", "10", "OFFSET", "0"]'
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/search/search-query.mdx b/redis/commands/search/search-query.mdx
index f111b6125..9c459e8ca 100644
--- a/redis/commands/search/search-query.mdx
+++ b/redis/commands/search/search-query.mdx
@@ -67,9 +67,9 @@ When `NOCONTENT` is used, each result is `[key, score]`. When `SELECT` is used,
 
 ## Examples
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis, s } from "@upstash/redis";
@@ -87,9 +87,9 @@ const results = await products.query({
 });
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -104,9 +104,9 @@ results = products.query(
 )
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import IORedis from "ioredis";
@@ -126,9 +126,9 @@ const results = await products.query({
 });
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -150,17 +150,17 @@ const results = await products.query({
 });
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="Redis CLI">
+<Accordion title="Redis CLI">
 
 ```bash
 SEARCH.QUERY products '{"name": "wireless"}' LIMIT 10 OFFSET 0
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="curl">
+<Accordion title="curl">
 
 ```bash
 curl -X POST https://YOUR_ENDPOINT.upstash.io \
@@ -168,6 +168,6 @@ curl -X POST https://YOUR_ENDPOINT.upstash.io \
   -d '["SEARCH.QUERY", "products", "{\"name\": \"wireless\"}", "LIMIT", "10", "OFFSET", "0"]'
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/search/search-reindex.mdx b/redis/commands/search/search-reindex.mdx
index 35f19d45d..059c66bf1 100644
--- a/redis/commands/search/search-reindex.mdx
+++ b/redis/commands/search/search-reindex.mdx
@@ -25,17 +25,17 @@ Returns `1` when the index is rebuilt or `0` if the index does not exist.
 
 ## Examples
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="Redis CLI">
+<Accordion title="Redis CLI">
 
 ```bash
 SEARCH.REINDEX products
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="curl">
+<Accordion title="curl">
 
 ```bash
 curl -X POST https://YOUR_ENDPOINT.upstash.io \
@@ -43,6 +43,6 @@ curl -X POST https://YOUR_ENDPOINT.upstash.io \
   -d '["SEARCH.REINDEX", "products"]'
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/search/search-waitindexing.mdx b/redis/commands/search/search-waitindexing.mdx
index 233376511..6d9e97874 100644
--- a/redis/commands/search/search-waitindexing.mdx
+++ b/redis/commands/search/search-waitindexing.mdx
@@ -27,9 +27,9 @@ Returns `1` when indexing is complete or `0` if the index was not found.
 
 ## Examples
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -39,9 +39,9 @@ const products = redis.search.index({ name: "products" });
 const result = await products.waitIndexing();
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -51,9 +51,9 @@ products = redis.search.index(name="products")
 result = products.wait_indexing()
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import IORedis from "ioredis";
@@ -65,9 +65,9 @@ const products = search.index({ name: "products" });
 const result = await products.waitIndexing();
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -81,17 +81,17 @@ const products = search.index({ name: "products" });
 const result = await products.waitIndexing();
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="Redis CLI">
+<Accordion title="Redis CLI">
 
 ```bash
 SEARCH.WAITINDEXING products
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="curl">
+<Accordion title="curl">
 
 ```bash
 curl -X POST https://YOUR_ENDPOINT.upstash.io \
@@ -99,6 +99,6 @@ curl -X POST https://YOUR_ENDPOINT.upstash.io \
   -d '["SEARCH.WAITINDEXING", "products"]'
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/server/acl.mdx b/redis/commands/server/acl.mdx
index 98786a1dd..a7deec90e 100644
--- a/redis/commands/server/acl.mdx
+++ b/redis/commands/server/acl.mdx
@@ -62,25 +62,25 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 <Note>
   This command is not supported yet in `upstash_redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -90,9 +90,9 @@ const result = await redis.acl("WHOAMI");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -104,9 +104,9 @@ const result = await client.aclWhoAmI();
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -117,9 +117,9 @@ result = client.acl_whoami()
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -146,9 +146,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -161,9 +161,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -179,6 +179,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/server/command.mdx b/redis/commands/server/command.mdx
index 80e854d01..1e9da1a6f 100644
--- a/redis/commands/server/command.mdx
+++ b/redis/commands/server/command.mdx
@@ -38,25 +38,25 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 <Note>
   This command is not supported yet in `upstash_redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -66,9 +66,9 @@ const result = await redis.call("COMMAND");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -80,9 +80,9 @@ const result = await client.command();
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -93,9 +93,9 @@ result = client.command()
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -122,9 +122,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -137,9 +137,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -155,6 +155,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/server/config-get.mdx b/redis/commands/server/config-get.mdx
index 468b44020..b0724bcaf 100644
--- a/redis/commands/server/config-get.mdx
+++ b/redis/commands/server/config-get.mdx
@@ -44,25 +44,25 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 <Note>
   This command is not supported yet in `upstash_redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -72,9 +72,9 @@ const result = await redis.config("GET", "notify-keyspace-events");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -86,9 +86,9 @@ const result = await client.configGet("notify-keyspace-events");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -99,9 +99,9 @@ result = client.config_get("notify-keyspace-events")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -128,9 +128,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -143,9 +143,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -162,6 +162,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/server/config-set.mdx b/redis/commands/server/config-set.mdx
index 894d8acdc..144bd5ed9 100644
--- a/redis/commands/server/config-set.mdx
+++ b/redis/commands/server/config-set.mdx
@@ -45,25 +45,25 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 <Note>
   This command is not supported yet in `upstash_redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -73,9 +73,9 @@ const result = await redis.config("SET", "notify-keyspace-events", "Ex");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -87,9 +87,9 @@ const result = await client.configSet("notify-keyspace-events", "Ex");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -100,9 +100,9 @@ result = client.config_set("notify-keyspace-events", "Ex")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -129,9 +129,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -144,9 +144,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -164,6 +164,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/server/dbsize.mdx b/redis/commands/server/dbsize.mdx
index 450e0e58c..0436699ac 100644
--- a/redis/commands/server/dbsize.mdx
+++ b/redis/commands/server/dbsize.mdx
@@ -38,9 +38,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -51,9 +51,9 @@ const keys = await redis.dbsize();
 console.log(keys) // 20
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -63,9 +63,9 @@ result = redis.dbsize()
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -75,9 +75,9 @@ const result = await redis.dbsize();
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -89,9 +89,9 @@ const result = await client.dbSize();
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -102,9 +102,9 @@ result = client.dbsize()
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -131,9 +131,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -146,9 +146,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -164,6 +164,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/server/flushall.mdx b/redis/commands/server/flushall.mdx
index 3d518e806..d2aa0c53e 100644
--- a/redis/commands/server/flushall.mdx
+++ b/redis/commands/server/flushall.mdx
@@ -44,9 +44,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -56,9 +56,9 @@ const redis = Redis.fromEnv();
 await redis.flushall();
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -68,9 +68,9 @@ result = redis.flushall()
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -80,9 +80,9 @@ const result = await redis.flushall();
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -94,9 +94,9 @@ const result = await client.flushAll();
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -107,9 +107,9 @@ result = client.flushall()
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -136,9 +136,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -151,9 +151,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -169,6 +169,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/server/flushdb.mdx b/redis/commands/server/flushdb.mdx
index cf4b5e999..79acab99f 100644
--- a/redis/commands/server/flushdb.mdx
+++ b/redis/commands/server/flushdb.mdx
@@ -44,9 +44,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -56,9 +56,9 @@ const redis = Redis.fromEnv();
 await redis.flushdb();
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -68,9 +68,9 @@ result = redis.flushdb()
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -80,9 +80,9 @@ const result = await redis.flushdb();
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -94,9 +94,9 @@ const result = await client.flushDb();
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -107,9 +107,9 @@ result = client.flushdb()
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -136,9 +136,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -151,9 +151,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -169,6 +169,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/server/info.mdx b/redis/commands/server/info.mdx
index a6f717bf8..3f3c1c4d6 100644
--- a/redis/commands/server/info.mdx
+++ b/redis/commands/server/info.mdx
@@ -44,25 +44,25 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 <Note>
   This command is not supported yet in `upstash_redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -72,9 +72,9 @@ const result = await redis.info("memory");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -86,9 +86,9 @@ const result = await client.info("memory");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -99,9 +99,9 @@ result = client.info("memory")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -128,9 +128,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -143,9 +143,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -161,6 +161,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/server/monitor.mdx b/redis/commands/server/monitor.mdx
index 1b1a85659..4ba9ed5c5 100644
--- a/redis/commands/server/monitor.mdx
+++ b/redis/commands/server/monitor.mdx
@@ -42,9 +42,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -58,9 +58,9 @@ redis.monitor((error, monitor) => {
 });
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -74,9 +74,9 @@ await client.monitor((command) => {
 });
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -88,9 +88,9 @@ with client.monitor() as monitor:
         print(command)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -107,9 +107,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -125,6 +125,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/server/time.mdx b/redis/commands/server/time.mdx
index 28e9d6d70..156dd047f 100644
--- a/redis/commands/server/time.mdx
+++ b/redis/commands/server/time.mdx
@@ -34,9 +34,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -46,9 +46,9 @@ const result = await redis.time();
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -58,9 +58,9 @@ result = redis.time()
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -70,9 +70,9 @@ const result = await redis.time();
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -84,9 +84,9 @@ const result = await client.time();
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -97,9 +97,9 @@ result = client.time()
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -126,9 +126,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -141,9 +141,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -159,6 +159,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/set/sadd.mdx b/redis/commands/set/sadd.mdx
index cded33de3..09c185dac 100644
--- a/redis/commands/set/sadd.mdx
+++ b/redis/commands/set/sadd.mdx
@@ -37,9 +37,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -53,9 +53,9 @@ await redis.sadd("key", "a", "b", "c");
 await redis.sadd("key", "a", "b");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -65,9 +65,9 @@ result = redis.sadd("my-key", "member")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -77,9 +77,9 @@ const result = await redis.sadd("my-key", "member");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -91,9 +91,9 @@ const result = await client.sAdd("my-key", "member");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -104,9 +104,9 @@ result = client.sadd("my-key", "member")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -133,9 +133,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -148,9 +148,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -166,6 +166,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/set/scard.mdx b/redis/commands/set/scard.mdx
index 51b20138b..6280d9753 100644
--- a/redis/commands/set/scard.mdx
+++ b/redis/commands/set/scard.mdx
@@ -36,9 +36,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -50,9 +50,9 @@ const cardinality = await redis.scard("key");
 console.log(cardinality); // 3
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -62,9 +62,9 @@ result = redis.scard("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -74,9 +74,9 @@ const result = await redis.scard("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -88,9 +88,9 @@ const result = await client.sCard("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -101,9 +101,9 @@ result = client.scard("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -130,9 +130,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -145,9 +145,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -163,6 +163,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/set/sdiff.mdx b/redis/commands/set/sdiff.mdx
index 890467f98..9696fcd93 100644
--- a/redis/commands/set/sdiff.mdx
+++ b/redis/commands/set/sdiff.mdx
@@ -38,9 +38,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -53,9 +53,9 @@ const diff =  await redis.sdiff("set1", "set2");
 console.log(diff); // ["a", "b"]
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -65,9 +65,9 @@ result = redis.sdiff("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -77,9 +77,9 @@ const result = await redis.sdiff("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -91,9 +91,9 @@ const result = await client.sDiff("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -104,9 +104,9 @@ result = client.sdiff(["my-key"])
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -133,9 +133,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -148,9 +148,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -166,6 +166,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/set/sdiffstore.mdx b/redis/commands/set/sdiffstore.mdx
index d9b45a9c7..3defe4516 100644
--- a/redis/commands/set/sdiffstore.mdx
+++ b/redis/commands/set/sdiffstore.mdx
@@ -39,9 +39,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -54,9 +54,9 @@ await redis.sdiff("dest", "set1", "set2");
 console.log(diff); // ["a", "b"]
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -66,9 +66,9 @@ result = redis.sdiffstore("destination-key", "my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -78,9 +78,9 @@ const result = await redis.sdiffstore("destination-key", "my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -92,9 +92,9 @@ const result = await client.sDiffStore("destination-key", "my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -105,9 +105,9 @@ result = client.sdiffstore("destination-key", ["my-key"])
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -134,9 +134,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -149,9 +149,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -167,6 +167,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/set/sinter.mdx b/redis/commands/set/sinter.mdx
index f68c093dd..763708033 100644
--- a/redis/commands/set/sinter.mdx
+++ b/redis/commands/set/sinter.mdx
@@ -38,9 +38,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -53,9 +53,9 @@ const intersection =  await redis.sinter("set1", "set2");
 console.log(intersection); // ["c"]
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -65,9 +65,9 @@ result = redis.sinter("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -77,9 +77,9 @@ const result = await redis.sinter("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -91,9 +91,9 @@ const result = await client.sInter("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -104,9 +104,9 @@ result = client.sinter(["my-key"])
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -133,9 +133,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -148,9 +148,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -166,6 +166,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/set/sintercard.mdx b/redis/commands/set/sintercard.mdx
index b0faaa274..13e56b9ec 100644
--- a/redis/commands/set/sintercard.mdx
+++ b/redis/commands/set/sintercard.mdx
@@ -44,9 +44,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -56,17 +56,17 @@ const result = await redis.sintercard(["my-key"]);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 <Note>
   This command is not supported yet in `upstash_redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -76,9 +76,9 @@ const result = await redis.sintercard("1", "my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -90,9 +90,9 @@ const result = await client.sInterCard(["my-key"]);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -103,9 +103,9 @@ result = client.sintercard(1, ["my-key"])
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -132,9 +132,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -147,9 +147,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -166,6 +166,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/set/sinterstore.mdx b/redis/commands/set/sinterstore.mdx
index 5fb596989..52acb2b45 100644
--- a/redis/commands/set/sinterstore.mdx
+++ b/redis/commands/set/sinterstore.mdx
@@ -37,9 +37,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -51,9 +51,9 @@ await redis.sadd("set2", "c", "d", "e");
 await redis.sinterstore("destination", "set1", "set2");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -63,9 +63,9 @@ result = redis.sinterstore("destination-key", "my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -75,9 +75,9 @@ const result = await redis.sinterstore("destination-key", "my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -89,9 +89,9 @@ const result = await client.sInterStore("destination-key", "my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -102,9 +102,9 @@ result = client.sinterstore("destination-key", ["my-key"])
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -131,9 +131,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -146,9 +146,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -164,6 +164,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/set/sismember.mdx b/redis/commands/set/sismember.mdx
index 03c76ced5..82260f638 100644
--- a/redis/commands/set/sismember.mdx
+++ b/redis/commands/set/sismember.mdx
@@ -37,9 +37,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -51,9 +51,9 @@ const isMember =  await redis.sismember("set", "a");
 console.log(isMember); // 1
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -63,9 +63,9 @@ result = redis.sismember("my-key", "member")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -75,9 +75,9 @@ const result = await redis.sismember("my-key", "member");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -89,9 +89,9 @@ const result = await client.sIsMember("my-key", "member");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -102,9 +102,9 @@ result = client.sismember("my-key", "member")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -131,9 +131,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -146,9 +146,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -164,6 +164,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/set/smembers.mdx b/redis/commands/set/smembers.mdx
index a3626c0f3..7763e49a5 100644
--- a/redis/commands/set/smembers.mdx
+++ b/redis/commands/set/smembers.mdx
@@ -36,9 +36,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -50,9 +50,9 @@ const members =  await redis.smembers("set");
 console.log(members); // ["a", "b", "c"]
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -62,9 +62,9 @@ result = redis.smembers("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -74,9 +74,9 @@ const result = await redis.smembers("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -88,9 +88,9 @@ const result = await client.sMembers("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -101,9 +101,9 @@ result = client.smembers("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -130,9 +130,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -145,9 +145,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -163,6 +163,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/set/smismember.mdx b/redis/commands/set/smismember.mdx
index fba424b96..eb5708674 100644
--- a/redis/commands/set/smismember.mdx
+++ b/redis/commands/set/smismember.mdx
@@ -37,9 +37,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -51,9 +51,9 @@ const members =  await redis.smismember("set", ["a", "b", "d"]);
 console.log(members); // [1, 1, 0]
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -63,9 +63,9 @@ result = redis.smismember("my-key", "member")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -75,9 +75,9 @@ const result = await redis.smismember("my-key", "member");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -89,9 +89,9 @@ const result = await client.smIsMember("my-key", ["member"]);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -102,9 +102,9 @@ result = client.smismember("my-key", ["member"])
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -131,9 +131,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -146,9 +146,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -164,6 +164,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/set/smove.mdx b/redis/commands/set/smove.mdx
index ae13f4e39..5414602d5 100644
--- a/redis/commands/set/smove.mdx
+++ b/redis/commands/set/smove.mdx
@@ -40,9 +40,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -56,9 +56,9 @@ const moved =  await redis.smove("original", "destination", "a");
 // destination: ["a"]
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -68,9 +68,9 @@ result = redis.smove("source-key", "destination-key", "member")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -80,9 +80,9 @@ const result = await redis.smove("source-key", "destination-key", "member");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -94,9 +94,9 @@ const result = await client.sMove("source-key", "destination-key", "member");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -107,9 +107,9 @@ result = client.smove("source-key", "destination-key", "member")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -136,9 +136,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -151,9 +151,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -169,6 +169,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/set/spop.mdx b/redis/commands/set/spop.mdx
index b8c94ce23..77c1cb559 100644
--- a/redis/commands/set/spop.mdx
+++ b/redis/commands/set/spop.mdx
@@ -39,9 +39,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -53,9 +53,9 @@ const popped = await redis.spop("set");
 console.log(popped); // "a"
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -65,9 +65,9 @@ result = redis.spop("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -77,9 +77,9 @@ const result = await redis.spop("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -91,9 +91,9 @@ const result = await client.sPop("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -104,9 +104,9 @@ result = client.spop("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -133,9 +133,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -148,9 +148,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -166,6 +166,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/set/srandmember.mdx b/redis/commands/set/srandmember.mdx
index aafa3a73b..58a8ab6a3 100644
--- a/redis/commands/set/srandmember.mdx
+++ b/redis/commands/set/srandmember.mdx
@@ -39,9 +39,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -53,9 +53,9 @@ const member = await redis.srandmember("set");
 console.log(member); // "a"
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -65,9 +65,9 @@ result = redis.srandmember("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -77,9 +77,9 @@ const result = await redis.srandmember("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -91,9 +91,9 @@ const result = await client.sRandMember("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -104,9 +104,9 @@ result = client.srandmember("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -133,9 +133,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -148,9 +148,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -166,6 +166,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/set/srem.mdx b/redis/commands/set/srem.mdx
index 74cdd57ab..0cebbe515 100644
--- a/redis/commands/set/srem.mdx
+++ b/redis/commands/set/srem.mdx
@@ -37,9 +37,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -51,9 +51,9 @@ const removed = await redis.srem("set", "a", "b", "d");
 console.log(removed); // 2
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -63,9 +63,9 @@ result = redis.srem("my-key", "member")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -75,9 +75,9 @@ const result = await redis.srem("my-key", "member");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -89,9 +89,9 @@ const result = await client.sRem("my-key", "member");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -102,9 +102,9 @@ result = client.srem("my-key", "member")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -131,9 +131,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -146,9 +146,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -164,6 +164,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/set/sscan.mdx b/redis/commands/set/sscan.mdx
index cbd504384..31073d688 100644
--- a/redis/commands/set/sscan.mdx
+++ b/redis/commands/set/sscan.mdx
@@ -46,9 +46,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -61,9 +61,9 @@ console.log(newCursor); // likely `0` since this is a very small set
 console.log(fields); // ["a", "ab"]
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -73,9 +73,9 @@ result = redis.sscan("my-key", 0)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -85,9 +85,9 @@ const result = await redis.sscan("my-key", "0");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -99,9 +99,9 @@ const result = await client.sScan("my-key", "0");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -112,9 +112,9 @@ result = client.sscan("my-key", 0)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -141,9 +141,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -156,9 +156,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -176,6 +176,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/set/sunion.mdx b/redis/commands/set/sunion.mdx
index a01819d6d..7c573679b 100644
--- a/redis/commands/set/sunion.mdx
+++ b/redis/commands/set/sunion.mdx
@@ -36,9 +36,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -51,9 +51,9 @@ const union =  await redis.sunion("set1", "set2");
 console.log(union); // ["a", "b", "c", "d", "e"]
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -63,9 +63,9 @@ result = redis.sunion("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -75,9 +75,9 @@ const result = await redis.sunion("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -89,9 +89,9 @@ const result = await client.sUnion("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -102,9 +102,9 @@ result = client.sunion(["my-key"])
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -131,9 +131,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -146,9 +146,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -164,6 +164,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/set/sunionstore.mdx b/redis/commands/set/sunionstore.mdx
index 57be47736..c6268de24 100644
--- a/redis/commands/set/sunionstore.mdx
+++ b/redis/commands/set/sunionstore.mdx
@@ -37,9 +37,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -51,9 +51,9 @@ await redis.sadd("set2", "c", "d", "e");
 await redis.sunionstore("destination", "set1", "set2");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -63,9 +63,9 @@ result = redis.sunionstore("destination-key", "my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -75,9 +75,9 @@ const result = await redis.sunionstore("destination-key", "my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -89,9 +89,9 @@ const result = await client.sUnionStore("destination-key", "my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -102,9 +102,9 @@ result = client.sunionstore("destination-key", ["my-key"])
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -131,9 +131,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -146,9 +146,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -164,6 +164,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/sorted-set/bzmpop.mdx b/redis/commands/sorted-set/bzmpop.mdx
index 21a73f5b0..5a5765bb9 100644
--- a/redis/commands/sorted-set/bzmpop.mdx
+++ b/redis/commands/sorted-set/bzmpop.mdx
@@ -46,25 +46,25 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 <Note>
   This command is not supported yet in `upstash_redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -74,9 +74,9 @@ const result = await redis.bzmpop("1.5", "1", "my-key", "MIN");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -88,9 +88,9 @@ const result = await client.bzmPop(1.5, "my-key", "MIN");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -101,9 +101,9 @@ result = client.bzmpop(1.5, 1, ["my-key"], min=True)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -131,9 +131,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -146,9 +146,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -164,6 +164,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/sorted-set/bzpopmax.mdx b/redis/commands/sorted-set/bzpopmax.mdx
index ee916accb..dc46aef5d 100644
--- a/redis/commands/sorted-set/bzpopmax.mdx
+++ b/redis/commands/sorted-set/bzpopmax.mdx
@@ -43,25 +43,25 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 <Note>
   This command is not supported yet in `upstash_redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -71,9 +71,9 @@ const result = await redis.bzpopmax("my-key", "1.5");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -85,9 +85,9 @@ const result = await client.bzPopMax("my-key", 1.5);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -98,9 +98,9 @@ result = client.bzpopmax(["my-key"], timeout=1.5)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -128,9 +128,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -143,9 +143,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -161,6 +161,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/sorted-set/bzpopmin.mdx b/redis/commands/sorted-set/bzpopmin.mdx
index 023b8c554..d22f2c3ac 100644
--- a/redis/commands/sorted-set/bzpopmin.mdx
+++ b/redis/commands/sorted-set/bzpopmin.mdx
@@ -43,25 +43,25 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 <Note>
   This command is not supported yet in `upstash_redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -71,9 +71,9 @@ const result = await redis.bzpopmin("my-key", "1.5");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -85,9 +85,9 @@ const result = await client.bzPopMin("my-key", 1.5);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -98,9 +98,9 @@ result = client.bzpopmin(["my-key"], timeout=1.5)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -128,9 +128,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -143,9 +143,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -161,6 +161,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/sorted-set/zadd.mdx b/redis/commands/sorted-set/zadd.mdx
index a7afca0bf..c5e842a64 100644
--- a/redis/commands/sorted-set/zadd.mdx
+++ b/redis/commands/sorted-set/zadd.mdx
@@ -48,9 +48,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -64,9 +64,9 @@ await redis.zadd(
 );
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -76,9 +76,9 @@ result = redis.zadd("my-key", {"member": 1.5})
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -88,9 +88,9 @@ const result = await redis.zadd("my-key", "1.5", "member");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -102,9 +102,9 @@ const result = await client.zAdd("my-key", { score: 1.5, value: "member" });
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -115,9 +115,9 @@ result = client.zadd("my-key", {"member": 1.5})
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -144,9 +144,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -159,9 +159,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -177,6 +177,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/sorted-set/zcard.mdx b/redis/commands/sorted-set/zcard.mdx
index f11148574..7bf0a69bf 100644
--- a/redis/commands/sorted-set/zcard.mdx
+++ b/redis/commands/sorted-set/zcard.mdx
@@ -36,9 +36,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -53,9 +53,9 @@ const elements = await redis.zrank("key");
 console.log(elements); // 2
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -65,9 +65,9 @@ result = redis.zcard("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -77,9 +77,9 @@ const result = await redis.zcard("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -91,9 +91,9 @@ const result = await client.zCard("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -104,9 +104,9 @@ result = client.zcard("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -133,9 +133,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -148,9 +148,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -166,6 +166,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/sorted-set/zcount.mdx b/redis/commands/sorted-set/zcount.mdx
index d7a73391a..d70d001c8 100644
--- a/redis/commands/sorted-set/zcount.mdx
+++ b/redis/commands/sorted-set/zcount.mdx
@@ -40,9 +40,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -57,9 +57,9 @@ const elements = await redis.zcount("key", "(1", "+inf");
 console.log(elements); // 1
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -69,9 +69,9 @@ result = redis.zcount("my-key", 1.5, 1.5)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -81,9 +81,9 @@ const result = await redis.zcount("my-key", "1.5", "1.5");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -95,9 +95,9 @@ const result = await client.zCount("my-key", 1.5, 1.5);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -108,9 +108,9 @@ result = client.zcount("my-key", 1.5, 1.5)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -137,9 +137,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -152,9 +152,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -170,6 +170,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/sorted-set/zdiff.mdx b/redis/commands/sorted-set/zdiff.mdx
index a4fb6ff44..99f85994f 100644
--- a/redis/commands/sorted-set/zdiff.mdx
+++ b/redis/commands/sorted-set/zdiff.mdx
@@ -46,17 +46,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -66,9 +66,9 @@ result = redis.zdiff(["my-key"])
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -78,9 +78,9 @@ const result = await redis.zdiff("1", "my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -92,9 +92,9 @@ const result = await client.zDiff("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -105,9 +105,9 @@ result = client.zdiff(["my-key"])
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -134,9 +134,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -149,9 +149,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -168,6 +168,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/sorted-set/zdiffstore.mdx b/redis/commands/sorted-set/zdiffstore.mdx
index 5a749fa4f..e9ad2f7ce 100644
--- a/redis/commands/sorted-set/zdiffstore.mdx
+++ b/redis/commands/sorted-set/zdiffstore.mdx
@@ -44,9 +44,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -56,9 +56,9 @@ const redis = Redis.fromEnv();
 const values = await redis.zdiffstore("destination", 2, "key1", "key2");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -68,9 +68,9 @@ result = redis.zdiffstore("destination-key", ["my-key"])
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -80,9 +80,9 @@ const result = await redis.zdiffstore("destination-key", "1", "my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -94,9 +94,9 @@ const result = await client.zDiffStore("destination-key", "my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -107,9 +107,9 @@ result = client.zdiffstore("destination-key", ["my-key"])
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -136,9 +136,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -151,9 +151,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -171,6 +171,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/sorted-set/zincrby.mdx b/redis/commands/sorted-set/zincrby.mdx
index 619ed4649..bc89d4152 100644
--- a/redis/commands/sorted-set/zincrby.mdx
+++ b/redis/commands/sorted-set/zincrby.mdx
@@ -44,9 +44,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -58,9 +58,9 @@ const value = await redis.zincrby("key", 2, "member");
 console.log(value); // 3
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -70,9 +70,9 @@ result = redis.zincrby("my-key", 1, "member")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -82,9 +82,9 @@ const result = await redis.zincrby("my-key", "1", "member");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -96,9 +96,9 @@ const result = await client.zIncrBy("my-key", 1, "member");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -109,9 +109,9 @@ result = client.zincrby("my-key", 1, "member")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -138,9 +138,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -153,9 +153,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -171,6 +171,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/sorted-set/zinter.mdx b/redis/commands/sorted-set/zinter.mdx
index 500f8aa35..8068bd751 100644
--- a/redis/commands/sorted-set/zinter.mdx
+++ b/redis/commands/sorted-set/zinter.mdx
@@ -51,17 +51,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -71,9 +71,9 @@ result = redis.zinter(["my-key"])
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -83,9 +83,9 @@ const result = await redis.zinter("1", "my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -97,9 +97,9 @@ const result = await client.zInter("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -110,9 +110,9 @@ result = client.zinter(["my-key"])
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -139,9 +139,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -154,9 +154,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -173,6 +173,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/sorted-set/zintercard.mdx b/redis/commands/sorted-set/zintercard.mdx
index 0a77eb9f5..9d0680748 100644
--- a/redis/commands/sorted-set/zintercard.mdx
+++ b/redis/commands/sorted-set/zintercard.mdx
@@ -38,25 +38,25 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 <Note>
   This command is not supported yet in `upstash_redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -66,9 +66,9 @@ const result = await redis.zintercard("1", "my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -80,9 +80,9 @@ const result = await client.zInterCard("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -93,9 +93,9 @@ result = client.zintercard(1, ["my-key"])
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -122,9 +122,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -137,9 +137,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -156,6 +156,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/sorted-set/zinterstore.mdx b/redis/commands/sorted-set/zinterstore.mdx
index ace6f2d90..386ade27e 100644
--- a/redis/commands/sorted-set/zinterstore.mdx
+++ b/redis/commands/sorted-set/zinterstore.mdx
@@ -48,9 +48,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -71,9 +71,9 @@ const res = await redis.zinterstore("destination", 2, ["key1", "key2"]);
 console.log(res) // 1
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -83,9 +83,9 @@ result = redis.zinterstore("destination-key", ["my-key"])
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -95,9 +95,9 @@ const result = await redis.zinterstore("destination-key", "1", "my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -109,9 +109,9 @@ const result = await client.zInterStore("destination-key", "my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -122,9 +122,9 @@ result = client.zinterstore("destination-key", ["my-key"])
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -151,9 +151,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -166,9 +166,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -184,6 +184,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/sorted-set/zlexcount.mdx b/redis/commands/sorted-set/zlexcount.mdx
index 8c6e2b6cd..29f99daa4 100644
--- a/redis/commands/sorted-set/zlexcount.mdx
+++ b/redis/commands/sorted-set/zlexcount.mdx
@@ -40,9 +40,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -57,9 +57,9 @@ const elements = await redis.zlexcount("key", "two", "+");
 console.log(elements); // 1
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -69,9 +69,9 @@ result = redis.zlexcount("my-key", "-", "+")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -81,9 +81,9 @@ const result = await redis.zlexcount("my-key", "-", "+");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -95,9 +95,9 @@ const result = await client.zLexCount("my-key", "-", "+");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -108,9 +108,9 @@ result = client.zlexcount("my-key", "-", "+")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -137,9 +137,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -152,9 +152,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -170,6 +170,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/sorted-set/zmpop.mdx b/redis/commands/sorted-set/zmpop.mdx
index 3d9d16b1e..21c703017 100644
--- a/redis/commands/sorted-set/zmpop.mdx
+++ b/redis/commands/sorted-set/zmpop.mdx
@@ -45,25 +45,25 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 <Note>
   This command is not supported yet in `upstash_redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -73,9 +73,9 @@ const result = await redis.zmpop("1", "my-key", "MIN");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -87,9 +87,9 @@ const result = await client.zmPop("my-key", "MIN");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -100,9 +100,9 @@ result = client.zmpop(1, ["my-key"], min=True)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -129,9 +129,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -144,9 +144,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -162,6 +162,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/sorted-set/zmscore.mdx b/redis/commands/sorted-set/zmscore.mdx
index 6a339293d..d37527250 100644
--- a/redis/commands/sorted-set/zmscore.mdx
+++ b/redis/commands/sorted-set/zmscore.mdx
@@ -41,9 +41,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -61,9 +61,9 @@ const scores = await redis.zmscore("key", ["m2", "m4"])
 console.log(scores) // [2, 4]
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -73,9 +73,9 @@ result = redis.zmscore("my-key", ["member"])
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -85,9 +85,9 @@ const result = await redis.zmscore("my-key", "member");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -99,9 +99,9 @@ const result = await client.zmScore("my-key", "member");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -112,9 +112,9 @@ result = client.zmscore("my-key", ["member"])
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -141,9 +141,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -156,9 +156,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -174,6 +174,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/sorted-set/zpopmax.mdx b/redis/commands/sorted-set/zpopmax.mdx
index 1d89f688e..798307b31 100644
--- a/redis/commands/sorted-set/zpopmax.mdx
+++ b/redis/commands/sorted-set/zpopmax.mdx
@@ -43,9 +43,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -55,9 +55,9 @@ const redis = Redis.fromEnv();
 const popped = await redis.zpopmax("key", 4);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -67,9 +67,9 @@ result = redis.zpopmax("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -79,9 +79,9 @@ const result = await redis.zpopmax("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -93,9 +93,9 @@ const result = await client.zPopMax("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -106,9 +106,9 @@ result = client.zpopmax("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -135,9 +135,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -150,9 +150,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -168,6 +168,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/sorted-set/zpopmin.mdx b/redis/commands/sorted-set/zpopmin.mdx
index 331cbc415..969d34f0c 100644
--- a/redis/commands/sorted-set/zpopmin.mdx
+++ b/redis/commands/sorted-set/zpopmin.mdx
@@ -43,9 +43,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -55,9 +55,9 @@ const redis = Redis.fromEnv();
 const popped = await redis.zpopmin("key", 4);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -67,9 +67,9 @@ result = redis.zpopmin("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -79,9 +79,9 @@ const result = await redis.zpopmin("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -93,9 +93,9 @@ const result = await client.zPopMin("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -106,9 +106,9 @@ result = client.zpopmin("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -135,9 +135,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -150,9 +150,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -168,6 +168,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/sorted-set/zrandmember.mdx b/redis/commands/sorted-set/zrandmember.mdx
index 7555a4981..6cf68f756 100644
--- a/redis/commands/sorted-set/zrandmember.mdx
+++ b/redis/commands/sorted-set/zrandmember.mdx
@@ -43,17 +43,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -63,9 +63,9 @@ result = redis.zrandmember("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -75,9 +75,9 @@ const result = await redis.zrandmember("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -89,9 +89,9 @@ const result = await client.zRandMember("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -102,9 +102,9 @@ result = client.zrandmember("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -131,9 +131,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -146,9 +146,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -164,6 +164,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/sorted-set/zrange.mdx b/redis/commands/sorted-set/zrange.mdx
index 10e4f62dd..113f371ae 100644
--- a/redis/commands/sorted-set/zrange.mdx
+++ b/redis/commands/sorted-set/zrange.mdx
@@ -55,9 +55,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -72,9 +72,9 @@ const res = await redis.zrange("key", 1, 3)
 console.log(res) // ["m2"]
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -84,9 +84,9 @@ result = redis.zrange("my-key", 0, -1)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -96,9 +96,9 @@ const result = await redis.zrange("my-key", "0", "-1");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -110,9 +110,9 @@ const result = await client.zRange("my-key", 0, -1);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -123,9 +123,9 @@ result = client.zrange("my-key", 0, -1)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -152,9 +152,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -167,9 +167,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -185,6 +185,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/sorted-set/zrangebylex.mdx b/redis/commands/sorted-set/zrangebylex.mdx
index 6542f3ed3..bfd88dc97 100644
--- a/redis/commands/sorted-set/zrangebylex.mdx
+++ b/redis/commands/sorted-set/zrangebylex.mdx
@@ -45,17 +45,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -65,9 +65,9 @@ result = redis.zrangebylex("my-key", "-", "+")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -77,9 +77,9 @@ const result = await redis.zrangebylex("my-key", "-", "+");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -91,9 +91,9 @@ const result = await client.zRangeByLex("my-key", "-", "+");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -104,9 +104,9 @@ result = client.zrangebylex("my-key", "-", "+")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -133,9 +133,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -148,9 +148,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -166,6 +166,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/sorted-set/zrangebyscore.mdx b/redis/commands/sorted-set/zrangebyscore.mdx
index 9ad74832f..107fdee81 100644
--- a/redis/commands/sorted-set/zrangebyscore.mdx
+++ b/redis/commands/sorted-set/zrangebyscore.mdx
@@ -50,17 +50,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -70,9 +70,9 @@ result = redis.zrangebyscore("my-key", "1.5", "1.5")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -82,9 +82,9 @@ const result = await redis.zrangebyscore("my-key", "1.5", "1.5");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -96,9 +96,9 @@ const result = await client.zRangeByScore("my-key", 1.5, 1.5);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -109,9 +109,9 @@ result = client.zrangebyscore("my-key", "1.5", "1.5")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -138,9 +138,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -153,9 +153,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -171,6 +171,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/sorted-set/zrangestore.mdx b/redis/commands/sorted-set/zrangestore.mdx
index 2163b323b..832f748c2 100644
--- a/redis/commands/sorted-set/zrangestore.mdx
+++ b/redis/commands/sorted-set/zrangestore.mdx
@@ -47,17 +47,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -67,9 +67,9 @@ result = redis.zrangestore("destination-key", "source-key", "-inf", "+inf", sort
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -79,9 +79,9 @@ const result = await redis.zrangestore("my-key", "my-key", "-inf", "+inf");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -93,9 +93,9 @@ const result = await client.zRangeStore("my-key", "my-key", "-inf", "+inf");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -106,9 +106,9 @@ result = client.zrangestore("destination-key", "source-key", "-inf", "+inf", bys
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -135,9 +135,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -150,9 +150,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -171,6 +171,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/sorted-set/zrank.mdx b/redis/commands/sorted-set/zrank.mdx
index 9b1418c51..c509913e6 100644
--- a/redis/commands/sorted-set/zrank.mdx
+++ b/redis/commands/sorted-set/zrank.mdx
@@ -44,9 +44,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -56,9 +56,9 @@ const redis = Redis.fromEnv();
 const rank = await redis.zrank("key", "member");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -68,9 +68,9 @@ result = redis.zrank("my-key", "member")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -80,9 +80,9 @@ const result = await redis.zrank("my-key", "member");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -94,9 +94,9 @@ const result = await client.zRank("my-key", "member");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -107,9 +107,9 @@ result = client.zrank("my-key", "member")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -136,9 +136,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -151,9 +151,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -169,6 +169,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/sorted-set/zrem.mdx b/redis/commands/sorted-set/zrem.mdx
index 227e9ca49..a33555e05 100644
--- a/redis/commands/sorted-set/zrem.mdx
+++ b/redis/commands/sorted-set/zrem.mdx
@@ -37,9 +37,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -49,9 +49,9 @@ const redis = Redis.fromEnv();
 await redis.zrem("key", "member");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -61,9 +61,9 @@ result = redis.zrem("my-key", "member")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -73,9 +73,9 @@ const result = await redis.zrem("my-key", "member");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -87,9 +87,9 @@ const result = await client.zRem("my-key", "member");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -100,9 +100,9 @@ result = client.zrem("my-key", "member")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -129,9 +129,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -144,9 +144,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -162,6 +162,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/sorted-set/zremrangebylex.mdx b/redis/commands/sorted-set/zremrangebylex.mdx
index ac2227d34..2bc0fa0f8 100644
--- a/redis/commands/sorted-set/zremrangebylex.mdx
+++ b/redis/commands/sorted-set/zremrangebylex.mdx
@@ -40,9 +40,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -52,9 +52,9 @@ const redis = Redis.fromEnv();
 await redis.zremrangebylex("key", "alpha", "omega")
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -64,9 +64,9 @@ result = redis.zremrangebylex("my-key", "-", "+")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -76,9 +76,9 @@ const result = await redis.zremrangebylex("my-key", "-", "+");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -90,9 +90,9 @@ const result = await client.zRemRangeByLex("my-key", "-", "+");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -103,9 +103,9 @@ result = client.zremrangebylex("my-key", "-", "+")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -132,9 +132,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -147,9 +147,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -165,6 +165,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/sorted-set/zremrangebyrank.mdx b/redis/commands/sorted-set/zremrangebyrank.mdx
index 842ba81bd..44ba71ac3 100644
--- a/redis/commands/sorted-set/zremrangebyrank.mdx
+++ b/redis/commands/sorted-set/zremrangebyrank.mdx
@@ -40,9 +40,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -52,9 +52,9 @@ const redis = Redis.fromEnv();
 await redis.zremrangebyrank("key", 4, 20)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -64,9 +64,9 @@ result = redis.zremrangebyrank("my-key", 0, 0)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -76,9 +76,9 @@ const result = await redis.zremrangebyrank("my-key", "0", "0");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -90,9 +90,9 @@ const result = await client.zRemRangeByRank("my-key", 0, 0);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -103,9 +103,9 @@ result = client.zremrangebyrank("my-key", 0, 0)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -132,9 +132,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -147,9 +147,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -165,6 +165,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/sorted-set/zremrangebyscore.mdx b/redis/commands/sorted-set/zremrangebyscore.mdx
index 57e2b3229..6c3078bbc 100644
--- a/redis/commands/sorted-set/zremrangebyscore.mdx
+++ b/redis/commands/sorted-set/zremrangebyscore.mdx
@@ -40,9 +40,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -52,9 +52,9 @@ const redis = Redis.fromEnv();
 await redis.zremrangebyscore("key", 2, 5)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -64,9 +64,9 @@ result = redis.zremrangebyscore("my-key", 1.5, 1.5)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -76,9 +76,9 @@ const result = await redis.zremrangebyscore("my-key", "1.5", "1.5");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -90,9 +90,9 @@ const result = await client.zRemRangeByScore("my-key", 1.5, 1.5);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -103,9 +103,9 @@ result = client.zremrangebyscore("my-key", 1.5, 1.5)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -132,9 +132,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -147,9 +147,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -165,6 +165,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/sorted-set/zrevrange.mdx b/redis/commands/sorted-set/zrevrange.mdx
index 9dab6557d..fc9e1bffb 100644
--- a/redis/commands/sorted-set/zrevrange.mdx
+++ b/redis/commands/sorted-set/zrevrange.mdx
@@ -47,17 +47,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -67,9 +67,9 @@ result = redis.zrevrange("my-key", 0, 0)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -79,9 +79,9 @@ const result = await redis.zrevrange("my-key", "0", "0");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -93,9 +93,9 @@ const result = await client.zRange("my-key", 0, 0, { REV: true });
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -106,9 +106,9 @@ result = client.zrevrange("my-key", 0, 0)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -135,9 +135,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -150,9 +150,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -168,6 +168,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/sorted-set/zrevrangebylex.mdx b/redis/commands/sorted-set/zrevrangebylex.mdx
index e4d378c2e..5b6468fb1 100644
--- a/redis/commands/sorted-set/zrevrangebylex.mdx
+++ b/redis/commands/sorted-set/zrevrangebylex.mdx
@@ -45,17 +45,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -65,9 +65,9 @@ result = redis.zrevrangebylex("my-key", "+", "-")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -77,9 +77,9 @@ const result = await redis.zrevrangebylex("my-key", "+", "-");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -91,9 +91,9 @@ const result = await client.zRange("my-key", "+", "-", { BY: "LEX", REV: true })
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -104,9 +104,9 @@ result = client.zrevrangebylex("my-key", "+", "-")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -133,9 +133,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -148,9 +148,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -166,6 +166,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/sorted-set/zrevrangebyscore.mdx b/redis/commands/sorted-set/zrevrangebyscore.mdx
index e00e0583b..f72154562 100644
--- a/redis/commands/sorted-set/zrevrangebyscore.mdx
+++ b/redis/commands/sorted-set/zrevrangebyscore.mdx
@@ -48,17 +48,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -68,9 +68,9 @@ result = redis.zrevrangebyscore("my-key", "1.5", "1.5")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -80,9 +80,9 @@ const result = await redis.zrevrangebyscore("my-key", "1.5", "1.5");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -94,9 +94,9 @@ const result = await client.zRange("my-key", 1.5, 1.5, { BY: "SCORE", REV: true
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -107,9 +107,9 @@ result = client.zrevrangebyscore("my-key", "1.5", "1.5")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -136,9 +136,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -151,9 +151,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -169,6 +169,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/sorted-set/zrevrank.mdx b/redis/commands/sorted-set/zrevrank.mdx
index a29c546e5..8fd279abc 100644
--- a/redis/commands/sorted-set/zrevrank.mdx
+++ b/redis/commands/sorted-set/zrevrank.mdx
@@ -42,9 +42,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -54,9 +54,9 @@ const redis = Redis.fromEnv();
 const rank = await redis.zrevrank("key", "member");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -66,9 +66,9 @@ result = redis.zrevrank("my-key", "member")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -78,9 +78,9 @@ const result = await redis.zrevrank("my-key", "member");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -92,9 +92,9 @@ const result = await client.zRevRank("my-key", "member");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -105,9 +105,9 @@ result = client.zrevrank("my-key", "member")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -134,9 +134,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -149,9 +149,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -167,6 +167,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/sorted-set/zscan.mdx b/redis/commands/sorted-set/zscan.mdx
index f6317d42e..ed640de98 100644
--- a/redis/commands/sorted-set/zscan.mdx
+++ b/redis/commands/sorted-set/zscan.mdx
@@ -47,9 +47,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -68,9 +68,9 @@ console.log(newCursor); // likely `0` since this is a very small set
 console.log(members); // ["a", "ab"]
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -80,9 +80,9 @@ result = redis.zscan("my-key", 0)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -92,9 +92,9 @@ const result = await redis.zscan("my-key", "0");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -106,9 +106,9 @@ const result = await client.zScan("my-key", "0");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -119,9 +119,9 @@ result = client.zscan("my-key", 0)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -148,9 +148,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -163,9 +163,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -183,6 +183,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/sorted-set/zscore.mdx b/redis/commands/sorted-set/zscore.mdx
index 451fc8049..fcb6cabba 100644
--- a/redis/commands/sorted-set/zscore.mdx
+++ b/redis/commands/sorted-set/zscore.mdx
@@ -41,9 +41,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -61,9 +61,9 @@ const score = await redis.zscore("key", "m2")
 console.log(score) // 2
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -73,9 +73,9 @@ result = redis.zscore("my-key", "member")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -85,9 +85,9 @@ const result = await redis.zscore("my-key", "member");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -99,9 +99,9 @@ const result = await client.zScore("my-key", "member");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -112,9 +112,9 @@ result = client.zscore("my-key", "member")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -141,9 +141,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -156,9 +156,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -174,6 +174,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/sorted-set/zunion.mdx b/redis/commands/sorted-set/zunion.mdx
index e56f3c02a..dbdd990fe 100644
--- a/redis/commands/sorted-set/zunion.mdx
+++ b/redis/commands/sorted-set/zunion.mdx
@@ -50,9 +50,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -62,9 +62,9 @@ const result = await redis.zunion(1, "my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -74,9 +74,9 @@ result = redis.zunion(["my-key"])
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -86,9 +86,9 @@ const result = await redis.zunion("1", "my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -100,9 +100,9 @@ const result = await client.zUnion("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -113,9 +113,9 @@ result = client.zunion(["my-key"])
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -142,9 +142,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -157,9 +157,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -176,6 +176,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/sorted-set/zunionstore.mdx b/redis/commands/sorted-set/zunionstore.mdx
index d00bcce89..8be24714c 100644
--- a/redis/commands/sorted-set/zunionstore.mdx
+++ b/redis/commands/sorted-set/zunionstore.mdx
@@ -48,9 +48,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -71,9 +71,9 @@ const res = await redis.zunionstore("destination", 2, ["key1", "key2"]);
 console.log(res) // 2
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -83,9 +83,9 @@ result = redis.zunionstore("destination-key", ["my-key"])
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -95,9 +95,9 @@ const result = await redis.zunionstore("destination-key", "1", "my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -109,9 +109,9 @@ const result = await client.zUnionStore("destination-key", "my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -122,9 +122,9 @@ result = client.zunionstore("destination-key", ["my-key"])
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -151,9 +151,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -166,9 +166,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -184,6 +184,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/streams/xack.mdx b/redis/commands/streams/xack.mdx
index 63a600ff8..66ebe1346 100644
--- a/redis/commands/streams/xack.mdx
+++ b/redis/commands/streams/xack.mdx
@@ -40,9 +40,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -52,9 +52,9 @@ const redis = Redis.fromEnv();
 const result = await redis.xack("mystream", "mygroup", "1638360173533-0");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -64,9 +64,9 @@ result = redis.xack("my-key", "workers", "0-0")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -76,9 +76,9 @@ const result = await redis.xack("my-key", "workers", "0-0");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -90,9 +90,9 @@ const result = await client.xAck("my-key", "workers", "0-0");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -103,9 +103,9 @@ result = client.xack("my-key", "workers", "0-0")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -132,9 +132,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -147,9 +147,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -165,6 +165,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/streams/xackdel.mdx b/redis/commands/streams/xackdel.mdx
index 8dc299487..4e1399ee0 100644
--- a/redis/commands/streams/xackdel.mdx
+++ b/redis/commands/streams/xackdel.mdx
@@ -43,9 +43,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -57,9 +57,9 @@ const result = await redis.xackdel("mystream", "mygroup", "1638360173533-0");
 console.log(result); // Array of results for each ID
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -69,9 +69,9 @@ result = redis.xackdel("my-key", "workers", "0-0")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -81,9 +81,9 @@ const result = await redis.call("XACKDEL", "my-key", "workers", "IDS", "1", "0-0
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -95,9 +95,9 @@ const result = await client.xAckDel("my-key", "workers", "0-0");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -108,9 +108,9 @@ result = client.xackdel("my-key", "workers", "0-0")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -137,9 +137,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -152,9 +152,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -170,6 +170,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/streams/xadd.mdx b/redis/commands/streams/xadd.mdx
index bf14ccc2d..11d5c8f73 100644
--- a/redis/commands/streams/xadd.mdx
+++ b/redis/commands/streams/xadd.mdx
@@ -49,9 +49,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -61,9 +61,9 @@ const redis = Redis.fromEnv();
 const result = await redis.xadd("mystream", "*", { name: "John Doe", age: 30 });
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -73,9 +73,9 @@ result = redis.xadd("my-key", "*", {"field": "value"})
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -85,9 +85,9 @@ const result = await redis.xadd("my-key", "*", "field", "value");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -99,9 +99,9 @@ const result = await client.xAdd("my-key", "*", { field: "value" });
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -112,9 +112,9 @@ result = client.xadd("my-key", {"field": "value"})
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -141,9 +141,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -156,9 +156,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -174,6 +174,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/streams/xautoclaim.mdx b/redis/commands/streams/xautoclaim.mdx
index c7a1f3230..aa26ad596 100644
--- a/redis/commands/streams/xautoclaim.mdx
+++ b/redis/commands/streams/xautoclaim.mdx
@@ -44,9 +44,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -62,9 +62,9 @@ const result = await redis.xautoclaim(
 );
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -74,9 +74,9 @@ result = redis.xautoclaim("my-key", "workers", "worker-1", 60000, "0-0")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -86,9 +86,9 @@ const result = await redis.xautoclaim("my-key", "workers", "worker-1", "60000",
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -100,9 +100,9 @@ const result = await client.xAutoClaim("my-key", "workers", "worker-1", 60000, "
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -113,9 +113,9 @@ result = client.xautoclaim("my-key", "workers", "worker-1", 60000, "0-0")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -143,9 +143,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -158,9 +158,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::streams::StreamAutoClaimOptions;
@@ -184,6 +184,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/streams/xclaim.mdx b/redis/commands/streams/xclaim.mdx
index ba44fafaa..ec4229bc8 100644
--- a/redis/commands/streams/xclaim.mdx
+++ b/redis/commands/streams/xclaim.mdx
@@ -56,9 +56,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -74,9 +74,9 @@ const result = await redis.xclaim(
 );
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -86,9 +86,9 @@ result = redis.xclaim("my-key", "workers", "worker-1", 60000, "0-0")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -98,9 +98,9 @@ const result = await redis.xclaim("my-key", "workers", "worker-1", "60000", "0-0
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -112,9 +112,9 @@ const result = await client.xClaim("my-key", "workers", "worker-1", 60000, "0-0"
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -125,9 +125,9 @@ result = client.xclaim("my-key", "workers", "worker-1", 60000, ["0-0"])
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -155,9 +155,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -170,9 +170,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -188,6 +188,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/streams/xdel.mdx b/redis/commands/streams/xdel.mdx
index c326dddbf..cf0201033 100644
--- a/redis/commands/streams/xdel.mdx
+++ b/redis/commands/streams/xdel.mdx
@@ -39,9 +39,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -51,9 +51,9 @@ const redis = Redis.fromEnv();
 const result = await redis.xdel("mystream", "1638360173533-0");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -63,9 +63,9 @@ result = redis.xdel("my-key", "0-0")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -75,9 +75,9 @@ const result = await redis.xdel("my-key", "0-0");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -89,9 +89,9 @@ const result = await client.xDel("my-key", "0-0");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -102,9 +102,9 @@ result = client.xdel("my-key", "0-0")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -131,9 +131,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -146,9 +146,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -164,6 +164,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/streams/xdelex.mdx b/redis/commands/streams/xdelex.mdx
index e9079f269..b45ca79d0 100644
--- a/redis/commands/streams/xdelex.mdx
+++ b/redis/commands/streams/xdelex.mdx
@@ -42,9 +42,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -56,9 +56,9 @@ const result = await redis.xdelex("mystream", "1638360173533-0");
 console.log(result); // Array of results for each ID
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -68,9 +68,9 @@ result = redis.xdelex("my-key", "0-0")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -80,9 +80,9 @@ const result = await redis.xdelex("my-key", "IDS", "1", "0-0");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -94,9 +94,9 @@ const result = await client.xDelEx("my-key", "0-0");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -107,9 +107,9 @@ result = client.xdelex("my-key", "0-0")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -136,9 +136,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -151,9 +151,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -169,6 +169,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/streams/xgroup.mdx b/redis/commands/streams/xgroup.mdx
index 71e43ca3b..ab7faf482 100644
--- a/redis/commands/streams/xgroup.mdx
+++ b/redis/commands/streams/xgroup.mdx
@@ -49,9 +49,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -66,9 +66,9 @@ const result = await redis.xgroup("mystream", {
 });
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -78,9 +78,9 @@ result = redis.xgroup_create("events", "workers", "$", mkstream=True)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -90,9 +90,9 @@ const result = await redis.xgroup("CREATE", "events", "workers", "$", "MKSTREAM"
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -104,9 +104,9 @@ const result = await client.xGroupCreate("events", "workers", "$", { MKSTREAM: t
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -117,9 +117,9 @@ result = client.xgroup_create("events", "workers", "$", mkstream=True)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -146,9 +146,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -161,9 +161,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -179,6 +179,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/streams/xinfo-consumers.mdx b/redis/commands/streams/xinfo-consumers.mdx
index 0111d8cdb..79d6d68b1 100644
--- a/redis/commands/streams/xinfo-consumers.mdx
+++ b/redis/commands/streams/xinfo-consumers.mdx
@@ -37,9 +37,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -52,9 +52,9 @@ const result = await redis.xinfo("my-key", {
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -64,9 +64,9 @@ result = redis.xinfo_consumers("my-key", "workers")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -76,9 +76,9 @@ const result = await redis.xinfo("CONSUMERS", "my-key", "workers");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -90,9 +90,9 @@ const result = await client.xInfoConsumers("my-key", "workers");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -103,9 +103,9 @@ result = client.xinfo_consumers("my-key", "workers")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -132,9 +132,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -147,9 +147,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -165,6 +165,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/streams/xinfo-groups.mdx b/redis/commands/streams/xinfo-groups.mdx
index 75b2c5519..da55280af 100644
--- a/redis/commands/streams/xinfo-groups.mdx
+++ b/redis/commands/streams/xinfo-groups.mdx
@@ -36,9 +36,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -48,9 +48,9 @@ const result = await redis.xinfo("my-key", { type: "GROUPS" });
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -60,9 +60,9 @@ result = redis.xinfo_groups("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -72,9 +72,9 @@ const result = await redis.xinfo("GROUPS", "my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -86,9 +86,9 @@ const result = await client.xInfoGroups("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -99,9 +99,9 @@ result = client.xinfo_groups("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -128,9 +128,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -143,9 +143,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -161,6 +161,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/streams/xinfo-stream.mdx b/redis/commands/streams/xinfo-stream.mdx
index 7e114eccb..ade38210d 100644
--- a/redis/commands/streams/xinfo-stream.mdx
+++ b/redis/commands/streams/xinfo-stream.mdx
@@ -39,25 +39,25 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 <Note>
   This command is not supported yet in `upstash_redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -67,9 +67,9 @@ const result = await redis.xinfo("STREAM", "my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -81,9 +81,9 @@ const result = await client.xInfoStream("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -94,9 +94,9 @@ result = client.xinfo_stream("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -123,9 +123,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -138,9 +138,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -156,6 +156,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/streams/xlen.mdx b/redis/commands/streams/xlen.mdx
index 6bea4045e..f6292c23f 100644
--- a/redis/commands/streams/xlen.mdx
+++ b/redis/commands/streams/xlen.mdx
@@ -36,9 +36,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -48,9 +48,9 @@ const redis = Redis.fromEnv();
 const result = await redis.xlen("mystream");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -60,9 +60,9 @@ result = redis.xlen("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -72,9 +72,9 @@ const result = await redis.xlen("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -86,9 +86,9 @@ const result = await client.xLen("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -99,9 +99,9 @@ result = client.xlen("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -128,9 +128,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -143,9 +143,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -161,6 +161,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/streams/xpending.mdx b/redis/commands/streams/xpending.mdx
index 7cd99f90d..7f7d2e71e 100644
--- a/redis/commands/streams/xpending.mdx
+++ b/redis/commands/streams/xpending.mdx
@@ -45,9 +45,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -57,9 +57,9 @@ const redis = Redis.fromEnv();
 const result = await redis.xpending("mystream", "mygroup", "-", "+", 10);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -69,9 +69,9 @@ result = redis.xpending("my-key", "workers")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -81,9 +81,9 @@ const result = await redis.xpending("my-key", "workers");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -95,9 +95,9 @@ const result = await client.xPending("my-key", "workers");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -108,9 +108,9 @@ result = client.xpending("my-key", "workers")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -137,9 +137,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -152,9 +152,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -170,6 +170,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/streams/xrange.mdx b/redis/commands/streams/xrange.mdx
index 0bc243755..d5ad43765 100644
--- a/redis/commands/streams/xrange.mdx
+++ b/redis/commands/streams/xrange.mdx
@@ -41,9 +41,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -53,9 +53,9 @@ const redis = Redis.fromEnv();
 const result = await redis.xrange("mystream", "-", "+");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -65,9 +65,9 @@ result = redis.xrange("my-key", "-", "+")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -77,9 +77,9 @@ const result = await redis.xrange("my-key", "-", "+");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -91,9 +91,9 @@ const result = await client.xRange("my-key", "-", "+");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -104,9 +104,9 @@ result = client.xrange("my-key", "-", "+")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -133,9 +133,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -148,9 +148,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -166,6 +166,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/streams/xread.mdx b/redis/commands/streams/xread.mdx
index 6cf6b0c7c..2818a45a8 100644
--- a/redis/commands/streams/xread.mdx
+++ b/redis/commands/streams/xread.mdx
@@ -50,9 +50,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -62,9 +62,9 @@ const redis = Redis.fromEnv();
 const result = await redis.xread("mystream", "0-0");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -74,9 +74,9 @@ result = redis.xread({"my-key": "0-0"})
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -86,9 +86,9 @@ const result = await redis.xread("STREAMS", "my-key", "0-0");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -100,9 +100,9 @@ const result = await client.xRead({ key: "my-key", id: "0-0" });
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -113,9 +113,9 @@ result = client.xread({"my-key": "0-0"})
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -142,9 +142,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -157,9 +157,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -175,6 +175,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/streams/xreadgroup.mdx b/redis/commands/streams/xreadgroup.mdx
index 981c8f362..fa29f7ce8 100644
--- a/redis/commands/streams/xreadgroup.mdx
+++ b/redis/commands/streams/xreadgroup.mdx
@@ -53,9 +53,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -65,9 +65,9 @@ const redis = Redis.fromEnv();
 const result = await redis.xreadgroup("mygroup", "consumer1", "mystream", ">");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -77,9 +77,9 @@ result = redis.xreadgroup("workers", "worker-1", {"my-key": "0-0"})
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -89,9 +89,9 @@ const result = await redis.xreadgroup("GROUP", "workers", "worker-1", "STREAMS",
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -103,9 +103,9 @@ const result = await client.xReadGroup("workers", "worker-1", { key: "my-key", i
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -116,9 +116,9 @@ result = client.xreadgroup("workers", "worker-1", {"my-key": "0-0"})
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -145,9 +145,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -160,9 +160,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -183,6 +183,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/streams/xrevrange.mdx b/redis/commands/streams/xrevrange.mdx
index 3b75491d2..663e0c712 100644
--- a/redis/commands/streams/xrevrange.mdx
+++ b/redis/commands/streams/xrevrange.mdx
@@ -41,9 +41,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -53,9 +53,9 @@ const redis = Redis.fromEnv();
 const result = await redis.xrevrange("mystream", "+", "-");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -65,9 +65,9 @@ result = redis.xrevrange("my-key", "+", "-")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -77,9 +77,9 @@ const result = await redis.xrevrange("my-key", "+", "-");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -91,9 +91,9 @@ const result = await client.xRevRange("my-key", "+", "-");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -104,9 +104,9 @@ result = client.xrevrange("my-key", "+", "-")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -133,9 +133,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -148,9 +148,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -166,6 +166,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/streams/xtrim.mdx b/redis/commands/streams/xtrim.mdx
index 07c44996f..771ab0aaf 100644
--- a/redis/commands/streams/xtrim.mdx
+++ b/redis/commands/streams/xtrim.mdx
@@ -44,9 +44,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -60,9 +60,9 @@ const result = await redis.xtrim("mystream", {
 });
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -72,9 +72,9 @@ result = redis.xtrim("my-key", maxlen=100)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -84,9 +84,9 @@ const result = await redis.xtrim("my-key", "MAXLEN", "100");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -98,9 +98,9 @@ const result = await client.xTrim("my-key", "MAXLEN", 100);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -111,9 +111,9 @@ result = client.xtrim("my-key", maxlen=100)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -140,9 +140,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -155,9 +155,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -173,6 +173,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/string/append.mdx b/redis/commands/string/append.mdx
index b42702e65..ced6a4f9f 100644
--- a/redis/commands/string/append.mdx
+++ b/redis/commands/string/append.mdx
@@ -37,9 +37,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -50,9 +50,9 @@ await redis.append(key, "Hello");
 // returns 5
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -62,9 +62,9 @@ result = redis.append("my-key", "value")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -74,9 +74,9 @@ const result = await redis.append("my-key", "value");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -88,9 +88,9 @@ const result = await client.append("my-key", "value");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -101,9 +101,9 @@ result = client.append("my-key", "value")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -130,9 +130,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -145,9 +145,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -163,6 +163,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/string/decr.mdx b/redis/commands/string/decr.mdx
index 51030fbb0..25111b01f 100644
--- a/redis/commands/string/decr.mdx
+++ b/redis/commands/string/decr.mdx
@@ -36,9 +36,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -50,9 +50,9 @@ await redis.decr("key");
 // returns 5
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -62,9 +62,9 @@ result = redis.decr("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -74,9 +74,9 @@ const result = await redis.decr("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -88,9 +88,9 @@ const result = await client.decr("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -101,9 +101,9 @@ result = client.decr("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -130,9 +130,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -145,9 +145,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -163,6 +163,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/string/decrby.mdx b/redis/commands/string/decrby.mdx
index a087fae28..c5fc979ee 100644
--- a/redis/commands/string/decrby.mdx
+++ b/redis/commands/string/decrby.mdx
@@ -37,9 +37,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -51,9 +51,9 @@ await redis.decrby("key", 4);
 // returns 2
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -63,9 +63,9 @@ result = redis.decrby("my-key", 1)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -75,9 +75,9 @@ const result = await redis.decrby("my-key", "1");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -89,9 +89,9 @@ const result = await client.decrBy("my-key", 1);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -102,9 +102,9 @@ result = client.decrby("my-key", 1)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -131,9 +131,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -146,9 +146,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -164,6 +164,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/string/delex.mdx b/redis/commands/string/delex.mdx
index a9a4edb1e..3060f0f68 100644
--- a/redis/commands/string/delex.mdx
+++ b/redis/commands/string/delex.mdx
@@ -45,25 +45,25 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 <Note>
   This command is not supported yet in `upstash_redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -73,9 +73,9 @@ const result = await redis.call("DELEX", "lock:job-1", "IFEQ", "worker-1");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -87,9 +87,9 @@ const result = await client.delEx("lock:job-1", { condition: "IFEQ", matchValue:
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -100,9 +100,9 @@ result = client.execute_command("DELEX", "lock:job-1", "IFEQ", "worker-1")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -129,9 +129,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -144,9 +144,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -162,6 +162,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/string/digest.mdx b/redis/commands/string/digest.mdx
index b573069d0..1687c9921 100644
--- a/redis/commands/string/digest.mdx
+++ b/redis/commands/string/digest.mdx
@@ -43,25 +43,25 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 <Note>
   This command is not supported yet in `upstash_redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -71,9 +71,9 @@ const result = await redis.call("DIGEST", "lock:job-1");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -85,9 +85,9 @@ const result = await client.digest("lock:job-1");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -98,9 +98,9 @@ result = client.execute_command("DIGEST", "lock:job-1")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -127,9 +127,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -142,9 +142,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -160,6 +160,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/string/get.mdx b/redis/commands/string/get.mdx
index d64f4f879..5e44e151a 100644
--- a/redis/commands/string/get.mdx
+++ b/redis/commands/string/get.mdx
@@ -36,9 +36,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -57,9 +57,9 @@ if (!value) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -69,9 +69,9 @@ result = redis.get("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -81,9 +81,9 @@ const result = await redis.get("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -95,9 +95,9 @@ const result = await client.get("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -108,9 +108,9 @@ result = client.get("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -137,9 +137,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -152,9 +152,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -170,6 +170,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/string/getdel.mdx b/redis/commands/string/getdel.mdx
index 34f7ac8ca..5560dcadf 100644
--- a/redis/commands/string/getdel.mdx
+++ b/redis/commands/string/getdel.mdx
@@ -36,9 +36,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -53,9 +53,9 @@ await redis.getdel<MyType>("key");
 // returns {a: 1, b: "2"}
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -65,9 +65,9 @@ result = redis.getdel("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -77,9 +77,9 @@ const result = await redis.getdel("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -91,9 +91,9 @@ const result = await client.getDel("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -104,9 +104,9 @@ result = client.getdel("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -133,9 +133,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -148,9 +148,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -166,6 +166,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/string/getex.mdx b/redis/commands/string/getex.mdx
index 85327b234..85d88bcae 100644
--- a/redis/commands/string/getex.mdx
+++ b/redis/commands/string/getex.mdx
@@ -41,9 +41,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -53,9 +53,9 @@ const result = await redis.getex("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -65,9 +65,9 @@ result = redis.getex("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -77,9 +77,9 @@ const result = await redis.getex("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -91,9 +91,9 @@ const result = await client.getEx("my-key", { type: "PX", value: 1000 });
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -104,9 +104,9 @@ result = client.getex("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -133,9 +133,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -148,9 +148,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -166,6 +166,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/string/getrange.mdx b/redis/commands/string/getrange.mdx
index 8746a7f2c..45f8eec47 100644
--- a/redis/commands/string/getrange.mdx
+++ b/redis/commands/string/getrange.mdx
@@ -44,9 +44,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -56,9 +56,9 @@ const redis = Redis.fromEnv();
 const substring = await redis.getrange("key", 2, 4);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -68,9 +68,9 @@ result = redis.getrange("my-key", "0", "1")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -80,9 +80,9 @@ const result = await redis.getrange("my-key", "0", "1");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -94,9 +94,9 @@ const result = await client.getRange("my-key", 0, 1);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -107,9 +107,9 @@ result = client.getrange("my-key", "0", "1")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -136,9 +136,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -151,9 +151,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -169,6 +169,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/string/getset.mdx b/redis/commands/string/getset.mdx
index d28c0b720..a85359b67 100644
--- a/redis/commands/string/getset.mdx
+++ b/redis/commands/string/getset.mdx
@@ -43,9 +43,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -55,9 +55,9 @@ const redis = Redis.fromEnv();
 const oldValue = await redis.getset("key", newValue);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -67,9 +67,9 @@ result = redis.getset("my-key", "value")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -79,9 +79,9 @@ const result = await redis.getset("my-key", "value");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -93,9 +93,9 @@ const result = await client.getSet("my-key", "value");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -106,9 +106,9 @@ result = client.getset("my-key", "value")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -135,9 +135,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -150,9 +150,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -168,6 +168,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/string/incr.mdx b/redis/commands/string/incr.mdx
index c2d71c960..aa111a67f 100644
--- a/redis/commands/string/incr.mdx
+++ b/redis/commands/string/incr.mdx
@@ -38,9 +38,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -52,9 +52,9 @@ await redis.incr("key");
 // returns 7
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -64,9 +64,9 @@ result = redis.incr("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -76,9 +76,9 @@ const result = await redis.incr("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -90,9 +90,9 @@ const result = await client.incr("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -103,9 +103,9 @@ result = client.incr("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -132,9 +132,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -147,9 +147,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -165,6 +165,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/string/incrby.mdx b/redis/commands/string/incrby.mdx
index d46933881..784a22c22 100644
--- a/redis/commands/string/incrby.mdx
+++ b/redis/commands/string/incrby.mdx
@@ -39,9 +39,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -53,9 +53,9 @@ await redis.incrby("key", 4);
 // returns 10
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -65,9 +65,9 @@ result = redis.incrby("my-key", 1)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -77,9 +77,9 @@ const result = await redis.incrby("my-key", "1");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -91,9 +91,9 @@ const result = await client.incrBy("my-key", 1);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -104,9 +104,9 @@ result = client.incrby("my-key", 1)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -133,9 +133,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -148,9 +148,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -166,6 +166,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/string/incrbyfloat.mdx b/redis/commands/string/incrbyfloat.mdx
index 14ea0909f..030b56133 100644
--- a/redis/commands/string/incrbyfloat.mdx
+++ b/redis/commands/string/incrbyfloat.mdx
@@ -43,9 +43,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -57,9 +57,9 @@ await redis.incrbyfloat("key", 4,5);
 // returns 10.5
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -69,9 +69,9 @@ result = redis.incrbyfloat("my-key", 1.5)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -81,9 +81,9 @@ const result = await redis.incrbyfloat("my-key", "1.5");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -95,9 +95,9 @@ const result = await client.incrByFloat("my-key", 1.5);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -108,9 +108,9 @@ result = client.incrbyfloat("my-key", 1.5)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -137,9 +137,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -152,9 +152,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -170,6 +170,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/string/mget.mdx b/redis/commands/string/mget.mdx
index 5df53bef9..57ee65793 100644
--- a/redis/commands/string/mget.mdx
+++ b/redis/commands/string/mget.mdx
@@ -38,9 +38,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -55,9 +55,9 @@ const values = await redis.mget<MyType>("key1", "key2", "key3");
 // values.length -> 3
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -67,9 +67,9 @@ result = redis.mget("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -79,9 +79,9 @@ const result = await redis.mget("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -93,9 +93,9 @@ const result = await client.mGet(["my-key"]);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -106,9 +106,9 @@ result = client.mget("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -135,9 +135,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -150,9 +150,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -168,6 +168,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/string/mset.mdx b/redis/commands/string/mset.mdx
index 444266c64..421e175d1 100644
--- a/redis/commands/string/mset.mdx
+++ b/redis/commands/string/mset.mdx
@@ -38,9 +38,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -54,9 +54,9 @@ await redis.mset({
 });
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -66,9 +66,9 @@ result = redis.mset({"my-key": "value"})
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -78,9 +78,9 @@ const result = await redis.mset("my-key", "value");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -92,9 +92,9 @@ const result = await client.mSet({ "my-key": "value" });
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -105,9 +105,9 @@ result = client.mset({"my-key": "value"})
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -134,9 +134,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -149,9 +149,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -167,6 +167,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/string/msetnx.mdx b/redis/commands/string/msetnx.mdx
index 47fcb2bb0..f4b5a53b5 100644
--- a/redis/commands/string/msetnx.mdx
+++ b/redis/commands/string/msetnx.mdx
@@ -36,9 +36,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -51,9 +51,9 @@ redis.msetnx({
 })
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -63,9 +63,9 @@ result = redis.msetnx({"my-key": "value"})
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -75,9 +75,9 @@ const result = await redis.msetnx("my-key", "value");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -89,9 +89,9 @@ const result = await client.mSetNX({ "my-key": "value" });
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -102,9 +102,9 @@ result = client.msetnx({"my-key": "value"})
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -131,9 +131,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -146,9 +146,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -164,6 +164,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/string/psetex.mdx b/redis/commands/string/psetex.mdx
index 898aa696d..f4022f007 100644
--- a/redis/commands/string/psetex.mdx
+++ b/redis/commands/string/psetex.mdx
@@ -44,9 +44,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -56,9 +56,9 @@ const result = await redis.psetex("my-key", 1000, "value");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -68,9 +68,9 @@ result = redis.psetex("my-key", 1000, "value")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -80,9 +80,9 @@ const result = await redis.psetex("my-key", "1000", "value");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -94,9 +94,9 @@ const result = await client.pSetEx("my-key", 1000, "value");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -107,9 +107,9 @@ result = client.psetex("my-key", 1000, "value")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -137,9 +137,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -152,9 +152,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -170,6 +170,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/string/set.mdx b/redis/commands/string/set.mdx
index 363247282..27d6ec5fb 100644
--- a/redis/commands/string/set.mdx
+++ b/redis/commands/string/set.mdx
@@ -55,9 +55,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -67,9 +67,9 @@ const redis = Redis.fromEnv();
 await redis.set("my-key", {my: "value"});
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -79,9 +79,9 @@ result = redis.set("my-key", "value")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -91,9 +91,9 @@ const result = await redis.set("my-key", "value");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -105,9 +105,9 @@ const result = await client.set("my-key", "value");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -118,9 +118,9 @@ result = client.set("my-key", "value")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -147,9 +147,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -162,9 +162,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -180,6 +180,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/string/setex.mdx b/redis/commands/string/setex.mdx
index bfb2bcc15..2cd69f79f 100644
--- a/redis/commands/string/setex.mdx
+++ b/redis/commands/string/setex.mdx
@@ -44,9 +44,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -56,9 +56,9 @@ const result = await redis.setex("my-key", 1000, "value");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -68,9 +68,9 @@ result = redis.setex("my-key", 1000, "value")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -80,9 +80,9 @@ const result = await redis.setex("my-key", "1000", "value");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -94,9 +94,9 @@ const result = await client.setEx("my-key", 1000, "value");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -107,9 +107,9 @@ result = client.setex("my-key", 1000, "value")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -137,9 +137,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -152,9 +152,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -170,6 +170,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/string/setnx.mdx b/redis/commands/string/setnx.mdx
index 10ea6f02e..ed946a761 100644
--- a/redis/commands/string/setnx.mdx
+++ b/redis/commands/string/setnx.mdx
@@ -43,9 +43,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -55,9 +55,9 @@ const result = await redis.setnx("my-key", "value");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -67,9 +67,9 @@ result = redis.setnx("my-key", "value")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -79,9 +79,9 @@ const result = await redis.setnx("my-key", "value");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -93,9 +93,9 @@ const result = await client.setNX("my-key", "value");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -106,9 +106,9 @@ result = client.setnx("my-key", "value")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -135,9 +135,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -150,9 +150,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -168,6 +168,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/string/setrange.mdx b/redis/commands/string/setrange.mdx
index 4aedf935a..158c5512f 100644
--- a/redis/commands/string/setrange.mdx
+++ b/redis/commands/string/setrange.mdx
@@ -40,9 +40,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -56,9 +56,9 @@ console.log(length); // 10
 // The value of "key" is now "helloredis"
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -68,9 +68,9 @@ result = redis.setrange("my-key", 0, "value")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -80,9 +80,9 @@ const result = await redis.setrange("my-key", "0", "value");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -94,9 +94,9 @@ const result = await client.setRange("my-key", 0, "value");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -107,9 +107,9 @@ result = client.setrange("my-key", 0, "value")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -136,9 +136,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -151,9 +151,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -169,6 +169,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/string/strlen.mdx b/redis/commands/string/strlen.mdx
index d85d81b8b..cbe82dcbe 100644
--- a/redis/commands/string/strlen.mdx
+++ b/redis/commands/string/strlen.mdx
@@ -36,9 +36,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -50,9 +50,9 @@ const length = await redis.strlen("key");
 console.log(length); // 10
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -62,9 +62,9 @@ result = redis.strlen("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -74,9 +74,9 @@ const result = await redis.strlen("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -88,9 +88,9 @@ const result = await client.strLen("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -101,9 +101,9 @@ result = client.strlen("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -130,9 +130,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -145,9 +145,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -163,6 +163,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/transactions/discard.mdx b/redis/commands/transactions/discard.mdx
index bd811ebc8..19d094edf 100644
--- a/redis/commands/transactions/discard.mdx
+++ b/redis/commands/transactions/discard.mdx
@@ -40,9 +40,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -53,9 +53,9 @@ await client.set("balance", "100");
 await client.discard();
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -66,9 +66,9 @@ await client.sendCommand(["SET", "balance", "100"]);
 await client.sendCommand(["DISCARD"]);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -80,9 +80,9 @@ with client.pipeline(transaction=True) as pipe:
     pipe.reset()
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 ctx := context.Background()
@@ -95,9 +95,9 @@ pipe.Set(ctx, "balance", "100", 0)
 pipe.Discard()
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -111,9 +111,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")));
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -124,6 +124,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/transactions/exec.mdx b/redis/commands/transactions/exec.mdx
index 0b0e2c2a5..3b21551d3 100644
--- a/redis/commands/transactions/exec.mdx
+++ b/redis/commands/transactions/exec.mdx
@@ -42,9 +42,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -53,9 +53,9 @@ const client = new Redis(process.env.REDIS_URL!);
 const result = await client.multi().set("balance", "100").exec();
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -64,9 +64,9 @@ const client = await createClient({ url: process.env.REDIS_URL }).connect();
 const result = await client.multi().set("balance", "100").exec();
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -77,9 +77,9 @@ with client.pipeline(transaction=True) as pipe:
     result = pipe.set("balance", "100").execute()
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 ctx := context.Background()
@@ -93,9 +93,9 @@ result, err := pipe.Exec(ctx)
 if err != nil { panic(err) }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -109,9 +109,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")));
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -128,6 +128,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/transactions/multi.mdx b/redis/commands/transactions/multi.mdx
index 149f2abb2..e02e9b21e 100644
--- a/redis/commands/transactions/multi.mdx
+++ b/redis/commands/transactions/multi.mdx
@@ -42,9 +42,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -53,9 +53,9 @@ const client = new Redis(process.env.REDIS_URL!);
 const result = await client.multi().set("balance", "100").exec();
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -64,9 +64,9 @@ const client = await createClient({ url: process.env.REDIS_URL }).connect();
 const result = await client.multi().set("balance", "100").exec();
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -77,9 +77,9 @@ with client.pipeline(transaction=True) as pipe:
     result = pipe.set("balance", "100").execute()
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 ctx := context.Background()
@@ -93,9 +93,9 @@ result, err := pipe.Exec(ctx)
 if err != nil { panic(err) }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -109,9 +109,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")));
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -128,6 +128,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/transactions/unwatch.mdx b/redis/commands/transactions/unwatch.mdx
index 457bd1ac0..243c7126b 100644
--- a/redis/commands/transactions/unwatch.mdx
+++ b/redis/commands/transactions/unwatch.mdx
@@ -40,9 +40,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -52,9 +52,9 @@ await client.watch("balance");
 await client.unwatch();
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -64,9 +64,9 @@ await client.watch("balance");
 await client.unwatch();
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -78,9 +78,9 @@ with client.pipeline() as pipe:
     pipe.unwatch()
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 ctx := context.Background()
@@ -94,9 +94,9 @@ err = client.Watch(ctx, func(tx *redis.Tx) error {
 if err != nil { panic(err) }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -108,9 +108,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -125,6 +125,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
diff --git a/redis/commands/transactions/watch.mdx b/redis/commands/transactions/watch.mdx
index 0c10e2b6e..87bf0e041 100644
--- a/redis/commands/transactions/watch.mdx
+++ b/redis/commands/transactions/watch.mdx
@@ -44,9 +44,9 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -56,9 +56,9 @@ await client.watch("balance");
 const result = await client.multi().set("balance", "100").exec();
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -68,9 +68,9 @@ await client.watch("balance");
 const result = await client.multi().set("balance", "100").exec();
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -84,9 +84,9 @@ with client.pipeline() as pipe:
     result = pipe.execute()
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 ctx := context.Background()
@@ -104,9 +104,9 @@ err = client.Watch(ctx, func(tx *redis.Tx) error {
 if err != nil { panic(err) }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -122,9 +122,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -139,6 +139,6 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>

From af9127213b6b925f1b962155f3e84cb656888073 Mon Sep 17 00:00:00 2001
From: Mehmet Dogan <mehmet@dogan.io>
Date: Thu, 13 Aug 2026 15:07:42 +0300
Subject: [PATCH 10/12] Add redis-cli

---
 redis/commands/bitmap/bitcount.mdx             |  8 ++++++++
 redis/commands/bitmap/bitfield-ro.mdx          |  8 ++++++++
 redis/commands/bitmap/bitfield.mdx             |  8 ++++++++
 redis/commands/bitmap/bitop.mdx                |  8 ++++++++
 redis/commands/bitmap/bitpos.mdx               |  8 ++++++++
 redis/commands/bitmap/getbit.mdx               |  8 ++++++++
 redis/commands/bitmap/setbit.mdx               |  8 ++++++++
 redis/commands/connection/auth.mdx             |  8 ++++++++
 redis/commands/connection/client-getname.mdx   |  8 ++++++++
 redis/commands/connection/client-id.mdx        |  8 ++++++++
 redis/commands/connection/client-info.mdx      |  8 ++++++++
 redis/commands/connection/client-list.mdx      |  8 ++++++++
 redis/commands/connection/client-setinfo.mdx   |  8 ++++++++
 redis/commands/connection/client-setname.mdx   |  8 ++++++++
 redis/commands/connection/echo.mdx             |  8 ++++++++
 redis/commands/connection/hello.mdx            |  8 ++++++++
 redis/commands/connection/ping.mdx             |  8 ++++++++
 redis/commands/connection/quit.mdx             |  8 ++++++++
 redis/commands/connection/reset.mdx            |  8 ++++++++
 redis/commands/connection/select.mdx           |  8 ++++++++
 redis/commands/functions/fcall-ro.mdx          |  8 ++++++++
 redis/commands/functions/fcall.mdx             |  8 ++++++++
 redis/commands/functions/function-delete.mdx   |  8 ++++++++
 redis/commands/functions/function-flush.mdx    |  8 ++++++++
 redis/commands/functions/function-kill.mdx     |  8 ++++++++
 redis/commands/functions/function-list.mdx     |  8 ++++++++
 redis/commands/functions/function-load.mdx     |  8 ++++++++
 redis/commands/functions/function-stats.mdx    |  8 ++++++++
 redis/commands/generic/copy.mdx                |  8 ++++++++
 redis/commands/generic/del.mdx                 |  8 ++++++++
 redis/commands/generic/dump.mdx                |  8 ++++++++
 redis/commands/generic/exists.mdx              |  8 ++++++++
 redis/commands/generic/expire.mdx              |  8 ++++++++
 redis/commands/generic/expireat.mdx            |  8 ++++++++
 redis/commands/generic/expiretime.mdx          |  8 ++++++++
 redis/commands/generic/keys.mdx                |  8 ++++++++
 redis/commands/generic/memory-usage.mdx        |  8 ++++++++
 redis/commands/generic/persist.mdx             |  8 ++++++++
 redis/commands/generic/pexpire.mdx             |  8 ++++++++
 redis/commands/generic/pexpireat.mdx           |  8 ++++++++
 redis/commands/generic/pexpiretime.mdx         |  8 ++++++++
 redis/commands/generic/pttl.mdx                |  8 ++++++++
 redis/commands/generic/randomkey.mdx           |  8 ++++++++
 redis/commands/generic/rename.mdx              |  8 ++++++++
 redis/commands/generic/renamenx.mdx            |  8 ++++++++
 redis/commands/generic/restore.mdx             |  8 ++++++++
 redis/commands/generic/scan.mdx                |  8 ++++++++
 redis/commands/generic/touch.mdx               |  8 ++++++++
 redis/commands/generic/ttl.mdx                 |  8 ++++++++
 redis/commands/generic/type.mdx                |  8 ++++++++
 redis/commands/generic/unlink.mdx              |  8 ++++++++
 redis/commands/generic/wait.mdx                |  8 ++++++++
 redis/commands/generic/waitaof.mdx             |  8 ++++++++
 redis/commands/geo/geoadd.mdx                  |  8 ++++++++
 redis/commands/geo/geodist.mdx                 |  8 ++++++++
 redis/commands/geo/geohash.mdx                 |  8 ++++++++
 redis/commands/geo/geopos.mdx                  |  8 ++++++++
 redis/commands/geo/georadius-ro.mdx            |  8 ++++++++
 redis/commands/geo/georadius.mdx               |  8 ++++++++
 redis/commands/geo/georadiusbymember-ro.mdx    |  8 ++++++++
 redis/commands/geo/georadiusbymember.mdx       |  8 ++++++++
 redis/commands/geo/geosearch.mdx               |  8 ++++++++
 redis/commands/geo/geosearchstore.mdx          |  8 ++++++++
 redis/commands/hash/hdel.mdx                   |  8 ++++++++
 redis/commands/hash/hexists.mdx                |  8 ++++++++
 redis/commands/hash/hexpire.mdx                |  8 ++++++++
 redis/commands/hash/hexpireat.mdx              |  8 ++++++++
 redis/commands/hash/hexpiretime.mdx            |  8 ++++++++
 redis/commands/hash/hget.mdx                   |  8 ++++++++
 redis/commands/hash/hgetall.mdx                |  8 ++++++++
 redis/commands/hash/hgetdel.mdx                |  8 ++++++++
 redis/commands/hash/hgetex.mdx                 |  8 ++++++++
 redis/commands/hash/hincrby.mdx                |  8 ++++++++
 redis/commands/hash/hincrbyfloat.mdx           |  8 ++++++++
 redis/commands/hash/hkeys.mdx                  |  8 ++++++++
 redis/commands/hash/hlen.mdx                   |  8 ++++++++
 redis/commands/hash/hmget.mdx                  |  8 ++++++++
 redis/commands/hash/hmset.mdx                  |  8 ++++++++
 redis/commands/hash/hpersist.mdx               |  8 ++++++++
 redis/commands/hash/hpexpire.mdx               |  8 ++++++++
 redis/commands/hash/hpexpireat.mdx             |  8 ++++++++
 redis/commands/hash/hpexpiretime.mdx           |  8 ++++++++
 redis/commands/hash/hpttl.mdx                  |  8 ++++++++
 redis/commands/hash/hrandfield.mdx             |  8 ++++++++
 redis/commands/hash/hscan.mdx                  |  8 ++++++++
 redis/commands/hash/hset.mdx                   |  8 ++++++++
 redis/commands/hash/hsetex.mdx                 |  8 ++++++++
 redis/commands/hash/hsetnx.mdx                 |  8 ++++++++
 redis/commands/hash/hstrlen.mdx                |  8 ++++++++
 redis/commands/hash/httl.mdx                   |  8 ++++++++
 redis/commands/hash/hvals.mdx                  |  8 ++++++++
 redis/commands/hyperloglog/pfadd.mdx           |  8 ++++++++
 redis/commands/hyperloglog/pfcount.mdx         |  8 ++++++++
 redis/commands/hyperloglog/pfmerge.mdx         |  8 ++++++++
 redis/commands/json/json-arrappend.mdx         |  8 ++++++++
 redis/commands/json/json-arrindex.mdx          |  8 ++++++++
 redis/commands/json/json-arrinsert.mdx         |  8 ++++++++
 redis/commands/json/json-arrlen.mdx            |  8 ++++++++
 redis/commands/json/json-arrpop.mdx            |  8 ++++++++
 redis/commands/json/json-arrtrim.mdx           |  8 ++++++++
 redis/commands/json/json-clear.mdx             |  8 ++++++++
 redis/commands/json/json-debug.mdx             |  8 ++++++++
 redis/commands/json/json-del.mdx               |  8 ++++++++
 redis/commands/json/json-forget.mdx            |  8 ++++++++
 redis/commands/json/json-get.mdx               |  8 ++++++++
 redis/commands/json/json-merge.mdx             |  8 ++++++++
 redis/commands/json/json-mget.mdx              |  8 ++++++++
 redis/commands/json/json-mset.mdx              |  8 ++++++++
 redis/commands/json/json-numincrby.mdx         |  8 ++++++++
 redis/commands/json/json-nummultby.mdx         |  8 ++++++++
 redis/commands/json/json-objkeys.mdx           |  8 ++++++++
 redis/commands/json/json-objlen.mdx            |  8 ++++++++
 redis/commands/json/json-resp.mdx              |  8 ++++++++
 redis/commands/json/json-set.mdx               |  8 ++++++++
 redis/commands/json/json-strappend.mdx         |  8 ++++++++
 redis/commands/json/json-strlen.mdx            |  8 ++++++++
 redis/commands/json/json-toggle.mdx            |  8 ++++++++
 redis/commands/json/json-type.mdx              |  8 ++++++++
 redis/commands/list/blmove.mdx                 |  8 ++++++++
 redis/commands/list/blmpop.mdx                 |  8 ++++++++
 redis/commands/list/blpop.mdx                  |  8 ++++++++
 redis/commands/list/brpop.mdx                  |  8 ++++++++
 redis/commands/list/brpoplpush.mdx             |  8 ++++++++
 redis/commands/list/lindex.mdx                 |  8 ++++++++
 redis/commands/list/linsert.mdx                |  8 ++++++++
 redis/commands/list/llen.mdx                   |  8 ++++++++
 redis/commands/list/lmove.mdx                  |  8 ++++++++
 redis/commands/list/lmpop.mdx                  |  8 ++++++++
 redis/commands/list/lpop.mdx                   |  8 ++++++++
 redis/commands/list/lpos.mdx                   |  8 ++++++++
 redis/commands/list/lpush.mdx                  |  8 ++++++++
 redis/commands/list/lpushx.mdx                 |  8 ++++++++
 redis/commands/list/lrange.mdx                 |  8 ++++++++
 redis/commands/list/lrem.mdx                   |  8 ++++++++
 redis/commands/list/lset.mdx                   |  8 ++++++++
 redis/commands/list/ltrim.mdx                  |  8 ++++++++
 redis/commands/list/rpop.mdx                   |  8 ++++++++
 redis/commands/list/rpoplpush.mdx              |  8 ++++++++
 redis/commands/list/rpush.mdx                  |  8 ++++++++
 redis/commands/list/rpushx.mdx                 |  8 ++++++++
 redis/commands/pub-sub/psubscribe.mdx          |  8 ++++++++
 redis/commands/pub-sub/publish.mdx             |  8 ++++++++
 redis/commands/pub-sub/pubsub.mdx              |  8 ++++++++
 redis/commands/pub-sub/punsubscribe.mdx        |  8 ++++++++
 redis/commands/pub-sub/subscribe.mdx           |  8 ++++++++
 redis/commands/pub-sub/unsubscribe.mdx         |  8 ++++++++
 redis/commands/scripting/eval-ro.mdx           |  8 ++++++++
 redis/commands/scripting/eval.mdx              |  8 ++++++++
 redis/commands/scripting/evalsha-ro.mdx        |  8 ++++++++
 redis/commands/scripting/evalsha.mdx           |  8 ++++++++
 redis/commands/scripting/script-exists.mdx     |  8 ++++++++
 redis/commands/scripting/script-flush.mdx      |  8 ++++++++
 redis/commands/scripting/script-kill.mdx       |  8 ++++++++
 redis/commands/scripting/script-load.mdx       |  8 ++++++++
 redis/commands/search/search-aggregate.mdx     | 16 ++++++++--------
 redis/commands/search/search-aliasadd.mdx      | 16 ++++++++--------
 redis/commands/search/search-aliasdel.mdx      | 16 ++++++++--------
 redis/commands/search/search-count.mdx         | 16 ++++++++--------
 redis/commands/search/search-create.mdx        | 16 ++++++++--------
 redis/commands/search/search-describe.mdx      | 16 ++++++++--------
 redis/commands/search/search-drop.mdx          | 16 ++++++++--------
 redis/commands/search/search-listaliases.mdx   | 16 ++++++++--------
 redis/commands/search/search-listindexes.mdx   | 16 ++++++++--------
 redis/commands/search/search-query.mdx         | 16 ++++++++--------
 redis/commands/search/search-reindex.mdx       |  2 +-
 redis/commands/search/search-waitindexing.mdx  | 16 ++++++++--------
 redis/commands/server/acl.mdx                  |  8 ++++++++
 redis/commands/server/command.mdx              |  8 ++++++++
 redis/commands/server/config-get.mdx           |  8 ++++++++
 redis/commands/server/config-set.mdx           |  8 ++++++++
 redis/commands/server/dbsize.mdx               |  8 ++++++++
 redis/commands/server/flushall.mdx             |  8 ++++++++
 redis/commands/server/flushdb.mdx              |  8 ++++++++
 redis/commands/server/info.mdx                 |  8 ++++++++
 redis/commands/server/monitor.mdx              |  8 ++++++++
 redis/commands/server/time.mdx                 |  8 ++++++++
 redis/commands/set/sadd.mdx                    |  8 ++++++++
 redis/commands/set/scard.mdx                   |  8 ++++++++
 redis/commands/set/sdiff.mdx                   |  8 ++++++++
 redis/commands/set/sdiffstore.mdx              |  8 ++++++++
 redis/commands/set/sinter.mdx                  |  8 ++++++++
 redis/commands/set/sintercard.mdx              |  8 ++++++++
 redis/commands/set/sinterstore.mdx             |  8 ++++++++
 redis/commands/set/sismember.mdx               |  8 ++++++++
 redis/commands/set/smembers.mdx                |  8 ++++++++
 redis/commands/set/smismember.mdx              |  8 ++++++++
 redis/commands/set/smove.mdx                   |  8 ++++++++
 redis/commands/set/spop.mdx                    |  8 ++++++++
 redis/commands/set/srandmember.mdx             |  8 ++++++++
 redis/commands/set/srem.mdx                    |  8 ++++++++
 redis/commands/set/sscan.mdx                   |  8 ++++++++
 redis/commands/set/sunion.mdx                  |  8 ++++++++
 redis/commands/set/sunionstore.mdx             |  8 ++++++++
 redis/commands/sorted-set/bzmpop.mdx           |  8 ++++++++
 redis/commands/sorted-set/bzpopmax.mdx         |  8 ++++++++
 redis/commands/sorted-set/bzpopmin.mdx         |  8 ++++++++
 redis/commands/sorted-set/zadd.mdx             |  8 ++++++++
 redis/commands/sorted-set/zcard.mdx            |  8 ++++++++
 redis/commands/sorted-set/zcount.mdx           |  8 ++++++++
 redis/commands/sorted-set/zdiff.mdx            |  8 ++++++++
 redis/commands/sorted-set/zdiffstore.mdx       |  8 ++++++++
 redis/commands/sorted-set/zincrby.mdx          |  8 ++++++++
 redis/commands/sorted-set/zinter.mdx           |  8 ++++++++
 redis/commands/sorted-set/zintercard.mdx       |  8 ++++++++
 redis/commands/sorted-set/zinterstore.mdx      |  8 ++++++++
 redis/commands/sorted-set/zlexcount.mdx        |  8 ++++++++
 redis/commands/sorted-set/zmpop.mdx            |  8 ++++++++
 redis/commands/sorted-set/zmscore.mdx          |  8 ++++++++
 redis/commands/sorted-set/zpopmax.mdx          |  8 ++++++++
 redis/commands/sorted-set/zpopmin.mdx          |  8 ++++++++
 redis/commands/sorted-set/zrandmember.mdx      |  8 ++++++++
 redis/commands/sorted-set/zrange.mdx           |  8 ++++++++
 redis/commands/sorted-set/zrangebylex.mdx      |  8 ++++++++
 redis/commands/sorted-set/zrangebyscore.mdx    |  8 ++++++++
 redis/commands/sorted-set/zrangestore.mdx      |  8 ++++++++
 redis/commands/sorted-set/zrank.mdx            |  8 ++++++++
 redis/commands/sorted-set/zrem.mdx             |  8 ++++++++
 redis/commands/sorted-set/zremrangebylex.mdx   |  8 ++++++++
 redis/commands/sorted-set/zremrangebyrank.mdx  |  8 ++++++++
 redis/commands/sorted-set/zremrangebyscore.mdx |  8 ++++++++
 redis/commands/sorted-set/zrevrange.mdx        |  8 ++++++++
 redis/commands/sorted-set/zrevrangebylex.mdx   |  8 ++++++++
 redis/commands/sorted-set/zrevrangebyscore.mdx |  8 ++++++++
 redis/commands/sorted-set/zrevrank.mdx         |  8 ++++++++
 redis/commands/sorted-set/zscan.mdx            |  8 ++++++++
 redis/commands/sorted-set/zscore.mdx           |  8 ++++++++
 redis/commands/sorted-set/zunion.mdx           |  8 ++++++++
 redis/commands/sorted-set/zunionstore.mdx      |  8 ++++++++
 redis/commands/streams/xack.mdx                |  8 ++++++++
 redis/commands/streams/xackdel.mdx             |  8 ++++++++
 redis/commands/streams/xadd.mdx                |  8 ++++++++
 redis/commands/streams/xautoclaim.mdx          |  8 ++++++++
 redis/commands/streams/xclaim.mdx              |  8 ++++++++
 redis/commands/streams/xdel.mdx                |  8 ++++++++
 redis/commands/streams/xdelex.mdx              |  8 ++++++++
 redis/commands/streams/xgroup.mdx              |  8 ++++++++
 redis/commands/streams/xinfo-consumers.mdx     |  8 ++++++++
 redis/commands/streams/xinfo-groups.mdx        |  8 ++++++++
 redis/commands/streams/xinfo-stream.mdx        |  8 ++++++++
 redis/commands/streams/xlen.mdx                |  8 ++++++++
 redis/commands/streams/xpending.mdx            |  8 ++++++++
 redis/commands/streams/xrange.mdx              |  8 ++++++++
 redis/commands/streams/xread.mdx               |  8 ++++++++
 redis/commands/streams/xreadgroup.mdx          |  8 ++++++++
 redis/commands/streams/xrevrange.mdx           |  8 ++++++++
 redis/commands/streams/xtrim.mdx               |  8 ++++++++
 redis/commands/string/append.mdx               |  8 ++++++++
 redis/commands/string/decr.mdx                 |  8 ++++++++
 redis/commands/string/decrby.mdx               |  8 ++++++++
 redis/commands/string/delex.mdx                |  8 ++++++++
 redis/commands/string/digest.mdx               |  8 ++++++++
 redis/commands/string/get.mdx                  |  8 ++++++++
 redis/commands/string/getdel.mdx               |  8 ++++++++
 redis/commands/string/getex.mdx                |  8 ++++++++
 redis/commands/string/getrange.mdx             |  8 ++++++++
 redis/commands/string/getset.mdx               |  8 ++++++++
 redis/commands/string/incr.mdx                 |  8 ++++++++
 redis/commands/string/incrby.mdx               |  8 ++++++++
 redis/commands/string/incrbyfloat.mdx          |  8 ++++++++
 redis/commands/string/mget.mdx                 |  8 ++++++++
 redis/commands/string/mset.mdx                 |  8 ++++++++
 redis/commands/string/msetnx.mdx               |  8 ++++++++
 redis/commands/string/psetex.mdx               |  8 ++++++++
 redis/commands/string/set.mdx                  |  8 ++++++++
 redis/commands/string/setex.mdx                |  8 ++++++++
 redis/commands/string/setnx.mdx                |  8 ++++++++
 redis/commands/string/setrange.mdx             |  8 ++++++++
 redis/commands/string/strlen.mdx               |  8 ++++++++
 redis/commands/transactions/discard.mdx        | 10 ++++++++++
 redis/commands/transactions/exec.mdx           | 10 ++++++++++
 redis/commands/transactions/multi.mdx          | 10 ++++++++++
 redis/commands/transactions/unwatch.mdx        |  8 ++++++++
 redis/commands/transactions/watch.mdx          |  8 ++++++++
 273 files changed, 2183 insertions(+), 89 deletions(-)

diff --git a/redis/commands/bitmap/bitcount.mdx b/redis/commands/bitmap/bitcount.mdx
index a529b8f0e..5e15a76cf 100644
--- a/redis/commands/bitmap/bitcount.mdx
+++ b/redis/commands/bitmap/bitcount.mdx
@@ -41,6 +41,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+BITCOUNT my-key
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/bitmap/bitfield-ro.mdx b/redis/commands/bitmap/bitfield-ro.mdx
index 68f9a01cf..db72fb150 100644
--- a/redis/commands/bitmap/bitfield-ro.mdx
+++ b/redis/commands/bitmap/bitfield-ro.mdx
@@ -39,6 +39,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+BITFIELD_RO my-key GET u8 0
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
diff --git a/redis/commands/bitmap/bitfield.mdx b/redis/commands/bitmap/bitfield.mdx
index ece8c18d9..0420236b6 100644
--- a/redis/commands/bitmap/bitfield.mdx
+++ b/redis/commands/bitmap/bitfield.mdx
@@ -52,6 +52,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+BITFIELD my-key GET u8 0
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/bitmap/bitop.mdx b/redis/commands/bitmap/bitop.mdx
index d42da5c34..11868326c 100644
--- a/redis/commands/bitmap/bitop.mdx
+++ b/redis/commands/bitmap/bitop.mdx
@@ -44,6 +44,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+BITOP AND destination-key source-key-1 source-key-2
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/bitmap/bitpos.mdx b/redis/commands/bitmap/bitpos.mdx
index a5e775f9f..afa0fe76d 100644
--- a/redis/commands/bitmap/bitpos.mdx
+++ b/redis/commands/bitmap/bitpos.mdx
@@ -42,6 +42,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+BITPOS my-key 1
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/bitmap/getbit.mdx b/redis/commands/bitmap/getbit.mdx
index dc35cef63..16ada3381 100644
--- a/redis/commands/bitmap/getbit.mdx
+++ b/redis/commands/bitmap/getbit.mdx
@@ -39,6 +39,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+GETBIT my-key 0
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/bitmap/setbit.mdx b/redis/commands/bitmap/setbit.mdx
index 1c51b9177..b3b546987 100644
--- a/redis/commands/bitmap/setbit.mdx
+++ b/redis/commands/bitmap/setbit.mdx
@@ -42,6 +42,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+SETBIT my-key 0 1
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/connection/auth.mdx b/redis/commands/connection/auth.mdx
index 8f75eff82..cc2d683c4 100644
--- a/redis/commands/connection/auth.mdx
+++ b/redis/commands/connection/auth.mdx
@@ -43,6 +43,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+AUTH password
+```
+
+</Accordion>
+
 <Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/connection/client-getname.mdx b/redis/commands/connection/client-getname.mdx
index 1be19f851..bebd9289a 100644
--- a/redis/commands/connection/client-getname.mdx
+++ b/redis/commands/connection/client-getname.mdx
@@ -41,6 +41,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+CLIENT GETNAME
+```
+
+</Accordion>
+
 <Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/connection/client-id.mdx b/redis/commands/connection/client-id.mdx
index 89ce44a60..ecaa099c3 100644
--- a/redis/commands/connection/client-id.mdx
+++ b/redis/commands/connection/client-id.mdx
@@ -41,6 +41,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+CLIENT ID
+```
+
+</Accordion>
+
 <Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/connection/client-info.mdx b/redis/commands/connection/client-info.mdx
index fd7d33881..ed6200823 100644
--- a/redis/commands/connection/client-info.mdx
+++ b/redis/commands/connection/client-info.mdx
@@ -41,6 +41,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+CLIENT INFO
+```
+
+</Accordion>
+
 <Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/connection/client-list.mdx b/redis/commands/connection/client-list.mdx
index 23e58f705..ee051f3d2 100644
--- a/redis/commands/connection/client-list.mdx
+++ b/redis/commands/connection/client-list.mdx
@@ -41,6 +41,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+CLIENT LIST
+```
+
+</Accordion>
+
 <Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/connection/client-setinfo.mdx b/redis/commands/connection/client-setinfo.mdx
index 88134d015..00bb6adb1 100644
--- a/redis/commands/connection/client-setinfo.mdx
+++ b/redis/commands/connection/client-setinfo.mdx
@@ -44,6 +44,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+CLIENT SETINFO LIB-NAME my-client
+```
+
+</Accordion>
+
 <Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/connection/client-setname.mdx b/redis/commands/connection/client-setname.mdx
index 6c0c8f06c..0656e902b 100644
--- a/redis/commands/connection/client-setname.mdx
+++ b/redis/commands/connection/client-setname.mdx
@@ -43,6 +43,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+CLIENT SETNAME worker-1
+```
+
+</Accordion>
+
 <Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/connection/echo.mdx b/redis/commands/connection/echo.mdx
index 7b0e6a314..ca0522a52 100644
--- a/redis/commands/connection/echo.mdx
+++ b/redis/commands/connection/echo.mdx
@@ -38,6 +38,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+ECHO hello
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/connection/hello.mdx b/redis/commands/connection/hello.mdx
index b149fe969..25afc32ad 100644
--- a/redis/commands/connection/hello.mdx
+++ b/redis/commands/connection/hello.mdx
@@ -47,6 +47,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+HELLO
+```
+
+</Accordion>
+
 <Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/connection/ping.mdx b/redis/commands/connection/ping.mdx
index 7778d5daa..ff7cf021d 100644
--- a/redis/commands/connection/ping.mdx
+++ b/redis/commands/connection/ping.mdx
@@ -43,6 +43,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+PING
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/connection/quit.mdx b/redis/commands/connection/quit.mdx
index 3fd9fe9b2..a9c5cf485 100644
--- a/redis/commands/connection/quit.mdx
+++ b/redis/commands/connection/quit.mdx
@@ -44,6 +44,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+QUIT
+```
+
+</Accordion>
+
 <Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/connection/reset.mdx b/redis/commands/connection/reset.mdx
index c210a27e1..6732dce85 100644
--- a/redis/commands/connection/reset.mdx
+++ b/redis/commands/connection/reset.mdx
@@ -40,6 +40,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+RESET
+```
+
+</Accordion>
+
 <Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/connection/select.mdx b/redis/commands/connection/select.mdx
index 9b969a582..da62118af 100644
--- a/redis/commands/connection/select.mdx
+++ b/redis/commands/connection/select.mdx
@@ -42,6 +42,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+SELECT 0
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
diff --git a/redis/commands/functions/fcall-ro.mdx b/redis/commands/functions/fcall-ro.mdx
index 6d8c2233b..01555d292 100644
--- a/redis/commands/functions/fcall-ro.mdx
+++ b/redis/commands/functions/fcall-ro.mdx
@@ -51,6 +51,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+FCALL_RO my_function 1 my-key value
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/functions/fcall.mdx b/redis/commands/functions/fcall.mdx
index 41f47f2e0..49f0a5ba6 100644
--- a/redis/commands/functions/fcall.mdx
+++ b/redis/commands/functions/fcall.mdx
@@ -71,6 +71,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+FCALL my_function 1 my-key value
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/functions/function-delete.mdx b/redis/commands/functions/function-delete.mdx
index e59772543..800719e59 100644
--- a/redis/commands/functions/function-delete.mdx
+++ b/redis/commands/functions/function-delete.mdx
@@ -38,6 +38,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+FUNCTION DELETE mylib
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/functions/function-flush.mdx b/redis/commands/functions/function-flush.mdx
index 1d6d4cf7a..5c49b8ebb 100644
--- a/redis/commands/functions/function-flush.mdx
+++ b/redis/commands/functions/function-flush.mdx
@@ -38,6 +38,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+FUNCTION FLUSH
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/functions/function-kill.mdx b/redis/commands/functions/function-kill.mdx
index 05e601c73..7c5d8d4b4 100644
--- a/redis/commands/functions/function-kill.mdx
+++ b/redis/commands/functions/function-kill.mdx
@@ -42,6 +42,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+FUNCTION KILL
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
diff --git a/redis/commands/functions/function-list.mdx b/redis/commands/functions/function-list.mdx
index e7d4259f4..40857d64f 100644
--- a/redis/commands/functions/function-list.mdx
+++ b/redis/commands/functions/function-list.mdx
@@ -39,6 +39,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+FUNCTION LIST
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/functions/function-load.mdx b/redis/commands/functions/function-load.mdx
index 95cc817c4..31c0b9d67 100644
--- a/redis/commands/functions/function-load.mdx
+++ b/redis/commands/functions/function-load.mdx
@@ -45,6 +45,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+FUNCTION LOAD "#!lua name=mylib\nredis.register_function('helloworld', function() return 'Hello World!' end)"
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/functions/function-stats.mdx b/redis/commands/functions/function-stats.mdx
index 5099fcf2d..d0731a88b 100644
--- a/redis/commands/functions/function-stats.mdx
+++ b/redis/commands/functions/function-stats.mdx
@@ -36,6 +36,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+FUNCTION STATS
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/generic/copy.mdx b/redis/commands/generic/copy.mdx
index c5200578f..f4e20d6a6 100644
--- a/redis/commands/generic/copy.mdx
+++ b/redis/commands/generic/copy.mdx
@@ -43,6 +43,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+COPY source-key destination-key
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/generic/del.mdx b/redis/commands/generic/del.mdx
index c4d48adb0..5c338d3f1 100644
--- a/redis/commands/generic/del.mdx
+++ b/redis/commands/generic/del.mdx
@@ -38,6 +38,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+DEL my-key
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/generic/dump.mdx b/redis/commands/generic/dump.mdx
index 7697ef3f7..27bef930e 100644
--- a/redis/commands/generic/dump.mdx
+++ b/redis/commands/generic/dump.mdx
@@ -40,6 +40,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+DUMP my-key
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
diff --git a/redis/commands/generic/exists.mdx b/redis/commands/generic/exists.mdx
index 73999203f..dc2a1493b 100644
--- a/redis/commands/generic/exists.mdx
+++ b/redis/commands/generic/exists.mdx
@@ -38,6 +38,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+EXISTS my-key
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/generic/expire.mdx b/redis/commands/generic/expire.mdx
index c2d8e94bb..099773dfb 100644
--- a/redis/commands/generic/expire.mdx
+++ b/redis/commands/generic/expire.mdx
@@ -49,6 +49,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+EXPIRE my-key 1000
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/generic/expireat.mdx b/redis/commands/generic/expireat.mdx
index 695a99931..04902071f 100644
--- a/redis/commands/generic/expireat.mdx
+++ b/redis/commands/generic/expireat.mdx
@@ -47,6 +47,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+EXPIREAT my-key 1735689600
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/generic/expiretime.mdx b/redis/commands/generic/expiretime.mdx
index d15c39c7b..4ea72cc38 100644
--- a/redis/commands/generic/expiretime.mdx
+++ b/redis/commands/generic/expiretime.mdx
@@ -42,6 +42,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+EXPIRETIME my-key
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
diff --git a/redis/commands/generic/keys.mdx b/redis/commands/generic/keys.mdx
index 85a1662f0..095a76e22 100644
--- a/redis/commands/generic/keys.mdx
+++ b/redis/commands/generic/keys.mdx
@@ -45,6 +45,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+KEYS *
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/generic/memory-usage.mdx b/redis/commands/generic/memory-usage.mdx
index ddeac1d62..bfe254cd5 100644
--- a/redis/commands/generic/memory-usage.mdx
+++ b/redis/commands/generic/memory-usage.mdx
@@ -46,6 +46,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+MEMORY USAGE my-key SAMPLES 10
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
diff --git a/redis/commands/generic/persist.mdx b/redis/commands/generic/persist.mdx
index fc09e18c8..cd5820dfe 100644
--- a/redis/commands/generic/persist.mdx
+++ b/redis/commands/generic/persist.mdx
@@ -38,6 +38,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+PERSIST my-key
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/generic/pexpire.mdx b/redis/commands/generic/pexpire.mdx
index bdef6080a..3b85ee6bc 100644
--- a/redis/commands/generic/pexpire.mdx
+++ b/redis/commands/generic/pexpire.mdx
@@ -47,6 +47,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+PEXPIRE my-key 1000
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/generic/pexpireat.mdx b/redis/commands/generic/pexpireat.mdx
index 96712b50e..ae4b8be22 100644
--- a/redis/commands/generic/pexpireat.mdx
+++ b/redis/commands/generic/pexpireat.mdx
@@ -47,6 +47,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+PEXPIREAT my-key 1735689600
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/generic/pexpiretime.mdx b/redis/commands/generic/pexpiretime.mdx
index 1beea429e..56f3716c9 100644
--- a/redis/commands/generic/pexpiretime.mdx
+++ b/redis/commands/generic/pexpiretime.mdx
@@ -42,6 +42,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+PEXPIRETIME my-key
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
diff --git a/redis/commands/generic/pttl.mdx b/redis/commands/generic/pttl.mdx
index dafb341cf..4e08362f2 100644
--- a/redis/commands/generic/pttl.mdx
+++ b/redis/commands/generic/pttl.mdx
@@ -42,6 +42,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+PTTL my-key
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/generic/randomkey.mdx b/redis/commands/generic/randomkey.mdx
index af3d38c94..aa0741ff1 100644
--- a/redis/commands/generic/randomkey.mdx
+++ b/redis/commands/generic/randomkey.mdx
@@ -36,6 +36,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+RANDOMKEY
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/generic/rename.mdx b/redis/commands/generic/rename.mdx
index 6c1c33178..1140d5f0b 100644
--- a/redis/commands/generic/rename.mdx
+++ b/redis/commands/generic/rename.mdx
@@ -41,6 +41,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+RENAME old-key new-key
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/generic/renamenx.mdx b/redis/commands/generic/renamenx.mdx
index 80ac14b34..21c5be7f3 100644
--- a/redis/commands/generic/renamenx.mdx
+++ b/redis/commands/generic/renamenx.mdx
@@ -39,6 +39,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+RENAMENX old-key new-key
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/generic/restore.mdx b/redis/commands/generic/restore.mdx
index 95fa6ce45..3e4c50b28 100644
--- a/redis/commands/generic/restore.mdx
+++ b/redis/commands/generic/restore.mdx
@@ -54,6 +54,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+RESTORE my-key 1 serialized-value
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
diff --git a/redis/commands/generic/scan.mdx b/redis/commands/generic/scan.mdx
index c684546df..ba329d740 100644
--- a/redis/commands/generic/scan.mdx
+++ b/redis/commands/generic/scan.mdx
@@ -50,6 +50,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+SCAN 0
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/generic/touch.mdx b/redis/commands/generic/touch.mdx
index cc6d1edcf..b0ece6034 100644
--- a/redis/commands/generic/touch.mdx
+++ b/redis/commands/generic/touch.mdx
@@ -38,6 +38,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+TOUCH my-key
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/generic/ttl.mdx b/redis/commands/generic/ttl.mdx
index f34c2d927..e4473e62f 100644
--- a/redis/commands/generic/ttl.mdx
+++ b/redis/commands/generic/ttl.mdx
@@ -42,6 +42,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+TTL my-key
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/generic/type.mdx b/redis/commands/generic/type.mdx
index 194ca3667..1aa942da1 100644
--- a/redis/commands/generic/type.mdx
+++ b/redis/commands/generic/type.mdx
@@ -38,6 +38,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+TYPE my-key
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/generic/unlink.mdx b/redis/commands/generic/unlink.mdx
index f06b620fe..e1b3073e8 100644
--- a/redis/commands/generic/unlink.mdx
+++ b/redis/commands/generic/unlink.mdx
@@ -38,6 +38,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+UNLINK my-key
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/generic/wait.mdx b/redis/commands/generic/wait.mdx
index a3a272f5d..c4026bab8 100644
--- a/redis/commands/generic/wait.mdx
+++ b/redis/commands/generic/wait.mdx
@@ -48,6 +48,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+WAIT 1 1000
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
diff --git a/redis/commands/generic/waitaof.mdx b/redis/commands/generic/waitaof.mdx
index c7a1cdbaa..c37338493 100644
--- a/redis/commands/generic/waitaof.mdx
+++ b/redis/commands/generic/waitaof.mdx
@@ -47,6 +47,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+WAITAOF 1 1 1000
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
diff --git a/redis/commands/geo/geoadd.mdx b/redis/commands/geo/geoadd.mdx
index 9f9852fc2..4bec704be 100644
--- a/redis/commands/geo/geoadd.mdx
+++ b/redis/commands/geo/geoadd.mdx
@@ -51,6 +51,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+GEOADD my-key 29.0 41.0 member
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/geo/geodist.mdx b/redis/commands/geo/geodist.mdx
index b33db1d4f..aceaa49fc 100644
--- a/redis/commands/geo/geodist.mdx
+++ b/redis/commands/geo/geodist.mdx
@@ -45,6 +45,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+GEODIST my-key member1 member2
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/geo/geohash.mdx b/redis/commands/geo/geohash.mdx
index 701053fd1..f7363fad6 100644
--- a/redis/commands/geo/geohash.mdx
+++ b/redis/commands/geo/geohash.mdx
@@ -39,6 +39,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+GEOHASH my-key member
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/geo/geopos.mdx b/redis/commands/geo/geopos.mdx
index 0e2d4dcca..9e9ff6fd2 100644
--- a/redis/commands/geo/geopos.mdx
+++ b/redis/commands/geo/geopos.mdx
@@ -39,6 +39,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+GEOPOS my-key member
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/geo/georadius-ro.mdx b/redis/commands/geo/georadius-ro.mdx
index 55c288462..1d1bd9d38 100644
--- a/redis/commands/geo/georadius-ro.mdx
+++ b/redis/commands/geo/georadius-ro.mdx
@@ -58,6 +58,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+GEORADIUS_RO my-key 29.0 41.0 1.5 m
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
diff --git a/redis/commands/geo/georadius.mdx b/redis/commands/geo/georadius.mdx
index d00a83a47..4d859c485 100644
--- a/redis/commands/geo/georadius.mdx
+++ b/redis/commands/geo/georadius.mdx
@@ -62,6 +62,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+GEORADIUS my-key 29.0 41.0 1.5 m
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
diff --git a/redis/commands/geo/georadiusbymember-ro.mdx b/redis/commands/geo/georadiusbymember-ro.mdx
index a78a4ab7e..3e9344048 100644
--- a/redis/commands/geo/georadiusbymember-ro.mdx
+++ b/redis/commands/geo/georadiusbymember-ro.mdx
@@ -55,6 +55,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+GEORADIUSBYMEMBER_RO my-key member 1.5 m
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
diff --git a/redis/commands/geo/georadiusbymember.mdx b/redis/commands/geo/georadiusbymember.mdx
index d9125cadb..feeebbf71 100644
--- a/redis/commands/geo/georadiusbymember.mdx
+++ b/redis/commands/geo/georadiusbymember.mdx
@@ -59,6 +59,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+GEORADIUSBYMEMBER my-key member 1.5 m
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
diff --git a/redis/commands/geo/geosearch.mdx b/redis/commands/geo/geosearch.mdx
index b77e02fb8..1678c7447 100644
--- a/redis/commands/geo/geosearch.mdx
+++ b/redis/commands/geo/geosearch.mdx
@@ -57,6 +57,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+GEOSEARCH my-key FROMMEMBER member BYRADIUS 1.5 m
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/geo/geosearchstore.mdx b/redis/commands/geo/geosearchstore.mdx
index 852f1580e..5f1c834e9 100644
--- a/redis/commands/geo/geosearchstore.mdx
+++ b/redis/commands/geo/geosearchstore.mdx
@@ -52,6 +52,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+GEOSEARCHSTORE destination-key source-key FROMMEMBER member BYRADIUS 1.5 m
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/hash/hdel.mdx b/redis/commands/hash/hdel.mdx
index ac2b8ee28..ffcb2245d 100644
--- a/redis/commands/hash/hdel.mdx
+++ b/redis/commands/hash/hdel.mdx
@@ -39,6 +39,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+HDEL my-key field
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/hash/hexists.mdx b/redis/commands/hash/hexists.mdx
index 1f72786e5..26bb63f05 100644
--- a/redis/commands/hash/hexists.mdx
+++ b/redis/commands/hash/hexists.mdx
@@ -39,6 +39,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+HEXISTS my-key field
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/hash/hexpire.mdx b/redis/commands/hash/hexpire.mdx
index d96e2f993..bd76d9bd3 100644
--- a/redis/commands/hash/hexpire.mdx
+++ b/redis/commands/hash/hexpire.mdx
@@ -52,6 +52,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+HEXPIRE my-key 1000 FIELDS 1 field
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/hash/hexpireat.mdx b/redis/commands/hash/hexpireat.mdx
index 131e83032..0edd76c39 100644
--- a/redis/commands/hash/hexpireat.mdx
+++ b/redis/commands/hash/hexpireat.mdx
@@ -52,6 +52,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+HEXPIREAT my-key 1735689600 FIELDS 1 field
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/hash/hexpiretime.mdx b/redis/commands/hash/hexpiretime.mdx
index 25aa7a707..24d0d8ef2 100644
--- a/redis/commands/hash/hexpiretime.mdx
+++ b/redis/commands/hash/hexpiretime.mdx
@@ -43,6 +43,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+HEXPIRETIME my-key FIELDS 1 field
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/hash/hget.mdx b/redis/commands/hash/hget.mdx
index e67f3de6f..5a09063a3 100644
--- a/redis/commands/hash/hget.mdx
+++ b/redis/commands/hash/hget.mdx
@@ -39,6 +39,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+HGET my-key field
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/hash/hgetall.mdx b/redis/commands/hash/hgetall.mdx
index 59d65ba31..61f481e27 100644
--- a/redis/commands/hash/hgetall.mdx
+++ b/redis/commands/hash/hgetall.mdx
@@ -44,6 +44,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+HGETALL my-key
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/hash/hgetdel.mdx b/redis/commands/hash/hgetdel.mdx
index 25e31741f..3ca63173a 100644
--- a/redis/commands/hash/hgetdel.mdx
+++ b/redis/commands/hash/hgetdel.mdx
@@ -41,6 +41,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+HGETDEL my-key FIELDS 1 field
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/hash/hgetex.mdx b/redis/commands/hash/hgetex.mdx
index 9d19a8397..55fd52126 100644
--- a/redis/commands/hash/hgetex.mdx
+++ b/redis/commands/hash/hgetex.mdx
@@ -45,6 +45,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+HGETEX my-key FIELDS 1 field
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/hash/hincrby.mdx b/redis/commands/hash/hincrby.mdx
index 37045a8c5..6d8776639 100644
--- a/redis/commands/hash/hincrby.mdx
+++ b/redis/commands/hash/hincrby.mdx
@@ -42,6 +42,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+HINCRBY my-key field 1
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/hash/hincrbyfloat.mdx b/redis/commands/hash/hincrbyfloat.mdx
index 7a0f33901..7f409f7ac 100644
--- a/redis/commands/hash/hincrbyfloat.mdx
+++ b/redis/commands/hash/hincrbyfloat.mdx
@@ -46,6 +46,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+HINCRBYFLOAT my-key field 1.5
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/hash/hkeys.mdx b/redis/commands/hash/hkeys.mdx
index ab3b2aede..9ae11406b 100644
--- a/redis/commands/hash/hkeys.mdx
+++ b/redis/commands/hash/hkeys.mdx
@@ -38,6 +38,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+HKEYS my-key
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/hash/hlen.mdx b/redis/commands/hash/hlen.mdx
index 46f321cc6..97c43ef92 100644
--- a/redis/commands/hash/hlen.mdx
+++ b/redis/commands/hash/hlen.mdx
@@ -38,6 +38,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+HLEN my-key
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/hash/hmget.mdx b/redis/commands/hash/hmget.mdx
index d38002c64..3f0928471 100644
--- a/redis/commands/hash/hmget.mdx
+++ b/redis/commands/hash/hmget.mdx
@@ -41,6 +41,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+HMGET my-key field
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/hash/hmset.mdx b/redis/commands/hash/hmset.mdx
index 2f9daebe4..29f403541 100644
--- a/redis/commands/hash/hmset.mdx
+++ b/redis/commands/hash/hmset.mdx
@@ -43,6 +43,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+HMSET my-key field value
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/hash/hpersist.mdx b/redis/commands/hash/hpersist.mdx
index bcff168b0..b1a2994f7 100644
--- a/redis/commands/hash/hpersist.mdx
+++ b/redis/commands/hash/hpersist.mdx
@@ -41,6 +41,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+HPERSIST my-key FIELDS 1 field
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/hash/hpexpire.mdx b/redis/commands/hash/hpexpire.mdx
index 5a71ac953..adf26c14e 100644
--- a/redis/commands/hash/hpexpire.mdx
+++ b/redis/commands/hash/hpexpire.mdx
@@ -50,6 +50,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+HPEXPIRE my-key 1000 FIELDS 1 field
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/hash/hpexpireat.mdx b/redis/commands/hash/hpexpireat.mdx
index dffbaf483..8705ef3cb 100644
--- a/redis/commands/hash/hpexpireat.mdx
+++ b/redis/commands/hash/hpexpireat.mdx
@@ -50,6 +50,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+HPEXPIREAT my-key 1735689600 FIELDS 1 field
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/hash/hpexpiretime.mdx b/redis/commands/hash/hpexpiretime.mdx
index 7a64e0616..20ba0aeec 100644
--- a/redis/commands/hash/hpexpiretime.mdx
+++ b/redis/commands/hash/hpexpiretime.mdx
@@ -43,6 +43,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+HPEXPIRETIME my-key FIELDS 1 field
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/hash/hpttl.mdx b/redis/commands/hash/hpttl.mdx
index f4bba8a36..6e59fe28b 100644
--- a/redis/commands/hash/hpttl.mdx
+++ b/redis/commands/hash/hpttl.mdx
@@ -43,6 +43,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+HPTTL my-key FIELDS 1 field
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/hash/hrandfield.mdx b/redis/commands/hash/hrandfield.mdx
index f319bcfac..09b913c8d 100644
--- a/redis/commands/hash/hrandfield.mdx
+++ b/redis/commands/hash/hrandfield.mdx
@@ -45,6 +45,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+HRANDFIELD my-key
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/hash/hscan.mdx b/redis/commands/hash/hscan.mdx
index 49cdf4258..d309dae11 100644
--- a/redis/commands/hash/hscan.mdx
+++ b/redis/commands/hash/hscan.mdx
@@ -49,6 +49,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+HSCAN my-key 0
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/hash/hset.mdx b/redis/commands/hash/hset.mdx
index b685da061..8232c4bd9 100644
--- a/redis/commands/hash/hset.mdx
+++ b/redis/commands/hash/hset.mdx
@@ -41,6 +41,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+HSET my-key field value
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/hash/hsetex.mdx b/redis/commands/hash/hsetex.mdx
index e6d7d46e2..e8ee4cdad 100644
--- a/redis/commands/hash/hsetex.mdx
+++ b/redis/commands/hash/hsetex.mdx
@@ -47,6 +47,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+HSETEX my-key FIELDS 1 field value
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/hash/hsetnx.mdx b/redis/commands/hash/hsetnx.mdx
index 39e6d1540..f670b6bf6 100644
--- a/redis/commands/hash/hsetnx.mdx
+++ b/redis/commands/hash/hsetnx.mdx
@@ -40,6 +40,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+HSETNX my-key field value
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/hash/hstrlen.mdx b/redis/commands/hash/hstrlen.mdx
index 73b81f5f7..7faefe033 100644
--- a/redis/commands/hash/hstrlen.mdx
+++ b/redis/commands/hash/hstrlen.mdx
@@ -39,6 +39,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+HSTRLEN my-key field
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/hash/httl.mdx b/redis/commands/hash/httl.mdx
index 21f0c23ae..6c582a50f 100644
--- a/redis/commands/hash/httl.mdx
+++ b/redis/commands/hash/httl.mdx
@@ -43,6 +43,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+HTTL my-key FIELDS 1 field
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/hash/hvals.mdx b/redis/commands/hash/hvals.mdx
index 962b4981e..4c86486e3 100644
--- a/redis/commands/hash/hvals.mdx
+++ b/redis/commands/hash/hvals.mdx
@@ -38,6 +38,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+HVALS my-key
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/hyperloglog/pfadd.mdx b/redis/commands/hyperloglog/pfadd.mdx
index 113a4d5c1..4ad72daf5 100644
--- a/redis/commands/hyperloglog/pfadd.mdx
+++ b/redis/commands/hyperloglog/pfadd.mdx
@@ -41,6 +41,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+PFADD my-key element
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/hyperloglog/pfcount.mdx b/redis/commands/hyperloglog/pfcount.mdx
index 5c6efcf50..4530cbe63 100644
--- a/redis/commands/hyperloglog/pfcount.mdx
+++ b/redis/commands/hyperloglog/pfcount.mdx
@@ -40,6 +40,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+PFCOUNT my-key
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/hyperloglog/pfmerge.mdx b/redis/commands/hyperloglog/pfmerge.mdx
index 13d78860e..1b72400ed 100644
--- a/redis/commands/hyperloglog/pfmerge.mdx
+++ b/redis/commands/hyperloglog/pfmerge.mdx
@@ -41,6 +41,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+PFMERGE destination-key source-key
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/json/json-arrappend.mdx b/redis/commands/json/json-arrappend.mdx
index 0b2bcbfc3..61a62a394 100644
--- a/redis/commands/json/json-arrappend.mdx
+++ b/redis/commands/json/json-arrappend.mdx
@@ -45,6 +45,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+JSON.ARRAPPEND profile $.tags '"new"'
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/json/json-arrindex.mdx b/redis/commands/json/json-arrindex.mdx
index 0dad49384..15a5c348f 100644
--- a/redis/commands/json/json-arrindex.mdx
+++ b/redis/commands/json/json-arrindex.mdx
@@ -47,6 +47,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+JSON.ARRINDEX profile $.tags '"new"'
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/json/json-arrinsert.mdx b/redis/commands/json/json-arrinsert.mdx
index 5e2c48cb9..f7d85df65 100644
--- a/redis/commands/json/json-arrinsert.mdx
+++ b/redis/commands/json/json-arrinsert.mdx
@@ -46,6 +46,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+JSON.ARRINSERT profile $.tags 0 '"first"'
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/json/json-arrlen.mdx b/redis/commands/json/json-arrlen.mdx
index 07c13a3e8..7027abb97 100644
--- a/redis/commands/json/json-arrlen.mdx
+++ b/redis/commands/json/json-arrlen.mdx
@@ -44,6 +44,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+JSON.ARRLEN profile $.tags
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/json/json-arrpop.mdx b/redis/commands/json/json-arrpop.mdx
index f9687b989..223455fca 100644
--- a/redis/commands/json/json-arrpop.mdx
+++ b/redis/commands/json/json-arrpop.mdx
@@ -47,6 +47,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+JSON.ARRPOP profile $.tags -1
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/json/json-arrtrim.mdx b/redis/commands/json/json-arrtrim.mdx
index 7447ac017..3528e38dd 100644
--- a/redis/commands/json/json-arrtrim.mdx
+++ b/redis/commands/json/json-arrtrim.mdx
@@ -48,6 +48,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+JSON.ARRTRIM profile $.tags 0 9
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/json/json-clear.mdx b/redis/commands/json/json-clear.mdx
index ed95f5b6a..9bdb2ff4e 100644
--- a/redis/commands/json/json-clear.mdx
+++ b/redis/commands/json/json-clear.mdx
@@ -46,6 +46,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+JSON.CLEAR profile $.stats
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/json/json-debug.mdx b/redis/commands/json/json-debug.mdx
index f9f68de29..9a8688743 100644
--- a/redis/commands/json/json-debug.mdx
+++ b/redis/commands/json/json-debug.mdx
@@ -49,6 +49,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+JSON.DEBUG MEMORY profile $.stats
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
diff --git a/redis/commands/json/json-del.mdx b/redis/commands/json/json-del.mdx
index 33868ebf3..7e8170e78 100644
--- a/redis/commands/json/json-del.mdx
+++ b/redis/commands/json/json-del.mdx
@@ -46,6 +46,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+JSON.DEL profile $.temporary
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/json/json-forget.mdx b/redis/commands/json/json-forget.mdx
index 3332644e2..e118f0699 100644
--- a/redis/commands/json/json-forget.mdx
+++ b/redis/commands/json/json-forget.mdx
@@ -44,6 +44,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+JSON.FORGET profile $.temporary
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/json/json-get.mdx b/redis/commands/json/json-get.mdx
index d32521d80..83221c65a 100644
--- a/redis/commands/json/json-get.mdx
+++ b/redis/commands/json/json-get.mdx
@@ -53,6 +53,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+JSON.GET profile $.name
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/json/json-merge.mdx b/redis/commands/json/json-merge.mdx
index f98d6d8e6..9e9874a5e 100644
--- a/redis/commands/json/json-merge.mdx
+++ b/redis/commands/json/json-merge.mdx
@@ -47,6 +47,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+JSON.MERGE profile $ '{"active":true}'
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/json/json-mget.mdx b/redis/commands/json/json-mget.mdx
index e6d9b0f5a..a52c41ef9 100644
--- a/redis/commands/json/json-mget.mdx
+++ b/redis/commands/json/json-mget.mdx
@@ -44,6 +44,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+JSON.MGET profile:1 profile:2 $.name
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/json/json-mset.mdx b/redis/commands/json/json-mset.mdx
index 2833f61cd..3d413bf6f 100644
--- a/redis/commands/json/json-mset.mdx
+++ b/redis/commands/json/json-mset.mdx
@@ -43,6 +43,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+JSON.MSET profile:1 $ '{"name":"Ada"}'
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/json/json-numincrby.mdx b/redis/commands/json/json-numincrby.mdx
index 688c6caad..e3fc1bfae 100644
--- a/redis/commands/json/json-numincrby.mdx
+++ b/redis/commands/json/json-numincrby.mdx
@@ -45,6 +45,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+JSON.NUMINCRBY profile $.visits 1
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/json/json-nummultby.mdx b/redis/commands/json/json-nummultby.mdx
index 47dd498b7..820639737 100644
--- a/redis/commands/json/json-nummultby.mdx
+++ b/redis/commands/json/json-nummultby.mdx
@@ -45,6 +45,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+JSON.NUMMULTBY profile $.score 2
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/json/json-objkeys.mdx b/redis/commands/json/json-objkeys.mdx
index 69bb38221..1a2cf29e3 100644
--- a/redis/commands/json/json-objkeys.mdx
+++ b/redis/commands/json/json-objkeys.mdx
@@ -44,6 +44,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+JSON.OBJKEYS profile $
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/json/json-objlen.mdx b/redis/commands/json/json-objlen.mdx
index 4162e657a..d6584c004 100644
--- a/redis/commands/json/json-objlen.mdx
+++ b/redis/commands/json/json-objlen.mdx
@@ -44,6 +44,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+JSON.OBJLEN profile $
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/json/json-resp.mdx b/redis/commands/json/json-resp.mdx
index 63af81215..98564c07e 100644
--- a/redis/commands/json/json-resp.mdx
+++ b/redis/commands/json/json-resp.mdx
@@ -46,6 +46,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+JSON.RESP profile $
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/json/json-set.mdx b/redis/commands/json/json-set.mdx
index 6466fe68f..841aff07d 100644
--- a/redis/commands/json/json-set.mdx
+++ b/redis/commands/json/json-set.mdx
@@ -48,6 +48,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+JSON.SET profile $ '{"name":"Ada"}'
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/json/json-strappend.mdx b/redis/commands/json/json-strappend.mdx
index cda2316a5..0d5e34d9f 100644
--- a/redis/commands/json/json-strappend.mdx
+++ b/redis/commands/json/json-strappend.mdx
@@ -45,6 +45,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+JSON.STRAPPEND profile $.name '" Lovelace"'
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/json/json-strlen.mdx b/redis/commands/json/json-strlen.mdx
index f5c557f50..a3663f8fe 100644
--- a/redis/commands/json/json-strlen.mdx
+++ b/redis/commands/json/json-strlen.mdx
@@ -44,6 +44,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+JSON.STRLEN profile $.name
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/json/json-toggle.mdx b/redis/commands/json/json-toggle.mdx
index d26a6f7f2..f81f8db22 100644
--- a/redis/commands/json/json-toggle.mdx
+++ b/redis/commands/json/json-toggle.mdx
@@ -44,6 +44,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+JSON.TOGGLE profile $.active
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/json/json-type.mdx b/redis/commands/json/json-type.mdx
index a63e125db..1615bdeb3 100644
--- a/redis/commands/json/json-type.mdx
+++ b/redis/commands/json/json-type.mdx
@@ -44,6 +44,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+JSON.TYPE profile $.name
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/list/blmove.mdx b/redis/commands/list/blmove.mdx
index d741698dc..c695da2b7 100644
--- a/redis/commands/list/blmove.mdx
+++ b/redis/commands/list/blmove.mdx
@@ -48,6 +48,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+BLMOVE source-key destination-key LEFT LEFT 1.5
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
diff --git a/redis/commands/list/blmpop.mdx b/redis/commands/list/blmpop.mdx
index 286084b66..ef0511c21 100644
--- a/redis/commands/list/blmpop.mdx
+++ b/redis/commands/list/blmpop.mdx
@@ -48,6 +48,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+BLMPOP 1.5 1 my-key LEFT
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
diff --git a/redis/commands/list/blpop.mdx b/redis/commands/list/blpop.mdx
index d18dc7fe1..f66b62bf9 100644
--- a/redis/commands/list/blpop.mdx
+++ b/redis/commands/list/blpop.mdx
@@ -45,6 +45,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+BLPOP my-key 1.5
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
diff --git a/redis/commands/list/brpop.mdx b/redis/commands/list/brpop.mdx
index 2fe0917c0..446ddb88c 100644
--- a/redis/commands/list/brpop.mdx
+++ b/redis/commands/list/brpop.mdx
@@ -45,6 +45,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+BRPOP my-key 1.5
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
diff --git a/redis/commands/list/brpoplpush.mdx b/redis/commands/list/brpoplpush.mdx
index 09c337966..0fdd3a39b 100644
--- a/redis/commands/list/brpoplpush.mdx
+++ b/redis/commands/list/brpoplpush.mdx
@@ -50,6 +50,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+BRPOPLPUSH source-key destination-key 1.5
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
diff --git a/redis/commands/list/lindex.mdx b/redis/commands/list/lindex.mdx
index e1b8c1f61..1ed338efb 100644
--- a/redis/commands/list/lindex.mdx
+++ b/redis/commands/list/lindex.mdx
@@ -39,6 +39,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+LINDEX my-key 0
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/list/linsert.mdx b/redis/commands/list/linsert.mdx
index cf259be12..0160ff4fc 100644
--- a/redis/commands/list/linsert.mdx
+++ b/redis/commands/list/linsert.mdx
@@ -43,6 +43,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+LINSERT my-key BEFORE pivot element
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/list/llen.mdx b/redis/commands/list/llen.mdx
index 11ec9ac8d..97e284b48 100644
--- a/redis/commands/list/llen.mdx
+++ b/redis/commands/list/llen.mdx
@@ -38,6 +38,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+LLEN my-key
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/list/lmove.mdx b/redis/commands/list/lmove.mdx
index 1840d1d54..6958dc82b 100644
--- a/redis/commands/list/lmove.mdx
+++ b/redis/commands/list/lmove.mdx
@@ -43,6 +43,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+LMOVE source-key destination-key LEFT LEFT
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/list/lmpop.mdx b/redis/commands/list/lmpop.mdx
index e482e036d..5efa8b670 100644
--- a/redis/commands/list/lmpop.mdx
+++ b/redis/commands/list/lmpop.mdx
@@ -43,6 +43,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+LMPOP 1 my-key LEFT
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/list/lpop.mdx b/redis/commands/list/lpop.mdx
index 09e66416f..b7cc2fb64 100644
--- a/redis/commands/list/lpop.mdx
+++ b/redis/commands/list/lpop.mdx
@@ -41,6 +41,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+LPOP my-key
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/list/lpos.mdx b/redis/commands/list/lpos.mdx
index 168d8d32a..baae909b7 100644
--- a/redis/commands/list/lpos.mdx
+++ b/redis/commands/list/lpos.mdx
@@ -44,6 +44,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+LPOS my-key element
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/list/lpush.mdx b/redis/commands/list/lpush.mdx
index d1603b8be..197427b96 100644
--- a/redis/commands/list/lpush.mdx
+++ b/redis/commands/list/lpush.mdx
@@ -41,6 +41,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+LPUSH my-key element
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/list/lpushx.mdx b/redis/commands/list/lpushx.mdx
index b6d9fe4e1..e8c1885c0 100644
--- a/redis/commands/list/lpushx.mdx
+++ b/redis/commands/list/lpushx.mdx
@@ -39,6 +39,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+LPUSHX my-key element
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/list/lrange.mdx b/redis/commands/list/lrange.mdx
index d6517bfa7..6a6f30687 100644
--- a/redis/commands/list/lrange.mdx
+++ b/redis/commands/list/lrange.mdx
@@ -42,6 +42,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+LRANGE my-key 0 0
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/list/lrem.mdx b/redis/commands/list/lrem.mdx
index d4467fe53..9bf90f2c3 100644
--- a/redis/commands/list/lrem.mdx
+++ b/redis/commands/list/lrem.mdx
@@ -42,6 +42,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+LREM my-key 1 element
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/list/lset.mdx b/redis/commands/list/lset.mdx
index 34f7aba1f..dba3b9edb 100644
--- a/redis/commands/list/lset.mdx
+++ b/redis/commands/list/lset.mdx
@@ -40,6 +40,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+LSET my-key 0 element
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/list/ltrim.mdx b/redis/commands/list/ltrim.mdx
index 1ce397075..f5286354c 100644
--- a/redis/commands/list/ltrim.mdx
+++ b/redis/commands/list/ltrim.mdx
@@ -42,6 +42,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+LTRIM my-key 0 0
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/list/rpop.mdx b/redis/commands/list/rpop.mdx
index b97cb2962..87d7d9645 100644
--- a/redis/commands/list/rpop.mdx
+++ b/redis/commands/list/rpop.mdx
@@ -41,6 +41,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+RPOP my-key
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/list/rpoplpush.mdx b/redis/commands/list/rpoplpush.mdx
index 8fd3d9f1a..9aaba63b6 100644
--- a/redis/commands/list/rpoplpush.mdx
+++ b/redis/commands/list/rpoplpush.mdx
@@ -45,6 +45,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+RPOPLPUSH source-key destination-key
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
diff --git a/redis/commands/list/rpush.mdx b/redis/commands/list/rpush.mdx
index 937666d1e..252203965 100644
--- a/redis/commands/list/rpush.mdx
+++ b/redis/commands/list/rpush.mdx
@@ -41,6 +41,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+RPUSH my-key element
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/list/rpushx.mdx b/redis/commands/list/rpushx.mdx
index 3fa250384..e0eaaefa6 100644
--- a/redis/commands/list/rpushx.mdx
+++ b/redis/commands/list/rpushx.mdx
@@ -39,6 +39,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+RPUSHX my-key element
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/pub-sub/psubscribe.mdx b/redis/commands/pub-sub/psubscribe.mdx
index 0e33d651f..670aa4bb9 100644
--- a/redis/commands/pub-sub/psubscribe.mdx
+++ b/redis/commands/pub-sub/psubscribe.mdx
@@ -45,6 +45,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+PSUBSCRIBE events:*
+```
+
+</Accordion>
+
 <Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/pub-sub/publish.mdx b/redis/commands/pub-sub/publish.mdx
index 7c868a59e..6e3baf1e1 100644
--- a/redis/commands/pub-sub/publish.mdx
+++ b/redis/commands/pub-sub/publish.mdx
@@ -41,6 +41,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+PUBLISH events hello
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/pub-sub/pubsub.mdx b/redis/commands/pub-sub/pubsub.mdx
index 248096f06..bae84a00d 100644
--- a/redis/commands/pub-sub/pubsub.mdx
+++ b/redis/commands/pub-sub/pubsub.mdx
@@ -44,6 +44,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+PUBSUB CHANNELS events:*
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
diff --git a/redis/commands/pub-sub/punsubscribe.mdx b/redis/commands/pub-sub/punsubscribe.mdx
index 4a516f424..3d85f4e88 100644
--- a/redis/commands/pub-sub/punsubscribe.mdx
+++ b/redis/commands/pub-sub/punsubscribe.mdx
@@ -45,6 +45,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+PUNSUBSCRIBE events:*
+```
+
+</Accordion>
+
 <Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/pub-sub/subscribe.mdx b/redis/commands/pub-sub/subscribe.mdx
index c980e9cff..38ecd7b62 100644
--- a/redis/commands/pub-sub/subscribe.mdx
+++ b/redis/commands/pub-sub/subscribe.mdx
@@ -45,6 +45,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+SUBSCRIBE events
+```
+
+</Accordion>
+
 <Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/pub-sub/unsubscribe.mdx b/redis/commands/pub-sub/unsubscribe.mdx
index db0d3cebd..311cdd048 100644
--- a/redis/commands/pub-sub/unsubscribe.mdx
+++ b/redis/commands/pub-sub/unsubscribe.mdx
@@ -45,6 +45,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+UNSUBSCRIBE events
+```
+
+</Accordion>
+
 <Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/scripting/eval-ro.mdx b/redis/commands/scripting/eval-ro.mdx
index aa532cf16..acc5c1730 100644
--- a/redis/commands/scripting/eval-ro.mdx
+++ b/redis/commands/scripting/eval-ro.mdx
@@ -49,6 +49,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+EVAL_RO "return ARGV[1]" 0 hello
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/scripting/eval.mdx b/redis/commands/scripting/eval.mdx
index 441e6dd0c..2472ae03f 100644
--- a/redis/commands/scripting/eval.mdx
+++ b/redis/commands/scripting/eval.mdx
@@ -73,6 +73,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+EVAL "return ARGV[1]" 0 hello
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/scripting/evalsha-ro.mdx b/redis/commands/scripting/evalsha-ro.mdx
index dfffd91f9..d98557b03 100644
--- a/redis/commands/scripting/evalsha-ro.mdx
+++ b/redis/commands/scripting/evalsha-ro.mdx
@@ -49,6 +49,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+EVALSHA_RO fb67a0c03b48ddbf8b4c9b011e779563bdbc28cb 0 value
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/scripting/evalsha.mdx b/redis/commands/scripting/evalsha.mdx
index fc83a4286..4a1ccad31 100644
--- a/redis/commands/scripting/evalsha.mdx
+++ b/redis/commands/scripting/evalsha.mdx
@@ -52,6 +52,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+EVALSHA fb67a0c03b48ddbf8b4c9b011e779563bdbc28cb 0 value
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/scripting/script-exists.mdx b/redis/commands/scripting/script-exists.mdx
index 9dc0b0637..eaa075433 100644
--- a/redis/commands/scripting/script-exists.mdx
+++ b/redis/commands/scripting/script-exists.mdx
@@ -38,6 +38,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+SCRIPT EXISTS fb67a0c03b48ddbf8b4c9b011e779563bdbc28cb
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/scripting/script-flush.mdx b/redis/commands/scripting/script-flush.mdx
index e1defb7bb..773f77af5 100644
--- a/redis/commands/scripting/script-flush.mdx
+++ b/redis/commands/scripting/script-flush.mdx
@@ -38,6 +38,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+SCRIPT FLUSH
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/scripting/script-kill.mdx b/redis/commands/scripting/script-kill.mdx
index 40560dff4..18df1b068 100644
--- a/redis/commands/scripting/script-kill.mdx
+++ b/redis/commands/scripting/script-kill.mdx
@@ -43,6 +43,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+SCRIPT KILL
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
diff --git a/redis/commands/scripting/script-load.mdx b/redis/commands/scripting/script-load.mdx
index 95f2363d5..3a8a32a39 100644
--- a/redis/commands/scripting/script-load.mdx
+++ b/redis/commands/scripting/script-load.mdx
@@ -44,6 +44,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+SCRIPT LOAD "return ARGV[1]"
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/search/search-aggregate.mdx b/redis/commands/search/search-aggregate.mdx
index a8f9f260d..3caa9e445 100644
--- a/redis/commands/search/search-aggregate.mdx
+++ b/redis/commands/search/search-aggregate.mdx
@@ -36,6 +36,14 @@ Raw RESP output may be rendered differently by client or protocol settings, but
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+SEARCH.AGGREGATE products '{}' '{"avg_price": {"$avg": {"field": "price"}}}'
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
@@ -108,14 +116,6 @@ const result = await products.aggregate({
 
 </Accordion>
 
-<Accordion title="Redis CLI">
-
-```bash
-SEARCH.AGGREGATE products '{}' '{"avg_price": {"$avg": {"field": "price"}}}'
-```
-
-</Accordion>
-
 <Accordion title="curl">
 
 ```bash
diff --git a/redis/commands/search/search-aliasadd.mdx b/redis/commands/search/search-aliasadd.mdx
index 7829cf99e..f16b50aac 100644
--- a/redis/commands/search/search-aliasadd.mdx
+++ b/redis/commands/search/search-aliasadd.mdx
@@ -25,6 +25,14 @@ Returns `1` if a new alias was created or `2` if an existing alias was updated,
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+SEARCH.ALIASADD products products-v2
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
@@ -87,14 +95,6 @@ const result = await search.alias.add({
 
 </Accordion>
 
-<Accordion title="Redis CLI">
-
-```bash
-SEARCH.ALIASADD products products-v2
-```
-
-</Accordion>
-
 <Accordion title="curl">
 
 ```bash
diff --git a/redis/commands/search/search-aliasdel.mdx b/redis/commands/search/search-aliasdel.mdx
index 90c4825d4..a23a13381 100644
--- a/redis/commands/search/search-aliasdel.mdx
+++ b/redis/commands/search/search-aliasdel.mdx
@@ -23,6 +23,14 @@ Returns `1` if the alias was deleted or `0` if the alias was not found.
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+SEARCH.ALIASDEL products
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
@@ -73,14 +81,6 @@ const result = await search.alias.delete({ alias: "products" });
 
 </Accordion>
 
-<Accordion title="Redis CLI">
-
-```bash
-SEARCH.ALIASDEL products
-```
-
-</Accordion>
-
 <Accordion title="curl">
 
 ```bash
diff --git a/redis/commands/search/search-count.mdx b/redis/commands/search/search-count.mdx
index 7edfbc467..c798a8555 100644
--- a/redis/commands/search/search-count.mdx
+++ b/redis/commands/search/search-count.mdx
@@ -25,6 +25,14 @@ Returns the number of matching documents as an integer. Returns `-1` if the inde
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+SEARCH.COUNT products '{"inStock": true}'
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
@@ -93,14 +101,6 @@ console.log(result.count);
 
 </Accordion>
 
-<Accordion title="Redis CLI">
-
-```bash
-SEARCH.COUNT products '{"inStock": true}'
-```
-
-</Accordion>
-
 <Accordion title="curl">
 
 ```bash
diff --git a/redis/commands/search/search-create.mdx b/redis/commands/search/search-create.mdx
index b16b41fb2..182bb54c4 100644
--- a/redis/commands/search/search-create.mdx
+++ b/redis/commands/search/search-create.mdx
@@ -58,6 +58,14 @@ Returns `1` when the index is created. With `EXISTSOK`, returns `0` if the exist
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+SEARCH.CREATE products ON JSON PREFIX 1 product: SCHEMA name TEXT price F64 FAST inStock BOOL
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
@@ -148,14 +156,6 @@ const products = await search.createIndex({
 
 </Accordion>
 
-<Accordion title="Redis CLI">
-
-```bash
-SEARCH.CREATE products ON JSON PREFIX 1 product: SCHEMA name TEXT price F64 FAST inStock BOOL
-```
-
-</Accordion>
-
 <Accordion title="curl">
 
 ```bash
diff --git a/redis/commands/search/search-describe.mdx b/redis/commands/search/search-describe.mdx
index d36fc311d..4078f4455 100644
--- a/redis/commands/search/search-describe.mdx
+++ b/redis/commands/search/search-describe.mdx
@@ -49,6 +49,14 @@ Returns `null` if the index does not exist.
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+SEARCH.DESCRIBE products
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
@@ -103,14 +111,6 @@ const description = await products.describe();
 
 </Accordion>
 
-<Accordion title="Redis CLI">
-
-```bash
-SEARCH.DESCRIBE products
-```
-
-</Accordion>
-
 <Accordion title="curl">
 
 ```bash
diff --git a/redis/commands/search/search-drop.mdx b/redis/commands/search/search-drop.mdx
index 28df1861a..ecdd7e361 100644
--- a/redis/commands/search/search-drop.mdx
+++ b/redis/commands/search/search-drop.mdx
@@ -25,6 +25,14 @@ Returns `1` if the index was dropped or `0` if the index was not found.
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+SEARCH.DROP products
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
@@ -79,14 +87,6 @@ const result = await products.drop();
 
 </Accordion>
 
-<Accordion title="Redis CLI">
-
-```bash
-SEARCH.DROP products
-```
-
-</Accordion>
-
 <Accordion title="curl">
 
 ```bash
diff --git a/redis/commands/search/search-listaliases.mdx b/redis/commands/search/search-listaliases.mdx
index 762e9728f..464e859fb 100644
--- a/redis/commands/search/search-listaliases.mdx
+++ b/redis/commands/search/search-listaliases.mdx
@@ -25,6 +25,14 @@ The SDKs below decode the pairs into an object or dictionary that maps each alia
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+SEARCH.LISTALIASES
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
@@ -79,14 +87,6 @@ const aliases = await search.alias.list();
 
 </Accordion>
 
-<Accordion title="Redis CLI">
-
-```bash
-SEARCH.LISTALIASES
-```
-
-</Accordion>
-
 <Accordion title="curl">
 
 ```bash
diff --git a/redis/commands/search/search-listindexes.mdx b/redis/commands/search/search-listindexes.mdx
index 7fcd975cf..8dee1fb90 100644
--- a/redis/commands/search/search-listindexes.mdx
+++ b/redis/commands/search/search-listindexes.mdx
@@ -43,6 +43,14 @@ Returns one entry per index, sorted by index name. Each entry is a map containin
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+SEARCH.LISTINDEXES MATCH 'product*' LIMIT 10 OFFSET 0
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
@@ -121,14 +129,6 @@ const indexes = await client.sendCommand([
 
 </Accordion>
 
-<Accordion title="Redis CLI">
-
-```bash
-SEARCH.LISTINDEXES MATCH 'product*' LIMIT 10 OFFSET 0
-```
-
-</Accordion>
-
 <Accordion title="curl">
 
 ```bash
diff --git a/redis/commands/search/search-query.mdx b/redis/commands/search/search-query.mdx
index 9c459e8ca..f67d41502 100644
--- a/redis/commands/search/search-query.mdx
+++ b/redis/commands/search/search-query.mdx
@@ -69,6 +69,14 @@ When `NOCONTENT` is used, each result is `[key, score]`. When `SELECT` is used,
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+SEARCH.QUERY products '{"name": "wireless"}' LIMIT 10 OFFSET 0
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
@@ -152,14 +160,6 @@ const results = await products.query({
 
 </Accordion>
 
-<Accordion title="Redis CLI">
-
-```bash
-SEARCH.QUERY products '{"name": "wireless"}' LIMIT 10 OFFSET 0
-```
-
-</Accordion>
-
 <Accordion title="curl">
 
 ```bash
diff --git a/redis/commands/search/search-reindex.mdx b/redis/commands/search/search-reindex.mdx
index 059c66bf1..cd3c275e1 100644
--- a/redis/commands/search/search-reindex.mdx
+++ b/redis/commands/search/search-reindex.mdx
@@ -27,7 +27,7 @@ Returns `1` when the index is rebuilt or `0` if the index does not exist.
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI">
+<Accordion title="Redis CLI" defaultOpen>
 
 ```bash
 SEARCH.REINDEX products
diff --git a/redis/commands/search/search-waitindexing.mdx b/redis/commands/search/search-waitindexing.mdx
index 6d9e97874..e044a3f92 100644
--- a/redis/commands/search/search-waitindexing.mdx
+++ b/redis/commands/search/search-waitindexing.mdx
@@ -29,6 +29,14 @@ Returns `1` when indexing is complete or `0` if the index was not found.
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+SEARCH.WAITINDEXING products
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
@@ -83,14 +91,6 @@ const result = await products.waitIndexing();
 
 </Accordion>
 
-<Accordion title="Redis CLI">
-
-```bash
-SEARCH.WAITINDEXING products
-```
-
-</Accordion>
-
 <Accordion title="curl">
 
 ```bash
diff --git a/redis/commands/server/acl.mdx b/redis/commands/server/acl.mdx
index a7deec90e..f4ebc6012 100644
--- a/redis/commands/server/acl.mdx
+++ b/redis/commands/server/acl.mdx
@@ -64,6 +64,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+ACL WHOAMI
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
diff --git a/redis/commands/server/command.mdx b/redis/commands/server/command.mdx
index 1e9da1a6f..130726f83 100644
--- a/redis/commands/server/command.mdx
+++ b/redis/commands/server/command.mdx
@@ -40,6 +40,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+COMMAND
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
diff --git a/redis/commands/server/config-get.mdx b/redis/commands/server/config-get.mdx
index b0724bcaf..89ad19df7 100644
--- a/redis/commands/server/config-get.mdx
+++ b/redis/commands/server/config-get.mdx
@@ -46,6 +46,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+CONFIG GET notify-keyspace-events
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
diff --git a/redis/commands/server/config-set.mdx b/redis/commands/server/config-set.mdx
index 144bd5ed9..4e4cdd343 100644
--- a/redis/commands/server/config-set.mdx
+++ b/redis/commands/server/config-set.mdx
@@ -47,6 +47,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+CONFIG SET notify-keyspace-events Ex
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
diff --git a/redis/commands/server/dbsize.mdx b/redis/commands/server/dbsize.mdx
index 0436699ac..55deab3ac 100644
--- a/redis/commands/server/dbsize.mdx
+++ b/redis/commands/server/dbsize.mdx
@@ -40,6 +40,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+DBSIZE
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/server/flushall.mdx b/redis/commands/server/flushall.mdx
index d2aa0c53e..25cd27aec 100644
--- a/redis/commands/server/flushall.mdx
+++ b/redis/commands/server/flushall.mdx
@@ -46,6 +46,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+FLUSHALL
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/server/flushdb.mdx b/redis/commands/server/flushdb.mdx
index 79acab99f..8b7017243 100644
--- a/redis/commands/server/flushdb.mdx
+++ b/redis/commands/server/flushdb.mdx
@@ -46,6 +46,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+FLUSHDB
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/server/info.mdx b/redis/commands/server/info.mdx
index 3f3c1c4d6..49ed6eb05 100644
--- a/redis/commands/server/info.mdx
+++ b/redis/commands/server/info.mdx
@@ -46,6 +46,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+INFO memory
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
diff --git a/redis/commands/server/monitor.mdx b/redis/commands/server/monitor.mdx
index 4ba9ed5c5..ff646717b 100644
--- a/redis/commands/server/monitor.mdx
+++ b/redis/commands/server/monitor.mdx
@@ -44,6 +44,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+MONITOR
+```
+
+</Accordion>
+
 <Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/server/time.mdx b/redis/commands/server/time.mdx
index 156dd047f..eb98e262e 100644
--- a/redis/commands/server/time.mdx
+++ b/redis/commands/server/time.mdx
@@ -36,6 +36,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+TIME
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/set/sadd.mdx b/redis/commands/set/sadd.mdx
index 09c185dac..9628dd42d 100644
--- a/redis/commands/set/sadd.mdx
+++ b/redis/commands/set/sadd.mdx
@@ -39,6 +39,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+SADD my-key member
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/set/scard.mdx b/redis/commands/set/scard.mdx
index 6280d9753..552245bad 100644
--- a/redis/commands/set/scard.mdx
+++ b/redis/commands/set/scard.mdx
@@ -38,6 +38,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+SCARD my-key
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/set/sdiff.mdx b/redis/commands/set/sdiff.mdx
index 9696fcd93..833c0da51 100644
--- a/redis/commands/set/sdiff.mdx
+++ b/redis/commands/set/sdiff.mdx
@@ -40,6 +40,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+SDIFF set1 set2
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/set/sdiffstore.mdx b/redis/commands/set/sdiffstore.mdx
index 3defe4516..6022b7a11 100644
--- a/redis/commands/set/sdiffstore.mdx
+++ b/redis/commands/set/sdiffstore.mdx
@@ -41,6 +41,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+SDIFFSTORE dest set1 set2
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/set/sinter.mdx b/redis/commands/set/sinter.mdx
index 763708033..07505673a 100644
--- a/redis/commands/set/sinter.mdx
+++ b/redis/commands/set/sinter.mdx
@@ -40,6 +40,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+SINTER set1 set2
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/set/sintercard.mdx b/redis/commands/set/sintercard.mdx
index 13e56b9ec..501221e33 100644
--- a/redis/commands/set/sintercard.mdx
+++ b/redis/commands/set/sintercard.mdx
@@ -46,6 +46,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+SINTERCARD 1 my-key
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/set/sinterstore.mdx b/redis/commands/set/sinterstore.mdx
index 52acb2b45..9c1d3e485 100644
--- a/redis/commands/set/sinterstore.mdx
+++ b/redis/commands/set/sinterstore.mdx
@@ -39,6 +39,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+SINTERSTORE destination set1 set2
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/set/sismember.mdx b/redis/commands/set/sismember.mdx
index 82260f638..c10c3667a 100644
--- a/redis/commands/set/sismember.mdx
+++ b/redis/commands/set/sismember.mdx
@@ -39,6 +39,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+SISMEMBER my-key member
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/set/smembers.mdx b/redis/commands/set/smembers.mdx
index 7763e49a5..473ef01d2 100644
--- a/redis/commands/set/smembers.mdx
+++ b/redis/commands/set/smembers.mdx
@@ -38,6 +38,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+SMEMBERS my-key
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/set/smismember.mdx b/redis/commands/set/smismember.mdx
index eb5708674..211d0ccb8 100644
--- a/redis/commands/set/smismember.mdx
+++ b/redis/commands/set/smismember.mdx
@@ -39,6 +39,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+SMISMEMBER my-key member
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/set/smove.mdx b/redis/commands/set/smove.mdx
index 5414602d5..2cc3b7835 100644
--- a/redis/commands/set/smove.mdx
+++ b/redis/commands/set/smove.mdx
@@ -42,6 +42,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+SMOVE source-key destination-key member
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/set/spop.mdx b/redis/commands/set/spop.mdx
index 77c1cb559..b8a712f01 100644
--- a/redis/commands/set/spop.mdx
+++ b/redis/commands/set/spop.mdx
@@ -41,6 +41,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+SPOP my-key
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/set/srandmember.mdx b/redis/commands/set/srandmember.mdx
index 58a8ab6a3..9da8c8da0 100644
--- a/redis/commands/set/srandmember.mdx
+++ b/redis/commands/set/srandmember.mdx
@@ -41,6 +41,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+SRANDMEMBER my-key
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/set/srem.mdx b/redis/commands/set/srem.mdx
index 0cebbe515..52cb78ce6 100644
--- a/redis/commands/set/srem.mdx
+++ b/redis/commands/set/srem.mdx
@@ -39,6 +39,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+SREM my-key member
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/set/sscan.mdx b/redis/commands/set/sscan.mdx
index 31073d688..43c77c6a1 100644
--- a/redis/commands/set/sscan.mdx
+++ b/redis/commands/set/sscan.mdx
@@ -48,6 +48,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+SSCAN my-key 0
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/set/sunion.mdx b/redis/commands/set/sunion.mdx
index 7c573679b..65915c5c9 100644
--- a/redis/commands/set/sunion.mdx
+++ b/redis/commands/set/sunion.mdx
@@ -38,6 +38,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+SUNION set1 set2
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/set/sunionstore.mdx b/redis/commands/set/sunionstore.mdx
index c6268de24..b525c61d0 100644
--- a/redis/commands/set/sunionstore.mdx
+++ b/redis/commands/set/sunionstore.mdx
@@ -39,6 +39,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+SUNIONSTORE destination set1 set2
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/sorted-set/bzmpop.mdx b/redis/commands/sorted-set/bzmpop.mdx
index 5a5765bb9..7e3947963 100644
--- a/redis/commands/sorted-set/bzmpop.mdx
+++ b/redis/commands/sorted-set/bzmpop.mdx
@@ -48,6 +48,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+BZMPOP 1.5 1 my-key MIN
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
diff --git a/redis/commands/sorted-set/bzpopmax.mdx b/redis/commands/sorted-set/bzpopmax.mdx
index dc46aef5d..ed4a7de6a 100644
--- a/redis/commands/sorted-set/bzpopmax.mdx
+++ b/redis/commands/sorted-set/bzpopmax.mdx
@@ -45,6 +45,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+BZPOPMAX my-key 1.5
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
diff --git a/redis/commands/sorted-set/bzpopmin.mdx b/redis/commands/sorted-set/bzpopmin.mdx
index d22f2c3ac..f45419752 100644
--- a/redis/commands/sorted-set/bzpopmin.mdx
+++ b/redis/commands/sorted-set/bzpopmin.mdx
@@ -45,6 +45,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+BZPOPMIN my-key 1.5
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
diff --git a/redis/commands/sorted-set/zadd.mdx b/redis/commands/sorted-set/zadd.mdx
index c5e842a64..6b13ee971 100644
--- a/redis/commands/sorted-set/zadd.mdx
+++ b/redis/commands/sorted-set/zadd.mdx
@@ -50,6 +50,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+ZADD my-key 1.5 member
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/sorted-set/zcard.mdx b/redis/commands/sorted-set/zcard.mdx
index 7bf0a69bf..4a6975478 100644
--- a/redis/commands/sorted-set/zcard.mdx
+++ b/redis/commands/sorted-set/zcard.mdx
@@ -38,6 +38,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+ZCARD my-key
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/sorted-set/zcount.mdx b/redis/commands/sorted-set/zcount.mdx
index d70d001c8..cdccb5888 100644
--- a/redis/commands/sorted-set/zcount.mdx
+++ b/redis/commands/sorted-set/zcount.mdx
@@ -42,6 +42,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+ZCOUNT my-key 1.5 1.5
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/sorted-set/zdiff.mdx b/redis/commands/sorted-set/zdiff.mdx
index 99f85994f..cb31e9856 100644
--- a/redis/commands/sorted-set/zdiff.mdx
+++ b/redis/commands/sorted-set/zdiff.mdx
@@ -48,6 +48,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+ZDIFF 1 my-key
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
diff --git a/redis/commands/sorted-set/zdiffstore.mdx b/redis/commands/sorted-set/zdiffstore.mdx
index e9ad2f7ce..348872789 100644
--- a/redis/commands/sorted-set/zdiffstore.mdx
+++ b/redis/commands/sorted-set/zdiffstore.mdx
@@ -46,6 +46,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+ZDIFFSTORE destination-key 1 my-key
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/sorted-set/zincrby.mdx b/redis/commands/sorted-set/zincrby.mdx
index bc89d4152..a10b88943 100644
--- a/redis/commands/sorted-set/zincrby.mdx
+++ b/redis/commands/sorted-set/zincrby.mdx
@@ -46,6 +46,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+ZINCRBY my-key 1 member
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/sorted-set/zinter.mdx b/redis/commands/sorted-set/zinter.mdx
index 8068bd751..65736698c 100644
--- a/redis/commands/sorted-set/zinter.mdx
+++ b/redis/commands/sorted-set/zinter.mdx
@@ -53,6 +53,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+ZINTER 1 my-key
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
diff --git a/redis/commands/sorted-set/zintercard.mdx b/redis/commands/sorted-set/zintercard.mdx
index 9d0680748..b4497df67 100644
--- a/redis/commands/sorted-set/zintercard.mdx
+++ b/redis/commands/sorted-set/zintercard.mdx
@@ -40,6 +40,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+ZINTERCARD 1 my-key
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
diff --git a/redis/commands/sorted-set/zinterstore.mdx b/redis/commands/sorted-set/zinterstore.mdx
index 386ade27e..bc5b76290 100644
--- a/redis/commands/sorted-set/zinterstore.mdx
+++ b/redis/commands/sorted-set/zinterstore.mdx
@@ -50,6 +50,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+ZINTERSTORE destination-key 1 my-key
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/sorted-set/zlexcount.mdx b/redis/commands/sorted-set/zlexcount.mdx
index 29f99daa4..f5d2885ba 100644
--- a/redis/commands/sorted-set/zlexcount.mdx
+++ b/redis/commands/sorted-set/zlexcount.mdx
@@ -42,6 +42,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+ZLEXCOUNT my-key - +
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/sorted-set/zmpop.mdx b/redis/commands/sorted-set/zmpop.mdx
index 21c703017..141ea1b18 100644
--- a/redis/commands/sorted-set/zmpop.mdx
+++ b/redis/commands/sorted-set/zmpop.mdx
@@ -47,6 +47,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+ZMPOP 1 my-key MIN
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
diff --git a/redis/commands/sorted-set/zmscore.mdx b/redis/commands/sorted-set/zmscore.mdx
index d37527250..9d216b2a5 100644
--- a/redis/commands/sorted-set/zmscore.mdx
+++ b/redis/commands/sorted-set/zmscore.mdx
@@ -43,6 +43,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+ZMSCORE my-key member
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/sorted-set/zpopmax.mdx b/redis/commands/sorted-set/zpopmax.mdx
index 798307b31..70c7f06e6 100644
--- a/redis/commands/sorted-set/zpopmax.mdx
+++ b/redis/commands/sorted-set/zpopmax.mdx
@@ -45,6 +45,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+ZPOPMAX my-key
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/sorted-set/zpopmin.mdx b/redis/commands/sorted-set/zpopmin.mdx
index 969d34f0c..00d9e0c2a 100644
--- a/redis/commands/sorted-set/zpopmin.mdx
+++ b/redis/commands/sorted-set/zpopmin.mdx
@@ -45,6 +45,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+ZPOPMIN my-key
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/sorted-set/zrandmember.mdx b/redis/commands/sorted-set/zrandmember.mdx
index 6cf68f756..54956aa67 100644
--- a/redis/commands/sorted-set/zrandmember.mdx
+++ b/redis/commands/sorted-set/zrandmember.mdx
@@ -45,6 +45,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+ZRANDMEMBER my-key
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
diff --git a/redis/commands/sorted-set/zrange.mdx b/redis/commands/sorted-set/zrange.mdx
index 113f371ae..a91f02824 100644
--- a/redis/commands/sorted-set/zrange.mdx
+++ b/redis/commands/sorted-set/zrange.mdx
@@ -57,6 +57,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+ZRANGE my-key 0 -1
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/sorted-set/zrangebylex.mdx b/redis/commands/sorted-set/zrangebylex.mdx
index bfd88dc97..802b424a2 100644
--- a/redis/commands/sorted-set/zrangebylex.mdx
+++ b/redis/commands/sorted-set/zrangebylex.mdx
@@ -47,6 +47,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+ZRANGEBYLEX my-key - +
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
diff --git a/redis/commands/sorted-set/zrangebyscore.mdx b/redis/commands/sorted-set/zrangebyscore.mdx
index 107fdee81..efe64d322 100644
--- a/redis/commands/sorted-set/zrangebyscore.mdx
+++ b/redis/commands/sorted-set/zrangebyscore.mdx
@@ -52,6 +52,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+ZRANGEBYSCORE my-key 1.5 1.5
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
diff --git a/redis/commands/sorted-set/zrangestore.mdx b/redis/commands/sorted-set/zrangestore.mdx
index 832f748c2..dc9cc2a26 100644
--- a/redis/commands/sorted-set/zrangestore.mdx
+++ b/redis/commands/sorted-set/zrangestore.mdx
@@ -49,6 +49,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+ZRANGESTORE destination-key source-key -inf +inf BYSCORE
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
diff --git a/redis/commands/sorted-set/zrank.mdx b/redis/commands/sorted-set/zrank.mdx
index c509913e6..bd321f937 100644
--- a/redis/commands/sorted-set/zrank.mdx
+++ b/redis/commands/sorted-set/zrank.mdx
@@ -46,6 +46,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+ZRANK my-key member
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/sorted-set/zrem.mdx b/redis/commands/sorted-set/zrem.mdx
index a33555e05..d0be824e5 100644
--- a/redis/commands/sorted-set/zrem.mdx
+++ b/redis/commands/sorted-set/zrem.mdx
@@ -39,6 +39,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+ZREM my-key member
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/sorted-set/zremrangebylex.mdx b/redis/commands/sorted-set/zremrangebylex.mdx
index 2bc0fa0f8..bc1ee425d 100644
--- a/redis/commands/sorted-set/zremrangebylex.mdx
+++ b/redis/commands/sorted-set/zremrangebylex.mdx
@@ -42,6 +42,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+ZREMRANGEBYLEX my-key - +
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/sorted-set/zremrangebyrank.mdx b/redis/commands/sorted-set/zremrangebyrank.mdx
index 44ba71ac3..031ef9e50 100644
--- a/redis/commands/sorted-set/zremrangebyrank.mdx
+++ b/redis/commands/sorted-set/zremrangebyrank.mdx
@@ -42,6 +42,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+ZREMRANGEBYRANK my-key 0 0
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/sorted-set/zremrangebyscore.mdx b/redis/commands/sorted-set/zremrangebyscore.mdx
index 6c3078bbc..bf5ca715e 100644
--- a/redis/commands/sorted-set/zremrangebyscore.mdx
+++ b/redis/commands/sorted-set/zremrangebyscore.mdx
@@ -42,6 +42,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+ZREMRANGEBYSCORE my-key 1.5 1.5
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/sorted-set/zrevrange.mdx b/redis/commands/sorted-set/zrevrange.mdx
index fc9e1bffb..6f5978d6d 100644
--- a/redis/commands/sorted-set/zrevrange.mdx
+++ b/redis/commands/sorted-set/zrevrange.mdx
@@ -49,6 +49,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+ZREVRANGE my-key 0 0
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
diff --git a/redis/commands/sorted-set/zrevrangebylex.mdx b/redis/commands/sorted-set/zrevrangebylex.mdx
index 5b6468fb1..c940cc673 100644
--- a/redis/commands/sorted-set/zrevrangebylex.mdx
+++ b/redis/commands/sorted-set/zrevrangebylex.mdx
@@ -47,6 +47,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+ZREVRANGEBYLEX my-key + -
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
diff --git a/redis/commands/sorted-set/zrevrangebyscore.mdx b/redis/commands/sorted-set/zrevrangebyscore.mdx
index f72154562..278546caa 100644
--- a/redis/commands/sorted-set/zrevrangebyscore.mdx
+++ b/redis/commands/sorted-set/zrevrangebyscore.mdx
@@ -50,6 +50,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+ZREVRANGEBYSCORE my-key 1.5 1.5
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
diff --git a/redis/commands/sorted-set/zrevrank.mdx b/redis/commands/sorted-set/zrevrank.mdx
index 8fd279abc..80e515273 100644
--- a/redis/commands/sorted-set/zrevrank.mdx
+++ b/redis/commands/sorted-set/zrevrank.mdx
@@ -44,6 +44,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+ZREVRANK my-key member
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/sorted-set/zscan.mdx b/redis/commands/sorted-set/zscan.mdx
index ed640de98..d39ae6467 100644
--- a/redis/commands/sorted-set/zscan.mdx
+++ b/redis/commands/sorted-set/zscan.mdx
@@ -49,6 +49,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+ZSCAN my-key 0
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/sorted-set/zscore.mdx b/redis/commands/sorted-set/zscore.mdx
index fcb6cabba..2ffe75a12 100644
--- a/redis/commands/sorted-set/zscore.mdx
+++ b/redis/commands/sorted-set/zscore.mdx
@@ -43,6 +43,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+ZSCORE my-key member
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/sorted-set/zunion.mdx b/redis/commands/sorted-set/zunion.mdx
index dbdd990fe..a806b09e1 100644
--- a/redis/commands/sorted-set/zunion.mdx
+++ b/redis/commands/sorted-set/zunion.mdx
@@ -52,6 +52,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+ZUNION 1 my-key
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/sorted-set/zunionstore.mdx b/redis/commands/sorted-set/zunionstore.mdx
index 8be24714c..ad0fc9e63 100644
--- a/redis/commands/sorted-set/zunionstore.mdx
+++ b/redis/commands/sorted-set/zunionstore.mdx
@@ -50,6 +50,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+ZUNIONSTORE destination-key 1 my-key
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/streams/xack.mdx b/redis/commands/streams/xack.mdx
index 66ebe1346..31778dab4 100644
--- a/redis/commands/streams/xack.mdx
+++ b/redis/commands/streams/xack.mdx
@@ -42,6 +42,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+XACK my-key workers 0-0
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/streams/xackdel.mdx b/redis/commands/streams/xackdel.mdx
index 4e1399ee0..5682ddd17 100644
--- a/redis/commands/streams/xackdel.mdx
+++ b/redis/commands/streams/xackdel.mdx
@@ -45,6 +45,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+XACKDEL my-key workers IDS 1 0-0
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/streams/xadd.mdx b/redis/commands/streams/xadd.mdx
index 11d5c8f73..2157e522d 100644
--- a/redis/commands/streams/xadd.mdx
+++ b/redis/commands/streams/xadd.mdx
@@ -51,6 +51,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+XADD my-key * field value
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/streams/xautoclaim.mdx b/redis/commands/streams/xautoclaim.mdx
index aa26ad596..85000b71c 100644
--- a/redis/commands/streams/xautoclaim.mdx
+++ b/redis/commands/streams/xautoclaim.mdx
@@ -46,6 +46,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+XAUTOCLAIM my-key workers worker-1 60000 0-0
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/streams/xclaim.mdx b/redis/commands/streams/xclaim.mdx
index ec4229bc8..39b99051a 100644
--- a/redis/commands/streams/xclaim.mdx
+++ b/redis/commands/streams/xclaim.mdx
@@ -58,6 +58,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+XCLAIM my-key workers worker-1 60000 0-0
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/streams/xdel.mdx b/redis/commands/streams/xdel.mdx
index cf0201033..6c13583b1 100644
--- a/redis/commands/streams/xdel.mdx
+++ b/redis/commands/streams/xdel.mdx
@@ -41,6 +41,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+XDEL my-key 0-0
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/streams/xdelex.mdx b/redis/commands/streams/xdelex.mdx
index b45ca79d0..9fbe09b87 100644
--- a/redis/commands/streams/xdelex.mdx
+++ b/redis/commands/streams/xdelex.mdx
@@ -44,6 +44,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+XDELEX my-key IDS 1 0-0
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/streams/xgroup.mdx b/redis/commands/streams/xgroup.mdx
index ab7faf482..b025ac0e8 100644
--- a/redis/commands/streams/xgroup.mdx
+++ b/redis/commands/streams/xgroup.mdx
@@ -51,6 +51,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+XGROUP CREATE events workers $ MKSTREAM
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/streams/xinfo-consumers.mdx b/redis/commands/streams/xinfo-consumers.mdx
index 79d6d68b1..29655c2d9 100644
--- a/redis/commands/streams/xinfo-consumers.mdx
+++ b/redis/commands/streams/xinfo-consumers.mdx
@@ -39,6 +39,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+XINFO CONSUMERS my-key workers
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/streams/xinfo-groups.mdx b/redis/commands/streams/xinfo-groups.mdx
index da55280af..7e901bbac 100644
--- a/redis/commands/streams/xinfo-groups.mdx
+++ b/redis/commands/streams/xinfo-groups.mdx
@@ -38,6 +38,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+XINFO GROUPS my-key
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/streams/xinfo-stream.mdx b/redis/commands/streams/xinfo-stream.mdx
index ade38210d..bbef591ab 100644
--- a/redis/commands/streams/xinfo-stream.mdx
+++ b/redis/commands/streams/xinfo-stream.mdx
@@ -41,6 +41,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+XINFO STREAM my-key
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
diff --git a/redis/commands/streams/xlen.mdx b/redis/commands/streams/xlen.mdx
index f6292c23f..9ee31be57 100644
--- a/redis/commands/streams/xlen.mdx
+++ b/redis/commands/streams/xlen.mdx
@@ -38,6 +38,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+XLEN my-key
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/streams/xpending.mdx b/redis/commands/streams/xpending.mdx
index 7f7d2e71e..0199d949b 100644
--- a/redis/commands/streams/xpending.mdx
+++ b/redis/commands/streams/xpending.mdx
@@ -47,6 +47,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+XPENDING my-key workers
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/streams/xrange.mdx b/redis/commands/streams/xrange.mdx
index d5ad43765..01dd8725d 100644
--- a/redis/commands/streams/xrange.mdx
+++ b/redis/commands/streams/xrange.mdx
@@ -43,6 +43,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+XRANGE my-key - +
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/streams/xread.mdx b/redis/commands/streams/xread.mdx
index 2818a45a8..742b8a387 100644
--- a/redis/commands/streams/xread.mdx
+++ b/redis/commands/streams/xread.mdx
@@ -52,6 +52,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+XREAD STREAMS my-key 0-0
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/streams/xreadgroup.mdx b/redis/commands/streams/xreadgroup.mdx
index fa29f7ce8..9c53e663a 100644
--- a/redis/commands/streams/xreadgroup.mdx
+++ b/redis/commands/streams/xreadgroup.mdx
@@ -55,6 +55,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+XREADGROUP GROUP workers worker-1 STREAMS my-key 0-0
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/streams/xrevrange.mdx b/redis/commands/streams/xrevrange.mdx
index 663e0c712..8647a5e72 100644
--- a/redis/commands/streams/xrevrange.mdx
+++ b/redis/commands/streams/xrevrange.mdx
@@ -43,6 +43,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+XREVRANGE my-key + -
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/streams/xtrim.mdx b/redis/commands/streams/xtrim.mdx
index 771ab0aaf..a5b09813c 100644
--- a/redis/commands/streams/xtrim.mdx
+++ b/redis/commands/streams/xtrim.mdx
@@ -46,6 +46,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+XTRIM my-key MAXLEN 100
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/string/append.mdx b/redis/commands/string/append.mdx
index ced6a4f9f..5dc2678f3 100644
--- a/redis/commands/string/append.mdx
+++ b/redis/commands/string/append.mdx
@@ -39,6 +39,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+APPEND my-key value
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/string/decr.mdx b/redis/commands/string/decr.mdx
index 25111b01f..f43604344 100644
--- a/redis/commands/string/decr.mdx
+++ b/redis/commands/string/decr.mdx
@@ -38,6 +38,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+DECR my-key
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/string/decrby.mdx b/redis/commands/string/decrby.mdx
index c5fc979ee..374430eb4 100644
--- a/redis/commands/string/decrby.mdx
+++ b/redis/commands/string/decrby.mdx
@@ -39,6 +39,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+DECRBY my-key 1
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/string/delex.mdx b/redis/commands/string/delex.mdx
index 3060f0f68..774aa9eb0 100644
--- a/redis/commands/string/delex.mdx
+++ b/redis/commands/string/delex.mdx
@@ -47,6 +47,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+DELEX lock:job-1 IFEQ worker-1
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
diff --git a/redis/commands/string/digest.mdx b/redis/commands/string/digest.mdx
index 1687c9921..0c16d8e67 100644
--- a/redis/commands/string/digest.mdx
+++ b/redis/commands/string/digest.mdx
@@ -45,6 +45,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+DIGEST lock:job-1
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
diff --git a/redis/commands/string/get.mdx b/redis/commands/string/get.mdx
index 5e44e151a..51b2466e0 100644
--- a/redis/commands/string/get.mdx
+++ b/redis/commands/string/get.mdx
@@ -38,6 +38,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+GET my-key
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/string/getdel.mdx b/redis/commands/string/getdel.mdx
index 5560dcadf..8a08bd833 100644
--- a/redis/commands/string/getdel.mdx
+++ b/redis/commands/string/getdel.mdx
@@ -38,6 +38,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+GETDEL my-key
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/string/getex.mdx b/redis/commands/string/getex.mdx
index 85d88bcae..e2592db2b 100644
--- a/redis/commands/string/getex.mdx
+++ b/redis/commands/string/getex.mdx
@@ -43,6 +43,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+GETEX my-key
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/string/getrange.mdx b/redis/commands/string/getrange.mdx
index 45f8eec47..2ea20a6e5 100644
--- a/redis/commands/string/getrange.mdx
+++ b/redis/commands/string/getrange.mdx
@@ -46,6 +46,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+GETRANGE my-key 0 1
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/string/getset.mdx b/redis/commands/string/getset.mdx
index a85359b67..683172246 100644
--- a/redis/commands/string/getset.mdx
+++ b/redis/commands/string/getset.mdx
@@ -45,6 +45,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+GETSET my-key value
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/string/incr.mdx b/redis/commands/string/incr.mdx
index aa111a67f..b6854da22 100644
--- a/redis/commands/string/incr.mdx
+++ b/redis/commands/string/incr.mdx
@@ -40,6 +40,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+INCR my-key
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/string/incrby.mdx b/redis/commands/string/incrby.mdx
index 784a22c22..ead1fd120 100644
--- a/redis/commands/string/incrby.mdx
+++ b/redis/commands/string/incrby.mdx
@@ -41,6 +41,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+INCRBY my-key 1
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/string/incrbyfloat.mdx b/redis/commands/string/incrbyfloat.mdx
index 030b56133..bf962e59e 100644
--- a/redis/commands/string/incrbyfloat.mdx
+++ b/redis/commands/string/incrbyfloat.mdx
@@ -45,6 +45,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+INCRBYFLOAT my-key 1.5
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/string/mget.mdx b/redis/commands/string/mget.mdx
index 57ee65793..285a59d7a 100644
--- a/redis/commands/string/mget.mdx
+++ b/redis/commands/string/mget.mdx
@@ -40,6 +40,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+MGET key1 key2 key3
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/string/mset.mdx b/redis/commands/string/mset.mdx
index 421e175d1..13206710b 100644
--- a/redis/commands/string/mset.mdx
+++ b/redis/commands/string/mset.mdx
@@ -40,6 +40,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+MSET key1 1 key2 hello
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/string/msetnx.mdx b/redis/commands/string/msetnx.mdx
index f4b5a53b5..8c532de4c 100644
--- a/redis/commands/string/msetnx.mdx
+++ b/redis/commands/string/msetnx.mdx
@@ -38,6 +38,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+MSETNX key1 value1 key2 value2
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/string/psetex.mdx b/redis/commands/string/psetex.mdx
index f4022f007..3214f1a19 100644
--- a/redis/commands/string/psetex.mdx
+++ b/redis/commands/string/psetex.mdx
@@ -46,6 +46,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+PSETEX my-key 1000 value
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/string/set.mdx b/redis/commands/string/set.mdx
index 27d6ec5fb..5298aa414 100644
--- a/redis/commands/string/set.mdx
+++ b/redis/commands/string/set.mdx
@@ -57,6 +57,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+SET my-key value
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/string/setex.mdx b/redis/commands/string/setex.mdx
index 2cd69f79f..c59069759 100644
--- a/redis/commands/string/setex.mdx
+++ b/redis/commands/string/setex.mdx
@@ -46,6 +46,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+SETEX my-key 1000 value
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/string/setnx.mdx b/redis/commands/string/setnx.mdx
index ed946a761..8d19450b2 100644
--- a/redis/commands/string/setnx.mdx
+++ b/redis/commands/string/setnx.mdx
@@ -45,6 +45,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+SETNX my-key value
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/string/setrange.mdx b/redis/commands/string/setrange.mdx
index 158c5512f..1d7f229c1 100644
--- a/redis/commands/string/setrange.mdx
+++ b/redis/commands/string/setrange.mdx
@@ -42,6 +42,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+SETRANGE my-key 0 value
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/string/strlen.mdx b/redis/commands/string/strlen.mdx
index cbe82dcbe..547aec3bf 100644
--- a/redis/commands/string/strlen.mdx
+++ b/redis/commands/string/strlen.mdx
@@ -38,6 +38,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+STRLEN my-key
+```
+
+</Accordion>
+
 <Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/transactions/discard.mdx b/redis/commands/transactions/discard.mdx
index 19d094edf..4516af76d 100644
--- a/redis/commands/transactions/discard.mdx
+++ b/redis/commands/transactions/discard.mdx
@@ -42,6 +42,16 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+MULTI
+SET balance 100
+DISCARD
+```
+
+</Accordion>
+
 <Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/transactions/exec.mdx b/redis/commands/transactions/exec.mdx
index 3b21551d3..38f477ef8 100644
--- a/redis/commands/transactions/exec.mdx
+++ b/redis/commands/transactions/exec.mdx
@@ -44,6 +44,16 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+MULTI
+SET balance 100
+EXEC
+```
+
+</Accordion>
+
 <Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/transactions/multi.mdx b/redis/commands/transactions/multi.mdx
index e02e9b21e..cecc85882 100644
--- a/redis/commands/transactions/multi.mdx
+++ b/redis/commands/transactions/multi.mdx
@@ -44,6 +44,16 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+MULTI
+SET balance 100
+EXEC
+```
+
+</Accordion>
+
 <Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/transactions/unwatch.mdx b/redis/commands/transactions/unwatch.mdx
index 243c7126b..280d8f3cf 100644
--- a/redis/commands/transactions/unwatch.mdx
+++ b/redis/commands/transactions/unwatch.mdx
@@ -42,6 +42,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+UNWATCH
+```
+
+</Accordion>
+
 <Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
diff --git a/redis/commands/transactions/watch.mdx b/redis/commands/transactions/watch.mdx
index 87bf0e041..19afc67d6 100644
--- a/redis/commands/transactions/watch.mdx
+++ b/redis/commands/transactions/watch.mdx
@@ -46,6 +46,14 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
+<Accordion title="Redis CLI" defaultOpen>
+
+```bash
+WATCH balance
+```
+
+</Accordion>
+
 <Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts

From 030071dbcae99853d123f281a81c7e13fc06b2bc Mon Sep 17 00:00:00 2001
From: Mehmet Dogan <mehmet@dogan.io>
Date: Thu, 13 Aug 2026 15:11:12 +0300
Subject: [PATCH 11/12] Add redis-cli icon

---
 redis/commands/bitmap/bitcount.mdx             | 2 +-
 redis/commands/bitmap/bitfield-ro.mdx          | 2 +-
 redis/commands/bitmap/bitfield.mdx             | 2 +-
 redis/commands/bitmap/bitop.mdx                | 2 +-
 redis/commands/bitmap/bitpos.mdx               | 2 +-
 redis/commands/bitmap/getbit.mdx               | 2 +-
 redis/commands/bitmap/setbit.mdx               | 2 +-
 redis/commands/connection/auth.mdx             | 2 +-
 redis/commands/connection/client-getname.mdx   | 2 +-
 redis/commands/connection/client-id.mdx        | 2 +-
 redis/commands/connection/client-info.mdx      | 2 +-
 redis/commands/connection/client-list.mdx      | 2 +-
 redis/commands/connection/client-setinfo.mdx   | 2 +-
 redis/commands/connection/client-setname.mdx   | 2 +-
 redis/commands/connection/echo.mdx             | 2 +-
 redis/commands/connection/hello.mdx            | 2 +-
 redis/commands/connection/ping.mdx             | 2 +-
 redis/commands/connection/quit.mdx             | 2 +-
 redis/commands/connection/reset.mdx            | 2 +-
 redis/commands/connection/select.mdx           | 2 +-
 redis/commands/functions/fcall-ro.mdx          | 2 +-
 redis/commands/functions/fcall.mdx             | 2 +-
 redis/commands/functions/function-delete.mdx   | 2 +-
 redis/commands/functions/function-flush.mdx    | 2 +-
 redis/commands/functions/function-kill.mdx     | 2 +-
 redis/commands/functions/function-list.mdx     | 2 +-
 redis/commands/functions/function-load.mdx     | 2 +-
 redis/commands/functions/function-stats.mdx    | 2 +-
 redis/commands/generic/copy.mdx                | 2 +-
 redis/commands/generic/del.mdx                 | 2 +-
 redis/commands/generic/dump.mdx                | 2 +-
 redis/commands/generic/exists.mdx              | 2 +-
 redis/commands/generic/expire.mdx              | 2 +-
 redis/commands/generic/expireat.mdx            | 2 +-
 redis/commands/generic/expiretime.mdx          | 2 +-
 redis/commands/generic/keys.mdx                | 2 +-
 redis/commands/generic/memory-usage.mdx        | 2 +-
 redis/commands/generic/persist.mdx             | 2 +-
 redis/commands/generic/pexpire.mdx             | 2 +-
 redis/commands/generic/pexpireat.mdx           | 2 +-
 redis/commands/generic/pexpiretime.mdx         | 2 +-
 redis/commands/generic/pttl.mdx                | 2 +-
 redis/commands/generic/randomkey.mdx           | 2 +-
 redis/commands/generic/rename.mdx              | 2 +-
 redis/commands/generic/renamenx.mdx            | 2 +-
 redis/commands/generic/restore.mdx             | 2 +-
 redis/commands/generic/scan.mdx                | 2 +-
 redis/commands/generic/touch.mdx               | 2 +-
 redis/commands/generic/ttl.mdx                 | 2 +-
 redis/commands/generic/type.mdx                | 2 +-
 redis/commands/generic/unlink.mdx              | 2 +-
 redis/commands/generic/wait.mdx                | 2 +-
 redis/commands/generic/waitaof.mdx             | 2 +-
 redis/commands/geo/geoadd.mdx                  | 2 +-
 redis/commands/geo/geodist.mdx                 | 2 +-
 redis/commands/geo/geohash.mdx                 | 2 +-
 redis/commands/geo/geopos.mdx                  | 2 +-
 redis/commands/geo/georadius-ro.mdx            | 2 +-
 redis/commands/geo/georadius.mdx               | 2 +-
 redis/commands/geo/georadiusbymember-ro.mdx    | 2 +-
 redis/commands/geo/georadiusbymember.mdx       | 2 +-
 redis/commands/geo/geosearch.mdx               | 2 +-
 redis/commands/geo/geosearchstore.mdx          | 2 +-
 redis/commands/hash/hdel.mdx                   | 2 +-
 redis/commands/hash/hexists.mdx                | 2 +-
 redis/commands/hash/hexpire.mdx                | 2 +-
 redis/commands/hash/hexpireat.mdx              | 2 +-
 redis/commands/hash/hexpiretime.mdx            | 2 +-
 redis/commands/hash/hget.mdx                   | 2 +-
 redis/commands/hash/hgetall.mdx                | 2 +-
 redis/commands/hash/hgetdel.mdx                | 2 +-
 redis/commands/hash/hgetex.mdx                 | 2 +-
 redis/commands/hash/hincrby.mdx                | 2 +-
 redis/commands/hash/hincrbyfloat.mdx           | 2 +-
 redis/commands/hash/hkeys.mdx                  | 2 +-
 redis/commands/hash/hlen.mdx                   | 2 +-
 redis/commands/hash/hmget.mdx                  | 2 +-
 redis/commands/hash/hmset.mdx                  | 2 +-
 redis/commands/hash/hpersist.mdx               | 2 +-
 redis/commands/hash/hpexpire.mdx               | 2 +-
 redis/commands/hash/hpexpireat.mdx             | 2 +-
 redis/commands/hash/hpexpiretime.mdx           | 2 +-
 redis/commands/hash/hpttl.mdx                  | 2 +-
 redis/commands/hash/hrandfield.mdx             | 2 +-
 redis/commands/hash/hscan.mdx                  | 2 +-
 redis/commands/hash/hset.mdx                   | 2 +-
 redis/commands/hash/hsetex.mdx                 | 2 +-
 redis/commands/hash/hsetnx.mdx                 | 2 +-
 redis/commands/hash/hstrlen.mdx                | 2 +-
 redis/commands/hash/httl.mdx                   | 2 +-
 redis/commands/hash/hvals.mdx                  | 2 +-
 redis/commands/hyperloglog/pfadd.mdx           | 2 +-
 redis/commands/hyperloglog/pfcount.mdx         | 2 +-
 redis/commands/hyperloglog/pfmerge.mdx         | 2 +-
 redis/commands/json/json-arrappend.mdx         | 2 +-
 redis/commands/json/json-arrindex.mdx          | 2 +-
 redis/commands/json/json-arrinsert.mdx         | 2 +-
 redis/commands/json/json-arrlen.mdx            | 2 +-
 redis/commands/json/json-arrpop.mdx            | 2 +-
 redis/commands/json/json-arrtrim.mdx           | 2 +-
 redis/commands/json/json-clear.mdx             | 2 +-
 redis/commands/json/json-debug.mdx             | 2 +-
 redis/commands/json/json-del.mdx               | 2 +-
 redis/commands/json/json-forget.mdx            | 2 +-
 redis/commands/json/json-get.mdx               | 2 +-
 redis/commands/json/json-merge.mdx             | 2 +-
 redis/commands/json/json-mget.mdx              | 2 +-
 redis/commands/json/json-mset.mdx              | 2 +-
 redis/commands/json/json-numincrby.mdx         | 2 +-
 redis/commands/json/json-nummultby.mdx         | 2 +-
 redis/commands/json/json-objkeys.mdx           | 2 +-
 redis/commands/json/json-objlen.mdx            | 2 +-
 redis/commands/json/json-resp.mdx              | 2 +-
 redis/commands/json/json-set.mdx               | 2 +-
 redis/commands/json/json-strappend.mdx         | 2 +-
 redis/commands/json/json-strlen.mdx            | 2 +-
 redis/commands/json/json-toggle.mdx            | 2 +-
 redis/commands/json/json-type.mdx              | 2 +-
 redis/commands/list/blmove.mdx                 | 2 +-
 redis/commands/list/blmpop.mdx                 | 2 +-
 redis/commands/list/blpop.mdx                  | 2 +-
 redis/commands/list/brpop.mdx                  | 2 +-
 redis/commands/list/brpoplpush.mdx             | 2 +-
 redis/commands/list/lindex.mdx                 | 2 +-
 redis/commands/list/linsert.mdx                | 2 +-
 redis/commands/list/llen.mdx                   | 2 +-
 redis/commands/list/lmove.mdx                  | 2 +-
 redis/commands/list/lmpop.mdx                  | 2 +-
 redis/commands/list/lpop.mdx                   | 2 +-
 redis/commands/list/lpos.mdx                   | 2 +-
 redis/commands/list/lpush.mdx                  | 2 +-
 redis/commands/list/lpushx.mdx                 | 2 +-
 redis/commands/list/lrange.mdx                 | 2 +-
 redis/commands/list/lrem.mdx                   | 2 +-
 redis/commands/list/lset.mdx                   | 2 +-
 redis/commands/list/ltrim.mdx                  | 2 +-
 redis/commands/list/rpop.mdx                   | 2 +-
 redis/commands/list/rpoplpush.mdx              | 2 +-
 redis/commands/list/rpush.mdx                  | 2 +-
 redis/commands/list/rpushx.mdx                 | 2 +-
 redis/commands/pub-sub/psubscribe.mdx          | 2 +-
 redis/commands/pub-sub/publish.mdx             | 2 +-
 redis/commands/pub-sub/pubsub.mdx              | 2 +-
 redis/commands/pub-sub/punsubscribe.mdx        | 2 +-
 redis/commands/pub-sub/subscribe.mdx           | 2 +-
 redis/commands/pub-sub/unsubscribe.mdx         | 2 +-
 redis/commands/scripting/eval-ro.mdx           | 2 +-
 redis/commands/scripting/eval.mdx              | 2 +-
 redis/commands/scripting/evalsha-ro.mdx        | 2 +-
 redis/commands/scripting/evalsha.mdx           | 2 +-
 redis/commands/scripting/script-exists.mdx     | 2 +-
 redis/commands/scripting/script-flush.mdx      | 2 +-
 redis/commands/scripting/script-kill.mdx       | 2 +-
 redis/commands/scripting/script-load.mdx       | 2 +-
 redis/commands/search/search-aggregate.mdx     | 2 +-
 redis/commands/search/search-aliasadd.mdx      | 2 +-
 redis/commands/search/search-aliasdel.mdx      | 2 +-
 redis/commands/search/search-count.mdx         | 2 +-
 redis/commands/search/search-create.mdx        | 2 +-
 redis/commands/search/search-describe.mdx      | 2 +-
 redis/commands/search/search-drop.mdx          | 2 +-
 redis/commands/search/search-listaliases.mdx   | 2 +-
 redis/commands/search/search-listindexes.mdx   | 2 +-
 redis/commands/search/search-query.mdx         | 2 +-
 redis/commands/search/search-reindex.mdx       | 2 +-
 redis/commands/search/search-waitindexing.mdx  | 2 +-
 redis/commands/server/acl.mdx                  | 2 +-
 redis/commands/server/command.mdx              | 2 +-
 redis/commands/server/config-get.mdx           | 2 +-
 redis/commands/server/config-set.mdx           | 2 +-
 redis/commands/server/dbsize.mdx               | 2 +-
 redis/commands/server/flushall.mdx             | 2 +-
 redis/commands/server/flushdb.mdx              | 2 +-
 redis/commands/server/info.mdx                 | 2 +-
 redis/commands/server/monitor.mdx              | 2 +-
 redis/commands/server/time.mdx                 | 2 +-
 redis/commands/set/sadd.mdx                    | 2 +-
 redis/commands/set/scard.mdx                   | 2 +-
 redis/commands/set/sdiff.mdx                   | 2 +-
 redis/commands/set/sdiffstore.mdx              | 2 +-
 redis/commands/set/sinter.mdx                  | 2 +-
 redis/commands/set/sintercard.mdx              | 2 +-
 redis/commands/set/sinterstore.mdx             | 2 +-
 redis/commands/set/sismember.mdx               | 2 +-
 redis/commands/set/smembers.mdx                | 2 +-
 redis/commands/set/smismember.mdx              | 2 +-
 redis/commands/set/smove.mdx                   | 2 +-
 redis/commands/set/spop.mdx                    | 2 +-
 redis/commands/set/srandmember.mdx             | 2 +-
 redis/commands/set/srem.mdx                    | 2 +-
 redis/commands/set/sscan.mdx                   | 2 +-
 redis/commands/set/sunion.mdx                  | 2 +-
 redis/commands/set/sunionstore.mdx             | 2 +-
 redis/commands/sorted-set/bzmpop.mdx           | 2 +-
 redis/commands/sorted-set/bzpopmax.mdx         | 2 +-
 redis/commands/sorted-set/bzpopmin.mdx         | 2 +-
 redis/commands/sorted-set/zadd.mdx             | 2 +-
 redis/commands/sorted-set/zcard.mdx            | 2 +-
 redis/commands/sorted-set/zcount.mdx           | 2 +-
 redis/commands/sorted-set/zdiff.mdx            | 2 +-
 redis/commands/sorted-set/zdiffstore.mdx       | 2 +-
 redis/commands/sorted-set/zincrby.mdx          | 2 +-
 redis/commands/sorted-set/zinter.mdx           | 2 +-
 redis/commands/sorted-set/zintercard.mdx       | 2 +-
 redis/commands/sorted-set/zinterstore.mdx      | 2 +-
 redis/commands/sorted-set/zlexcount.mdx        | 2 +-
 redis/commands/sorted-set/zmpop.mdx            | 2 +-
 redis/commands/sorted-set/zmscore.mdx          | 2 +-
 redis/commands/sorted-set/zpopmax.mdx          | 2 +-
 redis/commands/sorted-set/zpopmin.mdx          | 2 +-
 redis/commands/sorted-set/zrandmember.mdx      | 2 +-
 redis/commands/sorted-set/zrange.mdx           | 2 +-
 redis/commands/sorted-set/zrangebylex.mdx      | 2 +-
 redis/commands/sorted-set/zrangebyscore.mdx    | 2 +-
 redis/commands/sorted-set/zrangestore.mdx      | 2 +-
 redis/commands/sorted-set/zrank.mdx            | 2 +-
 redis/commands/sorted-set/zrem.mdx             | 2 +-
 redis/commands/sorted-set/zremrangebylex.mdx   | 2 +-
 redis/commands/sorted-set/zremrangebyrank.mdx  | 2 +-
 redis/commands/sorted-set/zremrangebyscore.mdx | 2 +-
 redis/commands/sorted-set/zrevrange.mdx        | 2 +-
 redis/commands/sorted-set/zrevrangebylex.mdx   | 2 +-
 redis/commands/sorted-set/zrevrangebyscore.mdx | 2 +-
 redis/commands/sorted-set/zrevrank.mdx         | 2 +-
 redis/commands/sorted-set/zscan.mdx            | 2 +-
 redis/commands/sorted-set/zscore.mdx           | 2 +-
 redis/commands/sorted-set/zunion.mdx           | 2 +-
 redis/commands/sorted-set/zunionstore.mdx      | 2 +-
 redis/commands/streams/xack.mdx                | 2 +-
 redis/commands/streams/xackdel.mdx             | 2 +-
 redis/commands/streams/xadd.mdx                | 2 +-
 redis/commands/streams/xautoclaim.mdx          | 2 +-
 redis/commands/streams/xclaim.mdx              | 2 +-
 redis/commands/streams/xdel.mdx                | 2 +-
 redis/commands/streams/xdelex.mdx              | 2 +-
 redis/commands/streams/xgroup.mdx              | 2 +-
 redis/commands/streams/xinfo-consumers.mdx     | 2 +-
 redis/commands/streams/xinfo-groups.mdx        | 2 +-
 redis/commands/streams/xinfo-stream.mdx        | 2 +-
 redis/commands/streams/xlen.mdx                | 2 +-
 redis/commands/streams/xpending.mdx            | 2 +-
 redis/commands/streams/xrange.mdx              | 2 +-
 redis/commands/streams/xread.mdx               | 2 +-
 redis/commands/streams/xreadgroup.mdx          | 2 +-
 redis/commands/streams/xrevrange.mdx           | 2 +-
 redis/commands/streams/xtrim.mdx               | 2 +-
 redis/commands/string/append.mdx               | 2 +-
 redis/commands/string/decr.mdx                 | 2 +-
 redis/commands/string/decrby.mdx               | 2 +-
 redis/commands/string/delex.mdx                | 2 +-
 redis/commands/string/digest.mdx               | 2 +-
 redis/commands/string/get.mdx                  | 2 +-
 redis/commands/string/getdel.mdx               | 2 +-
 redis/commands/string/getex.mdx                | 2 +-
 redis/commands/string/getrange.mdx             | 2 +-
 redis/commands/string/getset.mdx               | 2 +-
 redis/commands/string/incr.mdx                 | 2 +-
 redis/commands/string/incrby.mdx               | 2 +-
 redis/commands/string/incrbyfloat.mdx          | 2 +-
 redis/commands/string/mget.mdx                 | 2 +-
 redis/commands/string/mset.mdx                 | 2 +-
 redis/commands/string/msetnx.mdx               | 2 +-
 redis/commands/string/psetex.mdx               | 2 +-
 redis/commands/string/set.mdx                  | 2 +-
 redis/commands/string/setex.mdx                | 2 +-
 redis/commands/string/setnx.mdx                | 2 +-
 redis/commands/string/setrange.mdx             | 2 +-
 redis/commands/string/strlen.mdx               | 2 +-
 redis/commands/transactions/discard.mdx        | 2 +-
 redis/commands/transactions/exec.mdx           | 2 +-
 redis/commands/transactions/multi.mdx          | 2 +-
 redis/commands/transactions/unwatch.mdx        | 2 +-
 redis/commands/transactions/watch.mdx          | 2 +-
 273 files changed, 273 insertions(+), 273 deletions(-)

diff --git a/redis/commands/bitmap/bitcount.mdx b/redis/commands/bitmap/bitcount.mdx
index 5e15a76cf..a636dd341 100644
--- a/redis/commands/bitmap/bitcount.mdx
+++ b/redis/commands/bitmap/bitcount.mdx
@@ -41,7 +41,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 BITCOUNT my-key
diff --git a/redis/commands/bitmap/bitfield-ro.mdx b/redis/commands/bitmap/bitfield-ro.mdx
index db72fb150..0aacd9b65 100644
--- a/redis/commands/bitmap/bitfield-ro.mdx
+++ b/redis/commands/bitmap/bitfield-ro.mdx
@@ -39,7 +39,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 BITFIELD_RO my-key GET u8 0
diff --git a/redis/commands/bitmap/bitfield.mdx b/redis/commands/bitmap/bitfield.mdx
index 0420236b6..0e80fa96b 100644
--- a/redis/commands/bitmap/bitfield.mdx
+++ b/redis/commands/bitmap/bitfield.mdx
@@ -52,7 +52,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 BITFIELD my-key GET u8 0
diff --git a/redis/commands/bitmap/bitop.mdx b/redis/commands/bitmap/bitop.mdx
index 11868326c..e0dd1566e 100644
--- a/redis/commands/bitmap/bitop.mdx
+++ b/redis/commands/bitmap/bitop.mdx
@@ -44,7 +44,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 BITOP AND destination-key source-key-1 source-key-2
diff --git a/redis/commands/bitmap/bitpos.mdx b/redis/commands/bitmap/bitpos.mdx
index afa0fe76d..1403ea683 100644
--- a/redis/commands/bitmap/bitpos.mdx
+++ b/redis/commands/bitmap/bitpos.mdx
@@ -42,7 +42,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 BITPOS my-key 1
diff --git a/redis/commands/bitmap/getbit.mdx b/redis/commands/bitmap/getbit.mdx
index 16ada3381..84b93cd06 100644
--- a/redis/commands/bitmap/getbit.mdx
+++ b/redis/commands/bitmap/getbit.mdx
@@ -39,7 +39,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 GETBIT my-key 0
diff --git a/redis/commands/bitmap/setbit.mdx b/redis/commands/bitmap/setbit.mdx
index b3b546987..fa3037020 100644
--- a/redis/commands/bitmap/setbit.mdx
+++ b/redis/commands/bitmap/setbit.mdx
@@ -42,7 +42,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 SETBIT my-key 0 1
diff --git a/redis/commands/connection/auth.mdx b/redis/commands/connection/auth.mdx
index cc2d683c4..ab3f3b2c1 100644
--- a/redis/commands/connection/auth.mdx
+++ b/redis/commands/connection/auth.mdx
@@ -43,7 +43,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 AUTH password
diff --git a/redis/commands/connection/client-getname.mdx b/redis/commands/connection/client-getname.mdx
index bebd9289a..d67a15804 100644
--- a/redis/commands/connection/client-getname.mdx
+++ b/redis/commands/connection/client-getname.mdx
@@ -41,7 +41,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 CLIENT GETNAME
diff --git a/redis/commands/connection/client-id.mdx b/redis/commands/connection/client-id.mdx
index ecaa099c3..54a760355 100644
--- a/redis/commands/connection/client-id.mdx
+++ b/redis/commands/connection/client-id.mdx
@@ -41,7 +41,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 CLIENT ID
diff --git a/redis/commands/connection/client-info.mdx b/redis/commands/connection/client-info.mdx
index ed6200823..4c5aa9746 100644
--- a/redis/commands/connection/client-info.mdx
+++ b/redis/commands/connection/client-info.mdx
@@ -41,7 +41,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 CLIENT INFO
diff --git a/redis/commands/connection/client-list.mdx b/redis/commands/connection/client-list.mdx
index ee051f3d2..c032815d5 100644
--- a/redis/commands/connection/client-list.mdx
+++ b/redis/commands/connection/client-list.mdx
@@ -41,7 +41,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 CLIENT LIST
diff --git a/redis/commands/connection/client-setinfo.mdx b/redis/commands/connection/client-setinfo.mdx
index 00bb6adb1..1e1297181 100644
--- a/redis/commands/connection/client-setinfo.mdx
+++ b/redis/commands/connection/client-setinfo.mdx
@@ -44,7 +44,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 CLIENT SETINFO LIB-NAME my-client
diff --git a/redis/commands/connection/client-setname.mdx b/redis/commands/connection/client-setname.mdx
index 0656e902b..352ae8e1a 100644
--- a/redis/commands/connection/client-setname.mdx
+++ b/redis/commands/connection/client-setname.mdx
@@ -43,7 +43,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 CLIENT SETNAME worker-1
diff --git a/redis/commands/connection/echo.mdx b/redis/commands/connection/echo.mdx
index ca0522a52..db83d1b36 100644
--- a/redis/commands/connection/echo.mdx
+++ b/redis/commands/connection/echo.mdx
@@ -38,7 +38,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 ECHO hello
diff --git a/redis/commands/connection/hello.mdx b/redis/commands/connection/hello.mdx
index 25afc32ad..65b7257eb 100644
--- a/redis/commands/connection/hello.mdx
+++ b/redis/commands/connection/hello.mdx
@@ -47,7 +47,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 HELLO
diff --git a/redis/commands/connection/ping.mdx b/redis/commands/connection/ping.mdx
index ff7cf021d..6fa03a0dc 100644
--- a/redis/commands/connection/ping.mdx
+++ b/redis/commands/connection/ping.mdx
@@ -43,7 +43,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 PING
diff --git a/redis/commands/connection/quit.mdx b/redis/commands/connection/quit.mdx
index a9c5cf485..be39c973f 100644
--- a/redis/commands/connection/quit.mdx
+++ b/redis/commands/connection/quit.mdx
@@ -44,7 +44,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 QUIT
diff --git a/redis/commands/connection/reset.mdx b/redis/commands/connection/reset.mdx
index 6732dce85..abbe1a948 100644
--- a/redis/commands/connection/reset.mdx
+++ b/redis/commands/connection/reset.mdx
@@ -40,7 +40,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 RESET
diff --git a/redis/commands/connection/select.mdx b/redis/commands/connection/select.mdx
index da62118af..f4b6f34be 100644
--- a/redis/commands/connection/select.mdx
+++ b/redis/commands/connection/select.mdx
@@ -42,7 +42,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 SELECT 0
diff --git a/redis/commands/functions/fcall-ro.mdx b/redis/commands/functions/fcall-ro.mdx
index 01555d292..54bf39839 100644
--- a/redis/commands/functions/fcall-ro.mdx
+++ b/redis/commands/functions/fcall-ro.mdx
@@ -51,7 +51,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 FCALL_RO my_function 1 my-key value
diff --git a/redis/commands/functions/fcall.mdx b/redis/commands/functions/fcall.mdx
index 49f0a5ba6..d8525cc6f 100644
--- a/redis/commands/functions/fcall.mdx
+++ b/redis/commands/functions/fcall.mdx
@@ -71,7 +71,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 FCALL my_function 1 my-key value
diff --git a/redis/commands/functions/function-delete.mdx b/redis/commands/functions/function-delete.mdx
index 800719e59..b4d8401ca 100644
--- a/redis/commands/functions/function-delete.mdx
+++ b/redis/commands/functions/function-delete.mdx
@@ -38,7 +38,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 FUNCTION DELETE mylib
diff --git a/redis/commands/functions/function-flush.mdx b/redis/commands/functions/function-flush.mdx
index 5c49b8ebb..b456bc9ad 100644
--- a/redis/commands/functions/function-flush.mdx
+++ b/redis/commands/functions/function-flush.mdx
@@ -38,7 +38,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 FUNCTION FLUSH
diff --git a/redis/commands/functions/function-kill.mdx b/redis/commands/functions/function-kill.mdx
index 7c5d8d4b4..f32e902be 100644
--- a/redis/commands/functions/function-kill.mdx
+++ b/redis/commands/functions/function-kill.mdx
@@ -42,7 +42,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 FUNCTION KILL
diff --git a/redis/commands/functions/function-list.mdx b/redis/commands/functions/function-list.mdx
index 40857d64f..142e87314 100644
--- a/redis/commands/functions/function-list.mdx
+++ b/redis/commands/functions/function-list.mdx
@@ -39,7 +39,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 FUNCTION LIST
diff --git a/redis/commands/functions/function-load.mdx b/redis/commands/functions/function-load.mdx
index 31c0b9d67..e2642a1a8 100644
--- a/redis/commands/functions/function-load.mdx
+++ b/redis/commands/functions/function-load.mdx
@@ -45,7 +45,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 FUNCTION LOAD "#!lua name=mylib\nredis.register_function('helloworld', function() return 'Hello World!' end)"
diff --git a/redis/commands/functions/function-stats.mdx b/redis/commands/functions/function-stats.mdx
index d0731a88b..275771627 100644
--- a/redis/commands/functions/function-stats.mdx
+++ b/redis/commands/functions/function-stats.mdx
@@ -36,7 +36,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 FUNCTION STATS
diff --git a/redis/commands/generic/copy.mdx b/redis/commands/generic/copy.mdx
index f4e20d6a6..188a31fbd 100644
--- a/redis/commands/generic/copy.mdx
+++ b/redis/commands/generic/copy.mdx
@@ -43,7 +43,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 COPY source-key destination-key
diff --git a/redis/commands/generic/del.mdx b/redis/commands/generic/del.mdx
index 5c338d3f1..dff0d3c5d 100644
--- a/redis/commands/generic/del.mdx
+++ b/redis/commands/generic/del.mdx
@@ -38,7 +38,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 DEL my-key
diff --git a/redis/commands/generic/dump.mdx b/redis/commands/generic/dump.mdx
index 27bef930e..ebe5d7d5e 100644
--- a/redis/commands/generic/dump.mdx
+++ b/redis/commands/generic/dump.mdx
@@ -40,7 +40,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 DUMP my-key
diff --git a/redis/commands/generic/exists.mdx b/redis/commands/generic/exists.mdx
index dc2a1493b..f06e00b52 100644
--- a/redis/commands/generic/exists.mdx
+++ b/redis/commands/generic/exists.mdx
@@ -38,7 +38,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 EXISTS my-key
diff --git a/redis/commands/generic/expire.mdx b/redis/commands/generic/expire.mdx
index 099773dfb..c417a6a88 100644
--- a/redis/commands/generic/expire.mdx
+++ b/redis/commands/generic/expire.mdx
@@ -49,7 +49,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 EXPIRE my-key 1000
diff --git a/redis/commands/generic/expireat.mdx b/redis/commands/generic/expireat.mdx
index 04902071f..73bb5bae6 100644
--- a/redis/commands/generic/expireat.mdx
+++ b/redis/commands/generic/expireat.mdx
@@ -47,7 +47,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 EXPIREAT my-key 1735689600
diff --git a/redis/commands/generic/expiretime.mdx b/redis/commands/generic/expiretime.mdx
index 4ea72cc38..68ab28b7c 100644
--- a/redis/commands/generic/expiretime.mdx
+++ b/redis/commands/generic/expiretime.mdx
@@ -42,7 +42,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 EXPIRETIME my-key
diff --git a/redis/commands/generic/keys.mdx b/redis/commands/generic/keys.mdx
index 095a76e22..24eecf90d 100644
--- a/redis/commands/generic/keys.mdx
+++ b/redis/commands/generic/keys.mdx
@@ -45,7 +45,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 KEYS *
diff --git a/redis/commands/generic/memory-usage.mdx b/redis/commands/generic/memory-usage.mdx
index bfe254cd5..267e736e9 100644
--- a/redis/commands/generic/memory-usage.mdx
+++ b/redis/commands/generic/memory-usage.mdx
@@ -46,7 +46,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 MEMORY USAGE my-key SAMPLES 10
diff --git a/redis/commands/generic/persist.mdx b/redis/commands/generic/persist.mdx
index cd5820dfe..6c78fc14d 100644
--- a/redis/commands/generic/persist.mdx
+++ b/redis/commands/generic/persist.mdx
@@ -38,7 +38,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 PERSIST my-key
diff --git a/redis/commands/generic/pexpire.mdx b/redis/commands/generic/pexpire.mdx
index 3b85ee6bc..6da8fa9bf 100644
--- a/redis/commands/generic/pexpire.mdx
+++ b/redis/commands/generic/pexpire.mdx
@@ -47,7 +47,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 PEXPIRE my-key 1000
diff --git a/redis/commands/generic/pexpireat.mdx b/redis/commands/generic/pexpireat.mdx
index ae4b8be22..5d3120106 100644
--- a/redis/commands/generic/pexpireat.mdx
+++ b/redis/commands/generic/pexpireat.mdx
@@ -47,7 +47,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 PEXPIREAT my-key 1735689600
diff --git a/redis/commands/generic/pexpiretime.mdx b/redis/commands/generic/pexpiretime.mdx
index 56f3716c9..61ea67125 100644
--- a/redis/commands/generic/pexpiretime.mdx
+++ b/redis/commands/generic/pexpiretime.mdx
@@ -42,7 +42,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 PEXPIRETIME my-key
diff --git a/redis/commands/generic/pttl.mdx b/redis/commands/generic/pttl.mdx
index 4e08362f2..af03f146d 100644
--- a/redis/commands/generic/pttl.mdx
+++ b/redis/commands/generic/pttl.mdx
@@ -42,7 +42,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 PTTL my-key
diff --git a/redis/commands/generic/randomkey.mdx b/redis/commands/generic/randomkey.mdx
index aa0741ff1..c32daa890 100644
--- a/redis/commands/generic/randomkey.mdx
+++ b/redis/commands/generic/randomkey.mdx
@@ -36,7 +36,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 RANDOMKEY
diff --git a/redis/commands/generic/rename.mdx b/redis/commands/generic/rename.mdx
index 1140d5f0b..d0e277810 100644
--- a/redis/commands/generic/rename.mdx
+++ b/redis/commands/generic/rename.mdx
@@ -41,7 +41,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 RENAME old-key new-key
diff --git a/redis/commands/generic/renamenx.mdx b/redis/commands/generic/renamenx.mdx
index 21c5be7f3..374a30c63 100644
--- a/redis/commands/generic/renamenx.mdx
+++ b/redis/commands/generic/renamenx.mdx
@@ -39,7 +39,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 RENAMENX old-key new-key
diff --git a/redis/commands/generic/restore.mdx b/redis/commands/generic/restore.mdx
index 3e4c50b28..3fc5d04d8 100644
--- a/redis/commands/generic/restore.mdx
+++ b/redis/commands/generic/restore.mdx
@@ -54,7 +54,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 RESTORE my-key 1 serialized-value
diff --git a/redis/commands/generic/scan.mdx b/redis/commands/generic/scan.mdx
index ba329d740..c73add37c 100644
--- a/redis/commands/generic/scan.mdx
+++ b/redis/commands/generic/scan.mdx
@@ -50,7 +50,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 SCAN 0
diff --git a/redis/commands/generic/touch.mdx b/redis/commands/generic/touch.mdx
index b0ece6034..368df6633 100644
--- a/redis/commands/generic/touch.mdx
+++ b/redis/commands/generic/touch.mdx
@@ -38,7 +38,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 TOUCH my-key
diff --git a/redis/commands/generic/ttl.mdx b/redis/commands/generic/ttl.mdx
index e4473e62f..f85462121 100644
--- a/redis/commands/generic/ttl.mdx
+++ b/redis/commands/generic/ttl.mdx
@@ -42,7 +42,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 TTL my-key
diff --git a/redis/commands/generic/type.mdx b/redis/commands/generic/type.mdx
index 1aa942da1..dd4d10a1f 100644
--- a/redis/commands/generic/type.mdx
+++ b/redis/commands/generic/type.mdx
@@ -38,7 +38,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 TYPE my-key
diff --git a/redis/commands/generic/unlink.mdx b/redis/commands/generic/unlink.mdx
index e1b3073e8..a35e1c5d3 100644
--- a/redis/commands/generic/unlink.mdx
+++ b/redis/commands/generic/unlink.mdx
@@ -38,7 +38,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 UNLINK my-key
diff --git a/redis/commands/generic/wait.mdx b/redis/commands/generic/wait.mdx
index c4026bab8..23ed588a2 100644
--- a/redis/commands/generic/wait.mdx
+++ b/redis/commands/generic/wait.mdx
@@ -48,7 +48,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 WAIT 1 1000
diff --git a/redis/commands/generic/waitaof.mdx b/redis/commands/generic/waitaof.mdx
index c37338493..f4fb6c02b 100644
--- a/redis/commands/generic/waitaof.mdx
+++ b/redis/commands/generic/waitaof.mdx
@@ -47,7 +47,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 WAITAOF 1 1 1000
diff --git a/redis/commands/geo/geoadd.mdx b/redis/commands/geo/geoadd.mdx
index 4bec704be..4fd5438b6 100644
--- a/redis/commands/geo/geoadd.mdx
+++ b/redis/commands/geo/geoadd.mdx
@@ -51,7 +51,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 GEOADD my-key 29.0 41.0 member
diff --git a/redis/commands/geo/geodist.mdx b/redis/commands/geo/geodist.mdx
index aceaa49fc..d76bff46c 100644
--- a/redis/commands/geo/geodist.mdx
+++ b/redis/commands/geo/geodist.mdx
@@ -45,7 +45,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 GEODIST my-key member1 member2
diff --git a/redis/commands/geo/geohash.mdx b/redis/commands/geo/geohash.mdx
index f7363fad6..305e37231 100644
--- a/redis/commands/geo/geohash.mdx
+++ b/redis/commands/geo/geohash.mdx
@@ -39,7 +39,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 GEOHASH my-key member
diff --git a/redis/commands/geo/geopos.mdx b/redis/commands/geo/geopos.mdx
index 9e9ff6fd2..bc657a09d 100644
--- a/redis/commands/geo/geopos.mdx
+++ b/redis/commands/geo/geopos.mdx
@@ -39,7 +39,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 GEOPOS my-key member
diff --git a/redis/commands/geo/georadius-ro.mdx b/redis/commands/geo/georadius-ro.mdx
index 1d1bd9d38..268376045 100644
--- a/redis/commands/geo/georadius-ro.mdx
+++ b/redis/commands/geo/georadius-ro.mdx
@@ -58,7 +58,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 GEORADIUS_RO my-key 29.0 41.0 1.5 m
diff --git a/redis/commands/geo/georadius.mdx b/redis/commands/geo/georadius.mdx
index 4d859c485..054ed78bd 100644
--- a/redis/commands/geo/georadius.mdx
+++ b/redis/commands/geo/georadius.mdx
@@ -62,7 +62,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 GEORADIUS my-key 29.0 41.0 1.5 m
diff --git a/redis/commands/geo/georadiusbymember-ro.mdx b/redis/commands/geo/georadiusbymember-ro.mdx
index 3e9344048..ca4e0e7e1 100644
--- a/redis/commands/geo/georadiusbymember-ro.mdx
+++ b/redis/commands/geo/georadiusbymember-ro.mdx
@@ -55,7 +55,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 GEORADIUSBYMEMBER_RO my-key member 1.5 m
diff --git a/redis/commands/geo/georadiusbymember.mdx b/redis/commands/geo/georadiusbymember.mdx
index feeebbf71..0017c641b 100644
--- a/redis/commands/geo/georadiusbymember.mdx
+++ b/redis/commands/geo/georadiusbymember.mdx
@@ -59,7 +59,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 GEORADIUSBYMEMBER my-key member 1.5 m
diff --git a/redis/commands/geo/geosearch.mdx b/redis/commands/geo/geosearch.mdx
index 1678c7447..0f9eaf1ad 100644
--- a/redis/commands/geo/geosearch.mdx
+++ b/redis/commands/geo/geosearch.mdx
@@ -57,7 +57,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 GEOSEARCH my-key FROMMEMBER member BYRADIUS 1.5 m
diff --git a/redis/commands/geo/geosearchstore.mdx b/redis/commands/geo/geosearchstore.mdx
index 5f1c834e9..1c841ec17 100644
--- a/redis/commands/geo/geosearchstore.mdx
+++ b/redis/commands/geo/geosearchstore.mdx
@@ -52,7 +52,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 GEOSEARCHSTORE destination-key source-key FROMMEMBER member BYRADIUS 1.5 m
diff --git a/redis/commands/hash/hdel.mdx b/redis/commands/hash/hdel.mdx
index ffcb2245d..b9e68e7a7 100644
--- a/redis/commands/hash/hdel.mdx
+++ b/redis/commands/hash/hdel.mdx
@@ -39,7 +39,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 HDEL my-key field
diff --git a/redis/commands/hash/hexists.mdx b/redis/commands/hash/hexists.mdx
index 26bb63f05..07e75830f 100644
--- a/redis/commands/hash/hexists.mdx
+++ b/redis/commands/hash/hexists.mdx
@@ -39,7 +39,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 HEXISTS my-key field
diff --git a/redis/commands/hash/hexpire.mdx b/redis/commands/hash/hexpire.mdx
index bd76d9bd3..46f961f6e 100644
--- a/redis/commands/hash/hexpire.mdx
+++ b/redis/commands/hash/hexpire.mdx
@@ -52,7 +52,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 HEXPIRE my-key 1000 FIELDS 1 field
diff --git a/redis/commands/hash/hexpireat.mdx b/redis/commands/hash/hexpireat.mdx
index 0edd76c39..375a66ed7 100644
--- a/redis/commands/hash/hexpireat.mdx
+++ b/redis/commands/hash/hexpireat.mdx
@@ -52,7 +52,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 HEXPIREAT my-key 1735689600 FIELDS 1 field
diff --git a/redis/commands/hash/hexpiretime.mdx b/redis/commands/hash/hexpiretime.mdx
index 24d0d8ef2..b56468cc7 100644
--- a/redis/commands/hash/hexpiretime.mdx
+++ b/redis/commands/hash/hexpiretime.mdx
@@ -43,7 +43,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 HEXPIRETIME my-key FIELDS 1 field
diff --git a/redis/commands/hash/hget.mdx b/redis/commands/hash/hget.mdx
index 5a09063a3..0b139b3bd 100644
--- a/redis/commands/hash/hget.mdx
+++ b/redis/commands/hash/hget.mdx
@@ -39,7 +39,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 HGET my-key field
diff --git a/redis/commands/hash/hgetall.mdx b/redis/commands/hash/hgetall.mdx
index 61f481e27..d0ffd76d9 100644
--- a/redis/commands/hash/hgetall.mdx
+++ b/redis/commands/hash/hgetall.mdx
@@ -44,7 +44,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 HGETALL my-key
diff --git a/redis/commands/hash/hgetdel.mdx b/redis/commands/hash/hgetdel.mdx
index 3ca63173a..a2cff3b21 100644
--- a/redis/commands/hash/hgetdel.mdx
+++ b/redis/commands/hash/hgetdel.mdx
@@ -41,7 +41,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 HGETDEL my-key FIELDS 1 field
diff --git a/redis/commands/hash/hgetex.mdx b/redis/commands/hash/hgetex.mdx
index 55fd52126..341f2d2a1 100644
--- a/redis/commands/hash/hgetex.mdx
+++ b/redis/commands/hash/hgetex.mdx
@@ -45,7 +45,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 HGETEX my-key FIELDS 1 field
diff --git a/redis/commands/hash/hincrby.mdx b/redis/commands/hash/hincrby.mdx
index 6d8776639..31cb90cc9 100644
--- a/redis/commands/hash/hincrby.mdx
+++ b/redis/commands/hash/hincrby.mdx
@@ -42,7 +42,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 HINCRBY my-key field 1
diff --git a/redis/commands/hash/hincrbyfloat.mdx b/redis/commands/hash/hincrbyfloat.mdx
index 7f409f7ac..a7b90fa9d 100644
--- a/redis/commands/hash/hincrbyfloat.mdx
+++ b/redis/commands/hash/hincrbyfloat.mdx
@@ -46,7 +46,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 HINCRBYFLOAT my-key field 1.5
diff --git a/redis/commands/hash/hkeys.mdx b/redis/commands/hash/hkeys.mdx
index 9ae11406b..c46fb5363 100644
--- a/redis/commands/hash/hkeys.mdx
+++ b/redis/commands/hash/hkeys.mdx
@@ -38,7 +38,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 HKEYS my-key
diff --git a/redis/commands/hash/hlen.mdx b/redis/commands/hash/hlen.mdx
index 97c43ef92..a2f55846f 100644
--- a/redis/commands/hash/hlen.mdx
+++ b/redis/commands/hash/hlen.mdx
@@ -38,7 +38,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 HLEN my-key
diff --git a/redis/commands/hash/hmget.mdx b/redis/commands/hash/hmget.mdx
index 3f0928471..dc0ba29c2 100644
--- a/redis/commands/hash/hmget.mdx
+++ b/redis/commands/hash/hmget.mdx
@@ -41,7 +41,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 HMGET my-key field
diff --git a/redis/commands/hash/hmset.mdx b/redis/commands/hash/hmset.mdx
index 29f403541..706130aed 100644
--- a/redis/commands/hash/hmset.mdx
+++ b/redis/commands/hash/hmset.mdx
@@ -43,7 +43,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 HMSET my-key field value
diff --git a/redis/commands/hash/hpersist.mdx b/redis/commands/hash/hpersist.mdx
index b1a2994f7..504eb1ba3 100644
--- a/redis/commands/hash/hpersist.mdx
+++ b/redis/commands/hash/hpersist.mdx
@@ -41,7 +41,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 HPERSIST my-key FIELDS 1 field
diff --git a/redis/commands/hash/hpexpire.mdx b/redis/commands/hash/hpexpire.mdx
index adf26c14e..60d3a0c53 100644
--- a/redis/commands/hash/hpexpire.mdx
+++ b/redis/commands/hash/hpexpire.mdx
@@ -50,7 +50,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 HPEXPIRE my-key 1000 FIELDS 1 field
diff --git a/redis/commands/hash/hpexpireat.mdx b/redis/commands/hash/hpexpireat.mdx
index 8705ef3cb..5d1568911 100644
--- a/redis/commands/hash/hpexpireat.mdx
+++ b/redis/commands/hash/hpexpireat.mdx
@@ -50,7 +50,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 HPEXPIREAT my-key 1735689600 FIELDS 1 field
diff --git a/redis/commands/hash/hpexpiretime.mdx b/redis/commands/hash/hpexpiretime.mdx
index 20ba0aeec..f59475ec1 100644
--- a/redis/commands/hash/hpexpiretime.mdx
+++ b/redis/commands/hash/hpexpiretime.mdx
@@ -43,7 +43,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 HPEXPIRETIME my-key FIELDS 1 field
diff --git a/redis/commands/hash/hpttl.mdx b/redis/commands/hash/hpttl.mdx
index 6e59fe28b..f698610e5 100644
--- a/redis/commands/hash/hpttl.mdx
+++ b/redis/commands/hash/hpttl.mdx
@@ -43,7 +43,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 HPTTL my-key FIELDS 1 field
diff --git a/redis/commands/hash/hrandfield.mdx b/redis/commands/hash/hrandfield.mdx
index 09b913c8d..8fd32cba9 100644
--- a/redis/commands/hash/hrandfield.mdx
+++ b/redis/commands/hash/hrandfield.mdx
@@ -45,7 +45,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 HRANDFIELD my-key
diff --git a/redis/commands/hash/hscan.mdx b/redis/commands/hash/hscan.mdx
index d309dae11..1d0d2737f 100644
--- a/redis/commands/hash/hscan.mdx
+++ b/redis/commands/hash/hscan.mdx
@@ -49,7 +49,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 HSCAN my-key 0
diff --git a/redis/commands/hash/hset.mdx b/redis/commands/hash/hset.mdx
index 8232c4bd9..bbae755cb 100644
--- a/redis/commands/hash/hset.mdx
+++ b/redis/commands/hash/hset.mdx
@@ -41,7 +41,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 HSET my-key field value
diff --git a/redis/commands/hash/hsetex.mdx b/redis/commands/hash/hsetex.mdx
index e8ee4cdad..46cd127d8 100644
--- a/redis/commands/hash/hsetex.mdx
+++ b/redis/commands/hash/hsetex.mdx
@@ -47,7 +47,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 HSETEX my-key FIELDS 1 field value
diff --git a/redis/commands/hash/hsetnx.mdx b/redis/commands/hash/hsetnx.mdx
index f670b6bf6..82bdc9abe 100644
--- a/redis/commands/hash/hsetnx.mdx
+++ b/redis/commands/hash/hsetnx.mdx
@@ -40,7 +40,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 HSETNX my-key field value
diff --git a/redis/commands/hash/hstrlen.mdx b/redis/commands/hash/hstrlen.mdx
index 7faefe033..963806126 100644
--- a/redis/commands/hash/hstrlen.mdx
+++ b/redis/commands/hash/hstrlen.mdx
@@ -39,7 +39,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 HSTRLEN my-key field
diff --git a/redis/commands/hash/httl.mdx b/redis/commands/hash/httl.mdx
index 6c582a50f..853e60243 100644
--- a/redis/commands/hash/httl.mdx
+++ b/redis/commands/hash/httl.mdx
@@ -43,7 +43,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 HTTL my-key FIELDS 1 field
diff --git a/redis/commands/hash/hvals.mdx b/redis/commands/hash/hvals.mdx
index 4c86486e3..55d984b5e 100644
--- a/redis/commands/hash/hvals.mdx
+++ b/redis/commands/hash/hvals.mdx
@@ -38,7 +38,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 HVALS my-key
diff --git a/redis/commands/hyperloglog/pfadd.mdx b/redis/commands/hyperloglog/pfadd.mdx
index 4ad72daf5..f7803f236 100644
--- a/redis/commands/hyperloglog/pfadd.mdx
+++ b/redis/commands/hyperloglog/pfadd.mdx
@@ -41,7 +41,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 PFADD my-key element
diff --git a/redis/commands/hyperloglog/pfcount.mdx b/redis/commands/hyperloglog/pfcount.mdx
index 4530cbe63..be237f3f6 100644
--- a/redis/commands/hyperloglog/pfcount.mdx
+++ b/redis/commands/hyperloglog/pfcount.mdx
@@ -40,7 +40,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 PFCOUNT my-key
diff --git a/redis/commands/hyperloglog/pfmerge.mdx b/redis/commands/hyperloglog/pfmerge.mdx
index 1b72400ed..ae2a720da 100644
--- a/redis/commands/hyperloglog/pfmerge.mdx
+++ b/redis/commands/hyperloglog/pfmerge.mdx
@@ -41,7 +41,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 PFMERGE destination-key source-key
diff --git a/redis/commands/json/json-arrappend.mdx b/redis/commands/json/json-arrappend.mdx
index 61a62a394..85888e161 100644
--- a/redis/commands/json/json-arrappend.mdx
+++ b/redis/commands/json/json-arrappend.mdx
@@ -45,7 +45,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 JSON.ARRAPPEND profile $.tags '"new"'
diff --git a/redis/commands/json/json-arrindex.mdx b/redis/commands/json/json-arrindex.mdx
index 15a5c348f..4e6b98b8a 100644
--- a/redis/commands/json/json-arrindex.mdx
+++ b/redis/commands/json/json-arrindex.mdx
@@ -47,7 +47,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 JSON.ARRINDEX profile $.tags '"new"'
diff --git a/redis/commands/json/json-arrinsert.mdx b/redis/commands/json/json-arrinsert.mdx
index f7d85df65..2762c18da 100644
--- a/redis/commands/json/json-arrinsert.mdx
+++ b/redis/commands/json/json-arrinsert.mdx
@@ -46,7 +46,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 JSON.ARRINSERT profile $.tags 0 '"first"'
diff --git a/redis/commands/json/json-arrlen.mdx b/redis/commands/json/json-arrlen.mdx
index 7027abb97..0623d7693 100644
--- a/redis/commands/json/json-arrlen.mdx
+++ b/redis/commands/json/json-arrlen.mdx
@@ -44,7 +44,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 JSON.ARRLEN profile $.tags
diff --git a/redis/commands/json/json-arrpop.mdx b/redis/commands/json/json-arrpop.mdx
index 223455fca..7e67f826c 100644
--- a/redis/commands/json/json-arrpop.mdx
+++ b/redis/commands/json/json-arrpop.mdx
@@ -47,7 +47,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 JSON.ARRPOP profile $.tags -1
diff --git a/redis/commands/json/json-arrtrim.mdx b/redis/commands/json/json-arrtrim.mdx
index 3528e38dd..796a0a8b7 100644
--- a/redis/commands/json/json-arrtrim.mdx
+++ b/redis/commands/json/json-arrtrim.mdx
@@ -48,7 +48,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 JSON.ARRTRIM profile $.tags 0 9
diff --git a/redis/commands/json/json-clear.mdx b/redis/commands/json/json-clear.mdx
index 9bdb2ff4e..201a2dd60 100644
--- a/redis/commands/json/json-clear.mdx
+++ b/redis/commands/json/json-clear.mdx
@@ -46,7 +46,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 JSON.CLEAR profile $.stats
diff --git a/redis/commands/json/json-debug.mdx b/redis/commands/json/json-debug.mdx
index 9a8688743..ac003bcc3 100644
--- a/redis/commands/json/json-debug.mdx
+++ b/redis/commands/json/json-debug.mdx
@@ -49,7 +49,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 JSON.DEBUG MEMORY profile $.stats
diff --git a/redis/commands/json/json-del.mdx b/redis/commands/json/json-del.mdx
index 7e8170e78..9580dfe73 100644
--- a/redis/commands/json/json-del.mdx
+++ b/redis/commands/json/json-del.mdx
@@ -46,7 +46,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 JSON.DEL profile $.temporary
diff --git a/redis/commands/json/json-forget.mdx b/redis/commands/json/json-forget.mdx
index e118f0699..cb1672eee 100644
--- a/redis/commands/json/json-forget.mdx
+++ b/redis/commands/json/json-forget.mdx
@@ -44,7 +44,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 JSON.FORGET profile $.temporary
diff --git a/redis/commands/json/json-get.mdx b/redis/commands/json/json-get.mdx
index 83221c65a..eb82b2ff5 100644
--- a/redis/commands/json/json-get.mdx
+++ b/redis/commands/json/json-get.mdx
@@ -53,7 +53,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 JSON.GET profile $.name
diff --git a/redis/commands/json/json-merge.mdx b/redis/commands/json/json-merge.mdx
index 9e9874a5e..afa3757be 100644
--- a/redis/commands/json/json-merge.mdx
+++ b/redis/commands/json/json-merge.mdx
@@ -47,7 +47,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 JSON.MERGE profile $ '{"active":true}'
diff --git a/redis/commands/json/json-mget.mdx b/redis/commands/json/json-mget.mdx
index a52c41ef9..3581b032a 100644
--- a/redis/commands/json/json-mget.mdx
+++ b/redis/commands/json/json-mget.mdx
@@ -44,7 +44,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 JSON.MGET profile:1 profile:2 $.name
diff --git a/redis/commands/json/json-mset.mdx b/redis/commands/json/json-mset.mdx
index 3d413bf6f..f699c2d0f 100644
--- a/redis/commands/json/json-mset.mdx
+++ b/redis/commands/json/json-mset.mdx
@@ -43,7 +43,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 JSON.MSET profile:1 $ '{"name":"Ada"}'
diff --git a/redis/commands/json/json-numincrby.mdx b/redis/commands/json/json-numincrby.mdx
index e3fc1bfae..d9fdd888f 100644
--- a/redis/commands/json/json-numincrby.mdx
+++ b/redis/commands/json/json-numincrby.mdx
@@ -45,7 +45,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 JSON.NUMINCRBY profile $.visits 1
diff --git a/redis/commands/json/json-nummultby.mdx b/redis/commands/json/json-nummultby.mdx
index 820639737..4cfcc84cd 100644
--- a/redis/commands/json/json-nummultby.mdx
+++ b/redis/commands/json/json-nummultby.mdx
@@ -45,7 +45,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 JSON.NUMMULTBY profile $.score 2
diff --git a/redis/commands/json/json-objkeys.mdx b/redis/commands/json/json-objkeys.mdx
index 1a2cf29e3..0625ba4ed 100644
--- a/redis/commands/json/json-objkeys.mdx
+++ b/redis/commands/json/json-objkeys.mdx
@@ -44,7 +44,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 JSON.OBJKEYS profile $
diff --git a/redis/commands/json/json-objlen.mdx b/redis/commands/json/json-objlen.mdx
index d6584c004..0595b321f 100644
--- a/redis/commands/json/json-objlen.mdx
+++ b/redis/commands/json/json-objlen.mdx
@@ -44,7 +44,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 JSON.OBJLEN profile $
diff --git a/redis/commands/json/json-resp.mdx b/redis/commands/json/json-resp.mdx
index 98564c07e..233b9c03f 100644
--- a/redis/commands/json/json-resp.mdx
+++ b/redis/commands/json/json-resp.mdx
@@ -46,7 +46,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 JSON.RESP profile $
diff --git a/redis/commands/json/json-set.mdx b/redis/commands/json/json-set.mdx
index 841aff07d..8da6281cf 100644
--- a/redis/commands/json/json-set.mdx
+++ b/redis/commands/json/json-set.mdx
@@ -48,7 +48,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 JSON.SET profile $ '{"name":"Ada"}'
diff --git a/redis/commands/json/json-strappend.mdx b/redis/commands/json/json-strappend.mdx
index 0d5e34d9f..aea042353 100644
--- a/redis/commands/json/json-strappend.mdx
+++ b/redis/commands/json/json-strappend.mdx
@@ -45,7 +45,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 JSON.STRAPPEND profile $.name '" Lovelace"'
diff --git a/redis/commands/json/json-strlen.mdx b/redis/commands/json/json-strlen.mdx
index a3663f8fe..1b1d6accf 100644
--- a/redis/commands/json/json-strlen.mdx
+++ b/redis/commands/json/json-strlen.mdx
@@ -44,7 +44,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 JSON.STRLEN profile $.name
diff --git a/redis/commands/json/json-toggle.mdx b/redis/commands/json/json-toggle.mdx
index f81f8db22..d7878796d 100644
--- a/redis/commands/json/json-toggle.mdx
+++ b/redis/commands/json/json-toggle.mdx
@@ -44,7 +44,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 JSON.TOGGLE profile $.active
diff --git a/redis/commands/json/json-type.mdx b/redis/commands/json/json-type.mdx
index 1615bdeb3..6989ead12 100644
--- a/redis/commands/json/json-type.mdx
+++ b/redis/commands/json/json-type.mdx
@@ -44,7 +44,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 JSON.TYPE profile $.name
diff --git a/redis/commands/list/blmove.mdx b/redis/commands/list/blmove.mdx
index c695da2b7..f7484d571 100644
--- a/redis/commands/list/blmove.mdx
+++ b/redis/commands/list/blmove.mdx
@@ -48,7 +48,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 BLMOVE source-key destination-key LEFT LEFT 1.5
diff --git a/redis/commands/list/blmpop.mdx b/redis/commands/list/blmpop.mdx
index ef0511c21..8638dc5a7 100644
--- a/redis/commands/list/blmpop.mdx
+++ b/redis/commands/list/blmpop.mdx
@@ -48,7 +48,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 BLMPOP 1.5 1 my-key LEFT
diff --git a/redis/commands/list/blpop.mdx b/redis/commands/list/blpop.mdx
index f66b62bf9..96fe39a0d 100644
--- a/redis/commands/list/blpop.mdx
+++ b/redis/commands/list/blpop.mdx
@@ -45,7 +45,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 BLPOP my-key 1.5
diff --git a/redis/commands/list/brpop.mdx b/redis/commands/list/brpop.mdx
index 446ddb88c..5e9477761 100644
--- a/redis/commands/list/brpop.mdx
+++ b/redis/commands/list/brpop.mdx
@@ -45,7 +45,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 BRPOP my-key 1.5
diff --git a/redis/commands/list/brpoplpush.mdx b/redis/commands/list/brpoplpush.mdx
index 0fdd3a39b..f94126e46 100644
--- a/redis/commands/list/brpoplpush.mdx
+++ b/redis/commands/list/brpoplpush.mdx
@@ -50,7 +50,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 BRPOPLPUSH source-key destination-key 1.5
diff --git a/redis/commands/list/lindex.mdx b/redis/commands/list/lindex.mdx
index 1ed338efb..bb19a5078 100644
--- a/redis/commands/list/lindex.mdx
+++ b/redis/commands/list/lindex.mdx
@@ -39,7 +39,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 LINDEX my-key 0
diff --git a/redis/commands/list/linsert.mdx b/redis/commands/list/linsert.mdx
index 0160ff4fc..2b4f83ffa 100644
--- a/redis/commands/list/linsert.mdx
+++ b/redis/commands/list/linsert.mdx
@@ -43,7 +43,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 LINSERT my-key BEFORE pivot element
diff --git a/redis/commands/list/llen.mdx b/redis/commands/list/llen.mdx
index 97e284b48..365dcb4ce 100644
--- a/redis/commands/list/llen.mdx
+++ b/redis/commands/list/llen.mdx
@@ -38,7 +38,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 LLEN my-key
diff --git a/redis/commands/list/lmove.mdx b/redis/commands/list/lmove.mdx
index 6958dc82b..890f9653a 100644
--- a/redis/commands/list/lmove.mdx
+++ b/redis/commands/list/lmove.mdx
@@ -43,7 +43,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 LMOVE source-key destination-key LEFT LEFT
diff --git a/redis/commands/list/lmpop.mdx b/redis/commands/list/lmpop.mdx
index 5efa8b670..239465d68 100644
--- a/redis/commands/list/lmpop.mdx
+++ b/redis/commands/list/lmpop.mdx
@@ -43,7 +43,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 LMPOP 1 my-key LEFT
diff --git a/redis/commands/list/lpop.mdx b/redis/commands/list/lpop.mdx
index b7cc2fb64..b8eff9b11 100644
--- a/redis/commands/list/lpop.mdx
+++ b/redis/commands/list/lpop.mdx
@@ -41,7 +41,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 LPOP my-key
diff --git a/redis/commands/list/lpos.mdx b/redis/commands/list/lpos.mdx
index baae909b7..13289d25c 100644
--- a/redis/commands/list/lpos.mdx
+++ b/redis/commands/list/lpos.mdx
@@ -44,7 +44,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 LPOS my-key element
diff --git a/redis/commands/list/lpush.mdx b/redis/commands/list/lpush.mdx
index 197427b96..2a6e96810 100644
--- a/redis/commands/list/lpush.mdx
+++ b/redis/commands/list/lpush.mdx
@@ -41,7 +41,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 LPUSH my-key element
diff --git a/redis/commands/list/lpushx.mdx b/redis/commands/list/lpushx.mdx
index e8c1885c0..0a4d60909 100644
--- a/redis/commands/list/lpushx.mdx
+++ b/redis/commands/list/lpushx.mdx
@@ -39,7 +39,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 LPUSHX my-key element
diff --git a/redis/commands/list/lrange.mdx b/redis/commands/list/lrange.mdx
index 6a6f30687..2cb9772ab 100644
--- a/redis/commands/list/lrange.mdx
+++ b/redis/commands/list/lrange.mdx
@@ -42,7 +42,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 LRANGE my-key 0 0
diff --git a/redis/commands/list/lrem.mdx b/redis/commands/list/lrem.mdx
index 9bf90f2c3..02bc861aa 100644
--- a/redis/commands/list/lrem.mdx
+++ b/redis/commands/list/lrem.mdx
@@ -42,7 +42,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 LREM my-key 1 element
diff --git a/redis/commands/list/lset.mdx b/redis/commands/list/lset.mdx
index dba3b9edb..c27d6946b 100644
--- a/redis/commands/list/lset.mdx
+++ b/redis/commands/list/lset.mdx
@@ -40,7 +40,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 LSET my-key 0 element
diff --git a/redis/commands/list/ltrim.mdx b/redis/commands/list/ltrim.mdx
index f5286354c..c3201ed32 100644
--- a/redis/commands/list/ltrim.mdx
+++ b/redis/commands/list/ltrim.mdx
@@ -42,7 +42,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 LTRIM my-key 0 0
diff --git a/redis/commands/list/rpop.mdx b/redis/commands/list/rpop.mdx
index 87d7d9645..8368e7a2c 100644
--- a/redis/commands/list/rpop.mdx
+++ b/redis/commands/list/rpop.mdx
@@ -41,7 +41,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 RPOP my-key
diff --git a/redis/commands/list/rpoplpush.mdx b/redis/commands/list/rpoplpush.mdx
index 9aaba63b6..8784a22cc 100644
--- a/redis/commands/list/rpoplpush.mdx
+++ b/redis/commands/list/rpoplpush.mdx
@@ -45,7 +45,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 RPOPLPUSH source-key destination-key
diff --git a/redis/commands/list/rpush.mdx b/redis/commands/list/rpush.mdx
index 252203965..d562a2c37 100644
--- a/redis/commands/list/rpush.mdx
+++ b/redis/commands/list/rpush.mdx
@@ -41,7 +41,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 RPUSH my-key element
diff --git a/redis/commands/list/rpushx.mdx b/redis/commands/list/rpushx.mdx
index e0eaaefa6..86f258581 100644
--- a/redis/commands/list/rpushx.mdx
+++ b/redis/commands/list/rpushx.mdx
@@ -39,7 +39,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 RPUSHX my-key element
diff --git a/redis/commands/pub-sub/psubscribe.mdx b/redis/commands/pub-sub/psubscribe.mdx
index 670aa4bb9..3278a6fc6 100644
--- a/redis/commands/pub-sub/psubscribe.mdx
+++ b/redis/commands/pub-sub/psubscribe.mdx
@@ -45,7 +45,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 PSUBSCRIBE events:*
diff --git a/redis/commands/pub-sub/publish.mdx b/redis/commands/pub-sub/publish.mdx
index 6e3baf1e1..6bbe706c6 100644
--- a/redis/commands/pub-sub/publish.mdx
+++ b/redis/commands/pub-sub/publish.mdx
@@ -41,7 +41,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 PUBLISH events hello
diff --git a/redis/commands/pub-sub/pubsub.mdx b/redis/commands/pub-sub/pubsub.mdx
index bae84a00d..02fecefce 100644
--- a/redis/commands/pub-sub/pubsub.mdx
+++ b/redis/commands/pub-sub/pubsub.mdx
@@ -44,7 +44,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 PUBSUB CHANNELS events:*
diff --git a/redis/commands/pub-sub/punsubscribe.mdx b/redis/commands/pub-sub/punsubscribe.mdx
index 3d85f4e88..3e36c5d6a 100644
--- a/redis/commands/pub-sub/punsubscribe.mdx
+++ b/redis/commands/pub-sub/punsubscribe.mdx
@@ -45,7 +45,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 PUNSUBSCRIBE events:*
diff --git a/redis/commands/pub-sub/subscribe.mdx b/redis/commands/pub-sub/subscribe.mdx
index 38ecd7b62..aa4e95908 100644
--- a/redis/commands/pub-sub/subscribe.mdx
+++ b/redis/commands/pub-sub/subscribe.mdx
@@ -45,7 +45,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 SUBSCRIBE events
diff --git a/redis/commands/pub-sub/unsubscribe.mdx b/redis/commands/pub-sub/unsubscribe.mdx
index 311cdd048..781f78e98 100644
--- a/redis/commands/pub-sub/unsubscribe.mdx
+++ b/redis/commands/pub-sub/unsubscribe.mdx
@@ -45,7 +45,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 UNSUBSCRIBE events
diff --git a/redis/commands/scripting/eval-ro.mdx b/redis/commands/scripting/eval-ro.mdx
index acc5c1730..540ef0bda 100644
--- a/redis/commands/scripting/eval-ro.mdx
+++ b/redis/commands/scripting/eval-ro.mdx
@@ -49,7 +49,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 EVAL_RO "return ARGV[1]" 0 hello
diff --git a/redis/commands/scripting/eval.mdx b/redis/commands/scripting/eval.mdx
index 2472ae03f..508ab510f 100644
--- a/redis/commands/scripting/eval.mdx
+++ b/redis/commands/scripting/eval.mdx
@@ -73,7 +73,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 EVAL "return ARGV[1]" 0 hello
diff --git a/redis/commands/scripting/evalsha-ro.mdx b/redis/commands/scripting/evalsha-ro.mdx
index d98557b03..d3e7a72ef 100644
--- a/redis/commands/scripting/evalsha-ro.mdx
+++ b/redis/commands/scripting/evalsha-ro.mdx
@@ -49,7 +49,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 EVALSHA_RO fb67a0c03b48ddbf8b4c9b011e779563bdbc28cb 0 value
diff --git a/redis/commands/scripting/evalsha.mdx b/redis/commands/scripting/evalsha.mdx
index 4a1ccad31..c07c8e417 100644
--- a/redis/commands/scripting/evalsha.mdx
+++ b/redis/commands/scripting/evalsha.mdx
@@ -52,7 +52,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 EVALSHA fb67a0c03b48ddbf8b4c9b011e779563bdbc28cb 0 value
diff --git a/redis/commands/scripting/script-exists.mdx b/redis/commands/scripting/script-exists.mdx
index eaa075433..e56764e61 100644
--- a/redis/commands/scripting/script-exists.mdx
+++ b/redis/commands/scripting/script-exists.mdx
@@ -38,7 +38,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 SCRIPT EXISTS fb67a0c03b48ddbf8b4c9b011e779563bdbc28cb
diff --git a/redis/commands/scripting/script-flush.mdx b/redis/commands/scripting/script-flush.mdx
index 773f77af5..7c6bb9423 100644
--- a/redis/commands/scripting/script-flush.mdx
+++ b/redis/commands/scripting/script-flush.mdx
@@ -38,7 +38,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 SCRIPT FLUSH
diff --git a/redis/commands/scripting/script-kill.mdx b/redis/commands/scripting/script-kill.mdx
index 18df1b068..a0e5cea58 100644
--- a/redis/commands/scripting/script-kill.mdx
+++ b/redis/commands/scripting/script-kill.mdx
@@ -43,7 +43,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 SCRIPT KILL
diff --git a/redis/commands/scripting/script-load.mdx b/redis/commands/scripting/script-load.mdx
index 3a8a32a39..67a5ab696 100644
--- a/redis/commands/scripting/script-load.mdx
+++ b/redis/commands/scripting/script-load.mdx
@@ -44,7 +44,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 SCRIPT LOAD "return ARGV[1]"
diff --git a/redis/commands/search/search-aggregate.mdx b/redis/commands/search/search-aggregate.mdx
index 3caa9e445..b4ff4177d 100644
--- a/redis/commands/search/search-aggregate.mdx
+++ b/redis/commands/search/search-aggregate.mdx
@@ -36,7 +36,7 @@ Raw RESP output may be rendered differently by client or protocol settings, but
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 SEARCH.AGGREGATE products '{}' '{"avg_price": {"$avg": {"field": "price"}}}'
diff --git a/redis/commands/search/search-aliasadd.mdx b/redis/commands/search/search-aliasadd.mdx
index f16b50aac..20ce81af5 100644
--- a/redis/commands/search/search-aliasadd.mdx
+++ b/redis/commands/search/search-aliasadd.mdx
@@ -25,7 +25,7 @@ Returns `1` if a new alias was created or `2` if an existing alias was updated,
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 SEARCH.ALIASADD products products-v2
diff --git a/redis/commands/search/search-aliasdel.mdx b/redis/commands/search/search-aliasdel.mdx
index a23a13381..4917ee788 100644
--- a/redis/commands/search/search-aliasdel.mdx
+++ b/redis/commands/search/search-aliasdel.mdx
@@ -23,7 +23,7 @@ Returns `1` if the alias was deleted or `0` if the alias was not found.
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 SEARCH.ALIASDEL products
diff --git a/redis/commands/search/search-count.mdx b/redis/commands/search/search-count.mdx
index c798a8555..bb3545d59 100644
--- a/redis/commands/search/search-count.mdx
+++ b/redis/commands/search/search-count.mdx
@@ -25,7 +25,7 @@ Returns the number of matching documents as an integer. Returns `-1` if the inde
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 SEARCH.COUNT products '{"inStock": true}'
diff --git a/redis/commands/search/search-create.mdx b/redis/commands/search/search-create.mdx
index 182bb54c4..5f576d9a8 100644
--- a/redis/commands/search/search-create.mdx
+++ b/redis/commands/search/search-create.mdx
@@ -58,7 +58,7 @@ Returns `1` when the index is created. With `EXISTSOK`, returns `0` if the exist
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 SEARCH.CREATE products ON JSON PREFIX 1 product: SCHEMA name TEXT price F64 FAST inStock BOOL
diff --git a/redis/commands/search/search-describe.mdx b/redis/commands/search/search-describe.mdx
index 4078f4455..4ee7b38d7 100644
--- a/redis/commands/search/search-describe.mdx
+++ b/redis/commands/search/search-describe.mdx
@@ -49,7 +49,7 @@ Returns `null` if the index does not exist.
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 SEARCH.DESCRIBE products
diff --git a/redis/commands/search/search-drop.mdx b/redis/commands/search/search-drop.mdx
index ecdd7e361..15f3a0c39 100644
--- a/redis/commands/search/search-drop.mdx
+++ b/redis/commands/search/search-drop.mdx
@@ -25,7 +25,7 @@ Returns `1` if the index was dropped or `0` if the index was not found.
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 SEARCH.DROP products
diff --git a/redis/commands/search/search-listaliases.mdx b/redis/commands/search/search-listaliases.mdx
index 464e859fb..4aaab0375 100644
--- a/redis/commands/search/search-listaliases.mdx
+++ b/redis/commands/search/search-listaliases.mdx
@@ -25,7 +25,7 @@ The SDKs below decode the pairs into an object or dictionary that maps each alia
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 SEARCH.LISTALIASES
diff --git a/redis/commands/search/search-listindexes.mdx b/redis/commands/search/search-listindexes.mdx
index 8dee1fb90..57efcb092 100644
--- a/redis/commands/search/search-listindexes.mdx
+++ b/redis/commands/search/search-listindexes.mdx
@@ -43,7 +43,7 @@ Returns one entry per index, sorted by index name. Each entry is a map containin
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 SEARCH.LISTINDEXES MATCH 'product*' LIMIT 10 OFFSET 0
diff --git a/redis/commands/search/search-query.mdx b/redis/commands/search/search-query.mdx
index f67d41502..620de0741 100644
--- a/redis/commands/search/search-query.mdx
+++ b/redis/commands/search/search-query.mdx
@@ -69,7 +69,7 @@ When `NOCONTENT` is used, each result is `[key, score]`. When `SELECT` is used,
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 SEARCH.QUERY products '{"name": "wireless"}' LIMIT 10 OFFSET 0
diff --git a/redis/commands/search/search-reindex.mdx b/redis/commands/search/search-reindex.mdx
index cd3c275e1..48f246d57 100644
--- a/redis/commands/search/search-reindex.mdx
+++ b/redis/commands/search/search-reindex.mdx
@@ -27,7 +27,7 @@ Returns `1` when the index is rebuilt or `0` if the index does not exist.
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 SEARCH.REINDEX products
diff --git a/redis/commands/search/search-waitindexing.mdx b/redis/commands/search/search-waitindexing.mdx
index e044a3f92..95038c0ce 100644
--- a/redis/commands/search/search-waitindexing.mdx
+++ b/redis/commands/search/search-waitindexing.mdx
@@ -29,7 +29,7 @@ Returns `1` when indexing is complete or `0` if the index was not found.
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 SEARCH.WAITINDEXING products
diff --git a/redis/commands/server/acl.mdx b/redis/commands/server/acl.mdx
index f4ebc6012..ee3f5706f 100644
--- a/redis/commands/server/acl.mdx
+++ b/redis/commands/server/acl.mdx
@@ -64,7 +64,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 ACL WHOAMI
diff --git a/redis/commands/server/command.mdx b/redis/commands/server/command.mdx
index 130726f83..2ead75055 100644
--- a/redis/commands/server/command.mdx
+++ b/redis/commands/server/command.mdx
@@ -40,7 +40,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 COMMAND
diff --git a/redis/commands/server/config-get.mdx b/redis/commands/server/config-get.mdx
index 89ad19df7..2cb4a638f 100644
--- a/redis/commands/server/config-get.mdx
+++ b/redis/commands/server/config-get.mdx
@@ -46,7 +46,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 CONFIG GET notify-keyspace-events
diff --git a/redis/commands/server/config-set.mdx b/redis/commands/server/config-set.mdx
index 4e4cdd343..5b6e77cb2 100644
--- a/redis/commands/server/config-set.mdx
+++ b/redis/commands/server/config-set.mdx
@@ -47,7 +47,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 CONFIG SET notify-keyspace-events Ex
diff --git a/redis/commands/server/dbsize.mdx b/redis/commands/server/dbsize.mdx
index 55deab3ac..742bee053 100644
--- a/redis/commands/server/dbsize.mdx
+++ b/redis/commands/server/dbsize.mdx
@@ -40,7 +40,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 DBSIZE
diff --git a/redis/commands/server/flushall.mdx b/redis/commands/server/flushall.mdx
index 25cd27aec..2a9609d29 100644
--- a/redis/commands/server/flushall.mdx
+++ b/redis/commands/server/flushall.mdx
@@ -46,7 +46,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 FLUSHALL
diff --git a/redis/commands/server/flushdb.mdx b/redis/commands/server/flushdb.mdx
index 8b7017243..4fbe60aec 100644
--- a/redis/commands/server/flushdb.mdx
+++ b/redis/commands/server/flushdb.mdx
@@ -46,7 +46,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 FLUSHDB
diff --git a/redis/commands/server/info.mdx b/redis/commands/server/info.mdx
index 49ed6eb05..4758a110e 100644
--- a/redis/commands/server/info.mdx
+++ b/redis/commands/server/info.mdx
@@ -46,7 +46,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 INFO memory
diff --git a/redis/commands/server/monitor.mdx b/redis/commands/server/monitor.mdx
index ff646717b..b0cc3f135 100644
--- a/redis/commands/server/monitor.mdx
+++ b/redis/commands/server/monitor.mdx
@@ -44,7 +44,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 MONITOR
diff --git a/redis/commands/server/time.mdx b/redis/commands/server/time.mdx
index eb98e262e..895f7a7e8 100644
--- a/redis/commands/server/time.mdx
+++ b/redis/commands/server/time.mdx
@@ -36,7 +36,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 TIME
diff --git a/redis/commands/set/sadd.mdx b/redis/commands/set/sadd.mdx
index 9628dd42d..3e95157bd 100644
--- a/redis/commands/set/sadd.mdx
+++ b/redis/commands/set/sadd.mdx
@@ -39,7 +39,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 SADD my-key member
diff --git a/redis/commands/set/scard.mdx b/redis/commands/set/scard.mdx
index 552245bad..70d616a68 100644
--- a/redis/commands/set/scard.mdx
+++ b/redis/commands/set/scard.mdx
@@ -38,7 +38,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 SCARD my-key
diff --git a/redis/commands/set/sdiff.mdx b/redis/commands/set/sdiff.mdx
index 833c0da51..26ac6c192 100644
--- a/redis/commands/set/sdiff.mdx
+++ b/redis/commands/set/sdiff.mdx
@@ -40,7 +40,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 SDIFF set1 set2
diff --git a/redis/commands/set/sdiffstore.mdx b/redis/commands/set/sdiffstore.mdx
index 6022b7a11..cac73862e 100644
--- a/redis/commands/set/sdiffstore.mdx
+++ b/redis/commands/set/sdiffstore.mdx
@@ -41,7 +41,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 SDIFFSTORE dest set1 set2
diff --git a/redis/commands/set/sinter.mdx b/redis/commands/set/sinter.mdx
index 07505673a..5887f0043 100644
--- a/redis/commands/set/sinter.mdx
+++ b/redis/commands/set/sinter.mdx
@@ -40,7 +40,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 SINTER set1 set2
diff --git a/redis/commands/set/sintercard.mdx b/redis/commands/set/sintercard.mdx
index 501221e33..b72b5315f 100644
--- a/redis/commands/set/sintercard.mdx
+++ b/redis/commands/set/sintercard.mdx
@@ -46,7 +46,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 SINTERCARD 1 my-key
diff --git a/redis/commands/set/sinterstore.mdx b/redis/commands/set/sinterstore.mdx
index 9c1d3e485..1cef544ff 100644
--- a/redis/commands/set/sinterstore.mdx
+++ b/redis/commands/set/sinterstore.mdx
@@ -39,7 +39,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 SINTERSTORE destination set1 set2
diff --git a/redis/commands/set/sismember.mdx b/redis/commands/set/sismember.mdx
index c10c3667a..9cb271de2 100644
--- a/redis/commands/set/sismember.mdx
+++ b/redis/commands/set/sismember.mdx
@@ -39,7 +39,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 SISMEMBER my-key member
diff --git a/redis/commands/set/smembers.mdx b/redis/commands/set/smembers.mdx
index 473ef01d2..7b879c3ba 100644
--- a/redis/commands/set/smembers.mdx
+++ b/redis/commands/set/smembers.mdx
@@ -38,7 +38,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 SMEMBERS my-key
diff --git a/redis/commands/set/smismember.mdx b/redis/commands/set/smismember.mdx
index 211d0ccb8..b3f200891 100644
--- a/redis/commands/set/smismember.mdx
+++ b/redis/commands/set/smismember.mdx
@@ -39,7 +39,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 SMISMEMBER my-key member
diff --git a/redis/commands/set/smove.mdx b/redis/commands/set/smove.mdx
index 2cc3b7835..daefa309b 100644
--- a/redis/commands/set/smove.mdx
+++ b/redis/commands/set/smove.mdx
@@ -42,7 +42,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 SMOVE source-key destination-key member
diff --git a/redis/commands/set/spop.mdx b/redis/commands/set/spop.mdx
index b8a712f01..f72114147 100644
--- a/redis/commands/set/spop.mdx
+++ b/redis/commands/set/spop.mdx
@@ -41,7 +41,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 SPOP my-key
diff --git a/redis/commands/set/srandmember.mdx b/redis/commands/set/srandmember.mdx
index 9da8c8da0..f2006a6cb 100644
--- a/redis/commands/set/srandmember.mdx
+++ b/redis/commands/set/srandmember.mdx
@@ -41,7 +41,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 SRANDMEMBER my-key
diff --git a/redis/commands/set/srem.mdx b/redis/commands/set/srem.mdx
index 52cb78ce6..3286edaa9 100644
--- a/redis/commands/set/srem.mdx
+++ b/redis/commands/set/srem.mdx
@@ -39,7 +39,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 SREM my-key member
diff --git a/redis/commands/set/sscan.mdx b/redis/commands/set/sscan.mdx
index 43c77c6a1..ed322dfe2 100644
--- a/redis/commands/set/sscan.mdx
+++ b/redis/commands/set/sscan.mdx
@@ -48,7 +48,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 SSCAN my-key 0
diff --git a/redis/commands/set/sunion.mdx b/redis/commands/set/sunion.mdx
index 65915c5c9..27c231d5d 100644
--- a/redis/commands/set/sunion.mdx
+++ b/redis/commands/set/sunion.mdx
@@ -38,7 +38,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 SUNION set1 set2
diff --git a/redis/commands/set/sunionstore.mdx b/redis/commands/set/sunionstore.mdx
index b525c61d0..f96971ec7 100644
--- a/redis/commands/set/sunionstore.mdx
+++ b/redis/commands/set/sunionstore.mdx
@@ -39,7 +39,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 SUNIONSTORE destination set1 set2
diff --git a/redis/commands/sorted-set/bzmpop.mdx b/redis/commands/sorted-set/bzmpop.mdx
index 7e3947963..4abfb73b2 100644
--- a/redis/commands/sorted-set/bzmpop.mdx
+++ b/redis/commands/sorted-set/bzmpop.mdx
@@ -48,7 +48,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 BZMPOP 1.5 1 my-key MIN
diff --git a/redis/commands/sorted-set/bzpopmax.mdx b/redis/commands/sorted-set/bzpopmax.mdx
index ed4a7de6a..405c8e0b4 100644
--- a/redis/commands/sorted-set/bzpopmax.mdx
+++ b/redis/commands/sorted-set/bzpopmax.mdx
@@ -45,7 +45,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 BZPOPMAX my-key 1.5
diff --git a/redis/commands/sorted-set/bzpopmin.mdx b/redis/commands/sorted-set/bzpopmin.mdx
index f45419752..0eb6e71cd 100644
--- a/redis/commands/sorted-set/bzpopmin.mdx
+++ b/redis/commands/sorted-set/bzpopmin.mdx
@@ -45,7 +45,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 BZPOPMIN my-key 1.5
diff --git a/redis/commands/sorted-set/zadd.mdx b/redis/commands/sorted-set/zadd.mdx
index 6b13ee971..3dcff49e9 100644
--- a/redis/commands/sorted-set/zadd.mdx
+++ b/redis/commands/sorted-set/zadd.mdx
@@ -50,7 +50,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 ZADD my-key 1.5 member
diff --git a/redis/commands/sorted-set/zcard.mdx b/redis/commands/sorted-set/zcard.mdx
index 4a6975478..3d7bdcdc8 100644
--- a/redis/commands/sorted-set/zcard.mdx
+++ b/redis/commands/sorted-set/zcard.mdx
@@ -38,7 +38,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 ZCARD my-key
diff --git a/redis/commands/sorted-set/zcount.mdx b/redis/commands/sorted-set/zcount.mdx
index cdccb5888..016f6a15f 100644
--- a/redis/commands/sorted-set/zcount.mdx
+++ b/redis/commands/sorted-set/zcount.mdx
@@ -42,7 +42,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 ZCOUNT my-key 1.5 1.5
diff --git a/redis/commands/sorted-set/zdiff.mdx b/redis/commands/sorted-set/zdiff.mdx
index cb31e9856..20e6164a4 100644
--- a/redis/commands/sorted-set/zdiff.mdx
+++ b/redis/commands/sorted-set/zdiff.mdx
@@ -48,7 +48,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 ZDIFF 1 my-key
diff --git a/redis/commands/sorted-set/zdiffstore.mdx b/redis/commands/sorted-set/zdiffstore.mdx
index 348872789..13edf909d 100644
--- a/redis/commands/sorted-set/zdiffstore.mdx
+++ b/redis/commands/sorted-set/zdiffstore.mdx
@@ -46,7 +46,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 ZDIFFSTORE destination-key 1 my-key
diff --git a/redis/commands/sorted-set/zincrby.mdx b/redis/commands/sorted-set/zincrby.mdx
index a10b88943..6fbae2778 100644
--- a/redis/commands/sorted-set/zincrby.mdx
+++ b/redis/commands/sorted-set/zincrby.mdx
@@ -46,7 +46,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 ZINCRBY my-key 1 member
diff --git a/redis/commands/sorted-set/zinter.mdx b/redis/commands/sorted-set/zinter.mdx
index 65736698c..0cf67b3ff 100644
--- a/redis/commands/sorted-set/zinter.mdx
+++ b/redis/commands/sorted-set/zinter.mdx
@@ -53,7 +53,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 ZINTER 1 my-key
diff --git a/redis/commands/sorted-set/zintercard.mdx b/redis/commands/sorted-set/zintercard.mdx
index b4497df67..a4a238220 100644
--- a/redis/commands/sorted-set/zintercard.mdx
+++ b/redis/commands/sorted-set/zintercard.mdx
@@ -40,7 +40,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 ZINTERCARD 1 my-key
diff --git a/redis/commands/sorted-set/zinterstore.mdx b/redis/commands/sorted-set/zinterstore.mdx
index bc5b76290..b8845fb12 100644
--- a/redis/commands/sorted-set/zinterstore.mdx
+++ b/redis/commands/sorted-set/zinterstore.mdx
@@ -50,7 +50,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 ZINTERSTORE destination-key 1 my-key
diff --git a/redis/commands/sorted-set/zlexcount.mdx b/redis/commands/sorted-set/zlexcount.mdx
index f5d2885ba..807aa8518 100644
--- a/redis/commands/sorted-set/zlexcount.mdx
+++ b/redis/commands/sorted-set/zlexcount.mdx
@@ -42,7 +42,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 ZLEXCOUNT my-key - +
diff --git a/redis/commands/sorted-set/zmpop.mdx b/redis/commands/sorted-set/zmpop.mdx
index 141ea1b18..04bb26889 100644
--- a/redis/commands/sorted-set/zmpop.mdx
+++ b/redis/commands/sorted-set/zmpop.mdx
@@ -47,7 +47,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 ZMPOP 1 my-key MIN
diff --git a/redis/commands/sorted-set/zmscore.mdx b/redis/commands/sorted-set/zmscore.mdx
index 9d216b2a5..c31e251f0 100644
--- a/redis/commands/sorted-set/zmscore.mdx
+++ b/redis/commands/sorted-set/zmscore.mdx
@@ -43,7 +43,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 ZMSCORE my-key member
diff --git a/redis/commands/sorted-set/zpopmax.mdx b/redis/commands/sorted-set/zpopmax.mdx
index 70c7f06e6..5f84eb26a 100644
--- a/redis/commands/sorted-set/zpopmax.mdx
+++ b/redis/commands/sorted-set/zpopmax.mdx
@@ -45,7 +45,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 ZPOPMAX my-key
diff --git a/redis/commands/sorted-set/zpopmin.mdx b/redis/commands/sorted-set/zpopmin.mdx
index 00d9e0c2a..8f916390f 100644
--- a/redis/commands/sorted-set/zpopmin.mdx
+++ b/redis/commands/sorted-set/zpopmin.mdx
@@ -45,7 +45,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 ZPOPMIN my-key
diff --git a/redis/commands/sorted-set/zrandmember.mdx b/redis/commands/sorted-set/zrandmember.mdx
index 54956aa67..33a7e7b68 100644
--- a/redis/commands/sorted-set/zrandmember.mdx
+++ b/redis/commands/sorted-set/zrandmember.mdx
@@ -45,7 +45,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 ZRANDMEMBER my-key
diff --git a/redis/commands/sorted-set/zrange.mdx b/redis/commands/sorted-set/zrange.mdx
index a91f02824..d31c17975 100644
--- a/redis/commands/sorted-set/zrange.mdx
+++ b/redis/commands/sorted-set/zrange.mdx
@@ -57,7 +57,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 ZRANGE my-key 0 -1
diff --git a/redis/commands/sorted-set/zrangebylex.mdx b/redis/commands/sorted-set/zrangebylex.mdx
index 802b424a2..d49608c96 100644
--- a/redis/commands/sorted-set/zrangebylex.mdx
+++ b/redis/commands/sorted-set/zrangebylex.mdx
@@ -47,7 +47,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 ZRANGEBYLEX my-key - +
diff --git a/redis/commands/sorted-set/zrangebyscore.mdx b/redis/commands/sorted-set/zrangebyscore.mdx
index efe64d322..c2ae8a32e 100644
--- a/redis/commands/sorted-set/zrangebyscore.mdx
+++ b/redis/commands/sorted-set/zrangebyscore.mdx
@@ -52,7 +52,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 ZRANGEBYSCORE my-key 1.5 1.5
diff --git a/redis/commands/sorted-set/zrangestore.mdx b/redis/commands/sorted-set/zrangestore.mdx
index dc9cc2a26..407a66485 100644
--- a/redis/commands/sorted-set/zrangestore.mdx
+++ b/redis/commands/sorted-set/zrangestore.mdx
@@ -49,7 +49,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 ZRANGESTORE destination-key source-key -inf +inf BYSCORE
diff --git a/redis/commands/sorted-set/zrank.mdx b/redis/commands/sorted-set/zrank.mdx
index bd321f937..c4f40ee9a 100644
--- a/redis/commands/sorted-set/zrank.mdx
+++ b/redis/commands/sorted-set/zrank.mdx
@@ -46,7 +46,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 ZRANK my-key member
diff --git a/redis/commands/sorted-set/zrem.mdx b/redis/commands/sorted-set/zrem.mdx
index d0be824e5..ebebc5320 100644
--- a/redis/commands/sorted-set/zrem.mdx
+++ b/redis/commands/sorted-set/zrem.mdx
@@ -39,7 +39,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 ZREM my-key member
diff --git a/redis/commands/sorted-set/zremrangebylex.mdx b/redis/commands/sorted-set/zremrangebylex.mdx
index bc1ee425d..41bee1977 100644
--- a/redis/commands/sorted-set/zremrangebylex.mdx
+++ b/redis/commands/sorted-set/zremrangebylex.mdx
@@ -42,7 +42,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 ZREMRANGEBYLEX my-key - +
diff --git a/redis/commands/sorted-set/zremrangebyrank.mdx b/redis/commands/sorted-set/zremrangebyrank.mdx
index 031ef9e50..83f9a4581 100644
--- a/redis/commands/sorted-set/zremrangebyrank.mdx
+++ b/redis/commands/sorted-set/zremrangebyrank.mdx
@@ -42,7 +42,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 ZREMRANGEBYRANK my-key 0 0
diff --git a/redis/commands/sorted-set/zremrangebyscore.mdx b/redis/commands/sorted-set/zremrangebyscore.mdx
index bf5ca715e..8dbdaa9ee 100644
--- a/redis/commands/sorted-set/zremrangebyscore.mdx
+++ b/redis/commands/sorted-set/zremrangebyscore.mdx
@@ -42,7 +42,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 ZREMRANGEBYSCORE my-key 1.5 1.5
diff --git a/redis/commands/sorted-set/zrevrange.mdx b/redis/commands/sorted-set/zrevrange.mdx
index 6f5978d6d..56daa31b6 100644
--- a/redis/commands/sorted-set/zrevrange.mdx
+++ b/redis/commands/sorted-set/zrevrange.mdx
@@ -49,7 +49,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 ZREVRANGE my-key 0 0
diff --git a/redis/commands/sorted-set/zrevrangebylex.mdx b/redis/commands/sorted-set/zrevrangebylex.mdx
index c940cc673..be4573cee 100644
--- a/redis/commands/sorted-set/zrevrangebylex.mdx
+++ b/redis/commands/sorted-set/zrevrangebylex.mdx
@@ -47,7 +47,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 ZREVRANGEBYLEX my-key + -
diff --git a/redis/commands/sorted-set/zrevrangebyscore.mdx b/redis/commands/sorted-set/zrevrangebyscore.mdx
index 278546caa..e7f1ef1d4 100644
--- a/redis/commands/sorted-set/zrevrangebyscore.mdx
+++ b/redis/commands/sorted-set/zrevrangebyscore.mdx
@@ -50,7 +50,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 ZREVRANGEBYSCORE my-key 1.5 1.5
diff --git a/redis/commands/sorted-set/zrevrank.mdx b/redis/commands/sorted-set/zrevrank.mdx
index 80e515273..c4381ad90 100644
--- a/redis/commands/sorted-set/zrevrank.mdx
+++ b/redis/commands/sorted-set/zrevrank.mdx
@@ -44,7 +44,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 ZREVRANK my-key member
diff --git a/redis/commands/sorted-set/zscan.mdx b/redis/commands/sorted-set/zscan.mdx
index d39ae6467..2e7e2b813 100644
--- a/redis/commands/sorted-set/zscan.mdx
+++ b/redis/commands/sorted-set/zscan.mdx
@@ -49,7 +49,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 ZSCAN my-key 0
diff --git a/redis/commands/sorted-set/zscore.mdx b/redis/commands/sorted-set/zscore.mdx
index 2ffe75a12..32079fdef 100644
--- a/redis/commands/sorted-set/zscore.mdx
+++ b/redis/commands/sorted-set/zscore.mdx
@@ -43,7 +43,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 ZSCORE my-key member
diff --git a/redis/commands/sorted-set/zunion.mdx b/redis/commands/sorted-set/zunion.mdx
index a806b09e1..ed1d5395c 100644
--- a/redis/commands/sorted-set/zunion.mdx
+++ b/redis/commands/sorted-set/zunion.mdx
@@ -52,7 +52,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 ZUNION 1 my-key
diff --git a/redis/commands/sorted-set/zunionstore.mdx b/redis/commands/sorted-set/zunionstore.mdx
index ad0fc9e63..f425a400a 100644
--- a/redis/commands/sorted-set/zunionstore.mdx
+++ b/redis/commands/sorted-set/zunionstore.mdx
@@ -50,7 +50,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 ZUNIONSTORE destination-key 1 my-key
diff --git a/redis/commands/streams/xack.mdx b/redis/commands/streams/xack.mdx
index 31778dab4..ebd3dafd6 100644
--- a/redis/commands/streams/xack.mdx
+++ b/redis/commands/streams/xack.mdx
@@ -42,7 +42,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 XACK my-key workers 0-0
diff --git a/redis/commands/streams/xackdel.mdx b/redis/commands/streams/xackdel.mdx
index 5682ddd17..b26994546 100644
--- a/redis/commands/streams/xackdel.mdx
+++ b/redis/commands/streams/xackdel.mdx
@@ -45,7 +45,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 XACKDEL my-key workers IDS 1 0-0
diff --git a/redis/commands/streams/xadd.mdx b/redis/commands/streams/xadd.mdx
index 2157e522d..bdb793941 100644
--- a/redis/commands/streams/xadd.mdx
+++ b/redis/commands/streams/xadd.mdx
@@ -51,7 +51,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 XADD my-key * field value
diff --git a/redis/commands/streams/xautoclaim.mdx b/redis/commands/streams/xautoclaim.mdx
index 85000b71c..ab42b1dab 100644
--- a/redis/commands/streams/xautoclaim.mdx
+++ b/redis/commands/streams/xautoclaim.mdx
@@ -46,7 +46,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 XAUTOCLAIM my-key workers worker-1 60000 0-0
diff --git a/redis/commands/streams/xclaim.mdx b/redis/commands/streams/xclaim.mdx
index 39b99051a..41797fc61 100644
--- a/redis/commands/streams/xclaim.mdx
+++ b/redis/commands/streams/xclaim.mdx
@@ -58,7 +58,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 XCLAIM my-key workers worker-1 60000 0-0
diff --git a/redis/commands/streams/xdel.mdx b/redis/commands/streams/xdel.mdx
index 6c13583b1..e34154844 100644
--- a/redis/commands/streams/xdel.mdx
+++ b/redis/commands/streams/xdel.mdx
@@ -41,7 +41,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 XDEL my-key 0-0
diff --git a/redis/commands/streams/xdelex.mdx b/redis/commands/streams/xdelex.mdx
index 9fbe09b87..782be2f4b 100644
--- a/redis/commands/streams/xdelex.mdx
+++ b/redis/commands/streams/xdelex.mdx
@@ -44,7 +44,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 XDELEX my-key IDS 1 0-0
diff --git a/redis/commands/streams/xgroup.mdx b/redis/commands/streams/xgroup.mdx
index b025ac0e8..f120e3927 100644
--- a/redis/commands/streams/xgroup.mdx
+++ b/redis/commands/streams/xgroup.mdx
@@ -51,7 +51,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 XGROUP CREATE events workers $ MKSTREAM
diff --git a/redis/commands/streams/xinfo-consumers.mdx b/redis/commands/streams/xinfo-consumers.mdx
index 29655c2d9..f71cc62fa 100644
--- a/redis/commands/streams/xinfo-consumers.mdx
+++ b/redis/commands/streams/xinfo-consumers.mdx
@@ -39,7 +39,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 XINFO CONSUMERS my-key workers
diff --git a/redis/commands/streams/xinfo-groups.mdx b/redis/commands/streams/xinfo-groups.mdx
index 7e901bbac..30e2f3de7 100644
--- a/redis/commands/streams/xinfo-groups.mdx
+++ b/redis/commands/streams/xinfo-groups.mdx
@@ -38,7 +38,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 XINFO GROUPS my-key
diff --git a/redis/commands/streams/xinfo-stream.mdx b/redis/commands/streams/xinfo-stream.mdx
index bbef591ab..352b1aa75 100644
--- a/redis/commands/streams/xinfo-stream.mdx
+++ b/redis/commands/streams/xinfo-stream.mdx
@@ -41,7 +41,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 XINFO STREAM my-key
diff --git a/redis/commands/streams/xlen.mdx b/redis/commands/streams/xlen.mdx
index 9ee31be57..bd8d014b4 100644
--- a/redis/commands/streams/xlen.mdx
+++ b/redis/commands/streams/xlen.mdx
@@ -38,7 +38,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 XLEN my-key
diff --git a/redis/commands/streams/xpending.mdx b/redis/commands/streams/xpending.mdx
index 0199d949b..8911880ea 100644
--- a/redis/commands/streams/xpending.mdx
+++ b/redis/commands/streams/xpending.mdx
@@ -47,7 +47,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 XPENDING my-key workers
diff --git a/redis/commands/streams/xrange.mdx b/redis/commands/streams/xrange.mdx
index 01dd8725d..61d832567 100644
--- a/redis/commands/streams/xrange.mdx
+++ b/redis/commands/streams/xrange.mdx
@@ -43,7 +43,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 XRANGE my-key - +
diff --git a/redis/commands/streams/xread.mdx b/redis/commands/streams/xread.mdx
index 742b8a387..5c8c62c17 100644
--- a/redis/commands/streams/xread.mdx
+++ b/redis/commands/streams/xread.mdx
@@ -52,7 +52,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 XREAD STREAMS my-key 0-0
diff --git a/redis/commands/streams/xreadgroup.mdx b/redis/commands/streams/xreadgroup.mdx
index 9c53e663a..0fa68edf0 100644
--- a/redis/commands/streams/xreadgroup.mdx
+++ b/redis/commands/streams/xreadgroup.mdx
@@ -55,7 +55,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 XREADGROUP GROUP workers worker-1 STREAMS my-key 0-0
diff --git a/redis/commands/streams/xrevrange.mdx b/redis/commands/streams/xrevrange.mdx
index 8647a5e72..dedd6765b 100644
--- a/redis/commands/streams/xrevrange.mdx
+++ b/redis/commands/streams/xrevrange.mdx
@@ -43,7 +43,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 XREVRANGE my-key + -
diff --git a/redis/commands/streams/xtrim.mdx b/redis/commands/streams/xtrim.mdx
index a5b09813c..326faf208 100644
--- a/redis/commands/streams/xtrim.mdx
+++ b/redis/commands/streams/xtrim.mdx
@@ -46,7 +46,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 XTRIM my-key MAXLEN 100
diff --git a/redis/commands/string/append.mdx b/redis/commands/string/append.mdx
index 5dc2678f3..fdcb3719a 100644
--- a/redis/commands/string/append.mdx
+++ b/redis/commands/string/append.mdx
@@ -39,7 +39,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 APPEND my-key value
diff --git a/redis/commands/string/decr.mdx b/redis/commands/string/decr.mdx
index f43604344..8005f3f88 100644
--- a/redis/commands/string/decr.mdx
+++ b/redis/commands/string/decr.mdx
@@ -38,7 +38,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 DECR my-key
diff --git a/redis/commands/string/decrby.mdx b/redis/commands/string/decrby.mdx
index 374430eb4..7a5f28c05 100644
--- a/redis/commands/string/decrby.mdx
+++ b/redis/commands/string/decrby.mdx
@@ -39,7 +39,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 DECRBY my-key 1
diff --git a/redis/commands/string/delex.mdx b/redis/commands/string/delex.mdx
index 774aa9eb0..5f632b8b4 100644
--- a/redis/commands/string/delex.mdx
+++ b/redis/commands/string/delex.mdx
@@ -47,7 +47,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 DELEX lock:job-1 IFEQ worker-1
diff --git a/redis/commands/string/digest.mdx b/redis/commands/string/digest.mdx
index 0c16d8e67..6a520cbae 100644
--- a/redis/commands/string/digest.mdx
+++ b/redis/commands/string/digest.mdx
@@ -45,7 +45,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 DIGEST lock:job-1
diff --git a/redis/commands/string/get.mdx b/redis/commands/string/get.mdx
index 51b2466e0..040e01dce 100644
--- a/redis/commands/string/get.mdx
+++ b/redis/commands/string/get.mdx
@@ -38,7 +38,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 GET my-key
diff --git a/redis/commands/string/getdel.mdx b/redis/commands/string/getdel.mdx
index 8a08bd833..617b79237 100644
--- a/redis/commands/string/getdel.mdx
+++ b/redis/commands/string/getdel.mdx
@@ -38,7 +38,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 GETDEL my-key
diff --git a/redis/commands/string/getex.mdx b/redis/commands/string/getex.mdx
index e2592db2b..00a8d15ec 100644
--- a/redis/commands/string/getex.mdx
+++ b/redis/commands/string/getex.mdx
@@ -43,7 +43,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 GETEX my-key
diff --git a/redis/commands/string/getrange.mdx b/redis/commands/string/getrange.mdx
index 2ea20a6e5..d43a33e36 100644
--- a/redis/commands/string/getrange.mdx
+++ b/redis/commands/string/getrange.mdx
@@ -46,7 +46,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 GETRANGE my-key 0 1
diff --git a/redis/commands/string/getset.mdx b/redis/commands/string/getset.mdx
index 683172246..a3927b86a 100644
--- a/redis/commands/string/getset.mdx
+++ b/redis/commands/string/getset.mdx
@@ -45,7 +45,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 GETSET my-key value
diff --git a/redis/commands/string/incr.mdx b/redis/commands/string/incr.mdx
index b6854da22..9f847c120 100644
--- a/redis/commands/string/incr.mdx
+++ b/redis/commands/string/incr.mdx
@@ -40,7 +40,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 INCR my-key
diff --git a/redis/commands/string/incrby.mdx b/redis/commands/string/incrby.mdx
index ead1fd120..65bdc9d41 100644
--- a/redis/commands/string/incrby.mdx
+++ b/redis/commands/string/incrby.mdx
@@ -41,7 +41,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 INCRBY my-key 1
diff --git a/redis/commands/string/incrbyfloat.mdx b/redis/commands/string/incrbyfloat.mdx
index bf962e59e..1c927de71 100644
--- a/redis/commands/string/incrbyfloat.mdx
+++ b/redis/commands/string/incrbyfloat.mdx
@@ -45,7 +45,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 INCRBYFLOAT my-key 1.5
diff --git a/redis/commands/string/mget.mdx b/redis/commands/string/mget.mdx
index 285a59d7a..0c87cfe75 100644
--- a/redis/commands/string/mget.mdx
+++ b/redis/commands/string/mget.mdx
@@ -40,7 +40,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 MGET key1 key2 key3
diff --git a/redis/commands/string/mset.mdx b/redis/commands/string/mset.mdx
index 13206710b..613c40e26 100644
--- a/redis/commands/string/mset.mdx
+++ b/redis/commands/string/mset.mdx
@@ -40,7 +40,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 MSET key1 1 key2 hello
diff --git a/redis/commands/string/msetnx.mdx b/redis/commands/string/msetnx.mdx
index 8c532de4c..d921f8810 100644
--- a/redis/commands/string/msetnx.mdx
+++ b/redis/commands/string/msetnx.mdx
@@ -38,7 +38,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 MSETNX key1 value1 key2 value2
diff --git a/redis/commands/string/psetex.mdx b/redis/commands/string/psetex.mdx
index 3214f1a19..2abdea271 100644
--- a/redis/commands/string/psetex.mdx
+++ b/redis/commands/string/psetex.mdx
@@ -46,7 +46,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 PSETEX my-key 1000 value
diff --git a/redis/commands/string/set.mdx b/redis/commands/string/set.mdx
index 5298aa414..9e680b953 100644
--- a/redis/commands/string/set.mdx
+++ b/redis/commands/string/set.mdx
@@ -57,7 +57,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 SET my-key value
diff --git a/redis/commands/string/setex.mdx b/redis/commands/string/setex.mdx
index c59069759..e180b1bb7 100644
--- a/redis/commands/string/setex.mdx
+++ b/redis/commands/string/setex.mdx
@@ -46,7 +46,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 SETEX my-key 1000 value
diff --git a/redis/commands/string/setnx.mdx b/redis/commands/string/setnx.mdx
index 8d19450b2..cd9e966de 100644
--- a/redis/commands/string/setnx.mdx
+++ b/redis/commands/string/setnx.mdx
@@ -45,7 +45,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 SETNX my-key value
diff --git a/redis/commands/string/setrange.mdx b/redis/commands/string/setrange.mdx
index 1d7f229c1..deabc3272 100644
--- a/redis/commands/string/setrange.mdx
+++ b/redis/commands/string/setrange.mdx
@@ -42,7 +42,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 SETRANGE my-key 0 value
diff --git a/redis/commands/string/strlen.mdx b/redis/commands/string/strlen.mdx
index 547aec3bf..3c75b6dbd 100644
--- a/redis/commands/string/strlen.mdx
+++ b/redis/commands/string/strlen.mdx
@@ -38,7 +38,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 STRLEN my-key
diff --git a/redis/commands/transactions/discard.mdx b/redis/commands/transactions/discard.mdx
index 4516af76d..d6e47e7b2 100644
--- a/redis/commands/transactions/discard.mdx
+++ b/redis/commands/transactions/discard.mdx
@@ -42,7 +42,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 MULTI
diff --git a/redis/commands/transactions/exec.mdx b/redis/commands/transactions/exec.mdx
index 38f477ef8..c40e76ee5 100644
--- a/redis/commands/transactions/exec.mdx
+++ b/redis/commands/transactions/exec.mdx
@@ -44,7 +44,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 MULTI
diff --git a/redis/commands/transactions/multi.mdx b/redis/commands/transactions/multi.mdx
index cecc85882..951cc6bff 100644
--- a/redis/commands/transactions/multi.mdx
+++ b/redis/commands/transactions/multi.mdx
@@ -44,7 +44,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 MULTI
diff --git a/redis/commands/transactions/unwatch.mdx b/redis/commands/transactions/unwatch.mdx
index 280d8f3cf..f32c56bcf 100644
--- a/redis/commands/transactions/unwatch.mdx
+++ b/redis/commands/transactions/unwatch.mdx
@@ -42,7 +42,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 UNWATCH
diff --git a/redis/commands/transactions/watch.mdx b/redis/commands/transactions/watch.mdx
index 19afc67d6..5f00b2e04 100644
--- a/redis/commands/transactions/watch.mdx
+++ b/redis/commands/transactions/watch.mdx
@@ -46,7 +46,7 @@ TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use
 
 <AccordionGroup>
 
-<Accordion title="Redis CLI" defaultOpen>
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 WATCH balance

From 818a44744614294f317433c7a34343ec14b9571f Mon Sep 17 00:00:00 2001
From: "github-actions[bot]"
 <41898282+github-actions[bot]@users.noreply.github.com>
Date: Thu, 13 Aug 2026 12:11:44 +0000
Subject: [PATCH 12/12] chore(llms): regenerate llms.txt and llms-full.txt

---
 llms-full.txt | 12089 ++++++++++++++++++++++++++++--------------------
 1 file changed, 7090 insertions(+), 4999 deletions(-)

diff --git a/llms-full.txt b/llms-full.txt
index 0568bb4c4..1de7dae59 100644
--- a/llms-full.txt
+++ b/llms-full.txt
@@ -17003,9 +17003,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
 
-<Tab title="@upstash/redis">
+```bash
+BITCOUNT my-key
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -17015,9 +17023,9 @@ const redis = Redis.fromEnv();
 const bits = await redis.bitcount(key);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -17027,9 +17035,9 @@ result = redis.bitcount("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -17039,9 +17047,9 @@ const result = await redis.bitcount("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -17053,9 +17061,9 @@ const result = await client.bitCount("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -17066,9 +17074,9 @@ result = client.bitcount("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -17095,9 +17103,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -17110,9 +17118,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -17128,9 +17136,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # BITFIELD
 Source: https://upstash.com/docs/redis/commands/bitmap/bitfield
@@ -17182,9 +17190,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
 
-<Tab title="@upstash/redis">
+```bash
+BITFIELD my-key GET u8 0
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -17194,9 +17210,9 @@ const result = await redis.bitfield("my-key").get("u8", 0).exec();
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -17206,9 +17222,9 @@ result = redis.bitfield("my-key").get("u8", 0).execute()
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -17218,9 +17234,9 @@ const result = await redis.bitfield("my-key", "GET", "u8", "0");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -17232,9 +17248,9 @@ const result = await client.bitField("my-key", [{ operation: "GET", encoding: "u
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -17245,9 +17261,9 @@ result = client.bitfield("my-key").get("u8", 0).execute()
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -17274,9 +17290,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -17289,9 +17305,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -17307,9 +17323,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # BITFIELD_RO
 Source: https://upstash.com/docs/redis/commands/bitmap/bitfield-ro
@@ -17348,17 +17364,25 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+BITFIELD_RO my-key GET u8 0
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -17368,9 +17392,9 @@ result = redis.bitfield_ro("my-key").get("u8", 0).execute()
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -17380,9 +17404,9 @@ const result = await redis.bitfield_ro("my-key", "GET", "u8", "0");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -17394,9 +17418,9 @@ const result = await client.bitFieldRo("my-key", [{ encoding: "u8", offset: 0 }]
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -17407,9 +17431,9 @@ result = client.bitfield_ro("my-key", "u8", 0)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -17436,9 +17460,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -17451,9 +17475,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -17469,9 +17493,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # BITOP
 Source: https://upstash.com/docs/redis/commands/bitmap/bitop
@@ -17515,9 +17539,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
 
-<Tab title="@upstash/redis">
+```bash
+BITOP AND destination-key source-key-1 source-key-2
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -17537,9 +17569,9 @@ await redis.bitop("xor", "destKey", "sourceKey1", "sourceKey2");
 await redis.bitop("not", "destKey", "sourceKey");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -17549,9 +17581,9 @@ result = redis.bitop("AND", "destination-key", "source-key-1", "source-key-2")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -17561,9 +17593,9 @@ const result = await redis.bitop("AND", "destination-key", "source-key-1", "sour
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -17575,9 +17607,9 @@ const result = await client.bitOp("AND", "destination-key", ["source-key-1", "so
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -17588,9 +17620,9 @@ result = client.bitop("AND", "destination-key", "source-key-1", "source-key-2")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -17617,9 +17649,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -17632,9 +17664,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -17650,9 +17682,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # BITPOS
 Source: https://upstash.com/docs/redis/commands/bitmap/bitpos
@@ -17694,9 +17726,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+BITPOS my-key 1
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -17706,9 +17746,9 @@ const redis = Redis.fromEnv();
 await redis.bitpos("key", 1);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -17718,9 +17758,9 @@ result = redis.bitpos("my-key", 1)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -17730,9 +17770,9 @@ const result = await redis.bitpos("my-key", "1");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -17744,9 +17784,9 @@ const result = await client.bitPos("my-key", 1);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -17757,9 +17797,9 @@ result = client.bitpos("my-key", 1)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -17786,9 +17826,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -17801,9 +17841,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -17820,9 +17860,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # GETBIT
 Source: https://upstash.com/docs/redis/commands/bitmap/getbit
@@ -17861,9 +17901,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+GETBIT my-key 0
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -17873,9 +17921,9 @@ const redis = Redis.fromEnv();
 const bit = await redis.getbit(key, 4);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -17885,9 +17933,9 @@ result = redis.getbit("my-key", 0)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -17897,9 +17945,9 @@ const result = await redis.getbit("my-key", "0");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -17911,9 +17959,9 @@ const result = await client.getBit("my-key", 0);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -17924,9 +17972,9 @@ result = client.getbit("my-key", 0)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -17953,9 +18001,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -17968,9 +18016,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -17986,9 +18034,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # Bitmap commands
 Source: https://upstash.com/docs/redis/commands/bitmap/overview
@@ -18043,9 +18091,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+SETBIT my-key 0 1
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -18055,9 +18111,9 @@ const redis = Redis.fromEnv();
 const originalBit = await redis.setbit(key, 4, 1);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -18067,9 +18123,9 @@ result = redis.setbit("my-key", 0, 1)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -18079,9 +18135,9 @@ const result = await redis.setbit("my-key", "0", "1");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -18093,9 +18149,9 @@ const result = await client.setBit("my-key", 0, 1);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -18106,9 +18162,9 @@ result = client.setbit("my-key", 0, 1)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -18135,9 +18191,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -18150,9 +18206,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -18168,9 +18224,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # AUTH
 Source: https://upstash.com/docs/redis/commands/connection/auth
@@ -18213,9 +18269,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+AUTH password
+```
+
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -18225,9 +18289,9 @@ const result = await redis.auth("password");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -18239,9 +18303,9 @@ const result = await client.auth({ password: "password" });
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -18252,9 +18316,9 @@ result = client.auth("password")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -18281,9 +18345,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -18296,9 +18360,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -18314,9 +18378,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # CLIENT GETNAME
 Source: https://upstash.com/docs/redis/commands/connection/client-getname
@@ -18357,9 +18421,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+CLIENT GETNAME
+```
+
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -18369,9 +18441,9 @@ const result = await redis.client("GETNAME");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -18383,9 +18455,9 @@ const result = await client.clientGetName();
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -18396,9 +18468,9 @@ result = client.client_getname()
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -18425,9 +18497,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -18440,27 +18512,27 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
+use redis::TypedCommands;
+
 fn main() -> redis::RedisResult<()> {
     let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
     let client = redis::Client::open(url)?;
     let mut connection = client.get_connection()?;
 
-    let mut command = redis::cmd("CLIENT");
-    command.arg("GETNAME");
-    let result: redis::Value = command.query(&mut connection)?;
+    let result = connection.client_getname()?;
     println!("{result:?}");
     Ok(())
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # CLIENT ID
 Source: https://upstash.com/docs/redis/commands/connection/client-id
@@ -18501,9 +18573,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
 
-<Tab title="ioredis">
+```bash
+CLIENT ID
+```
+
+</Accordion>
+
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -18513,9 +18593,9 @@ const result = await redis.client("ID");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -18527,9 +18607,9 @@ const result = await client.clientId();
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -18540,9 +18620,9 @@ result = client.client_id()
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -18569,9 +18649,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -18584,27 +18664,27 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
+use redis::TypedCommands;
+
 fn main() -> redis::RedisResult<()> {
     let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
     let client = redis::Client::open(url)?;
     let mut connection = client.get_connection()?;
 
-    let mut command = redis::cmd("CLIENT");
-    command.arg("ID");
-    let result: redis::Value = command.query(&mut connection)?;
+    let result = connection.client_id()?;
     println!("{result:?}");
     Ok(())
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # CLIENT INFO
 Source: https://upstash.com/docs/redis/commands/connection/client-info
@@ -18645,9 +18725,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+CLIENT INFO
+```
+
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -18657,9 +18745,9 @@ const result = await redis.client("INFO");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -18671,9 +18759,9 @@ const result = await client.clientInfo();
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -18684,9 +18772,9 @@ result = client.client_info()
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -18713,9 +18801,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -18728,9 +18816,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -18746,9 +18834,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # CLIENT LIST
 Source: https://upstash.com/docs/redis/commands/connection/client-list
@@ -18789,9 +18877,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="ioredis">
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+CLIENT LIST
+```
+
+</Accordion>
+
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -18801,9 +18897,9 @@ const result = await redis.client("LIST");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -18815,9 +18911,9 @@ const result = await client.clientList();
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -18828,9 +18924,9 @@ result = client.client_list()
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -18857,9 +18953,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -18872,9 +18968,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -18890,9 +18986,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # CLIENT SETINFO
 Source: https://upstash.com/docs/redis/commands/connection/client-setinfo
@@ -18936,9 +19032,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
 
-<Tab title="ioredis">
+```bash
+CLIENT SETINFO LIB-NAME my-client
+```
+
+</Accordion>
+
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -18948,9 +19052,9 @@ const result = await redis.call("CLIENT", "SETINFO", "LIB-NAME", "my-client");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -18962,9 +19066,9 @@ const result = await client.sendCommand(["CLIENT", "SETINFO", "LIB-NAME", "my-cl
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -18975,9 +19079,9 @@ result = client.client_setinfo("LIB-NAME", "my-client")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -19004,9 +19108,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -19019,9 +19123,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -19039,9 +19143,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # CLIENT SETNAME
 Source: https://upstash.com/docs/redis/commands/connection/client-setname
@@ -19084,9 +19188,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+CLIENT SETNAME worker-1
+```
+
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -19096,9 +19208,9 @@ const result = await redis.client("SETNAME", "worker-1");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -19110,9 +19222,9 @@ const result = await client.clientSetName("worker-1");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -19123,9 +19235,9 @@ result = client.client_setname("worker-1")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -19152,9 +19264,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -19167,28 +19279,27 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
+use redis::TypedCommands;
+
 fn main() -> redis::RedisResult<()> {
     let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
     let client = redis::Client::open(url)?;
     let mut connection = client.get_connection()?;
 
-    let mut command = redis::cmd("CLIENT");
-    command.arg("SETNAME");
-    command.arg("worker-1");
-    let result: redis::Value = command.query(&mut connection)?;
+    let result = connection.client_setname("worker-1")?;
     println!("{result:?}");
     Ok(())
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # ECHO
 Source: https://upstash.com/docs/redis/commands/connection/echo
@@ -19226,9 +19337,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+ECHO hello
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -19239,9 +19358,9 @@ const response = await redis.echo("hello world");
 console.log(response); // "hello world"
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -19251,9 +19370,9 @@ result = redis.echo("hello")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -19263,9 +19382,9 @@ const result = await redis.echo("hello");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -19277,9 +19396,9 @@ const result = await client.echo("hello");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -19290,9 +19409,9 @@ result = client.echo("hello")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -19319,9 +19438,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -19334,9 +19453,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -19352,9 +19471,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # HELLO
 Source: https://upstash.com/docs/redis/commands/connection/hello
@@ -19401,9 +19520,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+HELLO
+```
+
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -19413,9 +19540,9 @@ const result = await redis.hello();
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -19427,9 +19554,9 @@ const result = await client.hello();
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -19440,9 +19567,9 @@ result = client.hello()
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -19469,9 +19596,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -19486,9 +19613,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -19504,9 +19631,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # Connection commands
 Source: https://upstash.com/docs/redis/commands/connection/overview
@@ -19568,9 +19695,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+PING
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -19581,9 +19716,9 @@ const response = await redis.ping();
 console.log(response); // "PONG"
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -19593,9 +19728,9 @@ result = redis.ping()
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -19605,9 +19740,9 @@ const result = await redis.ping();
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -19619,9 +19754,9 @@ const result = await client.ping();
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -19632,9 +19767,9 @@ result = client.ping()
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -19661,9 +19796,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -19676,33 +19811,33 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
+use redis::TypedCommands;
+
 fn main() -> redis::RedisResult<()> {
     let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
     let client = redis::Client::open(url)?;
     let mut connection = client.get_connection()?;
 
-    let mut command = redis::cmd("PING");
-
-    let result: redis::Value = command.query(&mut connection)?;
+    let result = connection.ping()?;
     println!("{result:?}");
     Ok(())
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # QUIT
 Source: https://upstash.com/docs/redis/commands/connection/quit
 
 <Warning>
-  Prefer closing the connection from the client in new code, which avoids leaving `TIME_WAIT` sockets on the server. `QUIT` has no replacement command; it is deprecated in Redis but still supported by Upstash.
+  Prefer closing the connection from the client in new code, which avoids leaving `TIME_WAIT` sockets on the server.
 </Warning>
 
 Use `QUIT` to ask the server to close the connection once all pending replies have been sent.
@@ -19740,9 +19875,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+QUIT
+```
+
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -19752,9 +19895,9 @@ const result = await redis.quit();
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -19766,9 +19909,9 @@ const result = await client.sendCommand(["QUIT"]);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -19779,9 +19922,9 @@ result = client.quit()
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -19808,9 +19951,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -19825,9 +19968,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -19843,9 +19986,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # RESET
 Source: https://upstash.com/docs/redis/commands/connection/reset
@@ -19885,9 +20028,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="ioredis">
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+RESET
+```
+
+</Accordion>
+
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -19897,9 +20048,9 @@ const result = await redis.reset();
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -19911,9 +20062,9 @@ const result = await client.sendCommand(["RESET"]);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -19924,9 +20075,9 @@ result = client.reset()
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -19953,9 +20104,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -19968,9 +20119,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -19986,9 +20137,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # SELECT
 Source: https://upstash.com/docs/redis/commands/connection/select
@@ -20030,25 +20181,33 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+SELECT 0
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 <Note>
   This command is not supported yet in `upstash_redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -20058,9 +20217,9 @@ const result = await redis.select("0");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -20072,9 +20231,9 @@ const result = await client.sendCommand(["SELECT", "0"]);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -20085,9 +20244,9 @@ result = client.select("0")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -20114,9 +20273,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -20129,9 +20288,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -20147,9 +20306,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # FCALL
 Source: https://upstash.com/docs/redis/commands/functions/fcall
@@ -20220,9 +20379,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+FCALL my_function 1 my-key value
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -20244,17 +20411,17 @@ const res = await redis.functions.call("helloworld");
 console.log(res); // "Hello World!"
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 <Note>
   This command is not supported yet in `upstash_redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -20264,9 +20431,9 @@ const result = await redis.fcall("my_function", "1", "my-key", "value");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -20278,9 +20445,9 @@ const result = await client.fCall("my_function", { keys: ["my-key"], arguments:
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -20291,9 +20458,9 @@ result = client.fcall("my_function", 1, "my-key", "value")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -20320,9 +20487,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -20335,9 +20502,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -20354,9 +20521,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # FCALL_RO
 Source: https://upstash.com/docs/redis/commands/functions/fcall-ro
@@ -20407,9 +20574,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+FCALL_RO my_function 1 my-key value
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -20438,17 +20613,17 @@ await redis.functions.load({ code, replace: true });
 const value = await redis.functions.callRo("get_value", ["mykey"])
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 <Note>
   This command is not supported yet in `upstash_redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -20458,9 +20633,9 @@ const result = await redis.fcall_ro("my_function", "1", "my-key", "value");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -20472,9 +20647,9 @@ const result = await client.fCallRo("my_function", { keys: ["my-key"], arguments
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -20485,9 +20660,9 @@ result = client.fcall_ro("my_function", 1, "my-key", "value")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -20514,9 +20689,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -20529,9 +20704,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -20548,9 +20723,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # FUNCTION DELETE
 Source: https://upstash.com/docs/redis/commands/functions/function-delete
@@ -20588,9 +20763,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+FUNCTION DELETE mylib
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -20600,17 +20783,17 @@ const redis = Redis.fromEnv();
 await redis.functions.delete("mylib")
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 <Note>
   This command is not supported yet in `upstash_redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -20620,9 +20803,9 @@ const result = await redis.function("DELETE", "library-name");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -20634,9 +20817,9 @@ const result = await client.functionDelete("library-name");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -20647,9 +20830,9 @@ result = client.function_delete("library-name")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -20676,9 +20859,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -20691,9 +20874,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -20710,9 +20893,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # FUNCTION FLUSH
 Source: https://upstash.com/docs/redis/commands/functions/function-flush
@@ -20750,9 +20933,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+FUNCTION FLUSH
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -20762,17 +20953,17 @@ const redis = Redis.fromEnv();
 await redis.functions.flush()
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 <Note>
   This command is not supported yet in `upstash_redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -20782,9 +20973,9 @@ const result = await redis.function("FLUSH");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -20796,9 +20987,9 @@ const result = await client.functionFlush();
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -20809,9 +21000,9 @@ result = client.function_flush()
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -20838,9 +21029,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -20853,9 +21044,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -20871,9 +21062,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # FUNCTION KILL
 Source: https://upstash.com/docs/redis/commands/functions/function-kill
@@ -20915,25 +21106,33 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+FUNCTION KILL
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 <Note>
   This command is not supported yet in `upstash_redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -20943,9 +21142,9 @@ const result = await redis.function("KILL");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -20957,9 +21156,9 @@ const result = await client.functionKill();
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -20970,9 +21169,9 @@ result = client.function_kill()
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -20999,9 +21198,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -21014,9 +21213,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -21032,9 +21231,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # FUNCTION LIST
 Source: https://upstash.com/docs/redis/commands/functions/function-list
@@ -21073,9 +21272,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+FUNCTION LIST
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -21102,17 +21309,17 @@ console.log(libs)
 // ]
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 <Note>
   This command is not supported yet in `upstash_redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -21122,9 +21329,9 @@ const result = await redis.function("LIST");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -21136,9 +21343,9 @@ const result = await client.functionList();
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -21149,9 +21356,9 @@ result = client.function_list()
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -21178,9 +21385,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -21193,9 +21400,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -21211,9 +21418,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # FUNCTION LOAD
 Source: https://upstash.com/docs/redis/commands/functions/function-load
@@ -21258,9 +21465,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+FUNCTION LOAD "#!lua name=mylib\nredis.register_function('helloworld', function() return 'Hello World!' end)"
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -21290,17 +21505,17 @@ const libraryName = await redis.functions.load({ code, replace: true });
 console.log(libraryName); // "mylib"
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 <Note>
   This command is not supported yet in `upstash_redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -21310,9 +21525,9 @@ const result = await redis.function("LOAD", "function-code");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -21324,9 +21539,9 @@ const result = await client.functionLoad("function-code");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -21337,9 +21552,9 @@ result = client.function_load("function-code")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -21366,9 +21581,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -21381,9 +21596,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -21400,9 +21615,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # FUNCTION STATS
 Source: https://upstash.com/docs/redis/commands/functions/function-stats
@@ -21438,9 +21653,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+FUNCTION STATS
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -21460,17 +21683,17 @@ console.log(stats)
 // }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 <Note>
   This command is not supported yet in `upstash_redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -21480,9 +21703,9 @@ const result = await redis.function("STATS");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -21494,9 +21717,9 @@ const result = await client.functionStats();
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -21507,9 +21730,9 @@ result = client.function_stats()
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -21536,9 +21759,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -21551,9 +21774,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -21569,9 +21792,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # Functions commands
 Source: https://upstash.com/docs/redis/commands/functions/overview
@@ -21628,9 +21851,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
 
-<Tab title="@upstash/redis">
+```bash
+COPY source-key destination-key
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -21640,9 +21871,9 @@ const result = await redis.copy("source-key", "destination-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -21652,9 +21883,9 @@ result = redis.copy("source-key", "destination-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -21664,9 +21895,9 @@ const result = await redis.copy("source-key", "destination-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -21678,9 +21909,9 @@ const result = await client.copy("source-key", "destination-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -21691,9 +21922,9 @@ result = client.copy("source-key", "destination-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -21720,9 +21951,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -21735,9 +21966,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -21753,9 +21984,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # DEL
 Source: https://upstash.com/docs/redis/commands/generic/del
@@ -21793,9 +22024,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+DEL my-key
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -21805,9 +22044,9 @@ const redis = Redis.fromEnv();
 await redis.del("key1", "key2");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -21817,9 +22056,9 @@ result = redis.delete("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -21829,9 +22068,9 @@ const result = await redis.del("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -21843,9 +22082,9 @@ const result = await client.del("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -21856,9 +22095,9 @@ result = client.delete("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -21885,9 +22124,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -21900,9 +22139,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -21918,9 +22157,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # DUMP
 Source: https://upstash.com/docs/redis/commands/generic/dump
@@ -21960,25 +22199,33 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+DUMP my-key
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 <Note>
   This command is not supported yet in `upstash_redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -21988,9 +22235,9 @@ const result = await redis.dump("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -22002,9 +22249,9 @@ const result = await client.dump("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -22015,9 +22262,9 @@ result = client.dump("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -22044,9 +22291,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -22059,9 +22306,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -22077,9 +22324,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # EXISTS
 Source: https://upstash.com/docs/redis/commands/generic/exists
@@ -22117,9 +22364,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+EXISTS my-key
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -22132,9 +22387,9 @@ const keys = await redis.exists("key1", "key2", "key3");
 console.log(keys) // 2
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -22144,9 +22399,9 @@ result = redis.exists("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -22156,9 +22411,9 @@ const result = await redis.exists("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -22170,9 +22425,9 @@ const result = await client.exists("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -22183,9 +22438,9 @@ result = client.exists("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -22212,9 +22467,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -22227,9 +22482,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -22245,9 +22500,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # EXPIRE
 Source: https://upstash.com/docs/redis/commands/generic/expire
@@ -22296,9 +22551,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+EXPIRE my-key 1000
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -22309,9 +22572,9 @@ await redis.set("mykey", "Hello");
 await redis.expire("mykey", 10);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -22321,9 +22584,9 @@ result = redis.expire("my-key", 1000)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -22333,9 +22596,9 @@ const result = await redis.expire("my-key", "1000");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -22347,9 +22610,9 @@ const result = await client.expire("my-key", 1000);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -22360,9 +22623,9 @@ result = client.expire("my-key", 1000)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -22390,9 +22653,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -22405,9 +22668,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -22423,9 +22686,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # EXPIREAT
 Source: https://upstash.com/docs/redis/commands/generic/expireat
@@ -22472,9 +22735,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+EXPIREAT my-key 1735689600
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -22486,9 +22757,9 @@ const tenSecondsFromNow = Math.floor(Date.now() / 1000) + 10;
 await redis.expireat("mykey", tenSecondsFromNow);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -22498,9 +22769,9 @@ result = redis.expireat("my-key", 1735689600)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -22510,9 +22781,9 @@ const result = await redis.expireat("my-key", "1735689600");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -22524,9 +22795,9 @@ const result = await client.expireAt("my-key", 1735689600);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -22537,9 +22808,9 @@ result = client.expireat("my-key", 1735689600)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -22567,9 +22838,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -22582,9 +22853,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -22600,9 +22871,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # EXPIRETIME
 Source: https://upstash.com/docs/redis/commands/generic/expiretime
@@ -22644,25 +22915,33 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+EXPIRETIME my-key
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 <Note>
   This command is not supported yet in `upstash_redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -22672,9 +22951,9 @@ const result = await redis.expiretime("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -22686,9 +22965,9 @@ const result = await client.expireTime("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -22699,9 +22978,9 @@ result = client.expiretime("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -22728,9 +23007,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -22743,9 +23022,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -22761,9 +23040,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # KEYS
 Source: https://upstash.com/docs/redis/commands/generic/keys
@@ -22808,9 +23087,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+KEYS *
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -22820,9 +23107,9 @@ const redis = Redis.fromEnv();
 const keys = await redis.keys("prefix*");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -22832,9 +23119,9 @@ result = redis.keys("*")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -22844,9 +23131,9 @@ const result = await redis.keys("*");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -22858,9 +23145,9 @@ const result = await client.keys("*");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -22871,9 +23158,9 @@ result = client.keys("*")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -22900,9 +23187,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -22915,9 +23202,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -22933,9 +23220,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # MEMORY USAGE
 Source: https://upstash.com/docs/redis/commands/generic/memory-usage
@@ -22981,25 +23268,33 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+MEMORY USAGE my-key SAMPLES 10
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 <Note>
   This command is not supported yet in `upstash_redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -23009,9 +23304,9 @@ const result = await redis.memory("USAGE", "my-key", "SAMPLES", "10");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -23023,9 +23318,9 @@ const result = await client.memoryUsage("my-key", { SAMPLES: 10 });
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -23036,9 +23331,9 @@ result = client.memory_usage("my-key", samples=10)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -23065,9 +23360,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -23080,9 +23375,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -23101,9 +23396,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # Generic commands
 Source: https://upstash.com/docs/redis/commands/generic/overview
@@ -23172,9 +23467,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+PERSIST my-key
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -23184,9 +23487,9 @@ const redis = Redis.fromEnv();
 await redis.persist(key);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -23196,9 +23499,9 @@ result = redis.persist("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -23208,9 +23511,9 @@ const result = await redis.persist("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -23222,9 +23525,9 @@ const result = await client.persist("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -23235,9 +23538,9 @@ result = client.persist("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -23264,9 +23567,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -23279,9 +23582,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -23297,9 +23600,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # PEXPIRE
 Source: https://upstash.com/docs/redis/commands/generic/pexpire
@@ -23346,9 +23649,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+PEXPIRE my-key 1000
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -23358,9 +23669,9 @@ const redis = Redis.fromEnv();
 await redis.pexpire(key, 60_000); // 1 minute
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -23370,9 +23681,9 @@ result = redis.pexpire("my-key", 1000)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -23382,9 +23693,9 @@ const result = await redis.pexpire("my-key", "1000");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -23396,9 +23707,9 @@ const result = await client.pExpire("my-key", 1000);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -23409,9 +23720,9 @@ result = client.pexpire("my-key", 1000)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -23439,9 +23750,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -23454,9 +23765,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -23472,9 +23783,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # PEXPIREAT
 Source: https://upstash.com/docs/redis/commands/generic/pexpireat
@@ -23521,9 +23832,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+PEXPIREAT my-key 1735689600
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -23535,9 +23854,9 @@ const tenMinutesFromNow = Date.now() + 10 * 60 * 1000;
 await redis.pexpireat("mykey", tenMinutesFromNow);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -23547,9 +23866,9 @@ result = redis.pexpireat("my-key", 1735689600)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -23559,9 +23878,9 @@ const result = await redis.pexpireat("my-key", "1735689600");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -23573,9 +23892,9 @@ const result = await client.pExpireAt("my-key", 1735689600);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -23586,9 +23905,9 @@ result = client.pexpireat("my-key", 1735689600)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -23616,9 +23935,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -23631,9 +23950,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -23649,9 +23968,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # PEXPIRETIME
 Source: https://upstash.com/docs/redis/commands/generic/pexpiretime
@@ -23693,25 +24012,33 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+PEXPIRETIME my-key
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 <Note>
   This command is not supported yet in `upstash_redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -23721,9 +24048,9 @@ const result = await redis.pexpiretime("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -23735,9 +24062,9 @@ const result = await client.pExpireTime("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -23748,9 +24075,9 @@ result = client.pexpiretime("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -23777,9 +24104,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -23792,9 +24119,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -23810,9 +24137,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # PTTL
 Source: https://upstash.com/docs/redis/commands/generic/pttl
@@ -23854,9 +24181,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+PTTL my-key
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -23866,9 +24201,9 @@ const redis = Redis.fromEnv();
 const millis = await redis.pttl(key);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -23878,9 +24213,9 @@ result = redis.pttl("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -23890,9 +24225,9 @@ const result = await redis.pttl("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -23904,9 +24239,9 @@ const result = await client.pTTL("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -23917,9 +24252,9 @@ result = client.pttl("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -23946,9 +24281,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -23961,9 +24296,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -23979,9 +24314,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # RANDOMKEY
 Source: https://upstash.com/docs/redis/commands/generic/randomkey
@@ -24017,9 +24352,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+RANDOMKEY
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -24029,9 +24372,9 @@ const redis = Redis.fromEnv();
 const key = await redis.randomkey();
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -24041,9 +24384,9 @@ result = redis.randomkey()
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -24053,9 +24396,9 @@ const result = await redis.randomkey();
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -24067,9 +24410,9 @@ const result = await client.randomKey();
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -24080,9 +24423,9 @@ result = client.randomkey()
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -24109,9 +24452,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -24124,9 +24467,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -24142,9 +24485,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # RENAME
 Source: https://upstash.com/docs/redis/commands/generic/rename
@@ -24185,9 +24528,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+RENAME old-key new-key
+```
 
-<Tab title="@upstash/redis">
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -24197,9 +24548,9 @@ const redis = Redis.fromEnv();
 await redis.rename("old", "new");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -24209,9 +24560,9 @@ result = redis.rename("old-key", "new-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -24221,9 +24572,9 @@ const result = await redis.rename("old-key", "new-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -24235,9 +24586,9 @@ const result = await client.rename("old-key", "new-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -24248,9 +24599,9 @@ result = client.rename("old-key", "new-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -24277,9 +24628,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -24292,9 +24643,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -24310,9 +24661,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # RENAMENX
 Source: https://upstash.com/docs/redis/commands/generic/renamenx
@@ -24351,9 +24702,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+RENAMENX old-key new-key
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -24363,9 +24722,9 @@ const redis = Redis.fromEnv();
 const renamed = await redis.renamenx("old", "new");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -24375,9 +24734,9 @@ result = redis.renamenx("old-key", "new-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -24387,9 +24746,9 @@ const result = await redis.renamenx("old-key", "new-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -24401,9 +24760,9 @@ const result = await client.renameNX("old-key", "new-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -24414,9 +24773,9 @@ result = client.renamenx("old-key", "new-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -24443,9 +24802,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -24458,9 +24817,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -24476,9 +24835,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # RESTORE
 Source: https://upstash.com/docs/redis/commands/generic/restore
@@ -24532,25 +24891,33 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
 
-<Tab title="@upstash/redis">
+```bash
+RESTORE my-key 1 serialized-value
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 <Note>
   This command is not supported yet in `upstash_redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -24560,9 +24927,9 @@ const result = await redis.restore("my-key", "1", "serialized-value");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -24574,9 +24941,9 @@ const result = await client.restore("my-key", 1, "serialized-value");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -24587,9 +24954,9 @@ result = client.restore("my-key", 1, "serialized-value")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -24617,9 +24984,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -24632,9 +24999,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -24652,9 +25019,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # SCAN
 Source: https://upstash.com/docs/redis/commands/generic/scan
@@ -24704,9 +25071,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+SCAN 0
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -24716,9 +25091,9 @@ const redis = Redis.fromEnv();
 const [cursor, keys] = await redis.scan(0, { match: "*" });
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -24728,9 +25103,9 @@ result = redis.scan(0)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -24740,9 +25115,9 @@ const result = await redis.scan("0");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -24754,9 +25129,9 @@ const result = await client.scan("0");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -24767,9 +25142,9 @@ result = client.scan(0)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -24796,9 +25171,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -24811,27 +25186,29 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
+use redis::TypedCommands;
+
 fn main() -> redis::RedisResult<()> {
     let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
     let client = redis::Client::open(url)?;
     let mut connection = client.get_connection()?;
 
-    let mut command = redis::cmd("SCAN");
-    command.arg("0");
-    let result: redis::Value = command.query(&mut connection)?;
-    println!("{result:?}");
+    let iter: redis::Iter<String> = connection.scan()?;
+    for key in iter {
+        println!("{key}");
+    }
     Ok(())
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # TOUCH
 Source: https://upstash.com/docs/redis/commands/generic/touch
@@ -24869,9 +25246,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+TOUCH my-key
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -24881,9 +25266,9 @@ const redis = Redis.fromEnv();
 await redis.touch("key1", "key2", "key3");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -24893,9 +25278,9 @@ result = redis.touch("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -24905,9 +25290,9 @@ const result = await redis.touch("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -24919,9 +25304,9 @@ const result = await client.touch("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -24932,9 +25317,9 @@ result = client.touch("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -24961,9 +25346,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -24976,9 +25361,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -24994,9 +25379,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # TTL
 Source: https://upstash.com/docs/redis/commands/generic/ttl
@@ -25038,9 +25423,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+TTL my-key
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -25050,9 +25443,9 @@ const redis = Redis.fromEnv();
 const seconds = await redis.ttl(key);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -25062,9 +25455,9 @@ result = redis.ttl("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -25074,9 +25467,9 @@ const result = await redis.ttl("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -25088,9 +25481,9 @@ const result = await client.ttl("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -25101,9 +25494,9 @@ result = client.ttl("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -25130,9 +25523,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -25145,9 +25538,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -25163,9 +25556,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # TYPE
 Source: https://upstash.com/docs/redis/commands/generic/type
@@ -25203,9 +25596,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
 
-<Tab title="@upstash/redis">
+```bash
+TYPE my-key
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -25217,9 +25618,9 @@ const t = await redis.type("key");
 console.log(t) // "string"
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -25229,9 +25630,9 @@ result = redis.type("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -25241,9 +25642,9 @@ const result = await redis.type("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -25255,9 +25656,9 @@ const result = await client.type("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -25268,9 +25669,9 @@ result = client.type("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -25297,9 +25698,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -25312,9 +25713,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -25330,9 +25731,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # UNLINK
 Source: https://upstash.com/docs/redis/commands/generic/unlink
@@ -25370,9 +25771,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+UNLINK my-key
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -25382,9 +25791,9 @@ const redis = Redis.fromEnv();
 await redis.unlink("key1", "key2");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -25394,9 +25803,9 @@ result = redis.unlink("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -25406,9 +25815,9 @@ const result = await redis.unlink("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -25420,9 +25829,9 @@ const result = await client.unlink("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -25433,9 +25842,9 @@ result = client.unlink("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -25462,9 +25871,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -25477,9 +25886,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -25495,9 +25904,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # WAIT
 Source: https://upstash.com/docs/redis/commands/generic/wait
@@ -25545,25 +25954,33 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+WAIT 1 1000
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 <Note>
   This command is not supported yet in `upstash_redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -25573,9 +25990,9 @@ const result = await redis.wait("1", "1000");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -25587,9 +26004,9 @@ const result = await client.wait(1, 1000);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -25600,9 +26017,9 @@ result = client.wait("1", "1000")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -25630,9 +26047,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -25645,9 +26062,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -25664,9 +26081,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # WAITAOF
 Source: https://upstash.com/docs/redis/commands/generic/waitaof
@@ -25713,25 +26130,33 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+WAITAOF 1 1 1000
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 <Note>
   This command is not supported yet in `upstash_redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -25741,9 +26166,9 @@ const result = await redis.call("WAITAOF", "1", "1", "1000");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -25755,9 +26180,9 @@ const result = await client.sendCommand(["WAITAOF", "1", "1", "1000"]);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -25768,9 +26193,9 @@ result = client.waitaof("1", "1", "1000")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -25798,9 +26223,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -25813,9 +26238,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -25833,9 +26258,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # GEOADD
 Source: https://upstash.com/docs/redis/commands/geo/geoadd
@@ -25886,9 +26311,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+GEOADD my-key 29.0 41.0 member
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -25902,9 +26335,9 @@ const result = await redis.geoadd("my-key", {
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -25914,9 +26347,9 @@ result = redis.geoadd("my-key", (29.0, 41.0, "member"))
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -25926,9 +26359,9 @@ const result = await redis.geoadd("my-key", "29.0", "41.0", "member");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -25940,9 +26373,9 @@ const result = await client.geoAdd("my-key", { longitude: 29, latitude: 41, memb
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -25953,9 +26386,9 @@ result = client.geoadd("my-key", (29.0, 41.0, "member"))
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -25982,9 +26415,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -25997,30 +26430,27 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
+use redis::TypedCommands;
+
 fn main() -> redis::RedisResult<()> {
     let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
     let client = redis::Client::open(url)?;
     let mut connection = client.get_connection()?;
 
-    let mut command = redis::cmd("GEOADD");
-    command.arg("my-key");
-    command.arg("29.0");
-    command.arg("41.0");
-    command.arg("member");
-    let result: redis::Value = command.query(&mut connection)?;
+    let result = connection.geo_add("my-key", (29.0, 41.0, "member"))?;
     println!("{result:?}");
     Ok(())
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # GEODIST
 Source: https://upstash.com/docs/redis/commands/geo/geodist
@@ -26065,9 +26495,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+GEODIST my-key member1 member2
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -26077,9 +26515,9 @@ const result = await redis.geodist("my-key", "member1", "member2");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -26089,9 +26527,9 @@ result = redis.geodist("my-key", "member1", "member2")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -26101,9 +26539,9 @@ const result = await redis.geodist("my-key", "member1", "member2");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -26115,9 +26553,9 @@ const result = await client.geoDist("my-key", "member1", "member2");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -26128,9 +26566,9 @@ result = client.geodist("my-key", "member1", "member2")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -26157,9 +26595,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -26172,29 +26610,28 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
+use redis::geo::Unit;
+use redis::TypedCommands;
+
 fn main() -> redis::RedisResult<()> {
     let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
     let client = redis::Client::open(url)?;
     let mut connection = client.get_connection()?;
 
-    let mut command = redis::cmd("GEODIST");
-    command.arg("my-key");
-    command.arg("member1");
-    command.arg("member2");
-    let result: redis::Value = command.query(&mut connection)?;
+    let result = connection.geo_dist("my-key", "member1", "member2", Unit::Meters)?;
     println!("{result:?}");
     Ok(())
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # GEOHASH
 Source: https://upstash.com/docs/redis/commands/geo/geohash
@@ -26233,9 +26670,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+GEOHASH my-key member
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -26245,9 +26690,9 @@ const result = await redis.geohash("my-key", "member");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -26257,9 +26702,9 @@ result = redis.geohash("my-key", "member")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -26269,9 +26714,9 @@ const result = await redis.geohash("my-key", "member");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -26283,9 +26728,9 @@ const result = await client.geoHash("my-key", "member");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -26296,9 +26741,9 @@ result = client.geohash("my-key", "member")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -26325,9 +26770,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -26340,27 +26785,27 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
+use redis::TypedCommands;
+
 fn main() -> redis::RedisResult<()> {
     let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
     let client = redis::Client::open(url)?;
     let mut connection = client.get_connection()?;
 
-    let mut command = redis::cmd("GEOHASH");
-    command.arg("my-key");
-    let result: redis::Value = command.query(&mut connection)?;
+    let result = connection.geo_hash("my-key", "member")?;
     println!("{result:?}");
     Ok(())
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # GEOPOS
 Source: https://upstash.com/docs/redis/commands/geo/geopos
@@ -26399,9 +26844,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
 
-<Tab title="@upstash/redis">
+```bash
+GEOPOS my-key member
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -26411,9 +26864,9 @@ const result = await redis.geopos("my-key", "member");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -26423,9 +26876,9 @@ result = redis.geopos("my-key", "member")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -26435,9 +26888,9 @@ const result = await redis.geopos("my-key", "member");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -26449,9 +26902,9 @@ const result = await client.geoPos("my-key", "member");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -26462,9 +26915,9 @@ result = client.geopos("my-key", "member")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -26491,9 +26944,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -26506,33 +26959,33 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
+use redis::TypedCommands;
+
 fn main() -> redis::RedisResult<()> {
     let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
     let client = redis::Client::open(url)?;
     let mut connection = client.get_connection()?;
 
-    let mut command = redis::cmd("GEOPOS");
-    command.arg("my-key");
-    let result: redis::Value = command.query(&mut connection)?;
+    let result = connection.geo_pos("my-key", "member")?;
     println!("{result:?}");
     Ok(())
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # GEORADIUS
 Source: https://upstash.com/docs/redis/commands/geo/georadius
 
 <Warning>
-  Prefer [`GEOSEARCH`](/docs/redis/commands/geo/geosearch) with `FROMLONLAT` and `BYRADIUS` in new code: `GEOSEARCH <key> FROMLONLAT <longitude> <latitude> BYRADIUS <radius> (m | km | ft | mi)`. In place of `STORE` and `STOREDIST`, use [`GEOSEARCHSTORE`](/docs/redis/commands/geo/geosearchstore) with the same query. `GEORADIUS` is deprecated in Redis but still supported by Upstash.
+  Prefer [`GEOSEARCH`](/docs/redis/commands/geo/geosearch) with `FROMLONLAT` and `BYRADIUS` in new code: `GEOSEARCH <key> FROMLONLAT <longitude> <latitude> BYRADIUS <radius> (m | km | ft | mi)`. In place of `STORE` and `STOREDIST`, use [`GEOSEARCHSTORE`](/docs/redis/commands/geo/geosearchstore) with the same query.
 </Warning>
 
 Use `GEORADIUS` to find the members of a geospatial index that lie within a given radius of a longitude and latitude point.
@@ -26588,17 +27041,25 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+GEORADIUS my-key 29.0 41.0 1.5 m
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -26608,9 +27069,9 @@ result = redis.georadius("my-key", 29.0, 41.0, 1.5, "M")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -26620,9 +27081,9 @@ const result = await redis.georadius("my-key", "29.0", "41.0", "1.5", "m");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -26634,9 +27095,9 @@ const result = await client.geoRadius("my-key", { longitude: 29, latitude: 41 },
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -26647,9 +27108,9 @@ result = client.georadius("my-key", 29.0, 41.0, 1.5, "m")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -26676,9 +27137,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -26691,37 +27152,41 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
+use redis::geo::{RadiusOptions, Unit};
+use redis::TypedCommands;
+
 fn main() -> redis::RedisResult<()> {
     let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
     let client = redis::Client::open(url)?;
     let mut connection = client.get_connection()?;
 
-    let mut command = redis::cmd("GEORADIUS");
-    command.arg("my-key");
-    command.arg("29.0");
-    command.arg("41.0");
-    command.arg("1.5");
-    command.arg("m");
-    let result: redis::Value = command.query(&mut connection)?;
+    let result = connection.geo_radius(
+        "my-key",
+        29.0,
+        41.0,
+        1.5,
+        Unit::Meters,
+        RadiusOptions::default(),
+    )?;
     println!("{result:?}");
     Ok(())
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # GEORADIUS_RO
 Source: https://upstash.com/docs/redis/commands/geo/georadius-ro
 
 <Warning>
-  Prefer [`GEOSEARCH`](/docs/redis/commands/geo/geosearch) with `FROMLONLAT` and `BYRADIUS` in new code: `GEOSEARCH <key> FROMLONLAT <longitude> <latitude> BYRADIUS <radius> (m | km | ft | mi)`. `GEORADIUS_RO` is deprecated in Redis but still supported by Upstash.
+  Prefer [`GEOSEARCH`](/docs/redis/commands/geo/geosearch) with `FROMLONLAT` and `BYRADIUS` in new code: `GEOSEARCH <key> FROMLONLAT <longitude> <latitude> BYRADIUS <radius> (m | km | ft | mi)`.
 </Warning>
 
 Use `GEORADIUS_RO` to find members within a radius of a point. It is the read-only form of [`GEORADIUS`](/docs/redis/commands/geo/georadius).
@@ -26773,17 +27238,25 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+GEORADIUS_RO my-key 29.0 41.0 1.5 m
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -26793,9 +27266,9 @@ result = redis.georadius_ro("my-key", 29.0, 41.0, 1.5, "M")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -26805,9 +27278,9 @@ const result = await redis.georadius_ro("my-key", "29.0", "41.0", "1.5", "m");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -26819,9 +27292,9 @@ const result = await client.geoRadiusRo("my-key", { longitude: 29, latitude: 41
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -26832,9 +27305,9 @@ result = client.execute_command("GEORADIUS_RO", "my-key", "29.0", "41.0", "1.5",
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -26861,9 +27334,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -26876,9 +27349,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -26898,15 +27371,15 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # GEORADIUSBYMEMBER
 Source: https://upstash.com/docs/redis/commands/geo/georadiusbymember
 
 <Warning>
-  Prefer [`GEOSEARCH`](/docs/redis/commands/geo/geosearch) with `FROMMEMBER` and `BYRADIUS` in new code: `GEOSEARCH <key> FROMMEMBER <member> BYRADIUS <radius> (m | km | ft | mi)`. In place of `STORE` and `STOREDIST`, use [`GEOSEARCHSTORE`](/docs/redis/commands/geo/geosearchstore) with the same query. `GEORADIUSBYMEMBER` is deprecated in Redis but still supported by Upstash.
+  Prefer [`GEOSEARCH`](/docs/redis/commands/geo/geosearch) with `FROMMEMBER` and `BYRADIUS` in new code: `GEOSEARCH <key> FROMMEMBER <member> BYRADIUS <radius> (m | km | ft | mi)`. In place of `STORE` and `STOREDIST`, use [`GEOSEARCHSTORE`](/docs/redis/commands/geo/geosearchstore) with the same query.
 </Warning>
 
 Use `GEORADIUSBYMEMBER` to find the members of a geospatial index that lie within a given radius of another member.
@@ -26959,17 +27432,25 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+GEORADIUSBYMEMBER my-key member 1.5 m
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -26979,9 +27460,9 @@ result = redis.georadiusbymember("my-key", "member", 1.5, "M")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -26991,9 +27472,9 @@ const result = await redis.georadiusbymember("my-key", "member", "1.5", "m");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -27005,9 +27486,9 @@ const result = await client.geoRadiusByMember("my-key", "member", 1.5, "m");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -27018,9 +27499,9 @@ result = client.georadiusbymember("my-key", "member", 1.5, "m")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -27047,9 +27528,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -27062,36 +27543,40 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
+use redis::geo::{RadiusOptions, Unit};
+use redis::TypedCommands;
+
 fn main() -> redis::RedisResult<()> {
     let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
     let client = redis::Client::open(url)?;
     let mut connection = client.get_connection()?;
 
-    let mut command = redis::cmd("GEORADIUSBYMEMBER");
-    command.arg("my-key");
-    command.arg("member");
-    command.arg("1.5");
-    command.arg("m");
-    let result: redis::Value = command.query(&mut connection)?;
+    let result = connection.geo_radius_by_member(
+        "my-key",
+        "member",
+        1.5,
+        Unit::Meters,
+        RadiusOptions::default(),
+    )?;
     println!("{result:?}");
     Ok(())
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # GEORADIUSBYMEMBER_RO
 Source: https://upstash.com/docs/redis/commands/geo/georadiusbymember-ro
 
 <Warning>
-  Prefer [`GEOSEARCH`](/docs/redis/commands/geo/geosearch) with `FROMMEMBER` and `BYRADIUS` in new code: `GEOSEARCH <key> FROMMEMBER <member> BYRADIUS <radius> (m | km | ft | mi)`. `GEORADIUSBYMEMBER_RO` is deprecated in Redis but still supported by Upstash.
+  Prefer [`GEOSEARCH`](/docs/redis/commands/geo/geosearch) with `FROMMEMBER` and `BYRADIUS` in new code: `GEOSEARCH <key> FROMMEMBER <member> BYRADIUS <radius> (m | km | ft | mi)`.
 </Warning>
 
 Use `GEORADIUSBYMEMBER_RO` to find members within a radius of another member. It is the read-only form of [`GEORADIUSBYMEMBER`](/docs/redis/commands/geo/georadiusbymember).
@@ -27140,17 +27625,25 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+GEORADIUSBYMEMBER_RO my-key member 1.5 m
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -27160,9 +27653,9 @@ result = redis.georadiusbymember_ro("my-key", "member", 1.5, "M")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -27172,9 +27665,9 @@ const result = await redis.georadiusbymember_ro("my-key", "member", "1.5", "m");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -27186,9 +27679,9 @@ const result = await client.geoRadiusByMemberRo("my-key", "member", 1.5, "m");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -27199,9 +27692,9 @@ result = client.execute_command("GEORADIUSBYMEMBER_RO", "my-key", "member", "1.5
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -27228,9 +27721,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -27243,9 +27736,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -27264,9 +27757,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # GEOSEARCH
 Source: https://upstash.com/docs/redis/commands/geo/geosearch
@@ -27323,9 +27816,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+GEOSEARCH my-key FROMMEMBER member BYRADIUS 1.5 m
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -27340,9 +27841,9 @@ const result = await redis.geosearch(
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -27352,9 +27853,9 @@ result = redis.geosearch("my-key", member="member", radius=1.5, unit="M")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -27364,9 +27865,9 @@ const result = await redis.geosearch("my-key", "FROMMEMBER", "member", "BYRADIUS
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -27378,9 +27879,9 @@ const result = await client.geoSearch("my-key", "member", { radius: 1.5, unit: "
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -27391,9 +27892,9 @@ result = client.geosearch("my-key", member="member", radius=1.5, unit="m")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -27420,9 +27921,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -27435,9 +27936,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -27456,9 +27957,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # GEOSEARCHSTORE
 Source: https://upstash.com/docs/redis/commands/geo/geosearchstore
@@ -27510,9 +28011,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
 
-<Tab title="@upstash/redis">
+```bash
+GEOSEARCHSTORE destination-key source-key FROMMEMBER member BYRADIUS 1.5 m
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -27528,9 +28037,9 @@ const result = await redis.geosearchstore(
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -27540,9 +28049,9 @@ result = redis.geosearchstore("destination-key", "source-key", member="member",
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -27552,9 +28061,9 @@ const result = await redis.geosearchstore("destination-key", "source-key", "FROM
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -27566,9 +28075,9 @@ const result = await client.geoSearchStore("destination-key", "source-key", "mem
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -27579,9 +28088,9 @@ result = client.geosearchstore("destination-key", "source-key", member="member",
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -27608,9 +28117,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -27623,9 +28132,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -27645,9 +28154,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # Geo commands
 Source: https://upstash.com/docs/redis/commands/geo/overview
@@ -27702,9 +28211,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+HDEL my-key field
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -27715,9 +28232,9 @@ await redis.hdel(key, 'field1', 'field2');
 // returns 5
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -27727,9 +28244,9 @@ result = redis.hdel("my-key", "field")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -27739,9 +28256,9 @@ const result = await redis.hdel("my-key", "field");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -27753,9 +28270,9 @@ const result = await client.hDel("my-key", "field");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -27766,9 +28283,9 @@ result = client.hdel("my-key", "field")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -27795,9 +28312,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -27810,9 +28327,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -27828,9 +28345,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # HEXISTS
 Source: https://upstash.com/docs/redis/commands/hash/hexists
@@ -27869,9 +28386,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+HEXISTS my-key field
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -27884,9 +28409,9 @@ const exists = await redis.hexists("key", "field");
 console.log(exists); // 1
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -27896,9 +28421,9 @@ result = redis.hexists("my-key", "field")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -27908,9 +28433,9 @@ const result = await redis.hexists("my-key", "field");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -27922,9 +28447,9 @@ const result = await client.hExists("my-key", "field");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -27935,9 +28460,9 @@ result = client.hexists("my-key", "field")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -27964,9 +28489,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -27979,9 +28504,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -27997,9 +28522,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # HEXPIRE
 Source: https://upstash.com/docs/redis/commands/hash/hexpire
@@ -28051,9 +28576,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+HEXPIRE my-key 1000 FIELDS 1 field
+```
 
-<Tab title="@upstash/redis">
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -28066,9 +28599,9 @@ const expirationSet = await redis.hexpire("my-key", "my-field", 1);
 console.log(expirationSet); // 1
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -28078,9 +28611,9 @@ result = redis.hexpire("my-key", "field", 1000)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -28090,9 +28623,9 @@ const result = await redis.hexpire("my-key", "1000", "FIELDS", "1", "field");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -28104,9 +28637,9 @@ const result = await client.hExpire("my-key", "field", 1000);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -28117,9 +28650,9 @@ result = client.hexpire("my-key", 1000, "field")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -28146,9 +28679,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -28161,9 +28694,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -28179,9 +28712,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # HEXPIREAT
 Source: https://upstash.com/docs/redis/commands/hash/hexpireat
@@ -28233,9 +28766,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+HEXPIREAT my-key 1735689600 FIELDS 1 field
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -28248,9 +28789,9 @@ const expirationSet = await redis.hexpireat("my-key", "my-field", Math.floor(Dat
 console.log(expirationSet); // [1]
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -28260,9 +28801,9 @@ result = redis.hexpireat("my-key", "field", 1735689600)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -28272,9 +28813,9 @@ const result = await redis.hexpireat("my-key", "1735689600", "FIELDS", "1", "fie
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -28286,9 +28827,9 @@ const result = await client.hExpireAt("my-key", "field", 1735689600);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -28299,9 +28840,9 @@ result = client.hexpireat("my-key", 1735689600, "field")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -28328,9 +28869,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -28343,9 +28884,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -28361,9 +28902,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # HEXPIRETIME
 Source: https://upstash.com/docs/redis/commands/hash/hexpiretime
@@ -28406,9 +28947,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+HEXPIRETIME my-key FIELDS 1 field
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -28422,9 +28971,9 @@ const expireTime = await redis.hexpiretime("my-key", "my-field");
 console.log(expireTime); // e.g., [1697059200]
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -28434,9 +28983,9 @@ result = redis.hexpiretime("my-key", "field")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -28446,9 +28995,9 @@ const result = await redis.hexpiretime("my-key", "FIELDS", "1", "field");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -28460,9 +29009,9 @@ const result = await client.hExpireTime("my-key", "field");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -28473,9 +29022,9 @@ result = client.hexpiretime("my-key", "field")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -28502,9 +29051,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -28516,9 +29065,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -28534,9 +29083,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # HGET
 Source: https://upstash.com/docs/redis/commands/hash/hget
@@ -28575,9 +29124,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
 
-<Tab title="@upstash/redis">
+```bash
+HGET my-key field
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -28589,9 +29146,9 @@ const field = await redis.hget("key", "field");
 console.log(field); // "value"
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -28601,9 +29158,9 @@ result = redis.hget("my-key", "field")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -28613,9 +29170,9 @@ const result = await redis.hget("my-key", "field");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -28627,9 +29184,9 @@ const result = await client.hGet("my-key", "field");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -28640,9 +29197,9 @@ result = client.hget("my-key", "field")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -28669,9 +29226,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -28684,9 +29241,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -28702,9 +29259,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # HGETALL
 Source: https://upstash.com/docs/redis/commands/hash/hgetall
@@ -28748,9 +29305,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+HGETALL my-key
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -28765,9 +29330,9 @@ const hash = await redis.hgetall("key");
 console.log(hash); // { field1: "value1", field2: "value2" }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -28777,9 +29342,9 @@ result = redis.hgetall("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -28789,9 +29354,9 @@ const result = await redis.hgetall("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -28803,9 +29368,9 @@ const result = await client.hGetAll("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -28816,9 +29381,9 @@ result = client.hgetall("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -28845,9 +29410,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -28860,9 +29425,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -28878,9 +29443,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # HGETDEL
 Source: https://upstash.com/docs/redis/commands/hash/hgetdel
@@ -28921,9 +29486,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+HGETDEL my-key FIELDS 1 field
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -28942,9 +29515,9 @@ const name = await redis.hget("user:123", "name");
 console.log(name); // null
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -28954,9 +29527,9 @@ result = redis.hgetdel("my-key", "field")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -28966,9 +29539,9 @@ const result = await redis.hgetdel("my-key", "FIELDS", "1", "field");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -28980,9 +29553,9 @@ const result = await client.hGetDel("my-key", "field");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -28993,9 +29566,9 @@ result = client.hgetdel("my-key", "field")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -29022,9 +29595,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -29037,9 +29610,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -29055,9 +29628,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # HGETEX
 Source: https://upstash.com/docs/redis/commands/hash/hgetex
@@ -29102,9 +29675,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+HGETEX my-key FIELDS 1 field
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -29118,9 +29699,9 @@ const result = await redis.hgetex("user:123", { ex: 60 }, "name", "email");
 console.log(result); // { name: "John", email: "john@example.com" }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -29130,9 +29711,9 @@ result = redis.hgetex("my-key", "field")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -29142,9 +29723,9 @@ const result = await redis.hgetex("my-key", "FIELDS", "1", "field");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -29156,9 +29737,9 @@ const result = await client.hGetEx("my-key", "field");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -29169,9 +29750,9 @@ result = client.hgetex("my-key", "field")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -29198,9 +29779,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -29213,9 +29794,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -29231,9 +29812,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # HINCRBY
 Source: https://upstash.com/docs/redis/commands/hash/hincrby
@@ -29275,9 +29856,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+HINCRBY my-key field 1
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -29291,9 +29880,9 @@ const after = await redis.hincrby("key", "field", 2);
 console.log(after); // 22
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -29303,9 +29892,9 @@ result = redis.hincrby("my-key", "field", 1)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -29315,9 +29904,9 @@ const result = await redis.hincrby("my-key", "field", "1");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -29329,9 +29918,9 @@ const result = await client.hIncrBy("my-key", "field", 1);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -29342,9 +29931,9 @@ result = client.hincrby("my-key", "field", 1)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -29371,9 +29960,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -29386,9 +29975,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -29404,9 +29993,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # HINCRBYFLOAT
 Source: https://upstash.com/docs/redis/commands/hash/hincrbyfloat
@@ -29452,9 +30041,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+HINCRBYFLOAT my-key field 1.5
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -29468,9 +30065,9 @@ const after = await redis.hincrby("key", "field", 2.5);
 console.log(after); // 22.5
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -29480,9 +30077,9 @@ result = redis.hincrbyfloat("my-key", "field", 1.5)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -29492,9 +30089,9 @@ const result = await redis.hincrbyfloat("my-key", "field", "1.5");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -29506,9 +30103,9 @@ const result = await client.hIncrByFloat("my-key", "field", 1.5);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -29519,9 +30116,9 @@ result = client.hincrbyfloat("my-key", "field", 1.5)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -29548,9 +30145,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -29563,9 +30160,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -29581,9 +30178,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # HKEYS
 Source: https://upstash.com/docs/redis/commands/hash/hkeys
@@ -29621,9 +30218,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+HKEYS my-key
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -29638,9 +30243,9 @@ const fields = await redis.hkeys("key");
 console.log(fields); // ["id", "username"]
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -29650,9 +30255,9 @@ result = redis.hkeys("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -29662,9 +30267,9 @@ const result = await redis.hkeys("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -29676,9 +30281,9 @@ const result = await client.hKeys("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -29689,9 +30294,9 @@ result = client.hkeys("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -29718,9 +30323,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -29733,9 +30338,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -29751,9 +30356,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # HLEN
 Source: https://upstash.com/docs/redis/commands/hash/hlen
@@ -29791,9 +30396,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+HLEN my-key
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -29808,9 +30421,9 @@ const fields = await redis.hlen("key");
 console.log(fields); // 2
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -29820,9 +30433,9 @@ result = redis.hlen("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -29832,9 +30445,9 @@ const result = await redis.hlen("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -29846,9 +30459,9 @@ const result = await client.hLen("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -29859,9 +30472,9 @@ result = client.hlen("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -29888,9 +30501,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -29903,9 +30516,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -29921,9 +30534,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # HMGET
 Source: https://upstash.com/docs/redis/commands/hash/hmget
@@ -29964,9 +30577,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+HMGET my-key field
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -29982,9 +30603,9 @@ const fields = await redis.hmget("key", "username", "name");
 console.log(fields); // { username: "chronark", name: "andreas" }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -29994,9 +30615,9 @@ result = redis.hmget("my-key", "field")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -30006,9 +30627,9 @@ const result = await redis.hmget("my-key", "field");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -30020,9 +30641,9 @@ const result = await client.hmGet("my-key", "field");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -30033,9 +30654,9 @@ result = client.hmget("my-key", ["field"])
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -30062,9 +30683,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -30077,9 +30698,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -30095,15 +30716,15 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # HMSET
 Source: https://upstash.com/docs/redis/commands/hash/hmset
 
 <Warning>
-  Prefer [`HSET`](/docs/redis/commands/hash/hset) with multiple field-value pairs in new code: `HSET <key> <field> <value> [<field> <value> ...]`. `HMSET` is deprecated in Redis but still supported by Upstash.
+  Prefer [`HSET`](/docs/redis/commands/hash/hset) with multiple field-value pairs in new code: `HSET <key> <field> <value> [<field> <value> ...]`.
 </Warning>
 
 Use `HMSET` to set several field and value pairs of a hash in one call, creating the key if it does not exist.
@@ -30140,9 +30761,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+HMSET my-key field value
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -30152,9 +30781,9 @@ const result = await redis.hmset("my-key", { field: "value" });
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -30164,9 +30793,9 @@ result = redis.hmset("my-key", {"field": "value"})
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -30176,9 +30805,9 @@ const result = await redis.hmset("my-key", "field", "value");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -30190,9 +30819,9 @@ const result = await client.hSet("my-key", { field: "value" });
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -30203,9 +30832,9 @@ result = client.hset("my-key", mapping={"field": "value"})
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -30232,9 +30861,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -30247,9 +30876,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -30265,9 +30894,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # HPERSIST
 Source: https://upstash.com/docs/redis/commands/hash/hpersist
@@ -30308,9 +30937,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+HPERSIST my-key FIELDS 1 field
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -30325,9 +30962,9 @@ const expirationRemoved = await redis.hpersist("my-key", "my-field");
 console.log(expirationRemoved); // [1]
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -30337,9 +30974,9 @@ result = redis.hpersist("my-key", "field")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -30349,9 +30986,9 @@ const result = await redis.hpersist("my-key", "FIELDS", "1", "field");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -30363,9 +31000,9 @@ const result = await client.hPersist("my-key", "field");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -30376,9 +31013,9 @@ result = client.hpersist("my-key", "field")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -30405,9 +31042,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -30420,9 +31057,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -30438,9 +31075,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # HPEXPIRE
 Source: https://upstash.com/docs/redis/commands/hash/hpexpire
@@ -30490,9 +31127,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+HPEXPIRE my-key 1000 FIELDS 1 field
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -30505,9 +31150,9 @@ const expirationSet = await redis.hpexpire("my-key", "my-field", 1000);
 console.log(expirationSet); // [1]
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -30517,9 +31162,9 @@ result = redis.hpexpire("my-key", "field", 1000)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -30529,9 +31174,9 @@ const result = await redis.hpexpire("my-key", "1000", "FIELDS", "1", "field");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -30543,9 +31188,9 @@ const result = await client.hpExpire("my-key", "field", 1000);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -30556,9 +31201,9 @@ result = client.hpexpire("my-key", 1000, "field")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -30585,9 +31230,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -30600,9 +31245,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -30618,9 +31263,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # HPEXPIREAT
 Source: https://upstash.com/docs/redis/commands/hash/hpexpireat
@@ -30670,9 +31315,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+HPEXPIREAT my-key 1735689600 FIELDS 1 field
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -30685,9 +31338,9 @@ const expirationSet = await redis.hpexpireat("my-key", "my-field", Date.now() +
 console.log(expirationSet); // [1]
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -30697,9 +31350,9 @@ result = redis.hpexpireat("my-key", "field", 1735689600)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -30709,9 +31362,9 @@ const result = await redis.hpexpireat("my-key", "1735689600", "FIELDS", "1", "fi
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -30723,9 +31376,9 @@ const result = await client.hpExpireAt("my-key", "field", 1735689600);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -30736,9 +31389,9 @@ result = client.hpexpireat("my-key", 1735689600, "field")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -30765,9 +31418,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -30780,9 +31433,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -30798,9 +31451,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # HPEXPIRETIME
 Source: https://upstash.com/docs/redis/commands/hash/hpexpiretime
@@ -30843,9 +31496,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
 
-<Tab title="@upstash/redis">
+```bash
+HPEXPIRETIME my-key FIELDS 1 field
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -30859,9 +31520,9 @@ const expireTime = await redis.hpexpiretime("my-key", "my-field");
 console.log(expireTime); // e.g., 1697059200000
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -30871,9 +31532,9 @@ result = redis.hpexpiretime("my-key", "field")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -30883,9 +31544,9 @@ const result = await redis.hpexpiretime("my-key", "FIELDS", "1", "field");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -30897,9 +31558,9 @@ const result = await client.hpExpireTime("my-key", "field");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -30910,9 +31571,9 @@ result = client.hpexpiretime("my-key", "field")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -30939,9 +31600,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -30954,9 +31615,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -30972,9 +31633,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # HPTTL
 Source: https://upstash.com/docs/redis/commands/hash/hpttl
@@ -31017,9 +31678,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+HPTTL my-key FIELDS 1 field
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -31033,9 +31702,9 @@ const ttl = await redis.hpttl("my-key", "my-field");
 console.log(ttl); // e.g., [950]
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -31045,9 +31714,9 @@ result = redis.hpttl("my-key", "field")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -31057,9 +31726,9 @@ const result = await redis.hpttl("my-key", "FIELDS", "1", "field");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -31071,9 +31740,9 @@ const result = await client.hpTTL("my-key", "field");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -31084,9 +31753,9 @@ result = client.hpttl("my-key", "field")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -31113,9 +31782,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -31128,9 +31797,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -31146,9 +31815,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # HRANDFIELD
 Source: https://upstash.com/docs/redis/commands/hash/hrandfield
@@ -31193,9 +31862,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+HRANDFIELD my-key
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -31211,9 +31888,9 @@ const randomField = await redis.hrandfield("key");
 console.log(randomField); // one of "id", "username" or  "name"
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -31223,9 +31900,9 @@ result = redis.hrandfield("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -31235,9 +31912,9 @@ const result = await redis.hrandfield("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -31249,9 +31926,9 @@ const result = await client.hRandField("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -31262,9 +31939,9 @@ result = client.hrandfield("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -31291,9 +31968,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -31306,9 +31983,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -31324,9 +32001,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # HSCAN
 Source: https://upstash.com/docs/redis/commands/hash/hscan
@@ -31375,9 +32052,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+HSCAN my-key 0
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -31394,9 +32079,9 @@ console.log(newCursor); // likely `0` since this is a very small hash
 console.log(fields); // ["id", 1, "username", "chronark", "name", "andreas"]
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -31406,9 +32091,9 @@ result = redis.hscan("my-key", 0)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -31418,9 +32103,9 @@ const result = await redis.hscan("my-key", "0");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -31432,9 +32117,9 @@ const result = await client.hScan("my-key", "0");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -31445,9 +32130,9 @@ result = client.hscan("my-key", 0)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -31474,9 +32159,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -31489,28 +32174,29 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
+use redis::TypedCommands;
+
 fn main() -> redis::RedisResult<()> {
     let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
     let client = redis::Client::open(url)?;
     let mut connection = client.get_connection()?;
 
-    let mut command = redis::cmd("HSCAN");
-    command.arg("my-key");
-    command.arg("0");
-    let result: redis::Value = command.query(&mut connection)?;
-    println!("{result:?}");
+    let iter: redis::Iter<(String, String)> = connection.hscan("my-key")?;
+    for (field, value) in iter {
+        println!("{field}: {value}");
+    }
     Ok(())
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # HSET
 Source: https://upstash.com/docs/redis/commands/hash/hset
@@ -31551,9 +32237,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+HSET my-key field value
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -31567,9 +32261,9 @@ await redis.hset("key", {
   });
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -31579,9 +32273,9 @@ result = redis.hset("my-key", "field", "value")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -31591,9 +32285,9 @@ const result = await redis.hset("my-key", "field", "value");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -31605,9 +32299,9 @@ const result = await client.hSet("my-key", "field", "value");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -31618,9 +32312,9 @@ result = client.hset("my-key", "field", "value")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -31647,9 +32341,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -31662,9 +32356,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -31680,9 +32374,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # HSETEX
 Source: https://upstash.com/docs/redis/commands/hash/hsetex
@@ -31729,9 +32423,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+HSETEX my-key FIELDS 1 field value
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -31745,9 +32447,9 @@ await redis.hsetex("user:123", { expiration: { ex: 3600 } }, {
 });
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -31757,9 +32459,9 @@ result = redis.hsetex("my-key", field="field", value="value")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -31769,9 +32471,9 @@ const result = await redis.hsetex("my-key", "FIELDS", "1", "field", "value");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -31783,9 +32485,9 @@ const result = await client.hSetEx("my-key", { field: "value" });
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -31796,9 +32498,9 @@ result = client.hsetex("my-key", mapping={"field": "value"})
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -31825,9 +32527,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -31840,31 +32542,31 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
+use redis::{HashFieldExpirationOptions, TypedCommands};
+
 fn main() -> redis::RedisResult<()> {
     let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
     let client = redis::Client::open(url)?;
     let mut connection = client.get_connection()?;
 
-    let mut command = redis::cmd("HSETEX");
-    command.arg("my-key");
-    command.arg("FIELDS");
-    command.arg("1");
-    command.arg("field");
-    command.arg("value");
-    let result: redis::Value = command.query(&mut connection)?;
+    let result = connection.hset_ex(
+        "my-key",
+        &HashFieldExpirationOptions::default(),
+        &[("field", "value")],
+    )?;
     println!("{result:?}");
     Ok(())
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # HSETNX
 Source: https://upstash.com/docs/redis/commands/hash/hsetnx
@@ -31904,9 +32606,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+HSETNX my-key field value
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -31916,9 +32626,9 @@ const redis = Redis.fromEnv();
 await redis.hsetnx("key", "id", 1)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -31928,9 +32638,9 @@ result = redis.hsetnx("my-key", "field", "value")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -31940,9 +32650,9 @@ const result = await redis.hsetnx("my-key", "field", "value");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -31954,9 +32664,9 @@ const result = await client.hSetNX("my-key", "field", "value");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -31967,9 +32677,9 @@ result = client.hsetnx("my-key", "field", "value")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -31996,9 +32706,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -32011,9 +32721,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -32029,9 +32739,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # HSTRLEN
 Source: https://upstash.com/docs/redis/commands/hash/hstrlen
@@ -32070,9 +32780,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+HSTRLEN my-key field
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -32082,9 +32800,9 @@ const redis = Redis.fromEnv();
 const length = await redis.hstrlen("key", "field")
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -32094,9 +32812,9 @@ result = redis.hstrlen("my-key", "field")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -32106,9 +32824,9 @@ const result = await redis.hstrlen("my-key", "field");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -32120,9 +32838,9 @@ const result = await client.hStrLen("my-key", "field");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -32133,9 +32851,9 @@ result = client.hstrlen("my-key", "field")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -32162,9 +32880,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -32177,9 +32895,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -32196,9 +32914,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # HTTL
 Source: https://upstash.com/docs/redis/commands/hash/httl
@@ -32241,9 +32959,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+HTTL my-key FIELDS 1 field
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -32257,9 +32983,9 @@ const ttl = await redis.httl("my-key", "my-field");
 console.log(ttl); // e.g., [9]
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -32269,9 +32995,9 @@ result = redis.httl("my-key", "field")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -32281,9 +33007,9 @@ const result = await redis.httl("my-key", "FIELDS", "1", "field");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -32295,9 +33021,9 @@ const result = await client.hTTL("my-key", "field");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -32308,9 +33034,9 @@ result = client.httl("my-key", "field")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -32337,9 +33063,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -32352,9 +33078,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -32370,9 +33096,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # HVALS
 Source: https://upstash.com/docs/redis/commands/hash/hvals
@@ -32410,9 +33136,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+HVALS my-key
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -32427,9 +33161,9 @@ const values = await redis.hvals("key")
 console.log(values) // ["Hello", "World"]
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -32439,9 +33173,9 @@ result = redis.hvals("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -32451,9 +33185,9 @@ const result = await redis.hvals("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -32465,9 +33199,9 @@ const result = await client.hVals("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -32478,9 +33212,9 @@ result = client.hvals("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -32507,9 +33241,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -32522,9 +33256,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -32540,9 +33274,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # Hash commands
 Source: https://upstash.com/docs/redis/commands/hash/overview
@@ -32626,9 +33360,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+PFADD my-key element
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -32638,9 +33380,9 @@ const result = await redis.pfadd("my-key", "element");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -32650,9 +33392,9 @@ result = redis.pfadd("my-key", "member")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -32662,9 +33404,9 @@ const result = await redis.pfadd("my-key", "element");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -32676,9 +33418,9 @@ const result = await client.pfAdd("my-key", "element");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -32689,9 +33431,9 @@ result = client.pfadd("my-key", "member")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -32718,9 +33460,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -32733,9 +33475,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -32751,9 +33493,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # PFCOUNT
 Source: https://upstash.com/docs/redis/commands/hyperloglog/pfcount
@@ -32793,9 +33535,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+PFCOUNT my-key
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -32805,9 +33555,9 @@ const result = await redis.pfcount("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -32817,9 +33567,9 @@ result = redis.pfcount("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -32829,9 +33579,9 @@ const result = await redis.pfcount("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -32843,9 +33593,9 @@ const result = await client.pfCount("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -32856,9 +33606,9 @@ result = client.pfcount("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -32885,9 +33635,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -32900,9 +33650,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -32918,9 +33668,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # PFMERGE
 Source: https://upstash.com/docs/redis/commands/hyperloglog/pfmerge
@@ -32961,9 +33711,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+PFMERGE destination-key source-key
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -32973,9 +33731,9 @@ const result = await redis.pfmerge("destination-key", "source-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -32985,9 +33743,9 @@ result = redis.pfmerge("destination-key", "source-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -32997,9 +33755,9 @@ const result = await redis.pfmerge("destination-key", "source-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -33011,9 +33769,9 @@ const result = await client.pfMerge("destination-key", "source-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -33024,9 +33782,9 @@ result = client.pfmerge("destination-key", "source-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -33053,9 +33811,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -33068,9 +33826,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -33086,9 +33844,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # JSON.ARRAPPEND
 Source: https://upstash.com/docs/redis/commands/json/json-arrappend
@@ -33133,9 +33891,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+JSON.ARRAPPEND profile $.tags '"new"'
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -33145,9 +33911,9 @@ const redis = Redis.fromEnv();
 await redis.json.arrappend("key", "$.path.to.array", "a");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -33157,9 +33923,9 @@ result = redis.json().arrappend("profile", "$.tags", "new")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -33169,9 +33935,9 @@ const result = await redis.call("JSON.ARRAPPEND", "profile", "$.tags", "\"new\""
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -33183,9 +33949,9 @@ const result = await client.json.arrAppend("profile", "$.tags", "new");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -33196,9 +33962,9 @@ result = client.json().arrappend("profile", "$.tags", "new")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -33225,9 +33991,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -33240,9 +34006,9 @@ try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::JsonCommands;
@@ -33258,9 +34024,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # JSON.ARRINDEX
 Source: https://upstash.com/docs/redis/commands/json/json-arrindex
@@ -33307,9 +34073,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+JSON.ARRINDEX profile $.tags '"new"'
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -33319,9 +34093,9 @@ const redis = Redis.fromEnv();
 const index = await redis.json.arrindex("key", "$.path.to.array", "a");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -33331,9 +34105,9 @@ result = redis.json().arrindex("profile", "$.tags", "new")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -33343,9 +34117,9 @@ const result = await redis.call("JSON.ARRINDEX", "profile", "$.tags", "\"new\"")
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -33357,9 +34131,9 @@ const result = await client.json.arrIndex("profile", "$.tags", "new");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -33370,9 +34144,9 @@ result = client.json().arrindex("profile", "$.tags", "new")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -33399,9 +34173,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -33414,9 +34188,9 @@ try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::JsonCommands;
@@ -33432,9 +34206,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # JSON.ARRINSERT
 Source: https://upstash.com/docs/redis/commands/json/json-arrinsert
@@ -33480,9 +34254,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+JSON.ARRINSERT profile $.tags 0 '"first"'
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -33492,9 +34274,9 @@ const redis = Redis.fromEnv();
 const length = await redis.json.arrinsert("key", "$.path.to.array", 2, "a", "b");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -33504,9 +34286,9 @@ result = redis.json().arrinsert("profile", "$.tags", 0, "first")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -33516,9 +34298,9 @@ const result = await redis.call("JSON.ARRINSERT", "profile", "$.tags", "0", "\"f
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -33530,9 +34312,9 @@ const result = await client.json.arrInsert("profile", "$.tags", 0, "first");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -33543,9 +34325,9 @@ result = client.json().arrinsert("profile", "$.tags", 0, "first")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -33572,9 +34354,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -33587,9 +34369,9 @@ try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::JsonCommands;
@@ -33605,9 +34387,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # JSON.ARRLEN
 Source: https://upstash.com/docs/redis/commands/json/json-arrlen
@@ -33651,9 +34433,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+JSON.ARRLEN profile $.tags
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -33663,9 +34453,9 @@ const redis = Redis.fromEnv();
 const length = await redis.json.arrlen("key", "$.path.to.array");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -33675,9 +34465,9 @@ result = redis.json().arrlen("profile", "$.tags")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -33687,9 +34477,9 @@ const result = await redis.call("JSON.ARRLEN", "profile", "$.tags");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -33701,9 +34491,9 @@ const result = await client.json.arrLen("profile", { path: "$.tags" });
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -33714,9 +34504,9 @@ result = client.json().arrlen("profile", "$.tags")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -33743,9 +34533,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -33758,9 +34548,9 @@ try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::JsonCommands;
@@ -33776,9 +34566,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # JSON.ARRPOP
 Source: https://upstash.com/docs/redis/commands/json/json-arrpop
@@ -33825,9 +34615,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+JSON.ARRPOP profile $.tags -1
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -33837,9 +34635,9 @@ const redis = Redis.fromEnv();
 const element = await redis.json.arrpop("key", "$.path.to.array");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -33849,9 +34647,9 @@ result = redis.json().arrpop("profile", "$.tags", -1)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -33861,9 +34659,9 @@ const result = await redis.call("JSON.ARRPOP", "profile", "$.tags", "-1");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -33875,9 +34673,9 @@ const result = await client.json.arrPop("profile", { path: "$.tags", index: -1 }
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -33888,9 +34686,9 @@ result = client.json().arrpop("profile", "$.tags", -1)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -33917,9 +34715,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -33932,9 +34730,9 @@ try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::JsonCommands;
@@ -33950,9 +34748,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # JSON.ARRTRIM
 Source: https://upstash.com/docs/redis/commands/json/json-arrtrim
@@ -34000,9 +34798,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+JSON.ARRTRIM profile $.tags 0 9
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -34012,9 +34818,9 @@ const redis = Redis.fromEnv();
 const length = await redis.json.arrtrim("key", "$.path.to.array", 2, 10);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -34024,9 +34830,9 @@ result = redis.json().arrtrim("profile", "$.tags", 0, 9)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -34036,9 +34842,9 @@ const result = await redis.call("JSON.ARRTRIM", "profile", "$.tags", "0", "9");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -34050,9 +34856,9 @@ const result = await client.json.arrTrim("profile", "$.tags", 0, 9);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -34063,9 +34869,9 @@ result = client.json().arrtrim("profile", "$.tags", 0, 9)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -34092,9 +34898,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -34107,9 +34913,9 @@ try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::JsonCommands;
@@ -34125,9 +34931,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # JSON.CLEAR
 Source: https://upstash.com/docs/redis/commands/json/json-clear
@@ -34173,9 +34979,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+JSON.CLEAR profile $.stats
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -34185,9 +34999,9 @@ const redis = Redis.fromEnv();
 await redis.json.clear("key");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -34197,9 +35011,9 @@ result = redis.json().clear("profile", "$.stats")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -34209,9 +35023,9 @@ const result = await redis.call("JSON.CLEAR", "profile", "$.stats");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -34223,9 +35037,9 @@ const result = await client.json.clear("profile", { path: "$.stats" });
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -34236,9 +35050,9 @@ result = client.json().clear("profile", "$.stats")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -34265,9 +35079,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -34280,9 +35094,9 @@ try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::JsonCommands;
@@ -34298,9 +35112,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # JSON.DEBUG
 Source: https://upstash.com/docs/redis/commands/json/json-debug
@@ -34349,25 +35163,33 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+JSON.DEBUG MEMORY profile $.stats
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 <Note>
   This command is not supported yet in `upstash_redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -34377,9 +35199,9 @@ const result = await redis.call("JSON.DEBUG", "MEMORY", "profile", "$.stats");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -34391,9 +35213,9 @@ const result = await client.json.debugMemory("profile", { path: "$.stats" });
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -34404,9 +35226,9 @@ result = client.json().debug("MEMORY", "profile", "$.stats")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -34433,9 +35255,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -34448,9 +35270,9 @@ try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -34468,9 +35290,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # JSON.DEL
 Source: https://upstash.com/docs/redis/commands/json/json-del
@@ -34516,9 +35338,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+JSON.DEL profile $.temporary
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -34528,9 +35358,9 @@ const redis = Redis.fromEnv();
 await redis.json.del("key", "$.path.to.value");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -34540,9 +35370,9 @@ result = redis.json().delete("profile", "$.temporary")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -34552,9 +35382,9 @@ const result = await redis.call("JSON.DEL", "profile", "$.temporary");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -34566,9 +35396,9 @@ const result = await client.json.del("profile", { path: "$.temporary" });
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -34579,9 +35409,9 @@ result = client.json().delete("profile", "$.temporary")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -34608,9 +35438,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -34623,9 +35453,9 @@ try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::JsonCommands;
@@ -34641,9 +35471,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # JSON.FORGET
 Source: https://upstash.com/docs/redis/commands/json/json-forget
@@ -34687,9 +35517,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+JSON.FORGET profile $.temporary
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -34699,9 +35537,9 @@ const redis = Redis.fromEnv();
 await redis.json.forget("key", "$.path.to.value");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -34711,9 +35549,9 @@ result = redis.json().forget("profile", "$.temporary")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -34723,9 +35561,9 @@ const result = await redis.call("JSON.FORGET", "profile", "$.temporary");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -34737,9 +35575,9 @@ const result = await client.json.forget("profile", { path: "$.temporary" });
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -34750,9 +35588,9 @@ result = client.json().forget("profile", "$.temporary")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -34779,9 +35617,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -34794,9 +35632,9 @@ try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::JsonCommands;
@@ -34812,9 +35650,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # JSON.GET
 Source: https://upstash.com/docs/redis/commands/json/json-get
@@ -34867,9 +35705,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+JSON.GET profile $.name
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -34879,9 +35725,9 @@ const redis = Redis.fromEnv();
 const value = await redis.json.get("key", "$.path.to.somewhere");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -34891,9 +35737,9 @@ result = redis.json().get("profile", "$.name")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -34903,9 +35749,9 @@ const result = await redis.call("JSON.GET", "profile", "$.name");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -34917,9 +35763,9 @@ const result = await client.json.get("profile", { path: "$.name" });
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -34930,9 +35776,9 @@ result = client.json().get("profile", "$.name")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -34959,9 +35805,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -34974,9 +35820,9 @@ try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::JsonCommands;
@@ -34992,9 +35838,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # JSON.MERGE
 Source: https://upstash.com/docs/redis/commands/json/json-merge
@@ -35041,9 +35887,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+JSON.MERGE profile $ '{"active":true}'
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -35053,9 +35907,9 @@ const redis = Redis.fromEnv();
 await redis.json.merge("key", "$.path.to.value", {"new": "value"})
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -35065,9 +35919,9 @@ result = redis.json().merge("profile", "$", {"active": True})
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -35077,9 +35931,9 @@ const result = await redis.call("JSON.MERGE", "profile", "$", "{\"active\":true}
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -35091,9 +35945,9 @@ const result = await client.json.merge("profile", "$", { active: true });
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -35104,9 +35958,9 @@ result = client.json().merge("profile", "$", {"active": True})
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -35133,9 +35987,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -35148,9 +36002,9 @@ try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -35168,9 +36022,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # JSON.MGET
 Source: https://upstash.com/docs/redis/commands/json/json-mget
@@ -35214,9 +36068,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+JSON.MGET profile:1 profile:2 $.name
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -35226,9 +36088,9 @@ const redis = Redis.fromEnv();
 const values = await redis.json.mget(["key1", "key2"],  "$.path.to.somewhere");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -35238,9 +36100,9 @@ result = redis.json().mget(["profile:1", "profile:2"], "$.name")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -35250,9 +36112,9 @@ const result = await redis.call("JSON.MGET", "profile:1", "profile:2", "$.name")
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -35264,9 +36126,9 @@ const result = await client.json.mGet(["profile:1", "profile:2"], "$.name");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -35277,9 +36139,9 @@ result = client.json().mget(["profile:1", "profile:2"], "$.name")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -35306,9 +36168,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -35321,9 +36183,9 @@ try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::JsonCommands;
@@ -35339,9 +36201,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # JSON.MSET
 Source: https://upstash.com/docs/redis/commands/json/json-mset
@@ -35384,9 +36246,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+JSON.MSET profile:1 $ '{"name":"Ada"}'
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -35398,9 +36268,9 @@ const result = await redis.json.mset([
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -35410,9 +36280,9 @@ result = redis.json().mset([("profile:1", "$", {"name": "Ada"})])
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -35422,9 +36292,9 @@ const result = await redis.call("JSON.MSET", "profile:1", "$", "{\"name\":\"Ada\
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -35436,9 +36306,9 @@ const result = await client.json.mSet([{ key: "profile:1", path: "$", value: { n
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -35449,9 +36319,9 @@ result = client.json().mset([("profile:1", "$", {"name": "Ada"})])
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -35478,9 +36348,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -35495,9 +36365,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -35515,9 +36385,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # JSON.NUMINCRBY
 Source: https://upstash.com/docs/redis/commands/json/json-numincrby
@@ -35562,9 +36432,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+JSON.NUMINCRBY profile $.visits 1
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -35574,9 +36452,9 @@ const redis = Redis.fromEnv();
 const newValue = await redis.json.numincrby("key", "$.path.to.value", 2);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -35586,9 +36464,9 @@ result = redis.json().numincrby("profile", "$.visits", 1)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -35598,9 +36476,9 @@ const result = await redis.call("JSON.NUMINCRBY", "profile", "$.visits", "1");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -35612,9 +36490,9 @@ const result = await client.json.numIncrBy("profile", "$.visits", 1);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -35625,9 +36503,9 @@ result = client.json().numincrby("profile", "$.visits", 1)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -35654,9 +36532,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -35669,9 +36547,9 @@ try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::JsonCommands;
@@ -35687,9 +36565,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # JSON.NUMMULTBY
 Source: https://upstash.com/docs/redis/commands/json/json-nummultby
@@ -35734,9 +36612,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+JSON.NUMMULTBY profile $.score 2
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -35746,9 +36632,9 @@ const redis = Redis.fromEnv();
 const newValue = await redis.json.nummultby("key", "$.path.to.value", 2);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -35758,9 +36644,9 @@ result = redis.json().nummultby("profile", "$.score", 2)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -35770,9 +36656,9 @@ const result = await redis.call("JSON.NUMMULTBY", "profile", "$.score", "2");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -35784,9 +36670,9 @@ const result = await client.json.numMultBy("profile", "$.score", 2);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -35797,9 +36683,9 @@ result = client.json().nummultby("profile", "$.score", 2)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -35826,9 +36712,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -35843,9 +36729,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -35863,9 +36749,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # JSON.OBJKEYS
 Source: https://upstash.com/docs/redis/commands/json/json-objkeys
@@ -35909,9 +36795,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+JSON.OBJKEYS profile $
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -35921,9 +36815,9 @@ const redis = Redis.fromEnv();
 const keys = await redis.json.objkeys("key", "$.path");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -35933,9 +36827,9 @@ result = redis.json().objkeys("profile", "$")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -35945,9 +36839,9 @@ const result = await redis.call("JSON.OBJKEYS", "profile", "$");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -35959,9 +36853,9 @@ const result = await client.json.objKeys("profile", { path: "$" });
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -35972,9 +36866,9 @@ result = client.json().objkeys("profile", "$")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -36001,9 +36895,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -36016,9 +36910,9 @@ try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::JsonCommands;
@@ -36034,9 +36928,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # JSON.OBJLEN
 Source: https://upstash.com/docs/redis/commands/json/json-objlen
@@ -36080,9 +36974,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
 
-<Tab title="@upstash/redis">
+```bash
+JSON.OBJLEN profile $
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -36092,9 +36994,9 @@ const redis = Redis.fromEnv();
 const lengths = await redis.json.objlen("key", "$.path");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -36104,9 +37006,9 @@ result = redis.json().objlen("profile", "$")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -36116,9 +37018,9 @@ const result = await redis.call("JSON.OBJLEN", "profile", "$");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -36130,9 +37032,9 @@ const result = await client.json.objLen("profile", { path: "$" });
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -36143,9 +37045,9 @@ result = client.json().objlen("profile", "$")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -36172,9 +37074,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -36187,9 +37089,9 @@ try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::JsonCommands;
@@ -36205,9 +37107,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # JSON.RESP
 Source: https://upstash.com/docs/redis/commands/json/json-resp
@@ -36253,9 +37155,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
 
-<Tab title="@upstash/redis">
+```bash
+JSON.RESP profile $
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -36265,9 +37175,9 @@ const result = await redis.json.resp("profile", "$");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -36277,9 +37187,9 @@ result = redis.json().resp("profile", "$")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -36289,9 +37199,9 @@ const result = await redis.call("JSON.RESP", "profile", "$");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -36303,9 +37213,9 @@ const result = await client.sendCommand(["JSON.RESP", "profile", "$"]);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -36316,9 +37226,9 @@ result = client.json().resp("profile", "$")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -36345,9 +37255,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -36362,9 +37272,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -36381,9 +37291,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # JSON.SET
 Source: https://upstash.com/docs/redis/commands/json/json-set
@@ -36431,9 +37341,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+JSON.SET profile $ '{"name":"Ada"}'
+```
 
-<Tab title="@upstash/redis">
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -36443,9 +37361,9 @@ const redis = Redis.fromEnv();
 redis.json.set(key, "$.path", value);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -36455,9 +37373,9 @@ result = redis.json().set("profile", "$", {"name": "Ada"})
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -36467,9 +37385,9 @@ const result = await redis.call("JSON.SET", "profile", "$", "{\"name\":\"Ada\"}"
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -36481,9 +37399,9 @@ const result = await client.json.set("profile", "$", { name: "Ada" });
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -36494,9 +37412,9 @@ result = client.json().set("profile", "$", {"name": "Ada"})
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -36523,9 +37441,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -36538,9 +37456,9 @@ try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::JsonCommands;
@@ -36556,9 +37474,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # JSON.STRAPPEND
 Source: https://upstash.com/docs/redis/commands/json/json-strappend
@@ -36603,9 +37521,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
 
-<Tab title="@upstash/redis">
+```bash
+JSON.STRAPPEND profile $.name '" Lovelace"'
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -36615,9 +37541,9 @@ const redis = Redis.fromEnv();
 await redis.json.strappend("key", "$.path.to.str", "abc");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -36627,9 +37553,9 @@ result = redis.json().strappend("profile", "$.name", " Lovelace")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -36639,9 +37565,9 @@ const result = await redis.call("JSON.STRAPPEND", "profile", "$.name", "\" Lovel
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -36653,9 +37579,9 @@ const result = await client.json.strAppend("profile", " Lovelace", { path: "$.na
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -36666,9 +37592,9 @@ result = client.json().strappend("profile", " Lovelace", "$.name")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -36695,9 +37621,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -36710,9 +37636,9 @@ try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::JsonCommands;
@@ -36728,9 +37654,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # JSON.STRLEN
 Source: https://upstash.com/docs/redis/commands/json/json-strlen
@@ -36774,9 +37700,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+JSON.STRLEN profile $.name
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -36786,9 +37720,9 @@ const redis = Redis.fromEnv();
 await redis.json.strlen("key", "$.path.to.str", "a");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -36798,9 +37732,9 @@ result = redis.json().strlen("profile", "$.name")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -36810,9 +37744,9 @@ const result = await redis.call("JSON.STRLEN", "profile", "$.name");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -36824,9 +37758,9 @@ const result = await client.json.strLen("profile", { path: "$.name" });
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -36837,9 +37771,9 @@ result = client.json().strlen("profile", "$.name")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -36866,9 +37800,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -36881,9 +37815,9 @@ try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::JsonCommands;
@@ -36899,9 +37833,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # JSON.TOGGLE
 Source: https://upstash.com/docs/redis/commands/json/json-toggle
@@ -36945,9 +37879,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+JSON.TOGGLE profile $.active
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -36957,9 +37899,9 @@ const redis = Redis.fromEnv();
 const bool = await redis.json.toggle("key", "$.path.to.bool");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -36969,9 +37911,9 @@ result = redis.json().toggle("profile", "$.active")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -36981,9 +37923,9 @@ const result = await redis.call("JSON.TOGGLE", "profile", "$.active");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -36995,9 +37937,9 @@ const result = await client.json.toggle("profile", "$.active");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -37008,9 +37950,9 @@ result = client.json().toggle("profile", "$.active")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -37037,9 +37979,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -37052,9 +37994,9 @@ try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::JsonCommands;
@@ -37070,9 +38012,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # JSON.TYPE
 Source: https://upstash.com/docs/redis/commands/json/json-type
@@ -37116,9 +38058,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+JSON.TYPE profile $.name
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -37128,9 +38078,9 @@ const redis = Redis.fromEnv();
 const myType = await redis.json.type("key", "$.path.to.value");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -37140,9 +38090,9 @@ result = redis.json().type("profile", "$.name")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -37152,9 +38102,9 @@ const result = await redis.call("JSON.TYPE", "profile", "$.name");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -37166,9 +38116,9 @@ const result = await client.json.type("profile", { path: "$.name" });
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -37179,9 +38129,9 @@ result = client.json().type("profile", "$.name")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -37208,9 +38158,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -37223,9 +38173,9 @@ try (JedisPooled jedis = new JedisPooled(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::JsonCommands;
@@ -37241,9 +38191,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # JSON commands
 Source: https://upstash.com/docs/redis/commands/json/overview
@@ -37323,25 +38273,33 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+BLMOVE source-key destination-key LEFT LEFT 1.5
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 <Note>
   This command is not supported yet in `upstash_redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -37351,9 +38309,9 @@ const result = await redis.blmove("source-key", "destination-key", "LEFT", "LEFT
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -37365,9 +38323,9 @@ const result = await client.blMove("source-key", "destination-key", "LEFT", "LEF
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -37378,9 +38336,9 @@ result = client.blmove("source-key", "destination-key", 1.5, "LEFT", "LEFT")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -37408,9 +38366,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -37423,31 +38381,33 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
+use redis::{Direction, TypedCommands};
+
 fn main() -> redis::RedisResult<()> {
     let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
     let client = redis::Client::open(url)?;
     let mut connection = client.get_connection()?;
 
-    let mut command = redis::cmd("BLMOVE");
-    command.arg("source-key");
-    command.arg("destination-key");
-    command.arg("LEFT");
-    command.arg("LEFT");
-    command.arg("1.5");
-    let result: redis::Value = command.query(&mut connection)?;
+    let result = connection.blmove(
+        "source-key",
+        "destination-key",
+        Direction::Left,
+        Direction::Left,
+        1.5,
+    )?;
     println!("{result:?}");
     Ok(())
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # BLMPOP
 Source: https://upstash.com/docs/redis/commands/list/blmpop
@@ -37495,25 +38455,33 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+BLMPOP 1.5 1 my-key LEFT
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 <Note>
   This command is not supported yet in `upstash_redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -37523,9 +38491,9 @@ const result = await redis.blmpop("1.5", "1", "my-key", "LEFT");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -37537,9 +38505,9 @@ const result = await client.blmPop(1.5, "my-key", "LEFT");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -37550,9 +38518,9 @@ result = client.blmpop(1.5, 1, "my-key", direction="LEFT")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -37580,9 +38548,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -37595,30 +38563,27 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
+use redis::{Direction, TypedCommands};
+
 fn main() -> redis::RedisResult<()> {
     let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
     let client = redis::Client::open(url)?;
     let mut connection = client.get_connection()?;
 
-    let mut command = redis::cmd("BLMPOP");
-    command.arg("1.5");
-    command.arg("1");
-    command.arg("my-key");
-    command.arg("LEFT");
-    let result: redis::Value = command.query(&mut connection)?;
+    let result = connection.blmpop(1.5, 1, "my-key", Direction::Left, 1)?;
     println!("{result:?}");
     Ok(())
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # BLPOP
 Source: https://upstash.com/docs/redis/commands/list/blpop
@@ -37663,25 +38628,33 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+BLPOP my-key 1.5
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 <Note>
   This command is not supported yet in `upstash_redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -37691,9 +38664,9 @@ const result = await redis.blpop("my-key", "1.5");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -37705,9 +38678,9 @@ const result = await client.blPop("my-key", 1.5);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -37718,9 +38691,9 @@ result = client.blpop(["my-key"], timeout=1.5)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -37748,9 +38721,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -37763,28 +38736,27 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
+use redis::TypedCommands;
+
 fn main() -> redis::RedisResult<()> {
     let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
     let client = redis::Client::open(url)?;
     let mut connection = client.get_connection()?;
 
-    let mut command = redis::cmd("BLPOP");
-    command.arg("my-key");
-    command.arg("1.5");
-    let result: redis::Value = command.query(&mut connection)?;
+    let result = connection.blpop("my-key", 1.5)?;
     println!("{result:?}");
     Ok(())
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # BRPOP
 Source: https://upstash.com/docs/redis/commands/list/brpop
@@ -37829,25 +38801,33 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+BRPOP my-key 1.5
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 <Note>
   This command is not supported yet in `upstash_redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -37857,9 +38837,9 @@ const result = await redis.brpop("my-key", "1.5");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -37871,9 +38851,9 @@ const result = await client.brPop("my-key", 1.5);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -37884,9 +38864,9 @@ result = client.brpop(["my-key"], timeout=1.5)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -37914,9 +38894,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -37929,34 +38909,33 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
+use redis::TypedCommands;
+
 fn main() -> redis::RedisResult<()> {
     let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
     let client = redis::Client::open(url)?;
     let mut connection = client.get_connection()?;
 
-    let mut command = redis::cmd("BRPOP");
-    command.arg("my-key");
-    command.arg("1.5");
-    let result: redis::Value = command.query(&mut connection)?;
+    let result = connection.brpop("my-key", 1.5)?;
     println!("{result:?}");
     Ok(())
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # BRPOPLPUSH
 Source: https://upstash.com/docs/redis/commands/list/brpoplpush
 
 <Warning>
-  Prefer [`BLMOVE`](/docs/redis/commands/list/blmove) with `RIGHT` and `LEFT` in new code: `BLMOVE <source> <destination> RIGHT LEFT <timeout>`. `BRPOPLPUSH` is deprecated in Redis but still supported by Upstash.
+  Prefer [`BLMOVE`](/docs/redis/commands/list/blmove) with `RIGHT` and `LEFT` in new code: `BLMOVE <source> <destination> RIGHT LEFT <timeout>`.
 </Warning>
 
 Use `BRPOPLPUSH` to pop an element from the tail of one list and push it to the head of another, blocking until the source has an element or the timeout expires.
@@ -38000,25 +38979,33 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
 
-<Tab title="@upstash/redis">
+```bash
+BRPOPLPUSH source-key destination-key 1.5
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 <Note>
   This command is not supported yet in `upstash_redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -38028,9 +39015,9 @@ const result = await redis.brpoplpush("source-key", "destination-key", "1.5");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -38042,9 +39029,9 @@ const result = await client.brPopLPush("source-key", "destination-key", 1.5);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -38055,9 +39042,9 @@ result = client.brpoplpush("source-key", "destination-key", timeout=1.5)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -38085,9 +39072,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -38100,29 +39087,27 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
+use redis::TypedCommands;
+
 fn main() -> redis::RedisResult<()> {
     let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
     let client = redis::Client::open(url)?;
     let mut connection = client.get_connection()?;
 
-    let mut command = redis::cmd("BRPOPLPUSH");
-    command.arg("source-key");
-    command.arg("destination-key");
-    command.arg("1.5");
-    let result: redis::Value = command.query(&mut connection)?;
+    let result = connection.brpoplpush("source-key", "destination-key", 1.5)?;
     println!("{result:?}");
     Ok(())
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # LINDEX
 Source: https://upstash.com/docs/redis/commands/list/lindex
@@ -38161,9 +39146,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+LINDEX my-key 0
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -38175,9 +39168,9 @@ const element = await redis.lindex("key", 0);
 console.log(element); // "a"
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -38187,9 +39180,9 @@ result = redis.lindex("my-key", 0)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -38199,9 +39192,9 @@ const result = await redis.lindex("my-key", "0");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -38213,9 +39206,9 @@ const result = await client.lIndex("my-key", 0);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -38226,9 +39219,9 @@ result = client.lindex("my-key", 0)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -38255,9 +39248,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -38270,9 +39263,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -38288,9 +39281,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # LINSERT
 Source: https://upstash.com/docs/redis/commands/list/linsert
@@ -38333,9 +39326,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+LINSERT my-key BEFORE pivot element
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -38346,9 +39347,9 @@ await redis.rpush("key", "a", "b", "c");
 await redis.linsert("key", "before", "b", "x");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -38358,9 +39359,9 @@ result = redis.linsert("my-key", "BEFORE", "pivot", "element")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -38370,9 +39371,9 @@ const result = await redis.linsert("my-key", "BEFORE", "pivot", "element");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -38384,9 +39385,9 @@ const result = await client.lInsert("my-key", "BEFORE", "pivot", "element");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -38397,9 +39398,9 @@ result = client.linsert("my-key", "BEFORE", "pivot", "element")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -38426,9 +39427,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -38441,9 +39442,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -38459,9 +39460,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # LLEN
 Source: https://upstash.com/docs/redis/commands/list/llen
@@ -38499,9 +39500,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+LLEN my-key
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -38513,9 +39522,9 @@ const length = await redis.llen("key");
 console.log(length); // 3
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -38525,9 +39534,9 @@ result = redis.llen("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -38537,9 +39546,9 @@ const result = await redis.llen("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -38551,9 +39560,9 @@ const result = await client.lLen("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -38564,9 +39573,9 @@ result = client.llen("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -38593,9 +39602,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -38608,9 +39617,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -38626,9 +39635,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # LMOVE
 Source: https://upstash.com/docs/redis/commands/list/lmove
@@ -38671,9 +39680,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+LMOVE source-key destination-key LEFT LEFT
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -38684,9 +39701,9 @@ await redis.rpush("source", "a", "b", "c");
 const element = await redis.lmove("source", "destination", "left", "left");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -38696,9 +39713,9 @@ result = redis.lmove("source-key", "destination-key", "LEFT", "LEFT")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -38708,9 +39725,9 @@ const result = await redis.lmove("source-key", "destination-key", "LEFT", "LEFT"
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -38722,9 +39739,9 @@ const result = await client.lMove("source-key", "destination-key", "LEFT", "LEFT
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -38735,9 +39752,9 @@ result = client.lmove("source-key", "destination-key", "LEFT", "LEFT")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -38764,9 +39781,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -38779,9 +39796,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -38797,9 +39814,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # LMPOP
 Source: https://upstash.com/docs/redis/commands/list/lmpop
@@ -38842,9 +39859,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+LMPOP 1 my-key LEFT
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -38854,17 +39879,17 @@ const result = await redis.lmpop(1, ["my-key"], "LEFT");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 <Note>
   This command is not supported yet in `upstash_redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -38874,9 +39899,9 @@ const result = await redis.lmpop("1", "my-key", "LEFT");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -38888,9 +39913,9 @@ const result = await client.lmPop("my-key", "LEFT");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -38901,9 +39926,9 @@ result = client.lmpop(1, "my-key", direction="LEFT")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -38930,9 +39955,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -38945,29 +39970,27 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
+use redis::{Direction, TypedCommands};
+
 fn main() -> redis::RedisResult<()> {
     let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
     let client = redis::Client::open(url)?;
     let mut connection = client.get_connection()?;
 
-    let mut command = redis::cmd("LMPOP");
-    command.arg("1");
-    command.arg("my-key");
-    command.arg("LEFT");
-    let result: redis::Value = command.query(&mut connection)?;
+    let result = connection.lmpop(1, "my-key", Direction::Left, 1)?;
     println!("{result:?}");
     Ok(())
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # LPOP
 Source: https://upstash.com/docs/redis/commands/list/lpop
@@ -39008,9 +40031,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+LPOP my-key
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -39022,9 +40053,9 @@ const element = await redis.lpop("key");
 console.log(element); // "a"
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -39034,9 +40065,9 @@ result = redis.lpop("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -39046,9 +40077,9 @@ const result = await redis.lpop("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -39060,9 +40091,9 @@ const result = await client.lPop("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -39073,9 +40104,9 @@ result = client.lpop("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -39102,9 +40133,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -39117,9 +40148,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -39135,9 +40166,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # LPOS
 Source: https://upstash.com/docs/redis/commands/list/lpos
@@ -39181,9 +40212,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+LPOS my-key element
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -39195,9 +40234,9 @@ const index = await redis.lpos("key", "b");
 console.log(index); // 1
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -39207,9 +40246,9 @@ result = redis.lpos("my-key", "element")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -39219,9 +40258,9 @@ const result = await redis.lpos("my-key", "element");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -39233,9 +40272,9 @@ const result = await client.lPos("my-key", "element");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -39246,9 +40285,9 @@ result = client.lpos("my-key", "element")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -39275,9 +40314,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -39290,28 +40329,27 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
+use redis::{LposOptions, TypedCommands};
+
 fn main() -> redis::RedisResult<()> {
     let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
     let client = redis::Client::open(url)?;
     let mut connection = client.get_connection()?;
 
-    let mut command = redis::cmd("LPOS");
-    command.arg("my-key");
-    command.arg("element");
-    let result: redis::Value = command.query(&mut connection)?;
+    let result: Option<isize> = connection.lpos("my-key", "element", LposOptions::default())?;
     println!("{result:?}");
     Ok(())
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # LPUSH
 Source: https://upstash.com/docs/redis/commands/list/lpush
@@ -39352,9 +40390,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
 
-<Tab title="@upstash/redis">
+```bash
+LPUSH my-key element
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -39367,9 +40413,9 @@ const length2 = await redis.lpush("key", "d");
 console.log(length2); // 4
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -39379,9 +40425,9 @@ result = redis.lpush("my-key", "element")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -39391,9 +40437,9 @@ const result = await redis.lpush("my-key", "element");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -39405,9 +40451,9 @@ const result = await client.lPush("my-key", "element");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -39418,9 +40464,9 @@ result = client.lpush("my-key", "element")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -39447,9 +40493,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -39462,9 +40508,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -39480,9 +40526,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # LPUSHX
 Source: https://upstash.com/docs/redis/commands/list/lpushx
@@ -39521,9 +40567,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
 
-<Tab title="@upstash/redis">
+```bash
+LPUSHX my-key element
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -39535,9 +40589,9 @@ const length = await redis.lpushx("key", "d");
 console.log(length); // 4
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -39547,9 +40601,9 @@ result = redis.lpushx("my-key", "element")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -39559,9 +40613,9 @@ const result = await redis.lpushx("my-key", "element");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -39573,9 +40627,9 @@ const result = await client.lPushX("my-key", "element");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -39586,9 +40640,9 @@ result = client.lpushx("my-key", "element")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -39615,9 +40669,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -39630,9 +40684,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -39648,9 +40702,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # LRANGE
 Source: https://upstash.com/docs/redis/commands/list/lrange
@@ -39692,9 +40746,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+LRANGE my-key 0 0
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -39706,9 +40768,9 @@ const elements = await redis.lrange("key", 1, 2);
 console.log(elements) // ["b", "c"]
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -39718,9 +40780,9 @@ result = redis.lrange("my-key", 0, 0)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -39730,9 +40792,9 @@ const result = await redis.lrange("my-key", "0", "0");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -39744,9 +40806,9 @@ const result = await client.lRange("my-key", 0, 0);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -39757,9 +40819,9 @@ result = client.lrange("my-key", 0, 0)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -39786,9 +40848,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -39801,9 +40863,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -39819,9 +40881,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # LREM
 Source: https://upstash.com/docs/redis/commands/list/lrem
@@ -39863,9 +40925,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+LREM my-key 1 element
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -39877,9 +40947,9 @@ const removed = await redis.lrem("key", 4, "b");
 console.log(removed) // 2
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -39889,9 +40959,9 @@ result = redis.lrem("my-key", 1, "element")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -39901,9 +40971,9 @@ const result = await redis.lrem("my-key", "1", "element");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -39915,9 +40985,9 @@ const result = await client.lRem("my-key", 1, "element");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -39928,9 +40998,9 @@ result = client.lrem("my-key", 1, "element")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -39957,9 +41027,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -39972,9 +41042,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -39990,9 +41060,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # LSET
 Source: https://upstash.com/docs/redis/commands/list/lset
@@ -40032,9 +41102,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+LSET my-key 0 element
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -40047,9 +41125,9 @@ await redis.lset("key", 1, "d");
 // list is now ["a", "d", "c"]
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -40059,9 +41137,9 @@ result = redis.lset("my-key", 0, "element")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -40071,9 +41149,9 @@ const result = await redis.lset("my-key", "0", "element");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -40085,9 +41163,9 @@ const result = await client.lSet("my-key", 0, "element");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -40098,9 +41176,9 @@ result = client.lset("my-key", 0, "element")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -40127,9 +41205,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -40142,9 +41220,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -40160,9 +41238,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # LTRIM
 Source: https://upstash.com/docs/redis/commands/list/ltrim
@@ -40204,9 +41282,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
 
-<Tab title="@upstash/redis">
+```bash
+LTRIM my-key 0 0
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -40218,9 +41304,9 @@ await redis.ltrim("key", 1, 2);
 // the list is now ["b", "c"]
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -40230,9 +41316,9 @@ result = redis.ltrim("my-key", 0, 0)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -40242,9 +41328,9 @@ const result = await redis.ltrim("my-key", "0", "0");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -40256,9 +41342,9 @@ const result = await client.lTrim("my-key", 0, 0);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -40269,9 +41355,9 @@ result = client.ltrim("my-key", 0, 0)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -40298,9 +41384,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -40313,9 +41399,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -40331,9 +41417,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # List commands
 Source: https://upstash.com/docs/redis/commands/list/overview
@@ -40402,9 +41488,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
 
-<Tab title="@upstash/redis">
+```bash
+RPOP my-key
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -40416,9 +41510,9 @@ const element = await redis.rpop("key");
 console.log(element); // "c"
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -40428,9 +41522,9 @@ result = redis.rpop("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -40440,9 +41534,9 @@ const result = await redis.rpop("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -40454,9 +41548,9 @@ const result = await client.rPop("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -40467,9 +41561,9 @@ result = client.rpop("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -40496,9 +41590,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -40511,9 +41605,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -40529,15 +41623,15 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # RPOPLPUSH
 Source: https://upstash.com/docs/redis/commands/list/rpoplpush
 
 <Warning>
-  Prefer [`LMOVE`](/docs/redis/commands/list/lmove) with `RIGHT` and `LEFT` in new code: `LMOVE <source> <destination> RIGHT LEFT`. `RPOPLPUSH` is deprecated in Redis but still supported by Upstash.
+  Prefer [`LMOVE`](/docs/redis/commands/list/lmove) with `RIGHT` and `LEFT` in new code: `LMOVE <source> <destination> RIGHT LEFT`.
 </Warning>
 
 Use `RPOPLPUSH` to atomically move an element from the tail of one list to the head of another, returning the element.
@@ -40576,17 +41670,25 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+RPOPLPUSH source-key destination-key
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -40596,9 +41698,9 @@ result = redis.rpoplpush("source-key", "destination-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -40608,9 +41710,9 @@ const result = await redis.rpoplpush("source-key", "destination-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -40622,9 +41724,9 @@ const result = await client.rPopLPush("source-key", "destination-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -40635,9 +41737,9 @@ result = client.rpoplpush("source-key", "destination-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -40664,9 +41766,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -40679,9 +41781,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -40697,9 +41799,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # RPUSH
 Source: https://upstash.com/docs/redis/commands/list/rpush
@@ -40740,9 +41842,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+RPUSH my-key element
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -40755,9 +41865,9 @@ const length2 = await redis.rpush("key", "d");
 console.log(length2); // 4
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -40767,9 +41877,9 @@ result = redis.rpush("my-key", "element")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -40779,9 +41889,9 @@ const result = await redis.rpush("my-key", "element");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -40793,9 +41903,9 @@ const result = await client.rPush("my-key", "element");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -40806,9 +41916,9 @@ result = client.rpush("my-key", "element")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -40835,9 +41945,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -40850,9 +41960,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -40868,9 +41978,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # RPUSHX
 Source: https://upstash.com/docs/redis/commands/list/rpushx
@@ -40909,9 +42019,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+RPUSHX my-key element
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -40923,9 +42041,9 @@ const length = await redis.rpushx("key", "d");
 console.log(length); // 4
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -40935,9 +42053,9 @@ result = redis.rpushx("my-key", "element")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -40947,9 +42065,9 @@ const result = await redis.rpushx("my-key", "element");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -40961,9 +42079,9 @@ const result = await client.rPushX("my-key", "element");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -40974,9 +42092,9 @@ result = client.rpushx("my-key", "element")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -41003,9 +42121,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -41018,9 +42136,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -41036,9 +42154,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # Redis command reference
 Source: https://upstash.com/docs/redis/commands/overview
@@ -41121,9 +42239,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
 
-<Tab title="ioredis">
+```bash
+PSUBSCRIBE events:*
+```
+
+</Accordion>
+
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -41133,9 +42259,9 @@ await subscriber.psubscribe("events:*");
 subscriber.on("message", (channel, message) => console.log(channel, message));
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -41146,9 +42272,9 @@ await subscriber.pSubscribe("events:*", (message, channel) => {
 });
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -41161,9 +42287,9 @@ for message in pubsub.listen():
     print(message)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -41190,9 +42316,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -41209,9 +42335,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -41230,9 +42356,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # PUBLISH
 Source: https://upstash.com/docs/redis/commands/pub-sub/publish
@@ -41273,9 +42399,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+PUBLISH events hello
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -41285,9 +42419,9 @@ const redis = Redis.fromEnv();
 const listeners = await redis.publish("my-channel", "my-message");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -41297,9 +42431,9 @@ result = redis.publish("events", "hello")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -41309,9 +42443,9 @@ const result = await redis.publish("events", "hello");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -41323,9 +42457,9 @@ const result = await client.publish("events", "hello");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -41336,9 +42470,9 @@ result = client.publish("events", "hello")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -41365,9 +42499,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -41380,9 +42514,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -41398,9 +42532,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # PUBSUB
 Source: https://upstash.com/docs/redis/commands/pub-sub/pubsub
@@ -41444,25 +42578,33 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
 
-<Tab title="@upstash/redis">
+```bash
+PUBSUB CHANNELS events:*
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 <Note>
   This command is not supported yet in `upstash_redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -41472,9 +42614,9 @@ const result = await redis.pubsub("CHANNELS", "events:*");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -41486,9 +42628,9 @@ const result = await client.pubSubChannels("events:*");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -41499,9 +42641,9 @@ result = client.pubsub_channels("events:*")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -41528,9 +42670,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -41543,9 +42685,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -41562,9 +42704,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # PUNSUBSCRIBE
 Source: https://upstash.com/docs/redis/commands/pub-sub/punsubscribe
@@ -41609,9 +42751,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="ioredis">
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+PUNSUBSCRIBE events:*
+```
+
+</Accordion>
+
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -41621,9 +42771,9 @@ await subscriber.psubscribe("events:*");
 await subscriber.punsubscribe("events:*");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -41633,9 +42783,9 @@ await subscriber.pSubscribe("events:*", console.log);
 await subscriber.pUnsubscribe("events:*");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -41647,9 +42797,9 @@ pubsub.psubscribe("events:*")
 pubsub.punsubscribe("events:*")
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -41676,9 +42826,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -41695,9 +42845,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -41712,9 +42862,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # SUBSCRIBE
 Source: https://upstash.com/docs/redis/commands/pub-sub/subscribe
@@ -41759,9 +42909,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+SUBSCRIBE events
+```
+
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -41771,9 +42929,9 @@ await subscriber.subscribe("events");
 subscriber.on("message", (channel, message) => console.log(channel, message));
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -41784,9 +42942,9 @@ await subscriber.subscribe("events", (message, channel) => {
 });
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -41799,9 +42957,9 @@ for message in pubsub.listen():
     print(message)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -41828,9 +42986,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -41847,9 +43005,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -41868,9 +43026,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # UNSUBSCRIBE
 Source: https://upstash.com/docs/redis/commands/pub-sub/unsubscribe
@@ -41915,9 +43073,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
 
-<Tab title="ioredis">
+```bash
+UNSUBSCRIBE events
+```
+
+</Accordion>
+
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -41927,9 +43093,9 @@ await subscriber.subscribe("events");
 await subscriber.unsubscribe("events");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -41939,9 +43105,9 @@ await subscriber.subscribe("events", console.log);
 await subscriber.unsubscribe("events");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -41953,9 +43119,9 @@ pubsub.subscribe("events")
 pubsub.unsubscribe("events")
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -41982,9 +43148,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -42001,9 +43167,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -42018,9 +43184,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # EVAL
 Source: https://upstash.com/docs/redis/commands/scripting/eval
@@ -42093,9 +43259,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+EVAL "return ARGV[1]" 0 hello
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -42109,9 +43283,9 @@ const result = await redis.eval(script, [], ["hello"]);
 console.log(result) // "hello"
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -42121,9 +43295,9 @@ result = redis.eval("return ARGV[1]", args=["value"])
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -42133,9 +43307,9 @@ const result = await redis.eval("return ARGV[1]", "0", "value");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -42147,9 +43321,9 @@ const result = await client.eval("return ARGV[1]", { arguments: ["value"] });
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -42160,9 +43334,9 @@ result = client.eval("return ARGV[1]", 0, "value")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -42189,9 +43363,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -42204,9 +43378,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -42223,9 +43397,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # EVAL_RO
 Source: https://upstash.com/docs/redis/commands/scripting/eval-ro
@@ -42274,9 +43448,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+EVAL_RO "return ARGV[1]" 0 hello
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -42290,9 +43472,9 @@ const result = await redis.evalRo(script, [], ["hello"]);
 console.log(result) // "hello"
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -42302,9 +43484,9 @@ result = redis.eval_ro("return ARGV[1]", args=["value"])
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -42314,9 +43496,9 @@ const result = await redis.eval_ro("return ARGV[1]", "0", "value");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -42328,9 +43510,9 @@ const result = await client.evalRo("return ARGV[1]", { arguments: ["value"] });
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -42341,9 +43523,9 @@ result = client.eval_ro("return ARGV[1]", 0, "value")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -42370,9 +43552,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -42385,9 +43567,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -42404,9 +43586,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # EVALSHA
 Source: https://upstash.com/docs/redis/commands/scripting/evalsha
@@ -42458,9 +43640,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+EVALSHA fb67a0c03b48ddbf8b4c9b011e779563bdbc28cb 0 value
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -42471,9 +43661,9 @@ const result = await redis.evalsha("fb67a0c03b48ddbf8b4c9b011e779563bdbc28cb", [
 console.log(result) // "hello"
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -42483,9 +43673,9 @@ result = redis.evalsha("<sha1>", args=["value"])
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -42495,9 +43685,9 @@ const result = await redis.evalsha("<sha1>", "0", "value");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -42509,9 +43699,9 @@ const result = await client.evalSha("<sha1>", { arguments: ["value"] });
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -42522,9 +43712,9 @@ result = client.evalsha("<sha1>", 0, "value")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -42551,9 +43741,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -42566,9 +43756,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -42585,9 +43775,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # EVALSHA_RO
 Source: https://upstash.com/docs/redis/commands/scripting/evalsha-ro
@@ -42636,9 +43826,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+EVALSHA_RO fb67a0c03b48ddbf8b4c9b011e779563bdbc28cb 0 value
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -42649,9 +43847,9 @@ const result = await redis.evalshaRo("fb67a0c03b48ddbf8b4c9b011e779563bdbc28cb",
 console.log(result) // "hello"
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -42661,9 +43859,9 @@ result = redis.evalsha_ro("<sha1>", args=["value"])
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -42673,9 +43871,9 @@ const result = await redis.evalsha_ro("<sha1>", "0", "value");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -42687,9 +43885,9 @@ const result = await client.evalShaRo("<sha1>", { arguments: ["value"] });
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -42700,9 +43898,9 @@ result = client.evalsha_ro("<sha1>", 0, "value")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -42729,9 +43927,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -42744,9 +43942,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -42763,9 +43961,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # Scripting commands
 Source: https://upstash.com/docs/redis/commands/scripting/overview
@@ -42817,9 +44015,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+SCRIPT EXISTS fb67a0c03b48ddbf8b4c9b011e779563bdbc28cb
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -42832,9 +44038,9 @@ await redis.scriptExists("<sha1>", "<sha2>")
 // [1, 0]
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -42844,9 +44050,9 @@ result = redis.script_exists("<sha1>")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -42856,9 +44062,9 @@ const result = await redis.script("EXISTS", "<sha1>");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -42870,9 +44076,9 @@ const result = await client.scriptExists("<sha1>");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -42883,9 +44089,9 @@ result = client.script_exists("<sha1>")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -42912,9 +44118,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -42927,9 +44133,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -42946,9 +44152,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # SCRIPT FLUSH
 Source: https://upstash.com/docs/redis/commands/scripting/script-flush
@@ -42986,9 +44192,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
 
-<Tab title="@upstash/redis">
+```bash
+SCRIPT FLUSH
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -42998,9 +44212,9 @@ const redis = Redis.fromEnv();
 await redis.scriptFlush();
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -43010,9 +44224,9 @@ result = redis.script_flush()
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -43022,9 +44236,9 @@ const result = await redis.script("FLUSH");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -43036,9 +44250,9 @@ const result = await client.scriptFlush();
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -43049,9 +44263,9 @@ result = client.script_flush()
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -43078,9 +44292,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -43093,9 +44307,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -43111,9 +44325,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # SCRIPT KILL
 Source: https://upstash.com/docs/redis/commands/scripting/script-kill
@@ -43156,25 +44370,33 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+SCRIPT KILL
+```
 
-<Tab title="@upstash/redis">
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 <Note>
   This command is not supported yet in `upstash_redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -43184,9 +44406,9 @@ const result = await redis.script("KILL");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -43198,9 +44420,9 @@ const result = await client.scriptKill();
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -43211,9 +44433,9 @@ result = client.script_kill()
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -43240,9 +44462,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -43255,9 +44477,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -43273,9 +44495,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # SCRIPT LOAD
 Source: https://upstash.com/docs/redis/commands/scripting/script-load
@@ -43319,9 +44541,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+SCRIPT LOAD "return ARGV[1]"
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -43335,9 +44565,9 @@ const script = `
 const sha1 = await redis.scriptLoad(script);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -43347,9 +44577,9 @@ result = redis.script_load("return ARGV[1]")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -43359,9 +44589,9 @@ const result = await redis.script("LOAD", "return ARGV[1]");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -43373,9 +44603,9 @@ const result = await client.scriptLoad("return ARGV[1]");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -43386,9 +44616,9 @@ result = client.script_load("return ARGV[1]")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -43415,9 +44645,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -43430,28 +44660,28 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
+use redis::{Script, TypedCommands};
+
 fn main() -> redis::RedisResult<()> {
     let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
     let client = redis::Client::open(url)?;
     let mut connection = client.get_connection()?;
 
-    let mut command = redis::cmd("SCRIPT");
-    command.arg("LOAD");
-    command.arg("return ARGV[1]");
-    let result: redis::Value = command.query(&mut connection)?;
+    let script = Script::new("return ARGV[1]");
+    let result: String = connection.load_script(&script)?;
     println!("{result:?}");
     Ok(())
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # Search commands
 Source: https://upstash.com/docs/redis/commands/search/overview
@@ -43540,9 +44770,17 @@ Raw RESP output may be rendered differently by client or protocol settings, but
 
 ## Examples
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+SEARCH.AGGREGATE products '{}' '{"avg_price": {"$avg": {"field": "price"}}}'
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -43557,9 +44795,9 @@ const result = await products.aggregate({
 });
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -43572,9 +44810,9 @@ result = products.aggregate(
 )
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import IORedis from "ioredis";
@@ -43591,9 +44829,9 @@ const result = await products.aggregate({
 });
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -43612,17 +44850,9 @@ const result = await products.aggregate({
 });
 ```
 
-</Tab>
-
-<Tab title="Redis CLI">
-
-```bash
-SEARCH.AGGREGATE products '{}' '{"avg_price": {"$avg": {"field": "price"}}}'
-```
-
-</Tab>
+</Accordion>
 
-<Tab title="curl">
+<Accordion title="curl">
 
 ```bash
 curl -X POST https://YOUR_ENDPOINT.upstash.io \
@@ -43630,9 +44860,9 @@ curl -X POST https://YOUR_ENDPOINT.upstash.io \
   -d '["SEARCH.AGGREGATE", "products", "{}", "{\"avg_price\": {\"$avg\": {\"field\": \"price\"}}}"]'
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # SEARCH.ALIASADD
 Source: https://upstash.com/docs/redis/commands/search/search-aliasadd
@@ -43657,9 +44887,17 @@ Returns `1` if a new alias was created or `2` if an existing alias was updated,
 
 ## Examples
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
 
-<Tab title="@upstash/redis">
+```bash
+SEARCH.ALIASADD products products-v2
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -43671,9 +44909,9 @@ const result = await redis.search.alias.add({
 });
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -43685,9 +44923,9 @@ result = redis.search.alias.add(
 )
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import IORedis from "ioredis";
@@ -43701,9 +44939,9 @@ const result = await search.alias.add({
 });
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -43719,17 +44957,9 @@ const result = await search.alias.add({
 });
 ```
 
-</Tab>
-
-<Tab title="Redis CLI">
-
-```bash
-SEARCH.ALIASADD products products-v2
-```
+</Accordion>
 
-</Tab>
-
-<Tab title="curl">
+<Accordion title="curl">
 
 ```bash
 curl -X POST https://YOUR_ENDPOINT.upstash.io \
@@ -43737,9 +44967,9 @@ curl -X POST https://YOUR_ENDPOINT.upstash.io \
   -d '["SEARCH.ALIASADD", "products", "products-v2"]'
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # SEARCH.ALIASDEL
 Source: https://upstash.com/docs/redis/commands/search/search-aliasdel
@@ -43762,9 +44992,17 @@ Returns `1` if the alias was deleted or `0` if the alias was not found.
 
 ## Examples
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
 
-<Tab title="@upstash/redis">
+```bash
+SEARCH.ALIASDEL products
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -43773,9 +45011,9 @@ const redis = Redis.fromEnv();
 const result = await redis.search.alias.delete({ alias: "products" });
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -43784,9 +45022,9 @@ redis = Redis.from_env()
 result = redis.search.alias.delete(alias="products")
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import IORedis from "ioredis";
@@ -43797,9 +45035,9 @@ const search = createSearch(redis);
 const result = await search.alias.delete({ alias: "products" });
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -43812,17 +45050,9 @@ const search = createSearch(client);
 const result = await search.alias.delete({ alias: "products" });
 ```
 
-</Tab>
-
-<Tab title="Redis CLI">
-
-```bash
-SEARCH.ALIASDEL products
-```
-
-</Tab>
+</Accordion>
 
-<Tab title="curl">
+<Accordion title="curl">
 
 ```bash
 curl -X POST https://YOUR_ENDPOINT.upstash.io \
@@ -43830,9 +45060,9 @@ curl -X POST https://YOUR_ENDPOINT.upstash.io \
   -d '["SEARCH.ALIASDEL", "products"]'
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # SEARCH.COUNT
 Source: https://upstash.com/docs/redis/commands/search/search-count
@@ -43857,9 +45087,17 @@ Returns the number of matching documents as an integer. Returns `-1` if the inde
 
 ## Examples
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+SEARCH.COUNT products '{"inStock": true}'
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -43873,9 +45111,9 @@ const result = await products.count({
 console.log(result.count);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -43887,9 +45125,9 @@ result = products.count(filter={"inStock": True})
 print(result.count)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import IORedis from "ioredis";
@@ -43905,9 +45143,9 @@ const result = await products.count({
 console.log(result.count);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -43925,17 +45163,9 @@ const result = await products.count({
 console.log(result.count);
 ```
 
-</Tab>
-
-<Tab title="Redis CLI">
-
-```bash
-SEARCH.COUNT products '{"inStock": true}'
-```
-
-</Tab>
+</Accordion>
 
-<Tab title="curl">
+<Accordion title="curl">
 
 ```bash
 curl -X POST https://YOUR_ENDPOINT.upstash.io \
@@ -43943,9 +45173,9 @@ curl -X POST https://YOUR_ENDPOINT.upstash.io \
   -d '["SEARCH.COUNT", "products", "{\"inStock\": true}"]'
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # SEARCH.CREATE
 Source: https://upstash.com/docs/redis/commands/search/search-create
@@ -44003,9 +45233,17 @@ Returns `1` when the index is created. With `EXISTSOK`, returns `0` if the exist
 
 ## Examples
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+SEARCH.CREATE products ON JSON PREFIX 1 product: SCHEMA name TEXT price F64 FAST inStock BOOL
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis, s } from "@upstash/redis";
@@ -44024,9 +45262,9 @@ const products = await redis.search.createIndex({
 });
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -44045,9 +45283,9 @@ products = redis.search.create_index(
 )
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import IORedis from "ioredis";
@@ -44068,9 +45306,9 @@ const products = await search.createIndex({
 });
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -44093,17 +45331,9 @@ const products = await search.createIndex({
 });
 ```
 
-</Tab>
-
-<Tab title="Redis CLI">
-
-```bash
-SEARCH.CREATE products ON JSON PREFIX 1 product: SCHEMA name TEXT price F64 FAST inStock BOOL
-```
-
-</Tab>
+</Accordion>
 
-<Tab title="curl">
+<Accordion title="curl">
 
 ```bash
 curl -X POST https://YOUR_ENDPOINT.upstash.io \
@@ -44111,9 +45341,9 @@ curl -X POST https://YOUR_ENDPOINT.upstash.io \
   -d '["SEARCH.CREATE", "products", "ON", "JSON", "PREFIX", "1", "product:", "SCHEMA", "name", "TEXT", "price", "F64", "FAST", "inStock", "BOOL"]'
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # SEARCH.DESCRIBE
 Source: https://upstash.com/docs/redis/commands/search/search-describe
@@ -44162,9 +45392,17 @@ Returns `null` if the index does not exist.
 
 ## Examples
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+SEARCH.DESCRIBE products
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -44174,9 +45412,9 @@ const products = redis.search.index({ name: "products" });
 const description = await products.describe();
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -44186,9 +45424,9 @@ products = redis.search.index(name="products")
 description = products.describe()
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import IORedis from "ioredis";
@@ -44200,9 +45438,9 @@ const products = search.index({ name: "products" });
 const description = await products.describe();
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -44216,17 +45454,9 @@ const products = search.index({ name: "products" });
 const description = await products.describe();
 ```
 
-</Tab>
-
-<Tab title="Redis CLI">
-
-```bash
-SEARCH.DESCRIBE products
-```
-
-</Tab>
+</Accordion>
 
-<Tab title="curl">
+<Accordion title="curl">
 
 ```bash
 curl -X POST https://YOUR_ENDPOINT.upstash.io \
@@ -44234,9 +45464,9 @@ curl -X POST https://YOUR_ENDPOINT.upstash.io \
   -d '["SEARCH.DESCRIBE", "products"]'
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # SEARCH.DROP
 Source: https://upstash.com/docs/redis/commands/search/search-drop
@@ -44261,9 +45491,17 @@ Returns `1` if the index was dropped or `0` if the index was not found.
 
 ## Examples
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
 
-<Tab title="@upstash/redis">
+```bash
+SEARCH.DROP products
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -44273,9 +45511,9 @@ const products = redis.search.index({ name: "products" });
 const result = await products.drop();
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -44285,9 +45523,9 @@ products = redis.search.index(name="products")
 result = products.drop()
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import IORedis from "ioredis";
@@ -44299,9 +45537,9 @@ const products = search.index({ name: "products" });
 const result = await products.drop();
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -44315,17 +45553,9 @@ const products = search.index({ name: "products" });
 const result = await products.drop();
 ```
 
-</Tab>
-
-<Tab title="Redis CLI">
-
-```bash
-SEARCH.DROP products
-```
-
-</Tab>
+</Accordion>
 
-<Tab title="curl">
+<Accordion title="curl">
 
 ```bash
 curl -X POST https://YOUR_ENDPOINT.upstash.io \
@@ -44333,9 +45563,9 @@ curl -X POST https://YOUR_ENDPOINT.upstash.io \
   -d '["SEARCH.DROP", "products"]'
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # SEARCH.LISTALIASES
 Source: https://upstash.com/docs/redis/commands/search/search-listaliases
@@ -44360,9 +45590,17 @@ The SDKs below decode the pairs into an object or dictionary that maps each alia
 
 ## Examples
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+SEARCH.LISTALIASES
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -44372,9 +45610,9 @@ const aliases = await redis.search.alias.list();
 // { products: "products-v2" }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -44384,9 +45622,9 @@ aliases = redis.search.alias.list()
 # {"products": "products-v2"}
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import IORedis from "ioredis";
@@ -44398,9 +45636,9 @@ const aliases = await search.alias.list();
 // { products: "products-v2" }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -44414,17 +45652,9 @@ const aliases = await search.alias.list();
 // { products: "products-v2" }
 ```
 
-</Tab>
-
-<Tab title="Redis CLI">
-
-```bash
-SEARCH.LISTALIASES
-```
-
-</Tab>
+</Accordion>
 
-<Tab title="curl">
+<Accordion title="curl">
 
 ```bash
 curl -X POST https://YOUR_ENDPOINT.upstash.io \
@@ -44432,9 +45662,9 @@ curl -X POST https://YOUR_ENDPOINT.upstash.io \
   -d '["SEARCH.LISTALIASES"]'
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # SEARCH.LISTINDEXES
 Source: https://upstash.com/docs/redis/commands/search/search-listindexes
@@ -44477,9 +45707,17 @@ Returns one entry per index, sorted by index name. Each entry is a map containin
   The high-level Search APIs do not currently expose `SEARCH.LISTINDEXES`. Use each client's generic command method for this command.
 </Note>
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+SEARCH.LISTINDEXES MATCH 'product*' LIMIT 10 OFFSET 0
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -44496,9 +45734,9 @@ const indexes = await redis.exec<string[][]>([
 ]);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -44515,9 +45753,9 @@ indexes = redis.execute([
 ])
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import IORedis from "ioredis";
@@ -44534,9 +45772,9 @@ const indexes = await redis.call(
 );
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -44555,17 +45793,9 @@ const indexes = await client.sendCommand([
 ]);
 ```
 
-</Tab>
-
-<Tab title="Redis CLI">
-
-```bash
-SEARCH.LISTINDEXES MATCH 'product*' LIMIT 10 OFFSET 0
-```
-
-</Tab>
+</Accordion>
 
-<Tab title="curl">
+<Accordion title="curl">
 
 ```bash
 curl -X POST https://YOUR_ENDPOINT.upstash.io \
@@ -44573,9 +45803,9 @@ curl -X POST https://YOUR_ENDPOINT.upstash.io \
   -d '["SEARCH.LISTINDEXES", "MATCH", "product*", "LIMIT", "10", "OFFSET", "0"]'
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # SEARCH.QUERY
 Source: https://upstash.com/docs/redis/commands/search/search-query
@@ -44644,9 +45874,17 @@ When `NOCONTENT` is used, each result is `[key, score]`. When `SELECT` is used,
 
 ## Examples
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
 
-<Tab title="@upstash/redis">
+```bash
+SEARCH.QUERY products '{"name": "wireless"}' LIMIT 10 OFFSET 0
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis, s } from "@upstash/redis";
@@ -44664,9 +45902,9 @@ const results = await products.query({
 });
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -44681,9 +45919,9 @@ results = products.query(
 )
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import IORedis from "ioredis";
@@ -44703,9 +45941,9 @@ const results = await products.query({
 });
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -44727,17 +45965,9 @@ const results = await products.query({
 });
 ```
 
-</Tab>
-
-<Tab title="Redis CLI">
-
-```bash
-SEARCH.QUERY products '{"name": "wireless"}' LIMIT 10 OFFSET 0
-```
-
-</Tab>
+</Accordion>
 
-<Tab title="curl">
+<Accordion title="curl">
 
 ```bash
 curl -X POST https://YOUR_ENDPOINT.upstash.io \
@@ -44745,9 +45975,9 @@ curl -X POST https://YOUR_ENDPOINT.upstash.io \
   -d '["SEARCH.QUERY", "products", "{\"name\": \"wireless\"}", "LIMIT", "10", "OFFSET", "0"]'
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # SEARCH.REINDEX
 Source: https://upstash.com/docs/redis/commands/search/search-reindex
@@ -44774,17 +46004,17 @@ Returns `1` when the index is rebuilt or `0` if the index does not exist.
 
 ## Examples
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="Redis CLI">
+<Accordion title="Redis CLI" icon="terminal">
 
 ```bash
 SEARCH.REINDEX products
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="curl">
+<Accordion title="curl">
 
 ```bash
 curl -X POST https://YOUR_ENDPOINT.upstash.io \
@@ -44792,9 +46022,9 @@ curl -X POST https://YOUR_ENDPOINT.upstash.io \
   -d '["SEARCH.REINDEX", "products"]'
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # SEARCH.WAITINDEXING
 Source: https://upstash.com/docs/redis/commands/search/search-waitindexing
@@ -44823,9 +46053,17 @@ Returns `1` when indexing is complete or `0` if the index was not found.
 
 ## Examples
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+SEARCH.WAITINDEXING products
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -44835,9 +46073,9 @@ const products = redis.search.index({ name: "products" });
 const result = await products.waitIndexing();
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -44847,9 +46085,9 @@ products = redis.search.index(name="products")
 result = products.wait_indexing()
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import IORedis from "ioredis";
@@ -44861,9 +46099,9 @@ const products = search.index({ name: "products" });
 const result = await products.waitIndexing();
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -44877,17 +46115,9 @@ const products = search.index({ name: "products" });
 const result = await products.waitIndexing();
 ```
 
-</Tab>
-
-<Tab title="Redis CLI">
-
-```bash
-SEARCH.WAITINDEXING products
-```
-
-</Tab>
+</Accordion>
 
-<Tab title="curl">
+<Accordion title="curl">
 
 ```bash
 curl -X POST https://YOUR_ENDPOINT.upstash.io \
@@ -44895,9 +46125,9 @@ curl -X POST https://YOUR_ENDPOINT.upstash.io \
   -d '["SEARCH.WAITINDEXING", "products"]'
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # ACL
 Source: https://upstash.com/docs/redis/commands/server/acl
@@ -44961,25 +46191,33 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
 
-<Tab title="@upstash/redis">
+```bash
+ACL WHOAMI
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 <Note>
   This command is not supported yet in `upstash_redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -44989,9 +46227,9 @@ const result = await redis.acl("WHOAMI");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -45003,9 +46241,9 @@ const result = await client.aclWhoAmI();
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -45016,9 +46254,9 @@ result = client.acl_whoami()
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -45045,9 +46283,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -45060,9 +46298,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -45078,9 +46316,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # COMMAND
 Source: https://upstash.com/docs/redis/commands/server/command
@@ -45120,25 +46358,33 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+COMMAND
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 <Note>
   This command is not supported yet in `upstash_redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -45148,9 +46394,9 @@ const result = await redis.call("COMMAND");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -45162,9 +46408,9 @@ const result = await client.command();
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -45175,9 +46421,9 @@ result = client.command()
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -45204,9 +46450,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -45219,9 +46465,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -45237,9 +46483,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # CONFIG GET
 Source: https://upstash.com/docs/redis/commands/server/config-get
@@ -45285,25 +46531,33 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+CONFIG GET notify-keyspace-events
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 <Note>
   This command is not supported yet in `upstash_redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -45313,9 +46567,9 @@ const result = await redis.config("GET", "notify-keyspace-events");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -45327,9 +46581,9 @@ const result = await client.configGet("notify-keyspace-events");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -45340,9 +46594,9 @@ result = client.config_get("notify-keyspace-events")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -45369,9 +46623,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -45384,9 +46638,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -45403,9 +46657,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # CONFIG SET
 Source: https://upstash.com/docs/redis/commands/server/config-set
@@ -45452,25 +46706,33 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+CONFIG SET notify-keyspace-events Ex
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 <Note>
   This command is not supported yet in `upstash_redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -45480,9 +46742,9 @@ const result = await redis.config("SET", "notify-keyspace-events", "Ex");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -45494,9 +46756,9 @@ const result = await client.configSet("notify-keyspace-events", "Ex");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -45507,9 +46769,9 @@ result = client.config_set("notify-keyspace-events", "Ex")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -45536,9 +46798,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -45551,9 +46813,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -45571,9 +46833,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # DBSIZE
 Source: https://upstash.com/docs/redis/commands/server/dbsize
@@ -45613,9 +46875,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+DBSIZE
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -45626,9 +46896,9 @@ const keys = await redis.dbsize();
 console.log(keys) // 20
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -45638,9 +46908,9 @@ result = redis.dbsize()
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -45650,9 +46920,9 @@ const result = await redis.dbsize();
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -45664,9 +46934,9 @@ const result = await client.dbSize();
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -45677,9 +46947,9 @@ result = client.dbsize()
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -45706,9 +46976,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -45721,9 +46991,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -45739,9 +47009,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # FLUSHALL
 Source: https://upstash.com/docs/redis/commands/server/flushall
@@ -45787,9 +47057,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+FLUSHALL
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -45799,9 +47077,9 @@ const redis = Redis.fromEnv();
 await redis.flushall();
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -45811,9 +47089,9 @@ result = redis.flushall()
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -45823,9 +47101,9 @@ const result = await redis.flushall();
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -45837,9 +47115,9 @@ const result = await client.flushAll();
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -45850,9 +47128,9 @@ result = client.flushall()
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -45879,9 +47157,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -45894,27 +47172,27 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
+use redis::TypedCommands;
+
 fn main() -> redis::RedisResult<()> {
     let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
     let client = redis::Client::open(url)?;
     let mut connection = client.get_connection()?;
 
-    let mut command = redis::cmd("FLUSHALL");
-
-    let result: redis::Value = command.query(&mut connection)?;
+    let result = connection.flushall()?;
     println!("{result:?}");
     Ok(())
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # FLUSHDB
 Source: https://upstash.com/docs/redis/commands/server/flushdb
@@ -45960,9 +47238,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+FLUSHDB
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -45972,9 +47258,9 @@ const redis = Redis.fromEnv();
 await redis.flushdb();
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -45984,9 +47270,9 @@ result = redis.flushdb()
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -45996,9 +47282,9 @@ const result = await redis.flushdb();
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -46010,9 +47296,9 @@ const result = await client.flushDb();
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -46023,9 +47309,9 @@ result = client.flushdb()
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -46052,9 +47338,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -46067,27 +47353,27 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
+use redis::TypedCommands;
+
 fn main() -> redis::RedisResult<()> {
     let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
     let client = redis::Client::open(url)?;
     let mut connection = client.get_connection()?;
 
-    let mut command = redis::cmd("FLUSHDB");
-
-    let result: redis::Value = command.query(&mut connection)?;
+    let result = connection.flushdb()?;
     println!("{result:?}");
     Ok(())
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # INFO
 Source: https://upstash.com/docs/redis/commands/server/info
@@ -46133,25 +47419,33 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+INFO memory
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 <Note>
   This command is not supported yet in `upstash_redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -46161,9 +47455,9 @@ const result = await redis.info("memory");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -46175,9 +47469,9 @@ const result = await client.info("memory");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -46188,9 +47482,9 @@ result = client.info("memory")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -46217,9 +47511,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -46232,9 +47526,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -46250,9 +47544,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # MONITOR
 Source: https://upstash.com/docs/redis/commands/server/monitor
@@ -46296,9 +47590,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="ioredis">
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+MONITOR
+```
+
+</Accordion>
+
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -46312,9 +47614,9 @@ redis.monitor((error, monitor) => {
 });
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -46328,9 +47630,9 @@ await client.monitor((command) => {
 });
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -46342,9 +47644,9 @@ with client.monitor() as monitor:
         print(command)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -46361,9 +47663,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -46379,9 +47681,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # Server commands
 Source: https://upstash.com/docs/redis/commands/server/overview
@@ -46433,9 +47735,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+TIME
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -46445,9 +47755,9 @@ const result = await redis.time();
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -46457,9 +47767,9 @@ result = redis.time()
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -46469,9 +47779,9 @@ const result = await redis.time();
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -46483,9 +47793,9 @@ const result = await client.time();
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -46496,9 +47806,9 @@ result = client.time()
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -46525,9 +47835,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -46540,9 +47850,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -46558,9 +47868,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # Set commands
 Source: https://upstash.com/docs/redis/commands/set/overview
@@ -46622,9 +47932,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+SADD my-key member
+```
 
-<Tab title="@upstash/redis">
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -46638,9 +47956,9 @@ await redis.sadd("key", "a", "b", "c");
 await redis.sadd("key", "a", "b");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -46650,9 +47968,9 @@ result = redis.sadd("my-key", "member")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -46662,9 +47980,9 @@ const result = await redis.sadd("my-key", "member");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -46676,9 +47994,9 @@ const result = await client.sAdd("my-key", "member");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -46689,9 +48007,9 @@ result = client.sadd("my-key", "member")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -46718,9 +48036,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -46733,9 +48051,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -46751,9 +48069,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # SCARD
 Source: https://upstash.com/docs/redis/commands/set/scard
@@ -46791,9 +48109,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
 
-<Tab title="@upstash/redis">
+```bash
+SCARD my-key
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -46805,9 +48131,9 @@ const cardinality = await redis.scard("key");
 console.log(cardinality); // 3
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -46817,9 +48143,9 @@ result = redis.scard("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -46829,9 +48155,9 @@ const result = await redis.scard("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -46843,9 +48169,9 @@ const result = await client.sCard("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -46856,9 +48182,9 @@ result = client.scard("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -46885,9 +48211,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -46900,9 +48226,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -46918,9 +48244,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # SDIFF
 Source: https://upstash.com/docs/redis/commands/set/sdiff
@@ -46960,9 +48286,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+SDIFF set1 set2
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -46975,9 +48309,9 @@ const diff =  await redis.sdiff("set1", "set2");
 console.log(diff); // ["a", "b"]
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -46987,9 +48321,9 @@ result = redis.sdiff("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -46999,9 +48333,9 @@ const result = await redis.sdiff("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -47013,9 +48347,9 @@ const result = await client.sDiff("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -47026,9 +48360,9 @@ result = client.sdiff(["my-key"])
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -47055,9 +48389,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -47070,9 +48404,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -47088,9 +48422,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # SDIFFSTORE
 Source: https://upstash.com/docs/redis/commands/set/sdiffstore
@@ -47131,9 +48465,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+SDIFFSTORE dest set1 set2
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -47146,9 +48488,9 @@ await redis.sdiff("dest", "set1", "set2");
 console.log(diff); // ["a", "b"]
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -47158,9 +48500,9 @@ result = redis.sdiffstore("destination-key", "my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -47170,9 +48512,9 @@ const result = await redis.sdiffstore("destination-key", "my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -47184,9 +48526,9 @@ const result = await client.sDiffStore("destination-key", "my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -47197,9 +48539,9 @@ result = client.sdiffstore("destination-key", ["my-key"])
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -47226,9 +48568,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -47241,9 +48583,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -47259,9 +48601,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # SINTER
 Source: https://upstash.com/docs/redis/commands/set/sinter
@@ -47301,9 +48643,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+SINTER set1 set2
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -47316,9 +48666,9 @@ const intersection =  await redis.sinter("set1", "set2");
 console.log(intersection); // ["c"]
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -47328,9 +48678,9 @@ result = redis.sinter("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -47340,9 +48690,9 @@ const result = await redis.sinter("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -47354,9 +48704,9 @@ const result = await client.sInter("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -47367,9 +48717,9 @@ result = client.sinter(["my-key"])
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -47396,9 +48746,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -47411,9 +48761,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -47429,9 +48779,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # SINTERCARD
 Source: https://upstash.com/docs/redis/commands/set/sintercard
@@ -47477,9 +48827,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+SINTERCARD 1 my-key
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -47489,17 +48847,17 @@ const result = await redis.sintercard(["my-key"]);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 <Note>
   This command is not supported yet in `upstash_redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -47509,9 +48867,9 @@ const result = await redis.sintercard("1", "my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -47523,9 +48881,9 @@ const result = await client.sInterCard(["my-key"]);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -47536,9 +48894,9 @@ result = client.sintercard(1, ["my-key"])
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -47565,9 +48923,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -47580,9 +48938,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -47599,9 +48957,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # SINTERSTORE
 Source: https://upstash.com/docs/redis/commands/set/sinterstore
@@ -47640,9 +48998,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+SINTERSTORE destination set1 set2
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -47654,9 +49020,9 @@ await redis.sadd("set2", "c", "d", "e");
 await redis.sinterstore("destination", "set1", "set2");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -47666,9 +49032,9 @@ result = redis.sinterstore("destination-key", "my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -47678,9 +49044,9 @@ const result = await redis.sinterstore("destination-key", "my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -47692,9 +49058,9 @@ const result = await client.sInterStore("destination-key", "my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -47705,9 +49071,9 @@ result = client.sinterstore("destination-key", ["my-key"])
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -47734,9 +49100,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -47749,9 +49115,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -47767,9 +49133,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # SISMEMBER
 Source: https://upstash.com/docs/redis/commands/set/sismember
@@ -47808,9 +49174,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+SISMEMBER my-key member
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -47822,9 +49196,9 @@ const isMember =  await redis.sismember("set", "a");
 console.log(isMember); // 1
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -47834,9 +49208,9 @@ result = redis.sismember("my-key", "member")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -47846,9 +49220,9 @@ const result = await redis.sismember("my-key", "member");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -47860,9 +49234,9 @@ const result = await client.sIsMember("my-key", "member");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -47873,9 +49247,9 @@ result = client.sismember("my-key", "member")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -47902,9 +49276,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -47917,9 +49291,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -47935,9 +49309,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # SMEMBERS
 Source: https://upstash.com/docs/redis/commands/set/smembers
@@ -47975,9 +49349,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+SMEMBERS my-key
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -47989,9 +49371,9 @@ const members =  await redis.smembers("set");
 console.log(members); // ["a", "b", "c"]
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -48001,9 +49383,9 @@ result = redis.smembers("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -48013,9 +49395,9 @@ const result = await redis.smembers("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -48027,9 +49409,9 @@ const result = await client.sMembers("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -48040,9 +49422,9 @@ result = client.smembers("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -48069,9 +49451,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -48084,9 +49466,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -48102,9 +49484,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # SMISMEMBER
 Source: https://upstash.com/docs/redis/commands/set/smismember
@@ -48143,9 +49525,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+SMISMEMBER my-key member
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -48157,9 +49547,9 @@ const members =  await redis.smismember("set", ["a", "b", "d"]);
 console.log(members); // [1, 1, 0]
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -48169,9 +49559,9 @@ result = redis.smismember("my-key", "member")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -48181,9 +49571,9 @@ const result = await redis.smismember("my-key", "member");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -48195,9 +49585,9 @@ const result = await client.smIsMember("my-key", ["member"]);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -48208,9 +49598,9 @@ result = client.smismember("my-key", ["member"])
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -48237,9 +49627,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -48252,9 +49642,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -48270,9 +49660,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # SMOVE
 Source: https://upstash.com/docs/redis/commands/set/smove
@@ -48314,9 +49704,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+SMOVE source-key destination-key member
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -48330,9 +49728,9 @@ const moved =  await redis.smove("original", "destination", "a");
 // destination: ["a"]
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -48342,9 +49740,9 @@ result = redis.smove("source-key", "destination-key", "member")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -48354,9 +49752,9 @@ const result = await redis.smove("source-key", "destination-key", "member");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -48368,9 +49766,9 @@ const result = await client.sMove("source-key", "destination-key", "member");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -48381,9 +49779,9 @@ result = client.smove("source-key", "destination-key", "member")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -48410,9 +49808,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -48425,9 +49823,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -48443,9 +49841,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # SPOP
 Source: https://upstash.com/docs/redis/commands/set/spop
@@ -48486,9 +49884,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+SPOP my-key
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -48500,9 +49906,9 @@ const popped = await redis.spop("set");
 console.log(popped); // "a"
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -48512,9 +49918,9 @@ result = redis.spop("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -48524,9 +49930,9 @@ const result = await redis.spop("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -48538,9 +49944,9 @@ const result = await client.sPop("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -48551,9 +49957,9 @@ result = client.spop("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -48580,9 +49986,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -48595,9 +50001,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -48613,9 +50019,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # SRANDMEMBER
 Source: https://upstash.com/docs/redis/commands/set/srandmember
@@ -48656,9 +50062,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+SRANDMEMBER my-key
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -48670,9 +50084,9 @@ const member = await redis.srandmember("set");
 console.log(member); // "a"
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -48682,9 +50096,9 @@ result = redis.srandmember("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -48694,9 +50108,9 @@ const result = await redis.srandmember("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -48708,9 +50122,9 @@ const result = await client.sRandMember("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -48721,9 +50135,9 @@ result = client.srandmember("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -48750,9 +50164,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -48765,9 +50179,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -48783,9 +50197,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # SREM
 Source: https://upstash.com/docs/redis/commands/set/srem
@@ -48824,9 +50238,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+SREM my-key member
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -48838,9 +50260,9 @@ const removed = await redis.srem("set", "a", "b", "d");
 console.log(removed); // 2
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -48850,9 +50272,9 @@ result = redis.srem("my-key", "member")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -48862,9 +50284,9 @@ const result = await redis.srem("my-key", "member");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -48876,9 +50298,9 @@ const result = await client.sRem("my-key", "member");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -48889,9 +50311,9 @@ result = client.srem("my-key", "member")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -48918,9 +50340,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -48933,9 +50355,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -48951,9 +50373,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # SSCAN
 Source: https://upstash.com/docs/redis/commands/set/sscan
@@ -49001,9 +50423,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+SSCAN my-key 0
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -49016,9 +50446,9 @@ console.log(newCursor); // likely `0` since this is a very small set
 console.log(fields); // ["a", "ab"]
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -49028,9 +50458,9 @@ result = redis.sscan("my-key", 0)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -49040,9 +50470,9 @@ const result = await redis.sscan("my-key", "0");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -49054,9 +50484,9 @@ const result = await client.sScan("my-key", "0");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -49067,9 +50497,9 @@ result = client.sscan("my-key", 0)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -49096,9 +50526,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -49111,28 +50541,29 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
+use redis::TypedCommands;
+
 fn main() -> redis::RedisResult<()> {
     let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
     let client = redis::Client::open(url)?;
     let mut connection = client.get_connection()?;
 
-    let mut command = redis::cmd("SSCAN");
-    command.arg("my-key");
-    command.arg("0");
-    let result: redis::Value = command.query(&mut connection)?;
-    println!("{result:?}");
+    let iter: redis::Iter<String> = connection.sscan("my-key")?;
+    for member in iter {
+        println!("{member}");
+    }
     Ok(())
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # SUNION
 Source: https://upstash.com/docs/redis/commands/set/sunion
@@ -49170,9 +50601,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+SUNION set1 set2
+```
 
-<Tab title="@upstash/redis">
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -49185,9 +50624,9 @@ const union =  await redis.sunion("set1", "set2");
 console.log(union); // ["a", "b", "c", "d", "e"]
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -49197,9 +50636,9 @@ result = redis.sunion("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -49209,9 +50648,9 @@ const result = await redis.sunion("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -49223,9 +50662,9 @@ const result = await client.sUnion("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -49236,9 +50675,9 @@ result = client.sunion(["my-key"])
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -49265,9 +50704,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -49280,9 +50719,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -49298,9 +50737,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # SUNIONSTORE
 Source: https://upstash.com/docs/redis/commands/set/sunionstore
@@ -49339,9 +50778,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+SUNIONSTORE destination set1 set2
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -49353,9 +50800,9 @@ await redis.sadd("set2", "c", "d", "e");
 await redis.sunionstore("destination", "set1", "set2");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -49365,9 +50812,9 @@ result = redis.sunionstore("destination-key", "my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -49377,9 +50824,9 @@ const result = await redis.sunionstore("destination-key", "my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -49391,9 +50838,9 @@ const result = await client.sUnionStore("destination-key", "my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -49404,9 +50851,9 @@ result = client.sunionstore("destination-key", ["my-key"])
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -49433,9 +50880,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -49448,9 +50895,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -49466,9 +50913,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # BZMPOP
 Source: https://upstash.com/docs/redis/commands/sorted-set/bzmpop
@@ -49516,25 +50963,33 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+BZMPOP 1.5 1 my-key MIN
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 <Note>
   This command is not supported yet in `upstash_redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -49544,9 +50999,9 @@ const result = await redis.bzmpop("1.5", "1", "my-key", "MIN");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -49558,9 +51013,9 @@ const result = await client.bzmPop(1.5, "my-key", "MIN");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -49571,9 +51026,9 @@ result = client.bzmpop(1.5, 1, ["my-key"], min=True)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -49601,9 +51056,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -49616,30 +51071,27 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
+use redis::TypedCommands;
+
 fn main() -> redis::RedisResult<()> {
     let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
     let client = redis::Client::open(url)?;
     let mut connection = client.get_connection()?;
 
-    let mut command = redis::cmd("BZMPOP");
-    command.arg("1.5");
-    command.arg("1");
-    command.arg("my-key");
-    command.arg("MIN");
-    let result: redis::Value = command.query(&mut connection)?;
+    let result = connection.bzmpop_min(1.5, "my-key", 1)?;
     println!("{result:?}");
     Ok(())
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # BZPOPMAX
 Source: https://upstash.com/docs/redis/commands/sorted-set/bzpopmax
@@ -49684,25 +51136,33 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+BZPOPMAX my-key 1.5
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 <Note>
   This command is not supported yet in `upstash_redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -49712,9 +51172,9 @@ const result = await redis.bzpopmax("my-key", "1.5");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -49726,9 +51186,9 @@ const result = await client.bzPopMax("my-key", 1.5);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -49739,9 +51199,9 @@ result = client.bzpopmax(["my-key"], timeout=1.5)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -49769,9 +51229,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -49784,28 +51244,27 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
+use redis::TypedCommands;
+
 fn main() -> redis::RedisResult<()> {
     let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
     let client = redis::Client::open(url)?;
     let mut connection = client.get_connection()?;
 
-    let mut command = redis::cmd("BZPOPMAX");
-    command.arg("my-key");
-    command.arg("1.5");
-    let result: redis::Value = command.query(&mut connection)?;
+    let result = connection.bzpopmax("my-key", 1.5)?;
     println!("{result:?}");
     Ok(())
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # BZPOPMIN
 Source: https://upstash.com/docs/redis/commands/sorted-set/bzpopmin
@@ -49850,25 +51309,33 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
 
-<Tab title="@upstash/redis">
+```bash
+BZPOPMIN my-key 1.5
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 <Note>
   This command is not supported yet in `upstash_redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -49878,9 +51345,9 @@ const result = await redis.bzpopmin("my-key", "1.5");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -49892,9 +51359,9 @@ const result = await client.bzPopMin("my-key", 1.5);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -49905,9 +51372,9 @@ result = client.bzpopmin(["my-key"], timeout=1.5)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -49935,9 +51402,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -49950,28 +51417,27 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
+use redis::TypedCommands;
+
 fn main() -> redis::RedisResult<()> {
     let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
     let client = redis::Client::open(url)?;
     let mut connection = client.get_connection()?;
 
-    let mut command = redis::cmd("BZPOPMIN");
-    command.arg("my-key");
-    command.arg("1.5");
-    let result: redis::Value = command.query(&mut connection)?;
+    let result = connection.bzpopmin("my-key", 1.5)?;
     println!("{result:?}");
     Ok(())
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # Sorted Set commands
 Source: https://upstash.com/docs/redis/commands/sorted-set/overview
@@ -50062,9 +51528,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+ZADD my-key 1.5 member
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -50078,9 +51552,9 @@ await redis.zadd(
 );
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -50090,9 +51564,9 @@ result = redis.zadd("my-key", {"member": 1.5})
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -50102,9 +51576,9 @@ const result = await redis.zadd("my-key", "1.5", "member");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -50116,9 +51590,9 @@ const result = await client.zAdd("my-key", { score: 1.5, value: "member" });
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -50129,9 +51603,9 @@ result = client.zadd("my-key", {"member": 1.5})
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -50158,9 +51632,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -50173,9 +51647,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -50191,9 +51665,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # ZCARD
 Source: https://upstash.com/docs/redis/commands/sorted-set/zcard
@@ -50231,9 +51705,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+ZCARD my-key
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -50248,9 +51730,9 @@ const elements = await redis.zrank("key");
 console.log(elements); // 2
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -50260,9 +51742,9 @@ result = redis.zcard("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -50272,9 +51754,9 @@ const result = await redis.zcard("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -50286,9 +51768,9 @@ const result = await client.zCard("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -50299,9 +51781,9 @@ result = client.zcard("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -50328,9 +51810,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -50343,9 +51825,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -50361,9 +51843,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # ZCOUNT
 Source: https://upstash.com/docs/redis/commands/sorted-set/zcount
@@ -50405,9 +51887,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+ZCOUNT my-key 1.5 1.5
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -50422,9 +51912,9 @@ const elements = await redis.zcount("key", "(1", "+inf");
 console.log(elements); // 1
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -50434,9 +51924,9 @@ result = redis.zcount("my-key", 1.5, 1.5)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -50446,9 +51936,9 @@ const result = await redis.zcount("my-key", "1.5", "1.5");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -50460,9 +51950,9 @@ const result = await client.zCount("my-key", 1.5, 1.5);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -50473,9 +51963,9 @@ result = client.zcount("my-key", 1.5, 1.5)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -50502,9 +51992,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -50517,9 +52007,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -50535,9 +52025,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # ZDIFF
 Source: https://upstash.com/docs/redis/commands/sorted-set/zdiff
@@ -50585,17 +52075,25 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
 
-<Tab title="@upstash/redis">
+```bash
+ZDIFF 1 my-key
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -50605,9 +52103,9 @@ result = redis.zdiff(["my-key"])
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -50617,9 +52115,9 @@ const result = await redis.zdiff("1", "my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -50631,9 +52129,9 @@ const result = await client.zDiff("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -50644,9 +52142,9 @@ result = client.zdiff(["my-key"])
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -50673,9 +52171,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -50688,9 +52186,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -50707,9 +52205,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # ZDIFFSTORE
 Source: https://upstash.com/docs/redis/commands/sorted-set/zdiffstore
@@ -50755,9 +52253,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
 
-<Tab title="@upstash/redis">
+```bash
+ZDIFFSTORE destination-key 1 my-key
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -50767,9 +52273,9 @@ const redis = Redis.fromEnv();
 const values = await redis.zdiffstore("destination", 2, "key1", "key2");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -50779,9 +52285,9 @@ result = redis.zdiffstore("destination-key", ["my-key"])
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -50791,9 +52297,9 @@ const result = await redis.zdiffstore("destination-key", "1", "my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -50805,9 +52311,9 @@ const result = await client.zDiffStore("destination-key", "my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -50818,9 +52324,9 @@ result = client.zdiffstore("destination-key", ["my-key"])
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -50847,9 +52353,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -50862,9 +52368,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -50882,9 +52388,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # ZINCRBY
 Source: https://upstash.com/docs/redis/commands/sorted-set/zincrby
@@ -50930,9 +52436,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+ZINCRBY my-key 1 member
+```
 
-<Tab title="@upstash/redis">
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -50944,9 +52458,9 @@ const value = await redis.zincrby("key", 2, "member");
 console.log(value); // 3
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -50956,9 +52470,9 @@ result = redis.zincrby("my-key", 1, "member")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -50968,9 +52482,9 @@ const result = await redis.zincrby("my-key", "1", "member");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -50982,9 +52496,9 @@ const result = await client.zIncrBy("my-key", 1, "member");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -50995,9 +52509,9 @@ result = client.zincrby("my-key", 1, "member")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -51024,9 +52538,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -51039,9 +52553,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -51057,9 +52571,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # ZINTER
 Source: https://upstash.com/docs/redis/commands/sorted-set/zinter
@@ -51112,17 +52626,25 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
 
-<Tab title="@upstash/redis">
+```bash
+ZINTER 1 my-key
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -51132,9 +52654,9 @@ result = redis.zinter(["my-key"])
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -51144,9 +52666,9 @@ const result = await redis.zinter("1", "my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -51158,9 +52680,9 @@ const result = await client.zInter("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -51171,9 +52693,9 @@ result = client.zinter(["my-key"])
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -51200,9 +52722,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -51215,9 +52737,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -51234,9 +52756,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # ZINTERCARD
 Source: https://upstash.com/docs/redis/commands/sorted-set/zintercard
@@ -51276,25 +52798,33 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+ZINTERCARD 1 my-key
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 <Note>
   This command is not supported yet in `upstash_redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -51304,9 +52834,9 @@ const result = await redis.zintercard("1", "my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -51318,9 +52848,9 @@ const result = await client.zInterCard("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -51331,9 +52861,9 @@ result = client.zintercard(1, ["my-key"])
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -51360,9 +52890,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -51375,9 +52905,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -51394,9 +52924,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # ZINTERSTORE
 Source: https://upstash.com/docs/redis/commands/sorted-set/zinterstore
@@ -51446,9 +52976,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+ZINTERSTORE destination-key 1 my-key
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -51469,9 +53007,9 @@ const res = await redis.zinterstore("destination", 2, ["key1", "key2"]);
 console.log(res) // 1
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -51481,9 +53019,9 @@ result = redis.zinterstore("destination-key", ["my-key"])
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -51493,9 +53031,9 @@ const result = await redis.zinterstore("destination-key", "1", "my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -51507,9 +53045,9 @@ const result = await client.zInterStore("destination-key", "my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -51520,9 +53058,9 @@ result = client.zinterstore("destination-key", ["my-key"])
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -51549,9 +53087,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -51564,9 +53102,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -51582,9 +53120,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # ZLEXCOUNT
 Source: https://upstash.com/docs/redis/commands/sorted-set/zlexcount
@@ -51626,9 +53164,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+ZLEXCOUNT my-key - +
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -51643,9 +53189,9 @@ const elements = await redis.zlexcount("key", "two", "+");
 console.log(elements); // 1
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -51655,9 +53201,9 @@ result = redis.zlexcount("my-key", "-", "+")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -51667,9 +53213,9 @@ const result = await redis.zlexcount("my-key", "-", "+");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -51681,9 +53227,9 @@ const result = await client.zLexCount("my-key", "-", "+");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -51694,9 +53240,9 @@ result = client.zlexcount("my-key", "-", "+")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -51723,9 +53269,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -51738,9 +53284,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -51756,9 +53302,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # ZMPOP
 Source: https://upstash.com/docs/redis/commands/sorted-set/zmpop
@@ -51805,25 +53351,33 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+ZMPOP 1 my-key MIN
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 <Note>
   This command is not supported yet in `upstash_redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -51833,9 +53387,9 @@ const result = await redis.zmpop("1", "my-key", "MIN");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -51847,9 +53401,9 @@ const result = await client.zmPop("my-key", "MIN");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -51860,9 +53414,9 @@ result = client.zmpop(1, ["my-key"], min=True)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -51889,9 +53443,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -51904,29 +53458,27 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
+use redis::TypedCommands;
+
 fn main() -> redis::RedisResult<()> {
     let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
     let client = redis::Client::open(url)?;
     let mut connection = client.get_connection()?;
 
-    let mut command = redis::cmd("ZMPOP");
-    command.arg("1");
-    command.arg("my-key");
-    command.arg("MIN");
-    let result: redis::Value = command.query(&mut connection)?;
+    let result = connection.zmpop_min("my-key", 1)?;
     println!("{result:?}");
     Ok(())
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # ZMSCORE
 Source: https://upstash.com/docs/redis/commands/sorted-set/zmscore
@@ -51969,9 +53521,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+ZMSCORE my-key member
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -51989,9 +53549,9 @@ const scores = await redis.zmscore("key", ["m2", "m4"])
 console.log(scores) // [2, 4]
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -52001,9 +53561,9 @@ result = redis.zmscore("my-key", ["member"])
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -52013,9 +53573,9 @@ const result = await redis.zmscore("my-key", "member");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -52027,9 +53587,9 @@ const result = await client.zmScore("my-key", "member");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -52040,9 +53600,9 @@ result = client.zmscore("my-key", ["member"])
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -52069,9 +53629,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -52084,9 +53644,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -52102,9 +53662,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # ZPOPMAX
 Source: https://upstash.com/docs/redis/commands/sorted-set/zpopmax
@@ -52149,9 +53709,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+ZPOPMAX my-key
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -52161,9 +53729,9 @@ const redis = Redis.fromEnv();
 const popped = await redis.zpopmax("key", 4);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -52173,9 +53741,9 @@ result = redis.zpopmax("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -52185,9 +53753,9 @@ const result = await redis.zpopmax("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -52199,9 +53767,9 @@ const result = await client.zPopMax("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -52212,9 +53780,9 @@ result = client.zpopmax("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -52241,9 +53809,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -52256,9 +53824,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -52274,9 +53842,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # ZPOPMIN
 Source: https://upstash.com/docs/redis/commands/sorted-set/zpopmin
@@ -52321,9 +53889,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+ZPOPMIN my-key
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -52333,9 +53909,9 @@ const redis = Redis.fromEnv();
 const popped = await redis.zpopmin("key", 4);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -52345,9 +53921,9 @@ result = redis.zpopmin("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -52357,9 +53933,9 @@ const result = await redis.zpopmin("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -52371,9 +53947,9 @@ const result = await client.zPopMin("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -52384,9 +53960,9 @@ result = client.zpopmin("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -52413,9 +53989,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -52428,9 +54004,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -52446,9 +54022,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # ZRANDMEMBER
 Source: https://upstash.com/docs/redis/commands/sorted-set/zrandmember
@@ -52493,17 +54069,25 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+ZRANDMEMBER my-key
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -52513,9 +54097,9 @@ result = redis.zrandmember("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -52525,9 +54109,9 @@ const result = await redis.zrandmember("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -52539,9 +54123,9 @@ const result = await client.zRandMember("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -52552,9 +54136,9 @@ result = client.zrandmember("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -52581,9 +54165,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -52596,9 +54180,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -52614,9 +54198,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # ZRANGE
 Source: https://upstash.com/docs/redis/commands/sorted-set/zrange
@@ -52673,9 +54257,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+ZRANGE my-key 0 -1
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -52690,9 +54282,9 @@ const res = await redis.zrange("key", 1, 3)
 console.log(res) // ["m2"]
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -52702,9 +54294,9 @@ result = redis.zrange("my-key", 0, -1)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -52714,9 +54306,9 @@ const result = await redis.zrange("my-key", "0", "-1");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -52728,9 +54320,9 @@ const result = await client.zRange("my-key", 0, -1);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -52741,9 +54333,9 @@ result = client.zrange("my-key", 0, -1)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -52770,9 +54362,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -52785,9 +54377,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -52803,15 +54395,15 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # ZRANGEBYLEX
 Source: https://upstash.com/docs/redis/commands/sorted-set/zrangebylex
 
 <Warning>
-  Prefer [`ZRANGE`](/docs/redis/commands/sorted-set/zrange) with `BYLEX` in new code: `ZRANGE <key> <min> <max> BYLEX [LIMIT <offset> <count>]`. `ZRANGEBYLEX` is deprecated in Redis but still supported by Upstash.
+  Prefer [`ZRANGE`](/docs/redis/commands/sorted-set/zrange) with `BYLEX` in new code: `ZRANGE <key> <min> <max> BYLEX [LIMIT <offset> <count>]`.
 </Warning>
 
 Use `ZRANGEBYLEX` to list the members of a sorted set that fall in a lexicographic range.
@@ -52852,17 +54444,25 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+ZRANGEBYLEX my-key - +
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -52872,9 +54472,9 @@ result = redis.zrangebylex("my-key", "-", "+")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -52884,9 +54484,9 @@ const result = await redis.zrangebylex("my-key", "-", "+");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -52898,9 +54498,9 @@ const result = await client.zRangeByLex("my-key", "-", "+");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -52911,9 +54511,9 @@ result = client.zrangebylex("my-key", "-", "+")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -52940,9 +54540,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -52955,9 +54555,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -52973,15 +54573,15 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # ZRANGEBYSCORE
 Source: https://upstash.com/docs/redis/commands/sorted-set/zrangebyscore
 
 <Warning>
-  Prefer [`ZRANGE`](/docs/redis/commands/sorted-set/zrange) with `BYSCORE` in new code: `ZRANGE <key> <min> <max> BYSCORE [LIMIT <offset> <count>] [WITHSCORES]`. `ZRANGEBYSCORE` is deprecated in Redis but still supported by Upstash.
+  Prefer [`ZRANGE`](/docs/redis/commands/sorted-set/zrange) with `BYSCORE` in new code: `ZRANGE <key> <min> <max> BYSCORE [LIMIT <offset> <count>] [WITHSCORES]`.
 </Warning>
 
 Use `ZRANGEBYSCORE` to list the members of a sorted set whose score falls in a range, from the lowest score up.
@@ -53027,17 +54627,25 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+ZRANGEBYSCORE my-key 1.5 1.5
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -53047,9 +54655,9 @@ result = redis.zrangebyscore("my-key", "1.5", "1.5")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -53059,9 +54667,9 @@ const result = await redis.zrangebyscore("my-key", "1.5", "1.5");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -53073,9 +54681,9 @@ const result = await client.zRangeByScore("my-key", 1.5, 1.5);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -53086,9 +54694,9 @@ result = client.zrangebyscore("my-key", "1.5", "1.5")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -53115,9 +54723,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -53130,9 +54738,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -53148,9 +54756,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # ZRANGESTORE
 Source: https://upstash.com/docs/redis/commands/sorted-set/zrangestore
@@ -53199,17 +54807,25 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+ZRANGESTORE destination-key source-key -inf +inf BYSCORE
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -53219,9 +54835,9 @@ result = redis.zrangestore("destination-key", "source-key", "-inf", "+inf", sort
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -53231,9 +54847,9 @@ const result = await redis.zrangestore("my-key", "my-key", "-inf", "+inf");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -53245,9 +54861,9 @@ const result = await client.zRangeStore("my-key", "my-key", "-inf", "+inf");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -53258,9 +54874,9 @@ result = client.zrangestore("destination-key", "source-key", "-inf", "+inf", bys
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -53287,9 +54903,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -53302,9 +54918,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -53323,9 +54939,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # ZRANK
 Source: https://upstash.com/docs/redis/commands/sorted-set/zrank
@@ -53371,9 +54987,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+ZRANK my-key member
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -53383,9 +55007,9 @@ const redis = Redis.fromEnv();
 const rank = await redis.zrank("key", "member");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -53395,9 +55019,9 @@ result = redis.zrank("my-key", "member")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -53407,9 +55031,9 @@ const result = await redis.zrank("my-key", "member");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -53421,9 +55045,9 @@ const result = await client.zRank("my-key", "member");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -53434,9 +55058,9 @@ result = client.zrank("my-key", "member")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -53463,9 +55087,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -53478,9 +55102,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -53496,9 +55120,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # ZREM
 Source: https://upstash.com/docs/redis/commands/sorted-set/zrem
@@ -53537,9 +55161,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+ZREM my-key member
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -53549,9 +55181,9 @@ const redis = Redis.fromEnv();
 await redis.zrem("key", "member");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -53561,9 +55193,9 @@ result = redis.zrem("my-key", "member")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -53573,9 +55205,9 @@ const result = await redis.zrem("my-key", "member");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -53587,9 +55219,9 @@ const result = await client.zRem("my-key", "member");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -53600,9 +55232,9 @@ result = client.zrem("my-key", "member")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -53629,9 +55261,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -53644,9 +55276,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -53662,9 +55294,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # ZREMRANGEBYLEX
 Source: https://upstash.com/docs/redis/commands/sorted-set/zremrangebylex
@@ -53706,9 +55338,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+ZREMRANGEBYLEX my-key - +
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -53718,9 +55358,9 @@ const redis = Redis.fromEnv();
 await redis.zremrangebylex("key", "alpha", "omega")
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -53730,9 +55370,9 @@ result = redis.zremrangebylex("my-key", "-", "+")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -53742,9 +55382,9 @@ const result = await redis.zremrangebylex("my-key", "-", "+");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -53756,9 +55396,9 @@ const result = await client.zRemRangeByLex("my-key", "-", "+");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -53769,9 +55409,9 @@ result = client.zremrangebylex("my-key", "-", "+")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -53798,9 +55438,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -53813,9 +55453,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -53831,9 +55471,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # ZREMRANGEBYRANK
 Source: https://upstash.com/docs/redis/commands/sorted-set/zremrangebyrank
@@ -53875,9 +55515,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+ZREMRANGEBYRANK my-key 0 0
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -53887,9 +55535,9 @@ const redis = Redis.fromEnv();
 await redis.zremrangebyrank("key", 4, 20)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -53899,9 +55547,9 @@ result = redis.zremrangebyrank("my-key", 0, 0)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -53911,9 +55559,9 @@ const result = await redis.zremrangebyrank("my-key", "0", "0");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -53925,9 +55573,9 @@ const result = await client.zRemRangeByRank("my-key", 0, 0);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -53938,9 +55586,9 @@ result = client.zremrangebyrank("my-key", 0, 0)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -53967,9 +55615,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -53982,9 +55630,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -54000,9 +55648,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # ZREMRANGEBYSCORE
 Source: https://upstash.com/docs/redis/commands/sorted-set/zremrangebyscore
@@ -54044,9 +55692,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
 
-<Tab title="@upstash/redis">
+```bash
+ZREMRANGEBYSCORE my-key 1.5 1.5
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -54056,9 +55712,9 @@ const redis = Redis.fromEnv();
 await redis.zremrangebyscore("key", 2, 5)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -54068,9 +55724,9 @@ result = redis.zremrangebyscore("my-key", 1.5, 1.5)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -54080,9 +55736,9 @@ const result = await redis.zremrangebyscore("my-key", "1.5", "1.5");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -54094,9 +55750,9 @@ const result = await client.zRemRangeByScore("my-key", 1.5, 1.5);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -54107,9 +55763,9 @@ result = client.zremrangebyscore("my-key", 1.5, 1.5)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -54136,9 +55792,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -54151,9 +55807,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -54169,15 +55825,15 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # ZREVRANGE
 Source: https://upstash.com/docs/redis/commands/sorted-set/zrevrange
 
 <Warning>
-  Prefer [`ZRANGE`](/docs/redis/commands/sorted-set/zrange) with `REV` in new code: `ZRANGE <key> <start> <stop> REV [WITHSCORES]`. `ZREVRANGE` is deprecated in Redis but still supported by Upstash.
+  Prefer [`ZRANGE`](/docs/redis/commands/sorted-set/zrange) with `REV` in new code: `ZRANGE <key> <start> <stop> REV [WITHSCORES]`.
 </Warning>
 
 Use `ZREVRANGE` to list a range of members of a sorted set ordered from the highest score down.
@@ -54220,17 +55876,25 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+ZREVRANGE my-key 0 0
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -54240,9 +55904,9 @@ result = redis.zrevrange("my-key", 0, 0)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -54252,9 +55916,9 @@ const result = await redis.zrevrange("my-key", "0", "0");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -54266,9 +55930,9 @@ const result = await client.zRange("my-key", 0, 0, { REV: true });
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -54279,9 +55943,9 @@ result = client.zrevrange("my-key", 0, 0)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -54308,9 +55972,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -54323,9 +55987,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -54341,15 +56005,15 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # ZREVRANGEBYLEX
 Source: https://upstash.com/docs/redis/commands/sorted-set/zrevrangebylex
 
 <Warning>
-  Prefer [`ZRANGE`](/docs/redis/commands/sorted-set/zrange) with `BYLEX` and `REV` in new code: `ZRANGE <key> <max> <min> BYLEX REV [LIMIT <offset> <count>]`. `ZREVRANGEBYLEX` is deprecated in Redis but still supported by Upstash.
+  Prefer [`ZRANGE`](/docs/redis/commands/sorted-set/zrange) with `BYLEX` and `REV` in new code: `ZRANGE <key> <max> <min> BYLEX REV [LIMIT <offset> <count>]`.
 </Warning>
 
 Use `ZREVRANGEBYLEX` to list the members in a lexicographic range, in reverse order.
@@ -54390,17 +56054,25 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
 
-<Tab title="@upstash/redis">
+```bash
+ZREVRANGEBYLEX my-key + -
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -54410,9 +56082,9 @@ result = redis.zrevrangebylex("my-key", "+", "-")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -54422,9 +56094,9 @@ const result = await redis.zrevrangebylex("my-key", "+", "-");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -54436,9 +56108,9 @@ const result = await client.zRange("my-key", "+", "-", { BY: "LEX", REV: true })
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -54449,9 +56121,9 @@ result = client.zrevrangebylex("my-key", "+", "-")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -54478,9 +56150,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -54493,9 +56165,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -54511,15 +56183,15 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # ZREVRANGEBYSCORE
 Source: https://upstash.com/docs/redis/commands/sorted-set/zrevrangebyscore
 
 <Warning>
-  Prefer [`ZRANGE`](/docs/redis/commands/sorted-set/zrange) with `BYSCORE` and `REV` in new code: `ZRANGE <key> <max> <min> BYSCORE REV [LIMIT <offset> <count>] [WITHSCORES]`. `ZREVRANGEBYSCORE` is deprecated in Redis but still supported by Upstash.
+  Prefer [`ZRANGE`](/docs/redis/commands/sorted-set/zrange) with `BYSCORE` and `REV` in new code: `ZRANGE <key> <max> <min> BYSCORE REV [LIMIT <offset> <count>] [WITHSCORES]`.
 </Warning>
 
 Use `ZREVRANGEBYSCORE` to list the members in a score range, ordered from the highest score down.
@@ -54563,17 +56235,25 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+ZREVRANGEBYSCORE my-key 1.5 1.5
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -54583,9 +56263,9 @@ result = redis.zrevrangebyscore("my-key", "1.5", "1.5")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -54595,9 +56275,9 @@ const result = await redis.zrevrangebyscore("my-key", "1.5", "1.5");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -54609,9 +56289,9 @@ const result = await client.zRange("my-key", 1.5, 1.5, { BY: "SCORE", REV: true
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -54622,9 +56302,9 @@ result = client.zrevrangebyscore("my-key", "1.5", "1.5")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -54651,9 +56331,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -54666,9 +56346,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -54684,9 +56364,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # ZREVRANK
 Source: https://upstash.com/docs/redis/commands/sorted-set/zrevrank
@@ -54730,9 +56410,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
 
-<Tab title="@upstash/redis">
+```bash
+ZREVRANK my-key member
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -54742,9 +56430,9 @@ const redis = Redis.fromEnv();
 const rank = await redis.zrevrank("key", "member");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -54754,9 +56442,9 @@ result = redis.zrevrank("my-key", "member")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -54766,9 +56454,9 @@ const result = await redis.zrevrank("my-key", "member");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -54780,9 +56468,9 @@ const result = await client.zRevRank("my-key", "member");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -54793,9 +56481,9 @@ result = client.zrevrank("my-key", "member")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -54822,9 +56510,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -54837,9 +56525,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -54855,9 +56543,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # ZSCAN
 Source: https://upstash.com/docs/redis/commands/sorted-set/zscan
@@ -54906,9 +56594,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+ZSCAN my-key 0
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -54927,9 +56623,9 @@ console.log(newCursor); // likely `0` since this is a very small set
 console.log(members); // ["a", "ab"]
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -54939,9 +56635,9 @@ result = redis.zscan("my-key", 0)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -54951,9 +56647,9 @@ const result = await redis.zscan("my-key", "0");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -54965,9 +56661,9 @@ const result = await client.zScan("my-key", "0");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -54978,9 +56674,9 @@ result = client.zscan("my-key", 0)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -55007,9 +56703,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -55022,28 +56718,29 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
+use redis::TypedCommands;
+
 fn main() -> redis::RedisResult<()> {
     let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
     let client = redis::Client::open(url)?;
     let mut connection = client.get_connection()?;
 
-    let mut command = redis::cmd("ZSCAN");
-    command.arg("my-key");
-    command.arg("0");
-    let result: redis::Value = command.query(&mut connection)?;
-    println!("{result:?}");
+    let iter: redis::Iter<(String, f64)> = connection.zscan("my-key")?;
+    for (member, score) in iter {
+        println!("{member}: {score}");
+    }
     Ok(())
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # ZSCORE
 Source: https://upstash.com/docs/redis/commands/sorted-set/zscore
@@ -55086,9 +56783,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+ZSCORE my-key member
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -55106,9 +56811,9 @@ const score = await redis.zscore("key", "m2")
 console.log(score) // 2
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -55118,9 +56823,9 @@ result = redis.zscore("my-key", "member")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -55130,9 +56835,9 @@ const result = await redis.zscore("my-key", "member");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -55144,9 +56849,9 @@ const result = await client.zScore("my-key", "member");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -55157,9 +56862,9 @@ result = client.zscore("my-key", "member")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -55186,9 +56891,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -55201,9 +56906,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -55219,9 +56924,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # ZUNION
 Source: https://upstash.com/docs/redis/commands/sorted-set/zunion
@@ -55273,9 +56978,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
 
-<Tab title="@upstash/redis">
+```bash
+ZUNION 1 my-key
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -55285,9 +56998,9 @@ const result = await redis.zunion(1, "my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -55297,9 +57010,9 @@ result = redis.zunion(["my-key"])
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -55309,9 +57022,9 @@ const result = await redis.zunion("1", "my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -55323,9 +57036,9 @@ const result = await client.zUnion("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -55336,9 +57049,9 @@ result = client.zunion(["my-key"])
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -55365,9 +57078,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -55380,9 +57093,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -55399,9 +57112,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # ZUNIONSTORE
 Source: https://upstash.com/docs/redis/commands/sorted-set/zunionstore
@@ -55451,9 +57164,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+ZUNIONSTORE destination-key 1 my-key
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -55474,9 +57195,9 @@ const res = await redis.zunionstore("destination", 2, ["key1", "key2"]);
 console.log(res) // 2
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -55486,9 +57207,9 @@ result = redis.zunionstore("destination-key", ["my-key"])
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -55498,9 +57219,9 @@ const result = await redis.zunionstore("destination-key", "1", "my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -55512,9 +57233,9 @@ const result = await client.zUnionStore("destination-key", "my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -55525,9 +57246,9 @@ result = client.zunionstore("destination-key", ["my-key"])
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -55554,9 +57275,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -55569,9 +57290,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -55587,9 +57308,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # Streams commands
 Source: https://upstash.com/docs/redis/commands/streams/overview
@@ -55655,9 +57376,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+XACK my-key workers 0-0
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -55667,9 +57396,9 @@ const redis = Redis.fromEnv();
 const result = await redis.xack("mystream", "mygroup", "1638360173533-0");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -55679,9 +57408,9 @@ result = redis.xack("my-key", "workers", "0-0")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -55691,9 +57420,9 @@ const result = await redis.xack("my-key", "workers", "0-0");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -55705,9 +57434,9 @@ const result = await client.xAck("my-key", "workers", "0-0");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -55718,9 +57447,9 @@ result = client.xack("my-key", "workers", "0-0")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -55747,9 +57476,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -55762,9 +57491,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -55780,9 +57509,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # XACKDEL
 Source: https://upstash.com/docs/redis/commands/streams/xackdel
@@ -55827,9 +57556,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
 
-<Tab title="@upstash/redis">
+```bash
+XACKDEL my-key workers IDS 1 0-0
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -55841,9 +57578,9 @@ const result = await redis.xackdel("mystream", "mygroup", "1638360173533-0");
 console.log(result); // Array of results for each ID
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -55853,9 +57590,9 @@ result = redis.xackdel("my-key", "workers", "0-0")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -55865,9 +57602,9 @@ const result = await redis.call("XACKDEL", "my-key", "workers", "IDS", "1", "0-0
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -55879,9 +57616,9 @@ const result = await client.xAckDel("my-key", "workers", "0-0");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -55892,9 +57629,9 @@ result = client.xackdel("my-key", "workers", "0-0")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -55921,9 +57658,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -55936,9 +57673,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -55954,9 +57691,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # XADD
 Source: https://upstash.com/docs/redis/commands/streams/xadd
@@ -56007,9 +57744,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
 
-<Tab title="@upstash/redis">
+```bash
+XADD my-key * field value
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -56019,9 +57764,9 @@ const redis = Redis.fromEnv();
 const result = await redis.xadd("mystream", "*", { name: "John Doe", age: 30 });
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -56031,9 +57776,9 @@ result = redis.xadd("my-key", "*", {"field": "value"})
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -56043,9 +57788,9 @@ const result = await redis.xadd("my-key", "*", "field", "value");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -56057,9 +57802,9 @@ const result = await client.xAdd("my-key", "*", { field: "value" });
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -56070,9 +57815,9 @@ result = client.xadd("my-key", {"field": "value"})
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -56099,9 +57844,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -56114,9 +57859,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -56132,9 +57877,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # XAUTOCLAIM
 Source: https://upstash.com/docs/redis/commands/streams/xautoclaim
@@ -56180,9 +57925,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+XAUTOCLAIM my-key workers worker-1 60000 0-0
+```
 
-<Tab title="@upstash/redis">
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -56198,9 +57951,9 @@ const result = await redis.xautoclaim(
 );
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -56210,9 +57963,9 @@ result = redis.xautoclaim("my-key", "workers", "worker-1", 60000, "0-0")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -56222,9 +57975,9 @@ const result = await redis.xautoclaim("my-key", "workers", "worker-1", "60000",
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -56236,9 +57989,9 @@ const result = await client.xAutoClaim("my-key", "workers", "worker-1", 60000, "
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -56249,9 +58002,9 @@ result = client.xautoclaim("my-key", "workers", "worker-1", 60000, "0-0")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -56279,9 +58032,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -56294,31 +58047,35 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
+use redis::streams::StreamAutoClaimOptions;
+use redis::TypedCommands;
+
 fn main() -> redis::RedisResult<()> {
     let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");
     let client = redis::Client::open(url)?;
     let mut connection = client.get_connection()?;
 
-    let mut command = redis::cmd("XAUTOCLAIM");
-    command.arg("my-key");
-    command.arg("workers");
-    command.arg("worker-1");
-    command.arg("min-idle-time");
-    command.arg("start");
-    let result: redis::Value = command.query(&mut connection)?;
+    let result = connection.xautoclaim_options(
+        "my-key",
+        "workers",
+        "worker-1",
+        60000,
+        "0-0",
+        StreamAutoClaimOptions::default(),
+    )?;
     println!("{result:?}");
     Ok(())
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # XCLAIM
 Source: https://upstash.com/docs/redis/commands/streams/xclaim
@@ -56376,9 +58133,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+XCLAIM my-key workers worker-1 60000 0-0
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -56394,9 +58159,9 @@ const result = await redis.xclaim(
 );
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -56406,9 +58171,9 @@ result = redis.xclaim("my-key", "workers", "worker-1", 60000, "0-0")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -56418,9 +58183,9 @@ const result = await redis.xclaim("my-key", "workers", "worker-1", "60000", "0-0
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -56432,9 +58197,9 @@ const result = await client.xClaim("my-key", "workers", "worker-1", 60000, "0-0"
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -56445,9 +58210,9 @@ result = client.xclaim("my-key", "workers", "worker-1", 60000, ["0-0"])
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -56475,9 +58240,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -56490,9 +58255,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -56508,9 +58273,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # XDEL
 Source: https://upstash.com/docs/redis/commands/streams/xdel
@@ -56551,9 +58316,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+XDEL my-key 0-0
+```
 
-<Tab title="@upstash/redis">
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -56563,9 +58336,9 @@ const redis = Redis.fromEnv();
 const result = await redis.xdel("mystream", "1638360173533-0");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -56575,9 +58348,9 @@ result = redis.xdel("my-key", "0-0")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -56587,9 +58360,9 @@ const result = await redis.xdel("my-key", "0-0");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -56601,9 +58374,9 @@ const result = await client.xDel("my-key", "0-0");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -56614,9 +58387,9 @@ result = client.xdel("my-key", "0-0")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -56643,9 +58416,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -56658,9 +58431,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -56676,9 +58449,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # XDELEX
 Source: https://upstash.com/docs/redis/commands/streams/xdelex
@@ -56722,9 +58495,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+XDELEX my-key IDS 1 0-0
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -56736,9 +58517,9 @@ const result = await redis.xdelex("mystream", "1638360173533-0");
 console.log(result); // Array of results for each ID
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -56748,9 +58529,9 @@ result = redis.xdelex("my-key", "0-0")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -56760,9 +58541,9 @@ const result = await redis.xdelex("my-key", "IDS", "1", "0-0");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -56774,9 +58555,9 @@ const result = await client.xDelEx("my-key", "0-0");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -56787,9 +58568,9 @@ result = client.xdelex("my-key", "0-0")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -56816,9 +58597,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -56831,9 +58612,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -56849,9 +58630,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # XGROUP
 Source: https://upstash.com/docs/redis/commands/streams/xgroup
@@ -56902,9 +58683,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+XGROUP CREATE events workers $ MKSTREAM
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -56919,9 +58708,9 @@ const result = await redis.xgroup("mystream", {
 });
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -56931,9 +58720,9 @@ result = redis.xgroup_create("events", "workers", "$", mkstream=True)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -56943,9 +58732,9 @@ const result = await redis.xgroup("CREATE", "events", "workers", "$", "MKSTREAM"
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -56957,9 +58746,9 @@ const result = await client.xGroupCreate("events", "workers", "$", { MKSTREAM: t
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -56970,9 +58759,9 @@ result = client.xgroup_create("events", "workers", "$", mkstream=True)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -56999,9 +58788,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -57014,9 +58803,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -57032,9 +58821,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # XINFO CONSUMERS
 Source: https://upstash.com/docs/redis/commands/streams/xinfo-consumers
@@ -57073,9 +58862,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
 
-<Tab title="@upstash/redis">
+```bash
+XINFO CONSUMERS my-key workers
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -57088,9 +58885,9 @@ const result = await redis.xinfo("my-key", {
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -57100,9 +58897,9 @@ result = redis.xinfo_consumers("my-key", "workers")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -57112,9 +58909,9 @@ const result = await redis.xinfo("CONSUMERS", "my-key", "workers");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -57126,9 +58923,9 @@ const result = await client.xInfoConsumers("my-key", "workers");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -57139,9 +58936,9 @@ result = client.xinfo_consumers("my-key", "workers")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -57168,9 +58965,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -57183,9 +58980,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -57201,9 +58998,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # XINFO GROUPS
 Source: https://upstash.com/docs/redis/commands/streams/xinfo-groups
@@ -57241,9 +59038,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+XINFO GROUPS my-key
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -57253,9 +59058,9 @@ const result = await redis.xinfo("my-key", { type: "GROUPS" });
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -57265,9 +59070,9 @@ result = redis.xinfo_groups("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -57277,9 +59082,9 @@ const result = await redis.xinfo("GROUPS", "my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -57291,9 +59096,9 @@ const result = await client.xInfoGroups("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -57304,9 +59109,9 @@ result = client.xinfo_groups("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -57333,9 +59138,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -57348,9 +59153,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -57366,9 +59171,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # XINFO STREAM
 Source: https://upstash.com/docs/redis/commands/streams/xinfo-stream
@@ -57409,25 +59214,33 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+XINFO STREAM my-key
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 <Note>
   This command is not supported yet in `upstash_redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -57437,9 +59250,9 @@ const result = await redis.xinfo("STREAM", "my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -57451,9 +59264,9 @@ const result = await client.xInfoStream("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -57464,9 +59277,9 @@ result = client.xinfo_stream("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -57493,9 +59306,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -57508,9 +59321,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -57526,9 +59339,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # XLEN
 Source: https://upstash.com/docs/redis/commands/streams/xlen
@@ -57566,9 +59379,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+XLEN my-key
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -57578,9 +59399,9 @@ const redis = Redis.fromEnv();
 const result = await redis.xlen("mystream");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -57590,9 +59411,9 @@ result = redis.xlen("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -57602,9 +59423,9 @@ const result = await redis.xlen("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -57616,9 +59437,9 @@ const result = await client.xLen("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -57629,9 +59450,9 @@ result = client.xlen("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -57658,9 +59479,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -57673,9 +59494,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -57691,9 +59512,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # XPENDING
 Source: https://upstash.com/docs/redis/commands/streams/xpending
@@ -57740,9 +59561,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+XPENDING my-key workers
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -57752,9 +59581,9 @@ const redis = Redis.fromEnv();
 const result = await redis.xpending("mystream", "mygroup", "-", "+", 10);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -57764,9 +59593,9 @@ result = redis.xpending("my-key", "workers")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -57776,9 +59605,9 @@ const result = await redis.xpending("my-key", "workers");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -57790,9 +59619,9 @@ const result = await client.xPending("my-key", "workers");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -57803,9 +59632,9 @@ result = client.xpending("my-key", "workers")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -57832,9 +59661,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -57847,9 +59676,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -57865,9 +59694,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # XRANGE
 Source: https://upstash.com/docs/redis/commands/streams/xrange
@@ -57910,9 +59739,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+XRANGE my-key - +
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -57922,9 +59759,9 @@ const redis = Redis.fromEnv();
 const result = await redis.xrange("mystream", "-", "+");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -57934,9 +59771,9 @@ result = redis.xrange("my-key", "-", "+")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -57946,9 +59783,9 @@ const result = await redis.xrange("my-key", "-", "+");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -57960,9 +59797,9 @@ const result = await client.xRange("my-key", "-", "+");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -57973,9 +59810,9 @@ result = client.xrange("my-key", "-", "+")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -58002,9 +59839,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -58017,9 +59854,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -58035,9 +59872,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # XREAD
 Source: https://upstash.com/docs/redis/commands/streams/xread
@@ -58089,9 +59926,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+XREAD STREAMS my-key 0-0
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -58101,9 +59946,9 @@ const redis = Redis.fromEnv();
 const result = await redis.xread("mystream", "0-0");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -58113,9 +59958,9 @@ result = redis.xread({"my-key": "0-0"})
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -58125,9 +59970,9 @@ const result = await redis.xread("STREAMS", "my-key", "0-0");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -58139,9 +59984,9 @@ const result = await client.xRead({ key: "my-key", id: "0-0" });
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -58152,9 +59997,9 @@ result = client.xread({"my-key": "0-0"})
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -58181,9 +60026,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -58196,9 +60041,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -58214,9 +60059,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # XREADGROUP
 Source: https://upstash.com/docs/redis/commands/streams/xreadgroup
@@ -58271,9 +60116,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+XREADGROUP GROUP workers worker-1 STREAMS my-key 0-0
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -58283,9 +60136,9 @@ const redis = Redis.fromEnv();
 const result = await redis.xreadgroup("mygroup", "consumer1", "mystream", ">");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -58295,9 +60148,9 @@ result = redis.xreadgroup("workers", "worker-1", {"my-key": "0-0"})
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -58307,9 +60160,9 @@ const result = await redis.xreadgroup("GROUP", "workers", "worker-1", "STREAMS",
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -58321,9 +60174,9 @@ const result = await client.xReadGroup("workers", "worker-1", { key: "my-key", i
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -58334,9 +60187,9 @@ result = client.xreadgroup("workers", "worker-1", {"my-key": "0-0"})
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -58363,9 +60216,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -58378,9 +60231,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -58401,9 +60254,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # XREVRANGE
 Source: https://upstash.com/docs/redis/commands/streams/xrevrange
@@ -58446,9 +60299,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+XREVRANGE my-key + -
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -58458,9 +60319,9 @@ const redis = Redis.fromEnv();
 const result = await redis.xrevrange("mystream", "+", "-");
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -58470,9 +60331,9 @@ result = redis.xrevrange("my-key", "+", "-")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -58482,9 +60343,9 @@ const result = await redis.xrevrange("my-key", "+", "-");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -58496,9 +60357,9 @@ const result = await client.xRevRange("my-key", "+", "-");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -58509,9 +60370,9 @@ result = client.xrevrange("my-key", "+", "-")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -58538,9 +60399,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -58553,9 +60414,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -58571,9 +60432,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # XTRIM
 Source: https://upstash.com/docs/redis/commands/streams/xtrim
@@ -58619,9 +60480,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+XTRIM my-key MAXLEN 100
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -58635,9 +60504,9 @@ const result = await redis.xtrim("mystream", {
 });
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -58647,9 +60516,9 @@ result = redis.xtrim("my-key", maxlen=100)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -58659,9 +60528,9 @@ const result = await redis.xtrim("my-key", "MAXLEN", "100");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -58673,9 +60542,9 @@ const result = await client.xTrim("my-key", "MAXLEN", 100);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -58686,9 +60555,9 @@ result = client.xtrim("my-key", maxlen=100)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -58715,9 +60584,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -58730,9 +60599,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -58748,9 +60617,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # APPEND
 Source: https://upstash.com/docs/redis/commands/string/append
@@ -58789,9 +60658,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+APPEND my-key value
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -58802,9 +60679,9 @@ await redis.append(key, "Hello");
 // returns 5
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -58814,9 +60691,9 @@ result = redis.append("my-key", "value")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -58826,9 +60703,9 @@ const result = await redis.append("my-key", "value");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -58840,9 +60717,9 @@ const result = await client.append("my-key", "value");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -58853,9 +60730,9 @@ result = client.append("my-key", "value")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -58882,9 +60759,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -58897,9 +60774,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -58915,9 +60792,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # DECR
 Source: https://upstash.com/docs/redis/commands/string/decr
@@ -58955,9 +60832,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+DECR my-key
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -58969,9 +60854,9 @@ await redis.decr("key");
 // returns 5
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -58981,9 +60866,9 @@ result = redis.decr("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -58993,9 +60878,9 @@ const result = await redis.decr("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -59007,9 +60892,9 @@ const result = await client.decr("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -59020,9 +60905,9 @@ result = client.decr("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -59049,9 +60934,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -59064,9 +60949,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -59082,9 +60967,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # DECRBY
 Source: https://upstash.com/docs/redis/commands/string/decrby
@@ -59123,9 +61008,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+DECRBY my-key 1
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -59137,9 +61030,9 @@ await redis.decrby("key", 4);
 // returns 2
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -59149,9 +61042,9 @@ result = redis.decrby("my-key", 1)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -59161,9 +61054,9 @@ const result = await redis.decrby("my-key", "1");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -59175,9 +61068,9 @@ const result = await client.decrBy("my-key", 1);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -59188,9 +61081,9 @@ result = client.decrby("my-key", 1)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -59217,9 +61110,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -59232,9 +61125,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -59250,9 +61143,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # DELEX
 Source: https://upstash.com/docs/redis/commands/string/delex
@@ -59299,25 +61192,33 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+DELEX lock:job-1 IFEQ worker-1
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 <Note>
   This command is not supported yet in `upstash_redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -59327,9 +61228,9 @@ const result = await redis.call("DELEX", "lock:job-1", "IFEQ", "worker-1");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -59341,9 +61242,9 @@ const result = await client.delEx("lock:job-1", { condition: "IFEQ", matchValue:
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -59354,9 +61255,9 @@ result = client.execute_command("DELEX", "lock:job-1", "IFEQ", "worker-1")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -59383,9 +61284,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -59398,9 +61299,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -59416,9 +61317,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # DIGEST
 Source: https://upstash.com/docs/redis/commands/string/digest
@@ -59463,25 +61364,33 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+DIGEST lock:job-1
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 <Note>
   This command is not supported yet in `@upstash/redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 <Note>
   This command is not supported yet in `upstash_redis`.
 </Note>
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -59491,9 +61400,9 @@ const result = await redis.call("DIGEST", "lock:job-1");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -59505,9 +61414,9 @@ const result = await client.digest("lock:job-1");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -59518,9 +61427,9 @@ result = client.execute_command("DIGEST", "lock:job-1")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -59547,9 +61456,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -59562,9 +61471,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -59580,9 +61489,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # GET
 Source: https://upstash.com/docs/redis/commands/string/get
@@ -59620,9 +61529,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+GET my-key
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -59641,9 +61558,9 @@ if (!value) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -59653,9 +61570,9 @@ result = redis.get("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -59665,9 +61582,9 @@ const result = await redis.get("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -59679,9 +61596,9 @@ const result = await client.get("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -59692,9 +61609,9 @@ result = client.get("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -59721,9 +61638,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -59736,9 +61653,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -59754,9 +61671,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # GETDEL
 Source: https://upstash.com/docs/redis/commands/string/getdel
@@ -59794,9 +61711,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+GETDEL my-key
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -59811,9 +61736,9 @@ await redis.getdel<MyType>("key");
 // returns {a: 1, b: "2"}
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -59823,9 +61748,9 @@ result = redis.getdel("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -59835,9 +61760,9 @@ const result = await redis.getdel("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -59849,9 +61774,9 @@ const result = await client.getDel("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -59862,9 +61787,9 @@ result = client.getdel("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -59891,9 +61816,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -59906,9 +61831,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -59924,9 +61849,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # GETEX
 Source: https://upstash.com/docs/redis/commands/string/getex
@@ -59969,9 +61894,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+GETEX my-key
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -59981,9 +61914,9 @@ const result = await redis.getex("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -59993,9 +61926,9 @@ result = redis.getex("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -60005,9 +61938,9 @@ const result = await redis.getex("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -60019,9 +61952,9 @@ const result = await client.getEx("my-key", { type: "PX", value: 1000 });
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -60032,9 +61965,9 @@ result = client.getex("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -60061,9 +61994,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -60076,9 +62009,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -60094,9 +62027,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # GETRANGE
 Source: https://upstash.com/docs/redis/commands/string/getrange
@@ -60142,9 +62075,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+GETRANGE my-key 0 1
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -60154,9 +62095,9 @@ const redis = Redis.fromEnv();
 const substring = await redis.getrange("key", 2, 4);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -60166,9 +62107,9 @@ result = redis.getrange("my-key", "0", "1")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -60178,9 +62119,9 @@ const result = await redis.getrange("my-key", "0", "1");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -60192,9 +62133,9 @@ const result = await client.getRange("my-key", 0, 1);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -60205,9 +62146,9 @@ result = client.getrange("my-key", "0", "1")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -60234,9 +62175,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -60249,9 +62190,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -60267,15 +62208,15 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # GETSET
 Source: https://upstash.com/docs/redis/commands/string/getset
 
 <Warning>
-  Prefer [`SET`](/docs/redis/commands/string/set) with the `GET` argument in new code: `SET <key> <value> GET`. `GETSET` is deprecated in Redis but still supported by Upstash.
+  Prefer [`SET`](/docs/redis/commands/string/set) with the `GET` argument in new code: `SET <key> <value> GET`.
 </Warning>
 
 Use `GETSET` to set a new value and get the previous one in a single atomic step.
@@ -60314,9 +62255,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+GETSET my-key value
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -60326,9 +62275,9 @@ const redis = Redis.fromEnv();
 const oldValue = await redis.getset("key", newValue);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -60338,9 +62287,9 @@ result = redis.getset("my-key", "value")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -60350,9 +62299,9 @@ const result = await redis.getset("my-key", "value");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -60364,9 +62313,9 @@ const result = await client.getSet("my-key", "value");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -60377,9 +62326,9 @@ result = client.getset("my-key", "value")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -60406,9 +62355,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -60421,9 +62370,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -60439,9 +62388,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # INCR
 Source: https://upstash.com/docs/redis/commands/string/incr
@@ -60481,9 +62430,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+INCR my-key
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -60495,9 +62452,9 @@ await redis.incr("key");
 // returns 7
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -60507,9 +62464,9 @@ result = redis.incr("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -60519,9 +62476,9 @@ const result = await redis.incr("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -60533,9 +62490,9 @@ const result = await client.incr("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -60546,9 +62503,9 @@ result = client.incr("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -60575,9 +62532,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -60590,9 +62547,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -60608,9 +62565,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # INCRBY
 Source: https://upstash.com/docs/redis/commands/string/incrby
@@ -60651,9 +62608,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+INCRBY my-key 1
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -60665,9 +62630,9 @@ await redis.incrby("key", 4);
 // returns 10
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -60677,9 +62642,9 @@ result = redis.incrby("my-key", 1)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -60689,9 +62654,9 @@ const result = await redis.incrby("my-key", "1");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -60703,9 +62668,9 @@ const result = await client.incrBy("my-key", 1);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -60716,9 +62681,9 @@ result = client.incrby("my-key", 1)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -60745,9 +62710,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -60760,9 +62725,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -60778,9 +62743,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # INCRBYFLOAT
 Source: https://upstash.com/docs/redis/commands/string/incrbyfloat
@@ -60825,9 +62790,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+INCRBYFLOAT my-key 1.5
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -60839,9 +62812,9 @@ await redis.incrbyfloat("key", 4,5);
 // returns 10.5
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -60851,9 +62824,9 @@ result = redis.incrbyfloat("my-key", 1.5)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -60863,9 +62836,9 @@ const result = await redis.incrbyfloat("my-key", "1.5");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -60877,9 +62850,9 @@ const result = await client.incrByFloat("my-key", 1.5);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -60890,9 +62863,9 @@ result = client.incrbyfloat("my-key", 1.5)
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -60919,9 +62892,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -60934,9 +62907,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -60952,9 +62925,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # MGET
 Source: https://upstash.com/docs/redis/commands/string/mget
@@ -60994,9 +62967,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
 
-<Tab title="@upstash/redis">
+```bash
+MGET key1 key2 key3
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -61011,9 +62992,9 @@ const values = await redis.mget<MyType>("key1", "key2", "key3");
 // values.length -> 3
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -61023,9 +63004,9 @@ result = redis.mget("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -61035,9 +63016,9 @@ const result = await redis.mget("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -61049,9 +63030,9 @@ const result = await client.mGet(["my-key"]);
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -61062,9 +63043,9 @@ result = client.mget("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -61091,9 +63072,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -61106,9 +63087,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -61124,9 +63105,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # MSET
 Source: https://upstash.com/docs/redis/commands/string/mset
@@ -61166,9 +63147,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+MSET key1 1 key2 hello
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -61182,9 +63171,9 @@ await redis.mset({
 });
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -61194,9 +63183,9 @@ result = redis.mset({"my-key": "value"})
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -61206,9 +63195,9 @@ const result = await redis.mset("my-key", "value");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -61220,9 +63209,9 @@ const result = await client.mSet({ "my-key": "value" });
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -61233,9 +63222,9 @@ result = client.mset({"my-key": "value"})
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -61262,9 +63251,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -61277,9 +63266,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -61295,9 +63284,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # MSETNX
 Source: https://upstash.com/docs/redis/commands/string/msetnx
@@ -61335,9 +63324,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+MSETNX key1 value1 key2 value2
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -61350,9 +63347,9 @@ redis.msetnx({
 })
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -61362,9 +63359,9 @@ result = redis.msetnx({"my-key": "value"})
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -61374,9 +63371,9 @@ const result = await redis.msetnx("my-key", "value");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -61388,9 +63385,9 @@ const result = await client.mSetNX({ "my-key": "value" });
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -61401,9 +63398,9 @@ result = client.msetnx({"my-key": "value"})
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -61430,9 +63427,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -61445,9 +63442,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -61463,9 +63460,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # String commands
 Source: https://upstash.com/docs/redis/commands/string/overview
@@ -61499,7 +63496,7 @@ Source: https://upstash.com/docs/redis/commands/string/overview
 Source: https://upstash.com/docs/redis/commands/string/psetex
 
 <Warning>
-  Prefer [`SET`](/docs/redis/commands/string/set) with the `PX` argument in new code: `SET <key> <value> PX <milliseconds>`. `PSETEX` is deprecated in Redis but still supported by Upstash.
+  Prefer [`SET`](/docs/redis/commands/string/set) with the `PX` argument in new code: `SET <key> <value> PX <milliseconds>`.
 </Warning>
 
 Use `PSETEX` to set a value together with a lifetime in milliseconds.
@@ -61539,9 +63536,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
 
-<Tab title="@upstash/redis">
+```bash
+PSETEX my-key 1000 value
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -61551,9 +63556,9 @@ const result = await redis.psetex("my-key", 1000, "value");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -61563,9 +63568,9 @@ result = redis.psetex("my-key", 1000, "value")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -61575,9 +63580,9 @@ const result = await redis.psetex("my-key", "1000", "value");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -61589,9 +63594,9 @@ const result = await client.pSetEx("my-key", 1000, "value");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -61602,9 +63607,9 @@ result = client.psetex("my-key", 1000, "value")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -61632,9 +63637,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -61647,9 +63652,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -61665,9 +63670,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # SET
 Source: https://upstash.com/docs/redis/commands/string/set
@@ -61724,9 +63729,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+SET my-key value
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -61736,9 +63749,9 @@ const redis = Redis.fromEnv();
 await redis.set("my-key", {my: "value"});
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -61748,9 +63761,9 @@ result = redis.set("my-key", "value")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -61760,9 +63773,9 @@ const result = await redis.set("my-key", "value");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -61774,9 +63787,9 @@ const result = await client.set("my-key", "value");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -61787,9 +63800,9 @@ result = client.set("my-key", "value")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -61816,9 +63829,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -61831,9 +63844,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -61849,15 +63862,15 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # SETEX
 Source: https://upstash.com/docs/redis/commands/string/setex
 
 <Warning>
-  Prefer [`SET`](/docs/redis/commands/string/set) with the `EX` argument in new code: `SET <key> <value> EX <seconds>`. `SETEX` is deprecated in Redis but still supported by Upstash.
+  Prefer [`SET`](/docs/redis/commands/string/set) with the `EX` argument in new code: `SET <key> <value> EX <seconds>`.
 </Warning>
 
 Use `SETEX` to set a value together with a lifetime in seconds.
@@ -61897,9 +63910,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+SETEX my-key 1000 value
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -61909,9 +63930,9 @@ const result = await redis.setex("my-key", 1000, "value");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -61921,9 +63942,9 @@ result = redis.setex("my-key", 1000, "value")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -61933,9 +63954,9 @@ const result = await redis.setex("my-key", "1000", "value");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -61947,9 +63968,9 @@ const result = await client.setEx("my-key", 1000, "value");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -61960,9 +63981,9 @@ result = client.setex("my-key", 1000, "value")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -61990,9 +64011,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -62005,9 +64026,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -62023,15 +64044,15 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # SETNX
 Source: https://upstash.com/docs/redis/commands/string/setnx
 
 <Warning>
-  Prefer [`SET`](/docs/redis/commands/string/set) with the `NX` argument in new code: `SET <key> <value> NX`. `SETNX` is deprecated in Redis but still supported by Upstash.
+  Prefer [`SET`](/docs/redis/commands/string/set) with the `NX` argument in new code: `SET <key> <value> NX`.
 </Warning>
 
 Use `SETNX` to set a value only if the key does not already exist.
@@ -62070,9 +64091,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
 
-<Tab title="@upstash/redis">
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+SETNX my-key value
+```
+
+</Accordion>
+
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -62082,9 +64111,9 @@ const result = await redis.setnx("my-key", "value");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -62094,9 +64123,9 @@ result = redis.setnx("my-key", "value")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -62106,9 +64135,9 @@ const result = await redis.setnx("my-key", "value");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -62120,9 +64149,9 @@ const result = await client.setNX("my-key", "value");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -62133,9 +64162,9 @@ result = client.setnx("my-key", "value")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -62162,9 +64191,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -62177,9 +64206,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -62195,9 +64224,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # SETRANGE
 Source: https://upstash.com/docs/redis/commands/string/setrange
@@ -62239,9 +64268,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+SETRANGE my-key 0 value
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -62255,9 +64292,9 @@ console.log(length); // 10
 // The value of "key" is now "helloredis"
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -62267,9 +64304,9 @@ result = redis.setrange("my-key", 0, "value")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -62279,9 +64316,9 @@ const result = await redis.setrange("my-key", "0", "value");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -62293,9 +64330,9 @@ const result = await client.setRange("my-key", 0, "value");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -62306,9 +64343,9 @@ result = client.setrange("my-key", 0, "value")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -62335,9 +64372,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -62350,9 +64387,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -62368,9 +64405,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # STRLEN
 Source: https://upstash.com/docs/redis/commands/string/strlen
@@ -62408,9 +64445,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+STRLEN my-key
+```
+
+</Accordion>
 
-<Tab title="@upstash/redis">
+<Accordion title="@upstash/redis" icon="node-js" iconType="brands">
 
 ```ts
 import { Redis } from "@upstash/redis";
@@ -62422,9 +64467,9 @@ const length = await redis.strlen("key");
 console.log(length); // 10
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="upstash_redis">
+<Accordion title="upstash_redis" icon="python" iconType="brands">
 
 ```python
 from upstash_redis import Redis
@@ -62434,9 +64479,9 @@ result = redis.strlen("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -62446,9 +64491,9 @@ const result = await redis.strlen("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -62460,9 +64505,9 @@ const result = await client.strLen("my-key");
 console.log(result);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -62473,9 +64518,9 @@ result = client.strlen("my-key")
 print(result)
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 package main
@@ -62502,9 +64547,9 @@ func main() {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -62517,9 +64562,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 use redis::TypedCommands;
@@ -62535,9 +64580,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # DISCARD
 Source: https://upstash.com/docs/redis/commands/transactions/discard
@@ -62579,9 +64624,19 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+MULTI
+SET balance 100
+DISCARD
+```
+
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -62592,9 +64647,9 @@ await client.set("balance", "100");
 await client.discard();
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -62605,9 +64660,9 @@ await client.sendCommand(["SET", "balance", "100"]);
 await client.sendCommand(["DISCARD"]);
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -62619,9 +64674,9 @@ with client.pipeline(transaction=True) as pipe:
     pipe.reset()
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 ctx := context.Background()
@@ -62634,9 +64689,9 @@ pipe.Set(ctx, "balance", "100", 0)
 pipe.Discard()
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -62650,9 +64705,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")));
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -62663,9 +64718,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # EXEC
 Source: https://upstash.com/docs/redis/commands/transactions/exec
@@ -62709,9 +64764,19 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+MULTI
+SET balance 100
+EXEC
+```
+
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -62720,9 +64785,9 @@ const client = new Redis(process.env.REDIS_URL!);
 const result = await client.multi().set("balance", "100").exec();
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -62731,9 +64796,9 @@ const client = await createClient({ url: process.env.REDIS_URL }).connect();
 const result = await client.multi().set("balance", "100").exec();
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -62744,9 +64809,9 @@ with client.pipeline(transaction=True) as pipe:
     result = pipe.set("balance", "100").execute()
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 ctx := context.Background()
@@ -62760,9 +64825,9 @@ result, err := pipe.Exec(ctx)
 if err != nil { panic(err) }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -62776,9 +64841,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")));
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -62795,9 +64860,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # MULTI
 Source: https://upstash.com/docs/redis/commands/transactions/multi
@@ -62841,9 +64906,19 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+MULTI
+SET balance 100
+EXEC
+```
+
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -62852,9 +64927,9 @@ const client = new Redis(process.env.REDIS_URL!);
 const result = await client.multi().set("balance", "100").exec();
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -62863,9 +64938,9 @@ const client = await createClient({ url: process.env.REDIS_URL }).connect();
 const result = await client.multi().set("balance", "100").exec();
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -62876,9 +64951,9 @@ with client.pipeline(transaction=True) as pipe:
     result = pipe.set("balance", "100").execute()
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 ctx := context.Background()
@@ -62892,9 +64967,9 @@ result, err := pipe.Exec(ctx)
 if err != nil { panic(err) }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -62908,9 +64983,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")));
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -62927,9 +65002,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # Transactions commands
 Source: https://upstash.com/docs/redis/commands/transactions/overview
@@ -62982,9 +65057,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+UNWATCH
+```
+
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -62994,9 +65077,9 @@ await client.watch("balance");
 await client.unwatch();
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -63006,9 +65089,9 @@ await client.watch("balance");
 await client.unwatch();
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -63020,9 +65103,9 @@ with client.pipeline() as pipe:
     pipe.unwatch()
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 ctx := context.Background()
@@ -63036,9 +65119,9 @@ err = client.Watch(ctx, func(tx *redis.Tx) error {
 if err != nil { panic(err) }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -63050,9 +65133,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -63067,9 +65150,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # WATCH
 Source: https://upstash.com/docs/redis/commands/transactions/watch
@@ -63115,9 +65198,17 @@ The reply reports the result of the operation. Error replies have the same shape
 
 TCP examples use the TLS `REDIS_URL` from the Upstash console. REST examples use `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`.
 
-<Tabs>
+<AccordionGroup>
+
+<Accordion title="Redis CLI" icon="terminal">
+
+```bash
+WATCH balance
+```
+
+</Accordion>
 
-<Tab title="ioredis">
+<Accordion title="ioredis" icon="node-js" iconType="brands">
 
 ```ts
 import Redis from "ioredis";
@@ -63127,9 +65218,9 @@ await client.watch("balance");
 const result = await client.multi().set("balance", "100").exec();
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="node-redis">
+<Accordion title="node-redis" icon="node-js" iconType="brands">
 
 ```ts
 import { createClient } from "redis";
@@ -63139,9 +65230,9 @@ await client.watch("balance");
 const result = await client.multi().set("balance", "100").exec();
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-py">
+<Accordion title="redis-py" icon="python" iconType="brands">
 
 ```python
 import os
@@ -63155,9 +65246,9 @@ with client.pipeline() as pipe:
     result = pipe.execute()
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="go-redis">
+<Accordion title="go-redis" icon="golang" iconType="brands">
 
 ```go
 ctx := context.Background()
@@ -63175,9 +65266,9 @@ err = client.Watch(ctx, func(tx *redis.Tx) error {
 if err != nil { panic(err) }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="jedis">
+<Accordion title="jedis" icon="java" iconType="brands">
 
 ```java
 import java.net.URI;
@@ -63193,9 +65284,9 @@ try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {
 }
 ```
 
-</Tab>
+</Accordion>
 
-<Tab title="redis-rs">
+<Accordion title="redis-rs" icon="rust" iconType="brands">
 
 ```rust
 fn main() -> redis::RedisResult<()> {
@@ -63210,9 +65301,9 @@ fn main() -> redis::RedisResult<()> {
 }
 ```
 
-</Tab>
+</Accordion>
 
-</Tabs>
+</AccordionGroup>
 
 # Auto Upgrade
 Source: https://upstash.com/docs/redis/features/auto-upgrade