# Placer.ai — API Agent Score

> Score: 53/100 (Grade: D) | Domain: placer.ai | Rubric: 1.0.0 | Checked: October 31, 2026

Placer.ai scored 53/100 (D), classified "not-ai-ready".

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

## Summary

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

## Category Scores

- API Design: 40/100 (F)
- Developer Experience: 64/100 (C)
- Agent Discovery: 81/100 (A)
- Agent Understanding: 68/100 (C)
- Agent Usability: 40/100 (F)

## Check Results

### API Design

- [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.
- [skip] Example coverage — No surface produced evidence for this capability in this run.

### Developer Experience

- [pass] Self-service developer portal — Signup page found at https://analytics.placer.ai/auth/signup, but no free tier or sandbox is documented in docs/pricing, so an agent may hit a paywall. 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] Code samples in docs — No surface produced evidence for this capability in this run.
- [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 — Official SDKs found in 3 distinct languages, covering the ones agents use most. Investigated: sdk 100%, docs 0%, cli 0%, mcp 0%, wellknown 0%.
- [warn] Docs reachable, not hard auth-gated — 50 JavaScript redirect(s) detected across 50 sampled pages. Investigated: docs 75%.
- [warn] llms.txt present, valid & comprehensive — Only 0/50 same-origin sampled links resolve (0%); 50 broken; 50 rate-limited (HTTP 429). Investigated: docs 71%.
- [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%.

### Agent Understanding

- [warn] Agent-navigable, token-efficient docs — 6 of 50 pages have substantive content differences between markdown and HTML (avg 7% missing). Investigated: docs 88%.
- [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] Docs structured data — 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 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

Placer.ai's API program shines in agent discovery — documentation is reachable, crawlable, and well-indexed. However, two gaps put partner and agent adoption at risk: the program lacks a fast, guided path to a first successful call (no quickstart, no runnable collection), and it is missing foundational machine-readable signals (security contact, agent instructions) that AI agents increasingly require to safely self-serve. Closing the runnable-onboarding gap first will unlock the largest partner-program lift, followed by the lightweight hygiene files that make the program trustworthy and agent-ready.