# IPUMS — API Agent Score

> Score: 56/100 (Grade: D) | Domain: ipums.org | Rubric: 1.0.0 | Checked: October 22, 2026

IPUMS scored 56/100 (D), classified "not-ai-ready".

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

## Summary

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

## Category Scores

- API Design: 55/100 (D)
- Developer Experience: 72/100 (B)
- Agent Discovery: 70/100 (B)
- Agent Understanding: 62/100 (C)
- Agent Usability: 40/100 (F)

## Check Results

### API Design

- [pass] Example coverage — Code samples appear on 3 of 20 sampled docs pages across 2 language(s), but broader multi-language coverage is missing. Investigated: docs 100%.
- [fail] Security & governance hygiene — No security.txt found at /.well-known/security.txt or /security.txt, so there's no machine-readable security contact for agents or researchers. Investigated: wellknown 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 found at https://developer.ipums.org/docs/v2/get-started/, but no free tier or sandbox is documented in docs/pricing, so an agent may hit a paywall. Investigated: docs 100%.
- [pass] Code samples in docs — Code samples appear on 3 of 20 sampled docs pages across 2 language(s), but broader multi-language coverage is missing. Investigated: docs 100%.
- [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%.
- [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] Registry & SDK presence — Indexed on Context7 (ipums/ipumspy, 296 snippets). Investigated: docs 100%, cli 100%, sdk 0%.
- [warn] Docs reachable, not hard auth-gated — Server ignores Accept: text/markdown header (0/46 pages return markdown); 1 returned error pages. Investigated: docs 75%.
- [pass] Crawlable / AEO — robots.txt lets all monitored AI crawlers reach the docs paths. Investigated: wellknown 100%.
- [fail] llms.txt present, valid & comprehensive — No llms.txt found at any candidate location (https://developer.ipums.org/llms.txt, https://developer.ipums.org/docs/llms.txt). Investigated: docs 0%.

### Agent Understanding

- [warn] Agent-navigable, token-efficient docs — No pages support .md URLs (0/46 tested). Investigated: docs 76%.
- [warn] Docs structured data — Only OpenGraph/meta tags across 19 assessed pages — no JSON-LD for AI answer engines to cite. Investigated: docs 50%.
- [fail] Agent instructions file (AGENTS.md) — No AGENTS.md at the site root or /.well-known/, so coding agents have no ready-made setup and usage instructions. 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 1 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 found for the org, so there's no runnable collection an agent can execute against. 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

Ipums has a solid documentation foundation and good discoverability basics, but two areas put the partner program at real risk: agents and partners cannot execute real workflows against the API (no runnable collection exists), and the API surface is nearly invisible to AI-powered tooling — missing the machine-readable files that allow agents to find, understand, and act on your APIs without a sales conversation. Fixing agent discoverability and runnable access first will unlock self-serve partner onboarding and make Ipums APIs first-class citizens in AI-assisted development workflows.