docs.dev vs TokenPath

Point your coding agent at your repo and your docs; it opens a docs branch, your team reviews on the rendered page, publishing is a commit. Runs on your Cloudflare, no...

One API to ground every generated token in its source, for output from any model. TokenPath measures attention directly, not the LLM's self-report, to return...

About docs.dev

Point your coding agent at your repo and your docs; it opens a docs branch, your team reviews on the rendered page, publishing is a commit. Runs on your Cloudflare, no platform fee, no metered AI. Reviews, branches, and rollbacks come free, because it is just git. Your content in their database, and an export button you hope works when you leave. Writing AI is the agent you already have; reader-facing AI runs on your Workers AI.

About TokenPath

One API to ground every generated token in its source, for output from any model. TokenPath measures attention directly, not the LLM's self-report, to return machine-readable, token-level citations your product can act on. You get back a list of attributions: each attribution is an answer span, the corresponding document span, and how confident the match is, enough to highlight it, cite it, or log it in a few lines. For the advanced raw token-by-token map, use /v1/attributions/heatmap .