Viridi · Schema
ComponentDescriptor
CompanyEnergyEnergy StorageBatteryIoTIndustrial IoTEnergy ManagementManufacturingTelematicsMicrogrid
Properties
| Name | Type | Description |
|---|---|---|
| id | object | JSON object with the descriptor Id. Specify existing descriptor id to update the descriptor. Referencing non-existing descriptor Id will cause error. Omit this field to create new descriptor. |
| createdTime | integer | Timestamp of the descriptor creation, in milliseconds |
| type | string | Type of the Rule Node |
| scope | string | Scope of the Rule Node. Always set to 'TENANT', since no rule chains on the 'SYSTEM' level yet. |
| clusteringMode | string | Clustering mode of the RuleNode. This mode represents the ability to start Rule Node in multiple microservices. |
| name | string | Name of the Rule Node. Taken from the @RuleNode annotation. |
| clazz | string | Full name of the Java class that implements the Rule Engine Node interface. |
| configurationVersion | integer | Rule node configuration version. By default, this value is 0. If the rule node is a versioned node, this value might be greater than 0. |
| actions | string | Rule Node Actions. Deprecated. Always null. |
| hasQueueName | boolean | Indicates that the RuleNode supports queue name configuration. |
| configurationDescriptor | object |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://raw.githubusercontent.com/api-evangelist/viridi-parente/main/json-schema/viridi-parente-component-descriptor-schema.json",
"title": "ComponentDescriptor",
"x-generated": "2026-10-20",
"x-method": "derived",
"x-generator": "derive-json-schema.py",
"x-source": "openapi/viridi-parente-component-descriptor-controller-api-openapi.yml#/components/schemas/ComponentDescriptor",
"properties": {
"id": {
"$ref": "#/$defs/ComponentDescriptorId",
"description": "JSON object with the descriptor Id. Specify existing descriptor id to update the descriptor. Referencing non-existing descriptor Id will cause error. Omit this field to create new descriptor."
},
"createdTime": {
"type": "integer",
"format": "int64",
"description": "Timestamp of the descriptor creation, in milliseconds",
"readOnly": true
},
"type": {
"type": "string",
"description": "Type of the Rule Node",
"enum": [
"ENRICHMENT",
"FILTER",
"TRANSFORMATION",
"ACTION",
"EXTERNAL",
"FLOW"
],
"readOnly": true
},
"scope": {
"type": "string",
"description": "Scope of the Rule Node. Always set to 'TENANT', since no rule chains on the 'SYSTEM' level yet.",
"enum": [
"TENANT"
],
"readOnly": true
},
"clusteringMode": {
"type": "string",
"description": "Clustering mode of the RuleNode. This mode represents the ability to start Rule Node in multiple microservices.",
"enum": [
"USER_PREFERENCE",
"ENABLED",
"SINGLETON"
],
"readOnly": true
},
"name": {
"type": "string",
"description": "Name of the Rule Node. Taken from the @RuleNode annotation.",
"readOnly": true
},
"clazz": {
"type": "string",
"description": "Full name of the Java class that implements the Rule Engine Node interface.",
"readOnly": true
},
"configurationVersion": {
"type": "integer",
"format": "int32",
"description": "Rule node configuration version. By default, this value is 0. If the rule node is a versioned node, this value might be greater than 0.",
"readOnly": true
},
"actions": {
"type": "string",
"description": "Rule Node Actions. Deprecated. Always null.",
"readOnly": true
},
"hasQueueName": {
"type": "boolean",
"description": "Indicates that the RuleNode supports queue name configuration.",
"readOnly": true
},
"configurationDescriptor": {
"$ref": "#/$defs/JsonNode"
}
},
"$defs": {
"ComponentDescriptorId": {
"properties": {
"id": {
"type": "string",
"format": "uuid",
"description": "string"
}
},
"required": [
"id"
]
},
"JsonNode": {
"description": "A value representing the any type (object or primitive)"
}
}
}
Work with this as data
Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/viridi-parente-component-descriptor"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.