# Giphy — API Agent Score

> Score: 75/100 (Grade: B) | Domain: giphy.com | Rubric: 1.0.0 | Checked: August 3, 2026

Giphy scored 75/100 (B), classified "partially-ready".

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

## Summary

- Overall: 75/100 (B)
- Classification: partially-ready

## Category Scores

- API Design: 96/100 (A+)
- Developer Experience: 66/100 (C)
- Agent Discovery: 65/100 (C)
- Agent Understanding: 81/100 (A)
- Agent Usability: 67/100 (C)

## Check Results

### API Design

- [pass] Machine-readable, versioned contract — Versioning declared (info.version="1.0") and url-versioning detected. Investigated: spec 100%, docs 100%.
- [pass] Schema coverage & depth — 100% of operations have documented request and response schemas. Investigated: spec 100%, sdk 75%.
- [pass] Auth declared & discoverable — Authentication required (global or on every operation). Investigated: spec 100%, docs 100%.
- [pass] Security & governance hygiene — No credential-shaped strings detected in spec. Investigated: spec 100%, wellknown 0%.
- [warn] Example coverage — README is present but has no runnable quickstart. Investigated: sdk 50%, spec 0%, docs 0%.

### Developer Experience

- [pass] Self-service developer portal — Self-service signup at https://giphy.com/login?next=%2Fdashboard%2Fsignup; no free tier or sandbox language detected. Investigated: docs 100%.
- [pass] Description completeness — 85% description completeness (target 90%+). Investigated: spec 100%, sdk 0%.
- [pass] Changelog published — Newest official SDK activity 31 day(s) ago. Investigated: sdk 100%, spec 0%, docs 0%.
- [fail] Quickstart present — No quickstart/getting-started page found at the conventional paths. Investigated: docs 0%.
- [fail] Code samples in docs — No detectable code samples across 1 sampled docs pages. Investigated: docs 0%.

### Agent Discovery

- [pass] Registry & SDK presence — Indexed on Context7 (giphy/giphy-js, 116 snippets). Investigated: docs 100%, sdk 100%, cli 0%.
- [warn] Docs reachable, not hard auth-gated — Server ignores Accept: text/markdown header (0/1 pages return markdown). Investigated: docs 75%.
- [warn] Crawlable / AEO — No sitemap discoverable via robots.txt or /sitemap.xml on the docs host. Investigated: wellknown 50%.
- [fail] llms.txt present, valid & comprehensive — No llms.txt found at any candidate location (https://developers.giphy.com/llms.txt, https://developers.giphy.com/docs/llms.txt). Investigated: docs 0%, sdk 0%.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — 4 distinct 4xx/5xx response codes documented. Investigated: spec 100%, docs 100%.
- [pass] Operation purpose clarity — 100% of operations have a clear summary + operationId an agent can select on. Investigated: spec 100%.
- [warn] Agent-navigable, token-efficient docs — No pages support .md URLs (0/1 tested). Investigated: docs 86%.
- [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 1 assessed pages (1 JS-rendered). Investigated: docs 0%.
- [skip] Description consistency across surfaces — Only 1 surface description(s) with ≥6 tokens available; need at least 2 to compare.

### Agent Usability

- [pass] Idempotency documented — Built-in retry machinery is present (grep-derived). Investigated: sdk 100%.
- [pass] Pagination documented & consistent — Pagination params detected on 5 list endpoint(s). Investigated: spec 100%, docs 100%.
- [warn] Sandbox separation — No test-mode flag or sandbox environment is exposed. Investigated: sdk 50%.
- [fail] Rate-limit signaling — No rate-limit response headers documented. Investigated: spec 0%, docs 0%.
- [fail] Runnable collection with test scripts — No public Postman workspace discovered for the org. Investigated: platform 0%.

## Executive Summary

Giphy's API design is a genuine strength — the contract is clean and machine-readable, giving partners and their agents a solid foundation to build against. The critical gaps are in discoverability and agent readiness: there is no llms.txt, no agent instructions file, no structured docs metadata, and no runnable collection with test scripts, meaning AI agents and new partners alike cannot find, parse, or confidently execute against the API without significant manual effort. Prioritize publishing a discoverable, agent-ready docs surface and a runnable collection first — those two moves unblock both human partners and the AI agents they rely on.