What ChatGPT and Claude Desktop Actually Need to Access the Reddit API

Neither ChatGPT nor Claude Desktop needs a custom SDK, a plugin, or a line of bespoke integration code to call a real API. Strip away the branding and every AI-assistant integration boils down to two things: a machine-readable description of what the API can do, and a revocable credential in a format the assistant knows how to send. That's the whole surface — which is why ThreadSnoop ships a complete OpenAPI spec and a real MCP server instead of a ChatGPT plugin here and a Claude extension there.

What does an AI assistant actually need to call an API?

Two things, and only two things:

1. A machine-readable description of the API
   — an OpenAPI spec (REST), or an MCP server's tool list (same idea,
   different transport: both just enumerate endpoints/tools, their
   parameters, and what each one returns)

2. A revocable credential and its auth format
   — e.g. header: x-api-key: YOUR_KEY

Give an assistant those two things and it can plan calls, fill in parameters, and read the results back — the same way it reasons about anything else you hand it. It doesn't need us to write a ChatGPT plugin or a Claude-specific extension, because the assistant itself already knows how to read a spec and attach a header; that capability is built into the platform, not into our integration. That's the whole reason no custom SDK, plugin, or per-platform integration code is what covers every AI surface we've seen someone actually use — just a spec at https://api.threadsnoop.com/openapi.json and an MCP server at https://api.threadsnoop.com/mcp.

ChatGPT and Claude Desktop: two paths, same idea

ChatGPT reads the OpenAPI spec through Custom GPT Actions — import the URL, set header auth, done; the full walkthrough is in connecting ChatGPT to Reddit. Worth knowing if you're choosing between paths: OpenAI documents its own native MCP “developer mode” / custom connectors as available to Pro, Plus, Business, Enterprise, and Edu plans specifically on the web, with an OAuth-or-pasted-token auth flow rather than a plain custom-header field — and desktop coverage isn't confirmed either way in OpenAI's own docs. Custom GPT Actions, by contrast, work identically on ChatGPT web and the desktop app, since Desktop is just a native wrapper around the same account with no separate integration surface. So if you want something that behaves the same on ChatGPT web and desktop today, Actions/OpenAPI is the more dependable path — not chasing ChatGPT's native connector feature.

Claude Desktop doesn't have a general “import an OpenAPI spec” feature the way ChatGPT's GPT builder does — MCP genuinely is Claude's extensibility mechanism, not one option among several. That makes it the natural fit here, and it already works today in both Claude Code and Claude Desktop with a real API key header, no waiting on a platform feature to land. The setup is one command or one config block; see giving Claude access to Reddit for the exact steps. If your Claude Code session would rather skip MCP and read the spec straight from its shell instead, that path exists too — see giving Claude Code access via an OpenAPI spec.

The spec has to be right, not just present

Handing an assistant a spec instead of a person a doc page changes what “good documentation” means. A person skimming docs tries the two or three things they need and moves on; an assistant calling the API mechanically, from the spec, will eventually hit every parameter combination the spec technically allows — including ones no human ever tried by hand. We learned this the practical way: real usage surfaced a case where our docs weren't precise enough about which values are actually valid for the fields= query parameter, and we tightened it. Once your API is being called by something reading the spec instead of a person skimming it, gaps in that spec become real bugs fast — worth keeping it accurate as you learn what real usage looks like. (More on the parameters themselves in the practical API guide.)

Frequently asked questions