kgen.io valid

KGeN

KGeN collects data from verified humans across the Global South

For agents: KGeN collects verified-human data from the Global South for physical AI and LLM training, and runs a contributor community with a $KGEN token.

verified human dataphysical aillm training dataglobal southkgen token

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-20T23:17:40.810Z. Cached copy · Source on kgen.io

# KGeN

> KGeN collects data from verified humans across the Global South
> to train Physical AI and large language models. Labs pay for multimodal human data that
> cannot be synthesised — voice and audio, image, video, text, sensor and interaction data,
> captured from real, verified contributors. A share of that revenue automatically retires
> the $KGEN token on-chain, so every AI lab contract reduces supply.

KGeN operates a network of verified contributors organised by local operators called Clan Chiefs.
Verification is proof-of-human (VeriFi), with provenance recorded on-chain contributor by contributor.

## Pages

- [KGeN — Verified-Human Data for Physical AI & LLMs](https://kgen.io/): What KGeN collects, why frontier labs and robotics teams pay for it, the diversity/verification/multimodal case, industry use cases, and the public proof sources.
- [$KGEN — Revenue Becomes Tokenomics](https://kgen.io/kgen): The supply-reduction mechanism, the genesis burn, the live supply monitor, the on-chain retirement ledger (date, amount, source contract, transaction hash), third-party audit and attestation links, and quarterly financial reports.
- [KGeN Community — Clan Chiefs](https://kgen.io/community): How the contributor network is organised, what a Clan Chief does, the three operator types (engagement, commerce, field ops), contributor stories, and how to join a clan.

## What KGeN is

- A verified-human data network for Physical AI and LLM training, focused on the Global South.
- Data types: voice and ambient audio, image, video, text, sensor and interaction data.
- Collection settings include real environments — manufacturing, residential, retail, hospitality and construction sites.
- Contributors are verified as human before their data counts; verification is on-chain and per-contributor.
- Local operators ("Clan Chiefs") mobilise contributors, secure permissions for commercial collection in their own region, and build coverage where a lab needs it.
- KGeN also operates consumer-facing products: KGeN Engage (quests, leaderboards, rewards) at engage.kgen.io, KStore, and developer docs at docs.kgen.io.
- Investors include Jump Capital, Accel, Prosus Ventures, Aptos and Polygon.

## How the $KGEN token works

- AI labs contract KGeN for data. A share of the contribution margin is used to buy and retire $KGEN on-chain, automatically and perpetually.
- The retirement is structural, not discretionary: supply reduction follows revenue.
- A genesis burn retired 22,000,000 $KGEN at launch (a fixed, historical figure — approximately 10% of circulating supply at that time), at zero cash cost, from unclaimed pools. It was a retirement, not a sale, and the retired tokens have no owner.
- Every retirement is published in a public ledger with its timestamp, amount, source contract and transaction hash.
- Token roles: rewards, settlement and reputation seeding. Demand comes from buy-and-remove (supply reduction) and buy-and-hold (staking). Staking carries gove
…

Related sites

Other listed sites in AI and machine learning. See the whole category →

Machine-readable: GET /v1/resolve?q=kgen.io · GET /v1/domain/kgen.io · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for kgen.io:
1. POST https://agentwebmap.com/v1/sites/kgen.io/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://kgen.io/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/kgen.io/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/kgen.io).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.