Aerial view of precision agriculture fields showing optimized routing patterns

Build autonomy-ready ag workflows

Get a route in one call, or integrate deeply across the Verge Launch Pad platform.

Upstream intelligence for autonomy

Our routing is designed as an upstream intelligence layer for mission planners and autonomy stacks.

Grower intent, captured at planning time

We capture grower intent before machines move—not just telemetry after the fact.

Getting an API Key

  1. 1
    Sign in to Launch Pad: app.vergeag.com
  2. 2
    Navigate to Profile → Manage API Keys
  3. 3
    Create Key (save it—it won't be shown again)
  4. 4
    Use key as X-API-KEY header in API calls

Testing & Sandbox: No dedicated sandbox environment. For additional testing capacity, email [email protected] to request testing credits (pay-per-use route plan session).

Quick Start

One call → one planned route (no setup required). View API reference

Inputs

  • • Field polygon (or multi-polygon), swath width, headland passes, preferred bearing

Units

Metric units (meters, seconds). Imperial units support coming soon.

Outputs

Two variants: Rich JSON or standard GeoJSON (tracks, headlands, connectors, turns) + metrics (time, distance, overlap).

Code Examples

Bash

curl -X POST https://app.vergeag.com/api/path-plans/direct \
  -H "X-API-KEY: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "field": { "type":"Polygon","coordinates":[[[lon,lat],[...],[lon,lat]]] },
        "machine": { "widthMeters": 12 },
        "headland": { "passes": 2 },
        "tracks": { "preferredDirectionDegrees": 90 } }'

JavaScript

const res = await fetch("https://app.vergeag.com/api/path-plans/direct", {
  method: "POST",
  headers: { 
    "X-API-KEY": "YOUR_API_KEY", 
    "Content-Type": "application/json" 
  },
  body: JSON.stringify({
    field: { type: "Polygon", coordinates: [[[lon,lat], ...]] },
    machine: { widthMeters: 12 },
    headland: { passes: 2 },
    tracks: { preferredDirectionDegrees: 90 }
  })
});
const plan = await res.json();

C#

using var client = new HttpClient();
client.DefaultRequestHeaders.Add("X-API-KEY", "YOUR_API_KEY");
var content = new StringContent(payloadJson, Encoding.UTF8, "application/json");
var res = await client.PostAsync("https://app.vergeag.com/api/path-plans/direct", content);
var json = await res.Content.ReadAsStringAsync();

Full Platform

Deep integration via entities & jobs (polling-only). Browse all endpoints

Auth

API Key

Boundaries I/O

GeoJSON/WKT/KML

Bulk Guidance Jobs

Submit & poll every 5 seconds until complete

Export Formats

ISO-XML, Shapefile, John Deere, CNH, Trimble, KML, plus direct push to JD Operations Center and CNH portals

Flow

Import boundary Create job Poll (5s) Retrieve outputs Export

Which API Should I Use?

Quick Start

2 simple endpoints for fast routing

Fast, no-login access to plans
Simple, one-call interface
Stateless routing requests
Quick prototyping & testing

Best for:

POCs, demos, simple integrations

Full Platform

Complete API suite for advanced integrations

Store fields, projects & user data
Customize projects & reuse routes
Track telemetry & operations
Multi-user & organization support

Best for:

Robotics, FMIS platforms, dealer tools, complex products

Capabilities

Coverage & Pass Generation

Swaths, headlands, connectors, AB/A+

Turns & Kinematics

Strategies, curvature/jerk limits, vehicle constraints

Obstacles & Geometry

Keepouts, non-convex/narrow corridors, no-go zones

Terrain & Ops

Slope-aware (Beta), entry/exit/staging, sequencing (Beta)

Optimization

Time/distance/fuel trade-offs, overlap/skip KPIs

Data I/O

Formats/adapters, bulk jobs/concurrency

Docs & Tools

Interactive API Reference

Complete OpenAPI documentation with live request testing, schemas, and examples

Explore

Note: No SDKs required

FAQ

Does it handle obstacles?

Yes—keepouts, buffers, corridor validation.

Can I use imperial units?

Metric units (meters/seconds) are supported now; imperial units support coming soon.

Are webhooks supported?

No; jobs use polling (every 5s).

How do I compare plans?

Use KPIs (time, distance, overlap, uncovered, turns).

Rate Limits & Support

Rate Limits

HTTP 429 when exceeded; implement exponential backoff.

Support

No formal SLAs. We review issues within 1 business day during North American business hours/days and do our best to resolve.

Email: [email protected]

Versioning & Deprecation

For breaking changes, we'll email impacted users and post updates on vergeag.com/developers.