WDS API Server
The WDS API Server provides the public REST and MCP surfaces for configuring jobs, downloading and processing web resources, running Traversals, and retrieving indexed content.
Capabilities
- Store job configurations, start jobs, fetch pages, and inspect job state.
- Crawl links, scrape structured values, read downloaded content in chunks, and inspect task status.
- Define, run, inspect, and schedule Traversals.
- Index and retrieve content with full-text or vector search.
- Expose the same workflows to AI clients through the MCP server.
Services
The current server consists of eight .Web projects: Dapi, Crawler, Datakeeper, Scraper, Idealer, Retriever, Jober, and Solidstack. Solidstack runs the gateway and backend capabilities in one process; the other projects form the independently deployable multi-service topology. See Services for responsibilities, dependencies, ports, and configuration.
Deployment options
- Docker runs Solidstack as a single container for evaluation and small workloads.
- Docker Compose provides current MINI and OEM Business topologies; the bundled-infrastructure BOX examples are pending their required support files and release image values.
- Helm deploys either the single-service or multi-service topology to Kubernetes.
- Air-gapped deployment covers private registries and offline environments.
Entry points
- REST API:
/api/v3; see API. - Swagger UI and OpenAPI:
/api/swaggerand/api/swagger/swagger.json. - MCP Streamable HTTP endpoint:
/mcp; see MCP. - Health probes:
/healthand/ready. - Auxiliary Playground and local Docs endpoints depend on the selected deployment topology.
Next steps
- Choose a deployment method.
- Follow the API Quickstart.
- Review the service architecture.