Get a Quote

Developer tools · communication APIs

PingMyUsers: an evidence-first directory of communication APIs for developers and AI agents

An evidence-first directory and ranking of email, SMS, OTP and WhatsApp APIs, with a public REST API and a read-only MCP server so AI agents can query the same sourced, dated facts as developers.

Visit the live site
Client
PingMyUsers
Industry
Developer tools · communication APIs
Year
2026
  • 27 communication-API providers with published cards
  • 4 channels ranked: email, SMS, OTP, WhatsApp
  • 10 read-only MCP tools
  • 8 REST API endpoint groups with OpenAPI
PingMyUsers home page with the headline “Which API should ping your users?” and a search box for describing what an app needs to send

Challenge

Choosing an email, SMS or WhatsApp API means reading pricing pages in several currencies and checking webhook security, SDKs and sender-registration rules. Teams that build with AI coding tools now also want to know whether a vendor offers an MCP server or agent skills. The information is scattered across vendor sites, often out of date, and hard for an AI agent to read.

Solution

We built PingMyUsers so that every fact on a provider card links to its source, carries an evidence level and shows the date it was checked. A rating engine computes scores from those facts with three methodologies (global, per channel and regional); weights of unknown criteria are renormalized and coverage is shown next to each score. Strengths, weaknesses and “Not a fit if…” lines come from threshold rules over the dated facts. The same data is published through a REST API and a read-only MCP server.

What we delivered

  • Information architecture: provider cards, rankings (global, per channel, per market), comparisons, alternatives pages, guides, tutorials, glossary, methodology and a developer page
  • YAML data model with one file per provider, a sourced fact per field and a versioned methodology file
  • Rating engine with three methodologies and rule-generated strengths, weaknesses and “Not a fit if…” lines
  • Public REST API with 8 endpoint groups and a published OpenAPI document
  • Read-only MCP server with 10 tools
  • Open CSV/JSON datasets under CC BY 4.0, including an AI-readiness dataset
  • MDX content system with an editorial calendar, date-gated publishing and live rating components
  • Build gates on every deploy and a pre-commit hook that blocks commits containing a secret value

Functionality

  • Natural-language search on the home page: describe what the app needs to send
  • Rankings for transactional email, SMS, OTP & verification and WhatsApp Business API
  • Market rankings for the US, Brazil and Mexico
  • Evidence level (official docs, other official page, third-party confirmed, vendor claim, not verified) and check date on every fact
  • Coverage shown next to every score
  • Comparison and alternatives pages
  • MCP tools for search, provider cards, comparisons, pricing by country, rankings, alternatives, integration guides, payment scenarios, recommendations and datasets
  • Free-text MCP requests handled by a deterministic intent parser, not an LLM
  • Dataset downloads showing which providers publish MCP servers, agent skills, llms.txt and OpenAPI

Integrations

  • Model Context Protocol server over HTTP, with read-only tool annotations
  • REST API (/api/v1) with an OpenAPI document
  • IndexNow submission
  • llms.txt
  • Append-only review-aggregator snapshots
  • Vercel Web Analytics

Technologies

  • Next.js 16
  • React 19
  • TypeScript 5
  • Tailwind CSS 4
  • MDX 3 (remark-gfm, rehype-slug)
  • Zod 4
  • MCP server SDK
  • Vitest 4
  • Vercel
PingMyUsers API and MCP server page listing the read-only MCP tools, such as search_services, compare_services, get_pricing and recommend_services, with a one-line install command
The website, the REST API and the MCP server read the same dataset and the same scoring code.
PingMyUsers home page on a phone, with the headline, the search box and example queries such as OTP codes by WhatsApp
Home page and search on a mobile viewport.

Result

PingMyUsers is public and indexable on pingmyusers.com. It publishes 27 provider cards, ranks four channels across three markets and has 16 editorial pages live, with more scheduled. Six further channels are defined in the taxonomy for later waves. Sensaria AG designed and built the site and is its named operator.

Built for agents as well as people

A developer reading a provider card and an AI agent calling the site get the same facts. The REST API covers providers, rankings, comparisons, recommendations, categories, markets, sources and datasets, and ships an OpenAPI document. The MCP server exposes 10 read-only tools. Free-text requests go through a deterministic intent parser, so the same question returns the same answer every time. llms.txt and the open datasets complete the machine-readable layer.

Numbers that cannot go stale

Articles contain no typed ratings. They embed live rating components that read from the data, so a corrected fact updates every page that cites it. Every deploy passes data-sync and schema checks, score verification, a link audit, content and voice gates, a publish check and a confidentiality scan.

Discuss your project

Tell us about your project

Get a Quote Explore our work