EVI v2 · Updated 2026-04-29

The open methodology behind every Trustmark.

EVI v2 is the open methodology Elephant Accountability uses to score B2B websites on agent-readiness. Six axes, 100 points, Bronze / Silver / Gold thresholds. Open-spec on GitHub under CC-BY-4.0.

Why this exists

The agent-protocol stack — A2A, MCP, ANP, OASF — gives agents a way to talk to each other. None of them score whether a business is reachable at the front door at all. EVI fills that gap. We publish the methodology open because trust auditors live or die on transparency: buyers and Trustmark recipients should see exactly what we score, how we weight it, and what triggers each tier. Opaque scoring makes us a vendor; published methodology makes us the auditor.

The six axes

Agents do four things in sequence — find a business, understand what it offers, act through its APIs, transact when commerce is involved — supported by trust and operational freshness. Six axes map onto that arc and sum to 100 points:

AxisWeightWhat it measures
A Discoverability primitives24Can an agent find the business?
B API surface22Can an agent act against published APIs?
C Commerce / transaction18Can an agent buy from you?
D Identity / trust14Can an agent verify what's published?
E Schema / semantic markup14Can an agent understand what's offered?
F Operational signals8Are the surfaces above kept current?
Plus a bonus pool of up to 5 points for forward-leaning signals (e.g. OASF skill-id taxonomy adoption). Bonus is additive on top of 100.

Surfaces scored

Twenty-seven detectable surfaces. Each row gives the canonical detection rule. Full per-rule detail lives in the open-spec repo.

SurfacePath / detectionSpecPts
Axis A — Discoverability primitives (24 pts)
A2A Agent Card/.well-known/agent-card.json (legacy /.well-known/agent.json)A2A9
llms.txt/llms.txtllms.txt6
robots.txt AI directives + Cloudflare Content-Signals/robots.txtCloudflare4
Sitemap freshness/sitemap.xml + <lastmod> < 90dsitemaps.org3
Anthropic Agent Skills index/.well-known/agent-skills/index.jsonSkills2
Axis B — API surface (22 pts)
OpenAPI / Swagger/openapi.json, /swagger.json, /v3/api-docsOpenAPI 3.18
MCP Server Card + registry/.well-known/mcp/server-card.jsonMCP7
OAuth / OIDC metadata/.well-known/oauth-authorization-serverRFC 84144
RFC 9727 api-catalog/.well-known/api-catalogRFC 97272
AsyncAPI / GraphQL / ODataAny one detected (bonus)AsyncAPI1
Axis C — Commerce / transaction (18 pts)
schema.org BuyAction + OfferCatalog + EntryPointJSON-LD parse with all three; EntryPoint.urlTemplateschema.org6
ACP conformance OR EUC manifestPartner registry presence OR /.well-known/euc.jsonACP5
schema.org Product + Offer + numeric priceJSON-LD Offer with price + priceCurrencyschema.org4
x402 / pay-per-call signalPaid endpoint returns 402 + crawler-price headerx4022
AP2 mandate types referencedIntent / Cart / Payment Mandate in MCP / A2A skillsAP21
Axis D — Identity / trust (14 pts)
W3C DID document/.well-known/did.json (did:web / did:wba)W3C DID5
security.txt/.well-known/security.txt with Expires: in futureRFC 91163
Web Bot Auth / Cloudflare Verified-Bot/.well-known/http-message-signatures-directoryWeb Bot Auth3
Verifiable Credentials issuerDID service array typed as VC issuerW3C VC2
ERC-8004 on-chain registrationIdentity Registry query by domainERC-80041
Axis E — Schema / semantic markup (14 pts)
schema.org OrganizationJSON-LD with name + url + sameAs ≥ 2schema.org4
Schema breadth1 type → 1pt; 3 → 2; 5+ → 3; 8+ → 4schema.org4
schema.org Service / WebAPIJSON-LD typed entries presentschema.org3
Microformats / RDFa / hreflang / canonicalCluster checkmicroformats2
OpenGraph + Twitter CardBoth og:title and twitter:card presentOG1
Axis F — Operational signals (8 pts)
RSS / Atom feedValid feed + <updated> < 60dRFC 42872
Status pagestatus.<domain> OR /api/v2/status.json2
Sitemap freshness cadenceRe-scored from <lastmod> velocity2
apple-app-site-association + assetlinks.jsonBoth present (apps only)Apple1
humans.txt + PWA manifest + favicon≥ 2 of 3humans.txt1

Trustmark thresholds

Tiers gate on score floors plus per-axis minimums plus required surfaces. Tiers are additive — Gold implies Silver implies Bronze. A failed gate returns the highest tier the site qualifies for plus the reasons a higher tier was not awarded — that list is the upgrade roadmap.

≥ 50

Bronze

  • Axis A ≥ 12 / 24
  • security.txt present
≥ 70

Silver

  • Axis A ≥ 16 / 24
  • Axis B ≥ 12 / 22
  • No AI-bot blanket-block
  • Schema.org Organization complete
≥ 85

Gold

  • Axis A ≥ 20 / 24
  • Axis B ≥ 16 / 22
  • Axis D ≥ 8 / 14
  • ≥ 1 of: ACP, EUC, BuyAction + OfferCatalog

Auto-fail conditions

Two conditions block tier issuance regardless of score. The audit still produces a raw_score for diagnostic visibility; the published evi_score is zeroed.

1. robots.txt blanket-blocks all AI bots. A User-agent: * block with Disallow: / and no offsetting allow is treated as an explicit "agents not welcome" signal. Targeted blocking (e.g. Disallow: /private) is fine; blanket-blocking is not.
2. Cloaking detected. A homepage that serves materially different content to AI-bot User-Agents than to anonymous fetches (body-size delta > 50%) is auto-failed. Cloaking is the inverse of transparency.

What we don't score (and why)

A methodology is more credible for what it excludes than for what it includes. Surfaces evaluated and not scored in v2:

  • AITP — pre-v1.0; near-zero adoption outside NEAR.
  • OASF on-domain — lives in OCI registries / AGNTCY Directory, not at the brand domain. No .well-known/oasf.json convention exists.
  • WebMCP — W3C draft, Chrome 146 Canary in early 2026. Not yet stable cross-browser.
  • W3C Web of Things Thing Description — IoT-specific; not applicable to B2B SaaS.
  • WebFinger / host-meta — federation signals; irrelevant unless the site is identity- or social-platform-shaped.

Full exclusion list with rationale: see the spec repo.

Versioning

EVI is versioned. v1 is deprecated; v2 is current. Audits issued before 2026-04-29 used v1. Old scores remain valid as EVI-v1; new scores ship as EVI-v2. The audit engine carries both for one release before v1 is removed. Reports stay scored on the methodology version they were issued under — we do not retroactively rewrite scores.

ISO 42001 alignment

Disclaimer. This crosswalk does not claim ISO/IEC 42001 certification. ISO 42001 certification is issued only by accredited certification bodies. Trustmark is an independent agent-readiness audit and is not a substitute for formal ISO 42001 certification.

That said — the EVI surfaces produce artifacts that map onto specific ISO 42001 Annex A controls. Strongest mappings:

EVI surface / axisISO 42001 controlStrength
Axis A — Discoverability (full axis)A.6.2 Transparency to interested partiesstrong
robots.txt AI-bot directivesA.10 Third-party AI relationshipsstrong
Cloudflare Content-SignalsA.10 Third-party AI relationshipsstrong
Cloaking detection (auto-fail)A.6.2 Transparencystrong
llms.txt + Agent CardA.4.6 Documentation of the AI systemmedium
Axis B — API surfaceA.7 Resources for AI systemsmedium
DID documentA.6.1 Roles and responsibilitiesmedium
security.txtA.7.4 Accountability + A.9medium

Read the full crosswalk → (14 mappings, sources, self-positioning paragraph)

Open methodology

The full spec lives at github.com/Chris-Eaccountability/Chris-Eaccountability-orchestrator-marketing under CC-BY-4.0. Use it, fork it, build a competing scorer, cite it in research. Attribution back to the methodology repo is required.

Surface proposals and weight revisions go through GitHub issues — see CONTRIBUTING.md. New surfaces ship as minor-version bumps; weight changes ship as major-version bumps.

For per-audit cohort details (e.g. the F100 baseline run) see our transparency page. For the production scorer that implements this methodology see the free scan.