# Airbyte docs: AI Agent Readiness Score 67.5% (D+)

**67.5% · 54/80 · AI Agent Readiness Score · 24/30 reading points · 30/50 agent surface points**

Airbyte received 10 PASS votes and passed 3 of five agent surface checks. The clearest finding came from the find the exact limits task.

- Tested: 2026-08-19
- Published: 2026-08-20
- Battery: v1
- Scoring: reading 30 pts · surface 50 pts
- Docs: https://docs.airbyte.com/

Three AI models, GPT 5.6 Sol, Claude Opus 5, and DeepSeek v4 Flash, each read Airbyte’s public documentation independently and attempted five first-hour developer jobs: run the first data sync, find the exact limits, recover a failed sync, verify a notification webhook, use PyAirbyte.

No accounts, API calls, or code execution were used. Every verdict came from public pages and every published quotation passed a live verification check.

## Freshness

[How rechecks work](https://docsforagents.com/methodology/#freshness)

- Category: [Data pipelines & documents](https://docsforagents.com/grades/?category=data-pipelines)
- Tested: 2026-08-19
- Quotes verified: 2026-08-19
- Surface rechecked: 2026-09-21

No confirmed change since the test.

4 of 5 quoted passages still appear on the live pages. The quoted page changed for Find the exact limits.

## Agent surface checks · 30/50

| Check | Verdict | Points |
| --- | --- | --- |
| llms.txt | PASS | 10 |
| llms-full.txt | FAIL | 0 |
| Markdown mirror | PASS | 10 |
| MCP server | FAIL | 0 |
| Docs AI | PASS | 10 |

## The Reading Test · 24/30

| Task | GPT 5.6 Sol | Opus 5 | DeepSeek v4F | Consensus |
| --- | --- | --- | --- | --- |
| Run the first data sync | PASS | PARTIAL | PASS | PASS |
| Find the exact limits | PARTIAL | PARTIAL | FAIL | PARTIAL |
| Recover a failed sync | PASS | PASS | PARTIAL | PASS |
| Verify a notification webhook | PASS | PASS | PASS | PASS |
| Use PyAirbyte | PASS | PASS | PASS | PASS |

Docs platform: Docusaurus 3.10.1 (unscored) · verified 2026-08-19

## What to fix first

These 3 fixes could add up to 24 points to the AI Agent Readiness Score. The list ranks each fix by the points it would add. [How the ranking works](https://docsforagents.com/methodology/#what-to-fix-first)

1. **+10 points · llms-full.txt · check failed**

   **Found:** HTTP 404 at the tested documentation roots.

   **Fix:** Publish llms-full.txt at the docs root with the full text of every docs page in one plain-text file.

   **Evidence:** [docs.airbyte.com/llms-full.txt](https://docs.airbyte.com/llms-full.txt)

2. **+10 points · MCP server · check failed**

   **Found:** Initialize returned HTTP 404, and no candidate endpoint completed initialization.

   **Fix:** Run a public MCP server for the docs that answers a JSON-RPC initialize call and offers a docs search tool.

   **Evidence:** [docs.airbyte.com/mcp](https://docs.airbyte.com/mcp)

3. **+4 points · Find the exact limits · PARTIAL**

   **Found:** In the panel's reading, pages disagree on Plus workspace limits and on the Pro and Enterprise Flex sync interval.

   **Fix:** Publish one plan table with the workspace limit and minimum sync interval for Standard, Plus, Pro, and Enterprise Flex.

   **Evidence:** [docs.airbyte.com/platform/cloud/managing-airbyte-cloud/understand-airbyte-cloud-limits](https://docs.airbyte.com/platform/cloud/managing-airbyte-cloud/understand-airbyte-cloud-limits)

## What the docs get right

- **Verify a notification webhook: 3 PASS votes.** The procedure covers Slack app creation, event toggles, webhook entry, test delivery to the channel, and saving.
- **Use PyAirbyte: 3 PASS votes.** One page installs airbyte, reads source-faker, and iterates result.streams.items() using current stream terminology.
- **3 of 5 agent surface checks.** Present: llms.txt, markdown mirrors, docs AI. Missing: llms-full.txt, an MCP server.

## Run the first data sync

**PASS**

PASS consensus from 2 PASS, 1 PARTIAL.

Linked pages cover both connectors and ELT setup; scheduled connections sync immediately, and Succeeded confirms complete loading. The source, destination, and ELT connection steps form an explicitly linked chain, but the final step stops at "Airbyte takes you to the page for that connection, where you can manage it and initiate syncs" and never names the sync trigger or the success check, so triggering and confirming the first sync requires cross-referencing the sync-schedules page for the "Sync Now" button and the connection-status page for the result. The quickstart and connector setup pages provide a complete, unambiguous path from zero to first sync for both OSS and Cloud.

## Find the exact limits

**PARTIAL**

PARTIAL consensus from 2 PARTIAL, 1 FAIL.

The limits page lists all numbers, but /platform/next/ returned 404 and the workspace page excludes Plus. One page carries every requested number with plan attribution and no internal disagreement (Standard: 1 workspace per user and 60-minute minimum schedule; Plus: 15-minute minimum schedule; all plans: 1,000 discoverable streams, 1,000 synced streams, 20,000 fields, 20MB records), but the minimum schedule interval for the Cloud Pro and Enterprise Flex plans is unresolvable because the limits page says the restriction is removed while the schedule options list offers nothing finer than 15 minutes and labels that option Plus-only. Schedule limits are documented, but no numeric workspace, stream, field, or record-size limits are published per plan. The pricing page matrix shows Core/Standard/Pro/Enterprise Flex but omits Plus, creating ambiguity about which plan is current. Record-size limits are destination-specific only.

## Recover a failed sync

**PASS**

PASS consensus from 2 PASS, 1 PARTIAL.

Rate-limited streams wait and retry automatically; configuration errors require re-testing and saving the affected connector. Rate limiting and configuration failure get separate named sections with different recovery instructions and different UI colors, and the notification payload reference reinforces the split by documenting the errorType values config_error and transient_error. The notification payload docs distinguish config_error from transient_error, and the monitoring blog covers rate-limit auto-recovery with countdown UI. However, there is no single troubleshooting page for sync failures; the information is scattered across blog posts and the notification docs page.

## Verify a notification webhook

**PASS**

PASS consensus from 3 PASS.

The procedure covers Slack app creation, event toggles, webhook entry, test delivery to the channel, and saving. A single page covers the whole path in order: create the Slack app, turn on Incoming Webhooks, copy the webhook URL, toggle the events you want in the Webhook column, paste the URL, click Test, then Save changes, with a nine-row table of notifiable events and example JSON payloads. A complete two-part walkthrough covering Slack app creation, webhook URL generation, notification event selection, and a test button that verifies receipt before saving.

## Use PyAirbyte

**PASS**

PASS consensus from 3 PASS.

One page installs airbyte, reads source-faker, and iterates result.streams.items() using current stream terminology. The page gives pip install airbyte plus a runnable example that calls ab.get_source("source-faker", ...), select_all_streams(), and read(), and the connector page confirms the example is current by listing PyAirbyte in its availability row, documenting the count parameter used in the example, and naming the three streams the loop will print. Install, source config, check, stream selection, read, and iteration are all demonstrated with a single clear example using current API methods (get_source, install_if_missing, select_all_streams, result.streams).

## The receipt

> These limitations only apply to those using the Standard plan. If you upgrade to Plus, Pro, or Enterprise Flex, Airbyte removes these limitations.

The limits page lists all numbers, but /platform/next/ returned 404 and the workspace page excludes Plus.

- [docs.airbyte.com/platform/cloud/managing-airbyte-cloud/understand-airbyte-cloud-limits](https://docs.airbyte.com/platform/cloud/managing-airbyte-cloud/understand-airbyte-cloud-limits)

## Agent surface notes

Initialize returned HTTP 404, and no candidate endpoint completed initialization.

The live docs expose a public Ask AI control.

## Method note

This is a reading test of public documentation, not an execution test. No accounts were created and no API calls were run. The AI Agent Readiness Score counts fifteen reading votes at PASS 2, PARTIAL 1, and FAIL 0, for 30 possible points. Five agent surface checks add 10 points each. The total is 80. Consensus chips show each row majority and do not affect scoring. The panel split on 3 of five tasks. Quotes shown here were re-fetched and confirmed verbatim on 2026-08-19.

Methodology: https://docsforagents.com/methodology/

Canonical URL: https://docsforagents.com/reports/airbyte-docs-ai-agent-readiness/