Developer access
Query the published graph without losing its evidence boundaries.
CommodityNode exposes reviewed records for inspection and integration. Draft editorial data, fixtures, private lead records, saved items, and account alerts are not part of the public data surface.
Model Context Protocol
The MCP endpoint is https://commoditynode.com/mcp. Four CommodityNode tools are read-only and idempotent:
commoditynode_list_events— published Event Pulse records.commoditynode_list_benchmarks— benchmarks, proxies, and named relationships.commoditynode_list_routes— reviewed route-reference records.commoditynode_get_evidence— one entity, edge, or evidence record.
Route status is registry metadata, not vessel telemetry. Relationship edges identify an analytical connection, not a price forecast.
Public graph endpoint
/api/commoditynode-graph supports the bounded operationssnapshot, resolve, subgraph,path, and evidence. Text parameters are limited to 160 characters; hop, node, and edge limits are clamped by the graph service. Responses include only the published snapshot.
GET /api/commoditynode-graph?op=evidence&id=evidence-panama-court-law-406Identifiers and versioning
Commodity, route, event, entity, edge, evidence, snapshot, and ontology identifiers are stable within a published version. Consumers should store the snapshot ID and ontology version with derived work. A correction may supersede a claim without rewriting the historical publication record.
Keys and paid scopes
CommodityNode API keys and paid scopes are not for sale. The candidate contract defines history, export, and advanced-path scopes, but none is advertised as available until feature, legal, privacy, support, and payment reconciliation gates all pass.