Renesas

Renesas Electronics Corporation (TYO: 6723) is a global semiconductor manufacturer producing microcontrollers and microprocessors (RA, RX, RL78, RH850, RZ, Synergy families), analog, power, sensor, timing, connectivity, and memory products for automotive, industrial, infrastructure, and consumer electronics applications. On the developer side Renesas operates a public developer portal at developer.renesas.com whose flagship programmable interface is the Renesas Web Data API — a REST API that lets approved partners and integrators retrieve Renesas product metadata (products, product parts, documents, boards & kits, packages, and software tools) in real time instead of relying on manual CSV downloads or periodic feed refreshes. The API is documented on a Redocly Realm site, ships an OpenAPI 3.0.0 description, an auto-generated Model Context Protocol (MCP) server, a browser Try-It console, and a semantic-versioned changelog.

Renesas publishes 6 API contracts indexed on the APIs.io network, including Board & Kit API, Document API, Package API, and 3 more. Tagged areas include Company, Semiconductors, Microcontrollers, Electronics, and Hardware.

The Renesas catalog on APIs.io includes 1 Spectral governance ruleset.

Renesas’ developer surface includes documentation, API reference, getting-started guide, authentication, support, engineering blog, signup flow, and 22 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

45.2/100 developing ▬ flat Agent 42/100 agent ready Front door AI 3/6 light Heartbeat 100/100 alive saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

1 published contract 1 MCP Servers 3 Agent Skills

Company Semiconductors Microcontrollers Electronics Hardware Product Data Automotive Industrial Embedded Developer Tools

What this lets a business do 1

Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →

Electrical Product Catalogue Management

BC-1940

Product Part

GET /product-parts GET /product-parts/{orderable_id} POST /product-parts/search POST /product-parts/cross-reference

Kin Score

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

Composite quality — 45.2/100 · developing

Contract Quality 9.2 / 19

Developer Ergonomics 9.9 / 15

Access Clarity 5.1 / 15

Operational Transparency 1.8 / 10

Contract Governance 1.6 / 9

Discoverability 5.6 / 8

Regulatory Posture 3.7 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 42/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 0 / 6

MCP Server 12 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 5 / 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 6 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 6 / 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 applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% 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/renesas/"><img src="https://apis.io/badge/renesas/card.svg" alt="Renesas 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):

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)
Typed Event Surface +6 pts — AsyncAPI document, OR webhooks/callbacks objects in the as-published OpenAPI, OR common[].type includes Webhooks
Documented Reversibility +6 pts — a reversal operation in the contract, graded up when a window is documented too
Protected Resource Metadata +5 pts — a served /.well-known/oauth-protected-resource carrying `resource` (documented), and naming its authorization_servers (verified)

4 more unmet checks in the Agent Readiness table above.

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

Access Clarity scores 34.2 — up to +13.2 composite points
Contract Quality scores 49.3 — up to +12.7 composite points
Operational Transparency scores 18.4 — up to +10.6 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/renesas/apis.yml: open an issue on github.com/api-evangelist/renesas 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
XR & Graphics (XR, 3D, GPU graphics)	standard	53.5	-	-
IDE Extension Marketplaces (JetBrains, VS Code, Open VSX, Docker Verified Publishers, PyPI orgs)	standard	53.5	-	-
Semiconductor Consortia (RISC-V, OCP hardware, CHIPS awards)	standard	53.5	-	-
Common Criteria Certified Products (ISO/IEC 15408, NIAP Product Compliant List)	standard	53.5	-	-
NIST CMVP FIPS 140 Validated Cryptographic Modules (FIPS 140-1 / 140-2 / 140-3)	standard	53.5	-	-

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.

Standards implemented 3

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

Model Context Protocol (MCP)

measured — observed by APIs.io (platform)

Dynamic Client Registration

measured — observed by APIs.io (published)

OpenAPI

measured — observed by APIs.io (published)

APIs 6

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

Renesas Board & Kit API

Endpoints for retrieving boards and kits.

Renesas Document API

Endpoint for retrieving documents.

Renesas Package API

Endpoints for retrieving packages.

Renesas Product API

Endpoints for retrieving products.

Renesas Product Part API

Endpoints for retrieving product parts.

Renesas Software Tool API

Endpoints for retrieving software tools.

Open Collections 6

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

Renesas Web Data Board & Kit API

OPEN COLLECTION

Renesas Web Data Board & Kit Document API

OPEN COLLECTION

Renesas Web Data Board & Kit Package API

OPEN COLLECTION

Renesas Web Data Board & Kit Product API

OPEN COLLECTION

Renesas Web Data Board & Kit Product Part API

OPEN COLLECTION

Renesas Web Data Board & Kit Software Tool API

OPEN COLLECTION

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

Renesas Web Data API docs MCP

Remote MCP server at developer.renesas.com over HTTP; 6 tools listed.

MCP SERVER

Agent Skills 3

Packaged agent skills for driving this provider's APIs from an AI assistant.

Cross-reference competitor parts to Renesas replacements

AGENT SKILL

Retrieve Renesas product documents

AGENT SKILL

Find and parametrically filter Renesas product parts

AGENT SKILL

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Renesas API Rules

61 rules · 56 errors 2 warnings 3 info

SPECTRAL

OpenAPI Overlays 1

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Renesas Web Data Overlay

3 actions · update · renesas-web-data-openapi-original.yml

DERIVED

Security Posture 2

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

Renesas Authentication

apiKey · 1 scheme

SECURITY

Renesas Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Renesas Agentic Access

18 operations · 2 acting

AGENTIC

Resources

Get Started 4

Portal, sign-up, and the first successful call

DeveloperPortal

GettingStarted

SignUp

Sandbox

Documentation 3

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

OpenAPI

OpenAPI

Agent Surfaces 5

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

MCPServer

AgentSkill

LLMsTxt

WellKnown

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

ErrorCatalog

Conventions

DataModel

Lifecycle

Conformance

Build 2

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Examples

Examples

Access & Security 2

Authentication, authorization, and security posture

Authentication

Authentication

DomainSecurity

DomainSecurity

Operate 2

Status, limits, changes, and where to get help

Support

Support

ChangeLog

ChangeLog

Commercial 2

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 2

The organization behind the API

Website

Website

Blog

Blog

Other 2

Properties that don't map to a standard resource type

CapabilityMap

CapabilityMap

Overlay

Overlay

Source (apis.yml)

x-docs-platform: redocly
x-docs-platform-confidence: high
x-docs-platform-checked: 2026-10-04
x-enrichment:
  date: '2026-07-20'
  status: enriched
  artifacts_added: 21
  pass: local-v1
aid: renesas
name: Renesas
description: 'Renesas Electronics Corporation (TYO: 6723) is a global semiconductor manufacturer producing microcontrollers
  and microprocessors (RA, RX, RL78, RH850, RZ, Synergy families), analog, power, sensor, timing, connectivity, and memory
  products for automotive, industrial, infrastructure, and consumer electronics applications. On the developer side Renesas
  operates a public developer portal at developer.renesas.com whose flagship programmable interface is the Renesas Web Data
  API — a REST API that lets approved partners and integrators retrieve Renesas product metadata (products, product parts,
  documents, boards & kits, packages, and software tools) in real time instead of relying on manual CSV downloads or periodic
  feed refreshes. The API is documented on a Redocly Realm site, ships an OpenAPI 3.0.0 description, an auto-generated Model
  Context Protocol (MCP) server, a browser Try-It console, and a semantic-versioned changelog.'
url: https://raw.githubusercontent.com/api-evangelist/renesas/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- norwest-venture-partners
x-tier: profiled
x-tier-reason: has-public-api
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - 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
  - sandbox
  generated: '2026-11-06'
  method: derived
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-20'
tags:
- Company
- Semiconductors
- Microcontrollers
- Electronics
- Hardware
- Product Data
- Automotive
- Industrial
- Embedded
- Developer Tools
image: https://www.renesas.com/themes/kachow/images/renesas-logo.png
apis:
- aid: renesas:renesas-board-kit-api
  name: Renesas Board & Kit API
  description: Endpoints for retrieving boards and kits.
  humanURL: https://developer.renesas.com/docs/web-data-api
  baseURL: https://api.renesas.com/web-data/v1
  tags:
  - Board & Kit
  properties:
  - type: OpenAPI
    url: openapi/renesas-board-kit-api-openapi.yml
  - type: Documentation
    url: https://developer.renesas.com/docs/web-data-api
  - type: APIReference
    url: https://developer.renesas.com/docs/web-data-api/apis/web-data
- aid: renesas:renesas-document-api
  name: Renesas Document API
  description: Endpoint for retrieving documents.
  humanURL: https://developer.renesas.com/docs/web-data-api
  baseURL: https://api.renesas.com/web-data/v1
  tags:
  - Documents
  tags_raw:
  - Document
  properties:
  - type: OpenAPI
    url: openapi/renesas-document-api-openapi.yml
  - type: Documentation
    url: https://developer.renesas.com/docs/web-data-api
  - type: APIReference
    url: https://developer.renesas.com/docs/web-data-api/apis/web-data
- aid: renesas:renesas-package-api
  name: Renesas Package API
  description: Endpoints for retrieving packages.
  humanURL: https://developer.renesas.com/docs/web-data-api
  baseURL: https://api.renesas.com/web-data/v1
  tags:
  - Package
  properties:
  - type: OpenAPI
    url: openapi/renesas-package-api-openapi.yml
  - type: Documentation
    url: https://developer.renesas.com/docs/web-data-api
  - type: APIReference
    url: https://developer.renesas.com/docs/web-data-api/apis/web-data
- aid: renesas:renesas-product-api
  name: Renesas Product API
  description: Endpoints for retrieving products.
  humanURL: https://developer.renesas.com/docs/web-data-api
  baseURL: https://api.renesas.com/web-data/v1
  tags:
  - Product
  properties:
  - type: OpenAPI
    url: openapi/renesas-product-api-openapi.yml
  - type: Documentation
    url: https://developer.renesas.com/docs/web-data-api
  - type: APIReference
    url: https://developer.renesas.com/docs/web-data-api/apis/web-data
- aid: renesas:renesas-product-part-api
  name: Renesas Product Part API
  description: Endpoints for retrieving product parts.
  humanURL: https://developer.renesas.com/docs/web-data-api
  baseURL: https://api.renesas.com/web-data/v1
  tags:
  - Product Part
  properties:
  - type: OpenAPI
    url: openapi/renesas-product-part-api-openapi.yml
  - type: Documentation
    url: https://developer.renesas.com/docs/web-data-api
  - type: APIReference
    url: https://developer.renesas.com/docs/web-data-api/apis/web-data
- aid: renesas:renesas-software-tool-api
  name: Renesas Software Tool API
  description: Endpoints for retrieving software tools.
  humanURL: https://developer.renesas.com/docs/web-data-api
  baseURL: https://api.renesas.com/web-data/v1
  tags:
  - Software Tool
  properties:
  - type: OpenAPI
    url: openapi/renesas-software-tool-api-openapi.yml
  - type: Documentation
    url: https://developer.renesas.com/docs/web-data-api
  - type: APIReference
    url: https://developer.renesas.com/docs/web-data-api/apis/web-data
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: CapabilityMap
  url: capabilities/renesas-capability-edges.yml
  name: Renesas Business Capability Map
- type: AgenticAccess
  url: agentic-access/renesas-agentic-access.yml
- type: Website
  url: https://www.renesas.com
- type: DeveloperPortal
  url: https://developer.renesas.com
- type: Documentation
  url: https://developer.renesas.com/docs/web-data-api
- type: APIReference
  url: https://developer.renesas.com/docs/web-data-api/apis/web-data
- type: GettingStarted
  url: https://developer.renesas.com/docs/web-data-api/guides/quickstart
- type: Authentication
  url: authentication/renesas-authentication.yml
- type: Support
  url: https://www.renesas.com/en/support
- type: Blog
  url: https://www.renesas.com/en/blogs
- type: GitHubOrganization
  url: https://github.com/renesas
- type: SignUp
  url: https://www.renesas.com/en/form/web-data-api-access-request
- type: TermsOfService
  url: https://www.renesas.com/legal-notices
- type: PrivacyPolicy
  url: https://www.renesas.com/privacy
- type: OpenAPI
  url: openapi/_original/renesas-web-data-openapi-original.yml
- type: Overlay
  url: overlays/renesas-web-data-overlay.yaml
- type: Examples
  url: openapi/_original/renesas-web-data-openapi-original.yml
- type: MCPServer
  url: mcp/renesas-mcp.yml
- type: AgentSkill
  url: skills/_index.yml
- type: LLMsTxt
  url: llms/renesas-llms.txt
- type: WellKnown
  url: well-known/renesas-well-known.yml
- type: ErrorCatalog
  url: errors/renesas-problem-types.yml
- type: Conventions
  url: conventions/renesas-conventions.yml
- type: DataModel
  url: data-model/renesas-data-model.yml
- type: Lifecycle
  url: lifecycle/renesas-lifecycle.yml
- type: ChangeLog
  url: changelog/renesas-changelog.yml
- type: Sandbox
  url: sandbox/renesas-sandbox.yml
- type: Conformance
  url: conformance/renesas-conformance.yml
- type: DomainSecurity
  url: security/renesas-domain-security.yml
x-tags-removed:
- Developer Portal

Renesas API — frequently asked questions

Does Renesas have an API?

Yes. APIs.io lists 6 APIs from Renesas, including Renesas Board & Kit API, Renesas Document API and Renesas Package API, and 3 more.

Is there an OpenAPI specification for the Renesas API?

Yes. APIs.io indexes 6 OpenAPI specifications for Renesas, each linked for download from this page.

How do I authenticate with the Renesas API?

Renesas documents its authentication (apiKey · 1 scheme). The details are profiled on APIs.io as Renesas Authentication.

Does Renesas have an MCP server?

Yes. APIs.io lists 1 MCP server for Renesas: Remote MCP server at developer.renesas.com over HTTP; 6 tools listed.

Is the Renesas API ready for AI agents?

Renesas has a Kin Score of 45.2 out of 100 (developing) and an Agent Readiness score of 42.0 (agent-ready), 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/renesas"

All providers

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

Every operation they expose

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

How their score was established

curl "https://apis.io/api/v1/providers/renesas/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.