How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Credo AI

Credo AI Risks API

Endpoints for management of risk classifications, risk types, and risk scenarios

Documentation Provider Profile APIs.io OpenAPI GitHub

Credo AI Risks API is one of 40 APIs that Credo AI publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Risks. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, and authentication docs.

This API exposes 12 operations across 8 paths, and defines 17 schemas. It is described by OpenAPI 3.2.0.

Requests are made against a single base URL, /api/v2/credoai.

12 operations 8 paths 17 schemas 2 DELETE4 GET3 PATCH2 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
Base URL
https://api.credo.ai/api/v2/{tenant}
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Credo AI Risks API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (Bearer).

Paths & Operations 12

Across 8 paths, the API surfaces 12 operations — 2 DELETE, 4 GET, 3 PATCH, 2 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

risks 12

Endpoints for management of risk classifications, risk types, and risk scenarios

DELETE
/risk_type/{id}
Delete a risk type identified by its ID.
CredoAIWeb.API.V2.RiskTypeController.delete 1 param → 204401403404
GET
/risk_classifications
Retrieve the list of custom risk classifications.
CredoAIWeb.API.V2.RiskClassificationController.index → 200401
PUT
/risk_classifications
Update the custom risk classifications with the provided attributes.
CredoAIWeb.API.V2.RiskClassificationController.update body → 200401403
GET
/risk_scenarios
Retrieves a list of all available risk scenarios.
CredoAIWeb.API.V2.RiskScenarioController.index 14 params → 200401
PATCH
/risk_types/{id}
Update an existing risk type identified by its ID.
CredoAIWeb.API.V2.RiskTypeController.update 1 param body → 200401403404
DELETE
/custom_risk_scenarios/{id}
Deletes the custom risk scenario identified by its ID.
CredoAIWeb.API.V2.CustomRiskScenarioController.delete 1 param → 204401403404
PATCH
/custom_risk_scenarios/{id}
Updates an existing custom risk scenario identified by its ID.
CredoAIWeb.API.V2.CustomRiskScenarioController.update 1 param body → 200401403404
GET
/risk_scenarios/{id}
Get risk scenario
CredoAIWeb.API.V2.RiskScenarioController.show 1 param → 200401404
PATCH
/risk_scenarios/{id}
Updates the visibility status of a specific risk scenario.
CredoAIWeb.API.V2.RiskScenarioController.update 1 param body → 200401404
POST
/custom_risk_scenarios
Creates a new custom risk scenario with the provided attributes.
CredoAIWeb.API.V2.CustomRiskScenarioController.create body → 201401403
GET
/risk_types
Retrieve a list of all available risk types.
CredoAIWeb.API.V2.RiskTypeController.index → 200401
POST
/risk_types
Create a new risk type with the specified attributes.
CredoAIWeb.API.V2.RiskTypeController.create body → 201401403

Schemas 17

The contract defines 17 schemas that model the data the API accepts and returns. The most detailed are RiskClassificationResource (4 properties), RiskTypeResource (4 properties), RiskScenarioResource (4 properties), RiskTypeResponse (2 properties). Each schema is shown below with its type and property counts.

RiskTypeCreateRequest
object
1 property
RiskScenarioUpdateRequest
object
1 property
RiskTypeUpdateRequest
object
1 property
CustomRiskScenarioUpdateRequest
object
1 property
RiskScenarioResource
object
4 properties
RiskScenarioResponse
object
A JSON-API document with a single [RiskScenarioResource](riskscenarioresource) resource
2 properties 1 required
RiskClassificationsUpdateRequest
object
1 property
AuthError
object
1 property
RiskScenariosResponse
object
A collection of [RiskScenarioResource](riskscenarioresource)
1 property 1 required
RiskTypeResource
object
4 properties
RiskClassificationResource
object
4 properties
RiskTypesResponse
object
A collection of [RiskTypeResource](risktyperesource)
1 property 1 required
RiskClassificationsResponse
object
A collection of [RiskClassificationResource](riskclassificationresource)
1 property 1 required
RiskTypeResponse
object
A JSON-API document with a single [RiskTypeResource](risktyperesource) resource
2 properties 1 required
CustomRiskScenarioCreateRequest
object
1 property
NotFoundError
object
1 property
ForbiddenError
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

credo-ai-risks-api-openapi.yml Raw ↑

Other APIs Credo AI publishes across the network.

Credo AI Governance Intelligence Pro MCP Server
AE Profile APIs.io
Credo AI Alerts API
AE Profile APIs.io
Credo AI Audit Logs API
AE Profile APIs.io
Credo AI Comment Threads API
AE Profile APIs.io
Credo AI Entities API
AE Profile APIs.io
Credo AI Entity Control Assignments API
AE Profile APIs.io
Credo AI Entity Controls API
AE Profile APIs.io
Credo AI Entity Evidences API
AE Profile APIs.io
Credo AI Entity Policy Packs API
AE Profile APIs.io
Credo AI Entity Risk Scenario Controls API
AE Profile APIs.io
Credo AI Entity Risk Scenarios API
AE Profile APIs.io
Credo AI Entity Section Assignments API
AE Profile APIs.io
#Risks
← Back to C APIs
API Details
ID
credo-ai:credo-ai-risks-api
Base URL
https://api.credo.ai/api/v2/{tenant}
Docs
https://docs.sdk.credo.ai/docs/intro/
Provider
Credo AI
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=credo-ai-risks-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/credo-ai-risks-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

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

Where this information came from

This is an independent, third-party profile of Credo AI Risks API, 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.