Locus
Locus is an AI-powered last-mile and dispatch logistics platform headquartered in Bengaluru, India (with US operations in Wilmington, Delaware) that helps enterprises plan, execute, and orchestrate deliveries across captive, contracted, outsourced, and hybrid fleets. The platform spans transportation management, dispatch planning and route optimization (across 180+ variables including time, distance, fuel, capacity, and SLAs), hub operations, delivery orchestration and carrier management, fulfillment automation, driver app and control tower track-and-trace, and analytics. Locus claims 360+ enterprise customers across 30+ countries — including Unilever, Nestlé, Blue Dart DHL, Meesho, Lenskart, and Justo — with 1.5B+ deliveries optimized and $320M+ in cost savings generated. The company was acquired by Ingka Group (the world's largest IKEA retailer) in 2024 while continuing to operate as an independent product organization. Locus exposes a SwaggerUI developer surface with three OpenAPI 2.0 specifications covering Order Management (oms.locus-api.com), Entity Management (locus-api.com), and Platform Entities (platform.locus-api.com); authentication is via HTTP Basic plus API key, provisioned by a Locus representative.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Locus the way a machine reads it — 24 machine-readable artifacts across 16 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Locus scores 33.3/100 (thin), with a separate agent-readiness read of 41/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Locus
Each block below is one kind of artifact we hold for Locus. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 16
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Locus HomebaseMaster API
The HomebaseMaster API from Locus — 2 operation(s) for homebasemaster.
Locus LocationMaster API
The LocationMaster API from Locus — 2 operation(s) for locationmaster.
Locus Order API
The Order API from Locus — 8 operation(s) for order.
Locus OrderServiceability API
The OrderServiceability API from Locus — 1 operation(s) for orderserviceability.
Locus PersonnelMaster API
The PersonnelMaster API from Locus — 2 operation(s) for personnelmaster.
Locus Rider API
The Rider API from Locus — 2 operation(s) for rider.
Locus RiderPersona API
The RiderPersona API from Locus — 2 operation(s) for riderpersona.
Locus Roster API
The Roster API from Locus — 3 operation(s) for roster.
Locus ServiceType API
The ServiceType API from Locus — 1 operation(s) for servicetype.
Locus ServiceTypeConfiguration API
The ServiceTypeConfiguration API from Locus — 1 operation(s) for servicetypeconfiguration.
Locus ShiftTag API
The ShiftTag API from Locus — 2 operation(s) for shifttag.
Locus SKUMaster API
The SKUMaster API from Locus — 2 operation(s) for skumaster.
Locus TeamMaster API
The TeamMaster API from Locus — 2 operation(s) for teammaster.
Locus Transporter API
The Transporter API from Locus — 2 operation(s) for transporter.
Locus Vehicle API
The Vehicle API from Locus — 2 operation(s) for vehicle.
Locus VehicleModel API
The VehicleModel API from Locus — 2 operation(s) for vehiclemodel.
Scroll within the panel for all 16 ·
Open Collections 3
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
GraphQL 1
Where a provider ships GraphQL, the schema is the contract. We profile it alongside the REST surface so the whole interface is legible in one place.
GraphQL schemas published by this provider.
Locus GraphQL Schema
Locus is an AI-powered last-mile and dispatch logistics platform that helps enterprises plan, execute, and orchestrate deliveries across captive, contracted, outsourced, and hyb...
GRAPHQLSecurity Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Locus — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 2
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 8
The organization behind the API
Scroll within the panel for all 8 ·
Other 8
Properties that don't map to a standard resource type
Scroll within the panel for all 8 ·
← All providers · Data indexed from github.com/api-evangelist/locus-sh · machine-readable index on apis.io