# C3 — API Agent Score

> Score: 49/100 (Grade: F) | Domain: c3.ai | Rubric: 1.0.0 | Checked: July 30, 2026

C3 scored 49/100 (F), classified "not-ai-ready".

[View full report](https://www.postman.com/ai/ai-ready-apis/company/c3)
[All organizations](https://www.postman.com/ai/ai-ready-apis/llms.txt)

## Summary

- Overall: 49/100 (F)
- Classification: not-ai-ready

## Category Scores

- API Design: 45/100 (F)
- Developer Experience: 57/100 (D)
- Agent Discovery: 70/100 (B)
- Agent Understanding: 47/100 (F)
- Agent Usability: 40/100 (F)

## Check Results

### API Design

- [pass] Example coverage — Code samples in 3 language(s) across docs (top: shell, javascript, python); 0/20 pages have ≥ 2 languages on the same page. Investigated: docs 100%, sdk 0%.
- [fail] Schema coverage & depth — no .d.ts found. Investigated: sdk 0%.
- [fail] Security & governance hygiene — No security.txt at /.well-known/security.txt or /security.txt. Investigated: wellknown 0%.
- [skip] Machine-readable, versioned contract — No surface produced evidence for this capability in this run.
- [skip] Auth declared & discoverable — No surface produced evidence for this capability in this run.

### Developer Experience

- [pass] Code samples in docs — Code samples in 3 language(s) across docs (top: shell, javascript, python); 0/20 pages have ≥ 2 languages on the same page. Investigated: docs 100%.
- [warn] Quickstart present — Quickstart page reachable (2 variants scanned starting at https://docs.c3.ai/api/auth/signin?callbackUrl=%2Fapi%2Fquickstart) but no runnable code sample detected in HTML or .md variant. Investigated: docs 50%.
- [fail] Self-service developer portal — No self-service signup detected: no signup link found on the homepage or docs, and no conventional signup path (/signup, /sign-up, /register, /get-started, /console/signup, /dashboard/signup, /try, /try-free, /free, /free-trial, /start, /start-free, /join, /create-account, /account/signup, /auth/signup, /users/sign_up) resolved. Investigated: docs 0%.
- [skip] Description completeness — No surface produced evidence for this capability in this run.
- [skip] Changelog published — No surface produced evidence for this capability in this run.

### Agent Discovery

- [pass] Registry & SDK presence — Indexed on Context7 (websites/c3-lang, 1499 snippets). Investigated: docs 100%, sdk 100%, cli 0%.
- [warn] Docs reachable, not hard auth-gated — Server ignores Accept: text/markdown header (0/49 sampled pages return markdown). Investigated: docs 75%.
- [pass] Crawlable / AEO — Docs paths crawlable by all monitored AI agents. Investigated: wellknown 100%.
- [fail] llms.txt present, valid & comprehensive — No llms.txt found at any candidate location (https://docs.c3.ai/llms.txt, https://docs.c3.ai/docs/llms.txt). Investigated: docs 0%.

### Agent Understanding

- [warn] Agent-navigable, token-efficient docs — No sampled pages support .md URLs (0/49 tested). Investigated: docs 50%.
- [warn] Description consistency across surfaces — Mean pairwise description similarity across 2 surfaces (docs, sdk) is 3% (threshold 35% for full credit).
- [fail] Agent instructions file (AGENTS.md) — No AGENTS.md at the site root or /.well-known/. Investigated: wellknown 0%.
- [fail] Docs structured data — Neither JSON-LD nor OpenGraph/meta tags detected across 3 assessed pages (3 JS-rendered). Investigated: docs 0%.
- [skip] Machine-readable errors (RFC 9457) — No surface produced evidence for this capability in this run.
- [skip] Operation purpose clarity — No surface produced evidence for this capability in this run.

### Agent Usability

- [fail] Runnable collection with test scripts — No public Postman workspace discovered for the org. Investigated: platform 0%.
- [skip] Idempotency documented — No surface produced evidence for this capability in this run.
- [skip] Rate-limit signaling — No surface produced evidence for this capability in this run.
- [skip] Pagination documented & consistent — No surface produced evidence for this capability in this run.
- [skip] Sandbox separation — No surface produced evidence for this capability in this run.

## Executive Summary

C3's API program shows meaningful strengths in documentation reachability and overall discoverability, but faces critical gaps in two areas that directly block partner and agent adoption: API design quality (missing schema depth and security hygiene) and agent understanding (no machine-readable context files, no structured data, and no runnable examples). Left unaddressed, partners and their AI agents will be unable to reliably build against the API surface, increasing integration failures and support burden. The highest-impact priorities are hardening the contract and design layer first, then ensuring agents and partners can discover, parse, and execute against it without friction.