# Zeta — API Agent Score

> Score: 67/100 (Grade: C) | Domain: zeta.tech | Rubric: 1.0.0 | Checked: August 10, 2026

Zeta scored 67/100 (C), classified "partially-ready".

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

## Summary

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

## Category Scores

- API Design: 80/100 (A)
- Developer Experience: 54/100 (D)
- Agent Discovery: 67/100 (C)
- Agent Understanding: 59/100 (D)
- Agent Usability: 72/100 (B)

## Check Results

### API Design

- [warn] Schema coverage & depth — 64 of 590 public signatures use loose types (anyTypeRatio=0.108). Investigated: sdk 83%.
- [pass] Example coverage — README is present and includes a runnable quickstart. Investigated: sdk 100%, docs 0%.
- [warn] Security & governance hygiene — security.txt present but missing Contact; missing or expired Expires. Investigated: wellknown 50%.
- [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

- [pass] Self-service developer portal — Self-service signup at https://fusion.tech/us/docs/account-holder/create-accountholder/; free tier / sandbox documented. Investigated: docs 100%.
- [warn] Description completeness — 170/234 operations lack a description. Investigated: sdk 27%.
- [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%.
- [skip] Changelog published — No surface produced evidence for this capability in this run.

### Agent Discovery

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

### Agent Understanding

- [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] 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

- [pass] Idempotency documented — Built-in retry machinery is present (grep-derived). Investigated: sdk 100%.
- [warn] Sandbox separation — No test-mode flag or sandbox environment is exposed. Investigated: sdk 50%.
- [fail] Runnable collection with test scripts — No public Postman workspace discovered for the org. Investigated: platform 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

Zeta's API design and overall usability foundations are solid, but the program has two critical gaps that will block partner and agent adoption: agents cannot find or understand the API context they need to integrate confidently, and partners lack the hands-on onboarding materials — quickstarts, code samples, and runnable collections — to reach a first successful call without friction. Prioritize making the API surface machine-readable and agent-navigable first, then close the onboarding gap so human partners and their AI agents can go from discovery to working integration in minutes, not weeks.