Put the github.com link after getjson.de/. The answer is the README, the issue with its comments, the release or the file as Markdown or text. No token, 0 credits.
curl https://getjson.de/https://github.com/cli/cli/issues/4
{
"source": {
"url": "https://github.com/cli/cli/issues/4",
"finalUrl": "https://github.com/cli/cli/issues/4",
"kind": "issue",
"platform": "github",
"provider": "github",
"fetchedAt": "2026-10-27T21:23:57.691Z",
"cached": false
},
"content": {
"title": "Task list – Oct. 7th",
"author": {
"name": "probablycorey",
"handle": "@probablycorey",
"url": "https://github.com/probablycorey"
},
"publishedDate": "2019-10-07T18:46:56.000Z",
"language": null,
"engagement": {
"comments": 5,
"reactions": 0
},
"hashtags": [],
"mentions": [],
"linkedContent": [],
"truncated": false,
"text": "State: closed\n\nHi @github/ce-cli, This is a more granular task list than what is listed in [Neha's demo planning doc](https://docs.google.com/document/d/18ym-_xjFTSXe0-xzgaBn13Su7MEhWfLE5qSNPJV4M0A/edit). \r\n\r\nIf you want to share what you a …",
"wordCount": 447
},
"meta": null,
"wall": null,
"result": null
}Recorded from https://getjson.de on 2026-10-27 with no key. Long text is cut and ends in " …".
curl -G https://getjson.de/https://github.com/cli/cli/issues/4 --data-urlencode 'schema={"type":"object","properties":{"tasks":{"type":"array","items":{"type":"object","properties":{"task":{"type":"string"},"done":{"type":"boolean"}}}}}}'Without a key a network has 3 schema calls a day. The call waits up to 60 s and fills result, validated against the schema. No answer of this call is recorded on this page.
The MCP tool read needs no key. Connect, then call it:
claude mcp add --transport http getjson https://getjson.de/mcp
{
"name": "read",
"arguments": {
"url": "https://github.com/cli/cli/issues/4"
}
}The tool answers with the same envelope as text.
getJSON reads any content a user or an agent points at, a web page or a file, and returns JSON in your schema, validated. Try and use it without an account. Guide for agents