This is not our API. This repository is an independent, third-party profile of a company's publicly available API surface, maintained by API Evangelist. API Evangelist does not operate, host, resell, or support this company's APIs, and is not affiliated with or endorsed by the company unless stated on the profile.
Where the information came from. Everything here is assembled from material a member of the public can reach with a browser and no credentials — the company's own website, developer portal and documentation, the specifications it publishes for public use (OpenAPI, AsyncAPI, JSON Schema,
apis.json,llms.txtand similar), its public repositories, and its public status, pricing and changelog pages. Nothing here is obtained by breaching a system, defeating an access control, or using credentials of any kind.The rating is an independent assessment. The Kin Score and Agent Readiness rating are independently calculated scores of a company's public API artifacts, produced by API Evangelist against a published rubric. They are not certifications, endorsements, security assessments, or audits, and they score published artifacts — not the quality, safety, or security of the software.
Corrections, re-scores, and removal are free. No partnership, contract, or purchase is required, and you do not need to justify the request.
- Something wrong? Open an issue on this repository, or email info@apievangelist.com.
- Published something new? Ask for a re-score and we will re-run the rating.
- Want the listing taken down? Say so and we will honor it. The profile is reduced to your company name, a factual description, and a link to your own site, and the company is recorded as unrated — never scored zero for having asked.
Response times. Acknowledgement within one business day; removal or restriction within two business days; corrections and re-scores within five business days.
Not from the company, and here with a question? You are welcome here — we would rather be the front line and point you the right way than have a good report go nowhere. What this repository can answer is narrow, though, so it is worth knowing who you are actually looking for:
- A question about how the API works, an account, billing, or a bug in the service — that is the company's own support, not us. We profile this API; we do not operate it and cannot see your account.
- A bug in an open-source project we only catalog — file it on that project's own repository. This has happened with a real and correct bug report that reached us instead of the people who could fix it, which helped nobody.
- Anything about this listing itself — the description, the tags, the rating, a missing or wrong artifact — is ours. Open an issue here.
- Not sure, or something general about API Evangelist or APIs.io — open an issue on the APIs.io Inbox and we will route it.
This repository contains no software, and we will never ask you to download anything. There is no build, release, installer, or binary here — only text and machine-readable API descriptions, so there is nothing here that can be "corrupt" or need "repairing". Any issue, comment, or email claiming otherwise and offering a download link is not from us and is hostile. Do not follow the link; it is a lure. Report it to GitHub and, if you like, tell us at info@apievangelist.com so we can take it down.
On a security or compliance team? Email info@apievangelist.com with security in the subject line and you will get a person, not a form. We will tell you exactly which public URLs this profile was built from so your team can see the same surface we did, and we will take the listing down on request while you work through it.
Full detail: Where this data comes from
Stack Exchange is the network of Q&A communities founded by Joel Spolsky and Jeff Atwood and headlined by Stack Overflow, the largest community of software developers on the web. The Stack Exchange API v2.3 (api.stackexchange.com) is a single, read-mostly HTTP/JSON interface that spans 180+ Q&A sites — Stack Overflow, Server Fault, Super User, Ask Ubuntu, Stats, Math Overflow, and the long tail of topical communities — and exposes the entire Q&A graph (questions, answers, comments, users, tags, badges, reputation, revisions, notifications, inbox, suggested-edits, network sites) under a uniform method surface. Stack Exchange also operates Stack Overflow for Teams (private knowledge bases with its own v3 REST API) and ships an official Stack Overflow MCP server that grounds AI agents in community-verified content.
URL: Visit APIs.json URL
Run: Capabilities Using Naftiko
- Q And A, Developer Community, Knowledge Graph, Stack Overflow, Stack Exchange, Reputation, Tags, Community, MCP, AI Grounding
- Created: 2026-05-28
- Modified: 2026-05-29
Public, read-mostly HTTP/JSON API spanning all 180+ Stack Exchange sites. All method families — questions, answers, comments, users, tags, badges, sites, search, /me, access-tokens, notifications, inbox, events, revisions, info, reputation, privileges, suggested-edits, posts — live under a single base URL with a uniform response wrapper (items, has_more, page, quota_max, quota_remaining, backoff). Read access requires no auth; writes (posting, voting, flagging, accepting) require OAuth 2.0 with the appropriate scopes (write_access, private_info, no_expiry).
Human URL: https://api.stackexchange.com/docs
Base URL: https://api.stackexchange.com/2.3
- Stack Exchange, Public API, Q And A, Read-Mostly, OAuth 2.0
- Documentation
- OpenAPI
- SignUp
- Authentication
- TermsOfService
- Throttling
- Filters
- ChangeLog
- SDK — .NET (StacMan)
- NaftikoCapability
- NaftikoCapability
- NaftikoCapability
- NaftikoCapability
- NaftikoCapability
- NaftikoCapability
- NaftikoCapability
- NaftikoCapability
- NaftikoCapability
- NaftikoCapability
- NaftikoCapability
- NaftikoCapability
- NaftikoCapability
- NaftikoCapability
- NaftikoCapability
- NaftikoCapability
Newer REST API powering Stack Overflow for Teams (private/internal instances). Resource-oriented (questions, answers, articles, comments, tags, users, collections, communities) with full CRUD and bearer-token auth. This is the API the official TypeScript SDK and Terraform provider target; it is distinct from the public v2.3 API.
Human URL: https://stackoverflowteams.help/en/articles/9085836-api-v3-overview
Base URL: https://api.stackoverflowteams.com/v3/teams/{team}/
- Stack Overflow for Teams, Internal API, REST, Bearer Token
- Documentation
- SDK — TypeScript SDK
- SDK — TypeScript SDK Source
- Tools — Terraform Provider
- Tools — Backstage Plugin
- Tools — LangChain Integration
- Website
- Documentation
- DeveloperPortal
- GitHubOrganization
- Blog
- TermsOfService
- PrivacyPolicy
- StatusPage
- ApplicationRegistration
- PublicAPIsListing
- Tools — MCP Server (Stack Overflow)
- Tools — MCP Server Documentation
- Tools — Stack Exchange Data Explorer
- Tools — Stacks Design System
- Plans
- RateLimits
- Rules
- Vocabulary
| Name | Description |
|---|---|
| Network-Wide Q&A Graph | Single API surface spans 180+ communities. Use the site parameter (stackoverflow, serverfault, superuser, askubuntu, stats, mathoverflow, …) to switch context without changing endpoints. |
| Vectorized IDs | Most methods accept up to 100 semicolon-delimited IDs in a single request (e.g., /questions/{ids}, /users/{ids}, /answers/{ids}), making bulk fetch and join workloads cheap. |
| Filter System | Custom response filters let consumers project exactly the fields they need, dramatically reducing payload size. Filters are created once via /filters/create and reused. |
| Compressed JSON | All responses are gzip-compressed by default; the wire payload is roughly 30-50% the size of an unconditioned JSON body. |
| Quota and Backoff Discipline | Every response advertises quota_max, quota_remaining, and an optional backoff integer. Clients must honor the backoff before re-querying the same method or risk being throttled at 503 / banned. |
| OAuth 2.0 Write Access | Read is unauthenticated. Write methods (post answer, create comment, vote, flag, accept) require an OAuth 2.0 access token issued via explicit or implicit flows registered on stackapps.com. |
| /me Convenience Methods | Every /users/{ids}/... method has a /me/... equivalent that infers the user from the access token, simplifying agent code paths. |
| Site Discovery | /sites enumerates every Q&A community on the network with its api_site_parameter, audience, launch date, and styling — the canonical way to bootstrap a multi-site integration. |
| AI Grounding via MCP | The official Stack Overflow MCP server exposes search, retrieve, and ground tools so MCP-compatible clients (Claude Desktop, Cursor, VS Code) can reach community-verified answers without bespoke integration. |
| Name | Description |
|---|---|
| AI Answer Grounding | Ground LLM responses in real Stack Overflow questions and answers — either directly via /search and /questions methods or through the official MCP server — to reduce hallucinations on technical topics. |
| Developer Reputation Scoring | Pull /users, /users/{ids}/reputation, badge counts, and tag scores to build developer reputation, expertise, and hiring-signal pipelines. |
| Community Analytics | Aggregate /questions, /tags, /tags/{tags}/info, and /sites data to track technology adoption, tag velocity, and community health across the network. |
| Personal Activity Dashboards | Use /me, /me/inbox, /me/notifications, /me/timeline, /me/answers, and /me/questions to build personal dashboards of a user's own activity, reputation, and unread events. |
| Tag Tracking and Triage | Watch /tags/{tags}/info, /questions?tagged=…, /search/advanced, and /questions/no-answers to triage incoming questions for OSS projects and vendor support teams. |
| Knowledge Base Mirroring | Periodically sweep /questions with a filter and a since-date to mirror Q&A into an internal knowledge base or RAG index, respecting the API quota and backoff. |
| Moderation Workbench | Combine /suggested-edits, /flags, /posts, and /revisions surfaces (with a moderator access token) to build moderation review queues. |
| Stack Overflow for Teams Integrations | Use the v3 Teams API plus the Terraform provider and Backstage plugin to provision questions, articles, and tags from CI/CD pipelines. |
| Name | Description |
|---|---|
| Claude Desktop / Cursor / VS Code via MCP | The Stack Overflow MCP server plugs directly into any MCP-compatible client, giving AI agents a typed search/retrieve interface to community content. |
| LangChain | Official LangChain integration for Stack Overflow for Teams enables retrieval and chat over private Teams content from LangChain pipelines. |
| Backstage | Backstage plugin (backstage-stackoverflow) surfaces Stack Overflow for Teams content inside Backstage developer portals. |
| Terraform | Terraform provider (terraform-provider-stackoverflow) manages questions, answers, and articles in Stack Overflow for Teams as code. |
| StacMan (.NET) | Long-standing .NET client for Stack Exchange API v2 (StackExchange/StacMan) covering the public v2.3 surface. |
| Name | Description |
|---|---|
| Public API v2.3 | Read-mostly, unauthenticated public access to the full Q&A graph across 180+ sites. Default integration path for developer tools, dashboards, community analytics, and AI grounding. |
| Stack Overflow for Teams API v3 | Private REST API for Stack Overflow for Teams customers, used by the TypeScript SDK, Terraform provider, Backstage plugin, and LangChain integration. |
| Stack Overflow MCP Server | Beta MCP server that lets MCP-compatible AI clients search, retrieve, and ground answers in Stack Overflow content with simple OAuth onboarding. |
| Stack Exchange Data Explorer | SQL-style query interface for the Stack Exchange data dumps, used for analytics workloads that exceed the API quota. |
Machine-readable API specifications organized by format.
- stackexchange-api-v2-3-access-token-schema.json
- stackexchange-api-v2-3-answer-schema.json
- stackexchange-api-v2-3-badge-count-schema.json
- stackexchange-api-v2-3-badge-schema.json
- stackexchange-api-v2-3-comment-schema.json
- stackexchange-api-v2-3-event-schema.json
- stackexchange-api-v2-3-filter-schema.json
- stackexchange-api-v2-3-inbox-item-schema.json
- stackexchange-api-v2-3-info-schema.json
- stackexchange-api-v2-3-notification-schema.json
- stackexchange-api-v2-3-post-schema.json
- stackexchange-api-v2-3-privilege-item-schema.json
- stackexchange-api-v2-3-question-schema.json
- stackexchange-api-v2-3-reputation-change-schema.json
- stackexchange-api-v2-3-revision-schema.json
- stackexchange-api-v2-3-shallow-user-schema.json
- stackexchange-api-v2-3-site-schema.json
- stackexchange-api-v2-3-suggested-edit-schema.json
- stackexchange-api-v2-3-tag-schema.json
- stackexchange-api-v2-3-tag-score-schema.json
- stackexchange-api-v2-3-tag-synonym-schema.json
- stackexchange-api-v2-3-user-schema.json
- stackexchange-api-v2-3-access-token-structure.json
- stackexchange-api-v2-3-answer-structure.json
- stackexchange-api-v2-3-badge-count-structure.json
- stackexchange-api-v2-3-badge-structure.json
- stackexchange-api-v2-3-comment-structure.json
- stackexchange-api-v2-3-event-structure.json
- stackexchange-api-v2-3-filter-structure.json
- stackexchange-api-v2-3-inbox-item-structure.json
- stackexchange-api-v2-3-info-structure.json
- stackexchange-api-v2-3-notification-structure.json
- stackexchange-api-v2-3-post-structure.json
- stackexchange-api-v2-3-privilege-item-structure.json
- stackexchange-api-v2-3-question-structure.json
- stackexchange-api-v2-3-reputation-change-structure.json
- stackexchange-api-v2-3-revision-structure.json
- stackexchange-api-v2-3-shallow-user-structure.json
- stackexchange-api-v2-3-site-structure.json
- stackexchange-api-v2-3-suggested-edit-structure.json
- stackexchange-api-v2-3-tag-score-structure.json
- stackexchange-api-v2-3-tag-structure.json
- stackexchange-api-v2-3-tag-synonym-structure.json
- stackexchange-api-v2-3-user-structure.json
- stackexchange-api-v2-3-access-token-example.json
- stackexchange-api-v2-3-answer-example.json
- stackexchange-api-v2-3-badge-count-example.json
- stackexchange-api-v2-3-badge-example.json
- stackexchange-api-v2-3-comment-example.json
- stackexchange-api-v2-3-event-example.json
- stackexchange-api-v2-3-filter-example.json
- stackexchange-api-v2-3-inbox-item-example.json
- stackexchange-api-v2-3-info-example.json
- stackexchange-api-v2-3-notification-example.json
- stackexchange-api-v2-3-post-example.json
- stackexchange-api-v2-3-privilege-item-example.json
- stackexchange-api-v2-3-question-example.json
- stackexchange-api-v2-3-reputation-change-example.json
- stackexchange-api-v2-3-revision-example.json
- stackexchange-api-v2-3-shallow-user-example.json
- stackexchange-api-v2-3-site-example.json
- stackexchange-api-v2-3-suggested-edit-example.json
- stackexchange-api-v2-3-tag-example.json
- stackexchange-api-v2-3-tag-score-example.json
- stackexchange-api-v2-3-tag-synonym-example.json
- stackexchange-api-v2-3-user-example.json
Self-contained Naftiko capabilities — one file per business surface (OpenAPI tag), each with consumes + REST + MCP exposers inlined.
| Capability | Tools | File |
|---|---|---|
| Stack Exchange API v2.3 — Access Tokens | 3 | stack-exchange-access-tokens.yaml |
| Stack Exchange API v2.3 — Answers | 4 | stack-exchange-answers.yaml |
| Stack Exchange API v2.3 — Badges | 5 | stack-exchange-badges.yaml |
| Stack Exchange API v2.3 — Comments | 2 | stack-exchange-comments.yaml |
| Stack Exchange API v2.3 — Events | 1 | stack-exchange-events.yaml |
| Stack Exchange API v2.3 — Filters | 2 | stack-exchange-filters.yaml |
| Stack Exchange API v2.3 — Info | 1 | stack-exchange-info.yaml |
| Stack Exchange API v2.3 — Me | 12 | stack-exchange-me.yaml |
| Stack Exchange API v2.3 — Posts | 5 | stack-exchange-posts.yaml |
| Stack Exchange API v2.3 — Questions | 9 | stack-exchange-questions.yaml |
| Stack Exchange API v2.3 — Revisions | 1 | stack-exchange-revisions.yaml |
| Stack Exchange API v2.3 — Search | 4 | stack-exchange-search.yaml |
| Stack Exchange API v2.3 — Sites | 1 | stack-exchange-sites.yaml |
| Stack Exchange API v2.3 — Suggested Edits | 2 | stack-exchange-suggested-edits.yaml |
| Stack Exchange API v2.3 — Tags | 7 | stack-exchange-tags.yaml |
| Stack Exchange API v2.3 — Users | 11 | stack-exchange-users.yaml |
- Stack Exchange Vocabulary — 16 resources, 8 actions, 16 workflows, 11 personas
- Stack Exchange Spectral Ruleset — 44 rules enforcing Stack Exchange API conventions
- Stack Exchange Plans & Pricing — 3 plans (API Commons Plans 0.1)
- Stack Exchange Rate Limits — 6 limits, 7 policies (API Commons Rate Limits 0.1)
FN: Kin Lane
Email: kin@apievangelist.com