Previsto API

Name: Previsto API
Brand: Previsto API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentProductivityCalendar Schedulingbasic21 EndpointsREST

For Agents

Manage field service scheduling with contacts, assignments, service agreements, and organizations for recurring service delivery operations.

Install Jentic One Beta

Connect the Previsto API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Previsto 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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 Previsto API.

Create and manage customer contacts with scheduling preferences and service history

Assign field workers to specific service tasks with date and location details

Define recurring service agreements between organizations and contacts

GET STARTED

Start building with Previsto API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Previsto API for, with concrete tasks.

★ Field Service Scheduling

Schedule and track field service assignments by creating assignment records linked to contacts and service agreements. Previsto manages the relationship between who needs service (contacts), what service is agreed (agreements), and when it happens (assignments). Field service companies use this to coordinate cleaning crews, maintenance technicians, or delivery routes with full visibility into scheduled and completed work.

Create a new assignment via POST /assignments linked to an existing contact ID and agreement ID with a scheduled date and time

Recurring Service Agreement Management

Define and manage recurring service agreements that specify what services are delivered to which contacts on what schedule. Agreements act as templates that drive assignment creation, ensuring consistent service delivery. This supports cleaning services, property maintenance, landscaping, and other recurring field operations where the same work repeats on a regular cadence.

Create a service agreement via POST /agreements with contact reference, service type, and recurrence schedule, then verify it appears in GET /agreements

Customer and Organization Management

Maintain a database of service customers (contacts) organized under business entities (organizations). Each contact stores address, scheduling preferences, and service history. Organizations group contacts for billing and reporting. This provides the foundation for field service operations where multiple customer locations are managed under parent companies.

Create a new organization via POST /organizations, then create a contact under it via POST /contacts with the organization ID reference

AI Agent Field Service Automation

AI agents use the Previsto API through Jentic to automate field service operations including creating assignments, managing customer contacts, and tracking service agreement fulfillment. The agent searches for scheduling operations, loads endpoint schemas with required fields for assignments and contacts, and executes multi-step workflows to coordinate service delivery.

Search Jentic for 'create field service assignment', load the assignments operation schema, and execute with contact ID, date, and service details

Key Endpoints

21 endpoints — jentic publishes the only available openapi specification for previsto api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/assignments

List all service assignments

POST

/assignments

Create a new assignment

GET

/contacts

List all customer contacts

POST

/contacts

Create a new contact

GET

/agreements

List all service agreements

POST

/agreements

Create a service agreement

GET

/organizations

List all organizations

GET

/accounts/current

Get current account details

GET

/assignments

List all service assignments

POST

/assignments

Create a new assignment

GET

/contacts

List all customer contacts

POST

/contacts

Create a new contact

GET

/agreements

List all service agreements

POST

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Previsto Basic auth credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive requests with the Base64-encoded Authorization header pre-configured, so raw credentials never enter agent context.

Intent-based discovery

Agents search by intent (e.g., 'schedule a field service assignment') and Jentic returns matching Previsto operations with their input schemas including required contact and agreement references.

Time to first call

Direct Previsto integration: 1-2 days for auth setup, resource relationship mapping, and CRUD implementation. Through Jentic: under 1 hour — search for scheduling operations, load schemas, and execute.

FAQs

Specific to using Previsto API through Jentic.

Why is there no official OpenAPI spec for Previsto API?

Previsto does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Previsto API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Previsto API use?

The Previsto API uses HTTP Basic authentication. Through Jentic, your Basic auth credentials (username and password) are stored encrypted in the MAXsystem vault and agents receive requests with the Authorization header pre-configured in Base64 format.

Can I create recurring service assignments from an agreement?

Yes. Create a service agreement via POST /agreements defining the recurrence pattern and linked contact, then create individual assignments via POST /assignments referencing that agreement. The agreement defines the scope while assignments represent specific scheduled instances.

What are the rate limits for the Previsto API?

The specification does not document explicit rate limits. Previsto is designed for field service workloads with moderate request volumes. For batch operations across many contacts or assignments, implement client-side throttling and process records sequentially.

How do I create a service assignment through Jentic?

Install the SDK with pip install jentic, set your JENTIC_AGENT_API_KEY, then search for 'create field service assignment'. Jentic returns the POST /assignments operation with its schema showing required fields like contact ID, date, and service type. Execute to create the assignment.

Can I organize contacts under parent organizations?

Yes. Create organizations via POST /organizations to represent business entities, then create contacts via POST /contacts with an organization reference. Use GET /contacts to list all contacts, filtering by organization to see grouped customer records.

Previsto API

Connect the Previsto API to your agent

Capabilities

Start building with Previsto API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs