Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Flex API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fflexonthejob.com%2Fflexonthejob" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fflexonthejob.com%2Fflexonthejob" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
What an agent can do with Flex API.
Track catalog items with price tiers, barcodes, and per-location stock levels
Create an invoice from a job or from explicit lines, then mark it sent, paid, or void
Record a payment or apply store credit against an invoice
Move stock with purchase orders, sales orders, transfers, and reorder points
Organise items with categories, inherited properties, and custom fields
GET STARTED
Keep customers, their job-site locations, and vendors up to date
Subscribe to webhooks that fire when Flex records change
Patterns agents use Flex API for, with concrete tasks.
★ Agent-Driven Billing
An AI agent connected through Jentic turns a finished job into money owed by creating a draft invoice from the job, refreshing its total from the job's unbilled amount, and marking it sent, so a business owner never has to assemble an invoice by hand. Because Flex keeps payments on the invoice, the agent can later record a payment or apply store credit in the same flow.
Create a draft invoice from this job, refresh its total, mark it sent, and record the customer's payment when it arrives
Inventory and Reorder Automation
A stock workflow reads each item's on-hand quantity by location, compares it to its reorder point, and raises a purchase order for anything running low, so a shop keeps shelves stocked without a manual count. Flex tracks per-location stock and supports transfers, so the workflow can also move stock between sites instead of buying more.
List items below their reorder point and create a purchase order to restock each one from its preferred vendor
Catalog Maintenance
A catalog workflow keeps items, categories, and custom properties consistent by creating categories, assigning items to them, and setting several custom-field values at once, so a growing product list stays organised and searchable. Categories inherit properties from their parents, so the workflow can define a field once and have it apply down the tree.
Create a category, assign the matching items to it, and set their shared custom-field values in one pass
169 endpoints — the flex api manages the inventory, catalog, and billing of a field-service or trade business, so an application can track stock across locations, build invoices from jobs, and keep customers and vendors in sync.
METHOD
PATH
DESCRIPTION
/api/v1/items
List catalog items with pricing and on-hand stock
/api/v1/items/{id}
Get one item with properties, price tiers, barcodes, and per-location stock
/api/v1/invoices
List invoice headers
/api/v1/invoices/from-job
Create a draft invoice for a job
/api/v1/invoices/{id}/payments
Record a payment or apply store credit to an invoice
/api/v1/customers
List customers
/api/v1/customers
Create a customer
/api/v1/items
List catalog items with pricing and on-hand stock
/api/v1/items/{id}
Get one item with properties, price tiers, barcodes, and per-location stock
/api/v1/invoices
List invoice headers
/api/v1/invoices/from-job
Create a draft invoice for a job
/api/v1/invoices/{id}/payments
Record a payment or apply store credit to an invoice
/api/v1/customers
List customers
/api/v1/customers
Create a customer
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Flex API by hand means creating a scoped bearer token in Flex, learning which permission each endpoint needs, and choosing between the production and sandbox hosts. Through Jentic you install once, import Flex from the API Directory, store the token once, and your agent calls it.
Permission scoping
You choose which operations your agent may call, so you can allow listing items and drafting invoices while leaving destructive ones like deleting a customer or voiding an invoice out. Rules bound which operations run, so the agent works the catalog and billing you grant and nothing else.
Credential isolation
Your Flex 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.
Intent-based discovery
Agents search Jentic by intent such as 'create an invoice from a job' or 'list low-stock items', and Jentic returns the matching Flex operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using Flex API through Jentic.
Is there a Flex MCP server?
You don't need an MCP server to give your agent the Flex API. Jentic connects it directly from the API Directory: import it, store your token once, and your agent can track inventory, build invoices, and manage customers straight away, with no extra server to run and no tool definitions sitting in the agent's context.
Can I limit what my agent is allowed to do with the Flex API?
Yes. Write a rule that allows only the operations the agent needs, such as listing items and creating draft invoices, and leave deletions and void actions out. Every call the agent makes is logged, so you can see exactly which invoices and stock changes it touched.
What authentication does the Flex API use?
The Flex API authenticates with a bearer token per its OpenAPI spec: an API key created by an organization administrator inside Flex and sent in the Authorization header, prefixed flx_live_. The key is scoped to one organization and granted a subset of permissions. Through Jentic the token is stored encrypted by your own instance and injected at call time, so it never appears in the agent's prompt or logs.
Can I create an invoice from a job with the Flex API?
Yes. One operation creates a draft invoice directly from a job, another recomputes its total from the job's current unbilled amount, and a third marks it sent. From there the agent can record payments, apply store credit, or void the invoice as needed.
What are the rate limits for the Flex API?
The OpenAPI spec does not state request rate limits for the Flex API. For current limits and fair-use guidance, check the provider documentation at https://app.flexonthejob.com.
How do I bill a job through Jentic?
Import the Flex API from the Jentic API Directory, then have your agent issue a request such as 'create an invoice for this completed job'. Jentic matches the intent to the invoice-from-job operation and returns its input schema so the agent builds the correct request, with your stored token injected at call time. To run it on your own infrastructure, install Jentic One from its GitHub repo.
For Agents
Track catalog items and per-location stock, build and settle invoices, manage customers, vendors, and purchase orders, and subscribe to change webhooks in Flex. Authenticates with a bearer token created inside Flex.
Use for: List the catalog items with their on-hand stock by location, Create a draft invoice from a completed job, Record a payment against an open invoice, Find all customers created this month
Not supported: Does not process card payments, run payroll, or manage a public storefront. Use for field-service inventory, catalog, and invoicing only.
The Flex API manages the inventory, catalog, and billing of a field-service or trade business, so an application can track stock across locations, build invoices from jobs, and keep customers and vendors in sync. You maintain catalog items with price tiers, barcodes, and per-location stock, organise them with categories and custom properties, and move stock with purchase orders, sales orders, transfers, and reorder points. Invoices can be created standalone or drawn from a job, then marked sent, paid, or voided, and webhooks notify your systems when records change.
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>