# Jitterbit — API Agent Score

> Score: 49/100 (Grade: F) | Domain: jitterbit.com | Rubric: 1.0.0 | Checked: July 29, 2026

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

[View full report](https://www.postman.com/ai/ai-ready-apis/company/jitterbit)
[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: 43/100 (F)
- Developer Experience: 60/100 (C)
- Agent Discovery: 77/100 (B)
- Agent Understanding: 44/100 (F)
- Agent Usability: 40/100 (F)

## Check Results

### API Design

- [warn] Security & governance hygiene — security.txt present but missing Contact; missing or expired Expires. Investigated: wellknown 50%.
- [warn] Machine-readable, versioned contract — `--version` not supported. Investigated: cli 25%.
- [fail] Schema coverage & depth — no .d.ts found. Investigated: sdk 0%.
- [fail] Auth declared & discoverable — no auth/config hint in --help. Investigated: cli 0%.
- [fail] Example coverage — No detectable code samples across 20 sampled docs pages. Investigated: docs 0%, sdk 0%, cli 0%.

### Developer Experience

- [pass] Self-service developer portal — Self-service signup at https://www.jitterbit.com/get-started-with-jitterbit/; free tier / sandbox documented. Investigated: docs 100%.
- [warn] Quickstart present — Quickstart page reachable (1 variants scanned starting at https://docs.jitterbit.com/getting-started/) but no runnable code sample detected in HTML or .md variant. Investigated: docs 50%.
- [fail] Code samples in docs — No detectable code samples across 20 sampled docs pages. Investigated: docs 0%.
- [fail] Changelog published — Official SDKs stale: newest activity 1685 days ago. Investigated: sdk 0%.
- [skip] Description completeness — No surface produced evidence for this capability in this run.

### Agent Discovery

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

### Agent Understanding

- [warn] Agent-navigable, token-efficient docs — No sampled pages support .md URLs (0/50 tested). Investigated: docs 58%.
- [warn] Description consistency across surfaces — Mean pairwise description similarity across 2 surfaces (docs, sdk) is 2% (threshold 35% for full credit).
- [fail] Machine-readable errors (RFC 9457) — errors are prose, not a structured envelope. Investigated: cli 0%.
- [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] Operation purpose clarity — No surface produced evidence for this capability in this run.

### Agent Usability

- [fail] Idempotency documented — no `--dry-run` flag found. Investigated: cli 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.
- [skip] Sandbox separation — No surface produced evidence for this capability in this run.

## Executive Summary

Jitterbit's API program shows strength in agent discoverability but faces critical gaps in API design quality and agent readiness that will block partners and their AI agents from integrating confidently. The most urgent priorities are establishing a complete, well-typed machine-readable contract with rich examples, and layering in the agent-facing context — structured errors, instruction files, and runnable collections — that modern integration workflows depend on. Closing these gaps will compress partner onboarding from weeks to days and make Jitterbit's APIs viable targets for AI-assisted development.