Two focused tools.
One clear review step.

Technical documentation for CropCheck and Service Closeout PDF. These deterministic tools process supplied images or structured notes. They do not use generative AI, certify facts or make decisions for you.

Integration evaluation. The authenticated API has passed synthetic end-to-end checks. This does not mean either tool is approved or available inside Muse. Use fictional or non-sensitive inputs only while provider file handling and user authorization are being verified.

CropCheck

Turn one supplied image into up to four exact-size Fit or Cover PNGs. Choose the focal point for Cover, inspect every preview, then export the PNGs and manifest in a ZIP. It does not detect subjects or invent missing image content.

Send base64 image bytes and target dimensions to POST /api/crop/prepare.
Display the returned PNG data URLs and warnings for the person to review.
Resend the same image/settings and returned approvalDigest to POST /api/crop/export.
Decode zipBase64 locally and offer the archive for download. Check that preview and exported bytes agree.

CropCheck OpenAPI specification

Service Closeout PDF

Prepare a readable service report from a job scope, supplied source notes, findings with exact excerpts, and next actions. Review the PDF page previews before export. It is a document-formatting tool, not an invoice, electronic signature, job-completion certification or assessment of whether a finding is true.

Send the structured data object to POST /api/report/prepare.
Display every returned previewPages image and the report for review.
Resend the same input and record.approval_digest as approvalDigest to POST /api/report/export.
Decode pdfBase64 and offer the PDF for download.

Full supplied notes are processed as input, even when output includes only selected excerpts. Do not include confidential notes or sensitive records. includePrivateSources: true is rejected by this hosted adapter.

Service Closeout OpenAPI specification

Connect and handle files

Base URL: https://muse-api.naumio.com. Use a dedicated credential in Authorization: Bearer <integration credential> and exactly Content-Type: application/json. Credentials are exchanged separately through an agreed secure channel. No sign-up, OAuth or paid plan is implemented by these endpoints.

Files travel inline as base64 or data URLs. There are no persistent download URLs, remote URL fetches, attachment IDs, stored jobs, delete endpoints or delivery receipts. The caller must decode the bytes and safely present them as files. Muse's support for this representation, its size limits and its secure credential channel still require provider confirmation.

Preparing is already processing and disclosure. A prepare response contains usable PNG/PDF bytes. A matching digest proves content consistency, not identity or consent. Obtain permission before supplying input and separate confirmation before sending any result to someone else. Neither endpoint sends email or uploads results elsewhere.

Limits and recovery

Boundary	Current behavior
Crop request	14,000,000 encoded request bytes; one image, at most four targets. See schema for pixel and format limits.
Report request	100,000 encoded request bytes; see schema for field lengths and supported characters.
Capacity	One active origin job at a time. Busy requests return 429. There is no queue or guaranteed service time.
Authentication	Missing or invalid credentials return 401. Unknown routes, query strings and unsupported methods return 404.
Availability	Invalid media/type, limits or unavailable upstream processing can return 4xx/5xx. No availability or response-time guarantee.

If an input changes, prepare again and review the new result. A timeout or interrupted request is not proof of success. Show errors clearly; do not silently approve, send or retry an uncertain export.

Data and support

Hosted calls pass through Cloudflare to Naumio's processing server. The application is configured for transient processing without a persistent customer-payload store. Operational infrastructure, temporary memory and provider handling mean this is not a promise of zero retention or secure erasure. Keep downloaded files under your own control. Read the privacy notice and terms before integration.