docs.dev vs Marginal

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...

Track every LLM call's cost and slice it by customer, feature, model, any field you define.

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 Marginal

Track every LLM call's cost and slice it by customer, feature, model, any field you define. Marginal tracks the cost of every LLM call and slices it by the fields you care about, customer, feature, model. Cost is computed server-side, usage in, dollars out. Every API request is logged with its outcome, accepted counts, rejected events and why, stripped keys, unpriced models. The SDKs are zero-dependency, buffered, fire-and-forget: track() never throws and never blocks your request path.