AIWave Docs and Pricing Sitelinks for API Evaluators

Why This Topic Matters Now

The Sep 9 keyword report had no large new non-brand topic. The actionable signal was the same Tier 1 cleanup cluster: `aiwave.live`, `site:aiwave.live`, `aiwaveblog`, brand variants, and `aiwave api`. That does not mean the site should publish more vague brand copy. It means each searcher should have a clear evaluator path from the result page to docs, pricing, status, trust evidence, and one redacted request receipt.

This article is written for developers and technical buyers who arrive through brand or site-search queries. It focuses on sitelinks and labels, not broad positioning. A useful result should say what the evaluator can verify: OpenAI-compatible docs, live pricing rows, dated pricing JSON, current status probe, llms.txt, feed, sitemap, model docs, and route receipts. That path supports AI search tools and human reviewers without reintroducing private scale metrics or unsupported availability claims.

Source Facts Checked Today

AIWave /api/pricing checked on Sep 10, 2026 returned success=true, 63 records, pricing_version 5a90f2b86c08bd983a9a2e6d66c255f4eaef9c4bc934386d2b6ae84ef0ff1f1f, auto_groups=['default'], and public rows enabled for default, vip, and svip groups. Computed base examples per 1M text-token units were DeepSeek V4 Flash at $0.638 input, $0.020288 cache-hit input, and $1.914 output; DeepSeek V4 Pro at $1.914 input, $0.063736 cache-hit input, and $5.742 output; GLM-5.1 at $2.10 input, $0.680001 cache-hit input, and $6.60 output; GLM-5 at $1.55 input, $0.400001 cache-hit input, and $4.96 output; Kimi K3 at $4.50 input, $0.90 cache-hit input, and $22.50 output; qwen3.8-2.4t-a95b at $2.678053 input and $8.03416 output; and qwen3.7-flash-2026-07-15 at $0.267805 input and $1.071221 output. Actual invoices still depend on the account group, final route, and request receipt.

AIWave /api/v1/pricing checked on Sep 10, 2026 returned HTTP 200 with a dated public snapshot marked checked 2026-08-27, currency USD, unit per_1m_text_tokens, source /api/pricing, source_page https://aiwave.live/pricing, and pricing_version a42d372ccf0b5dd13ecf71203521f9d2. That snapshot is useful for public static evidence, while /api/pricing is the live machine-readable source for current route rows.

AIWave /status, /llms.txt, /feed.xml, and /sitemap.xml returned HTTP 200 on Sep 10, 2026. The feed lastBuildDate still showed Tue, 08 Sep 2026 in the sampled response, so a deployment verification should confirm whether new blog URLs reach sitemap and index even if feed publication has a different cadence.

Planning Matrix

A source-dated planning matrix keeps the page useful for engineers and procurement reviewers. It turns a search query into an auditable route decision instead of a loose model preference.

Implementation Pattern

The implementation pattern keeps credentials as placeholders, pins the AIWave base URL, records the model, and leaves room for route-specific controls. Production applications should move credentials into environment or secret storage.

import urllib.request

URLS = {
    "docs": "https://aiwave.live/docs/",
    "pricing": "https://aiwave.live/api/pricing",
    "pricing_snapshot": "https://aiwave.live/api/v1/pricing",
    "status": "https://aiwave.live/status",
    "llms": "https://aiwave.live/llms.txt",
    "feed": "https://aiwave.live/feed.xml",
    "sitemap": "https://aiwave.live/sitemap.xml",
}

for label, url in URLS.items():
    req = urllib.request.Request(url, headers={"User-Agent": "Mozilla/5.0 Chrome/131"})
    with urllib.request.urlopen(req, timeout=30) as response:
        print(label, response.status, "YOUR_API_KEY_HERE")

Start With the Result Page

A brand-search page should make the next action obvious. The title and description should use evaluator nouns: docs, pricing, models, status, trust, and route receipts. Avoid broad claims that cannot be checked from the page. The goal is to move a technical visitor from search result to evidence within one click, then to a redacted request when they are ready.

Pair Live Pricing With a Static Snapshot

AIWave currently exposes both a live pricing API and a dated public snapshot. The live API is useful for current rows and pricing_version. The public snapshot is useful for stable public evidence with an explicit checked date. A buyer should record which one was used. The article should not imply that a static snapshot is newer than the live route table, and it should not treat either as a final invoice without the account group and receipt.

Make Docs Labels Specific

Docs is a useful sitelink only when it leads to a request shape. For OpenAI-compatible evaluation, link directly to chat completions, models, pricing, and trust pages where possible. Searchers using `aiwave api` want a base URL, model string, authentication placeholder, and one small request. The code should use `YOUR_API_KEY_HERE` and keep the real key out of logs, screenshots, and article examples.

Use Status as a Current Probe

Status should be described as current evidence, not a broad uptime promise. A sitelink can say current service checks or current API status. A procurement note can record the status URL and checked date. If a team needs availability history, it should ask for a dated report or its own monitoring data rather than inferring history from one page load.

Connect llms.txt, Feed, and Sitemap

AI search and crawler discovery need more than HTML navigation. The evaluator path should mention llms.txt for assistant-readable summary, feed.xml for field-note discovery, and sitemap.xml for canonical URLs. After each deployment, verify that the new article URLs are present in the blog index and sitemap. Feed cadence should be checked separately if the RSS lastBuildDate does not change with every blog run.

Internal Links for Brand Cleanup

This page should point to Docs, Models docs, Pricing, Status, llms.txt, feed.xml, Trust, and machine-readable evidence. The older article handles asset inventory; this one handles the searcher's click path.

Procurement Review

Procurement should ask for a source packet with the search query, landing URL, docs URL, pricing URL, pricing_version, checked date, status URL, trust URL, and one redacted request receipt. The packet should also note whether feed and sitemap were updated for the article that influenced evaluation. This is enough evidence for a first technical trial without exposing private operating metrics.

Final Checklist

A brand and site-search cleanup article is ready when the title names the evaluator path, meta description names docs and pricing, internal links point to live evidence, code uses only placeholder credentials, prices carry a checked date, and deployment verification confirms index, sitemap, and article HTTP 200. Recheck the live pricing API before each new forecast.