Skip to main content

Node Registry

The Node Registry is the ARP Standard v1 service that catalogs NodeTypes:

  • publish/get/search node type metadata
  • versioning and deprecation
  • input/output JSON schemas per node type
Standard vs. implementation

This page documents the ARP Standard contract (OpenAPI + schemas).

For a runnable reference implementation, see: JARVIS Node Registry.

OpenAPI (v1)​

  • ARP_Standard/spec/v1/openapi/node-registry.openapi.yaml

Endpoints (v1)​

All services MUST implement:

  • GET /v1/health
  • GET /v1/version

Node Registry MUST implement:

EndpointDescription
GET /v1/node-typesList node types (NodeType[]; optional q + kind)
POST /v1/node-typesPublish a node type (NodeTypePublishRequest → NodeType)
GET /v1/node-types/{node_type_id}Get node type (NodeType; optional version)

Key payloads​

  • NodeType: spec/v1/schemas/core/node_type.schema.json
  • NodeTypePublishRequest: spec/v1/schemas/node_registry/node_types/node_type_publish_request.schema.json

Notes​

  • The registry stores metadata, not executable code.
  • Selection and PDP often depend on registry metadata to make decisions.
  • NodeTypes are “capability contracts”: stable node_type_id + versioned schemas + descriptive metadata for selection/binding.

See also​