ORO Labs (platform)
ORO Labs is an AI procurement-orchestration platform built on an embedded iPaaS. Rather than one public REST object model, ORO federates 200+ semantically rich integrations across ERP, procure-to-pay, contract and risk systems. VMS Agent maps canonical intent onto ORO's intake-request and workflow objects so services and contingent demand enter the orchestrated source-to-pay flow.
The public API facts VMS Agent's adapter relies on. Tenant-specific details (custom fields, picklists, approval chains) are confirmed during connection and folded into the MappingProfile.
| Authentication | SSO + role-based access control with encryption; SOC 1, SOC 2 and ISO 42001 (responsible AI) certified. API credentials are provisioned per customer — no public self-service developer portal. |
|---|---|
| API style | Embedded iPaaS connectors (semantically rich — the platform understands suppliers, line items and contracts) rather than a single public REST surface; workflow triggers + real-time data sync. |
| Base URL | Per-customer tenant, provisioned at onboarding. No public base URL. |
| Objects | Intake request, Approval, Supplier, Contract, Risk assessment, Purchase Order, Invoice (source-to-pay) |
| Events / webhooks | Real-time data sharing and activity triggering across systems via the embedded iPaaS; event-driven workflow triggers. Delivery specs provisioned per integration. |
| Rate limits | Not publicly documented; defined per integration. |
“Docs confidence” describes how deterministic our mapping templates can be before we connect to a tenant. Even with public docs, implementations vary — especially around custom fields, approval flows and object extensions.
Deterministic mapping
Common Workforce Model fields map to known API fields. Best for standard objects (requisitions, assignments, timesheets, POs).
Tenant discovery
VMS Agent can scan tenant configuration (custom fields, picklists, required fields) where the platform permits it, then generate a tenant‑specific MappingProfile.
Enrichment loop
If the target platform requires a field the Intent record doesn't yet have, VMS Agent emits an enrichment_request back to the intake layer.
An opinionated baseline. The platform adapter enforces additional requirements via preflight. “Tenant required” fields are discovered during connection and added to the MappingProfile.
| Object | Canonical fields | Platform target | Required status | Notes |
|---|---|---|---|---|
| Intake request Start the orchestration |
service_category, sow.summary, budget, dates | Intake request (orchestrated workflow) | Required | Routes through the configured source-to-pay flow |
| Supplier Resolve + risk |
supplier_name, tax_id, risk_flags | Supplier object + risk assessment | Tenant required | Risk / onboarding gates progression |
| Contract / PO Back-sync |
contract_ref, po_lines, amount, status | Contract + PO via iPaaS connector | Read | Synced from the downstream ERP / P2P system |
Idempotency & drift — publish + reconcileExpand
Publish operations are idempotent using a deterministic key {intent_id}-{intent_version}-{target_system}. Because humans can change records inside the platform, VMS Agent supports reconciliation: it compares the platform record snapshot to the canonical intent and flags drift.
Real deployments rely on program-specific custom fields (for compliance, approvals, GL coding, rate rules or supplier constraints). VMS Agent is designed to generate tenant‑specific mappings rather than forcing you to redesign your intake.
How scanning works
High-level flow
What gets produced
Portable artefacts
Important — where this platform is tenant-definedExpand
ORO is an orchestration layer, not a transactional system of record — it federates to your ERP / P2P (SAP, Oracle, NetSuite, Coupa, Ariba, JAGGAER, GEP) through its embedded iPaaS. There is no public REST object catalogue; integration is delivered via ORO's connector framework and provisioned per customer. Public API, auth and webhook specifications are not published.
Use this page alongside the API + Schemas docs to implement: destination connection, preflight validation, publish, webhook back-sync and reconciliation.