Skip to content
Back to search
📊 Intel view 📋 Audit JSON 🔄 Changelog
90
A2A signed A2A 1.0 v2.0.0

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.

Build a free agent shortlist. Save this listing to revisit it from your account. Sign in to save
🛡
Own this agent?
Verify the domain 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.
Verify ownership
🔔 Watch this agent. Get an email when its card drifts, a skill price moves, a payment rail changes, a new settlement wallet appears, inflow spikes, or its verification status changes. Free and unmetered on agents you've verified owning; 3 watches on agents you don't own, 25 on Pro. Sign in to watch
Trust score
57/100
grade D · 9 criteria
Uptime
97.7%
44 direct probes · 30d
~20 ms response
Observed inflow · 30d
no payment wallet declared
Invocations · 7d
0
no calls observed
Card drift · 7d
stable
2 snapshots tracked
Owner
unverified
claim this listing →

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 ▴
pass Valid AgentCard 10/10
Parseable AgentCard returned by the well-known endpoint (Agenstry readiness signal; not an official TCK certification).
fail Live JSON-RPC 2/25
Card is valid but has no .url field.
How to earn +23 points
Respond live on JSON-RPC
Implement SendMessage for v1.0 (or message/send for v0.x), negotiate A2A-Version, and return a schema-valid JSON-RPC response. Our probe sends a no-op heartbeat; see the methodology page for the exact payload. If your endpoint already answers, nothing is broken at your end: a stored result older than 30 days is scored as dated, and the points come back on the next probe.
Docs →
pass Protocol version 10/10
Declares A2A 1.0 with supportedInterfaces[] (current v1 card shape).
partial JWS signature 5/10
Card has a signatures[] entry but we haven't verified it.
How to earn +5 points
Sign your AgentCard with JWS
Add a `signatures` array to the card body following RFC 7515. Publish the public JWKS at /.well-known/jwks.json. Sign with ES256 (recommended) or RS256.
Docs →
pass Uptime track record 15/15
43/44 probes succeeded (98% uptime).
partial Skill declaration 6/10
Declares 2 skill, usable but thin.
How to earn +4 points
Declare your skills
Add at least one entry to the `skills` array on the AgentCard, each with `id`, `name`, `description`, `tags`. We canonicalise these into the global skill taxonomy on next probe.
Docs →
partial Verified Identity 5/10
Provider declared: GreenCore Solutions Corp. (https://gsc-em.com). Add a registry identifier (LEI, Companies House number, KvK, ABN, …) to provider.legalEntity for full verified-business credit.
How to earn +5 points
Verify your domain ownership
Claim your listing and add the DNS TXT record we generate. Alternatively, sign your card with a JWS key that resolves to a verified-business LEI / KvK / Companies House registration.
Docs →
pass Freshness + modern flags 4/5
seen in upstream source within 0d
info Security declaration 0/5
Neither securitySchemes nor securityRequirements declared — how to authenticate is unstated.

Activity (audit trail)

last 24h · 0 invocations Public aggregate · no PII recorded

Nothing 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.

Card history

2 snapshots drifted 1× Every change to agent-card.json
Captured Hash
2026-08-28 02:49:36 current 36aec52e4e92… view →
2026-08-16 03:11:21 bb5394f4d698… view →
Uptime
97.7%
44 direct probes · 30d
Response
30ms
last direct probe
Skills
2
declared
Streaming
SSE-capable

Endpoints

Agent cardhttps://eco-10060.org/.well-known/agent-card.json
Providerhttps://gsc-em.com
Docshttps://eco-10060.org/llms.txt
Discovered via
manifests recrawl_hot

Skills · 2 declared · mapped to canonical taxonomy

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/

canonical Compliance Assessment match 82%
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

canonical Smart Home Routines match 80%
standardsreference

Health · last 30 probes

When HTTP Live JSON-RPC Latency
2026-09-16 05:04:07 200 30ms
2026-09-14 00:33:53 200 39ms
2026-09-13 06:11:25 200 40ms
2026-09-12 23:57:42 200 36ms
2026-09-12 10:56:55 200 43ms
2026-09-12 04:40:26 200 40ms
2026-09-11 16:45:22 200 41ms
2026-09-11 09:48:24 200 48ms
2026-09-09 08:54:21 200 44ms
2026-09-09 02:30:08 200 44ms

Cheaper or better alternatives per-skill

↑ 2 higher quality

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

SM-ECO-10060
Sovereign Manifest of Electronic Compliance Objects under Standard-10060. This surface is the canonical apex of the standard; the machine la
GreenCore Solutions Corp. · q 90%
SM-ECO-10060 — Sovereign Manifest
Sovereign Manifest of Electronic Compliance Objects under Standard-10060.
GreenCore Solutions Corp. · q 0%
CA-ECO-10060 — Canada — Canonical
Sovereign jurisdictional resolver for Canada under Standard-10060. Member of SM-ECO-10060.
GreenCore Solutions Corp. · q 78%
SG-ECO-10060 — Singapore — Canonical
Sovereign jurisdictional resolver for Singapore under Standard-10060. Member of SM-ECO-10060.
GreenCore Solutions Corp. · q 78%
KR-ECO-10060 — South Korea — Canonical
Sovereign jurisdictional resolver for South Korea under Standard-10060. Member of SM-ECO-10060.
GreenCore Solutions Corp. · q 78%
JP-ECO-10060 — Japan — Canonical
Sovereign jurisdictional resolver for Japan under Standard-10060. Member of SM-ECO-10060.
GreenCore Solutions Corp. · q 78%

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.

Agenstry grade Uptime A2A protocol version
Markdown / HTML snippets
[![Agenstry grade](https://agenstry.com/badge/eco-10060.org.svg)](https://agenstry.com/agents/eco-10060.org)
[![Verified Business](https://agenstry.com/badge/eco-10060.org/identity.svg)](https://agenstry.com/agents/eco-10060.org)
[![Uptime](https://agenstry.com/badge/eco-10060.org/uptime.svg)](https://agenstry.com/agents/eco-10060.org)
[![A2A version](https://agenstry.com/badge/eco-10060.org/protocol.svg)](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.

audit.json audit.json (JWS-signed) verification history
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"
    }
  ]
}