NFC (Near Field Communication)
Near Field Communication (NFC) is a set of short-range wireless communication protocols that enable two electronic devices to establish communication by bringing them within a few centimeters of each other. NFC is governed by the NFC Forum and standardized through ISO/IEC 18092 and ISO/IEC 14443. Common applications include contactless payments (Apple Pay, Google Pay), transit ticketing, access control, device pairing, smart posters, and secure identification. NFC defines several technical specifications including NDEF (data exchange format), NCI (controller interface), LLCP (link layer), SNEP (data exchange), and the Tag Type 1-5 operation specifications.
Index entry only — little beyond a description and a link, and nothing machine-readable enough for an agent to act on without a human reading the site first.
NFC (Near Field Communication) is tracked in the API Evangelist network. This page is the human-readable profile that sits on top of the machine-readable index we maintain at apis.io.
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 — NFC (Near Field Communication) scores 7.2/100 (minimal), with a separate agent-readiness read of 0/100 (human only). 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
Resources
Every other property we hold for NFC (Near Field Communication) — 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
Access & Security 1
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Company 1
The organization behind the API
Other 1
Properties that don't map to a standard resource type
NFC (Near Field Communication) is in the network as a tracked entity. We haven't yet indexed a public API surface for it — when one is published, the artifacts, score, and agent-readiness read will appear here automatically. The source repository is where that profile is built.
← All providers · Data indexed from github.com/api-evangelist/nfc · machine-readable index on apis.io