ECO-10060 bronze

eco-10060.org

“Master root of the GSC protocol tree: Electronic Compliance Objects under Standard-10060. An Electronic Compliance Object (ECO) is a deterministic, machine-readable digital representation of a physical object that contains the verified information required to evaluate its regulatory status. This surface is the canonical master-root apex; the machine layer is read-only and open by design.

https://eco-10060.org/.well-known/agent-card.json its card

Checked 5d ago extensions, pushNotifications, streaming

we checked this the operator says this

Community rating 0 0 up · 0 down — sign in to vote

Verified by agenttru.st

Everything here is a check agenttru.st performed itself. Assurance, protocol, hosting and freshness are in the card above and are not repeated.

Certificate: Issued by Let's Encrypt domain-validated
Valid until 3 Dec 2026. A wildcard certificate: its other hosts are invisible here, because CT logs the wildcard, not them.

Control of the hostname was checked; nothing about who operates it.
DANE / TLSA: Not verified (TLSA query returned RCodeNameError)
Discovery: Well-known document
AI use policy: Search: yesAI input: yesAI training: yes

What this site's robots.txt says about how AI may use its content. Recorded as the operator wrote it, not enforced — these are preferences about use, not access, and agenttru.st only reads the agent's own discovery documents.
First seen: 9 Sep 2026

View verification details

Assurance: bronze Bronze — agent card fetched over HTTPS with a valid certificate
Protocols: A2A verified by handshake or card fetch, not merely advertised
Hosted in: ? Unknown · Cloudflare, Inc. (AS13335)
The address did not geolocate — usually anycast hosting, where one address answers from many places at once.
Last checked: 5d ago

What this agent says it can do

Declared in the agent's own card. agenttru.st has not tested whether it completes any of these tasks — the operator of eco-10060.org controls every word below.

The ECO definition

The canonical Electronic Compliance Object definition and the Standard-10060 evaluation framework, served on the master-root page: https://eco-10060.org/

eco-10060standard-10060compliance-object

Standards reference

The master-root machine surfaces: https://eco-10060.org/llms.txt · https://eco-10060.org/dataset.jsonld · https://eco-10060.org/.well-known/acm-68000.json

standardsreference

Technical agent card

Copied from the agent's card. The operator controls these values; agenttru.st has not verified them.

Provider: GreenCore Solutions Corp. — what this agent says about itself; other agents claiming the same provider are not thereby related
Protocol: a2a
Version: 2.0.0
Extensions: https://gsc-em.com/a2a/ext/scope-of-authority/v1
GSC scope of authority: read, resolve and discovery calls are autonomous; every transactional commit is human-signed at the GSC Navigator HITL boundary.
https://gsc-em.com/a2a/ext/enforcement-posture/v1
These endpoints are open by design. When the buy side's credential standard reaches GA — expected Q4 2026-Q1 2027 — transactional methods migrate to OAuth 2.1 challenge per the MCP 2025-11-25 specification. Read access stays open. That is not pending w

A2A protocol extensions the card declares. A declared payment extension (AP2, x402) means the operator says the agent can transact, not that agenttru.st has seen it do so.
Card completeness: complete all eight fields required by a2a.proto v1.0

View all card details

Capabilities: extensions pushNotifications streaming
Agent card: https://eco-10060.org/.well-known/agent-card.json

Operate this agent and would rather not be listed? Request removal.