SiFive

SiFive is a semiconductor intellectual-property company founded by the creators of the RISC-V instruction set architecture at UC Berkeley — Krste Asanovic, Yunsup Lee and Andrew Waterman — and licenses configurable RISC-V processor core IP rather than manufacturing chips. Its catalog spans the Essential (E/S/U), Performance (P500/P600/P800), Intelligence (X100/X200/X300/XM) and Automotive (E6-A/E7-A/S7-A) core families plus system IP including SiFive Insight trace and debug, IOMMU Gen 2, Shield and WorldGuard. Customers configure a Core Design and generate a downloadable Dev Kit of RTL, testbench, software and documentation through SiFive Core Designer, delivered from the SiFive Cloud Services (SCS) portal at scs.sifive.com. The public developer surface is software tooling rather than a hosted REST API: the Freedom SDK for Metal and for Linux, Freedom Studio, Freedom Tools, the SiFive Kernel Library and the open-source DUH hardware-IP description toolchain and JSON Schema published on npm and GitHub.

SiFive publishes 1 API on the APIs.io network. Tagged areas include Company, Semiconductors, RISC-V, Processor IP, and Chip Design.

SiFive’s developer surface includes documentation, getting-started guide, support, engineering blog, signup flow, authentication, CLI, and 22 more developer resources.

🌐 Visit website 📡 Source on GitHub

30.0/100 thin ▬ flat Agent 21/100 agent aware saas Full breakdown ↓
scored 2026-09-08 · rubric v0.20.0

AccessSelf serve

1 APIs 1 MCP Servers

Company Semiconductors RISC-V Processor IP Chip Design Embedded Hardware Developer Tools Electronic Design Automation Authentication

Kin Score

Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0

Composite quality — 30.0/100 · thin

Contract Quality 0.0 / 25

Developer Ergonomics 12.4 / 20

Access Clarity 6.8 / 20

Operational Transparency 1.7 / 13

Contract Governance 2.2 / 12

Discoverability 6.9 / 10

Agent readiness — 21/100 · agent aware

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 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 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 6 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 6 / 6

Agentic Commerce Well-Known Document 0 / 5

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.

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 github.com/api-evangelist/sifive: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 1

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

SiFive Cloud Services OAuth 2.0

The OAuth 2.0 authorization server that fronts the SiFive Cloud Services (SCS) portal at scs.sifive.com, where SiFive Core Designer and the rest of the SiFive development toolin...

MCP Servers 1

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

SiFive MCP Server

SiFive Cloud Services advertises "mcp:read" and "mcp:write" in the scopes_supported array of its live RFC 8414 OAuth 2.0 Authorization Server Metadata. That is the provider's ow...

MCP SERVER

JSON Schema 1

Standalone JSON Schema definitions for this provider's data models.

Sifive Duh

0 properties

JSON SCHEMA

Security Posture 3

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

Sifive Authentication

oauth2/openIdConnect · 1 scheme

SECURITY

Sifive Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Sifive Vulnerability Disclosure

security.txt · contact published

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Sifive Scopes

3 scopes · authorizationCode

3 scopes

SCOPES

Resources

Get Started 3

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

SignUp

SignUp

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

JSONSchema

JSONSchema

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

MCPServer

MCPServer

WellKnown

WellKnown

LLMsTxt

LLMsTxt

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

DataModel

ErrorCatalog

Conformance

Conventions

Lifecycle

Build 4

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

Packages

SDKs

CLI

Access & Security 5

Authentication, authorization, and security posture

Security

Security

VulnerabilityDisclosure

VulnerabilityDisclosure

DomainSecurity

DomainSecurity

Authentication

Authentication

OAuthScopes

OAuthScopes

Operate 2

Status, limits, changes, and where to get help

Support

Support

Community

Community

Commercial 2

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 3

The organization behind the API

Website

Website

Blog

Blog

BlogRSS

BlogRSS

Source (apis.yml)

aid: sifive
name: SiFive
description: 'SiFive is a semiconductor intellectual-property company founded by the creators of the RISC-V instruction set
  architecture at UC Berkeley — Krste Asanovic, Yunsup Lee and Andrew Waterman — and licenses configurable RISC-V processor
  core IP rather than manufacturing chips. Its catalog spans the Essential (E/S/U), Performance (P500/P600/P800), Intelligence
  (X100/X200/X300/XM) and Automotive (E6-A/E7-A/S7-A) core families plus system IP including SiFive Insight trace and debug,
  IOMMU Gen 2, Shield and WorldGuard. Customers configure a Core Design and generate a downloadable Dev Kit of RTL, testbench,
  software and documentation through SiFive Core Designer, delivered from the SiFive Cloud Services (SCS) portal at scs.sifive.com.
  The public developer surface is software tooling rather than a hosted REST API: the Freedom SDK for Metal and for Linux,
  Freedom Studio, Freedom Tools, the SiFive Kernel Library and the open-source DUH hardware-IP description toolchain and JSON
  Schema published on npm and GitHub.'
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: self-serve
  trial: false
  try_now: false
  public: false
  label: Self-serve signup
  confidence: medium
  source:
  - authentication
  - scopes
  - security
  generated: '2026-09-02'
  method: derived
image: https://www.sifive.com/assets/sifive-ogp.jpeg
url: https://raw.githubusercontent.com/api-evangelist/sifive/refs/heads/main/apis.yml
x-type: company
x-source: harvest:secondary-market
specificationVersion: '0.23'
created: '2026-08-05'
modified: '2026-08-05'
tags:
- Company
- Semiconductors
- RISC-V
- Processor IP
- Chip Design
- Embedded
- Hardware
- Developer Tools
- Electronic Design Automation
- Authentication
tags_raw:
- Company
- Semiconductors
- RISC-V
- Processor IP
- Chip Design
- Embedded
- Hardware
- Developer Tools
- Electronic Design Automation
- OAuth
apis:
- aid: sifive-cloud-services-oauth
  name: SiFive Cloud Services OAuth 2.0
  description: The OAuth 2.0 authorization server that fronts the SiFive Cloud Services (SCS) portal at scs.sifive.com, where
    SiFive Core Designer and the rest of the SiFive development tooling are delivered. It publishes RFC 8414 authorization
    server metadata anonymously at /.well-known/oauth-authorization-server, supports the authorization_code and refresh_token
    grants with PKCE (S256), exposes token, introspection, revocation, userinfo, dynamic client registration and JWKS endpoints,
    and advertises the openid, mcp:read and mcp:write scopes. The protected resources behind it — including the MCP surface
    implied by those scopes — require a SiFive customer account.
  humanURL: https://www.sifive.com/software/sifive-core-designer
  baseURL: https://scs.sifive.com/o
  tags:
  - Authentication
  - Authorization
  - Identity
  - Chip Design
  - Developer Tools
  tags_raw:
  - OAuth
  - Authorization
  - Identity
  - Chip Design
  - Developer Tools
  properties:
  - type: Authentication
    url: authentication/sifive-authentication.yml
  - type: OAuthScopes
    url: scopes/sifive-scopes.yml
  - type: ErrorCatalog
    url: errors/sifive-problem-types.yml
  - type: WellKnown
    url: well-known/sifive-well-known.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: MCPServer
  url: mcp/sifive-mcp.yml
- type: Website
  url: https://www.sifive.com/
- type: DeveloperPortal
  url: https://www.sifive.com/developers
- type: Documentation
  url: https://www.sifive.com/documentation
- type: GettingStarted
  url: https://www.sifive.com/software
- type: Support
  url: https://support.sifive.com/
- type: Community
  url: https://forums.sifive.com/
- type: Blog
  url: https://www.sifive.com/blog
- type: BlogRSS
  url: https://www.sifive.com/blog/rss.xml
- type: GitHubOrganization
  url: https://github.com/sifive
- type: SignUp
  url: https://scs.sifive.com/accounts/login/
- type: TermsOfService
  url: https://www.sifive.com/terms
- type: PrivacyPolicy
  url: https://www.sifive.com/privacy
- type: Security
  url: https://www.sifive.com/psirt-report-vulnerability
- type: VulnerabilityDisclosure
  url: security/sifive-vulnerability-disclosure.yml
- type: DomainSecurity
  url: security/sifive-domain-security.yml
- type: WellKnown
  url: well-known/sifive-well-known.yml
- type: Authentication
  url: authentication/sifive-authentication.yml
- type: OAuthScopes
  url: scopes/sifive-scopes.yml
- type: Packages
  url: packages/sifive-packages.yml
- type: SDKs
  url: packages/sifive-packages.yml
- type: CLI
  url: cli/sifive-cli.yml
- type: JSONSchema
  url: json-schema/sifive-duh-schema.json
- type: DataModel
  url: data-model/sifive-data-model.yml
- type: ErrorCatalog
  url: errors/sifive-problem-types.yml
- type: Conformance
  url: conformance/sifive-conformance.yml
- type: Conventions
  url: conventions/sifive-conventions.yml
- type: Lifecycle
  url: lifecycle/sifive-lifecycle.yml
- type: LLMsTxt
  url: llms/sifive-llms.txt
x-enrichment:
  date: '2026-08-05'
  status: enriched
  artifacts_added: 17
  pass: local-v1
x-coverage:
  state: covered
  reason: null
  detail: 'SiFive has no public REST API and publishes no OpenAPI — contract discovery probed /openapi.json, /openapi.yaml,
    /swagger.json, /api-docs, /graphql and /.well-known/api-catalog on both www.sifive.com and scs.sifive.com and every one
    returned 404. What it does publish was captured: a live RFC 8414 OAuth 2.0 authorization server on the SiFive Cloud Services
    portal (whose scopes_supported names mcp:read and mcp:write, so an MCP server exists behind the customer login even though
    no MCP endpoint is publicly reachable or documented), the draft-07 DUH hardware-IP JSON Schema, the first-party DUH npm/PyPI
    toolchain, and an ISO/IEC 29147 PSIRT disclosure program.'
  evidence:
  - url: https://scs.sifive.com/.well-known/oauth-authorization-server
    status: 200
  - url: https://www.sifive.com/psirt-report-vulnerability
    status: 200
  - url: https://www.sifive.com/openapi.json
    status: 404
  - url: https://scs.sifive.com/mcp
    status: 404
  - url: https://www.sifive.com/.well-known/agent-card.json
    status: 404
  checked: '2026-08-05'

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/sifive"

All providers

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

Every operation they expose

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

How their score was established

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

Discovery needs no key. Ratings and market analysis are Pro.

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.