SDKs and CLI

ia.sdk-cli · 4.28

Act SHOULD Recommendation AR-ACT-06 AgentReady requirement

Why it matters

SDK links and CLI installation examples help agents find an interface. An SDK reference does not prove a CLI, and source hints do not verify installation or task execution.

How to fix it

Publish an SDK and a CLI, with separate installation and first-call examples.

Publish an SDK in a package registry and label its registry link as an SDK in your docs.
Document the CLI separately, including its installation command and a first-call example.

Link both the SDK and CLI documentation from llms.txt.

## Tools
- [SDK](https://www.npmjs.com/package/@example/sdk): SDK package and usage examples
- [CLI](https://example.com/docs/cli): `npm install -g @example/cli`, then `example --help`

Verify

curl -sf https://{domain}/llms.txt

Expected: Follow both documentation links. Check that the SDK has a labeled registry link and the CLI has its own installation command. This does not verify installation or task execution.

Run a new scan for this checkpoint:

isagentready results {domain} --checkpoint ia.sdk-cli

Details Mapping, lifecycle and references

AR mapping: Direct relation
Evidence source: agentready.org AR-ACT-06
Score role: Bonus
Introduced: 2026-10-22
Revised: 2026-10-30
Methodology version: 2026-10-30

agentready.org AR-ACT-06

Checkpoint data (JSON)