Agent-ready OpenAPI document · curated by JenticHR recruitingEmployee Managementbearer12 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Manage work orders, job sites, devices, and time clock entries for a field workforce, and send messages to deployed workers via the allGeo API.
Use for: I need to schedule a work order for a field technician, Create a new job site at a customer address, Register a new mobile device for a worker, Record a clock-in event for an employee
Not supported: Does not handle payroll calculation, invoicing, or customer billing - use for field workforce dispatch, time clock capture, and worker messaging only.
Jentic publishes the only available OpenAPI specification for allGeo API, keeping it validated and agent-ready. allGeo is a workforce management platform for distributed and field teams, and the API covers work orders, job sites, devices, time clock entries, and SMS or push messaging. Authentication is bearer-token based with explicit login and refresh endpoints, and the API is scoped to operational data - not payroll calculation or invoicing. The endpoint set is small enough to learn in a session yet covers the core daily operational events of a field workforce.
Install Jentic One Beta
Connect the allGeo API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the allGeo 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%2Fallgeo.com%2Fallgeo" | 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%2Fallgeo.com%2Fallgeo" | 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 allGeo API.
Authenticate with login and refresh tokens for tenant-scoped access
Create or update work orders for scheduled field jobs
Provision new job sites and remove ones no longer in service
Register field devices and remove them when retired
Record and update time clock entries for shift attendance
Send SMS or push notifications to workers in the field
Use Cases
Patterns agents use allGeo API for, with concrete tasks.
★ Field service scheduling
Dispatch teams push new work orders into allGeo whenever a customer ticket is approved, then update or delete them as plans change. POST /api/v1/schedule creates or updates a work order in one call, and DELETE /api/v1/deleteSchedule/{workOrderNumber} removes one. The flat endpoint shape avoids juggling multiple resource trees per dispatch event.
Call POST /api/v1/schedule for work order WO-9123 with the technician ID, job site name, and start time, then verify the response indicates success.
Mobile time clock capture
Operations capture clock-in and clock-out events from the allGeo mobile app via POST /api/v1/createTimeClock and update them via POST /api/v1/updateTimeClock. The data feeds downstream payroll without manual sheet collection. This is the fastest path to enforce attendance accuracy in distributed teams.
Record a clock-in for employee E-101 at job site 'Warehouse-3' by calling POST /api/v1/createTimeClock with the timestamp.
Field crew messaging
Coordinators push job updates to workers via allGeo's messaging endpoint, which dispatches an SMS or push notification depending on device registration. POST /api/v1/allgeo/sendMessage takes the worker identifier and the body, and the message lands on the device the worker uses in the field. This avoids a separate SMS provider integration when allGeo is already in place.
Send an SMS to worker E-204 with body 'Reschedule: arrive at site Warehouse-3 at 14:00' via POST /api/v1/allgeo/sendMessage.
AI agent dispatch automation
An AI agent watching customer tickets can create the matching allGeo work order, register the assigned device, and message the technician in one chained execution. Through Jentic the agent searches by intent for each step and the bearer token never appears in the prompt. This converts a manual dispatch console into an event-driven loop.
Use Jentic to search 'create an allGeo work order', execute POST /api/v1/schedule with the ticket data, then call POST /api/v1/allgeo/sendMessage to alert the technician.
Key Endpoints
12 endpoints — jentic publishes the only available openapi specification for allgeo api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
POST
/react/v1/login
Authenticate and obtain a bearer token
GET
/react/v1/refresh
Refresh an expired bearer token
POST
/api/v1/schedule
Create or update a work order
POST
/api/v1/createSites
Create a job site
POST
/api/v1/createDevices
Register a device
POST
/api/v1/createTimeClock
Record a time clock entry
POST
/api/v1/allgeo/sendMessage
Send SMS or push notification
POST
/react/v1/login
Authenticate and obtain a bearer token
GET
/react/v1/refresh
Refresh an expired bearer token
POST
/api/v1/schedule
Create or update a work order
POST
/api/v1/createSites
Create a job site
POST
/api/v1/createDevices
Register a device
POST
/api/v1/createTimeClock
Record a time clock entry
POST
/api/v1/allgeo/sendMessage
Send SMS or push notification
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.
A
allGeo API
- AI-Aware (B)65/100
100
Foundational Compliance63
Developer Experience & Jentic Compatibility42
AI-Readiness & Agent Experience94
Agent Usability60
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
100
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 4
98%
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).
100%
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.
42
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: D-Signals: 4
36%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
83%
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 the allGeo API by hand means running its bearer login and refresh flow against api.allgeo.com/track and encoding schedule, site, device, and time-clock calls yourself. Through Jentic you install once, import the allGeo API from the API Directory, store the bearer token once, and your agent calls it.
Permission scoping
The allGeo API carries its targets in the request body rather than as path resources, so limit the agent to the operations it needs, such as creating a schedule or sending a worker message. You choose the operations it may call, so creating sites or devices is not included unless you add them.
Credential isolation
Your allGeo bearer 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 'schedule a field worker' or 'send a message to a worker', and Jentic returns the matching allGeo operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using allGeo API through Jentic.
Why is there no official OpenAPI spec for allGeo API?
allGeo does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call allGeo 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 allGeo API use?
Bearer token, obtained by calling POST /react/v1/login and refreshed via GET /react/v1/refresh. Through Jentic, the token is held in the encrypted vault and injected at execution time so it never appears in agent prompts.
Can I create or update a work order with the allGeo API?
Yes. POST /api/v1/schedule creates or updates a work order in one call, and DELETE /api/v1/deleteSchedule/{workOrderNumber} removes one. This is the primary dispatch surface for the API.
How do I record a time clock entry via the allGeo API through Jentic?
Run pip install jentic, search 'record a time clock entry in allGeo', load the input schema for POST /api/v1/createTimeClock, and execute with the worker ID and timestamp.
Can the allGeo API send messages to workers?
Yes. POST /api/v1/allgeo/sendMessage dispatches an SMS or push notification to a registered worker, removing the need for a separate SMS provider when allGeo is the system of record for the field workforce.
Does the allGeo API handle payroll calculation?
No. The API captures time clock events and operational data but does not run payroll. Use a payroll API such as Gusto or BambooHR for net pay calculation, deductions, and pay stubs.
Can I limit what my agent is allowed to do with the allGeo API?
Yes. Because Jentic One is self-hosted, your own rules decide which allGeo operations and credentials the agent may use, and you grant only the ones a given task needs, such as creating a work order with POST /api/v1/schedule or messaging a worker with POST /api/v1/allgeo/sendMessage. The allGeo API carries its targets in the request body rather than as path resources, so operations like creating job sites or registering devices stay out of reach unless you explicitly add them. The bearer token is injected at execution time and never enters the agent's prompt.
GET STARTED