What this tests

loopsparsing

Point your client at this specimen and find out — before prod does — whether it bounds loops, or loops unboundedly until the invoice arrives.

Anatomy

Every response hands back a next_cursor pointing at itself — the off-by-one that turns "while next is not null" into an infinite self-fetching loop, billing both ends forever. The API is not broken. It is returning a perfectly valid page that happens to be the same page, again, like a lift whose doors open onto the same floor every time. A polite paginator bounds pages or detects a cycle — has seen this before, probably in its own code, and learned humility. An impolite one learns about it from the invoice, or from the rate limiter, which will show up eventually like a bailiff with a 429. The specimen: two items, one self-referential cursor, and an education in loop invariants. Your client either notices it's seen this page before or it doesn't, and the difference between those two clients is measured in dollars per hour.

Replay it

curl -i https://faultydata.com/r/FD-2026-042

// response appears here

Signature

{Status:200 Headers:map[] Body:{"items":[{"id":1,"name":"ada"},{"id":2,"name":"bo"}],"next_cursor":"same","next":"/r/FD-2026-042"} Corrupt: Delay:<nil> Flaky:<nil> Sequence:<nil> Drip:<nil> StallAfter:0 Hang:false Reset:false Raw: Phases:[]}

Keep digging

FD-2026-101 — Infinite pagination cursor FD-2026-011 — Truncated JSON body FD-2026-012 — Malformed JSON (trailing comma) FD-2026-013 — Wrong types in a valid envelope FD-2026-014 — Encoding mismatch (claims UTF-8, sends Latin-1) FD-2026-015 — UTF-8 BOM prefix