Credo AI Use Case Questionnaires 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
12 operations
across 8 paths,
and defines 22 schemas.
It is described by OpenAPI 3.2.0.
Requests are made against a single base URL, /api/v2/credoai.
12 operations8 paths22 schemas2 DELETE5 GET1 PATCH4 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 Questionnaires 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, 5 GET, 1 PATCH, 4 POST. Each is listed below with its method, path, parameters, and response codes.
use_case_questionnaires 12
Operations related to questionnaires, questionnaire sections, and questionnaire evidence for a specific use case
Update usecasequestionnaires. If version is provided, it will upgrade questinnaire to that version and other attributes will be ignored. If duedate is provided, it will update duedate of usecasequest…
The contract defines 22 schemas that model the data the API accepts and returns. The most detailed are UseCaseQuestionnaireSectionResource (4 properties), SectionFileResource (4 properties), UseCaseQuestionnaireResource (4 properties), TaskResource (4 properties). Each schema is shown below with its type and property counts.
UseCaseQuestionnaireSectionEvidenceCreateRequest
object
1 property
TaskResponse
object
A JSON-API document with a single [TaskResource](taskresource) resource
2 properties1 required
SectionFileResponse
object
A JSON-API document with a single [SectionFileResource](sectionfileresource) resource
2 properties1 required
TaskResource
object
4 properties
UseCaseQuestionnaireSectionResponse
object
A JSON-API document with a single [UseCaseQuestionnaireSectionResource](usecasequestionnairesectionresource) resource
2 properties1 required
EvidenceResponse
object
A JSON-API document with a single [EvidenceResource](evidenceresource) resource
2 properties1 required
EvidencesResponse
object
A collection of [EvidenceResource](evidenceresource)
1 property1 required
UseCaseControlTaskCreateRequest
object
1 property
UseCaseQuestionnaireCreateRequest
object
1 property
SectionFileCreateRequest
object
1 property
EvidenceResource
object
4 properties
UseCaseQuestionnaireSectionsResponse
object
A collection of [UseCaseQuestionnaireSectionResource](usecasequestionnairesectionresource)
1 property1 required
UseCaseQuestionnairesResponse
object
A collection of [UseCaseQuestionnaireResource](usecasequestionnaireresource)
1 property1 required
UseCaseQuestionnaireResponse
object
A JSON-API document with a single [UseCaseQuestionnaireResource](usecasequestionnaireresource) resource
2 properties1 required
ForbiddenError
object
1 property
AuthError
object
1 property
UseCaseQuestionnaireSectionResource
object
4 properties
UseCaseQuestionnaireResource
object
4 properties
SectionFileResource
object
4 properties
SectionFilesResponse
object
A page of [SectionFileResponse](sectionfileresponse) results
2 properties1 required
NotFoundError
object
1 property
UseCaseQuestionnaireUpdateRequest
object
1 property
Specification
The full machine-readable OpenAPI contract behind this narrative.
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.
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 Questionnaires 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.