# PEXA — API Agent Score

> Score: 48/100 (Grade: F) | Domain: pexa.co.uk | Rubric: 1.0.0 | Checked: August 24, 2026

PEXA scored 48/100 (F), classified "not-ai-ready".

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

## Summary

- Overall: 48/100 (F)
- Classification: not-ai-ready

## Category Scores

- API Design: 68/100 (C)
- Developer Experience: 40/100 (F)
- Agent Discovery: 51/100 (D)
- Agent Understanding: 51/100 (D)
- Agent Usability: 40/100 (F)

## Check Results

### API Design

- [pass] Security & governance hygiene — Valid security.txt at https://pexa.co.uk/.well-known/security.txt with a Contact line and an unexpired Expires date. Investigated: wellknown 100%.
- [fail] Example coverage — No code samples detected across 2 sampled docs pages, so a coding agent gets no ready-to-use examples. Investigated: docs 0%.
- [skip] Machine-readable, versioned contract — No surface produced evidence for this capability in this run.
- [skip] Schema coverage & depth — 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

- [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] Description completeness — No surface produced evidence for this capability in this run.
- [skip] Changelog published — No surface produced evidence for this capability in this run.

### Agent Discovery

- [warn] Docs reachable, not hard auth-gated — 16 of 18 pages return 200 for non-existent URLs (soft 404). Investigated: docs 75%.
- [warn] Crawlable / AEO — Sitemap has 2 entries but no lastmod values, so crawlers can't tell what changed recently. Investigated: wellknown 75%.
- [fail] llms.txt present, valid & comprehensive — No llms.txt found at any candidate location (https://developer.pexa.co.uk/llms.txt, https://developer.pexa.co.uk/docs/llms.txt). Investigated: docs 0%.
- [fail] Registry & SDK presence — Not indexed on Context7 — agents can't pull this API's docs on demand via Context7. Investigated: docs 0%, sdk 0%, cli 0%, mcp 0%, wellknown 0%.

### Agent Understanding

- [warn] Agent-navigable, token-efficient docs — 16 of 18 pages have substantive content differences between markdown and HTML (avg 65% missing). Investigated: docs 60%.
- [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%.
- [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%.
- [skip] Machine-readable errors (RFC 9457) — No surface produced evidence for this capability in this run.
- [skip] Operation purpose clarity — No surface produced evidence for this capability in this run.
- [skip] Description consistency across surfaces — Only 0 surface description(s) with ≥6 tokens available; need at least 2 to compare.

### Agent Usability

- [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] Idempotency documented — No surface produced evidence for this capability in this run.
- [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.
- [skip] Sandbox separation — No surface produced evidence for this capability in this run.

## Executive Summary

Pexa's API program has a strong foundation in its contract design, but partners and their AI agents currently face significant barriers at every stage of adoption. The two most critical gaps are developer onboarding — there is no self-service path, no quickstart, and no code samples — and agent discoverability, where the absence of llms.txt, registry presence, and machine-readable instructions means AI-powered tools cannot find or act on the API without manual intervention. Closing the onboarding and agent-readiness gaps should be the immediate priority, as they block both human partners and autonomous agents from making a first successful call.