evidence.dev valid
Evidence Docs
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-27T09:51:59.668Z. Cached copy · Source on evidence.dev
# Evidence Docs
- [What is Evidence?](https://docs.evidence.dev/index.md): Evidence is a powerful framework for building and publishing data products using SQL, markdown, and AI.
- [Quickstart](https://docs.evidence.dev/quickstart.md): Start building reports in under 5 minutes
- [Migration Guide](https://docs.evidence.dev/migration-guide.md): Migrate a legacy Evidence project to Evidence Studio
- [Editing](https://docs.evidence.dev/editing.md): The Evidence Editor is the core of Evidence Studio, allowing you to create and edit reports in markdown and SQL.
- [Publishing](https://docs.evidence.dev/publishing.md): Publish your reports on Evidence Studio, or self host your reports to share them with your team.
- [Markdown](https://docs.evidence.dev/core-concepts/markdown.md): Evidence pages are written in markdown, with additional syntax for adding SQL queries and charts.
- [Components](https://docs.evidence.dev/core-concepts/components.md): Components are used to create visual elements such as charts, tables and UI elements.
- [Models](https://docs.evidence.dev/core-concepts/models.md): Transform and combine your data with SQL models that run automatically in the background.
- [Metrics](https://docs.evidence.dev/core-concepts/metrics.md): Define reusable, governed metrics once and reference them by name from any data component.
- [Value Formatting](https://docs.evidence.dev/core-concepts/value-formatting.md): Format values in components.
- [Variables](https://docs.evidence.dev/core-concepts/variables.md): Create reusable values for use in markdown and SQL.
- [Partials](https://docs.evidence.dev/core-concepts/partials.md): Partials allow you to define reusable sections of content that can be included across multiple pages in your project.
- [Custom Components](https://docs.evidence.dev/core-concepts/custom-components.md): Build your own Markdoc tags from markdown files — each component declares typed attributes in frontmatter and can be called from any page like a built-in.
- [Version Control](https://docs.evidence.dev/features/version-control.md): Learn how to manage your Evidence projects using BI as code with Git.
- [Project Settings](https://docs.evidence.dev/features/project-settings.md): Configure project-wide settings and theme with version-controlled evidence.config.yaml and theme.yaml files.
- [Page Settings](https://docs.evidence.dev/features/page-settings.md): Set a page title, layout, theme, and other per-page settings using YAML frontmatter at the top of a page.
- [Themes](https://docs.evidence.dev/features/themes.md): Customize colors and layout to match your brand with version-controlled theme.yaml and page settings.
- [Layouts](https://docs.evidence.dev/features/layouts.md): The Row and Stack components help you create an interactive data visualization dashboard in Evidence markdown.
- [SQL Files](https://docs.evidence.dev/features/sql-files.md): Create reusable SQL queries as standalone files that can be referenced by components and
…
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 |
|---|---|---|---|---|---|---|---|
| sli.dev | Slidev | documentation Developer tools Documentation and reference | DE | 60 | ✓ | ✓ | |
| powerbi.tips | PowerBI.tips | documentation Data and analytics Developer tools | — | 55 | ✓ | ✓ | |
| reactbricks.com | React Bricks | documentation Developer tools | US | 52 | ✓ | ||
| vitepress.dev | VitePress | documentation Developer tools Documentation and reference | CA | 64 | ✓ | ✓ | |
| getdoks.org | Doks | documentation Developer tools Documentation and reference | DE | 52 | ✓ | ||
| visme.co | Visme | transactional Design | — | 59 | ✓ | ||
| valq.com | ValQ - Plan | documentation | — | 46 | ✓ | ✓ | |
| emdashcms.com | EmDash | documentation Developer tools Documentation and reference | — | 49 | ✓ |
Machine-readable: GET /v1/resolve?q=evidence.dev · GET /v1/domain/evidence.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 evidence.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 evidence.dev:
1. POST https://agentwebmap.com/v1/sites/evidence.dev/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://evidence.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/evidence.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/evidence.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.