canonical: https://jentic.com/apis/mold.ninja/mold-ninja # Mold Ninja API Jentic publishes the only available OpenAPI specification for Mold Ninja API, keeping it validated and agent-ready. Mold Ninja is a field-service management platform built for mold inspection and remediation businesses, covering customer records, estimates, inspections, scheduling, referral partners, and technician dispatch. The API spans 78 endpoints across user authentication, customer CRM, estimate generation, inspection attachments and PDF delivery, calendar scheduling, and referral tracking. It targets remediation contractors who need a single back-office API for the full job lifecycle from lead intake to scheduled inspection. ## For AI agents Manage mold inspection and remediation operations including customers, estimates, inspections, schedules, referral partners, and technicians via a single field-service API. ## Scope Does not handle payment processing, marketing campaigns, or accounting reconciliation - use for mold inspection job, customer, and schedule management only. ## Capabilities - Manage customer records, contact info, and addresses for inspection clients - Create estimates, attach customer details, and update estimate notes through the job lifecycle - Capture inspections with attachments and email PDF reports to customers - Schedule inspections, filter the calendar, and assign technicians to jobs - Track referral partners and log referral events for partner-driven leads ## Use cases ### Mold Inspection Job Lifecycle Run the full inspection job lifecycle by creating a customer, generating an estimate, scheduling the inspection, capturing field data with attachments, and emailing the final PDF report to the client. Mold Ninja's tagged endpoints map directly to each stage so a remediation contractor's office software can drive the job from lead to completion. Suitable for small-to-mid mold remediation businesses replacing a stack of spreadsheets and email threads with a single API. Example prompt: Call POST `/user/createCustomer`, POST `/user/createEstimates`, POST `/user/creatSchedule`, POST `/user/createInspection`, then POST `/user/sendInspectionPDFToCustomer` to complete a job. ### Technician Dispatch and Calendar Filtering Assign jobs to technicians and pull a filtered calendar view to balance workloads across the team. The schedule endpoints expose calendar filters and update operations, while user endpoints retrieve the technician roster including pagination via limit and skip parameters. Useful for dispatch managers running daily route planning instead of working off whiteboards or printed schedules. Example prompt: Call POST `/user/getTechinicianList/{limit}/{skip}` to fetch technicians, then PUT `/user/calanderFilters` to apply a filter and PUT `/user/updateShedule` to reassign a job. ### Referral Partner Management Track referral partners (insurance adjusters, plumbers, real estate agents) and log every event tied to a partner-sourced lead. The referral endpoints support partner creation, event logging, and listing, so a remediation business can attribute revenue accurately and prioritise high-value partnerships. Practical for owners running monthly referral commission reports. Example prompt: Call POST `/user/createReferalPartner` with a new partner's details, then PUT `/user/addEvents` to log each referral event. ### Agent-Driven Job Scheduling AI agents handling inbound customer calls or messages call Mold Ninja through Jentic to create customer records and book inspections without holding the bearer token in their context. Jentic's spec is the only structured definition for this API, so agents that depend on schema-driven tool selection can only use Mold Ninja through Jentic. Example prompt: Search Jentic for 'schedule a mold inspection', load POST `/user/creatSchedule`, and execute with the customer ID and time slot. ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/user/login` | Authenticate a user and receive a bearer token | | POST | `/user/createCustomer` | Create a new customer record | | POST | `/user/createEstimates` | Create an estimate for a customer | | POST | `/user/createInspection` | Create an inspection record | | POST | `/user/sendInspectionPDFToCustomer` | Email the inspection PDF to the customer | | POST | `/user/creatSchedule` | Schedule an inspection on a technician's calendar | | POST | `/user/createReferalPartner` | Register a new referral partner | | POST | `/user/inviteUser` | Invite a technician to the organisation | ## Key resources - **Authentication** — Sign up, log in, and reset passwords via OTP for user accounts - **Customer** — Create and manage customer records, contact info, and addresses - **Estimates** — Create, list, and update inspection estimates linked to customers - **Inspection** — Create inspections, attach files, and send inspection PDFs to customers - **Schedule** — Create and update job schedules with calendar filtering - **Referral** — Manage referral partners and log referral events - **Tags** — Create, search, and delete tags applied across records - **User** — Invite technicians, manage organisation users, and retrieve technician lists ## Why Jentic - **Setup:** Wiring the Mold Ninja API by hand means logging in for a bearer token, then coding the customer, estimate, inspection, and scheduling calls across dozens of operations yourself. Through Jentic you install once, import the Mold Ninja API from the API Directory, store the token once, and your agent calls it. - **Permission scoping:** Mold Ninja carries the customer, estimate, and inspection target in the request body rather than as a path resource, so you limit the agent to the operations it needs, such as creating an inspection or a schedule. You choose the operations it may call, so one like inviting a user is not included unless you add it. - **Credential handling:** Your Mold Ninja token 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. - **Discovery method:** Agents search Jentic by intent such as 'schedule a mold inspection' or 'create a customer', and Jentic returns the matching Mold Ninja operation with its parameter schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Stripe API** — Payment processing platform for charging customers after inspection completion - **Twilio Messaging API** — Programmable SMS gateway for sending appointment reminders to inspection customers - **SendGrid Email Activity API** — Transactional email delivery and tracking that complements Mold Ninja's PDF report emails ## FAQ ### Why is there no official OpenAPI spec for Mold Ninja API? Mold Ninja does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Mold Ninja 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 Mold Ninja API use? Mold Ninja uses HTTP Bearer authentication. Obtain a token through POST `/user/login`, then send it as Authorization: Bearer on subsequent requests. Through Jentic, the token is held in the encrypted credential vault and injected at request time so it never enters agent context. ### Can I generate and send inspection reports with the Mold Ninja API? Yes. Create the inspection record with POST `/user/createInspection`, attach files with POST `/user/addInspectionAttachment`, and email the final PDF to the customer with POST `/user/sendInspectionPDFToCustomer.` The full inspection-to-report pipeline runs through three calls. ### What are the rate limits for the Mold Ninja API? Mold Ninja does not document rate limits in this OpenAPI spec. As a back-office field-service API, throughput is generally bounded by the per-organisation account tier rather than fixed numeric limits. Confirm current limits with the Mold Ninja team before running bulk operations. ### How do I schedule an inspection through Jentic? Run pip install jentic, search for 'schedule a mold inspection', load POST `/user/creatSchedule`, and execute with the customer ID, technician ID, and time slot. Jentic returns the scheduled job ID for downstream confirmation flows. ### Does Mold Ninja support referral partner tracking? Yes. POST `/user/createReferalPartner` registers a new partner, GET `/user/getReferalListing` lists existing partners, and PUT `/user/addEvents` logs each referral event tied to a partner. This supports commission reporting and source attribution for partner-driven leads. ### Can I limit what my agent is allowed to do with the Mold Ninja API? Yes. Because you run Jentic One yourself, your own rules decide which Mold Ninja operations the agent may call and which credentials it may use. Mold Ninja carries the customer, estimate, and inspection target in the request body rather than in the path, so you scope the agent to just the operations it needs, such as POST `/user/createInspection` and POST `/user/creatSchedule.` An operation like POST `/user/inviteUser` stays off limits unless you explicitly add it.