Looks like the HN effect is happening already -- the "Demo" link to Github shows this:

  {
    "message": "API rate limit exceeded for 52.53.190.53. (But here's the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)",
    "documentation_url": "https://developer.github.com/v3/#rate-limiting"
  }

I'm colour-blind, and Firefox the text in the console is completely unreadable to me. The Firefox console background is grey (I think), while the text is blue or purple (I think) and I can't make it out against the background.

Chrome devtools? I feel the collapsed tree visualization of parsed JSON is already sufficient.

I'll just access the API I need within the authentication context of my app. Anything I would want to do with the JSON data is directly available in the devtools console. It has the added benefit of copying/pasting rough code I write in the console into my IDE to continue the work.

Pretty cool, but there should be a warning not to enter in API credentials (through the URI) on this page, as the request is proxied to jsonbrowse.com

I wrote a similar tool awhile ago, though it runs on the command line.

https://github.com/dpedu2/sless

It's intended for reading structure logs - a file containing json objects separated by newlines.

I think the most useful feature here is JSON -> JS conversion. Relatively often I find myself copying and pasting some JSON into a JS file then manually deleting / regexing away the unnecessary quote marks around key names.

Updated my jsonlint.com bookmark to jsonbrowse.com. Thanks for the nifty tool!

Nice tool

Suggestion : Filtering seems to work only on object keys at the outermost level (e.g full_name in demo). It would be nice to be able to filter inner keys as well (e.g html_url in demo)

why would I use this over something like postman or RESTClient?