# Tipalti — API Agent Score

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

Tipalti scored 62/100 (C), classified "partially-ready".

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

## Summary

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

## Category Scores

- API Design: 55/100 (D)
- Developer Experience: 58/100 (D)
- Agent Discovery: 69/100 (C)
- Agent Understanding: 47/100 (F)
- Agent Usability: 86/100 (A)

## Check Results

### API Design

- [warn] Schema coverage & depth — 0/1 (0%) public params are fully typed (no any/**kwargs). Analyzer reports not all methods have a derivable input schema. Investigated: sdk 40%.
- [pass] Example coverage — README is present and includes a runnable quickstart. Investigated: sdk 100%, docs 0%.
- [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] Self-service developer portal — Signup page at https://tipalti.com/get-started (CSR-rendered — body classifier inconclusive); free tier / sandbox documented in pricing/docs. Investigated: docs 100%.
- [warn] Quickstart present — Quickstart page reachable (10 variants scanned starting at https://developer.tipalti.com/quickstart) but no runnable code sample detected in HTML or .md variant. Investigated: docs 50%.
- [warn] Description completeness — 3/4 operations lack a description. Investigated: sdk 25%.
- [fail] Code samples in docs — No detectable code samples across 1 sampled docs pages. Investigated: docs 0%.
- [fail] Changelog published — Official SDKs stale: newest activity 1403 days ago. Investigated: sdk 0%.

### Agent Discovery

- [pass] Registry & SDK presence — Indexed on Context7 (websites/tipalti, 1835 snippets). Investigated: docs 100%, sdk 42%, cli 0%.
- [warn] Docs reachable, not hard auth-gated — 1 of 1 pages return 200 for non-existent URLs (soft 404). Investigated: docs 50%.
- [warn] llms.txt present, valid & comprehensive — No llms.txt found at any candidate location (https://developer.tipalti.com/llms.txt, https://developer.tipalti.com/docs/llms.txt); 1 failed to fetch. Investigated: docs 33%, sdk 0%.
- [warn] Crawlable / AEO — Sitemap present (0 entries) but carries no lastmod values. Investigated: wellknown 75%.

### Agent Understanding

- [warn] Agent-navigable, token-efficient docs — No pages support .md URLs (0/1 tested). Investigated: docs 71%.
- [fail] Machine-readable errors (RFC 9457) — No single common SDK base error class was found; errors do not share one root. Investigated: sdk 0%.
- [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] 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

- [pass] Idempotency documented — Built-in retry machinery is present (grep-derived). Investigated: sdk 100%.
- [pass] Sandbox separation — Sandbox environments are exposed (sandbox). Investigated: sdk 100%.
- [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

Tipalti's API program shows strength in overall agent usability but has critical gaps in three areas that will stall partner adoption: agents and developers cannot reliably interpret errors, discover instructions, or find structured context to build against; versioning and changelog visibility leave partners flying blind when the API evolves; and foundational security hygiene and onboarding friction slow the path to a first successful integration. Closing the agent-understanding gaps first will unlock self-serve adoption by both human developers and the AI coding tools they rely on, while publishing a changelog and hardening security hygiene will protect the partner relationships already in flight.