{"ok":true,"schema_version":1,"data":{"contract_version":"2026-07-03.2","endpoint_summary":{"by_kind":{"dashboard":2,"data-artifact":4,"docs":3,"source-repo":3,"subnet-api":2,"website":2},"by_layer":{"data-provider":4,"docs-provider":8,"subnet-app":4},"by_publication_state":{"monitored":13,"verified":3},"by_status":{"ok":13,"unknown":3},"endpoint_count":16,"monitored_count":13,"pool_eligible_count":0},"generated_at":"2026-11-04T15:29:42.770Z","provider":{"authority":"provider-claimed","cluster_id":"nodexo.ai","docs_url":"https://docs.nodexo.ai/","endpoint_count":16,"id":"nodexo","kind":"subnet-team","name":"Nodexo","netuids":[27,106],"notes":"Provider entry for Nodexo Compute / SN106 (on-chain SubnetIdentitiesV3 netuid 106 = \"Nodexo\", nodexo.ai; previously mis-keyed to SN27, which on-chain is \"Team TBC\"). Official browser-facing website, docs, and console surfaces are tracked, but simple Node/HEAD probes currently receive connection resets and are not treated as healthy monitored endpoints.","schema_version":1,"subnet_count":2,"surface_count":16,"website_url":"https://nodexo.ai/"},"schema_version":1},"meta":{"artifact_path":"/metagraph/providers/nodexo.json","cache":"standard","contract_version":"2026-07-03.2","generated_at":"2026-11-04T15:29:42.770Z","published_at":"2026-11-04T15:29:42.770Z","source":"kv"}}