Mertzcrew API
Agent-ready OpenAPI document · curated by JenticHR recruitingEmployee Managementbearer89 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Manage AV freelancer crews, projects, assignments, contracts, and payments through the Mertzcrew bearer-authenticated API.
Use for: I need to broadcast a project to qualified contractors, List unpaid projects on the Mertzcrew dashboard, Find assignments that have not been accepted by their start date, Get the contractor roles available for a client
Not supported: Does not handle payroll tax filing, general accounting, or job-board posting - use for AV freelancer crew booking, project lifecycle, and assignment management in Mertzcrew only.
Jentic publishes the only available OpenAPI specification for Mertzcrew API, keeping it validated and agent-ready. Mertzcrew is a workforce platform purpose-built for audio-visual production companies that book live-event freelancers. The API covers the full operational surface: contractor profiles and skills, project and assignment lifecycle, broadcast and offer flows, contracts, insurance documents, payment release, and dashboards for unpaid, unapproved, and broadcast work. With 89 endpoints across reference data, projects, assignments, contractors, and reporting, it exposes the operations needed to drive crew bookings end-to-end from a single API.
Install Jentic One Beta
Connect the Mertzcrew API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Mertzcrew 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.
1
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%2Fmertzcrew.com%2Fmertzcrew" | sh2
Step 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%2Fmertzcrew.com%2Fmertzcrew" | 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.
Capabilities
What an agent can do with Mertzcrew API.
Authenticate AV company users and retrieve the current authenticated profile for session management
List reference data (countries, states, contractor roles, skills, project classifications) needed to populate booking forms
Run dashboards covering unpaid projects, unaccepted assignments, broadcast jobs, and assignments needing attention
Create and update projects, project notes, and project reports across the booking lifecycle
Manage contractor assignments including offers, acceptance, and broadcast distribution to qualified crew
Issue contracts and capture insurance documentation tied to contractor assignments
Drive payment release workflows for completed assignments using the project and assignment payment endpoints
Use Cases
Patterns agents use Mertzcrew API for, with concrete tasks.
★ Crew Broadcast and Offer
Booking coordinators at AV companies can broadcast an open project to qualified contractors and track responses through the dashboard endpoints. GET /dashboard/projects/broadcast surfaces broadcast projects, while assignment endpoints capture offers and acceptances. This shortens the booking cycle for short-notice live events where reaching a wide pool quickly matters.
Call GET /dashboard/projects/broadcast to list broadcast projects and pull the assignment-needs-attention list with GET /dashboard/assignments/needAttention to follow up on stale offers.
Operations Dashboards
Operations leads can drive a single dashboard from Mertzcrew's purpose-built endpoints: GET /dashboard/projects/unpaid, GET /dashboard/projects/unapprovedByPaymentReleaseDate, GET /dashboard/assignments/unacceptedByStartDate, and GET /dashboard/assignments/needAttention. Together they surface the four operational queues an AV booking team works through each day.
Call the four /dashboard endpoints in parallel and render them as the four queues in the morning operations stand-up dashboard.
Contractor Profile Setup
Onboarding new freelancers requires populating dropdowns for skills, contractor roles, and pay rules. Mertzcrew exposes /skills/all, /contractor_roles, /contractor_role_departments, and /pay_rules/{clientId} to drive these forms with the values configured for the booking company. This keeps contractor profiles consistent with how the company structures its crew taxonomy.
Call GET /skills/all and GET /contractor_roles, then render them as the skill and role pickers in the new contractor onboarding form.
Project Reports and Notes
Producers wrapping a live event can capture post-show notes and reports against the project record using the Project Notes and Project Reports endpoints. These flow back into the dashboards and provide an audit trail for client invoicing and contractor performance reviews, supporting both archive and reporting workflows.
Call the project-notes and project-reports endpoints to record the wrap-up summary and any contractor flags after the event.
Agent-Built AV Booking Workflows
An AI agent embedded in an AV company's operations can take instructions like 'broadcast Friday's gig to qualified A2s' or 'show me unpaid projects from last month'. Through Jentic the agent finds the matching Mertzcrew operation, loads its schema, and executes the call without writing custom Mertzcrew client code or handling raw bearer tokens.
Search Jentic for 'list unpaid Mertzcrew projects', load GET /dashboard/projects/unpaid, and execute it to surface the queue for the operations lead.
Key Endpoints
89 endpoints — jentic publishes the only available openapi specification for mertzcrew api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
POST
/login
Authenticate user and obtain a bearer token
GET
/authenticated-user
Get the current authenticated user
GET
/dashboard/projects/unpaid
List unpaid projects
GET
/dashboard/projects/broadcast
List broadcast projects
GET
/dashboard/assignments/needAttention
List assignments needing attention
GET
/skills/all
List all contractor skills
GET
/contractor_roles
List contractor roles
GET
/pay_rules/{clientId}
List client pay rules
POST
/login
Authenticate user and obtain a bearer token
GET
/authenticated-user
Get the current authenticated user
GET
/dashboard/projects/unpaid
List unpaid projects
GET
/dashboard/projects/broadcast
List broadcast projects
GET
/dashboard/assignments/needAttention
List assignments needing attention
GET
/skills/all
List all contractor skills
GET
/contractor_roles
List contractor roles
GET
/pay_rules/{clientId}
List client pay rules
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Mertzcrew API by hand means calling /login for a bearer token, refreshing it against app.mertzcrew.com, and coding the dashboard, project, and assignment requests yourself. Through Jentic you install once, import the Mertzcrew API from the API Directory, store the login credentials once, and your agent calls it.
Permission scoping
The Mertzcrew endpoints in this scope are read-only listings of projects, assignments, skills, and pay rules, with the client id appearing in the path only on the pay-rules lookup, so scope your agent by operation: limit it to the dashboard and reference reads it needs and leave out anything else. This keeps the agent to viewing crew and project data.
Credential isolation
Your Mertzcrew login credentials are stored once, encrypted, by your own Jentic One instance, which mints the bearer token at execution time. Neither the credentials nor the token enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'list unpaid Mertzcrew projects' or 'find assignments needing attention', and Jentic returns the matching dashboard, project, or assignment operation with its parameter schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Mertzcrew API through Jentic.
Why is there no official OpenAPI spec for Mertzcrew API?
Mertzcrew does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Mertzcrew API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.
What authentication does the Mertzcrew API use?
Mertzcrew uses bearer-token authentication. Clients call POST /login with credentials to obtain the token, then send it in the Authorization header on subsequent requests. Through Jentic, the Mertzcrew login credentials live in the vault and the agent receives a scoped Jentic token.
Can I broadcast a project to multiple contractors with the Mertzcrew API?
Yes. Broadcast projects appear in GET /dashboard/projects/broadcast and the assignment endpoints handle the resulting offers and acceptances. Broadcasting is the standard pattern for short-notice live events where the booking team wants to reach all qualified crew at once.
What are the rate limits for the Mertzcrew API?
The OpenAPI spec does not declare explicit rate limits. Mertzcrew applies tenant-level throttling on the production endpoint; reporting jobs that paginate the dashboard or contractor lists should sequence calls and back off on 429 responses rather than running unthrottled fan-out.
How do I list unpaid projects through Jentic?
Install the SDK with pip install jentic, search for 'list unpaid Mertzcrew projects', load the GET /dashboard/projects/unpaid operation, and execute it. Jentic attaches the bearer token and returns the queue.
Does the Mertzcrew API expose pay rules per client?
Yes. GET /pay_rules/{clientId} returns the configured pay rules for a specific client, which is the data driving rate calculations on assignments. Combine it with /contractor_roles to render fully populated booking forms.
Can I limit what my agent is allowed to do with the Mertzcrew API?
Yes. Jentic One is self-hosted by you, so your own rules decide which Mertzcrew operations and credentials the agent may use. Because the operations here are read-only listings of projects, assignments, skills, and pay rules, you can restrict the agent to just the dashboard and reference reads it needs, such as GET /dashboard/projects/unpaid, GET /skills/all, or GET /pay_rules/{clientId}, and leave out everything else. That keeps the agent to viewing crew and project data without touching operations you have not allowed.
GET STARTED