A VIN code — and a resolution layer — for every GPU
The same H100 exists as four unrelated entries at the lessor, the lessee, the lender and the insurer. CVIN assigns each physical GPU one globally unique, cross-operator, machine-verifiable identity, backed by an append-only registry anyone can independently replay. Think "Carfax for GPUs": we don't score, we don't appraise — we record what happened, when, and who saw it.
cvin:<mfr>.<model>.<form>.<mem>:<serial-hash-16>
Example: cvin:nv.h100.sxm.80g:6a1kfvdo43buqm34. The last segment is a truncated SHA-256 of the serial number — one-way. Your asset list never leaves your facility; anyone holding the device can re-derive the same CVIN at any time.
Append-only, hash-chained
Every observation (listing, rental, telemetry, lien) is chained: record hash + global head. Editing one byte breaks the chain. Anyone can replay and verify — trust comes from verifiability, not from us.
1,109 observations · 298 canonical IDs (+1 aliases)
Live numbers from /v1/stats. Synthetic seed data is disclosed per-record (synthetic:true) with a public target — see the provenance page. We publish our own weaknesses because that is the only way this kind of registry earns trust.
Identity levels — what can be asserted
| Level | Basis | Can assert | Cannot assert | Use in contracts |
|---|---|---|---|---|
| M · model | Platform listing for a model | This model is offered at this price | Anything about a physical unit | No |
| L0 · listing fingerprint | Listing consistency | The same listing is unchanged | That two records are the same physical device | No |
| L1 · serial-observable | SHA-256 of observed serial | Same physical device, same ID across operators | That telemetry is device-signed | Yes — pledge lists, pre-rental checks |
| L2 · hardware trust root | Device-side ed25519 key signs telemetry | This telemetry was signed by the device itself | — | Yes — in-custody verification, claims triggers |
L0 and M records are structurally barred from any legal act whose subject is "this physical device" (pledge registration, insurance underwriting, pool admission). The machine-readable version: GET /v1/permits?cvin=…&use=pledge. Full definitions on the levels page.
Pricing — writes are free, forever
- GET /v1/resolve/{cvin} — existence, level, summary
- Declarations, promotions, device attestations
- Public condition certificate + embeddable badge
- Full history + continuity proof
- MCP tools: cvin_resolve / cvin_history / cvin_verify
- Settled on-chain (Base, USDC, EIP-3009)
- Identity, activity, attestation status
- Lien detail + duplicate-pledge determination
- Chain continuity proof, printable for the file
- Periodic signed-telemetry checks while pledged
- Instant alerts: device offline, went cold, key change
- Lien-change webhooks
Why writes are free
Operators are the supply side — without your devices this registry is worth nothing, so registration never costs you anything. The people who pay are the ones making money decisions: they are buying "I verified before the money moved." Full pricing rationale on the pricing page.
Quickstart — 5 minutes, no account
# 1) Resolve — free, no key
curl https://cvin.org/v1/resolve/cvin:nv.h100.sxm.80g:6a1kfvdo43buqm34
# 2) Register your own fleet — free, serial never uploaded
curl -X POST https://cvin.org/v1/declare -H 'content-type: application/json' \
-d '{"cvin":"cvin:nv.h100.sxm.80g:6a1kfvdo43buqm34",
"operator":"your-cloud","region":"us-east",
"source_url":"https://your-site.com/fleet/h100"}'
# 3) Full history — per-call via x402 (Base USDC), returns 402 + challenge first
curl https://cvin.org/v1/history/cvin:nv.h100.sxm.80g:6a1kfvdo43buqm34Batch onboarding script (tested, zero dependencies beyond Python + cryptography): cvin_onboard.py — full manual on the operator onboarding page. MCP endpoint for AI agents: POST https://cvin.org/mcp (13 tools incl. cvin_report at $2/report; see .well-known/mcp.json).
Who uses this
Compute operators & lessors
Your buyers ask: "why should I trust that these cards are real?" Get a linkable certificate and an embeddable badge for your sales page — /badge/{cvin}.svg, live-rendered, can't be photoshopped.
Used-GPU dealers & resellers
One bad card eats the margin of ten deals. Before you buy: is the serial real, is it the same device, has it been pledged elsewhere, is the history continuous? $2 per verification, printable for the deal file.
Lenders, lessors, insurers
During the life of a loan you don't need one query — you need proof the device still exists, still is the same machine, week after week. That's signed telemetry + webhooks: $0.60/device/month.
Boundaries (read this before integrating)
Chinese-market note: the statutory pledge registration authority in mainland China is the 中登网 (动产融资统一登记公示系统). CVIN is an evidence layer that complements it — it does not replace legal filing. Third-party market data is licensed CC BY 4.0 from rentgpu.link (GPUPLN v0.1), attributed per record.
Full documentation (Chinese, machine-translatable, machine-readable): spec v0.1 · identity levels · pricing · quickstart · llms.txt · FAQ