Identity & context inputs
Personalization on Kariant is not a black box. Four identity surfaces — Account, Profile, Organization, and the Kontext context node — supply the data points that power matching on both sides of the marketplace. This page lists exactly what each contributes.
Kariant Account — the identity spinelink
One account, created once at hq.kariant.app, carries every role — buyer, partner, advertiser — across every Kariant surface. It contributes the sign-in identity and verified contact points, the roles held per surface, language and region defaults, and the security context (sessions, providers).
For buyers this means continuity: saved comparisons, shortlists, and chat threads follow them across sessions and devices. For partners it sets the currency context and runs your console, wallet, and every role from one login. At the agentic tier it is also the permission boundary: agents act strictly within what the account’s scopes allow.
Kariant Profile — the personlink
The master profile at /profile updates in real time across the platform: professional identity (role, function, seniority), interests and followed categories, engagement history (views, compares, saves, chats), and communication preferences.
This is what makes the same search return different, better-fitting orders for a marketing lead and a CTO. For partners, profile completeness earns Koins, and your professional context personalizes your console. At Kariant AI, matching reads profile role and interests to weight intent; at Agentic AI, agents tailor conversation depth to the person they are talking to.
Kariant Organization — the companylink
The organization record at /organization carries the company-level identity: the globally-unique @handle, industry, company size, region, billing currency (₹ India / $ Global), teams, and subsidiaries.
It powers B2B matching at the company level — recommendations weight what organizations of that industry, size, and region actually adopt, not just what one person clicked. For partners it sets billing region and contextual pricing, carries the verified identity behind listings, and scopes team access. At the agentic tier, agents reason about company-level fit before citing or contacting: an enterprise brief and a solo-founder brief produce different shortlists.
Kontext — the context nodelink
The Kontext profile at /klick/kontext/profile is the declared context node: your ideal customer profile (target industries, sizes, regions, buyer roles), your offering context, the goals the AI should optimize for, and voice/tone constraints for generated content.
It is the single highest-leverage input a partner controls. It grounds lead-scoring reasons, the sales agent’s outreach drafts, intelligence prompts, and recommendation fit. At Basic it informs structured matching; at Kariant AI every AI run optimizes against it; at Agentic AI, agents read it before every run. Ten minutes spent sharpening your Kontext upgrades every AI surface you touch.
- check_circleAccount → identity, roles, language/region, permission scopes
- check_circleProfile → role, interests, engagement history, preferences
- check_circleOrganization → @handle, industry, size, region, currency, teams
- check_circleKontext → ICP, offering context, goals, tone — read before every AI/agent run
Frequently asked questions
Can buyers see my Kontext ICP?expand_more
No. Your Kontext profile is private to your account. Buyers only experience its effects — better-fitting matches, sharper agent conversations.
What should I fill in first?expand_more
Organization (it sets your billing region and pricing) and then Kontext (it grounds every AI feature). Profile and account settings refine from there.