Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the MatchMates External API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmatchmates.de%2Fmatchmates" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmatchmates.de%2Fmatchmates" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
What an agent can do with MatchMates External API.
Search candidate records against a set of criteria
Create a new candidate in the recruiting pipeline
Fully replace an existing candidate record by id
Delete a candidate by id
Keep an external system in sync with MatchMates candidate data
GET STARTED
Patterns agents use MatchMates External API for, with concrete tasks.
★ Candidate sourcing for an AI agent
Give an AI agent the ability to add and find candidates in a MatchMates pipeline without hand-wiring the X-API-Key header. Through Jentic the agent discovers the candidate search and create operations by intent and calls them with a validated input schema, so a sourcing assistant can create candidate records from applications it processes and search the pipeline for existing matches before adding duplicates.
Search the pipeline for a candidate by email, and if none exists, create a new candidate record from the parsed application data
Candidate data sync
Keep candidate records in MatchMates aligned with an external system by creating new candidates, fully replacing changed records, and deleting ones that are no longer relevant. This backs a nightly sync or a webhook-driven pipeline that mirrors candidate data from an applicant source into MatchMates.
Replace an existing candidate record with an updated version pulled from the source system and confirm the update
Candidate search and screening
Search the candidate pool against criteria to build shortlists for a role. A screening tool can query the pipeline for candidates matching skills, location, or other attributes and hand the results to a recruiter or an agent for the next step.
Search for candidates matching a role's required skills and return a shortlist for a recruiter to review
4 endpoints — the matchmates external api manages candidate records in a recruiting workflow.
METHOD
PATH
DESCRIPTION
/candidates/search
Search candidates against criteria
/candidates
Create a candidate
/candidates/{candidateId}
Fully replace a candidate record
/candidates/{candidateId}
Delete a candidate
/candidates/search
Search candidates against criteria
/candidates
Create a candidate
/candidates/{candidateId}
Fully replace a candidate record
/candidates/{candidateId}
Delete a candidate
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the MatchMates External API by hand means setting the `X-API-Key` header on every request and coordinating search-before-create logic to avoid duplicate candidates. Through Jentic you install once, import MatchMates from the API Directory, store the key once, and your agent calls the candidate operations directly.
Permission scoping
You choose the operations your agent may call, so you can allow candidate search and creation while withholding replacement and deletion. That way a sourcing assistant can grow the pipeline without the ability to overwrite or remove existing records.
Credential isolation
Your MatchMates API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'search candidates' or 'create a candidate', and Jentic returns the matching MatchMates operation with its input schema so the agent calls the right endpoint without reading the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using MatchMates External API through Jentic.
What authentication does the MatchMates External API use?
The MatchMates External API authenticates with an API key sent in the `X-API-Key` request header, per its OpenAPI spec. You obtain the key from your MatchMates company settings. Through Jentic the key is stored once and injected at call time, so your agent never places it in the header itself.
What can I do with the MatchMates External API?
You can search candidate records against criteria, create a new candidate, fully replace an existing candidate record, and delete a candidate by id. It is a focused candidate-management surface for keeping an external system in sync with your MatchMates recruiting pipeline.
Is there a MatchMates MCP server?
You do not need an MCP server to give your agent the MatchMates External API. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent calls the candidate operations on demand. Nothing extra runs, and no server tool definitions sit in the agent's context between calls.
Can I limit what my agent is allowed to do with the MatchMates External API?
Yes. Write a rule that allows only the operations you need, such as searching and creating candidates while leaving out deletion, so the agent can grow the pipeline but cannot remove records. Every call it makes is logged, so you can audit exactly which operations ran.
What are the rate limits for the MatchMates External API?
The OpenAPI spec does not specify rate limits. Any limits are set by MatchMates for your account, so check your MatchMates account settings or contact their support for the quota that applies to your key.
How do I add a candidate with MatchMates through Jentic?
Search Jentic for 'create a candidate' to find the create operation, which adds a candidate record to your pipeline, and pair it with the search operation to check for an existing match first. Jentic returns each operation with its input schema so your agent calls it correctly. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Know of an official OpenAPI document? Contribute it →
For Agents
Search candidate records, create new candidates, fully replace an existing candidate, and delete a candidate by id. A focused surface for syncing candidate data with a MatchMates recruiting pipeline.
Use for: I need to search for candidates matching a set of criteria, Create a new candidate record, Update a candidate's details by replacing the record, Delete a candidate that is no longer relevant
Not supported: Manages candidate records only; does not post jobs, schedule interviews, or run the full hiring pipeline through this surface. Use for candidate search and record management.
The MatchMates External API manages candidate records in a recruiting workflow. It searches candidates against criteria, creates a new candidate, fully replaces an existing candidate record, and deletes a candidate by id. It is a focused candidate-management surface for keeping an external system in sync with a MatchMates recruiting pipeline rather than a full applicant-tracking suite.