# Phia — API Agent Score

> Score: 58/100 (Grade: D) | Domain: phia.com | Rubric: 1.0.0 | Checked: July 28, 2026

Phia scored 58/100 (D), classified "not-ai-ready".

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

## Summary

- Overall: 58/100 (D)
- Classification: not-ai-ready

## Category Scores

- API Design: 50/100 (D)
- Developer Experience: 55/100 (D)
- Agent Discovery: 95/100 (A+)
- Agent Understanding: 71/100 (B)
- Agent Usability: 40/100 (F)

## Check Results

### API Design

- [warn] Security & governance hygiene — security.txt present but served only at the legacy /security.txt path; missing Contact; missing or expired Expires. Investigated: wellknown 50%.
- [fail] Example coverage — No detectable code samples across 3 sampled docs pages. 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

- [pass] Self-service developer portal — Signup page at https://phia.com/signup; no free-tier language detected in docs/pricing. Investigated: docs 100%.
- [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 3 sampled docs pages. 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

- [pass] Docs reachable, not hard auth-gated — All 1 pages are publicly accessible. Investigated: docs 100%.
- [pass] Registry & SDK presence — Indexed on Context7 (websites/hexdocs_pm_phia_ui_0_1_17, 54 snippets). Investigated: docs 100%, sdk 0%, cli 0%, mcp 0%, wellknown 0%.
- [warn] llms.txt present, valid & comprehensive — llms.txt contains parseable links but doesn't fully follow the proposed structure: https://docs.phia.com/llms.txt: No blockquote summary found. Investigated: docs 92%.
- [warn] Crawlable / AEO — Sitemap present (3 entries) but carries no lastmod values. Investigated: wellknown 75%.

### Agent Understanding

- [pass] Agent-navigable, token-efficient docs — All 1 pages contain server-rendered content. Investigated: docs 100%.
- [warn] Docs structured data — JSON-LD on 1/1 assessed pages, but coverage is sparse or dateModified is missing. Investigated: docs 50%.
- [fail] Agent instructions file (AGENTS.md) — No AGENTS.md at the site root or /.well-known/. Investigated: wellknown 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 discovered for the org. 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

Phia's API program shows strong discoverability fundamentals, but partners and their AI agents face two critical blockers: the API contract lacks concrete examples that agents can build against, and there is no runnable collection to validate real workflows. Close behind, the onboarding experience is incomplete — missing a quickstart and code samples — meaning partners cannot get hands-on without friction. Prioritize making the API contract executable and example-rich first, then layer in guided onboarding so partners reach their first successful integration in minutes rather than weeks.