# Slt — API Agent Score

> Score: 52/100 (Grade: D) | Domain: slt.lk | Rubric: 1.0.0 | Checked: August 5, 2026

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

[View full report](https://www.postman.com/ai/ai-ready-apis/company/slt)
[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: 45/100 (F)
- Developer Experience: 66/100 (C)
- Agent Discovery: 53/100 (D)
- Agent Understanding: 57/100 (D)
- Agent Usability: 45/100 (F)

## Check Results

### API Design

- [pass] Example coverage — README is present and includes a runnable quickstart. Investigated: sdk 100%, docs 0%.
- [fail] Schema coverage & depth — no py.typed marker (PEP 561). Investigated: sdk 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 — Self-service signup at https://developer.mobitel.lk/mobitelint/mapis/user/register; no free tier or sandbox language detected. Investigated: docs 100%.
- [warn] Quickstart present — Quickstart page reachable (12 variants scanned starting at https://developer.mobitel.lk/mobitelint/mapis/search/content?keys=quickstart) but no runnable code sample detected in HTML or .md variant. Investigated: docs 50%.
- [fail] Code samples in docs — No detectable code samples across 1 sampled docs pages. 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

- [warn] Docs reachable, not hard auth-gated — Server ignores Accept: text/markdown header (0/1 pages return markdown). Investigated: docs 75%.
- [warn] Registry & SDK presence — No MCP server, tool manifest, or list-tools capability is discoverable (server entrypoint: absent, tool manifest: unknown, list-tools: unknown). Investigated: sdk 25%, docs 0%, cli 0%.
- [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://developer.mobitel.lk/mobitelint/mapis/llms.txt, https://developer.mobitel.lk/llms.txt, https://developer.mobitel.lk/docs/llms.txt); 2 failed to fetch. Investigated: docs 0%, sdk 0%.

### Agent Understanding

- [warn] Agent-navigable, token-efficient docs — No pages support .md URLs (0/1 tested). Investigated: docs 79%.
- [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] 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

- [warn] Sandbox separation — No test-mode flag or sandbox environment is exposed. Investigated: sdk 50%.
- [fail] Idempotency documented — No built-in retry machinery was found; transient failures are not retried. Investigated: sdk 0%.
- [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

SLT's API program shows promise in developer experience basics but has critical gaps in two areas that directly block partner and agent adoption: API design completeness and agent readiness. Schema coverage is missing and security hygiene is incomplete, meaning partners and their AI agents cannot build reliable integrations against an underspecified contract. Simultaneously, the absence of machine-readable discovery artifacts, agent instruction files, runnable collections, and idempotency documentation means agents cannot find, understand, or safely execute SLT's APIs without manual intervention. Prioritize hardening the API contract and then layering agent-ready documentation and executable resources on top.