Mertzcrew API

Name: Mertzcrew API
Brand: Mertzcrew API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentHR recruitingEmployee Managementbearer89 EndpointsREST

For Agents

Manage AV freelancer crews, projects, assignments, contracts, and payments through the Mertzcrew bearer-authenticated 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.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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

GET STARTED

Start building with Mertzcrew API

Explore with Jentic

View OpenAPI Document

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.

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

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Mertzcrew login credentials are stored in the Jentic vault. Agents call the API with a scoped Jentic token; Jentic mints the bearer token at the gateway, so raw login credentials and bearer tokens never enter the agent context.

Intent-based discovery

Agents search Jentic with intents like 'list unpaid Mertzcrew projects' or 'broadcast a crew assignment' and receive the matching dashboard, project, or assignment operation with its parameter schema.

Time to first call

Direct Mertzcrew integration: 1-2 weeks to cover login, dashboards, projects, assignments, and payment release. Through Jentic: a few hours per workflow.

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 at https://app.jentic.com/sign-up.

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.