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 Use Case Controls API

Operations related to controls for a specific use case

Documentation Provider Profile APIs.io OpenAPI GitHub

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

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 14 operations across 10 paths, and defines 27 schemas. It is described by OpenAPI 3.2.0.

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

14 operations 10 paths 27 schemas 2 DELETE6 GET1 PATCH5 POST

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 Use Case Controls API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (Bearer).

Paths & Operations 14

Across 10 paths, the API surfaces 14 operations — 2 DELETE, 6 GET, 1 PATCH, 5 POST. Each is listed below with its method, path, parameters, and response codes.

use_case_controls 14

Operations related to controls for a specific use case

DELETE
/use_cases/{use_case_id}/controls/{control_id}/files/{id}
Deletes a specific file associated with a questionnaire control for a given use case.
CredoAIWeb.API.V2.UseCase.ControlFileController.delete 3 params → 204401403404
POST
/use_cases/{use_case_id}/controls/{control_id}/tasks
Create a new task for a specific control within a use case.
CredoAIWeb.API.V2.UseCase.ControlController.create_task 2 params body → 201401403404
DELETE
/use_cases/{use_case_id}/risk_control_links/{id}
Delete a specific risk control link associated with a use case.
CredoAIWeb.API.V2.UseCase.RiskControlLinkController.delete 2 params → 204401403404
GET
/use_cases/{use_case_id}/controls/{control_id}/evidences
Retrieve a list of evidences associated with a specific use case control.
CredoAIWeb.API.V2.UseCase.ControlEvidenceController.index 2 params → 200401
POST
/use_cases/{use_case_id}/controls/{control_id}/evidences
Create a new evidence entry for a specified requirement of a use case control.
CredoAIWeb.API.V2.UseCase.ControlEvidenceController.create 2 params body → 201401403
GET
/use_cases/{use_case_id}/controls/{control_id}/files
Retrieves a list of all supplementary files associated with a specific questionnaire control for a given use case.
CredoAIWeb.API.V2.UseCase.ControlFileController.index 2 params → 200401
POST
/use_cases/{use_case_id}/controls/{control_id}/files
Creates a new file associated with a specific questionnaire control for a given use case.
CredoAIWeb.API.V2.UseCase.ControlFileController.create 2 params body → 201401403
GET
/use_cases/{use_case_id}/controls/{id}/cookbook
Retrieve the cookbook associated with a specific control in a use case.
CredoAIWeb.API.V2.UseCase.ControlController.cookbook 2 params → 200401404
GET
/use_cases/{use_case_id}/controls
Retrieve a list of controls associated with a specific use case.
CredoAIWeb.API.V2.UseCase.ControlController.index 1 param → 200401404
POST
/use_cases/{use_case_id}/control_assignments
Creates tasks for multiple controls and assigns them to a user or team
CredoAIWeb.API.V2.UseCase.ControlsAssignmentController.create 1 param body → 201401403
GET
/use_cases/{use_case_id}/risk_control_links
Retrieve a list of risk control links associated with a specific use case.
CredoAIWeb.API.V2.UseCase.RiskControlLinkController.index 1 param → 200401404
POST
/use_cases/{use_case_id}/risk_control_links
Create a new risk control link for a specified use case.
CredoAIWeb.API.V2.UseCase.RiskControlLinkController.create 1 param body → 201401403404
GET
/use_cases/{use_case_id}/controls/{id}
Fetch detailed information about a specific control within a use case.
CredoAIWeb.API.V2.UseCase.ControlController.show 2 params → 200401404
PATCH
/use_cases/{use_case_id}/controls/{id}
Update the details of a specific control within a use case.
CredoAIWeb.API.V2.UseCase.ControlController.update 2 params body → 200401403404

Schemas 27

The contract defines 27 schemas that model the data the API accepts and returns. The most detailed are ControlFileResource (4 properties), UseCaseControlResource (4 properties), EvidenceResource (4 properties), UseCaseControlCookbookResource (4 properties). Each schema is shown below with its type and property counts.

TasksResponse
object
A collection of [TaskResource](taskresource)
1 property 1 required
UseCaseControlCookbookResource
object
4 properties
TaskResponse
object
A JSON-API document with a single [TaskResource](taskresource) resource
2 properties 1 required
UseCaseControlResource
object
4 properties
UseCaseControlEvidenceCreateRequest
object
1 property
UseCaseRiskControlLinkResponse
object
A JSON-API document with a single [UseCaseRiskControlLinkResource](usecaseriskcontrollinkresource) resource
2 properties 1 required
UseCaseControlsResponse
object
A collection of [UseCaseControlResource](usecasecontrolresource)
1 property 1 required
EvidencesResponse
object
A collection of [EvidenceResource](evidenceresource)
1 property 1 required
EvidenceResponse
object
A JSON-API document with a single [EvidenceResource](evidenceresource) resource
2 properties 1 required
TaskResource
object
4 properties
UseCaseRiskControlLinkResource
object
4 properties
ControlsAssignmentRequest
object
A JSON-API document with a single [ControlsAssignmentResource](controlsassignmentresource) resource
2 properties 1 required
UseCaseControlTaskCreateRequest
object
1 property
ControlFileCreateRequest
object
1 property
UseCaseControlUpdateRequest
object
1 property
UseCaseRiskControlLinkCreateRequest
object
1 property
UseCaseControlCookbookResponse
object
A JSON-API document with a single [UseCaseControlCookbookResource](usecasecontrolcookbookresource) resource
2 properties 1 required
ControlFileResponse
object
A JSON-API document with a single [ControlFileResource](controlfileresource) resource
2 properties 1 required
EvidenceResource
object
4 properties
ControlFileResource
object
4 properties
UseCaseRiskControlLinksResponse
object
A collection of [UseCaseRiskControlLinkResource](usecaseriskcontrollinkresource)
1 property 1 required
ForbiddenError
object
1 property
AuthError
object
1 property
UseCaseControlResponse
object
A JSON-API document with a single [UseCaseControlResource](usecasecontrolresource) resource
2 properties 1 required
ControlsAssignmentResource
object
4 properties
ControlFilesResponse
object
A page of [ControlFileResponse](controlfileresponse) results
2 properties 1 required
NotFoundError
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

credo-ai-use-case-controls-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
← Back to C APIs
API Details
ID
credo-ai:credo-ai-use-case-controls-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-use-case-controls-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/credo-ai-use-case-controls-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 Use Case Controls 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.