ESRI ArcGIS
ESRI ArcGIS is the world's leading geospatial platform providing mapping, spatial analysis, and location intelligence APIs and SDKs. The developer platform includes REST APIs, multiple language SDKs, and cloud services for GIS professionals and developers building location-enabled applications.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles ESRI ArcGIS the way a machine reads it — 36 machine-readable artifacts across 8 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 — ESRI ArcGIS scores 49.5/100 (developing), with a separate agent-readiness read of 48/100 (agent ready). 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 ESRI ArcGIS
Each block below is one kind of artifact we hold for ESRI ArcGIS. 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 8
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.
ArcGIS Maps SDK for JavaScript
The ArcGIS Maps SDK for JavaScript enables web developers to build compelling 2D and 3D mapping applications with interactive visualizations, spatial analysis tools, geocoding, ...
ArcGIS API for Python
The ArcGIS API for Python provides a Pythonic interface for GIS capabilities including data management, spatial analysis, geocoding, routing, and administration of ArcGIS Online...
ArcGIS Geocoding Service
The ArcGIS Geocoding Service provides address search, reverse geocoding, address suggestions, and batch geocoding capabilities using the World Geocoding Service.
ArcGIS Routing Service
The ArcGIS Routing Service provides route optimization, turn-by-turn directions, nearest facility finding, service area definition, and fleet management capabilities.
ArcGIS Places Service
The ArcGIS Places Service provides search and retrieval of global points of interest spanning over 1,000 feature categories for location-aware applications.
ESRI ArcGIS Geocoding API
Address search, reverse geocoding, and batch geocoding
ESRI ArcGIS Places API
Points of interest search and retrieval
ESRI ArcGIS Portal API
Portal items, users, groups, and organizational management
Scroll within the panel for all 8 ·
Open Collections 1
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).
ESRI ArcGIS Platform API
OPEN COLLECTIONPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Esri Arcgis Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Esri Arcgis Finops
FINOPSSemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Esri Arcgis Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
ESRI ArcGIS API Rules
SPECTRALJSON Schema 17
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
Category
JSON SCHEMAError
JSON SCHEMAArcGIS Feature
JSON SCHEMAGeocodeCandidate
JSON SCHEMAGeocodeResponse
JSON SCHEMAGroupRef
JSON SCHEMAItem
JSON SCHEMAItemCollection
JSON SCHEMAPlace
JSON SCHEMAPlacesResponse
JSON SCHEMAPlaceSummary
JSON SCHEMAPoint
JSON SCHEMAPortal
JSON SCHEMAReverseGeocodeResponse
JSON SCHEMASearchResults
JSON SCHEMASpatialReference
JSON SCHEMAUser
JSON SCHEMAScroll within the panel for all 17 ·
JSON Structure 1
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Esri Arcgis Structure
JSON STRUCTURESecurity Posture 2
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.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
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 ESRI ArcGIS — 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.
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Access & Security 3
Authentication, authorization, and security posture
Company 1
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/esri-arcgis · machine-readable index on apis.io