# Globo — API Agent Score

> Score: 69/100 (Grade: C) | Domain: globo.com | Rubric: 1.0.0 | Checked: September 29, 2026

Globo scored 69/100 (C), classified "partially-ready".

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

## Summary

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

## Category Scores

- API Design: 100/100 (A+)
- Developer Experience: 44/100 (F)
- Agent Discovery: 62/100 (C)
- Agent Understanding: 79/100 (B)
- Agent Usability: 62/100 (C)

## Check Results

### API Design

- [pass] Schema coverage & depth — 33/33 (100%) public params are fully typed (no any/**kwargs). Analyzer confirms all methods have a derivable input schema. Investigated: sdk 100%.
- [pass] Security & governance hygiene — Code is formatter-clean with zero linter errors and zero style warnings. Investigated: sdk 100%, wellknown 0%.
- [pass] Example coverage — README is present and includes a runnable quickstart. Investigated: sdk 100%, docs 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

- [warn] Description completeness — 558/632 operations carry a description. Investigated: sdk 88%.
- [fail] Self-service developer portal — No self-service signup detected — no signup link on the homepage or docs, and no conventional signup path (/signup, /sign-up, /register, /get-started, /console/signup, /dashboard/signup, /try, /try-free, /free, /free-trial, /start, /start-free, /join, /create-account, /account/signup, /auth/signup, /users/sign_up) resolved — so an agent can't onboard on its own. Investigated: docs 0%.
- [fail] Quickstart present — No quickstart or getting-started page found at the conventional docs paths, so new developers and agents have no obvious first step. Investigated: docs 0%.
- [fail] Code samples in docs — No code samples detected across 2 sampled docs pages, so a coding agent gets no ready-to-use examples. Investigated: docs 0%.
- [skip] Changelog published — No surface produced evidence for this capability in this run.

### Agent Discovery

- [pass] Docs reachable, not hard auth-gated — All 1 pages are publicly accessible. Investigated: docs 100%.
- [warn] Registry & SDK presence — No MCP server, tool manifest, or list-tools capability is discoverable (server entrypoint: absent, tool manifest: unknown, list-tools: unknown). Investigated: sdk 42%, docs 0%, cli 0%.
- [warn] Crawlable / AEO — Sitemap has lastmod on only 100% of entries, or its newest entry is over 90 days old. Investigated: wellknown 75%.
- [fail] llms.txt present, valid & comprehensive — No llms.txt found at any candidate location (https://globonetworkapi.readthedocs.io/en/latest/llms.txt, https://globonetworkapi.readthedocs.io/llms.txt, https://globonetworkapi.readthedocs.io/docs/llms.txt). Investigated: docs 0%, sdk 0%.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — Single base error "NetworkAPIClientError" with 131 subclasses. Investigated: sdk 100%.
- [pass] Agent-navigable, token-efficient docs — All 1 pages contain server-rendered content. Investigated: docs 100%.
- [warn] Operation purpose clarity — Read/write classification is partial: 400/632 classified (413 read, 219 write). Investigated: sdk 82%.
- [warn] Agent instructions file (AGENTS.md) — No agents.md or skill.md context file found (nice-to-have for agent operation). Investigated: sdk 50%, wellknown 0%.
- [fail] Docs structured data — No JSON-LD or OpenGraph/meta tags found across 2 assessed pages (2 JS-rendered), so answer engines have nothing to cite. Investigated: docs 0%.
- [fail] Description consistency across surfaces — Mean pairwise description similarity across 2 surfaces (docs, sdk) is 0% (threshold 35% for full credit).

### Agent Usability

- [pass] Sandbox separation — Sandbox environments are exposed (sandbox). Investigated: sdk 100%.
- [pass] Runnable collection with test scripts — README is present and includes a runnable quickstart. Investigated: sdk 100%, platform 0%.
- [fail] Idempotency documented — No built-in retry machinery was found; transient failures are not retried. Investigated: sdk 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

Globo's API program has meaningful strengths in operation semantics and crawlability, but partners and their AI agents face two critical blockers today: there is no self-service path to get started — no signup, no quickstart, no code samples — and the program is effectively invisible to AI-driven discovery tools because it lacks an llms.txt, structured metadata, and consistent descriptions across surfaces. Fixing the onboarding gap and the agent-discoverability gap in parallel will unlock the partner pipeline and let AI agents route to Globo's APIs without a sales conversation.