Get resolve

GET /v1/plan/resolve/{id}

Plan → · All API references → · Get started →

Address	`https://api.hanzo.ai/v1/plan/resolve/{id}`
Method	`GET`
Operation	`get_plan_resolve_by_id`
Auth	`Authorization: Bearer $HANZO_API_KEY`

Resolves one plan to everything a consumer of the catalog needs at once: its canonical entitlement block, the flat license-feature list a signed license carries, its billing reference, and the catalog it came from. The id may be the plan's id or its slug, and it is resolved against the caller's catalog, so a reseller's override wins over the canonical record. An id no catalog holds answers 404.

Request

1 field.

Field	In	Type	Required	Description
`id`	path	string	yes	ID is the plan's catalog id or slug — "dev", "max", "team", "rpc-growth".

Response

Status	Body	Meaning
`200`	plan.planResolution	ok
`default`	problem-details	refused

200 body — 5 fields.

Field	In	Type	Always	Description
`entitlements`	body	any	—	Entitlements is the canonical namespaced entitlement block derived from the plan's limits and addons — keys like "ai.tokens_per_min" and "world.api_rate_limit", where -1 means unlimited.
`id`	body	string	—	ID is the plan's catalog id.
`license_features`	body	string[]	—	LicenseFeatures is the flat, sorted feature list a signed license carries, derived from the entitlements — "ai.premium", "licensing.product:team".
`price_ref`	body	any	—	PriceRef is the plan's billing reference — currency, the recurring monthly and annual amounts, whether it prices per seat, its Stripe lookup key and its metered components.
`tenant_id`	body	string	—	TenantID is the catalog the record came from: "hanzo" for the canonical catalog, a reseller org for that reseller's override.

Failure carries the platform error shape — see Errors.

Examples

CLI

SDK

HTTP

MCP

hanzo plan resolve get <id>

.ts

.py

.go

.rs

.java

import { Configuration, PlanApi } from 'hanzoai';

const api = new PlanApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getPlanResolveById({ id: 'id' });

from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import PlanApi

client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = PlanApi(client).get_plan_resolve_by_id(id='id')

cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)

resp, _, err := client.PlanAPI.GetPlanResolveById(context.Background()).Execute()
if err != nil {
	return err
}

use hanzo_client::apis::{configuration::Configuration, plan_api};

let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();

let result = plan_api::get_plan_resolve_by_id(&cfg, Default::default()).await?;

import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.PlanApi;

ApiClient client = new ApiClient();
client.setBearerToken(System.getenv("HANZO_API_KEY"));

var result = new PlanApi(client).getPlanResolveById();

curl https://api.hanzo.ai/v1/plan/resolve/<id> \
  -H "Authorization: Bearer $HANZO_API_KEY"

MCP reaches plan through the plan tool, which names its 14 operations with its own verbs — this one among them, under a name only MCP declares. describe explains any of them:

curl -X POST https://api.hanzo.ai/v1/mcp \
  -H "Content-Type: application/json" \
  -d '{
       "jsonrpc": "2.0",
       "id": 1,
       "method": "tools/call",
       "params": {
         "name": "describe",
         "arguments": {
           "op": "list_plans"
         }
       }
     }'

Plan API · All Hanzo APIs · Interactive reference

Was this page useful?

PreviousList regions NextList schema