# Avalara — API Agent Score

> Score: 76/100 (Grade: B) | Domain: avalara.com | Rubric: 1.0.0 | Checked: August 6, 2026

Avalara scored 76/100 (B), classified "partially-ready".

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

## Summary

- Overall: 76/100 (B)
- Classification: partially-ready

## Category Scores

- API Design: 75/100 (B)
- Developer Experience: 79/100 (B)
- Agent Discovery: 77/100 (B)
- Agent Understanding: 63/100 (C)
- Agent Usability: 87/100 (A)

## Check Results

### API Design

- [warn] Schema coverage & depth — 487/491 (99%) public params are fully typed (no any/**kwargs). Analyzer reports not all methods have a derivable input schema. Investigated: sdk 100%.
- [pass] Example coverage — Code samples present on 2/17 pages across 2 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] Self-service developer portal — Signup page at https://www.avalara.com/us/en/get-started.html (CSR-rendered — body classifier inconclusive); free tier / sandbox documented in pricing/docs. Investigated: docs 100%.
- [pass] Code samples in docs — Code samples present on 2/17 pages across 2 language(s); broader multi-language coverage missing. Investigated: docs 100%.
- [pass] Description completeness — 68/68 operations carry a description. Investigated: sdk 100%.
- [pass] Changelog published — Newest official SDK activity 9 day(s) ago. Investigated: sdk 100%.
- [fail] Quickstart present — No quickstart/getting-started page found at the conventional paths. Investigated: docs 0%.

### Agent Discovery

- [pass] Registry & SDK presence — Indexed on Context7 (avadev/avalara-sdk-java, 1584 snippets). Investigated: docs 100%, sdk 100%, mcp 100%, cli 0%, wellknown 0%.
- [warn] llms.txt present, valid & comprehensive — No llms.txt directive found in HTML of any of 41 sampled pages; 9 failed to fetch. Investigated: docs 56%, sdk 0%.
- [warn] Docs reachable, not hard auth-gated — 1 of 50 sampled pages return 200 for non-existent URLs (soft 404). Investigated: docs 50%.
- [pass] Crawlable / AEO — Docs paths crawlable by all monitored AI agents. Investigated: wellknown 100%.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — Single base error "AvaTaxError" with 2 subclasses. Investigated: sdk 100%.
- [warn] Agent-navigable, token-efficient docs — 3 of 50 sampled pages appear to be client-side rendered SPA shells (__next detected); agents using HTTP fetches will see no content; 11 more have page structure but little substantive content. Investigated: docs 35%.
- [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 assessed pages (1 JS-rendered). Investigated: docs 0%.
- [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] Idempotency documented — Built-in retry machinery is present (grep-derived). Investigated: sdk 100%.
- [pass] Sandbox separation — Sandbox environments are exposed (sandbox). Investigated: sdk 100%.
- [warn] Pagination documented & consistent — 8/9 list method(s) return an auto-paginating iterable. Investigated: sdk 89%.
- [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.

## Executive Summary

Avalara's API program shows genuine strength in operational reliability and schema quality — a solid foundation for partner integrations. However, the program has two critical gaps that will slow partner adoption and block AI-agent workflows: docs and contracts lack the machine-readable structure that agents require to discover and act on APIs autonomously, and the absence of a runnable collection with test scripts means partners and their agents have no executable truth to build against confidently. Closing these gaps — agent-readable docs first, then a verified runnable collection — will unlock self-serve partner onboarding and make Avalara's APIs a first-class target for AI-assisted development.