Add SAVER Verifier

[SAVER-Ronny]

Adds SAVER Verifier as an agent-enabling verification service with first-party evidence, plus a reusable Agent Verification & Trust category because the existing taxonomy does not cover evidence-backed factual verification for autonomous agents.

[foo-bender]

Outcome: changes-requested

Policy assessment

@SAVER-Ronny The complete initial PR diff supports an agent-enabling hosted factual-verification API: agents submit claims and obtain structured status, confidence, explanation and cited web evidence as an input to decisions. REST/x402, 0.20 USDC per verification on Base Mainnet, and documentation-reviewed provenance are supported. The website identifies the submitted service, required frontmatter/evidence structure passes, and the proposed reusable Agent Verification & Trust category fits the documented workflow and passes schema validation. No commit-attribution restriction was applied to this first submission.

Please address these material findings together:

• Repository field: githubUrl points to https://github.com/SAVER-SI/saver-verifier, a documentation/integration repository, not the service implementation. Its API documentation explicitly says the production implementation is maintained separately; the public tree contains docs, examples, schemas and skill integration. Remove githubUrl and retain this valid documentation URL as docsUrl/evidence, or supply a genuine first-party implementation repository. No licence is specified; do not imply the hosted service is open source.
• Decision boundary: expand limitationsMd to include documented mixed and insufficient_evidence outcomes, and explain that confidence/citations must be evaluated rather than treating verification as definitive permission to act or pay. The official README explicitly excludes wallet-policy enforcement, transaction simulation, token-contract security analysis and sanctions screening. Reflect that boundary in suitability/body wording about gating consequential actions.

Evidence checked

Both exact submitted evidence URLs returned HTTP 200 without redirect substitution and support their stated documentation/discovery claims:

• https://github.com/SAVER-SI/saver-verifier — documents /verify, x402 authorize-and-retry, price and structured cited-evidence responses; it does not substantiate the separate implementation meaning of githubUrl.
• https://api.saververify.com/.well-known/x402 — JSON publishes paid POST /verify, 0.20 USDC, eip155:8453 (Base Mainnet) and payment metadata.

The independent contradiction pass covered the official website, live OpenAPI and discovery, full repository tree and README/API/skill/client/example documentation, releases/tags/package/licence availability and official linked skill/discovery surfaces. Price and response contracts agree. Discovery's version: 1 belongs to its discovery schema; the API/skill payment contract advertises x402 v2, which the listing does not pin. An unpaid POST returned the documented 402 challenge; no payment, wallet authorization or successful verification was exercised, and accuracy/latency remain unbenchmarked.

Checks run

Exact head b7701b5 was merged without committing into current main 21adcb7 in an isolated clone. npm run validate:content passed (59 tools, 17 categories); npm test passed 90/90; git diff --check passed, using Node 26.7.0 and Bash 5.3.20. GitHub enrichment is successful; the current check rollup has no completed content-validation check. No SEO evaluation, reviewer commit, workflow approval, PR approval or merge was applied.

[SAVER-Ronny]

Requested changes have been addressed in the latest commits: the public repository is now referenced as documentation only, and the decision-boundary/limitations language has been expanded. The PR is ready for re-review when convenient.