API
Add job-feasibility intelligence to the systems you already use.
Three modules, each answering one operational question. Endpoint shapes are described here; specifications are shared with development-access partners.
Coming next: public API access is not open yet. There is no self-serve key issuing today.
A fourth module, the used electric van check at /api/v1/ev-van-check, is in development. The endpoint describes its planned request and response fields and returns no assessment yet. Licensed third-party vehicle data will not be passed through it without redistribution rights in writing.
Deliverd APIs are modules within the One Fleet Technologies Reality Platform.
Three modules
Job feasibility API
Input
- Job
- Vehicle
- Load
- Deadline
- Relevant operational data
Output
- Accept
- Accept with conditions
- Reprice
- Decline
- Confidence
- Conditions
- Missing evidence
- Driver brief
Property fit API
Input
- Product
- Packaging
- Property measurements
- Handling resources
Output
- Fit verdict
- Required checks
- Handler requirement
- Missing measurements
- Confidence
Charging Value API
Input
- Vehicle profile
- Mission profile
- Driver hourly cost
- Detour limit
- Memberships held
Output
- Ranked options
- Cost components
- Suitability verdict
- Confidence
- Stated limitations
Outcome capture API
Input
- Job stage
- Waiting
- Issue
- Evidence
- Final outcome
Output
- Operational timeline
- Outcome record
- Review status
- Future evidence signal
Endpoint paths, authentication details and internal assessment rules are not published. Deliverd does not disclose proprietary scoring rules or infrastructure details.
How partners use it
Decision at intake
Score the job as it enters the TMS or order system.
Fit at checkout
Run a property-fit verdict before the promise is made.
Outcome back
Return the operational timeline so the record stays honest.