# FloQast — API Agent Score

> Score: 64/100 (Grade: C) | Domain: floqast.com | Rubric: 1.0.0 | Checked: July 29, 2026

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

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

## Summary

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

## Category Scores

- API Design: 92/100 (A+)
- Developer Experience: 67/100 (C)
- Agent Discovery: 63/100 (C)
- Agent Understanding: 80/100 (A)
- Agent Usability: 40/100 (F)

## Check Results

### API Design

- [pass] Auth declared & discoverable — Authentication required (global or on every operation). Investigated: spec 100%, docs 100%.
- [warn] Machine-readable, versioned contract — info.version="1.0.0" set but no versioning scheme (URL / header / media type) detected. Investigated: spec 88%, docs 75%.
- [warn] Schema coverage & depth — 79% of operations have documented schemas (target 95%+). Investigated: spec 75%.
- [pass] Security & governance hygiene — No credential-shaped strings detected in spec. Investigated: spec 100%, wellknown 0%.
- [pass] Example coverage — 23% example coverage. Investigated: spec 100%, docs 100%.

### Developer Experience

- [pass] Quickstart present — Quickstart at https://developer.floqast.app/docs/getting-started has a runnable sample in the .md variant (https://developer.floqast.app/docs/getting-started.md). Investigated: docs 100%.
- [pass] Code samples in docs — Code samples present on 2/13 pages across 2 language(s); broader multi-language coverage missing. Investigated: docs 100%.
- [pass] Description completeness — 94% of operations + parameters have substantive descriptions. Investigated: spec 100%.
- [fail] Self-service developer portal — No self-service signup detected: no signup link found 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. Investigated: docs 0%.
- [fail] Changelog published — No changelog URL or mention found in spec metadata. Investigated: spec 0%, docs 0%.

### Agent Discovery

- [warn] Docs reachable, not hard auth-gated — Server ignores Accept: text/markdown header (0/16 pages return markdown). Investigated: docs 75%.
- [warn] llms.txt present, valid & comprehensive — No llms.txt directive found in HTML of any of 17 pages. Investigated: docs 71%.
- [warn] Crawlable / AEO — Sitemap present (189 entries) but carries no lastmod values. Investigated: wellknown 75%.
- [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%.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — 6 distinct 4xx/5xx response codes documented. Investigated: docs 100%, spec 50%.
- [pass] Operation purpose clarity — 95% of operations have a clear summary + operationId an agent can select on. Investigated: spec 100%.
- [warn] Agent-navigable, token-efficient docs — 2 of 14 pages have substantive content differences between markdown and HTML (avg 7% missing). Investigated: docs 80%.
- [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

- [fail] Idempotency documented — 0% of mutating operations document idempotency. Investigated: spec 0%, docs 0%.
- [fail] Rate-limit signaling — No rate-limit response headers documented. Investigated: spec 0%, docs 0%.
- [fail] Pagination documented & consistent — 14 list endpoint(s) exist but no pagination params found. Investigated: spec 0%, docs 0%.
- [fail] Sandbox separation — No sandbox/test server declared across 3 server entries; no test-key prefixes 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

FloQast's API program shows strong foundations in API design and documentation structure, but partners and their agents face real friction in three areas that matter most to program outcomes: operational reliability, sandbox access, and discoverability. The most urgent priority is making the API safe and trustworthy to integrate against — partners cannot confidently build production workflows without documented rate limits, idempotency, pagination, or a sandbox environment. Closing those gaps, alongside adding runnable collections and a self-service portal with machine-readable context, will unlock partner self-sufficiency and enable AI agents to onboard and operate without manual support.