# Teller — API Agent Score

> Score: 61/100 (Grade: C) | Domain: teller.io | Rubric: 1.0.0 | Checked: July 24, 2026

Teller scored 61/100 (C), classified "partially-ready".

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

## Summary

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

## Category Scores

- API Design: 75/100 (B)
- Developer Experience: 46/100 (F)
- Agent Discovery: 85/100 (A)
- Agent Understanding: 54/100 (D)
- Agent Usability: 53/100 (D)

## Check Results

### API Design

- [pass] Schema coverage & depth — package.json "types" → dist/@types/index.d.ts. Investigated: sdk 100%.
- [pass] Example coverage — Code samples present on 5/8 pages across 1 language(s); broader multi-language coverage missing. Investigated: docs 100%, sdk 100%.
- [fail] Security & governance hygiene — No security.txt at /.well-known/security.txt or /security.txt. Investigated: wellknown 0%.
- [skip] Machine-readable, versioned contract — 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] Code samples in docs — Code samples present on 5/8 pages across 1 language(s); broader multi-language coverage missing. Investigated: docs 100%.
- [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] Quickstart present — No quickstart/getting-started page found at the conventional paths. Investigated: docs 0%.
- [fail] Changelog published — Official SDKs stale: newest activity 492 days ago. Investigated: sdk 0%.
- [skip] Description completeness — No surface produced evidence for this capability in this run.

### Agent Discovery

- [pass] Registry & SDK presence — Indexed on Context7 (websites/teller_io, 163 snippets). Investigated: docs 100%, sdk 58%, cli 0%.
- [warn] llms.txt present, valid & comprehensive — No llms.txt directive found in HTML of any of 16 pages. Investigated: docs 86%, sdk 0%.
- [warn] Docs reachable, not hard auth-gated — Server ignores Accept: text/markdown header (0/16 pages return markdown). Investigated: docs 75%.
- [warn] Crawlable / AEO — No sitemap discoverable via robots.txt or /sitemap.xml on the docs host. Investigated: wellknown 50%.

### Agent Understanding

- [warn] Agent-navigable, token-efficient docs — 1 of 16 pages have substantive content differences between markdown and HTML (avg 5% missing). Investigated: docs 70%.
- [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 3 assessed pages (3 JS-rendered). 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 1 surface description(s) with ≥6 tokens available; need at least 2 to compare.

### Agent Usability

- [pass] Sandbox separation — Sandbox environments are exposed (sandbox). Investigated: sdk 100%.
- [fail] Idempotency documented — No built-in retry machinery was found; transient failures are not retried. Investigated: sdk 0%.
- [fail] Runnable collection with test scripts — No public Postman workspace discovered for the org. Investigated: platform 0%.
- [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.

## Executive Summary

Teller's agent discovery posture is a genuine strength — docs are reachable and indexable today. However, the partner program has two critical gaps that will slow or block partner adoption: onboarding is almost entirely manual (no self-serve portal, no quickstart), and AI agents lack the structured context, runnable examples, and operational guardrails they need to integrate reliably. Prioritize building a self-serve, always-in-sync documentation experience first, then layer in runnable collections and operational documentation to let partners and their agents go from discovery to production without hand-holding.