Anchored Metadata
For credit classes, projects, and credit batches, the metadata field in the ecocredit module holds an IRI that points to an off-chain JSON-LD document. Metadata for these entities is accessed the same way:
Query the Ledger (via gRPC, REST, or CLI) to retrieve the entity's metadata IRI
Resolve the IRI using the Metadata Graph API to retrieve the full JSON-LD document
Interpret the JSON-LD as linked data describing the entity's attributes, relationships, and supporting documents
Retrieving Metadata IRIs from the Ledger
Each entity stores its metadata reference in a metadata field within the ecocredit module. Ledger queries return a string like:
regen:13toVh9VgHfMJUDXSFTMQiDwRtiWQvhyeBpZe3jYpGMRnkZZB7jQyN8.rdfThis IRI is a deterministic, content-addressed identifier for the full metadata document.
Resolving IRIs via the Metadata Graph API
Use the Metadata Graph API to resolve any IRI:
GET https://api.regen.network/data/v2/metadata-graph/{iri}The API automatically retrieves content from IPFS, HTTPS endpoints, or other configured resolvers and returns a JSON-LD document containing the complete semantic structure: context, types, relationships, and links to supporting evidence.
For full API specifications, see the Metadata Graph API Swagger docs.
JSON-LD Response Examples
Credit Class Metadata
Credit class metadata describes the protocol itself—methodology, eligible activities, impact categories, and governance structure.
Request:
GET https://api.regen.network/data/v2/metadata-graph/regen:...class-iri....rdfResponse (excerpt):
json
Typical fields: protocol name and description, crediting term, ecosystem types, primary impact with SDG mappings, eligible activities, applicable regions, and links to methodology documents.
Project Metadata
Project metadata describes the specific implementation—location, stakeholders, ecosystem characteristics, and activities.
Request:
GET https://api.regen.network/data/v2/metadata-graph/regen:...project-iri....rdfResponse (excerpt):
json
Typical fields: name and description, geographic location (GeoJSON), project size, ecosystem type, project developer/operator/monitor/verifier, co-benefits, activities, media assets, and start/end dates.
Credit Batch Metadata
Credit batch metadata documents the issuance event—monitoring reports, verification reports, and supporting evidence.
Request:
GET https://api.regen.network/data/v2/metadata-graph/regen:...batch-iri....rdfResponse (excerpt):
json
Typical fields: registry agent, project verifier, monitoring reports with anchored data IRIs, verification reports, supplemental materials, and links to PDFs and evidence documents.
Upcoming Standardization
The Framework Working Group is finalizing unified LinkML-backed metadata schemas for credit classes, projects, credit batches, evidence, claims, and methodologies.
Once adopted:
All JSON-LD documents will share consistent structures across entity types
Developers can reliably parse metadata using shared vocabularies
New capabilities (SPARQL queries, schema validation, graph navigation) will work seamlessly across the ecosystem
Last updated
Was this helpful?