Jitterbitjitterbit.com
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.
API DesignA clean, typed, well-governed API contract agents can reason about0 pass2 warn3 fail43F
| Signal | Points | Findings | Rationale | |
|---|---|---|---|---|
| warn | Security & governance hygienevia wellknown | 7.5/15 | security.txt present but missing Contact; missing or expired Expires. Investigated: wellknown 50%. | No leaked secrets, no critical lint violations, no OWASP API Top-10 spec smells, and a published vulnerability-disclosure channel. |
| warn | Machine-readable, versioned contractvia cli | 6.3/25 | `--version` not supported. Investigated: cli 25%. | A current OpenAPI version with a declared versioning scheme lets agents reason about the contract. |
| fail | Schema coverage & depthvia sdk | 0/25 | no .d.ts found. Investigated: sdk 0%. | Typed, complete request/response schemas are what make agent function-calling possible. |
| fail | Auth declared & discoverablevia cli | 0/25 | no auth/config hint in --help. Investigated: cli 0%. | Agents can only authenticate when auth is declared, scoped, and discoverable. |
| fail | Example coveragevia docs | 0/10 | No detectable code samples across 20 sampled docs pages. Investigated: docs 0%, sdk 0%, cli 0%. | Examples carry shape semantics schemas under-specify — for humans and agents alike. |
Developer ExperienceThe context both developers and agents need to integrate fast — onboarding, code samples, complete descriptions and worked examples1 pass1 warn2 fail60C
| Signal | Points | Findings | Rationale | |
|---|---|---|---|---|
| pass | Self-service developer portalvia docs | 29/29 | Self-service signup at https://www.jitterbit.com/get-started-with-jitterbit/; free tier / sandbox documented. Investigated: docs 100%. | Self-serve key/account creation is the fast first call for partners, with no sales gate. |
| warn | Quickstart presentvia docs | 12.5/25 | 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%. | A quickstart is the fastest path from landing page to first successful call. |
| fail | Code samples in docsvia docs | 0/18 | No detectable code samples across 20 sampled docs pages. Investigated: docs 0%. | Multi-language samples shorten time-to-first-call. |
| fail | Changelog publishedvia sdk | 0/13 | Official SDKs stale: newest activity 1685 days ago. Investigated: sdk 0%. | A published changelog lets partners track changes without surprise. |
| na | Description completeness | —/15 | No surface produced evidence for this capability in this run. | Complete descriptions are the context humans and agents need to use endpoints. |
Agent DiscoveryPartners and their agents can find your APIs — llms.txt, registries, crawlable and reachable docs2 pass2 warn0 fail77B
| Signal | Points | Findings | Rationale | |
|---|---|---|---|---|
| pass | Registry & SDK presencevia docs | 28/28 | Indexed on Context7 (websites/jitterbit, 53888 snippets). Investigated: docs 100%, sdk 75%, cli 0%. | Listing in MCP registries and publishing SDKs puts the API where agents and their tooling look. |
| warn | Docs reachable, not hard auth-gatedvia docs | 22.5/30 | Server ignores Accept: text/markdown header (0/50 sampled pages return markdown). Investigated: docs 75%. | Agents can only index and fetch docs they can reach — past auth gates and over correct HTTP semantics. |
| pass | Crawlable / AEOvia wellknown | 12/12 | Docs paths crawlable by all monitored AI agents. Investigated: wellknown 100%. | Bots allowed plus a fresh sitemap make docs findable by agent crawlers. |
| warn | llms.txt present, valid & comprehensivevia docs | 10/30 | No llms.txt found at any candidate location (https://docs.jitterbit.com/llms.txt, https://docs.jitterbit.com/docs/llms.txt). Investigated: docs 33%. | A valid, comprehensive llms.txt is the machine-readable entry point for agents. |
Agent UnderstandingAgents can correctly interpret your APIs — machine-readable errors, consistent descriptions, structured data, parseable docs0 pass2 warn3 fail44F
| Signal | Points | Findings | Rationale | |
|---|---|---|---|---|
| warn | Agent-navigable, token-efficient docsvia docs | 12.8/22 | No sampled pages support .md URLs (0/50 tested). Investigated: docs 58%. | Server-rendered, clean, small-footprint docs are what an agent can cheaply fetch and parse correctly. |
| warn | Description consistency across surfaces | 0.5/7 | Mean pairwise description similarity across 2 surfaces (docs, sdk) is 2% (threshold 35% for full credit). | Every surface tells the same story about what the product is. |
| fail | Machine-readable errors (RFC 9457)via cli | 0/28 | errors are prose, not a structured envelope. Investigated: cli 0%. | RFC 9457 problem details and a documented error-code inventory let agents parse failures without burning tokens. |
| fail | Agent instructions file (AGENTS.md)via wellknown | 0/10 | No AGENTS.md at the site root or /.well-known/. Investigated: wellknown 0%. | An AGENTS.md gives coding agents explicit setup, auth, and usage instructions to interpret and operate the API — beyond llms.txt's link index. |
| fail | Docs structured datavia docs | 0/8 | Neither JSON-LD nor OpenGraph/meta tags detected across 3 assessed pages (3 JS-rendered). Investigated: docs 0%. | Structured data (JSON-LD/schema.org) on docs pages gives agents an unambiguous parse target and is what answer engines cite. Detected on the JS-rendered head (Firecrawl) for a bounded page budget, so JS-injected JSON-LD is now caught; pages we can't render are excluded rather than failed. |
| na | Operation purpose clarity | —/25 | No surface produced evidence for this capability in this run. | Agents select the right endpoint from its summary + operationId; clear, named operations make tool-selection reliable — the strongest driver of correct tool choice. |
Agent UsabilityAgents have the context to use your APIs reliably, not just find them0 pass0 warn2 fail40F
| Signal | Points | Findings | Rationale | |
|---|---|---|---|---|
| fail | Idempotency documentedvia cli | 0/27 | no `--dry-run` flag found. Investigated: cli 0%. | Documented idempotency lets agents retry safely. |
| fail | Runnable collection with test scriptsvia platform | 0/9 | No public Postman workspace discovered for the org. Investigated: platform 0%. | A public, maintained collection with assertions is runnable truth agents validate against. |
| na | Rate-limit signaling | —/22 | No surface produced evidence for this capability in this run. | Machine-readable rate-limit headers let agents throttle adaptively. |
| na | Pagination documented & consistent | —/22 | No surface produced evidence for this capability in this run. | Consistent, documented pagination lets agents traverse collections. |
| na | Sandbox separation | —/20 | No surface produced evidence for this capability in this run. | An isolated environment lets agents exercise destructive operations safely. |
Resources Discovered
The public resources we found for Jitterbit — the evidence behind the score. All discovered from public sources; nothing here requires access to your systems.
| Agent hints | Context7 (53,888) |
|---|