# Splinks — API Agent Score

> Score: 52/100 (Grade: D) | Domain: splinks.co.jp | Rubric: 1.0.0 | Checked: August 21, 2026

Splinks scored 52/100 (D), classified "not-ai-ready".

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

## Summary

- Overall: 52/100 (D)
- Classification: not-ai-ready

## Category Scores

- API Design: 55/100 (D)
- Developer Experience: 48/100 (F)
- Agent Discovery: 78/100 (B)
- Agent Understanding: 54/100 (D)
- Agent Usability: 40/100 (F)

## Check Results

### API Design

- [pass] Example coverage — Code samples appear on 1 of 6 sampled docs pages across 2 language(s), but broader multi-language coverage is missing. Investigated: docs 100%.
- [fail] Security & governance hygiene — No security.txt found at /.well-known/security.txt or /security.txt, so there's no machine-readable security contact for agents or researchers. Investigated: wellknown 0%.
- [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] Code samples in docs — Code samples appear on 1 of 6 sampled docs pages across 2 language(s), but broader multi-language coverage is missing. Investigated: docs 100%.
- [fail] Self-service developer portal — No self-service signup detected — no signup link 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 — so an agent can't onboard on its own. Investigated: docs 0%.
- [fail] Quickstart present — No quickstart or getting-started page found at the conventional docs paths, so new developers and agents have no obvious first step. Investigated: docs 0%.
- [skip] Description completeness — No surface produced evidence for this capability in this run.
- [skip] Changelog published — No surface produced evidence for this capability in this run.

### Agent Discovery

- [pass] Registry & SDK presence — Indexed on Context7 (moj-analytical-services/splink, 11690 snippets). Investigated: docs 100%, sdk 0%, cli 0%.
- [warn] Docs reachable, not hard auth-gated — Server ignores Accept: text/markdown header (0/6 pages return markdown). Investigated: docs 75%.
- [warn] llms.txt present, valid & comprehensive — No llms.txt directive found in HTML of any of 6 pages. Investigated: docs 57%.
- [warn] Crawlable / AEO — No sitemap found via robots.txt or /sitemap.xml on the docs host, so AI search engines have no crawl map for your docs. Investigated: wellknown 50%.

### Agent Understanding

- [warn] Agent-navigable, token-efficient docs — No pages support .md URLs (0/6 tested). Investigated: docs 69%.
- [fail] Agent instructions file (AGENTS.md) — No AGENTS.md at the site root or /.well-known/, so coding agents have no ready-made setup and usage instructions. Investigated: wellknown 0%.
- [fail] Docs structured data — No JSON-LD or OpenGraph/meta tags found across 3 assessed pages (3 JS-rendered), so answer engines have nothing to cite. 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 0 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 found for the org, so there's no runnable collection an agent can execute against. 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

Splinks has a solid foundation in agent discovery and crawlability, but the partner program faces two critical gaps that will stall adoption: there is no self-service onboarding path for new developers, and AI agents cannot parse, execute against, or trust any of the documentation surfaces. The highest-priority work is establishing a runnable, self-serve developer experience — quickstart content, a signup path, and executable collections — followed immediately by embedding the machine-readable signals (structured data, AGENTS.md, security.txt) that let AI agents find and act on the API without human intervention.