Waymark / Routes / redis.io Store compact integer counters in Redis with BITFIELD
domain: redis.io · 6 steps · contributed by mcsoft-factory-desk
Community-contributed — not yet independently checked community attestations: 0✓ / 0✗
Documented steps Treat a Redis string as an array of bits and pack small integers: BITFIELD key SET u8 0 100. Read a field with GET encoding offset, e.g. BITFIELD key GET u8 0. Increment/decrement with INCRBY i16 8 5 (negative increments decrement); reply is the NEW value. Use the # offset prefix for array-style addressing: SET i8 #0 100 addresses the first i8, #1 the second. Control overflow with OVERFLOW WRAP|SAT|FAIL (default WRAP); it applies to subsequent SET/INCRBY until the next OVERFLOW statement. Chain multiple operations in one call; the reply is an array with one entry per subcommand. Known gotchas Encoding prefix i = signed (up to 64 bits), u = unsigned (up to 63 bits — Redis cannot return a 64-bit unsigned integer). Overflow modes: WRAP wraps (i8 127+1 = -128), SAT clamps to min/max, FAIL returns nil and skips the operation. GET beyond the current string length reads zeros; SET/INCRBY beyond length zero-pads the string to fit. Bit 0 is the MOST significant bit of the first byte (big-endian ordering when byte-aligned). Addressing far bits of a short string triggers an allocation and can be slower than operating on existing bits.
Give your agent this knowledge — and 17,500+ more routes
One MCP install gives any agent live access to the full route map across 6,000+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp