cv-builder

name	cv-builder
description	Creates professional CVs with permanent URLs at talent.de. Supports PDF export, multiple templates, 4 skill types, and human-in-the-loop review. Free API for AI agents — basic use without API key, full features with Access-ID. Use when the user wants to create, build, or generate a CV or resume.
homepage	https://www.talent.de
license	Free-to-use
compatibility	Requires HTTP client and network access.
env_vars	{"TALENT_ACCESS_ID":{"required":false,"sensitive":true,"description":"Optional for basic CV creation (3/day without ID). Required for callbacks and higher rate limits."}}
metadata	{"openclaw":{"emoji":"📄"},"talent":{"category":"cv-studio","version":"5.2.2","api_base":"https://www.talent.de/api","credentials":{"access_id":{"required":false,"env_var":"TALENT_ACCESS_ID","note":"Optional for basic CV creation (3/day without ID). Required for callbacks and higher rate limits."}}}}

CV Builder — Create CVs via API

Create a CV with a permanent URL at talent.de. The user chooses their personal URL slug and template design via a review page. CVs are permanent — URLs never expire.

Agent Guidelines

HITL is required. You MUST include either "prefer_hitl": true (human review) or "skip_hitl": true (direct creation). Omitting both returns a 400 error. If a human is present, ALWAYS use "prefer_hitl": true — this lets the user choose their URL slug, pick a template, review the data, and approve before publishing. Use "skip_hitl": true only for automated pipelines with no human in the loop.

Data principle: Only use data the requestor has explicitly provided or approved in this conversation. Do not extract personal information from unrelated system contexts or other sessions.

Before sending: Present a brief summary to the requestor — name, title, email — and ask "Send it? Or should I change anything?"

Claim token: Treat like a password. Share only with the requestor — anyone with the token can claim CV ownership. Never share with third parties.

User Communication

What to say at each step

Step	Say to the user
Before API call	"Let me set up your CV. I just need a few details."
Slug selection (review_url received)	"Choose your personal URL — this is where your CV will live: [link]"
Template selection	"Almost done! Pick a design for your CV: [link]"
Approval	"Your CV is ready for review. Take a look and approve it: [link]"
After final 201	"Your CV is live! Here's your link: {url}"

Quick Start

1. Collect: name, title, email (minimum 4 fields)
2. POST /api/agent/cv-simple with "prefer_hitl": true and the data
3. Present the review_url to the user (they pick slug, template, review data)
4. Poll poll_url for completion, continue through steps
5. After final approval: present the live CV URL and claim token

Example (with HITL — recommended)

POST https://www.talent.de/api/agent/cv-simple
Content-Type: application/json

{
  "prefer_hitl": true,
  "cv_data": {
    "firstName": "Alex",
    "lastName": "Johnson",
    "title": "Software Engineer",
    "email": "[e-mail]"
  }
}

Response (202 — human review required):

{
  "status": "human_input_required",
  "message": "Please confirm: is this CV for you?",
  "hitl": {
    "case_id": "review_a7f3b2c8d9e1f0g4",
    "review_url": "https://www.talent.de/en/hitl/review/review_a7f3b2c8d9e1f0g4?token=abc123...",
    "poll_url": "https://www.talent.de/api/hitl/cases/review_a7f3b2c8d9e1f0g4/status",
    "type": "confirmation",
    "inline_actions": ["confirm", "cancel"],
    "timeout": "24h"
  }
}

Present the review URL to the user:

I've prepared your CV. Please review and make your choices here: Review your CV You'll pick your personal URL slug, template design, and approve the final result.

Then poll poll_url until completed, and continue through steps with hitl_continue_case_id. After all steps (confirmation, data review, slug selection, template selection, approval), the final POST returns 201 with the live URL.

Full HITL protocol with all steps, inline submit, edit cycles, and escalation: reference/hitl.md

HITL Multi-Step Flow

The user goes through up to 5 review steps. The agent loops: present review URL, poll, continue.

Step 1: Confirmation  →  "For whom is this CV?"
Step 2: Data Review   →  "Are these details correct?"
Step 3: Slug          →  Human picks personal URL slug (e.g. pro, dev, 007)
Step 4: Template      →  Human picks template design
Step 5: Approval      →  Human reviews final CV draft

Each step returns 202. After the user decides, continue:

POST https://www.talent.de/api/agent/cv-simple
Content-Type: application/json

{
  "prefer_hitl": true,
  "hitl_continue_case_id": "review_a7f3b2c8d9e1f0g4",
  "cv_data": { ... }
}

Steps are skipped when you already provide the value:

• Include slug → slug selection step is skipped
• Include template_id → template selection step is skipped
• Include both → only confirmation, data review, and approval remain

After the final approval step, submit with hitl_approved_case_id to publish:

POST https://www.talent.de/api/agent/cv-simple
Content-Type: application/json

{
  "hitl_approved_case_id": "review_final_case_id"
}

Response (201):

{
  "success": true,
  "url": "https://www.talent.de/dev/alex-johnson",
  "cv_id": "cv_abc123",
  "claim_token": "claim_xyz789",
  "template_id": "007"
}

Present the result:

Your CV is live: talent.de/dev/alex-johnson

To claim ownership, visit: talent.de/claim/claim_xyz789 Keep this token safe — it never expires.

Direct Creation (No Human Present)

For fully automated pipelines, batch operations, or when the user explicitly says "just create it" — set "skip_hitl": true:

POST https://www.talent.de/api/agent/cv-simple
Content-Type: application/json

{
  "skip_hitl": true,
  "cv_data": {
    "firstName": "Alex",
    "lastName": "Johnson",
    "title": "Software Engineer",
    "email": "[e-mail]"
  }
}

Response (201):

{
  "success": true,
  "url": "https://www.talent.de/pro/alex-johnson",
  "cv_id": "cv_abc123",
  "claim_token": "claim_xyz789",
  "template_id": "018",
  "hitl_skipped": true,
  "auto_fixes": []
}

In direct mode, the server auto-assigns slug (pro by default) and template (018 Amber Horizon). The user has no choice. Use this only when no human needs to review.

You MUST choose one: "prefer_hitl": true or "skip_hitl": true. Omitting both returns a 400 error.

All fields beyond the 4 required ones are optional. Omit what you don't have — don't send empty arrays.

PDF Export

Get a downloadable PDF alongside the CV. Three visual themes available:

Theme	Style	Best for
classic	Single-column, red accent (default)	Traditional industries
modern	Two-column sidebar, blue accent	Tech & creative roles
minimal	Monochrome, generous whitespace	Executive & senior roles

Option A: Inline with CV creation

Add "include_pdf": true to your request. The response includes a base64-encoded PDF:

POST https://www.talent.de/api/agent/cv-simple
Content-Type: application/json

{
  "prefer_hitl": true,
  "include_pdf": true,
  "pdf_format": "A4",
  "pdf_theme": "modern",
  "cv_data": {
    "firstName": "Alex",
    "lastName": "Johnson",
    "title": "Software Engineer",
    "email": "[e-mail]"
  }
}

Response includes a pdf object:

{
  "success": true,
  "url": "https://www.talent.de/pro/alex-johnson",
  "cv_id": "cv_abc123",
  "claim_token": "claim_xyz789",
  "pdf": {
    "base64": "JVBERi0xLjQK...",
    "size_bytes": 6559,
    "generation_ms": 226,
    "format": "A4"
  }
}

Option B: Generate PDF for existing CV

POST https://www.talent.de/api/agent/cv/pdf
Content-Type: application/json

{
  "cv_id": "cv_abc123",
  "format": "A4",
  "theme": "minimal"
}

Returns the PDF binary directly (Content-Type: application/pdf). Format options: A4 (default), LETTER. Theme options: classic (default), modern, minimal.

PDF generation takes ~200ms (no headless browser needed).

Server-Side Intelligence

You do not need to check slug availability or validate data — the server handles it:

• Slug uniqueness: A slug is NOT globally unique — it's unique per person. pro/thomas-mueller and pro/anna-schmidt can coexist. Only the combination of slug + firstName + lastName is reserved. That's why the server needs the name first to check availability.
• Slug auto-selection: If omitted (and no HITL), the server picks pro. If that slug is already in use for this person's name, it tries the next available slug automatically. In HITL mode, the human can choose their slug interactively. Popular picks: 007 · dev · pro · ceo · gtr · zen · 404. Full list: GET /api/public/slugs
• Template default: 018 (Amber Horizon) if omitted.
• Date normalization: 2024 becomes 2024-01-01, 2024-03 becomes 2024-03-01.
• Language levels: Normalized to CEFR (NATIVE, C2, C1, B2, B1, A2, A1).
• Human-readable errors: If something goes wrong, the response explains what to fix in plain English.
• Auto-fix summary: The auto_fixes array tells you what the server adjusted (e.g. "Slug 'pro' is already in use for this name, using 'dev' instead").

Skills Use 4 Arrays

• hardSkills — technical skills, optional level 1-5
• softSkills — name only
• toolSkills — name only
• languages — with CEFR level: NATIVE, C2, C1, B2, B1, A2, A1

Do not use a generic skills array — it will be ignored.

Guardrails

• Rate limits (with Access-ID): 50 CVs/day, 100 job searches/day
• Rate limits (without Access-ID): 3 CVs/day per IP
• Never auto-commit without requestor approval
• Claim tokens are permanent — treat as passwords

References

• CV Data Reference: All fields and constraints for cv_data
• Templates: Full template catalog with previews
• HITL Protocol: Human-in-the-loop review flow (all steps, inline submit, edit cycles)
• Access System: Rate limits and Access-ID registration
• Error Codes: Error reference and troubleshooting
• Privacy: Data handling and GDPR compliance