No more typing reviews! Try our Samantha, our new voice AI agent.

ReadMe vs XGEN AI comparison

Why PeerSpot?
 

Comparison Buyer's Guide

Executive Summary

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

ReadMe
Ranking in AWS Marketplace
44th
Average Rating
8.6
Number of Reviews
3
Ranking in other categories
No ranking in other categories
XGEN AI
Ranking in AWS Marketplace
85th
Average Rating
7.6
Number of Reviews
2
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of October 2026, in the AWS Marketplace category, the mindshare of ReadMe is 0.2%, up from 0.1% compared to the previous year. The mindshare of XGEN AI is 0.2%, up from 0.2% compared to the previous year. It is calculated based on PeerSpot user engagement data.
AWS Marketplace Mindshare Distribution
ProductMindshare (%)
ReadMe0.2%
XGEN AI0.2%
Other99.6%
AWS Marketplace
 

Featured Reviews

TejaswiniAleti - PeerSpot reviewer
Member Technical at ADP
Centralized API documentation has improved collaboration and reduces onboarding time
Overall, I have had a positive experience with ReadMe, but there are a few areas where I think it could improve. One is customization. While it is easy to create clean documentation, making deeper UI or layout customizations can be somewhat limiting without additional effort. Having more built-in customization options would help teams tailor the developer portal to their branding and documentation needs. I would also like to see more advanced analytics. It would be useful to have richer insights into which APIs are viewed most frequently, where developers spend the most time, and which document pages generate the most support requests. Those metrics could help us continuously improve our documentation. Another improvement would be the tighter integration with Git-based development workflows. While synchronizing documentation works well, making documentation updates, previews, and reviews even more seamless as part of the pull request process would improve the developer experience. All of these are not major issues. They are enhancements that would make an already solid platform even better. Overall, ReadMe has worked well for our API documentation needs. An additional improvement I would like to see is better support for documentation versioning and change tracking. In enterprise applications, APIs evolve over time, and having more intuitive tools to compare versions and clearly highlight changes would make it easier for both internal teams and external consumers to adopt new API versions. I would also appreciate more built-in collaboration features, such as richer review workflows or commenting capabilities for documentation changes before they are published. That would make it easier for developers, QA teams, and technical writers to review documentation together and keep it accurate. Other than those enhancements, I think ReadMe is an easy-to-use platform that has met our API documentation needs. I do not have any major concerns beyond the improvements I already mentioned.
Rajiv Kedia - PeerSpot reviewer
IT Director at a consultancy with 10,001+ employees
Personalized conversations have boosted engagement but need clearer insights and cleaner data
My experience with using XGEN AI for hyper-personalization is that it is generally very strong, but it needs to be implemented correctly. The way it really works well is that real-time behavior tracking is very fast, allowing you to give better results to your users. The recommendation engine is also very fast. The main point is that you need clean data; if you don't have clean data, it can reduce the impact and sometimes over-personalize, which can be of no use or may have negative implications as users might see repetitive items. The best features XGEN AI offers, in my view, are its strong event tracking capabilities. It can track events, clicks, and views, and it has good product metadata. If you're looking to build a true conversational AI engine, it is the best. My assessment is that it works best when treated as a revenue engine, not just as a feature. You have to tie it to a metric such as conversation and retention to see clear ROIs. What stands out to me most about the event tracking or conversational AI engine in XGEN AI is its conversational AI understanding. With NLPs or with most chatbots or voicebots that you would be building, the biggest struggle point is that they are very deterministic in nature, and they don't let you know what to tell and when to tell the user. With XGEN AI, I feel this is consolidated and you get a unified view. XGEN AI has positively impacted our organization by helping us track what users are looking for. The initial release itself showed that the success rate is more than what we were getting previously. We were able to collect a lot of data, and the best part is that it can work across channels, apps, and emails, which helps us provide a unified experience to the end user. We have seen XGEN AI recommendations lift conversion by 10 to 15 percent. We have experienced real-time behavior tracking and have started seeing some ROIs; though I'm not allowed to share the actual ROI itself, we see improvement in the overall metrics. User engagement has been very positive. We have focus groups and are collecting client feedback, and for most people that we have been able to capture feedback from, the CSAT has improved. That's the biggest thing, so overall, it's trending towards positive.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"Previously, our documentation was split up, but now it is unified through ReadMe, which gives a clear overview and is very easy to navigate, acting as a single source of truth for our business and providing more stability."
"Overall, if your organization wants to improve the developer experience, reduce repetitive support questions, and provide a centralized and professional API portal, I think ReadMe is a strong choice."
"With ReadMe serving as a clear, self-service developer portal, our partners can now complete their integration in a fraction of the time, which has accelerated project delivery timelines, improved our partner satisfaction, and optimized engineering promises."
"We have seen a positive ROI with XGEN AI, as it has helped us save roughly fifteen to twenty percent of development time on coding, debugging, and documentation tasks, allowing the team to focus more on higher-value tasks."
"We have seen XGEN AI recommendations lift conversion by 10 to 15 percent."
 

Cons

"We could probably have more advanced analytics, multi-domain support, or something similar, and advanced access controls."
"ReadMe is a software-as-a-service offering only, and there is no way to self-host ReadMe."
"One is customization. While it is easy to create clean documentation, making deeper UI or layout customizations can be somewhat limiting without additional effort."
"An area for development with XGEN AI is providing more features for complex or project-specific code, better analysis across multiple codebases or services, and deeper integration with the development tools would make it even more useful for day-to-day work."
"However, the things that do not work as well include its high dependency on data quality and very limited transparency in how recommendations are generated, which needs to improve."
report
Use our free recommendation engine to learn which AWS Marketplace solutions are best for your needs.
915,341 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Construction Company
43%
Comms Service Provider
12%
Healthcare Company
12%
Outsourcing Company
6%
Construction Company
26%
Comms Service Provider
25%
Manufacturing Company
11%
Outsourcing Company
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
No data available
 

Questions from the Community

What needs improvement with ReadMe?
For our internal APIs that move quickly with frequent minor schema changes, the versioning felt more rigid than we wanted. We ended up simplifying our branching strategy to fit ReadMe's model. Read...
What is your primary use case for ReadMe?
My company has been using ReadMe for about two years. We use ReadMe to document the APIs exposed by our large finance-related application. We document internal-facing endpoints consumed by our team...
What advice do you have for others considering ReadMe?
You need to have a good Open API specification that is clean because if that is bad, then it is not ReadMe's fault that the documentation is bad, as the underlying data has to be there. My overall ...
What is your experience regarding pricing and costs for XGEN AI?
My experience with pricing, setup cost, and licensing is that it is in line with other similar providers we have used. I would say pricing is comparable, and the licensing is based on subscription ...
What needs improvement with XGEN AI?
One of the improvements I would suggest for XGEN AI is the use of hybrid models and asking real quality questions to the users. Additionally, product attributes or data quality needs to be improved...
What is your primary use case for XGEN AI?
Primarily, our use case for XGEN AI is to advise clients on how to use AI for conversational chatbots. A specific example of how I have used XGEN AI in my work is that we have advised clients on AI...
 

Comparisons

No data available
 

Overview

Find out what your peers are saying about ReadMe vs. XGEN AI and other solutions. Updated: September 2026.
915,341 professionals have used our research since 2012.