GeonicDB

GeonicDB is a FIWARE Orion-compatible Context Broker. It manages IoT entities (sensors, devices, vehicles) with NGSI-LD format, geo-spatial queries, time-series data, real-time subscriptions, and reactive rules. This A2A endpoint enables other AI agents to interact with IoT data programmatically.

Skills

• Entity Management
  CRUD operations on IoT entities, entity types, and attributes. Supports list, get, create, update, delete, and geo-spatial/attribute search. The query actions (list / search_by_location / search_by_attribute) accept typePattern, a GeonicDB extension evaluated as a verbatim regular expression and combined with type as an AND (#2156). Entities are returned in the NGSI-LD simplified (keyValues) representation; multi-attributes (several instances of the same attribute, distinguished by datasetId) are returned as {"<attr>": {"dataset": {"@none": <default instance value>, "<datasetId>": <value>}}} per ETSI GS CIM 009 clause 4.5.4, where "@none" appears only when a default instance exists. Distributed operations are opt-in (#2072): pass local=false on list / search_by_location / search_by_attribute to also query registered Context Sources; without it only local data is returned. `servicePath`: Deprecated / not supported (#1608): NGSI-LD has no Fiware-ServicePath concept, all data is stored under "/" (matching the HTTP NGSI-LD API). Any non-root value is rejected with an error. Use the entity "scope" attribute / "scopeQ" query for hierarchical organization instead.
  iotentitiesngsi-ldgeospatial
• Batch Operations
  Bulk create, upsert, update, merge, delete, and query operations on multiple entities at once. The query action accepts local=false to opt in to querying registered Context Sources (#2072) and typePattern (#2156); purge rejects typePattern rather than silently ignoring it. `servicePath`: Deprecated / not supported (#1608): NGSI-LD has no Fiware-ServicePath concept, all data is stored under "/" (matching the HTTP NGSI-LD API). Any non-root value is rejected with an error. Use the entity "scope" attribute / "scopeQ" query for hierarchical organization instead.
  batchbulkentities
• Temporal Data
  Time-series data management for entity attributes. Query historical values, create temporal entities, manage attribute instances. The get / query / list actions interpret the full set of temporal parameters (timerel, timeAt, endTimeAt, timeproperty, lastN, attrs, format, options, aggrMethods, aggrPeriodDuration) and query also accepts typePattern (#2156). timeproperty selects observedAt (default) / createdAt / modifiedAt / deletedAt per ETSI clause 4.11 (#2267). aggrPeriodDuration is optional (ETSI Table 5.2.21-1 cardinality 0..1): omitting it — or passing PT0S / P0D explicitly — aggregates the whole time range of the query as a single period, whose unspecified bounds are reported from the actual observedAt range of the matched data (#2109). get on a missing entity is a loud error, and a truncated history is reported in a "warnings" array. `servicePath`: Deprecated / not supported (#1608): NGSI-LD has no Fiware-ServicePath concept, all data is stored under "/" (matching the HTTP NGSI-LD API). Any non-root value is rejected with an error. Use the entity "scope" attribute / "scopeQ" query for hierarchical organization instead.
  temporaltimeserieshistory
• Configuration
  Manage reactive rules, JSON-LD contexts, and the read-only Smart Data Models catalog. Accepted `resource` values: `rules`, `jsonld_contexts`, `data_models`. Unknown values are rejected. Note the deliberate asymmetry with the MCP config tool: tenant-defined custom data models (`custom_data_models`) are reachable only through MCP (POST /mcp) or the HTTP API (/custom-data-models), and the Smart Data Models catalog (`data_models`) is reachable only here. For `jsonld_contexts`, the `kind` filter takes `Cached` / `Hosted` / `ImplicitlyCreated` (ETSI GS CIM 009 clause 5.13.3.3; the lowercase forms are accepted for backward compatibility). Any other value is rejected rather than silently ignored.
  configrulesjsonlddata-models
• Administration
  User and XACML policy management. Accepted `resource` values: `users`, `policies`. Unknown values are rejected. Tenant administration is not exposed here — use the HTTP Admin API (/admin/tenants). Requires tenant_admin or super_admin role.
  adminuserspolicies

How to call

https://geonicdb.geolonia.com/a2a

Listed in

Directories this entry was found in.