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

Cohere Check Api Key API

The Check Api Key API from Cohere — 1 operation(s) for check api key.

Cohere Check Api Key API is one of 17 APIs that Cohere publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Check Api Key. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 1 operation across 1 path, and defines 13 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, https://api.cohere.com.

1 operations 1 paths 13 schemas 1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.cohere.com
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Cohere Check Api Key API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth).

Paths & Operations 1

Across 1 path, the API surfaces 1 operation — 1 POST. Each is listed below with its method, path, parameters, and response codes.

Check Api Key 1
POST
/v1/check-api-key
Check API key
checkAPIKey 1 param → 200400401403404422429498

Schemas 13

The contract defines 13 schemas that model the data the API accepts and returns. The most detailed are checkAPIKey_Response_200 (3 properties), CheckAPIKeyRequestForbiddenError (2 properties), CheckAPIKeyRequestGatewayTimeoutError (2 properties), CheckAPIKeyRequestInternalServerError (2 properties). Each schema is shown below with its type and property counts.

CheckAPIKeyRequestGatewayTimeoutError
object
2 properties
CheckAPIKeyRequestClientClosedRequestError
object
2 properties
CheckAPIKeyRequestNotImplementedError
object
2 properties
CheckAPIKeyRequestUnprocessableEntityError
object
2 properties
CheckAPIKeyRequestNotFoundError
object
2 properties
CheckAPIKeyRequestBadRequestError
object
2 properties
CheckAPIKeyRequestUnauthorizedError
object
2 properties
CheckAPIKeyRequestTooManyRequestsError
object
2 properties
CheckAPIKeyRequestServiceUnavailableError
object
2 properties
CheckAPIKeyRequestInternalServerError
object
2 properties
checkAPIKey_Response_200
object
3 properties 1 required
CheckAPIKeyRequestForbiddenError
object
2 properties
CheckAPIKeyRequestInvalidTokenError
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

cohere-check-api-key-api-openapi.yml Raw ↑

Other APIs Cohere publishes across the network.

Cohere Chat API
Cohere Embed API
Cohere Rerank API
Cohere Classify API
Cohere Datasets API
Cohere Models API
Cohere Tokenize API
Cohere Detokenize API
Cohere Batches API
Cohere Connectors API
Cohere Embed Jobs API
Cohere /finetuning API
Where this information came from

This is an independent, third-party profile of Cohere Check Api Key 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.