Provider graph
Model professionals, services, and eligibility attributes.
Provider resolution infrastructure
Find the right professional. Book the right time.
Orita helps AI applications onboard professionals, search their own provider networks, apply eligibility rules, resolve real-time availability, and complete booking workflows through one API.
Your providers. Your customer experience. Orita handles the infrastructure.
REST APINode SDKPython SDKMCPA2ASigned webhooks
CUSTOMER NEED
Find a Spanish-speaking therapist who offers virtual sessions, accepts Sanitas, and is available next Tuesday afternoon.
01Search network
02Apply eligibility
03Resolve availability
04Rank and explain
VALID OPTION
AG
Dr. Ana GarcĂaTuesday · 3:00 PM · Virtual
94
Matches every required condition and is the earliest available afternoon appointment.
POST
/api/v2/resolutions/res_7812/confirm201 confirmedEligibility engine
Separate required constraints from ranking preferences.
Resolution API
Return valid provider-and-time options with reasons.
Reliable execution
Hold, confirm once, and synchronize the lifecycle.
Why Orita exists
AI understands the request. Orita resolves who can fulfill it.
Traditional scheduling assumes the host is already known. But provider-based applications begin with a customer need and must determine which professional is eligible, available, and appropriate.
Orita turns that need into ranked, explainable provider-and-time options, then safely completes the booking lifecycle.
Scheduling tools find time.Orita resolves service delivery.
A different starting point
From customer need to confirmed booking.
Orita starts before the calendar lookup and continues after the recommendation.
Customer need
Receive a structured request from an AI application.
Provider eligibility
Apply service, language, insurance, license, and organization rules.
Availability resolution
Check schedules and connected calendars only for eligible providers.
Ranked options
Return valid provider-time combinations with reason codes and explanations.
Reliable confirmation
Hold, revalidate, and confirm the selected option exactly once.
Lifecycle sync
Keep every system consistent with signed, retryable webhooks.
Product demo
See provider resolution in 72 seconds.
Watch Orita search a provider network, apply eligibility rules, resolve availability, confirm a booking, and synchronize every system.
Resolution API
Search, explain, hold, and confirm.
One request searches your provider network, applies hard constraints and preferences, and returns valid options your application can safely execute.
- Hard constraints fail closed when provider data is missing
- Preferences affect ranking without invalidating options
- Every option includes reason codes and a plain-language explanation
- Idempotency and atomic confirmation prevent duplicate bookings
- Signed webhooks keep the complete lifecycle synchronized
import { OritaClient } from "orita-sdk";
const orita = new OritaClient({
apiKey: process.env.ORITA_API_KEY
});
const resolution = await orita.resolveScheduling({
service: "therapy",
dateRange: {
from: "2026-08-05",
to: "2026-08-12",
timezone: "America/New_York"
},
constraints: {
languageCodes: { anyOf: ["es"] },
modalityCodes: { anyOf: ["virtual"] },
acceptsNewClients: true
},
preferences: {
dayParts: ["afternoon"],
earliestAvailable: true
},
limit: 5
});
const option = resolution.options[0];
await orita.holdOption(
resolution.resolutionId,
option.optionId,
120 // ttlSeconds — hold expires in 2 minutes
);
const booking = await orita.confirmResolution(
resolution.resolutionId,
{
optionId: option.optionId,
customer: {
name: "James Park",
email: "james@example.com"
}
}
); SAMPLE RESPONSE
{
"resolutionId": "res_7812",
"status": "resolved",
"summary": {
"providersScanned": 126,
"eligibleProviders": 14,
"providersWithAvailability": 4
},
"options": [
{
"optionId": "opt_92ab",
"provider": {
"id": "pro_82fa1",
"displayName": "Dr. Ana GarcĂa"
},
"slot": {
"start": "2026-08-05T15:00:00-04:00"
},
"score": 94,
"reason": "Earliest afternoon slot matching
all hard constraints."
}
]
} Eligibility checked Availability verified Conflict protected Signed webhook sent
Explainable resolution
See exactly how Orita reached the result.
Every provider is evaluated against explicit rules. Every returned option explains why it qualified and why it ranked where it did.
Sample resolutionTherapy · Spanish · Virtual · Sanitas · New Jersey
126providers searched
84offer therapy
37support virtual sessions
19speak Spanish
11accept Sanitas
7accept new clients
4have verified availability
5valid options returned
AG
Dr. Ana GarcĂaTuesday · 3:00 PM
94
Required rules passed
- Offers the requested therapy service
- Licensed in New Jersey
- Accepts Sanitas
- Supports virtual appointments
- Accepting new clients
- Real-time availability verified
Ranked higher because
- Preferred language
- Preferred afternoon daypart
- Earliest eligible option
Why others were excluded19 insurance mismatches12 not accepting new clients22 without verified availability
Reliable execution
Resolution you can safely execute.
Orita does not stop at a recommendation. It carries the selected option through a reliable, auditable booking lifecycle.
01Resolve
02Hold
03Revalidate
04Confirm once
05Synchronize
Idempotent requestsAtomic confirmationConflict protectionWebhook retries and replayComplete audit trail
Two scheduling modes
Use the simplest flow for each request.
You already know who should be booked.
getSlots()
↓
book()Use direct booking for a specific professional and service.
You know the customer need, but not who should handle it.
resolveScheduling()
↓
holdOption()
↓
confirmResolution()Use provider resolution to search, rank, explain, and confirm.
A different abstraction
Calendar tools schedule known hosts. Orita resolves provider networks.
DimensionTraditional schedulingOrita
Starting pointA known host or predefined teamThe customer’s service need
Primary jobFind an open timeFind an eligible professional and time
Data modelCalendar and eventProfessional, service, eligibility, and availability
RoutingGeneric team assignmentHard rules plus configurable preferences
ResponseAvailable slotRanked and explained provider-time option
ExecutionCreate a meetingConfirm and synchronize the booking lifecycle
Initial vertical focus
Built first for behavioral health and professional-service networks.
Model specialties, languages, modalities, insurance, license regions, accepting-new-client status, services, and availability in one provider graph.
SpecialtiesLanguagesModalitiesInsuranceLicense regionsServicesAvailabilityScheduling rules
Why now
AI applications are moving from answering to executing.
Before
Software helped users find information and complete forms.
Now
AI applications understand intent and coordinate multi-step workflows.
Next
Those applications need infrastructure to interact with real-world professionals.
Orita is building the provider resolution layer, starting with scheduling.
FAQ
Common questions.
What is provider resolution?+
Provider resolution is the process of determining which professional in a network is eligible and available to fulfill a specific customer request. Orita applies deterministic eligibility rules, checks real-time availability, ranks valid options, and explains every result.
When should an application use Orita?+
Use Orita when your application receives a service request and needs to determine which professional should handle it. If you already know the provider and only need to find a free time slot, a simpler scheduling API may be sufficient.
Does Orita provide the professionals?+
No. Orita is infrastructure. You connect and manage your own provider network. Orita searches it, applies your rules, and returns results.
Does creating a resolution create a booking?+
No. A resolution returns valid options. A booking is created only when you explicitly call confirmResolution with the customer’s approval.
How does Orita prevent duplicate bookings?+
Every mutating request supports idempotency keys. Atomic confirmation revalidates availability before writing the booking, preventing race conditions.
How does Orita explain why a provider was selected?+
Every option includes matched constraints, ranking factors, a plain-language reason, and a list of excluded providers with exclusion codes.
Can an AI agent book without a hosted page?+
Yes. Agents can call the Resolution API directly via REST, Node SDK, Python SDK, or MCP. Confirmation still requires explicit customer approval in the agent flow.
What happens when no provider qualifies?+
Orita returns a zero-result resolution with exclusion reasons for every provider. Your application can use that data to adjust constraints or prompt the user to broaden their request.
When should I use direct booking instead?+
Use getSlots() + book() when your application already knows which professional should handle the request and only needs to find an available time.
Does Orita replace Google Calendar or Outlook?+
No. Orita is provider resolution and booking infrastructure for professional-service networks. It can connect to calendars, but its primary job is eligibility and resolution — not calendar management.
Start building
Give your application the ability to find and book the right professional.
Import your provider network, define your rules, and return valid, explained provider-and-time options through one API.
REST APINode SDKPython SDKMCPA2ASigned webhooks