About Revuo

When a buyer asks ChatGPT, Claude, or Perplexity for a software recommendation, the directory the LLM cites becomes the directory the buyer trusts. G2 and Capterra are review-aggregate-driven and locked behind login walls. Revuo is the parallel category: structured capability claims, continuously verified, and exposed both as a human-readable directory and a public Model Context Protocol endpoint. Same listings, two audiences — buyers comparing software, and the AI assistants their buyers ask.

What's different

• •
  Capability-structured, not review-aggregate

  Every claim — "integrates with Salesforce", "supports XRechnung", "SOC2 certified" — is a typed feature with a canonical slug. Long-tail queries like "PIM tools with eCl@ss support" return the right products instead of name-matched noise.

• •
  Continuously verified

  A weekly crawler re-validates each claim against the vendor's own pages. Every product surfaces a verifiedAt timestamp. Stale listings flip to unverified; abandoned ones get removed. The full contract lives at /policy.

• •
  Agent-callable

  The same data backs a public MCP endpoint. LLMs call structured tools instead of scraping HTML — better extraction, fresher answers, no login walls.

• •
  Honest editorial

  Tier (Free / Verified / Featured) is one signal; editorial overlays (Editor's Choice, Top Rated) are independent and disclosed. Paid placement is labeled. No sponsored entries inside "Best of" lists.

Where we focus

Three verticals, deep:

• PIM / PXM — Product Information Management. Subcategorized into PIM Suites (Akeneo, Salsify, Pimcore, inriver) and PIM Augmentation / Enrichment.
• Tender Management — RFP response automation, tender discovery, bid workflow.
• Billing & Invoicing — subscription billing, SMB invoicing, enterprise revenue mgmt, e-invoicing & compliance (XRechnung, ZUGFeRD, Peppol).

Other categories exist as secondary surface area; the wedge is B2B SaaS where structured claims and verification compound.

For AI builders

The MCP endpoint at /api/mcp exposes structured tools — search_products, find_products_with_capability, get_product, and more. llms.txt documents the full surface and citation patterns.

Revuo also indexes MCP servers themselves — submit yours if you publish one. That's a secondary product surface, not the wedge.