# BigCommerce — API Agent Score

> Score: 80/100 (Grade: A) | Domain: bigcommerce.com | Rubric: 1.0.0 | Checked: July 24, 2026

BigCommerce scored 80/100 (A), classified "ai-ready".

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

## Summary

- Overall: 80/100 (A)
- Classification: ai-ready

## Category Scores

- API Design: 75/100 (B)
- Developer Experience: 71/100 (B)
- Agent Discovery: 100/100 (A+)
- Agent Understanding: 68/100 (C)
- Agent Usability: 86/100 (A)

## Check Results

### API Design

- [pass] Schema coverage & depth — 11/11 (100%) public params are fully typed (no any/**kwargs). Analyzer confirms all methods have a derivable input schema. Investigated: sdk 100%.
- [pass] Example coverage — Code samples present on 1/1 pages across 1 language(s); broader multi-language coverage missing. Investigated: docs 100%, sdk 100%.
- [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] Self-service developer portal — Signup page at https://www.bigcommerce.com/free-trial/ (CSR-rendered — body classifier inconclusive); free tier / sandbox documented in pricing/docs. Investigated: docs 100%.
- [pass] Code samples in docs — Code samples present on 1/1 pages across 1 language(s); broader multi-language coverage missing. Investigated: docs 100%.
- [pass] Changelog published — Newest official SDK activity 0 day(s) ago. Investigated: sdk 100%.
- [warn] Description completeness — 22/31 operations lack a description. Investigated: sdk 29%.
- [fail] Quickstart present — No quickstart/getting-started page found at the conventional paths. Investigated: docs 0%.

### Agent Discovery

- [pass] llms.txt present, valid & comprehensive — llms-full.txt reachable at https://developer.bigcommerce.com/llms-full.txt. Investigated: docs 100%, sdk 0%.
- [pass] Registry & SDK presence — Discovered SDKs in 4 distinct languages. Investigated: sdk 100%, docs 0%, cli 0%.
- [pass] Crawlable / AEO — Docs paths crawlable by all monitored AI agents. Investigated: wellknown 100%.
- [skip] Docs reachable, not hard auth-gated — No surface produced evidence for this capability in this run.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — Single base error "HttpException" with 7 subclasses. Investigated: sdk 100%.
- [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 1 assessed pages (1 JS-rendered). Investigated: docs 0%.
- [skip] Operation purpose clarity — No surface produced evidence for this capability in this run.
- [skip] Agent-navigable, token-efficient docs — No surface produced evidence for this capability in this run.
- [skip] Description consistency across surfaces — Only 0 surface description(s) with ≥6 tokens available; need at least 2 to compare.

### Agent Usability

- [pass] Idempotency documented — Built-in retry machinery is present (grep-derived). Investigated: sdk 100%.
- [pass] Sandbox separation — Sandbox environments are exposed (sandbox). Investigated: sdk 100%.
- [fail] Runnable collection with test scripts — No public Postman workspace discovered for the org. Investigated: platform 0%.
- [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.

## Executive Summary

BigCommerce's API program shows genuine strength in agent usability overall, but two areas demand immediate attention: the API contract has security and governance gaps that erode partner trust before integration begins, and the documentation layer is invisible to AI agents — missing the structured signals, machine-readable files, and runnable context that coding agents need to work autonomously. Closing these gaps will let partners and their agents move from discovery to a working integration without friction or guesswork.
