# Yoofooz API Readiness Report

## API
**Name:** Cohere API
**Docs URL:** https://docs.cohere.com/
**Domain:** docs.cohere.com
**Generated At:** 2026-10-05T23:26:40.814227+00:00

## Certification
**Agent Readiness Score:** 65/100
**Certification Level:** Agent-Compatible With Gaps

## Agent Commerce Readiness
**Agent Commerce Score:** 45/100
**Agent Commerce Level:** Agent Commerce Emerging

This score is separate from the core Agent Readiness Score and evaluates MCP support, scoped agent identity, machine-native payments, consumption pricing, budget controls, rate controls, deterministic errors, auditability, least-privilege security, and agent observability.

## Category Scores
- Documentation Clarity: 10
- Machine Readable Spec: 10
- Authentication Clarity: 10
- Error Handling: 10
- Rate Limit Clarity: 10
- Agent Safe Workflow Support: 0
- Sandbox Availability: 0
- Webhook Event Support: 0
- Commercial Trust: 5
- Developer Experience: 10

## Strengths
- Documentation clarity
- Machine-readable specification (OpenAPI/GraphQL/etc.)
- Authentication model clarity
- Error handling and status codes
- Rate-limit / quota behavior
- Developer experience (SDKs, quickstart, CLI)

## Risks
- Agent-safe workflow primitives (idempotency, retries) signal not detected in docs.
- Sandbox / test-mode availability signal not detected in docs.
- Webhook / event support signal not detected in docs.
- Commercial trust (status, SLA, compliance) signal is partial; clearer documentation recommended.

## Recommended Next Steps
- Document idempotency keys, test mode, dry runs, and safe retry semantics for agents.
- Provide a sandbox / test mode with test API keys for safe agent testing.
- Expose webhook/event docs including event types, signature verification, and retry delivery.
- Strengthen: Publish status page, SLA, and security/compliance posture (SOC 2, GDPR, PCI as applicable).

## Evidence Signals

### Documentation clarity
- **Source:** https://docs.cohere.com/v1/docs/connector-authentication.md
- **Matched:** quickstart, request, response, docs
- **Evidence:** "...will have to modify your connector to forward the authorization header from the request to the connector to the request to the data source. a few quickstart connectors (google drive and slack) do this out of the box without any configuration, so you may wish to look at those to copy this functionality...."

- **Source:** https://docs.cohere.com/reference/oauthauthorize-connector.md
- **Matched:** parameters, request, response, examples, docs, reference
- **Evidence:** "...- `authorization` header (bearer token, required) — bearer authentication of the form `bearer `, where token is your auth token. request path parameters - `id` (string, required) — the id of the connector to authorize. query parameters - `after_token_redirect` (string, optional) — the url to redirect..."

### Machine-readable specification (OpenAPI/GraphQL/etc.)
- **Source:** https://docs.cohere.com/openapi.json
- **Matched:** openapi, api spec
- **Evidence:** "available apis select an api to view its openapi specification. cohere api cohere api"

- **Source:** https://docs.cohere.com/reference/errors.md
- **Matched:** api spec, schema
- **Evidence:** "...is not valid. this can happen when required fields are missing, or when the values provided are not valid. to resolve this error, consult [the api spec](https://docs.cohere.com/reference/about) to ensure that you are providing the correct fields and values. example error responses | message | |..."

### Authentication model clarity
- **Source:** https://docs.cohere.com/v1/docs/connector-authentication.md
- **Matched:** bearer token, oauth, access token, authentication, authorization, api key, keys
- **Evidence:** "...serviceauth: }); console.log(connector); })(); ``` now when you call the chat api with this connector specified, cohere will now pass the configured bearer token in the search request to your connector. option 2: oauth 2.0 the second method of authentication and authorization is **oauth 2.0**. users are..."

- **Source:** https://docs.cohere.com/reference/oauthauthorize-connector.md
- **Matched:** bearer token, oauth, authentication, authorization
- **Evidence:** "...for more information. reference: https://docs.cohere.com/reference/oauthauthorize-connector authentication - `authorization` header (bearer token, required) — bearer authentication of the form `bearer `, where token is your auth token. request path parameters - `id` (string, required) — the id..."

### Error handling and status codes
- **Source:** https://docs.cohere.com/reference/errors.md
- **Matched:** 400, 401, 404, 409, 429, 500, errors, status codes
- **Evidence:** "...codes and description) > understand cohere's http response codes and how to handle errors in various programming languages. # http status codes 400 - bad request 400 responses are sent when the body of the request is not valid. this can happen when required fields are missing, or when the values..."

- **Source:** https://docs.cohere.com/reference/oauthauthorize-connector.md
- **Matched:** 400, 401, 403, 404, 429, 500, errors
- **Evidence:** "...response 200 ok - `redirect_url` (string, optional) — the oauth 2.0 redirect url. redirect the user to this url to authorize the connector. errors 400 bad request error this error is returned when the request is not well formed. this could be because: - json is invalid - the request is missing..."

### Rate-limit / quota behavior
- **Source:** https://docs.cohere.com/reference/errors.md
- **Matched:** rate limit, rate limits, too many requests, 429, limits
- **Evidence:** "...not found. | | dataset with id my-dataset-id not found | | finetuned model xyz not found | 429 - too many requests 429 responses are sent when the rate limit has been exceeded. please consult the [rate limit documentation](https://docs.cohere.com/v2/docs/rate-limits) to understand the limits and how to..."

- **Source:** https://docs.cohere.com/docs/rate-limits.md
- **Matched:** rate limit, rate limits, limits
- **Evidence:** "...client integration (claude code, cursor, etc.), connect to the mcp server at https://docs.cohere.com/_mcp/server. # different types of api keys and rate limits > this page describes cohere api rate limits for production and evaluation keys. cohere offers two kinds of api keys: evaluation keys (free but..."

### Agent-safe workflow primitives (idempotency, retries)
- **Source:** https://docs.cohere.com/docs/model-vault/encrypted/security-model.md
- **Matched:** metadata
- **Evidence:** "...area. * attacks requiring deep physical access to the hardware (for example, power or electromagnetic analysis, or invasive chip probing). * metadata and traffic-pattern observation (timing, sizes, the model being called), even though payload contents stay protected. * availability: the..."

### Webhook / event support
- **Source:** https://docs.cohere.com/openapi/cohere-api-2.json
- **Matched:** events
- **Evidence:** "preambles are a part of the prompt used to adjust the model's overall behavior and conversation style, and use the `system` role.\n\nthe `system` role is also used for the contents of the optional `chat_history=` parameter."

### Commercial trust (status, SLA, compliance)
- **Source:** https://docs.cohere.com/reference/errors.md
- **Matched:** support, versioning, api version
- **Evidence:** "...or tool results must be specified. | | invalid request: query must not be empty or be only whitespace | | invalid request: model 'command-r' is not supported by the generate api | | invalid request: cannot specify both frequency\_penalty and presence\_penalty. | | invalid request: only one of..."

- **Source:** https://docs.cohere.com/openapi/cohere-api-2.json
- **Matched:** support, security
- **Evidence:** "...and [command r+ 08-2024](https://docs.cohere.com/docs/command-r-plus#august-2024-release).\n\n**note**: `command-r7b-12-2024` and newer models only support `\'contextual\'` and `\'strict\'` modes.\n\ncompatible deployments: cohere platform, azure, aws sagemaker/bedrock, private..."

### Developer experience (SDKs, quickstart, CLI)
- **Source:** https://docs.cohere.com/reference/oauthauthorize-connector.md
- **Matched:** sdk, cli
- **Evidence:** "...to: - an internal services taking too long to respond - `message` (string, optional) - `id` (string, optional) examples **response** ```json ``` **sdk code** ```go cohere go sdk package main import ( 'context' 'log' 'os' cohere 'github.com/cohere-ai/cohere-go/v2' client..."

- **Source:** https://docs.cohere.com/v1/docs/connector-authentication.md
- **Matched:** quickstart, cli
- **Evidence:** "...will have to modify your connector to forward the authorization header from the request to the connector to the request to the data source. a few quickstart connectors (google drive and slack) do this out of the box without any configuration, so you may wish to look at those to copy this functionality...."

## AI Analyst Summary
AI analysis unavailable: NVIDIA analysis failed: http 410

## Yoofooz Summary
This API has been evaluated for autonomous AI-agent usability. The score reflects documentation quality, machine-readable specification signals, authentication clarity, error handling, workflow safety, commercial trust, and developer experience.