Editorial questions and corrections
Email [email protected] with the page title or address and the passage you are asking about. For a correction, describe what appears inaccurate and include a primary source when one is available. Precise context makes a technical issue easier to evaluate.
Suggestions are welcome across process mapping, automation, batch images and files, local model workloads, frontier AI evaluation, API design, and self-hosted operations. A concrete workflow or failure case is particularly useful when proposing a future guide.
What to include in a technical question
Describe the intended outcome, the stage where work becomes unclear, and any relevant constraints. Distinguish a proposed architecture from a system already in production. A small, synthetic example is usually more useful than a large collection of unstructured logs.
Do not send API keys, passwords, private customer records, confidential documents, or unrestricted production access. Remove identifying details from examples before sharing them. This mailbox is for editorial communication, not a secure intake channel for processing business data.
Looking for implementation material?
The reference documentation contains an example job contract, lifecycle, and batch manifest. The Process Playbook provides longer explanations of design choices and operational tradeoffs. For a subject overview, use the topic links in the navigation.
ProcessAPI.com publishes guides and examples rather than operating a hosted API service. Account, billing, or live-service issues for another provider should be directed to that provider's own support channel. No contact form or account sign-up is required to use this site.