RiskRecon

RiskRecon by Mastercard is a third-party and supply-chain cyber risk management platform that continuously assesses, rates, and monitors the cybersecurity posture of an organization and its vendor ecosystem. It produces objective, automated security ratings across dozens of security criteria, prioritizes findings by asset value and issue severity, and lets teams tune assessments to their own risk appetite. RiskRecon exposes a REST API (api.riskrecon.com) so customers can programmatically pull portfolio ratings, toe (target-of-evaluation) analyses, findings, and evidence into their own GRC, TPRM, and security workflows. Originally venture backed by Accel and others, RiskRecon was acquired by Mastercard and now operates as RiskRecon by Mastercard.

RiskRecon is listed with 1 API on the APIs.io network. Tagged areas include Company, Cybersecurity, Security Ratings, Third-Party Risk Management, and Supply Chain Risk.

RiskRecon’s developer surface includes documentation, API reference, getting-started guide, support, engineering blog, authentication, and 13 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

21.7/100 emerging ▬ flat Agent 5/100 agent aware Front door AI 2/6 trace Heartbeat 100/100 alive saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

1 API

Company Cybersecurity Security Ratings Third-Party Risk Management Supply Chain Risk Risk Management GRCVendor MonitoringAttack Surface

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 21.7/100 · emerging

Contract Quality 0.0 / 21

Developer Ergonomics 8.1 / 17

Access Clarity 3.6 / 17

Operational Transparency 0.0 / 11

Contract Governance 0.0 / 10

Discoverability 6.2 / 9

Regulatory Posture 2.9 / 15

Agent readiness — 5/100 · agent aware

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/riskrecon/"><img src="https://apis.io/badge/riskrecon/card.svg" alt="RiskRecon on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

Machine-Readable Contract +18 pts — api_specs includes an OpenAPI document
MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)

11 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 0.0 — up to +25.0 composite points
Access Clarity scores 21.1 — up to +15.8 composite points
Operational Transparency scores 0.0 — up to +13.0 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/riskrecon/apis.yml: open an issue on github.com/api-evangelist/riskrecon to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
Compliance Assurance and Cloud Attestation	standard	19.4 (thin)	-	-
ServiceNow Store (partner apps + ServiceNow Certified App)	standard	19.4 (thin)	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

APIs 1

Individual APIs this provider publishes, each with its own machine-readable definition.

RiskRecon API

RiskRecon REST API for programmatic access to security ratings, portfolio and toe (target-of-evaluation) analyses, findings, and evidence. Authenticated with a JWT bearer token....

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Riskrecon Authentication

http · 1 scheme

SECURITY

Riskrecon Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Resources

Get Started 3

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

Login

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

WellKnown

WellKnown

Design & Contract 3

Pagination, idempotency, versioning, errors, and events

ErrorCatalog

ErrorCatalog

Conventions

Conventions

Lifecycle

Lifecycle

Access & Security 2

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Authentication

Authentication

Operate 1

Status, limits, changes, and where to get help

Support

Support

Commercial 2

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 3

The organization behind the API

BlogRSS

BlogRSS

Website

Website

Blog

Blog

Other 1

Properties that don't map to a standard resource type

ParentCompany

ParentCompany

Source (apis.yml)

aid: riskrecon
name: RiskRecon
description: RiskRecon by Mastercard is a third-party and supply-chain cyber risk management platform that continuously assesses,
  rates, and monitors the cybersecurity posture of an organization and its vendor ecosystem. It produces objective, automated
  security ratings across dozens of security criteria, prioritizes findings by asset value and issue severity, and lets teams
  tune assessments to their own risk appetite. RiskRecon exposes a REST API (api.riskrecon.com) so customers can programmatically
  pull portfolio ratings, toe (target-of-evaluation) analyses, findings, and evidence into their own GRC, TPRM, and security
  workflows. Originally venture backed by Accel and others, RiskRecon was acquired by Mastercard and now operates as RiskRecon
  by Mastercard.
url: https://raw.githubusercontent.com/api-evangelist/riskrecon/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- accel
x-owned-by: mastercard
x-tier: profiled
x-tier-reason: enrichment-pass
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - security
  generated: '2026-11-06'
  method: derived
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-10-06'
image: https://www.riskrecon.com/hubfs/riskrecon-by-mastercard-logo.png
tags:
- Company
- Cybersecurity
- Security Ratings
- Third-Party Risk Management
- Supply Chain Risk
- Risk Management
- GRC
- Vendor Monitoring
- Attack Surface
tags_raw:
- Company
- Cybersecurity
- Security Ratings
- Third Party Risk
- Supply Chain Risk
- Risk Management
- GRC
- Vendor Monitoring
- Attack Surface
- Third-Party Risk
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
apis:
- name: RiskRecon API
  description: RiskRecon REST API for programmatic access to security ratings, portfolio and toe (target-of-evaluation) analyses,
    findings, and evidence. Authenticated with a JWT bearer token. Multiple version prefixes are published (v1, v2, and a
    v0/cpe surface), each with its own Swagger UI documentation.
  humanURL: https://api.riskrecon.com/v1/swagger/index.html
  baseURL: https://api.riskrecon.com/v1
  properties:
  - type: APIReference
    url: https://api.riskrecon.com/v1/swagger/index.html
  - type: APIReference
    url: https://api.riskrecon.com/v2/swagger/index.html
  - type: Authentication
    url: authentication/riskrecon-authentication.yml
  - type: ErrorCatalog
    url: errors/riskrecon-problem-types.yml
x-enrichment:
  date: '2026-07-21'
  status: enriched
  artifacts_added: 7
  pass: local-v1
common:
- url: https://blog.riskrecon.com/rss.xml
  type: BlogRSS
- type: ParentCompany
  url: https://apis.io/providers/mastercard/
  name: Mastercard
  x-relationship: acquired
  x-evidence: Originally venture backed by Accel and others, RiskRecon was acquired by Mastercard and now operates as RiskRecon
    by Mastercard.
- type: DomainSecurity
  url: security/riskrecon-domain-security.yml
- type: Website
  url: https://www.riskrecon.com
- type: DeveloperPortal
  url: https://portal.riskrecon.com/
- type: Documentation
  url: https://api.riskrecon.com/v1/swagger/index.html
- type: APIReference
  url: https://api.riskrecon.com/v1/swagger/index.html
- type: GettingStarted
  url: https://www.riskrecon.com/academy
- type: Support
  url: https://www.riskrecon.com/contact-us
- type: Blog
  url: https://blog.riskrecon.com
- type: TermsOfService
  url: https://www.riskrecon.com/terms-of-use
- type: PrivacyPolicy
  url: https://www.riskrecon.com/privacy-policy
- type: Login
  url: https://portal.riskrecon.com/
- type: Authentication
  url: authentication/riskrecon-authentication.yml
- type: ErrorCatalog
  url: errors/riskrecon-problem-types.yml
- type: Conventions
  url: conventions/riskrecon-conventions.yml
- type: Lifecycle
  url: lifecycle/riskrecon-lifecycle.yml
- type: LLMsTxt
  url: llms/riskrecon-llms.txt
- type: WellKnown
  url: well-known/riskrecon-well-known.yml

RiskRecon API — frequently asked questions

Does RiskRecon have an API?

Yes. APIs.io lists 1 API from RiskRecon, including RiskRecon API.

How do I authenticate with the RiskRecon API?

RiskRecon uses bearer-token authentication (http · 1 scheme). The details are profiled on APIs.io as Riskrecon Authentication.

Is the RiskRecon API ready for AI agents?

RiskRecon has a Kin Score of 21.7 out of 100 (emerging) and an Agent Readiness score of 5.4 (agent-aware), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/riskrecon"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/riskrecon/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/riskrecon/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.