markline.dev valid
Markline
Open-source, self-hostable documentation framework with first-class OpenAPI, an interactive API playground, instant search, and AI on your own key (BYOK).
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-27T09:56:17.210Z. Cached copy · Source on markline.dev
# Markline
> Open-source, self-hostable documentation framework with first-class OpenAPI, an interactive API playground, instant search, and AI on your own key (BYOK).
This index lists the documentation. The full text of every page concatenated into one file is available at [llms-full.txt](https://markline.dev/llms-full.txt).
## Documentation · Getting started
- [Quickstart](https://markline.dev/quickstart): Create and run a documentation site in under a minute.
- [CLI](https://markline.dev/cli): The markline command runs your docs project from its own markline.json and content.
## Documentation · Authoring
- [Configuration](https://markline.dev/configuration): markline.json is the single source of truth for navigation, theming, and behavior.
- [Theming](https://markline.dev/theming): Brand your docs entirely from markline.json — logo, favicon, fonts, colors, and the full palette. No code to fork.
- [Components](https://markline.dev/components): Rich components available in any MDX page — no import required.
- [API reference](https://markline.dev/openapi): Point Markline at an OpenAPI document and it generates a polished three-pane reference — resource pages, multi-language code, and a live request explorer.
- [Search](https://markline.dev/search): Full-text search across your docs and API reference — built into the static output, no service required.
## Documentation · Ship
- [Deployment](https://markline.dev/deployment): Ship your docs as static HTML or a Node server — markline init scaffolds the configs.
- [Versions & i18n](https://markline.dev/versions): Ship multiple documentation versions or languages from one project — same URL-prefix mechanism, a switcher in the header, fully static.
- [Ask AI (BYOK)](https://markline.dev/ai): An opt-in AI assistant for your docs and API reference — running on your own LLM key, never ours.
- [Feedback](https://markline.dev/feedback): "Was this helpful?" widgets on every docs page and API resource — opt-in, sink-agnostic, with a drop-in Cloudflare Worker for static hosting.
## Documentation · Compare
- [vs Mintlify](https://markline.dev/mintlify-alternative): A modern docs experience without the SaaS — MIT-licensed, self-hostable, and yours to own.
- [vs Scalar](https://markline.dev/scalar-alternative): More than an API reference — a full open-source docs framework that includes one.
## Guides · Overview
- [Framework guides](https://markline.dev/guides): Point Markline at the OpenAPI document your backend already emits — then use four small extensions to shape the reference without touching your routes.
## Guides · Node & TypeScript
- [NestJS](https://markline.dev/guides/nestjs): Emit your OpenAPI document from @nestjs/swagger, snapshot it into your docs, and shape the reference with decorators that survive regeneration.
- [Hono + Zod OpenAPI](https://markline.dev/guides/hono-zod-openapi): Define routes and schemas once with @hono/zod-openapi, write the document to disk, and drop Markline's e
…
Related sites
Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.
| Domain | Title | Category | Country | Authority | llms.txt | llms-full.txt | Save |
|---|---|---|---|---|---|---|---|
| jamdesk.com | Jamdesk | documentation Developer tools Documentation and reference | US | 50 | ✓ | ✓ | |
| mintlify.com | Mintlify | interface AI and machine learning Developer tools +1 | US | 67 | ✓ | ✓ | |
| documentation.ai | Documentation.AI | transactional AI and machine learning Documentation and reference +1 | — | 52 | ✓ | ||
| docus.dev | Docus | interface Documentation and reference Developer tools | US | 50 | ✓ | ✓ | |
| trillet.ai | Trillet AI | documentation AI and machine learning | US | 48 | ✓ | ✓ | |
| linkup.so | Linkup | interface AI agents and MCP APIs and SDKs +1 | US | 50 | ✓ | ||
| docula.org | Docula | documentation Documentation and reference Developer tools | — | 50 | ✓ | ✓ | |
| readme.com | ReadMe | documentation AI and machine learning Developer tools +1 | US | 60 | ✓ |
Machine-readable: GET /v1/resolve?q=markline.dev · GET /v1/domain/markline.dev · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Own or manage this website?
If you own or manage markline.dev, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- See your website in the map
Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for markline.dev:
1. POST https://agentwebmap.com/v1/sites/markline.dev/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://markline.dev/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/markline.dev/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/markline.dev).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.