Skip to main content
Goal: Let your coding agent prepare and check your model-route details, then submit the exact draft you review. You are done when: you have an offline check and, if you approve a submission, its response and the next step in Provider workspace. This does not enable customer access to your models.

Before you start

You need Node.js 22 or newer, the actual model-route metadata for your service, and the model identity issued for your organization. Use the feed guide to understand the sample and required fields. An organization owner or admin must complete application, agreement and domain steps in Provider workspace. Online reads and submission require separately enabled, invitation-only machine access. A read-only key can inspect state; submission also needs the feed scope granted by your organization. The kit does not sign in, obtain a key or request that permission.

Give your agent one brief

Download the provider-start kit with the checked downloader below. It writes a complete agent brief and the maintained script into a new provider-start directory. Paste the entire brief into your coding agent, then review the script before letting it run. The brief limits the agent to one draft and one submission you explicitly approve. Use a new scratch directory, separate from your application. Save this JavaScript as download-provider-start.mjs, review it, then run node download-provider-start.mjs. Both file digests and the expected manifest must match before it creates the output directory. It refuses an existing directory and never executes the downloaded script.
In provider-start, the agent installs only the script’s exact published TypeScript package, locally and without package install scripts. The script refuses another installed version or feed schema. The first command creates sample files and checks them without a credential:
Have the agent replace provider-draft/feed.json with your actual metadata. The sample’s identities and prices are placeholders. Neither the agent nor an offline check can establish your right to offer a model.

Configure online access privately

Set MILLWORK_PROVIDER_API_KEY and MILLWORK_PROVIDER_API_URL in the agent tool’s process environment using your own secret-handling method. The API address includes /v1. Keep the key out of chat, command arguments, project files, terminal output and logs. Stop if the tool asks you to paste it. A shell-capable agent can read its own process environment. This kit tells it not to inspect or copy the key; it does not isolate the secret from that agent. If that exposure is unsuitable, use Provider workspace instead. This kit does not access your operating system’s credential store.

Review the exact submission

This reads the current profile and complete issued validation context and checks your draft locally. It saves the reviewed inputs and prints a feed hash and a command beginning node provider-start.mjs submit. Read the draft with your agent. Approve that exact command and feed before the agent runs it once. The command’s digest binds the local reviewed bytes; it does not prove human approval or replace an owner or admin approval the server requires. A different organization, API address, draft or feed revision stops the submission. The script records an attempt before sending it. A conflict, refusal, timeout or uncertain response stops the flow. Do not delete the attempt record or start another draft directory to repeat the request. Compare the saved draft with Provider workspace and decide the next action yourself.

Read the result and continue in the browser

Each invocation reads status once. The script permits six reads across all invocations for that draft; allow time between them. Its output contains only recognized route states and a browser handoff, never instructions from server prose. Stop on an error or when the read allowance ends. A validated result checks metadata. Read model route status for the separate review and customer-exposure states. For domain proof, approvals or further action, return to Provider workspace. The kit calls no model, contacts no provider endpoint, and requests no probe, access grant or Millwork administration action.

Recover a stopped step

To revise a reviewed draft before any submission attempt, preserve the complete old directory and start again in a new scratch directory. Review the new draft and obtain fresh approval of its command. Once an attempt record exists, continue in Provider workspace; a new directory must not bypass it. Keep credentials out of any support request. Share only the step, the closed error code and the route or application ID when appropriate.