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
| Address | https://api.hanzo.ai/v1/seo/rates |
| Method | GET |
| Operation | seoRate |
| Auth | Authorization: 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
| Status | Body | Meaning |
|---|---|---|
200 | seoRateOut | ok |
200 body — 4 fields.
| Field | In | Type | Always | Description |
|---|---|---|---|---|
rates | body | seoCharge[] | — | Rates is one row per op on this surface. |
rates[].op | body | string | — | Op is the operation id — seoKeyword, seoRank — so a line here and a tool in a model's list are the same name. |
rates[].request | body | string | — | Request is the flat charge for making the call, in USD, as an exact decimal string. |
rates[].result | body | string | — | Result 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.
import { Configuration, SeoApi } from 'hanzoai';
const api = new SeoApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.seoRate();from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import SeoApi
client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = SeoApi(client).seo_rate()cfg := cloud.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := cloud.NewAPIClient(cfg)
resp, _, err := client.SeoAPI.SeoRate(context.Background()).Execute()
if err != nil {
return err
}use hanzo_cloud::apis::{configuration::Configuration, seo_api};
let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();
let result = seo_api::seo_rate(&cfg, Default::default()).await?;import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.SeoApi;
ApiClient client = new ApiClient();
client.setRequestInterceptor(b -> b.header("Authorization", "Bearer " + System.getenv("HANZO_API_KEY")));
var result = new SeoApi(client).seoRate();The method above is the one at the current release of the document. [email protected] (npm) and [email protected] (PyPI) were generated from an earlier release, where this operation carried a different id, so it spells the method differently — regenerating the clients is what makes the two agree. SDKs →
curl https://api.hanzo.ai/v1/seo/rates \
-H "Authorization: Bearer $HANZO_API_KEY"The door declares no tool for seo — tools/list on https://api.hanzo.ai/v1/mcp names the products it does reach. Use HTTP or an SDK.
How is this guide?