FIWARE
FIWARE is an open-source framework that provides a curated set of standards and components for context information management. The cornerstone is the NGSI-LD API standardized by ETSI ISG CIM, which allows applications to provide, consume, and subscribe to context information in smart cities, smart industry, smart agriculture, and smart energy scenarios.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles FIWARE the way a machine reads it — 22 machine-readable artifacts across 15 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — FIWARE scores 35.7/100 (thin), with a separate agent-readiness read of 39/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile FIWARE
Each block below is one kind of artifact we hold for FIWARE. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 15
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
FIWARE API Entry Point API
The API Entry Point API from FIWARE — 1 operation(s) for api entry point.
FIWARE Attribute Value API
The Attribute Value API from FIWARE — 1 operation(s) for attribute value.
FIWARE Attributes API
The Attributes API from FIWARE — 1 operation(s) for attributes.
FIWARE Batch Operations API
The Batch Operations API from FIWARE — 7 operation(s) for batch operations.
FIWARE Context Information API
The Context Information API from FIWARE — 4 operation(s) for context information.
FIWARE Context Sources API
The Context Sources API from FIWARE — 4 operation(s) for context sources.
FIWARE Context Subscription API
The Context Subscription API from FIWARE — 2 operation(s) for context subscription.
FIWARE CSourceRegistrations API
The CSourceRegistrations API from FIWARE — 2 operation(s) for csourceregistrations.
FIWARE CSourceSubscriptions API
The CSourceSubscriptions API from FIWARE — 2 operation(s) for csourcesubscriptions.
FIWARE Entities API
The Entities API from FIWARE — 11 operation(s) for entities.
FIWARE Registrations API
The Registrations API from FIWARE — 2 operation(s) for registrations.
FIWARE Subscriptions API
The Subscriptions API from FIWARE — 4 operation(s) for subscriptions.
FIWARE Temporal API
The Temporal API from FIWARE — 5 operation(s) for temporal.
FIWARE Temporal Evolution API
The Temporal Evolution API from FIWARE — 5 operation(s) for temporal evolution.
FIWARE Types API
The Types API from FIWARE — 2 operation(s) for types.
Scroll within the panel for all 15 ·
Open Collections 2
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
ETSI ISG CIM / NGSI-LD API
OPEN COLLECTIONFIWARE-NGSI v2 Specification
OPEN COLLECTIONPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Fiware Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Fiware Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Fiware Finops
FINOPSSecurity Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for FIWARE — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Company 3
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/fiware · machine-readable index on apis.io