30 days free. No credit card. Full access from the moment you connect your site.

Start free trial

GeoDirectory List Pricing Packages

geodirectory/list-packages lists the pricing packages for a listing type: price, billing interval, trial terms, recurring settings, and which one is the default.

Requires the Pricing Manager add-on. Without it there are no packages, and the ability reports that rather than returning nothing.

At a glance

Abilitygeodirectory/list-packages
ToolsetGeoDirectory — toolset/geodirectory
GroupGeoDirectory › Pricing Packages
RequiresAcrossAI Pro, plus GeoDirectory active on the site
Capabilitymanage_options
SafetyRead-only — changes nothing
RepeatableIdempotent — running it twice leaves the same result
Ships inAcrossAI Pro 0.9.16 and later

How it works

Packages are per listing type, which is easy to forget on a multi-directory site — the restaurant packages and the venue packages are different sets with different defaults.

The default is the package new listings land on, so it is the one that decides what a submission costs when nobody chose.

The include_meta flag adds each package’s limits, excluded fields and featured or private flags. That is a larger response and it is the part that matters before editing listings, because the excluded-fields list is what silently drops writes.

Disabled packages are excluded by default. They still exist and listings can still be on them — a package disabled for new signups does not move its existing listings — so an audit wants them included.

Read this before assigning a package or editing package-gated fields.

Input

NameTypeRequiredWhat it is
post_typestringNoListing type, for example gd_place. Defaults to the site default. See geodirectory/get-directory-overview for the valid values.
package_idintegerNoFetch a single package instead of listing.
include_metabooleanNoInclude limits, excluded fields and the featured and private flags. Larger response.
statusstringNoWhether to include disabled packages.

What comes back

NameTypeWhat it is
packagesarrayEach package with its pricing, terms and flags.
successbooleanWhether the call completed.
messagestringA one-line summary of what happened, suitable for showing a human.
error_codestringPresent only on failure — a stable machine-readable reason, such as a missing field, a wrong field type or an unmet confirmation.

Example

Ask your assistant:

What listing packages do we sell?

It resolves to one call:

{
  "ability": "geodirectory/list-packages",
  "parameters": {
    "include_meta": true
  }
}

Worth knowing

  • Packages are per listing type.
  • The default decides what a submission costs when nobody chose.
  • The excluded-fields list is what silently drops listing writes.
  • Disabled packages still hold their existing listings.

Related abilities


Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager

Browse the rest: Every ability, by category


Keep reading