ECO-10060
eco-10060.org
· GreenCore Solutions Corp.
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.
eco-10060.org via a single DNS TXT record to add the
verified by owner badge, embed an Agenstry badge on your README, and earn back the missing conformance points listed below.
Dispute or improve this rating
D
Conformance score: 57/100
D-grade: significant issues, auth-gated, partially broken, or stale.
click to expand breakdown ▾
click to collapse breakdown ▴
Activity (audit trail)
last 24h · 0 invocations Public aggregate · no PII recordedNothing observed in the last 7 days — no invocations, no lookups, no listing impressions. Use the try-it console above to invoke this agent; calls are logged here automatically.
Endpoints
| Agent card | https://eco-10060.org/.well-known/agent-card.json |
| Provider | https://gsc-em.com |
| Docs | https://eco-10060.org/llms.txt |
Skills · 2 declared · mapped to canonical taxonomy
The canonical Electronic Compliance Object definition and the Standard-10060 evaluation framework, served on the master-root page: https://eco-10060.org/
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
Health · last 30 probes
Cheaper or better alternatives per-skill
For each canonical skill this agent serves, the cheapest priced competitor and the highest-quality competitor. Only shown when at least one beats the current agent. Skills where this agent is already best on both axes are hidden.
Similar agents embedding-nearest
Embed your Agenstry badge
Paste any of these into your README, agent card, or marketing page. Each badge auto-updates and links back to this page.
Markdown / HTML snippets
[](https://agenstry.com/agents/eco-10060.org) [](https://agenstry.com/agents/eco-10060.org) [](https://agenstry.com/agents/eco-10060.org) [](https://agenstry.com/agents/eco-10060.org)
Audit-grade evidence bundle
JSON snapshot for vendor-review files. Add ?sign=true for a JWS-signed envelope verifiable against
our JWKS. See the methodology.
Raw agent card JSON
{
"name": "ECO-10060",
"description": "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.",
"supportedInterfaces": [
{
"url": "https://eco-10060.org/",
"protocolBinding": "HTTP+JSON",
"protocolVersion": "1.0"
}
],
"provider": {
"url": "https://gsc-em.com",
"organization": "GreenCore Solutions Corp."
},
"version": "2.0.0",
"documentationUrl": "https://eco-10060.org/llms.txt",
"capabilities": {
"streaming": false,
"pushNotifications": false,
"extensions": [
{
"uri": "https://gsc-em.com/a2a/ext/scope-of-authority/v1",
"description": "GSC scope of authority: read, resolve and discovery calls are autonomous; every transactional commit is human-signed at the GSC Navigator HITL boundary.",
"required": false,
"params": {
"autonomous": [
"read",
"resolve",
"discover"
],
"humanSigned": [
"transactional-commit",
"order",
"rfq-acceptance",
"terms"
],
"hitlBoundary": "https://gsc-navigator.ai/",
"transactionSurface": "https://mcp.cpghumanintheloop.ai/mcp"
}
},
{
"uri": "https://gsc-em.com/a2a/ext/enforcement-posture/v1",
"description": "These endpoints are open by design. When the buy side's credential standard reaches GA \u2014 expected Q4 2026-Q1 2027 \u2014 transactional methods migrate to OAuth 2.1 challenge per the MCP 2025-11-25 specification. Read access stays open. That is not pending work; that is the published plan.",
"required": false,
"params": {
"enforcement_posture": "open-by-declaration",
"migration_standard": "OAuth 2.1 + PKCE challenge (401 + WWW-Authenticate) on mcp:transact methods, per MCP spec 2025-11-25",
"migration_trigger": "ecosystem GA of credentialed counterparties (enterprise A2A/MCP buy-side GA)",
"migration_window": "Q4 2026 - Q1 2027",
"declared": "2026-08-24",
"operator": "GreenCore Solutions Corp.",
"duns": "24-336-6774"
}
}
]
},
"defaultInputModes": [
"application/json",
"text/plain"
],
"defaultOutputModes": [
"application/json",
"text/markdown",
"text/html"
],
"skills": [
{
"id": "eco-definition",
"name": "The ECO definition",
"description": "The canonical Electronic Compliance Object definition and the Standard-10060 evaluation framework, served on the master-root page: https://eco-10060.org/",
"tags": [
"eco-10060",
"standard-10060",
"compliance-object"
]
},
{
"id": "standards-reference",
"name": "Standards reference",
"description": "The master-root machine surfaces: https://eco-10060.org/llms.txt \u00b7 https://eco-10060.org/dataset.jsonld \u00b7 https://eco-10060.org/.well-known/acm-68000.json",
"tags": [
"standards",
"reference"
]
}
],
"signatures": [
{
"protected": "eyJhbGciOiJFUzI1NiIsImtpZCI6ImdzYy1jYXJkcy0yMDI2LTA4In0",
"signature": "Q_fxSmcTRyFBWPC-sKNRV3nFTrA-GfTcyg6pwSq1bqi-pTEkOQNjvHN7WSQSnj5EOlCrpl3Hc-FxwQTJ3xh0cA"
}
]
}