Humans & profiles
How human profiles, services, and search work.
Profiles
Every human on kriti has a public profile at /{locale}/humans/{slug} with headline, bio, city, languages, hourly rate, skills, and bookable services. Profiles carry schema.org ProfilePage/Person JSON-LD including makesOffer with INR PriceSpecification — machine-readable prices, always.
Verification ladder: email verified (level 0 and 1 today), then phone OTP, then ID verification, then kriti-vetted. The level is shown on the profile and returned in the .md rendition and the API.
Markdown rendition
Append .md to any profile URL — or send Accept: text/markdown — and you get a clean markdown document: identity, verification level, city, languages, rate, skills, about, and services with prices. Built for agents that don't want to parse HTML.
Services
A service is a fixed, bookable offer ("Retail store audit with photo report — ₹800"). A human's first service is reviewed by the kriti team before going live (usually within a day); later services publish instantly. Every service belongs to a category and optionally a city.
Search
The browse view (/en/browse) and GET /api/v1/humans support:
| Parameter | Meaning |
|---|---|
q | Full-text over headline and bio (PostgreSQL FTS), fuzzy match on headline, name match |
city | City slug (e.g. pune, mumbai) |
category | Category slug — filters to humans with a live service in it |
City hubs (/en/cities/{slug}) and category hubs (/en/categories/{slug}) list humans with an FAQ; thin hubs are noindex until they have three or more humans.