canonical: https://jentic.com/apis/routific.com/routific

# Routific Engine API

Routific Engine API for vehicle routing optimization, including Vehicle Routing Problem (VRP) and Pickup & Delivery Problem (PDP) solvers with both synchronous and long-running task support. The API exposes 5 endpoints secured with bearer authentication.

## For AI agents

Programmatically solve vehicle routing problem, solve vrp as long-running task. Covers 5 operations with bearer authentication.

## Scope

Does not handle payments, communications, or developer tools - use for crm only.

## Capabilities

- Solve Vehicle Routing Problem
- Get long-running job status
- Integrate Routific Engine API into automated workflows
- Query and filter Routific Engine API records by parameters
- Monitor Routific Engine API operational status and events

## Use cases

### CRM Operations

Use the Routific Engine API to perform crm operations programmatically. The API provides 5 endpoints covering core functionality including solve vehicle routing problem, solve vrp as long-running task, solve pickup and delivery problem.

Example prompt: Call POST /v1/vrp to solve vehicle routing problem

### Automated Vehicle Routing Management

Automate vehicle routing operations by combining multiple Routific Engine API endpoints. Agents can solve vrp as long-running task and then solve pickup and delivery problem in a single workflow.

Example prompt: Call POST /v1/vrp-long to solve vrp as long-running task, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Routific Engine API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer tokens manually.

Example prompt: Search Jentic for 'solve vehicle routing problem', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /v1/vrp | Solve Vehicle Routing Problem |
| POST | /v1/vrp-long | Solve VRP as long-running task |
| POST | /v1/pdp | Solve Pickup and Delivery Problem |
| POST | /v1/pdp-long | Solve PDP as long-running task |
| GET | /jobs/{jobId} | Get long-running job status |

## Key resources

- **Vehicle Routing** — Vehicle Routing Problem endpoints
- **Pickup & Delivery** — Pickup and Delivery Problem endpoints
- **Jobs** — Long-running job management

## Why Jentic

- **Setup:** Wiring Routific by hand means handling its bearer token against api.routific.com and building your own polling loop for the long-running VRP and PDP jobs. Through Jentic you install once, import Routific from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Routific takes the routing problem in the request body, so scope the agent to the operations it needs, such as solving a vehicle routing problem or checking a job's status. You pick that allowed set, so the pickup and delivery solvers stay out unless you include them.
- **Credential handling:** Your Routific 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.
- **Discovery method:** Agents search Jentic by intent such as 'solve a vehicle routing problem' or 'check a routing job status', and Jentic returns the matching Routific operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Hubspot** — Alternative crm API
- **Salesforce** — Alternative crm API
- **Pipedrive** — Complementary crm API
- **Zoho** — Complementary crm API

## FAQ

### What authentication does the Routific Engine API use?

The Routific Engine API uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I solve vehicle routing problem with the Routific Engine API?

Yes. Use the POST /v1/vrp endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Routific Engine API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I solve vehicle routing problem through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'solve vehicle routing problem'. Jentic returns the matching Routific Engine API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Routific Engine API have?

The Routific Engine API exposes 5 endpoints covering vehicle routing, pickup & delivery, jobs operations.

### Can I limit what my agent is allowed to do with the Routific Engine API?

Yes. Because Jentic One is self-hosted, you set the rules that decide which Routific operations and credentials your agent may use. You can allow only the calls it needs, such as solving a vehicle routing problem or checking a job's status, and leave the pickup and delivery solvers out of the allowed set. The stored bearer token is injected at execution time only for the operations you permit.