Agent-ready OpenAPI document · curated by JenticProductivityTask Managementbearer50 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Manage Checkmob clients, work orders, services, questionnaires, and users so an agent can dispatch field jobs, pull checklist answers, and sync field data with other systems.
Use for: Create a new Checkmob client record, List all open work orders for a specific client, Pull the checklist answers captured for a service today, Find all questionnaires defined for our account
Not supported: Does not handle payment processing, payroll, or marketing campaigns - use for managing field service clients, work orders, checklists, and users only.
Jentic publishes the only available OpenAPI specification for Checkmob API, keeping it validated and agent-ready. Checkmob is a Brazil-headquartered field service management platform used to dispatch technicians, track work orders, and capture data from the field on mobile devices. The API spans 50 endpoints across clients, addresses, work orders, services, checklists, questionnaires, users, segments, and custom fields, with a token-exchange flow for authentication. It is suited to teams integrating field operations with their CRM, billing, or BI stack.
Install Jentic One Beta
Connect the Checkmob API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Checkmob 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.
1
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%2Fcheckmob.com%2Fcheckmob" | sh2
Step 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%2Fcheckmob.com%2Fcheckmob" | 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.
Capabilities
What an agent can do with Checkmob API.
Create, list, update, activate, and deactivate client records
Create and look up work orders dispatched to field technicians
List services and checklist questionnaires tied to a client
Pull checklist answers captured by technicians on site
Provision users and assign them to groups or segments
Manage segments and link or unlink clients from each segment
Define custom fields and service types for the account
Use Cases
Patterns agents use Checkmob API for, with concrete tasks.
★ Field Work Order Dispatch
Mirror work orders between an internal scheduling system and Checkmob so technicians see assignments on their mobile app. Listing work orders via /api/OrdemServico/List shows current state, and /api/OrdemServico/Post creates new orders when scheduling produces a job. Useful for service businesses already running a homegrown scheduler.
Create a work order via /api/OrdemServico/Post for client_id 42 with service_type 'maintenance' scheduled for 2026-06-15.
Checklist Answer Sync
Pull checklist answers captured by field technicians into a BI tool or QA dashboard. /api/RespostasQuestionario/List returns the answers for a given questionnaire and date range, which a scheduled job can normalise into a warehouse. Useful for compliance reviews or customer-facing service reports.
Pull /api/RespostasQuestionario/List for questionnaire_id 7 over the last 7 days and return the count of completed responses.
Client and Segment Management
Provision new clients in Checkmob from a CRM and slot them into the right segment so the field team picks up the relationship correctly. /api/Cliente/Post creates the client, /api/Endereco/Post adds an address, and /api/SegmentoClientes/Add links them to one or more segments for routing.
Create a client via /api/Cliente/Post named 'Acme Co', add an address, and link them to segment_id 3.
AI Agent for Field Service Operations
An autonomous agent receives natural-language requests from a dispatcher ('schedule a maintenance visit for Acme tomorrow', 'how many open jobs does Maria have?') and translates them into Checkmob calls through Jentic. The bearer token never enters the agent's prompt - Jentic handles token exchange and injection.
Through Jentic, search 'create a work order', load the schema for /api/OrdemServico/Post, and execute with the requested client and service type.
Key Endpoints
50 endpoints — jentic publishes the only available openapi specification for checkmob api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
POST
/api/Cliente/Post
Create a client
POST
/api/Cliente/List
List clients
POST
/api/OrdemServico/Post
Create a work order
POST
/api/OrdemServico/List
List work orders
POST
/api/RespostasQuestionario/List
Pull checklist answers
POST
/api/Usuario/Post
Create a user
GET
/token
Request an access token
POST
/api/Cliente/Post
Create a client
POST
/api/Cliente/List
List clients
POST
/api/OrdemServico/Post
Create a work order
POST
/api/OrdemServico/List
List work orders
POST
/api/RespostasQuestionario/List
Pull checklist answers
POST
/api/Usuario/Post
Create a user
GET
/token
Request an access token
Jentic AI Readiness Score
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.
C
Checkmob API
- AI-Aware (B)67/100
87
Foundational Compliance63
Developer Experience & Jentic Compatibility47
AI-Readiness & Agent Experience94
Agent Usability60
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
87
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: ASignals: 4
97%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
50%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
63
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
50%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
47
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: D+Signals: 4
39%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
50%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
60
Security
Trust, risk posture, and security compliance.
Grade: B-Signals: 1
60%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
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>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Checkmob by hand means minting a bearer token at /token, refreshing it, and finding the right call among 50 endpoints for clients, work orders, and checklists. Through Jentic you install once, import the Checkmob API from the API Directory, store the credentials once, and your agent calls it.
Permission scoping
Checkmob identifies records through the request body rather than the URL path, so scope the agent to the operations it needs, such as listing work orders and reading checklist answers. You choose that set, so creating clients or users is not included unless you add it.
Credential isolation
Your Checkmob credentials and the token minted at /token are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'create a work order' or 'pull checklist answers', and Jentic returns the matching Checkmob operation with its input schema so the agent picks the right endpoint among 50 without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Checkmob API through Jentic.
Why is there no official OpenAPI spec for Checkmob API?
Checkmob does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Checkmob API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.
What authentication does the Checkmob API use?
Checkmob uses HTTP bearer authentication. You exchange credentials at GET /token to receive a bearer token, which is then sent in the Authorization header on subsequent requests. Through Jentic, both the credentials and the resulting token are stored encrypted in your Jentic One instance, and Jentic refreshes the token transparently.
Can I create work orders with the Checkmob API?
Yes. POST /api/OrdemServico/Post creates a new work order tied to a client and service type. /api/OrdemServico/List returns existing orders with filters, and /api/OrdemServico/Get fetches a specific order by ID.
How do I read checklist answers via the Checkmob API?
Use POST /api/RespostasQuestionario/List with the questionnaire and date range. The endpoint returns the completed responses captured by technicians on the mobile app, which you can then transform into reports or compliance evidence.
What are the rate limits for the Checkmob API?
The OpenAPI specification does not declare formal rate limits. Plan for retry-with-backoff on 429 responses and avoid polling /api/OrdemServico/List in tight loops - pull on a schedule and react to webhooks if available.
How do I create a Checkmob work order through Jentic?
Install the SDK with `pip install jentic`, then call Jentic.search('create a work order'), load the schema for /api/OrdemServico/Post, and execute with the client_id, service_type, and scheduled date. Jentic handles the /token exchange and bearer injection.
Can I limit what my agent is allowed to do with the Checkmob API?
Yes. Because you run Jentic One yourself, your own rules decide which Checkmob operations and credentials the agent may use. You can scope it to only the calls it needs, such as listing work orders with /api/OrdemServico/List and reading checklist answers with /api/RespostasQuestionario/List, while leaving out write operations. Since Checkmob identifies records through the request body rather than the URL, creating clients via /api/Cliente/Post or provisioning users via /api/Usuario/Post is excluded unless you add it to that set.
GET STARTED