IYK

IYK API

The IYK API provides primitives for building digi-physical experiences. Core endpoints manage chips (NFC tags such as NTAG 424, KONG, and ARX HaLo), chip groups, items, taps/refs (validated physical interactions with replay protection), OTP codes (30-minute one-time passwords for NFT transfers and minting), and phygitals. Module endpoints cover POAP Events and Guestbook Events, and a Self-Service surface manages POAP devices. Authentication is via an x-iyk-api-key request header.

GitHub

Documentation

📖
Documentation
https://docs.iyk.app/api-overview
📖
APIReference
https://docs.iyk.app/api-core/chips
📖
GettingStarted
https://docs.iyk.app/api-quickstart
📖
Authentication
https://raw.githubusercontent.com/api-evangelist/iyk/refs/heads/main/authentication/iyk-authentication.yml

Other Resources

🔗
DeveloperPortal
https://docs.iyk.app
🔗
Conventions
https://raw.githubusercontent.com/api-evangelist/iyk/refs/heads/main/conventions/iyk-conventions.yml
🔗
X-MCPServerCandidate
https://raw.githubusercontent.com/api-evangelist/iyk/refs/heads/main/mcp/iyk-mcp.yml
🔗
DataModel
https://raw.githubusercontent.com/api-evangelist/iyk/refs/heads/main/data-model/iyk-data-model.yml
🔗
WellKnown
https://raw.githubusercontent.com/api-evangelist/iyk/refs/heads/main/well-known/iyk-well-known.yml
🔗
APIsJSON
https://raw.githubusercontent.com/api-evangelist/iyk/refs/heads/main/apis.yml

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API 
curl "https://apis.io/api/v1/apis/iyk-api"
All apis 
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

API entry from apis.yml

apis.yml Raw ↑ 
aid: iyk:iyk-api
name: IYK API
humanURL: https://docs.iyk.app
baseURL: https://api.iyk.app
tags:
- Chips
- Chip Groups
- Item
- Refs
- Taps
- OTP
- Phygitals
- POAP
- Event
- NFC
tags_raw:
- Chips
- Chip Groups
- Items
- Refs
- Taps
- OTP
- Phygitals
- POAP
- Events
- NFC
description: The IYK API provides primitives for building digi-physical experiences. Core endpoints manage
  chips (NFC tags such as NTAG 424, KONG, and ARX HaLo), chip groups, items, taps/refs (validated physical
  interactions with replay protection), OTP codes (30-minute one-time passwords for NFT transfers and
  minting), and phygitals. Module endpoints cover POAP Events and Guestbook Events, and a Self-Service
  surface manages POAP devices. Authentication is via an x-iyk-api-key request header.
properties:
- type: DeveloperPortal
  url: https://docs.iyk.app
- type: Documentation
  url: https://docs.iyk.app/api-overview
- type: APIReference
  url: https://docs.iyk.app/api-core/chips
- type: GettingStarted
  url: https://docs.iyk.app/api-quickstart
- type: Authentication
  url: authentication/iyk-authentication.yml
- type: Conventions
  url: conventions/iyk-conventions.yml
- type: X-MCPServerCandidate
  url: mcp/iyk-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate
    — a tool list derived from the published API contracts, not an existing server. The scorer already
    read the manifest and reported mcp_server correctly; the MCPServer type was crediting the artifact-type
    surfaces with a server that does not exist.'
- type: DataModel
  url: data-model/iyk-data-model.yml
- type: WellKnown
  url: well-known/iyk-well-known.yml