Komi

Komi is a link-in-bio service aimed at the higher end of the creator market, which shows in who uses it: pages tend to belong to talent with real commercial operations behind them. Note the URL shape — Komi puts the handle in a subdomain ({handle}.komi.io) rather than a path.

Base URL: /v1/komi/...

Getting started

One endpoint, one parameter, 1 credit. Pass the full page URL.

curl "https://www.socialcrawl.dev/v1/komi/page?url=https://kimkardashian.komi.io/" \
  -H "x-api-key: $SOCIALCRAWL_API_KEY"

What comes back

GET /v1/komi/page returns the page's display name, bio and avatar, plus every link on the page with its title and destination URL. The link list is the valuable part: it is a creator's own declaration of where their audience should go next, which usually includes the shops they sell through, the affiliate networks they run, the newsletter they own, and the social accounts they actually maintain rather than the ones they merely registered.

Two ways that is used in practice. For creator vetting, the destinations reveal commercial relationships that a profile bio does not — an affiliate subdomain or a brand-specific landing page is a disclosed partnership. For cross-platform resolution, the outbound social links turn one handle into the creator's full account set, which you can then feed into the per-platform profile endpoints.

Endpoints

1 endpoint available.

Read this before you build

Destinations are as-published, not resolved. A link that points at a shortener or a tracking redirect comes back as that URL. Follow it yourself if you need the final destination, and expect UTM parameters to survive.

One page per call, and no discovery. There is no way to search Komi pages or list a creator's page from their social handle — you need the page URL. It usually comes from a social profile's bio link (author.ext.bio_link where a platform exposes one) or from the bio text itself.

Each link-in-bio service has its own endpoint. Linktree, lnk.bio, Linkme and Pillar are separate paths that return the same shape, so one parser handles all of them; only the base path changes.

Notes

• The endpoint uses GET with query parameters
• Authentication via the x-api-key header
• Responses follow the unified SocialCrawl schema
• A page with no links returns an empty link list rather than an error
• The URL must be the public page URL, including the scheme