# Rakuten — API Agent Score

> Score: 71/100 (Grade: B) | Domain: rakuten.co.jp | Rubric: 1.0.0 | Checked: July 30, 2026

Rakuten scored 71/100 (B), classified "partially-ready".

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

## Summary

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

## Category Scores

- API Design: 75/100 (B)
- Developer Experience: 47/100 (F)
- Agent Discovery: 65/100 (C)
- Agent Understanding: 74/100 (B)
- Agent Usability: 90/100 (A+)

## Check Results

### API Design

- [pass] Schema coverage & depth — 6/6 (100%) public params are fully typed (no any/**kwargs). Analyzer confirms all methods have a derivable input schema. Investigated: sdk 100%.
- [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] Changelog published — Newest official SDK activity 58 day(s) ago. Investigated: sdk 100%.
- [warn] Description completeness — 2/8 operations lack a description. Investigated: sdk 75%.
- [fail] Self-service developer portal — No self-service signup detected: no signup link found on the homepage or docs, and no conventional signup path (/signup, /sign-up, /register, /get-started, /console/signup, /dashboard/signup, /try, /try-free, /free, /free-trial, /start, /start-free, /join, /create-account, /account/signup, /auth/signup, /users/sign_up) resolved. Investigated: docs 0%.
- [fail] Quickstart present — No quickstart/getting-started page found at the conventional paths. Investigated: docs 0%.
- [fail] Code samples in docs — No detectable code samples across 1 sampled docs pages. Investigated: docs 0%.

### Agent Discovery

- [pass] Registry & SDK presence — Indexed on Context7 (rakuten-nlp/rakutenma, 66 snippets). Investigated: docs 100%, sdk 100%, cli 0%.
- [warn] Docs reachable, not hard auth-gated — Server ignores Accept: text/markdown header (0/1 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%.
- [fail] llms.txt present, valid & comprehensive — No llms.txt found at any candidate location (https://webservice.rakuten.co.jp/documentation/llms.txt, https://webservice.rakuten.co.jp/llms.txt, https://webservice.rakuten.co.jp/docs/llms.txt). Investigated: docs 0%, sdk 0%.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — Single base error "Error" with 6 subclasses. Investigated: sdk 100%.
- [warn] Agent-navigable, token-efficient docs — No pages support .md URLs (0/1 tested). Investigated: docs 86%.
- [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] Pagination documented & consistent — An SDK-wide auto-paginator 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.

## Executive Summary

Rakuten's API program shows genuine strength in agent usability — partners and their agents can largely run real workflows — but two areas demand urgent attention: Developer Experience is effectively non-functional for self-serve partners, with no portal, no quickstart, and no code samples to get a partner to a first call without hand-holding. Agent and AI discoverability are also weak, with no llms.txt, no structured docs metadata, and no agent instruction file, meaning both human partners and AI coding agents cannot reliably find or understand the API surface without a direct relationship. Prioritize building a self-serve onboarding foundation first, then layer in the machine-readable signals that let agents discover and act on your APIs autonomously.