Globelabsglobelabs.com.ph

ScoredOct 25, 2026, 12:53 AM

Globelabs' API Design is a clear strength — the schema and contract surface is solid, giving partners a reliable foundation to build against. The most urgent gaps are in Agent Understanding and Agent Usability: docs lack the structured metadata that answer engines need to cite your APIs, and there is no retry or idempotency guidance to protect partners from transient failures in production.

API DesignA clean, typed, well-governed API contract agents can reason about2 pass1 warn0 fail94A+

Signal	Points	Findings	Rationale
Schema coverage & depthvia sdk	21.4/25	0/7 (0%) enum-like params are realized as constrained types (not bare strings). Investigated: sdk 86%. Fix: Realize spec enums as literal unions or named enum types instead of bare strings so agents can choose only valid values.	Typed, complete request/response schemas are what make agent function-calling possible.
Security & governance hygienevia sdk	15/15	Code is formatter-clean with zero linter errors and zero style warnings. Investigated: sdk 100%, wellknown 50%.	No leaked secrets, no critical lint violations, no OWASP API Top-10 spec smells, and a published vulnerability-disclosure channel.
Example coveragevia sdk	10/10	README is present and includes a runnable quickstart. Investigated: sdk 100%, docs 0%.	Examples carry shape semantics schemas under-specify — for humans and agents alike.
Machine-readable, versioned contract	—/25	No surface produced evidence for this capability in this run.	A current OpenAPI version with a declared versioning scheme lets agents reason about the contract.
Auth declared & discoverable	—/25	No surface produced evidence for this capability in this run.	Agents can only call an API when they can determine its auth posture — a declared scheme, or an explicit statement that none is required.

Developer ExperienceThe context both developers and agents need to integrate fast — onboarding, code samples, complete descriptions and worked examples2 pass0 warn2 fail62C

Signal	Points	Findings	Rationale
Self-service developer portalvia docs	29/29	Self-service signup available at https://globelabs.com.ph/, with a free tier or sandbox documented — an agent can onboard without contacting sales. Investigated: docs 100%.	A first call without a human in the loop — self-serve credentials, a free tier, or an API that needs none.
Description completenessvia sdk	15/15	26/26 operations carry a description. Investigated: sdk 100%.	Complete descriptions are the context humans and agents need to use endpoints.
Quickstart presentvia docs	0/25	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%. Fix: Publish a single-page quickstart that goes from zero to a first successful API call.	A quickstart is the fastest path from landing page to first successful call.
Code samples in docsvia docs	0/18	No code samples detected across 1 sampled docs pages, so a coding agent gets no ready-to-use examples. Investigated: docs 0%. Fix: Add copy-pasteable code samples to API reference and quickstart pages.	Multi-language samples shorten time-to-first-call.
Changelog published	—/13	No surface produced evidence for this capability in this run.	A published changelog lets partners track changes without surprise.

Agent DiscoveryPartners and their agents can find your APIs — llms.txt, registries, crawlable and reachable docs0 pass4 warn0 fail64C

Signal	Points	Findings	Rationale
Docs reachable, not hard auth-gatedvia docs	20/30	No alternative access paths detected for 1 auth-gated pages. Some access paths cannot be detected automatically: bundled SDK docs, CLI doc commands, and MCP servers. Investigated: docs 67%.	Agents can only index and fetch docs they can reach — past auth gates and over correct HTTP semantics.
llms.txt present, valid & comprehensivevia docs	15/30	No llms.txt found at any candidate location (https://developer.globelabs.com.ph/users/login/llms.txt, https://developer.globelabs.com.ph/llms.txt, https://developer.globelabs.com.ph/docs/llms.txt). Investigated: docs 50%, sdk 0%.	A valid, comprehensive llms.txt is the machine-readable entry point for agents.
Registry & SDK presencevia sdk	14/28	No MCP server, tool manifest, or list-tools capability is discoverable (server entrypoint: absent, tool manifest: unknown, list-tools: unknown). Investigated: sdk 50%, docs 0%, cli 0%. Fix: Ship an MCP server entrypoint and a derivable tool manifest (one tool per operation) so agents can discover the SDK surface.	Listing in MCP registries and publishing SDKs puts the API where agents and their tooling look.
Crawlable / AEOvia wellknown	6/12	No sitemap found via robots.txt or /sitemap.xml on the docs host, so AI search engines have no crawl map for your docs. Investigated: wellknown 50%. Fix: Publish an XML sitemap and reference it from robots.txt.	Bots allowed plus a fresh sitemap make docs findable by agent crawlers.

Agent UnderstandingAgents can correctly interpret your APIs — machine-readable errors, consistent descriptions, structured data, parseable docs1 pass3 warn1 fail74B

Signal	Points	Findings	Rationale
Operation purpose clarityvia sdk	22.9/25	Read/write classification is partial: 5/6 classified (1 read, 5 write). Investigated: sdk 92%. Fix: Use standard verbs (get/list/create/update/delete) and clear mutation semantics so agents can tell reads from writes.	Agents select the right endpoint from its summary + operationId; clear, named operations make tool-selection reliable — the strongest driver of correct tool choice.
Agent-navigable, token-efficient docsvia docs	22/22	All 1 pages contain server-rendered content. Investigated: docs 100%.	Server-rendered, clean, small-footprint docs are what an agent can cheaply fetch and parse correctly.
Machine-readable errors (RFC 9457)via sdk	14/28	Single base error "GlobeConnectError" present, but only 1 subclass found; a richer hierarchy lets consumers catch narrowly. Investigated: sdk 50%. Fix: Add specific error subclasses (e.g. per status family / category) under the base so consumers can distinguish failure modes.	RFC 9457 problem details and a documented error-code inventory let agents parse failures without burning tokens.
Agent instructions file (AGENTS.md)via sdk	5/10	No agents.md or skill.md context file found (nice-to-have for agent operation). Investigated: sdk 50%, wellknown 0%. Fix: Add an agents.md or skill.md describing how an agent should use this SDK (auth setup, key operations, gotchas).	An AGENTS.md gives coding agents explicit setup, auth, and usage instructions to interpret and operate the API — beyond llms.txt's link index.
Docs structured datavia docs	0/8	No JSON-LD or OpenGraph/meta tags found across 1 assessed pages (1 JS-rendered), so answer engines have nothing to cite. Investigated: docs 0%. Fix: Server-render structured data (JSON-LD) so AI answer engines can cite your docs.	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.
Description consistency across surfaces	—/7	Only 1 surface description(s) with ≥6 tokens available; need at least 2 to compare.	Every surface tells the same story about what the product is.

Agent UsabilityAgents have the context to use your APIs reliably, not just find them1 pass1 warn1 fail52D

Signal	Points	Findings	Rationale
Sandbox separationvia sdk	10/20	No test-mode flag or sandbox environment is exposed. Investigated: sdk 50%. Fix: Expose a test-mode flag or sandbox environment so agents can exercise the SDK safely.	An isolated environment lets agents exercise destructive operations safely.
Runnable collection with test scriptsvia sdk	9/9	README is present and includes a runnable quickstart. Investigated: sdk 100%, platform 0%.	A public, maintained collection with assertions is runnable truth agents validate against.
Idempotency documentedvia sdk	0/27	No built-in retry machinery was found; transient failures are not retried. Investigated: sdk 0%. Fix: Add built-in retry support (retry transient/retryable status codes with backoff) so consumers do not have to implement it themselves.	Documented idempotency lets agents retry safely.
Rate-limit signaling	—/22	No surface produced evidence for this capability in this run.	Machine-readable rate-limit headers let agents throttle adaptively.
Pagination documented & consistent	—/22	No surface produced evidence for this capability in this run.	Consistent, documented pagination lets agents traverse collections.

Want to improve your results?