# Global E — API Agent Score

> Score: 65/100 (Grade: C) | Domain: global-e.com | Rubric: 1.0.0 | Checked: October 27, 2026

Global E scored 65/100 (C), classified "partially-ready".

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

## Summary

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

## Category Scores

- API Design: 92/100 (A+)
- Developer Experience: 65/100 (C)
- Agent Discovery: 91/100 (A+)
- Agent Understanding: 63/100 (C)
- Agent Usability: 40/100 (F)

## Check Results

### API Design

- [pass] Auth declared & discoverable — authentication is documented on the docs site at https://docs.global-e.com/authentication, even though it isn't declared in the API spec. Investigated: spec 100%, docs 100%.
- [warn] Schema coverage & depth — The request body of POST /checkout/CreateOrder has a structured shape (more than 5 top-level fields, or a nested object / array-of-objects field), which is harder for an agent to fill correctly. Investigated: spec 89%.
- [warn] Machine-readable, versioned contract — The API sets a version ("1.0.0") but exposes no versioning scheme in the URL, a header, or the media type, so an agent can't pin to a specific version. Investigated: spec 75%, docs 50%.
- [pass] Security & governance hygiene — No credential-shaped strings detected in spec. Investigated: spec 100%, wellknown 0%.
- [pass] Example coverage — Only 50% of parameters and responses (1 of 2) include examples (target 80%+), so an agent guesses payload shapes the schema under-specifies. Investigated: spec 100%, docs 0%.

### Developer Experience

- [pass] Self-service developer portal — Signup page found at https://www.global-e.com/join-us/, but no free tier or sandbox is documented in docs/pricing, so an agent may hit a paywall. Investigated: docs 100%.
- [pass] Description completeness — 100% of operations and parameters carry substantive descriptions (1 of 1 ops, 0 of 0 params), the main semantic cue an agent relies on. Investigated: spec 100%.
- [warn] Quickstart present — Quickstart page is reachable at https://docs.global-e.com/getting-started (1 variants scanned) but has no runnable code sample in its HTML or .md variant, so there's nothing to copy and run. Investigated: docs 50%.
- [fail] Code samples in docs — No code samples detected across 20 sampled docs pages, so a coding agent gets no ready-to-use examples. Investigated: docs 0%.
- [fail] Changelog published — No changelog link or mention appears in the spec, so an agent can't tell what changed before something breaks. Investigated: spec 0%, docs 0%.

### Agent Discovery

- [pass] Docs reachable, not hard auth-gated — All 1 pages are publicly accessible. Investigated: docs 100%.
- [pass] Registry & SDK presence — Indexed on Context7 (websites/global-e_enterprise_en, 3434 snippets). Investigated: docs 100%, sdk 0%, cli 0%.
- [warn] llms.txt present, valid & comprehensive — No llms-full.txt was found at any candidate origin, so agents can't grab your full docs in one fetch. Investigated: docs 65%.
- [pass] Crawlable / AEO — robots.txt lets all monitored AI crawlers reach the docs paths. Investigated: wellknown 100%.

### Agent Understanding

- [pass] Agent-navigable, token-efficient docs — All 1 pages contain server-rendered content. Investigated: docs 100%.
- [warn] Operation purpose clarity — Only 0% of operations (0 of 1) have a clear summary plus descriptive name, so an agent must guess purpose from the URL path for most. Investigated: spec 67%.
- [pass] Docs structured data — Machine-readable JSON-LD Article markup on 20 of 20 assessed pages (100%), with dateModified present. Investigated: docs 100%.
- [warn] Machine-readable errors (RFC 9457) — No error responses (4xx/5xx or a catch-all default) are documented anywhere in the spec, so an agent can't anticipate or handle failures. Investigated: spec 17%, docs 17%.
- [warn] Description consistency across surfaces — Mean pairwise description similarity across 2 surfaces (spec, docs) is 11% (threshold 35% for full credit).
- [fail] Agent instructions file (AGENTS.md) — No AGENTS.md at the site root or /.well-known/, so coding agents have no ready-made setup and usage instructions. Investigated: wellknown 0%.

### Agent Usability

- [fail] Idempotency documented — Only 0% of mutating operations (0 of 1) document idempotency, so an agent's retries can create duplicate writes. Investigated: spec 0%, docs 0%.
- [fail] Rate-limit signaling — No rate-limit response headers are documented, so an agent can't tell when it is approaching a limit and will get throttled. Investigated: spec 0%, docs 0%.
- [fail] Sandbox separation — None of the 1 declared server(s) is a sandbox/test host, and no test-key prefixes are documented, so agents can only hit production. Investigated: spec 0%, docs 0%.
- [fail] Runnable collection with test scripts — No public Postman workspace found for the org, so there's no runnable collection an agent can execute against. Investigated: platform 0%.
- [skip] Pagination documented & consistent — No surface produced evidence for this capability in this run.

## Executive Summary

Global E's API contract and discoverability are strong — partners and agents can find and read the surface without friction. The critical gaps are in operational reliability and agent readiness: there is no sandbox environment, no idempotency or rate-limit guidance, no runnable examples, and no agent instruction file, meaning partners and their AI agents are forced to experiment directly against production with no safety net and no reliable context to build from. Prioritize making the API safe and executable first — sandbox separation and runnable collections — then layer in the operational signals (idempotency, rate-limits, changelog) and agent-specific context files that let autonomous agents operate without human intervention.