AiCred Verified
AiCred Verified gives talent platforms a portable, revocable, assessment-backed AI credential they can trust and actually use.
It turns AI skill from a marketing claim into a product signal. And because the integration is lean, it has a real chance of getting implemented instead of getting stuck in roadmap purgatory.

Verified Signal
Assessment-backed, not self-reported
The credential comes from a completed conversational assessment, not polished profile copy.
Portable
API + official card kit
Partners can fetch the credential or drop in the official card without inventing the presentation layer from scratch.
User Control
Explicit consent and immediate revocation
The user approves the connection first, and they can shut it off later from their AiCred dashboard.
What It Is
Two parts: a verified credential API and an official presentation layer.
AiCred Verified is built to be simple to understand and realistic to implement. Partners get a clean machine-readable credential plus an official UI layer that makes the signal immediately legible.
Verified API
Partners exchange a consent code for a credential token, then fetch a structured, read-only credential payload.
Official Card Kit
The drop-in Verified Card makes the credential recognizable, legible, and fast to ship inside a real product.
User-Controlled Sharing
The user approves the connection, and they can revoke access later from their AiCred dashboard at any time.
This is what turns AI skill from a claim into a signal.
If you run a talent marketplace, creator network, expert directory, or hiring workflow, AiCred Verified gives you something most platforms do not have: a clean way to show that a person's AI capability was actually evaluated.
How It Works
Simple consent for the user. Clean integration for the partner.
The product is intentionally lean. No giant export. No messy sync project. Just a verified credential that can move between systems cleanly.
01
User connects AiCred
A partner platform sends the user to AiCred for a simple human approval flow.
02
AiCred issues consent code
After approval, AiCred redirects back to the partner callback with a short-lived code.
03
Partner exchanges for token
The partner swaps that code for a persistent credential token using the Verified API.
04
Credential renders anywhere
The partner fetches the verified credential server-side and renders the official card or their own UI.
Portable credential, explicit consent, immediate revocation.
That is the real shape of the product. It is partner-friendly without taking control away from the user, and it is structured enough to be useful without turning into a raw account-data dump.
What It Looks Like
The credential is designed to be instantly legible.
The official card gives partners a presentation layer that feels professional, recognizable, and easy to ship. The API is useful on its own. The card is what makes the signal readable.
Detailed Card · Profile View
For profile pages, talent records, and places where the credential should carry real weight.

Compact Card
For search results, list views, and fast-scan profile headers.

In Progress
A graceful state when the user exists but has not completed the assessment yet.

Revoked
A clean fallback when the user revokes access later.

Data Shape
Enough structure to be useful. Enough restraint to be trusted.
AiCred Verified is deliberately not a raw data export. It gives partner platforms a credible public-facing credential without exposing the user’s full account history.
What partners can show
- Display name and professional title
- Stable credential identifier and public profile URL
- Overall score, Velocity signal, and assessment date
- Component scores for AI Delegation & Direction, Technical & Model Literacy, Verification & Judgment, Practical Implementation, Workflow, Skills, Agents & Harnesses
- Section number, section name, section score, summary, strengths, and growth areas
- Competitive context and critical bottleneck
- Assessment type, evaluation type, methodology, API version, retrieval time, and cache TTL
What stays out
- Email address
- Transcripts
- Raw conversation history
- Learning plans
- Exercises
- Quizzes
- Webhook payloads
- Bulk export surfaces
- Score mutation APIs
Where It Fits
Built for products that need a better AI trust layer.
If your platform helps people get discovered, hired, matched, or trusted, this is where AiCred Verified becomes valuable.
Talent marketplaces
Hiring platforms
Expert networks
Professional directories
Creator ecosystems
Operator communities
Why the official card matters
The API is useful. The card is what makes the credential legible. It gives hiring managers, buyers, and collaborators a recognizable visual cue that this was verified, not self-declared.
It also lowers adoption friction. A partner developer can copy one file, pass data, and ship a professional result quickly instead of inventing the whole presentation layer from scratch.
Integration surface
- 01Get an AiCred API key
- 02Add the callback route
- 03Store one credential token per connected user
- 04Fetch the verified credential server-side
- 05Render the official card or map the payload into your own UI
API key → callback route → credential token → server-side fetch → official card