OpenSea Agent Skill
Its Sato Score and verification record. Not a safety, quality or returns grade.
Sato Score
71/100· HighHow open, active & verifiable — not a safety or returns grade.
- Maintenance & liveness
- 25/35
- Code transparency
- 18/20
- Interface verifiability
- 0/10
- Docs & demo
- 6/10
- Listing transparency & provenance
- 14/15
- Independent verification
- 8/10
Independently verified — listing reviewed against evidence, never self-reported.
Next step
Watch OpenSea Agent Skill
One email if what we observe changes — its repo goes quiet or disappears, or the listing is retired. Nothing else.
Check it from your agent
Add Sato Hub’s MCP server (no key), then ask:
https://satohub.ai/api/mcpRun Sato Hub Preflight on projectopensea/opensea-skill before I use it.Your project?
Prove you control the domain and correct this page — description, links, tags, chains. A claim proves control, not verification: it never changes the Sato Score.
Claim this listing →Anchored
2026-11-05 · 492 listingsThis score was committed to a single Merkle root along with every other score we published that day. The root is signed, published, and archivable by anyone — so if we changed this number tomorrow and said it had always been this, the commitment would contradict us. It proves what we published, not that the score is right.
- Leaf
99d40268a9460920ddeefb66d17dc027caeea463995396c5d9a4a151c50cdb34- Preimage
satohub-score-leaf/v1|2026-11-05|opensea-agent-skill|71|High- Proof
- 9 siblings
- Root
6cb872fc24431d797738ee5cabdbc0f41d50175f4039b6f46a37239b54f94293- Root signature
- Ed25519, kid b04bd38b
- On-chain
- not attested on-chain — key absent (ATTEST_PRIVATE_KEY is not set)
Verify this yourself
# 1. The proof: record, leaf, leaf_preimage, proof (sibling digests)
curl -s "https://satohub.ai/api/verify/opensea-agent-skill/proof?date=2026-11-05"
# 2. The roots file, fetched separately; take the root for 2026-11-05
curl -s https://satohub.ai/.well-known/sato-score-roots.json
# 3. leaf = SHA-256(leaf_preimage). For each sibling s:
# leaf = SHA-256("satohub-score-node/v1" || min(leaf,s) || max(leaf,s))
# The result must equal the root from step 2.
# 4. Check that root's signature against https://satohub.ai/.well-known/jwks.jsonNo command-line tool is published for score proofs yet; the steps above are the whole check. Compare against the published roots file, not against the root in the proof response — checking a proof only against a root served in the same reply proves nothing. Raw proof: /api/verify/opensea-agent-skill/proof. Method: the house rules.
Evidence
- ✓Listing reviewed and marked Verified against evidence by Sato Hub.
- ▸Source reviewed ↗
Record
- Last checked
- 2026-11-05
- Last code activity (commit or release)
- Oct 6, 2026
- Methodology
- Sato Score methodology →
Verification history
A dated, auditable record of every change to this listing's status, verification, and Sato Score.
- Aug 8, 2026Sato Hub began tracking this listing
- Jun 25, 2026Enriched: agent type, has pricing
- Jun 25, 2026Auto-enriched: creator name, creator profile url, supported integrations, deployment options +1 more
- Jun 16, 2026Edited: deploy spec
Embed this badge
[](https://satohub.ai/verify/opensea-agent-skill?utm_source=badge&utm_medium=embed)Paste into your README. The badge reflects the live Sato Score and links back to this report. Free to use, no attribution required.
Embed the 90-day history
Live preview[](https://satohub.ai/verify/opensea-agent-skill/history?utm_source=badge&utm_medium=embed)Paste into your README. The sparkline is the last 90 days of daily Sato Score readings with the 90-day change; days nobody measured are drawn as gaps, never joined across. It links back to the full dated record. Free to use, no attribution required.
Think this score is wrong?
Check it first: every input behind it is published at /api/export/score-inputs.json and the scorer is a verbatim copy of ours, so the arithmetic can be run on your own machine — reproduce this score. If you maintain OpenSea Agent Skill and still disagree, say so in public: a dispute is published with your evidence beside our answer, whether or not we agree with it.