Pricing change
GPT-6 Astra passed
- Tokens
- 57,381
- Cost
- $0.51
Write the transactional notice Norvane Labs sends to Norvane API account holders whose organization has used the Web Search tool, telling them its pricing is changing. Cover the facts below.
Subject: Upcoming change to Web Search pricing on the Norvane API. Preview text: Web Search pricing update, effective October 15. Headline: Upcoming change to Web Search pricing.
Opening paragraph: starting October 15, 2026 at 12:00 PM PT, Web Search tool calls (tool id web_search, set in monospace) made through the Norvane API will be billed per item returned instead of per tool call. This aligns Web Search billing with how Norvane's search providers charge for read queries.
The prices, as one comparison table with three labelled columns: Billing unit, Current, and Effective October 15, 2026. One row per unit; a cell where the unit is not billed under that pricing shows an em dash.
- Per 1,000 tool calls: $5 current; not billed after the change
- Per 1,000 search results returned: not billed today; $5 after the change
- Per 1,000 full-page fetches: not billed today; $10 after the change
Below the table, a note that pricing for all other models and tools on the Norvane API remains unchanged.
What you need to do, as a short list under a small heading:
- No code changes are required; existing web_search calls keep working.
- Review the organization's current Web Search usage at https://norvane-email.s3.amazonaws.com/console/usage to estimate the effect of the change.
- To cap what a single call can return, set max_results (monospace) on the tool; the parameter is documented at https://norvane-email.s3.amazonaws.com/docs/tools/web-search.
- The full price list is at https://norvane-email.s3.amazonaws.com/docs/pricing.
Sign-off: The Norvane Team.
The footer links Console, Docs, and Support at https://norvane-email.s3.amazonaws.com/console, https://norvane-email.s3.amazonaws.com/docs, and https://norvane-email.s3.amazonaws.com/support, gives the postal address from tokens.json, the copyright line, and links Privacy and Terms at https://norvane-email.s3.amazonaws.com/privacy and https://norvane-email.s3.amazonaws.com/terms.
Use /world/norvane-email for brand chrome and CSS; this is the transactional family, and the header is the wordmark (assets.logo and assets.logoDark). Use the absolute HTTPS URLs from tokens.json; do not use /world/ paths as image src.
Dark mode should be supported.
Leave the HTML in output/email.html, a plain-text version in output/email.txt, and the subject in output/meta.json as {"subject": "..."}. Don't include From, To, or Date headers.