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
ReadMe is a developer hub platform that helps companies design, document, and operate their APIs. The platform combines hosted API reference (OpenAPI-driven), guides and changelog, bi-directional Git sync (GitHub and GitLab), interactive API explorer, Try-It console, Developer Dashboard with real-time API logs, and a deep layer of AI tooling — including the ReadMe Agent for multi-page editing, Inline AI rewrites, the AI Linter for style-guide enforcement, Docs Audit, GitHub AI Writer for PR-triggered doc updates, Ask AI for end users, and Model Context Protocol (MCP) servers for both ReadMe itself and each customer project so AI tools can search, read, update docs, and call APIs.
APIs.json: https://raw.githubusercontent.com/api-evangelist/readme/refs/heads/main/apis.yml
- Type: Index
- Position: Consumer
- Access: 3rd-Party
- Documentation
- Developer Hub
- API Reference
- Portals
- Analytics
- AI
- MCP
- Bi-Directional Sync
- Created: 2025-01-08
- Modified: 2026-05-30
The ReadMe API (v2) lets you programmatically control your ReadMe developer hub. It manages API definitions, API reference pages, guides, changelog, custom pages, categories, branches (versions), images, recipes, and search. Authentication uses a Bearer API key.
- Human URL: https://docs.readme.com/main/reference/intro-to-the-readme-api
- Base URL:
https://api.readme.com/v2
- Documentation
- Developer Hub
- Content Management
- API Reference
- Documentation
- Authentication
- OpenAPI — OpenAPI Specification
- Postman Collection — Postman Collection 2.1
- Open Collection — Open Collection 1.0
- Postman Collection — Postman Collection 2.1
- Open Collection — Open Collection 1.0
The ReadMe Developer Metrics API powers the Developer Dashboard. It accepts API request logs from Metrics SDKs (Node.js, Python, Ruby, PHP, .NET) and exposes analytics including page quality scores, page view statistics, and search analytics so teams can investigate API usage by key or email and debug requests in real time.
- Human URL: https://docs.readme.com/main/docs/sending-api-logs
- Base URL:
https://metrics.readme.io/v1
- Analytics
- Metrics
- Logging
- Developer Dashboard
- Documentation
- OpenAPI — OpenAPI Specification
- SDK
- Postman Collection — Postman Collection 2.1
- Open Collection — Open Collection 1.0
- Postman Collection — Postman Collection 2.1
- Open Collection — Open Collection 1.0
ReadMe operates a hosted Model Context Protocol (MCP) server that lets AI tools (Claude, Cursor, IDEs, CI pipelines) search, read, and update ReadMe documentation through natural language. ReadMe also auto-provisions a per-project MCP server for every customer so end users' AI tools can read, search, and call that project's API directly.
- MCP
- AI
- Model Context Protocol
- Agents
- Documentation
- Use Cases
- Documentation
- Use Cases
- Explainer
- Postman Collection — Postman Collection 2.1
- Open Collection — Open Collection 1.0
- Postman Collection — Postman Collection 2.1
- Open Collection — Open Collection 1.0
ReadMe's Personalized Docs Webhook is the outbound, customer-hosted webhook the developer hub calls at user sign-in to look up a reader's account data. ReadMe POSTs a JSON body containing the user's email, signs the request with a Stripe-style ReadMe-Signature header (t=<unix-ms>,v0=<hmac-sha256-hex>) using the project's webhook secret, and expects a JSON response describing the user (apiKey, keys array, server-variable parameters, Basic Auth, GraphQL bearer, etc.) which the hub then merges into the rendered API Reference, Try-It console, and Recipes. The single documented event is the user-data lookup.
- Webhooks
- Personalized Docs
- Developer Hub
- Authentication
- Documentation
- Explainer
- Documentation
- SDK
- AsyncAPI — AsyncAPI Specification
- Postman Collection — Postman Collection 2.1
- Open Collection — Open Collection 1.0
- Postman Collection — Postman Collection 2.1
- Open Collection — Open Collection 1.0
- Arazzo Workflows — Arazzo Specification
- Portal
- Getting Started
- Documentation
- API Reference
- Pricing
- Sign Up
- Login
- Blog
- Changelog
- About
- Status Page
- Terms of Service
- Privacy Policy
- Git Hub Org
- L L Ms Txt
- C L I
- SDK
- Tools
- Tools
- Tools
- Git Hub Action
- Marketplace
- Plans
- Rate Limits
- Fin Ops
- Vocabulary
- J S O N L D Context
- Spectral Rules
FN: Kin Lane Email: kin@apievangelist.com