# Census — API Agent Score

> Score: 49/100 (Grade: F) | Domain: getcensus.com | Rubric: 1.0.0 | Checked: July 24, 2026

Census scored 49/100 (F), classified "not-ai-ready".

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

## Summary

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

## Category Scores

- API Design: 40/100 (F)
- Developer Experience: 50/100 (D)
- Agent Discovery: 83/100 (A)
- Agent Understanding: 51/100 (D)
- Agent Usability: 40/100 (F)

## Check Results

### API Design

- [fail] Security & governance hygiene — No security.txt at /.well-known/security.txt or /security.txt. Investigated: wellknown 0%.
- [fail] Example coverage — No detectable code samples across 1 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] Changelog published — Newest official SDK activity 8 day(s) ago. Investigated: sdk 100%.
- [warn] Quickstart present — Quickstart page reachable (12 variants scanned starting at https://fivetran.com/docs/activations) but no runnable code sample detected in HTML or .md variant. Investigated: docs 50%.
- [fail] Self-service developer portal — No signup page detected across conventional paths (/signup, /sign-up, /register, /get-started, /console/signup, /dashboard/signup, /try, /try-free, /free, /free-trial, /start, /start-free). Investigated: docs 0%.
- [fail] Code samples in docs — No detectable code samples across 1 sampled docs pages. Investigated: docs 0%.
- [skip] Description completeness — No surface produced evidence for this capability in this run.

### Agent Discovery

- [pass] Registry & SDK presence — Indexed on Context7 (centeronbudget/getcensus, 85 snippets). Investigated: docs 100%, sdk 0%, cli 0%.
- [warn] Docs reachable, not hard auth-gated — Server ignores Accept: text/markdown header (0/50 sampled pages return markdown). Investigated: docs 75%.
- [warn] llms.txt present, valid & comprehensive — No llms.txt directive found in HTML of any of 50 sampled pages. Investigated: docs 69%.
- [warn] Crawlable / AEO — Sitemap present (0 entries) but carries no lastmod values. Investigated: wellknown 75%.

### Agent Understanding

- [warn] Agent-navigable, token-efficient docs — 6 of 50 pages have substantive content differences between markdown and HTML (avg 15% missing). Investigated: docs 60%.
- [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 sampled pages — likely a CSR-only docs site. 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 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

Getcensus's API program shows strength in agent discovery — documentation is reachable and crawlable — but the program has critical gaps in API contract quality and agent-readiness that will slow or block partner integration. The most urgent priorities are hardening the OpenAPI spec with security schemes and realistic examples, and creating the runnable, self-serve onboarding surface that partners and their AI agents need to go from discovery to working integration without hand-holding. Fixing these two areas will unlock the rest of the partner program's potential.