Hanzo
OpenapiSeo

What each call on this surface costs, from the vendor's own list

Publishes what every call on this surface costs.

GET /v1/seo/rates

Addresshttps://api.hanzo.ai/v1/seo/rates
MethodGET
OperationseoRate
AuthAuthorization: Bearer $HANZO_API_KEY

Publishes what every call on this surface costs.

The numbers are read from the upstream's own published price list, not from a table kept here, so a price change on their side moves this card within the hour and moves what is debited with it. That is the whole of the pricing model: this surface resells at cost, and the cost is theirs to state.

A row has two numbers because a call has two costs: a flat charge for asking, and a charge per row returned. An op priced per request reports zero for the second, and for one priced per row the total is request + result x limit — which is the amount your balance is authorized against before the call, and roughly what you will be debited after it.

It is a read and it is free: asking what something costs must not require the balance that would pay for it. If the upstream cannot be reached the card comes back empty rather than stale — a price nobody can confirm is not a price.

Request

GET /v1/seo/rates takes no parameters and no body — the credential is the whole request.

Response

StatusBodyMeaning
200seoRateOutok

200 body — 4 fields.

FieldInTypeAlwaysDescription
ratesbodyseoCharge[]Rates is one row per op on this surface.
rates[].opbodystringOp is the operation id — seoKeyword, seoRank — so a line here and a tool in a model's list are the same name.
rates[].requestbodystringRequest is the flat charge for making the call, in USD, as an exact decimal string.
rates[].resultbodystringResult is the charge for each row returned, in USD, as an exact decimal string.

Failure carries the platform error shape — see Errors.

Examples

hanzo has no subcommand for this operation — the CLI serves only what cloud's live route table confirms. Use HTTP or an SDK.


SEO API · All Hanzo APIs · Interactive reference

How is this guide?

On this page