Everything people ask about HuMetric.

HuMetric is a consent-first talent platform. Each professional chooses one audience for their profile: public web, authorized recruiter pool, or private. Publishing is explicit, and email and phone remain private.

LinkedIn is a closed network that AI agents cannot query directly; HuMetric is built to be queried. Authorized profiles are machine-readable as JSON and Markdown and through MCP, while each person chooses the audience for their profile.

The person chooses the audience: public web, authorized recruiter pool, or private. A profile remains a private draft until the person explicitly publishes it. The selected audience is enforced across the website and search surfaces.

No. Email and phone are hidden by default and no publicity setting can expose them. What a profile can publish instead is a contact-willingness signal — open to offers, passive, or not looking — so recruiters know whether to approach without receiving your address.

Every public profile read and every API result is written to a consent log recording who asked, which fields were returned, and for what purpose. Consent is revocable: withdrawing it removes the profile from the directory, the sitemap and the API.

Submitting and publishing a profile is free for professionals. Recruiter access requires an authorized workspace and follows its entitlement and disclosure quotas.

Use the MCP Streamable HTTP endpoint at /api/mcp with an OAuth 2.0 access token. After login, candidate tools operate only on the authenticated user's own profile, while recruiter tools require an authorized workspace. MCP does not provide anonymous public viewing. The search and fetch tools cover only people who published their profile and enabled AI-agent discovery.

Each public profile embeds schema.org ProfilePage JSON-LD whose mainEntity is a Person, and the same consented projection is available as JSON at /api/v1/profiles/{slug} and as Markdown with ?format=markdown. Site-wide guidance for agents lives at /llms.txt.

Yes. Being agent-readable is the product, so robots.txt explicitly welcomes GPTBot, ClaudeBot, PerplexityBot, Google-Extended and other named AI crawlers. Only ingestion endpoints and management routes are disallowed.

Agents must not infer fields a person has hidden, re-identify an anonymous profile, or contact someone who has marked themselves not looking. A public profile is permission to read stated facts, not to reconstruct an identity or make unsupported claims.

Every result carries query-aware highlights — the specific supporting chunks and the source fields behind the match — so an agent can cite what a claim rests on instead of re-reading a whole profile.

Publish it somewhere a machine can read on the public web. Submitting a profile to HuMetric serves server-rendered HTML, schema.org JSON-LD, JSON and Markdown at one public URL. MCP is a separate OAuth-protected interface: candidate tools are own-profile only, and recruiter tools require an authorized workspace.

It is parsed into structured fields that you review and confirm before anything is published. Thirty days after you confirm, the uploaded file and the extracted raw text are deleted automatically, and the structured profile you approved is what remains.

Yes. Choose Private to keep it out of public and recruiter search, or choose the public web or authorized recruiter pool audience when you are ready. Email and phone stay hidden at every level.

Set your contact status. A profile publishes one of three signals — open to offers, passive, or not looking — so recruiters and agents know whether to approach, without your email or phone number being exposed to them.

Delete it from your account. That removes the profile from the public directory, the sitemap and the API, and the public profile API is cached for only sixty seconds, so a deleted profile stops being served within a minute.