KOLens Authenticity API
The Authenticity API from KOLens — 2 operation(s) for authenticity.
The Authenticity API from KOLens — 2 operation(s) for authenticity.
Every API here is available over the APIs.io API and to AI agents over MCP.
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
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.curl "https://apis.io/api/v1/apis/kolens-ai:kolens-ai-authenticity-api"
curl "https://apis.io/api/v1/apis?limit=25"
Calls without X-API-Key need no key. Calls with it need a paid plan — get a 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. By signing up you are subscribing to the APIs.io and API Evangelist newsletters — you can unsubscribe from any issue. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
openapi: 3.2.0
info:
title: KOLens Authenticity API
description: KOLens — TikTok KOL Intelligence API. Search keywords, extract KOL profiles, collect contact info, export reports.
version: 1.0.0
tags:
- name: Authenticity
paths:
/api/kols/{username}/authenticity:
get:
tags:
- Authenticity
summary: Authenticity score (cached, daily) for one KOL
description: 'Return the composite authenticity score + per-signal breakdown.
Cached daily per (username, platform, ALGORITHM_VERSION). The
first call of the day computes and persists; subsequent calls
return the cached row instantly.
Returns 404 only when the author doesn''t exist in our DB at all.
Accounts that exist but lack data return a row with
``confidence=''insufficient_data''`` — caller renders a grey badge.'
operationId: get_authenticity_score_api_kols__username__authenticity_get
security:
- HTTPBearer: []
parameters:
- name: username
in: path
required: true
schema:
type: string
title: Username
- name: platform
in: query
required: false
schema:
type: string
description: Platform identifier
default: tiktok
title: Platform
description: Platform identifier
- name: refresh
in: query
required: false
schema:
type: boolean
description: If true, recompute even if a same-day cache row exists.
default: false
title: Refresh
description: If true, recompute even if a same-day cache row exists.
responses:
'200':
description: Successful Response
content:
application/json:
schema:
$ref: '#/components/schemas/AuthenticityScoreOut'
'422':
description: Validation Error
content:
application/json:
schema:
$ref: '#/components/schemas/HTTPValidationError'
/api/kols/{username}/authenticity/dispute:
post:
tags:
- Authenticity
summary: Mark an authenticity score as contested
description: 'Stamp the latest score row as disputed by the caller''s workspace.
Required for legal cover (PM revision): every authenticity score
must be challengeable on day 1. We don''t *retract* the score on
dispute — we just attach the operator''s note + workspace id so the
UI can render "Contested by Acme on 2026-04-01" alongside the
badge, and downstream consumers (filters, alerts) can skip
disputed scores if they want.
Workspace resolution is best-effort: if the caller has no
workspace binding the dispute still records (with NULL workspace),
so legacy CLI keys can flag scores too.'
operationId: dispute_authenticity_score_api_kols__username__authenticity_dispute_post
security:
- HTTPBearer: []
parameters:
- name: username
in: path
required: true
schema:
type: string
title: Username
- name: platform
in: query
required: false
schema:
type: string
default: tiktok
title: Platform
- name: x-kolens-user-id
in: header
required: false
schema:
anyOf:
- type: string
- type: 'null'
title: X-Kolens-User-Id
- name: x-kolens-workspace-id
in: header
required: false
schema:
anyOf:
- type: string
- type: 'null'
title: X-Kolens-Workspace-Id
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/DisputeIn'
responses:
'200':
description: Successful Response
content:
application/json:
schema:
$ref: '#/components/schemas/AuthenticityScoreOut'
'422':
description: Validation Error
content:
application/json:
schema:
$ref: '#/components/schemas/HTTPValidationError'
components:
schemas:
AuthenticityScoreOut:
properties:
username:
type: string
title: Username
platform:
type: string
title: Platform
algorithm_version:
type: string
title: Algorithm Version
snapshot_date:
type: string
title: Snapshot Date
score:
type: integer
maximum: 100.0
minimum: 0.0
title: Score
confidence:
type: string
title: Confidence
signals:
additionalProperties:
$ref: '#/components/schemas/SignalDetailOut'
type: object
title: Signals
disputed_at:
anyOf:
- type: string
- type: 'null'
title: Disputed At
disputed_by_workspace_id:
anyOf:
- type: string
- type: 'null'
title: Disputed By Workspace Id
dispute_note:
anyOf:
- type: string
- type: 'null'
title: Dispute Note
computed_at:
type: string
title: Computed At
summary:
type: string
title: Summary
type: object
required:
- username
- platform
- algorithm_version
- snapshot_date
- score
- confidence
- signals
- computed_at
- summary
title: AuthenticityScoreOut
description: 'Composite authenticity score + per-signal breakdown.
Note on copy: every user-visible string here says "authenticity"
or "signal" — never "fake" / "bot" / "fraud". The PM revision is
firm on this: the score lives in legal grey area and the wording
is the cover.'
ValidationError:
properties:
loc:
items:
anyOf:
- type: string
- type: integer
type: array
title: Location
msg:
type: string
title: Message
type:
type: string
title: Error Type
type: object
required:
- loc
- msg
- type
title: ValidationError
SignalDetailOut:
properties:
score:
anyOf:
- type: integer
- type: 'null'
title: Score
weight:
type: number
title: Weight
note:
type: string
title: Note
type: object
required:
- weight
- note
title: SignalDetailOut
description: One sub-signal's payload — score + weight + 1-line human note.
HTTPValidationError:
properties:
detail:
items:
$ref: '#/components/schemas/ValidationError'
type: array
title: Detail
type: object
title: HTTPValidationError
DisputeIn:
properties:
note:
anyOf:
- type: string
maxLength: 2000
- type: 'null'
title: Note
description: Optional explanation of why this score is contested.
type: object
title: DisputeIn
securitySchemes:
HTTPBearer:
type: http
scheme: bearer