verifiable.pro valid
verifiable.pro
verifiable.pro reports in English and Simplified Chinese on verifiable AI: evidence that lets someone other than an AI provider check the provider's claims, such as which model answered a request or which software handled it. Coverage starts from trusted execution environments (TEEs), remote attestation and confidential computing. It compares them with other ways to check a claim: zkML, verifiable inference and formal verification check computations and code, while AI evaluations, audits, model
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-25T08:14:22.270Z. Cached copy · Source on verifiable.pro
# verifiable.pro
> verifiable.pro reports in English and Simplified Chinese on verifiable AI: evidence that lets someone other than an AI provider check the provider's claims, such as which model answered a request or which software handled it. Coverage starts from trusted execution environments (TEEs), remote attestation and confidential computing. It compares them with other ways to check a claim: zkML, verifiable inference and formal verification check computations and code, while AI evaluations, audits, model signing and supply-chain provenance check models and their origins. The comparison also extends to content credentials (C2PA) and watermarking, agent accountability and the verification of AI governance commitments. The site publishes news briefs, analysis, explainers and guides, a resource library and a glossary.
Besides the articles, the site keeps a hub on trusted execution environments (TEEs) and a map of the verification stack: seven layers from Hardware & compute (T1) to Policy (T7), with five trust tiers. Every piece says what a check establishes and what it still leaves to trust, and the site never calls a service verified.
Each factual claim in an article traces to a numbered source listed with it; in the Markdown, [^n] cites source n. Every news brief ends with a "What we checked" box that names the primary sources opened, the day they were opened and what could not be confirmed, and the site's interpretation sits apart in a "Why it matters" box. A vendor's security claim is reported as the vendor's claim. Corrections are listed with their dates at the end of the article they correct. Each article's byline gives the name of the person who wrote it or, for an article that software drafted with AI models, one of the site's automated bylines (verifiable.pro Wire or verifiable.pro Research), marked as automated. AI tools also translate, and an editor decides what is published and checks each claim against its source before publication.
Every article and page has a Markdown source beside it: `/articles/<slug>/en.md` and `zh.md` for the article at `/articles/<slug>/` and `/zh/articles/<slug>/`, and `/pages/<name>.en.md` or `.zh.md` for the page at `/<name>/` and `/zh/<name>/`. The site manifest lists the SHA-256 digest of every source and data file; its `digest` field is the SHA-256 of the manifest without its `digest` and `digest_note` fields, serialized with sorted keys, no whitespace and UTF-8. To check a page, download its source, compute its SHA-256 and compare it with the source's entry in the manifest; `tools/verify_manifest.py` in the source repository checks every entry. A match shows that the text is what the site recorded when it was built, not that the reporting is correct. To cite a page, give its title, its address (not the address of its Markdown source), verifiable.pro and its filing or update date.
An article with a lead image also has `/articles/<slug>/illustration.json` beside its sources, with the picture's a
…
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 |
|---|---|---|---|---|---|---|---|
| truebit.io | Truebit - Don’t just trust, verify | documentation Marketing Crypto and Web3 +1 | — | 46 | ✓ | ||
| confident-ai.com | Confident AI | documentation AI and machine learning DevOps and observability +1 | US | 61 | ✓ | ✓ | |
| sigma.ai | Sigma AI | documentation AI and machine learning | PL | 51 | ✓ | ||
| auraone.ai | AuraOne | documentation AI and machine learning Business software | US | 53 | ✓ | ✓ | |
| trstd.com | #trstd | documentation Cybersecurity Authentication and identity | DE | 59 | ✓ | ||
| swept.ai | Swept AI | documentation AI and machine learning Cybersecurity | US | 50 | ✓ | ✓ | |
| tinfoil.sh | Tinfoil - Verifiably Private AI | interface Developer tools AI and machine learning +1 | US | 51 | ✓ | ||
| near.ai | NEAR AI | interface AI and machine learning APIs and SDKs | US | 55 | ✓ |
Machine-readable: GET /v1/resolve?q=verifiable.pro · GET /v1/domain/verifiable.pro · 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 verifiable.pro, 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 verifiable.pro:
1. POST https://agentwebmap.com/v1/sites/verifiable.pro/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://verifiable.pro/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/verifiable.pro/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/verifiable.pro).
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.