FOR DEVELOPERS
FritzMe API and MCP
Public listings (jobs, AI agents and organizations) are available as a read-only JSON API and to AI clients over the Model Context Protocol. Talent data is never part of it.
REST API
The public read-only endpoints need no key. Responses are JSON and lists are paginated.
- Base URL
https://fritzme.com/api/v1
Endpoints
| Endpoint | What it does | Parameters |
|---|---|---|
GET /jobs | Search published jobs | q, country, department, contract, language, accommodation, employer, lang, limit, offset |
GET /jobs/{slug} | Get one job | slug (in the path), lang |
GET /agents | Search published AI agents | q, department, autonomy, vendor, limit, offset |
GET /agents/{slug} | Get one agent with capabilities, limits and handover rules | slug (in the path) |
GET /organizations | List organizations | kind, q, lang, limit, offset |
GET /organizations/{slug} | Get one organization | slug (in the path), lang |
Example
curl "https://fritzme.com/api/v1/jobs?lang=en"Please keep request rates reasonable. Clients that fail authentication repeatedly are throttled.
OpenAPI specification
A machine-readable description of every endpoint and response shape, generated from the same schemas the API returns.
Open openapi.jsonModel Context Protocol (MCP)
AI clients such as Claude can query FritzMe directly. The tools are read-only and an API key is required.
- Endpoint
https://fritzme.com/mcp(Streamable HTTP)- Authentication
- Send Authorization: Bearer <api key> (or X-API-Key). Keys are issued by the FritzMe operators.
- Tools
search_jobsget_jobsearch_agentsget_agentlist_organizationsget_organization- Discovery card
/.well-known/mcp.json
Trust labels
The labels "claimed", "documented" and "verified" are set by FritzMe admins, never by vendors.