Cardinal
Cardinal is an AI platform for precision outbound sales — it markets itself as "revenue agents for high-growth companies" — built for go-to-market teams that want outbound to run as one engine instead of a stack of disconnected tools. Its agents build and refresh account lists from signals, monitor what prospects post and engage with, generate personalized snippets, and orchestrate end-to-end email and LinkedIn plays, while capturing inbound from website visitors, product signups and ad impressions. The company is a Y Combinator Winter 2026 company founded by Devishi Jha and Jianna Liu, based in San Francisco, and names Mintlify, Deepgram, Greptile, Giga and Luminai among its customers. Cardinal moved its primary web presence from trycardinal.ai to trycardinal.com during 2026: https://trycardinal.ai/ now HTTP 301s to https://www.trycardinal.com/ and the former deep pages on the .ai domain (/company, /product) return 404, though the company still runs its customer application, its email and its analytics identity on trycardinal.ai. The product is sold as half-software and half-service ("we wire into your existing stack and build agents around plays that already work for you"), delivered through a customer app at app.trycardinal.ai behind a Stytch login, with a Calendly GTM chat as the only publicly reachable entry point. It reads from and writes back to customer CRMs and says it adds a new integration every two weeks, but names none of them publicly and publishes no outbound API of its own: across four hosts on two domains this pass found no OpenAPI, GraphQL SDL, AsyncAPI, MCP server, agent card, webhook catalog, SDK, CLI, developer portal or documentation site. docs.trycardinal.ai does not resolve in DNS, api.trycardinal.ai is a dangling custom domain whose Render origin answers x-render-routing: no-server, and every /api/* path on the customer app returns HTTP 401 {"error":"Unauthorized"}.
Index entry only — little beyond a description and a link, and nothing machine-readable enough for an agent to act on without a human reading the site first.
API Evangelist profiles Cardinal the way a machine reads it — 3 machine-readable artifacts, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Cardinal scores 9.6/100 (minimal), with a separate agent-readiness read of 3/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Why this profile is thin
Cardinal sells a half-software, half-service outbound sales product delivered through a customer application behind a Stytch login, not a developer product: contract discovery across four hosts on two domains found no OpenAPI, GraphQL SDL, AsyncAPI, MCP endpoint, agent card, webhook catalog, SDK, CLI or documentation site of any kind, there is no docs host to find (docs.trycardinal.ai and docs.trycardinal.com have no DNS record), the company's own eleven-URL sitemap contains no docs, developers, pricing or legal path, and the one API hostname it still publishes (api.trycardinal.ai) is a dangling CNAME to a Render service that answers x-render-routing:no-server and presents no TLS certificate — the only public place the word "API" appears is as the name of the single component on its status page.
This is an honest zero, not a gap in our research. Cardinal does not appear to expose an API, so there is nothing here for us to index and nothing for them to fix.
What we probed
https://trycardinal.ai/→ HTTP 301https://www.trycardinal.com/openapi.json→ HTTP 404https://www.trycardinal.com/llms.txt→ HTTP 404https://www.trycardinal.com/sitemap.xml→ HTTP 200https://app.trycardinal.ai/api→ HTTP 401https://app.trycardinal.ai/openapi.json→ HTTP 404https://app.trycardinal.ai/.well-known/agent-card.json→ HTTP 404https://api.trycardinal.ai/→ HTTP 409https://coordinator-api-wmxp.onrender.com/openapi.json→ HTTP 404https://status.trycardinal.ai/api/v2/summary.json→ HTTP 200
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Cardinal's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/trycardinal-ai/"
title="Cardinal on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/trycardinal-ai.svg"
alt="Cardinal Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/trycardinal-ai/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/trycardinal-ai/"
title="Cardinal on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/trycardinal-ai/card.svg"
alt="Cardinal Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Cardinal
Each block below is one kind of artifact we hold for Cardinal. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Trycardinal Ai Rate Limits
RATE LIMITSSecurity Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for Cardinal — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 1
Portal, sign-up, and the first successful call
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 1
Pagination, idempotency, versioning, errors, and events
Access & Security 1
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 1
Pricing, plans, and the legal terms of use
Company 6
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/trycardinal-ai · machine-readable index on apis.io
This is an independent, third-party profile of Cardinal, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put 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.