# Airbyte — API Agent Score

> Score: 60/100 (Grade: C) | Domain: airbyte.com | Rubric: 1.0.0 | Checked: July 24, 2026

Airbyte scored 60/100 (C), classified "partially-ready".

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

## Summary

- Overall: 60/100 (C)
- Classification: partially-ready

## Category Scores

- API Design: 69/100 (C)
- Developer Experience: 83/100 (A)
- Agent Discovery: 96/100 (A+)
- Agent Understanding: 40/100 (F)
- Agent Usability: 45/100 (F)

## Check Results

### API Design

- [warn] Schema coverage & depth — 17 of 83 public signatures use loose types (anyTypeRatio=0.205). Investigated: sdk 82%.
- [pass] Example coverage — Code samples in 2 language(s) across docs (top: shell, python); 12/18 pages have ≥ 2 languages on the same page. Investigated: docs 100%, sdk 50%.
- [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 — Self-service signup at https://airbyte.com/signup; free tier / sandbox documented. Investigated: docs 100%.
- [pass] Code samples in docs — Code samples in 2 language(s) across docs (top: shell, python); 12/18 pages have ≥ 2 languages on the same page. Investigated: docs 100%.
- [pass] Changelog published — Newest official SDK activity 0 day(s) ago. Investigated: sdk 100%.
- [warn] Quickstart present — Quickstart page reachable (1 variants scanned starting at https://docs.airbyte.com/platform) but no runnable code sample detected in HTML or .md variant. Investigated: docs 50%.
- [warn] Description completeness — 16/35 operations lack a description. Investigated: sdk 54%.

### Agent Discovery

- [pass] llms.txt present, valid & comprehensive — llms-full.txt reachable at https://airbyte.com/llms-full.txt. Investigated: docs 100%, sdk 0%.
- [pass] Registry & SDK presence — Indexed on Context7 (websites/airbyte, 17855 snippets). Investigated: docs 100%, sdk 100%, cli 100%, mcp 0%, wellknown 0%.
- [warn] Crawlable / AEO — Sitemap present (1654 entries) but carries no lastmod values. Investigated: wellknown 75%.
- [skip] Docs reachable, not hard auth-gated — No surface produced evidence for this capability in this run.

### Agent Understanding

- [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 18 sampled pages — likely a CSR-only docs site. 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.
- [skip] Agent-navigable, token-efficient docs — No surface produced evidence for this capability in this run.

### Agent Usability

- [warn] Sandbox separation — No test-mode flag or sandbox environment is exposed. Investigated: sdk 50%.
- [fail] Idempotency documented — No built-in retry machinery was found; transient failures are not retried. Investigated: sdk 0%.
- [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

Airbyte's partner API program shows strong developer experience and discoverability fundamentals, but two areas are holding back partner and agent adoption: agents cannot reliably understand or act on the API surface (missing structured context, machine-readable instructions, and idempotency guidance), and the API contract has a security hygiene gap that creates trust and governance risk for partners. Closing the agent-understanding and agent-usability gaps should be the immediate priority, followed by hardening the API design layer to meet partner security expectations.