# Web4Strategy developer resources

Web4Strategy provides a public, read-only REST API 1, an OpenAPI specification, structured errors, and a publish-ready CLI package.

## Start here

- Human and agent documentation: https://web4strategy.com/docs
- Public API index: https://web4strategy.com/api
- OpenAPI 3.1 specification: https://web4strategy.com/openapi.json
- API versioning and deprecation policy: https://web4strategy.com/api/versioning.md
- Agent guidance: https://web4strategy.com/llms.txt
- Capabilities: https://web4strategy.com/api/agent/capabilities
- CLI package source and publishing instructions: https://web4strategy.com/cli

## Authentication

The documented GET endpoints are public, read-only, and do not require an API key or account. There is no public write API or external-system sandbox. Ask a person before any authenticated or mutating workflow.

## REST API

The canonical endpoints are under /api/. They use API version 1 by default. Clients may send X-Web4Strategy-API-Version: 1; unsupported versions receive a typed UNSUPPORTED_API_VERSION response. Every endpoint documents JSON response schemas and typed 4xx/5xx error responses in the OpenAPI document.

Responses include the IETF-style RateLimit-Limit, RateLimit-Remaining, RateLimit-Reset, and RateLimit-Policy headers. A 429 response also includes Retry-After. Legacy X-RateLimit-* headers remain during the migration period.

## CLI

The repository contains a dependency-light npm package named @web4strategy/cli in the /cli directory. It is prepared for publication and provides commands for capabilities, skills, prompts, PRDs, bots, directory listings, and page metadata. Publishing it to npm requires the project owner’s npm account and release approval.