Skip to content
Octo × Services and REST PT Request an assessment

Octo for ArcGIS services and REST

Everything has a URL. The credit ceiling is yours.

In ArcGIS, layers, geoprocessing tools, geocoding, routing and fleet are services with an HTTP address. They can be automated with curl or Python, on Linux too. Octo can estimate the cost before spending, write scripts that only simulate until someone approves, and build the review queues: low-score addresses, sync conflicts, orders outside the time window. Spending credits, writing to production and sending addresses (which are personal data) remain decisions for the client's authorized people.

Request an assessment See what it does
A terminal sends REST calls to ArcGIS services; a gauge shows the estimated spend below the credit ceiling; Octo, in the center, takes the result to a map with points and a route and to a review queue $ curl -X POST .../FeatureServer/0/query resultOffset=2000 resultRecordCount=2000 $ .../BatchGeocode/submitJob jobStatus: esriJobSucceeded $ .../extractChanges layerServerGens adds 1 · updates 2 · deleteIds 1 $ ESTIMATED CREDITS × CEILING CEILING 6,800 after dedup POINTS AND ROUTE SCORE < 90 · FOR REVIEW python3 geocodificar_lote.py cadastro.csv --teto-creditos 8000 OCTO × REST SIMULATION S-05
Stored geocoding40credits per 1,000 in ArcGIS Online
Direct batch, world service1000addresses per call (suggests 150)
Fleet (VRP), job mode2.000orders and 100 routes per job
Sources15listed at the end of the page
01

What Octo does with the services.

Six possible deliverables, drawn from the survey. All of them start from reading and simulation; writing to production, publishing and spending credits stay with whoever the client authorizes.

Geocoding with a ceiling

Can deduplicate the registry, estimate credits from the official table, stop above the approved ceiling and set aside low-score addresses for review.

Deliverable: estimate, points and review queue

Sync with a legacy system

Can pull what changed in the field with extractChanges, apply the ERP delta with applyEdits and check the counts on both sides at the end.

Deliverable: simulation, conflicts and verification

Routes, fleet and service areas

Can build the routing job (VRP) from spreadsheets, with time windows and capacity, and return a report per vehicle and the orders that did not fit.

Deliverable: proposed routes for the dispatcher

Paginated extraction and indicators

Can download entire layers with resultOffset, check the total with returnCountOnly and calculate indicators by group on the server itself.

Deliverable: complete, verified file

Publishing prepared

Proposes the publishing flow by script (arcpy: draft, StageService, UploadServiceDefinition) for the authorized person to run and check.

Deliverable: reviewed publishing script

Minimum-scope credentials

Can design one credential per purpose (geocode only, read one layer only), with expiration and key rotation, always outside the code.

Deliverable: matrix of credentials and privileges
Map of service areas around a facility: three concentric irregular polygons show how far one can get in 5, 10 and 15 minutes by car, distorted by the main roads and cut off by a river river main ave. Facility up to 5 min up to 10 min up to 15 min SERVICE AREAS · 5 / 10 / 15 MIN
Illustration: example of the type of map the procedure generates; fictitious data.
02

Eight arms, one service call.

The same Octo cycle, applied to the ArcGIS REST API. Each arm has a narrow role; spending credits, writing to production and publishing are done by the client's authorized people.

  1. Discovery

    Reads the services

    ArcGIS Online or Enterprise, version, description of each service: capabilities, maxRecordCount, pagination, ChangeTracking, accepted formats.

  2. Data

    Pins down keys and counts

    Which field links the map to the ERP, with a unique index; coordinate system; how many records each side has before starting.

  3. Security

    Minimum credentials and LGPD

    One credential per purpose, only in an environment variable. An address is personal data: sending it to an external service is decided beforehand, with the client.

  4. Architecture

    Chooses the operation

    Direct batch or file job; applyEdits or append; synchronous or submitJob. The cost from the official table goes into the choice.

  5. Development

    Writes the script

    In curl or Python, with simulation by default, credit ceiling, resume and retry on temporary errors. Runs on Linux.

  6. Review

    Checks by content

    Counts on both sides, usage_cost against the estimate, a sample of points on the map. A 200 response does not prove it worked.

  7. Release

    Delivers to whoever runs it

    Only with your OK, and by the authorized person: running with --executar, loading into production, publishing the layer.

  8. Documentation

    Records what holds in your environment

    Service version, parameters, actual cost and date of each run. The next estimate starts from the measured cost, not from the table.

Octo does not spend credits above the agreed ceiling, write to production services or publish layers. That belongs to the client's authorized people.

03

Each task, its path.

The criteria Octo uses to choose the operation. Prices and limits are those in the Esri documentation accessed on October 29, 2026.

TaskPathNote
Downloading an entire layerquery with resultOffset and resultRecordCountRequires supportsPagination; check with returnCountOnly
Indicator by groupquery with outStatisticsCalculated on the server, without downloading features
Editing a few recordsapplyEdits with rollbackOnFailure=trueWriting to production: authorized person
What changed since yesterdayextractChanges with layerServerGensRequires ChangeTracking
Geocoding 100,000 or moreBatchGeocode job with a CSV file40 credits per 1,000 in ArcGIS Online
Fleet routes with time windowsVRP via submitJobUp to 2,000 orders and 100 routes per job
Distance between many pairsOrigin-destination matrix0.5 credit per 1,000 pairs in ArcGIS Online
Publishing or overwriting a layerarcpy: draft, StageService, UploadServiceDefinitionRequires ArcGIS Pro, which runs on Windows
04

From one-off script to routine.

Three steps. Each one only makes sense after the previous one has shown results in your environment.

A proposal, not a promise

1 Today

Reading and estimating

With read access, Octo describes the services and estimates the cost of the work you have in mind.

  • Inventory of each service's capabilities
  • Paginated extraction verified by count
  • Cost estimated from the official table, with dedup applied
Benefit: deciding with the number in hand
2 Next

Procedures with simulation

Geocoding, sync and routing now run with an approved simulation and a credit ceiling.

  • Review queues instead of checking everything
  • Conflicts and unserved orders with the reason
  • Actual cost compared with the estimate
Benefit: the team reviews exceptions, not entire spreadsheets
3 Later

Monitored nightly routine

Sync and loads become a scheduled routine in the client's environment, with an alert when the verification fails.

  • State that only advances when the counts match
  • Cost history per run
  • Key rotation before expiration
Benefit: map and legacy system match every day
05

Confirmed by source.

Each point below has a source published by the vendor, the project or the responsible agency. The sources are in the next section.

4

points with a published source, each with its reference alongside.

ConfirmedGeocoding price
Stored geocoding, which includes the direct batch and the file job: 40 credits per 1,000 in ArcGIS Online or $4 per 1,000 in ArcGIS Location Platform. Billing is per result returned; suggest is free.Source: ArcGIS Geocoding service; Understand credits (ArcGIS Online)
ConfirmedBatch and fleet: limits
The world geocoding service reports MaxBatchSize 1000 and SuggestedBatchSize 150. The fleet job accepts up to 2,000 orders, 100 routes, 200 orders per route and 4 hours of execution; the price table lists 1,000 credits per 1,000 fleet routes.Source: GeocodeServer description read on October 29, 2026; SolveVehicleRoutingProblem; ArcGIS Routing service
ConfirmedIncremental changes and upsert
extractChanges requires ChangeTracking; in ArcGIS Online, a hosted service cannot have Sync and ChangeTracking together. The append upsert is not accepted with sync or changeTracking enabled and matches by ObjectID, GlobalID or a field with a unique index (upsertMatchingField).Source: Extract Changes and Append (Feature Service), developers.arcgis.com
ConfirmedTokens and keys
App token via client_credentials: default validity of 120 minutes, maximum of 20,160. API keys are valid for at most one year, up to two per credential, with chosen privileges. Python API arcgis 2.4.4 published on October 20, 2026.Source: Token (OAuth 2.0); API key credentials; PyPI
06

What Octo does and what stays with you.

Octo prepares everything, but does not sign. The document of record stays with whoever is accountable for it.

Octo prepares

Gathers, calculates, organizes and produces the documents: spreadsheets, reports, maps and drafts.

Deliverable: material ready for review

Your team reviews

The licensed professional reviews what Octo delivered before signing. If something doesn't add up, it goes back to Octo with the correction.

Step: review by whoever signs

Who signs

Octo does not sign. Designs, technical reports, ART/RRT, accountability reports and any official document are still signed by the licensed professional at the company or agency: here, the professional of record for the map or survey.

Signature: professional of record for the map or survey
07

Sources.

Esri documentation used in the research, accessed October 29, 2026.

Your services, automated within the ceiling.

The assessment starts read-only: the description of your services and a cost estimate for the work you have in mind. You get a proposal and decide with it in hand.

Request an assessment