Docs Discover
Discover machine-readable integration documentation from a public developer/docs page: llms.txt, Markdown alternates, API/auth docs, OpenAPI or Swagger specifications, and MCP candidates. Candidates are returned only after bounded verification. Maximum 10 HTTP requests; no JavaScript, recursive crawl or authenticated content.
Forest exposes this capability as a deterministic machine-readable API for software agents. Discovery is free; execution uses the canonical paid endpoint below. The live x402 challenge is the source of truth for payment terms.
Typical agent tasks
This capability is intended for bounded machine decisions such as:
- find machine-readable integration endpoints or specifications from developer documentation
- discover OpenAPI Swagger MCP or llms.txt resources linked from docs
- locate public API and authentication documentation suitable for machine use
- inspect a developer docs page for verified integration artifacts
What Forest guarantees
- SSRF-safe bounded discovery
- verified candidates only
Boundaries
- JavaScript-rendered docs
- recursive crawling
- authenticated documentation
Machine contract
The request and response schemas are published in the canonical OpenAPI document. This page shows a representative input from the same production manifest.
Input example
Canonical paid endpoint
Related capabilities
- Api Readiness — Compose bounded API discovery with one deterministic OpenAPI or Swagger preflight into a concise agent-readiness state. The check does not authenticate, call discovered API operations, or prove business-level API correctness.
- Api Discover — Discover the callable public API behind a developer or documentation page: identify candidate API base URLs, developer portals, machine-readable API docs and authentication documentation for integration setup.
- Mcp Discover — Find public MCP server candidates and registry metadata.
- Openapi Breaking-change — Compare two public OpenAPI or Swagger contracts and determine whether the API update contains directly observable breaking compatibility changes. Detects removed operations, newly required request inputs, narrowed inline enums, removed content types or successful responses and tightened authentication; unsupported compatibility questions remain unknown. No API operation is executed.
- Openapi Operation-contract — Inspect the declared request and response contract for one exact OpenAPI or Swagger operation before integration. Returns parameters, request-body content types, response statuses/content types and declared security scheme names without executing the endpoint or resolving external references.
- Openapi Operation-resolve — Look up one exact HTTP method and path in a public OpenAPI or Swagger contract and report whether that documented API endpoint exists. This is a contract/endpoint existence check only; Forest reads the specification and never invokes the API operation.