We don't bolt a chatbot onto Flex and call it AI. We make Flex easy for your tools to operate — an MCP server, a documented API, signed webhooks — and we're honest about what's shipped, what's next, and what we do with your data.
on the jobapp.flexonthejob.com/mcp — 16 tools and 2 resources covering customers, jobs, schedule, items and invoices.A three-truck HVAC shop doesn't want to evaluate our model choice; it wants "what's on Truck 3?" answered in whatever assistant it already uses. Standards — OpenAPI, MCP, webhooks — get you that without a lock-in, and let you switch agents without switching inventory systems.
When we do add first-party assistance inside Flex it will be opt-in, per organization, with the provider named on this page.
Agents and scripts are first-class users of the API and MCP server. The same terms apply as for a person, plus these specifics.
429 and Retry-After. The limits are generous for a business; they exist so one runaway loop can't slow down the crew in the field.Idempotency-Key. It's required on writes precisely so an agent's retry never creates a second invoice./docs, /openapi/v1.json, /llms.txt and /llms-full.txt need no key and aren't rate-limited. Crawl them.Your data → your agent. When you connect an assistant over MCP, whatever it reads goes to the provider you chose under your agreement with them. Flex is not a party to that. Prefer read-only keys for exploration and add write permissions deliberately.
Our staff. Flex support accesses an organization's data only to resolve a request you made, and that access is by named, individually-accountable administrator accounts.
Aggregate product metrics (how many jobs are created per day across all customers, which pages are slow) are used to run the service. They are never per-customer benchmarks and never leave us.
Full detail in the privacy policy and on the security page.
Dates are targets, not promises; order is the commitment. Anything here can be pulled forward by a customer who needs it.
Customers, jobs, schedule, items, invoices. API keys with per-key permissions and rate limits, idempotent writes, ETags, RFC 7807 errors, OpenAPI + Scalar reference + llms.txt.
Eight signed events with retry and delivery log. Streamable-HTTP MCP server with 16 tools and 2 resources under the same keys.
Phone and tablet app for the office side, with camera barcode scanning.
CSV on every list endpoint (Accept: text/csv), updatedSince filters for delta pulls, and a documented recipe for a scheduled nightly export driven by webhooks.
transfer.completed, inventory.low_stock, item.updated and invoice.sent. Additive — existing subscriptions keep working unchanged.
Triggers from the existing webhooks, actions from the existing writes, so non-developers can wire Flex to their books, their forms and their calendar.
Invoices and payments pushed automatically, replacing today's CSV export.
Two-factor authentication, then single sign-on with Google and Microsoft accounts.
The technician-side phone app: today's job, parts used, photos and signatures, working offline and syncing back.
Opt-in, per organization, provider named here, built on the same MCP tools any external agent uses — so it can never do more than a key can.
Additive changes are listed here as they ship; anything deprecated gets a dated notice at least 12 months ahead. Subscribe by watching llms.txt — it carries the same notices.
/api, /docs, /openapi.json and /developers on either host now redirect to the right place. robots.txt and security.txt published on both hosts./mcp (16 tools, 2 resources). Webhooks: job.created, job.status_changed, job.scheduled, job.assigned, job.completed, invoice.created, invoice.paid, customer.created; X-Flex-Signature HMAC-SHA256./modules, /customers (read, create, update, locations), /items, /invoices (read, from-job, mark-sent), /jobs (read, create, status, assignees, reschedule, cancel), /schedule, /schedule-groups, /users. API keys with per-key permissions and rate limits; cursor paging; ETags; Idempotency-Key required on writes; RFC 7807 errors; /docs, /openapi/v1.json, /llms.txt, /llms-full.txt.Tell us what you're building. Customers set the order.