# AJA — API Agent Score

> Score: 64/100 (Grade: C) | Domain: aja.com | Rubric: 1.0.0 | Checked: November 10, 2026

AJA scored 64/100 (C), classified "partially-ready".

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

## Summary

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

## Category Scores

- API Design: 89/100 (A)
- Developer Experience: 40/100 (F)
- Agent Discovery: 71/100 (B)
- Agent Understanding: 92/100 (A+)
- Agent Usability: 45/100 (F)

## Check Results

### API Design

- [pass] Machine-readable, versioned contract — The API declares version "1.0.0" and uses url-based versioning, so an agent can pin to a stable contract. Investigated: spec 100%, docs 100%.
- [pass] Auth declared & discoverable — The MCP server at https://ablakarajanlat.hu/api/mcp accepts unauthenticated requests, so an agent knows it needs no credentials. Investigated: mcp 100%, spec 50%, docs 50%.
- [pass] Security & governance hygiene — No credential-shaped strings detected in spec. Investigated: spec 100%, sdk 100%, wellknown 0%.
- [warn] Schema coverage & depth — Only 58% of the 69 operations document request and response schemas, so an agent can't do function-calling against most endpoints. Investigated: spec 50%, sdk 0%.
- [pass] Example coverage — Only 56% of parameters and responses (28 of 50) include examples (target 80%+), so an agent guesses payload shapes the schema under-specifies. Investigated: spec 100%, sdk 100%, docs 0%.

### 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 1 sampled docs pages, so a coding agent gets no ready-to-use examples. Investigated: docs 0%.
- [fail] Description completeness — Only 20% of operations and parameters have descriptions (27 of 69 ops, 0 of 8 params), leaving an agent to guess what most endpoints do. Investigated: spec 0%.
- [fail] Changelog published — No changelog link or mention appears in the spec, so an agent can't tell what changed before something breaks. Investigated: spec 0%, docs 0%.

### 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/sdkdocs_aja, 28554 snippets). Investigated: docs 100%, sdk 25%, cli 0%, mcp 0%, wellknown 0%.
- [warn] Crawlable / AEO — 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%.
- [fail] llms.txt present, valid & comprehensive — No llms.txt found at any candidate location (https://sdkdocs.aja.com/llms.txt, https://sdkdocs.aja.com/docs/llms.txt). Investigated: docs 0%, sdk 0%.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — Only 1 distinct 4xx/5xx error codes are documented (plus 0 catch-all "default" responses), so an agent has limited failure branching. Investigated: docs 100%, spec 50%.
- [pass] Operation purpose clarity — Surface uses a single dominant casing convention (snake_case). Investigated: sdk 100%, spec 0%.
- [pass] Agent-navigable, token-efficient docs — All 1 pages contain server-rendered content. Investigated: docs 100%.
- [warn] Agent instructions file (AGENTS.md) — No agents.md or skill.md context file found (nice-to-have for agent operation). Investigated: sdk 50%, wellknown 0%.
- [warn] Docs structured data — Only OpenGraph/meta tags across 1 assessed pages — no JSON-LD for AI answer engines to cite. Investigated: docs 50%.
- [skip] Description consistency across surfaces — Only 1 surface description(s) with ≥6 tokens available; need at least 2 to compare.

### Agent Usability

- [warn] Sandbox separation — No test-mode flag or sandbox environment is exposed. Investigated: sdk 50%, spec 0%, docs 0%.
- [pass] Runnable collection with test scripts — README is present and includes a runnable quickstart. Investigated: sdk 100%, platform 0%.
- [fail] Idempotency documented — Only 0% of mutating operations (0 of 32) document idempotency, so an agent's retries can create duplicate writes. Investigated: spec 0%, docs 0%, sdk 0%.
- [fail] Rate-limit signaling — No rate-limit response headers are documented, so an agent can't tell when it is approaching a limit and will get throttled. Investigated: spec 0%, docs 0%.
- [fail] Pagination documented & consistent — The 10 list endpoint(s) expose no pagination parameters, forcing an agent into all-or-nothing reads. Investigated: spec 0%, docs 0%.

## Executive Summary

Aja's API program has clear strengths in schema design, structured data, and agent context — partners and their agents can trust the data shapes they receive. However, the program's most urgent gaps are in developer onboarding and operational reliability: there is no self-service entry point, no quickstart, and no code examples, meaning partners cannot get to a first working call without a sales conversation. At the same time, mutating operations lack idempotency documentation, rate-limit signals are absent, and list endpoints have no pagination — gaps that cause agent-driven integrations to fail in production. Closing the onboarding and reliability gaps is the highest-leverage work to convert partner interest into durable, expanding integrations.