Integrations

Machine-readable docs

fp2 keeps stable machine endpoints on the existing Worker while Fern adds page-level Markdown and discovery on the documentation domain.

Canonical Worker endpoints

URLPurpose
https://new.fp.dev/start.mdExact deployed CLI runbook
https://new.fp.dev/llms.txtCompact operational documentation index
https://new.fp.dev/api/v1/docsExisting Scalar-generated API reference
https://new.fp.dev/api/v1/healthzAPI reachability probe
https://new.fp.dev/install.shSigned standalone CLI installer

These routes stay on new.fp.dev and are not redirected through Fern.

Fern agent surfaces

Fern provides:

  • https://docs.new.fp.dev/llms.txt as an index of the explanatory docs and generated API reference;
  • clean Markdown for any page by appending .md;
  • content negotiation with Accept: text/markdown;
  • the generated OpenAPI document in its API discovery output;
  • the fp2 skill under /.well-known/agent-skills/.

For example:

curl https://docs.new.fp.dev/quickstart.md
curl https://docs.new.fp.dev/llms.txt

new.fp.dev/llms.txt is the compact operational entry point. docs.new.fp.dev/llms.txt is the broader documentation-site index. Agents should use the former when they need the shortest executable path.

Source ownership

The generated Fern OpenAPI input comes from packages/contract. The hosted skill comes from .agents/skills/fp2/SKILL.md. Both are regenerated before every validation, preview, and publish, and bun run check refuses a contract operation that has no documented summary.