KonbiniAPI
KonbiniAPI is the social data layer for Instagram and TikTok, normalizing real-time public profile, post, video, comment, audio, location, and search data into a consistent ActivityStreams 2.0 (W3C) format. The service exposes one Bearer-authenticated REST API and an MCP (Model Context Protocol) interface so developers, AI agents, and automation platforms can fetch normalized social data without managing platform-specific JSON quirks, TLS fingerprinting, sessions, or pagination internals.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles KonbiniAPI the way a machine reads it — 95 machine-readable artifacts across 2 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 — KonbiniAPI scores 59.3/100 (developing), with a separate agent-readiness read of 48/100 (agent ready). 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 KonbiniAPI
Each block below is one kind of artifact we hold for KonbiniAPI. 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 2
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.
KonbiniAPI Instagram API
Instagram data endpoints
KonbiniAPI TikTok API
TikTok data endpoints
Open Collections 1
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).
KonbiniAPI
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.
Rate 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.
Konbiniapi 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.
Konbiniapi Finops
FINOPSSemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Konbiniapi Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
KonbiniAPI API Rules
SPECTRALKonbiniAPI API Rules
SPECTRALJSON Schema 26
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
InstagramAttachment
JSON SCHEMAInstagramAudio
JSON SCHEMAInstagramCarouselItem
JSON SCHEMAInstagramComment
JSON SCHEMAInstagramEmbeddedUser
JSON SCHEMAInstagramHighlight
JSON SCHEMAInstagramImage
JSON SCHEMAInstagramImageWithDimensions
JSON SCHEMAInstagramLink
JSON SCHEMAInstagramLocation
JSON SCHEMAInstagramPost
JSON SCHEMAInstagramStoryItem
JSON SCHEMAInstagramTag
JSON SCHEMATikTokAudio
JSON SCHEMATikTokCollection
JSON SCHEMATikTokComment
JSON SCHEMATikTokEmbeddedUser
JSON SCHEMATikTokImage
JSON SCHEMATikTokLink
JSON SCHEMATikTokLiveStreamAttachment
JSON SCHEMATikTokStoryAttachment
JSON SCHEMATikTokStory
JSON SCHEMATikTokTag
JSON SCHEMATikTokVideoAttachmentHeaders
JSON SCHEMATikTokVideoAttachment
JSON SCHEMATikTokVideo
JSON SCHEMAScroll within the panel for all 26 ·
JSON Structure 26
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Konbiniapi Instagram Attachment Structure
JSON STRUCTUREKonbiniapi Instagram Audio Structure
JSON STRUCTUREKonbiniapi Instagram Carousel Item Structure
JSON STRUCTUREKonbiniapi Instagram Comment Structure
JSON STRUCTUREKonbiniapi Instagram Embedded User Structure
JSON STRUCTUREKonbiniapi Instagram Highlight Structure
JSON STRUCTUREKonbiniapi Instagram Image Structure
JSON STRUCTUREKonbiniapi Instagram Image With Dimensions Structure
JSON STRUCTUREKonbiniapi Instagram Link Structure
JSON STRUCTUREKonbiniapi Instagram Location Structure
JSON STRUCTUREKonbiniapi Instagram Post Structure
JSON STRUCTUREKonbiniapi Instagram Story Item Structure
JSON STRUCTUREKonbiniapi Instagram Tag Structure
JSON STRUCTUREKonbiniapi Tik Tok Audio Structure
JSON STRUCTUREKonbiniapi Tik Tok Collection Structure
JSON STRUCTUREKonbiniapi Tik Tok Comment Structure
JSON STRUCTUREKonbiniapi Tik Tok Embedded User Structure
JSON STRUCTUREKonbiniapi Tik Tok Image Structure
JSON STRUCTUREKonbiniapi Tik Tok Link Structure
JSON STRUCTUREKonbiniapi Tik Tok Live Stream Attachment Structure
JSON STRUCTUREKonbiniapi Tik Tok Story Attachment Structure
JSON STRUCTUREKonbiniapi Tik Tok Story Structure
JSON STRUCTUREKonbiniapi Tik Tok Tag Structure
JSON STRUCTUREKonbiniapi Tik Tok Video Attachment Headers Structure
JSON STRUCTUREKonbiniapi Tik Tok Video Attachment Structure
JSON STRUCTUREKonbiniapi Tik Tok Video Structure
JSON STRUCTUREScroll within the panel for all 26 ·
Examples 30
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Scroll within the panel for all 30 ·
Security Posture 3
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 KonbiniAPI — 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.
Get Started 2
Portal, sign-up, and the first successful call
Documentation 1
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 4
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
← All providers · Data indexed from github.com/api-evangelist/konbiniapi · machine-readable index on apis.io