Planning Credits

Path planning is metered in credits. A planning credit is consumed when you create a path plan: tracks and routes generated for one field boundary and one operation. We call that a planning session. The same credit applies whether you plan in the Launch Pad web app or through the API.

1 credit = 1 planning session

One field boundary, one operation. Every adjustment you make while refining that plan is included in the same credit. You are not charged again for tuning the result.

What a planning session includes

Adjusting inputs and re-running the plan for the same field and operation: equipment, swath width, headland passes, preferred bearing, turn strategy, and advanced options.
Generating and tweaking routes within the session. You can keep up to 5 routes per plan. This is a soft guideline, not a hard cap.
Comparing results with KPIs (time, distance, overlap) before you commit to a plan.

Updating a plan (planned): We may add support for updating an existing path plan in place. An update would not consume a new credit, but it is restricted to effectively the same field, boundary, and operation. Updates are intended for tweaking parameters, not for regenerating a brand-new plan. This capability is on our roadmap and may not be available everywhere yet.

Intended use and reasonable limits

Credits are priced for agricultural use cases. The following are reasonable guidelines for a single planning session:

• Field size typically ranges from one to two quarter sections, up to a full section (about 640 ac / 260 ha) per plan.
• A boundary may contain a few parts (a multi-polygon for one field). This is supported and fully expected.
• One operation per plan. Planning a different operation on the same field is a separate planning session.

What counts as abuse

A planning session is meant to plan one real field and operation. The following defeat that intent and are not permitted:

Swapping the boundary to a completely different field and then re-planning as if it were the same plan, to avoid spending a credit.
Packing what are effectively multiple fields into a single boundary to plan them all on one credit. A few parts of one field is fine, several distinct fields is not.
Using the update capability (where available) to re-plan a different field, boundary, or operation rather than to tweak parameters on the same plan.
APIScripting or automating the planning flow to mass-produce many distinct plans from one credit, or otherwise working around credit deduction, rate limits, or the soft route guideline.
Submitting boundaries far larger than a reasonable single field to cover many fields' worth of area in one call.

Fair use: These limits are guidelines. Verge Ag determines, at its sole discretion, what constitutes reasonable use versus abuse, and may adjust limits, decline requests, charge for additional credits consumed, or suspend access where abuse is detected.

Credits, billing accounts, and teams

Credits are held by a billing account, not by an individual user, so a team can share one pool:

• Each user has a billing account, and a billing account can be assigned to multiple users.
• Users can independently belong to multiple organizations (companies).
• As long as a user's assigned billing account has credits, that user can plan in any organization they have access to.

Buying credits: Buy credits in the Launch Pad web app, where you can view current package prices. If you use the API, you generate keys in the same place (your Profile). See the Planning Credits guide for a step-by-step walkthrough.