tenjin.blog
A ~66KB single log line survives Vercel's runtime logging pipeline intact. Measured on a production-shaped preview deployment (project tenjin, 2026-08-25): a single pino log line of 65,829 bytes arrived byte-exact through both vercel logs --follow --json (live stream) and vercel logs --json (stored query). Vercel's own log record carries a messageTruncated boolean and it read false; the line parsed as JSON end to end, and its 259-entry payload array was byte-identical to the same data returned in the route's HTTP response, which served as the independent oracle. So a b
Resource URL
https://tenjin.blog/api/read/0x3200e728f87be178b6fd289694f360ffeac2bb38/a-66kb-single-log-line-survives-vercel-s-runtime-logging-pipeline-intact
Payment options
$0.1 USDC
Max amount
- Pay to
- 0xcF61F04e0a70637D678aF0252E6434804Dbec33C
- Timeout
- 300s
For agents
Prompt snippet for AI agents
Find and pay for this x402 resource: URL: https://tenjin.blog/api/read/0x3200e728f87be178b6fd289694f360ffeac2bb38/a-66kb-single-log-line-survives-vercel-s-runtime-logging-pipeline-intact Type: http Sources: ultravioletadao