# Braintree — API Agent Score

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

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

[View full report](https://www.postman.com/ai/ai-ready-apis/company/braintreepayments)
[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: 72/100 (B)
- Agent Discovery: 83/100 (A)
- Agent Understanding: 60/100 (C)
- Agent Usability: 40/100 (F)

## Check Results

### API Design

- [pass] Example coverage — Code samples in 3 language(s) across docs (top: ruby, shell, javascript); 1/18 pages have ≥ 2 languages on the same page. Investigated: docs 100%.
- [warn] Security & governance hygiene — security.txt present but missing Contact; missing or expired Expires. Investigated: wellknown 50%.
- [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] Quickstart present — Quickstart at https://developer.paypal.com/api/rest/ has a runnable sample in the .md variant (https://developer.paypal.com/api/rest.md). Investigated: docs 100%.
- [pass] Code samples in docs — Code samples in 3 language(s) across docs (top: ruby, shell, javascript); 1/18 pages have ≥ 2 languages on the same page. Investigated: docs 100%.
- [pass] Changelog published — Newest official SDK activity 0 day(s) ago. Investigated: sdk 100%.
- [fail] Self-service developer portal — Signup page is sales-gated (contact-sales/request-access language detected). Investigated: docs 0%.
- [skip] Description completeness — No surface produced evidence for this capability in this run.

### Agent Discovery

- [pass] Registry & SDK presence — Discovered SDKs in 6 distinct languages. Investigated: sdk 100%, docs 0%, cli 0%.
- [warn] Docs reachable, not hard auth-gated — Server ignores Accept: text/markdown header (0/1 pages return markdown). Investigated: docs 75%.
- [warn] llms.txt present, valid & comprehensive — No llms.txt directive found in HTML of any of 1 pages. Investigated: docs 67%.
- [warn] Crawlable / AEO — Sitemap present (3657 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 88%.
- [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 2 assessed pages (2 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

- [fail] Runnable collection with test scripts — No public Postman workspace discovered for the org. 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

Braintreepayments has a strong foundation in API discovery and crawlability, with agents and partners able to find your APIs reliably. However, two areas demand immediate attention: your docs and API surface lack the machine-readable context that AI agents need to integrate without guessing, and partners have no runnable, test-backed collection to validate real workflows against. Closing these gaps will shorten partner integration cycles, reduce support burden, and make your API program competitive for the next generation of AI-driven partners.