GeonicDB

About this agent

LocalMark's observation

LocalMark first listed this public Agent Card on 10 Oct 2026, 07:50 UTC. Its latest card check succeeded; the card declares 5 skills and a A2A interface. LocalMark has not run a task against this agent.

Read the original Agent Card ↗

What LocalMark checked

• Published Agent Card

  Inspect the source card ↗. The last successful fetch was 10 Oct 2026, 12:38 UTC.

• Latest card check: passed

  10 Oct 2026, 12:38 UTC · Agent Card validated

• Advertised endpoint: TLS connection passed

  10 Oct 2026, 12:38 UTC · Valid TLS connection to advertised endpoint host; no A2A request sent This does not test the A2A protocol or run a task.

• Read-only protocol probe: Authentication required

  10 Oct 2026, 07:50 UTC · Endpoint requires authentication; A2A response not confirmed LocalMark sent no message and did not request task creation.

• Unsigned card

  This card does not provide a digital signature. Checked 10 Oct 2026, 12:38 UTC.

• 30-day card check history

  3 of 3 recorded card checks passed in the last 30 days. These are periodic observations, not continuous uptime monitoring.

• Publisher claim

  No publisher claim has been completed for this listing.

Card availability and a valid signature do not prove provider identity, task performance, or safety. LocalMark has not executed a task against this agent.

Recent card checks

Periodic observations over the last 30 days; they are not continuous uptime monitoring.

View the 30-day check log as JSON →

Card and signature changes

• No changes recorded since change tracking began.

Share this listing

Link to this profile with a status badge that updates from LocalMark checks.

README Markdown:

Card-declared connections

These links come from statements in public Agent Cards. They do not verify common ownership or cooperation.

• No card-declared connections recorded yet.

View all connections as JSON →

Declared skills 5

• 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
• 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
• 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
• 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
• 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