← News & Changelog

3 entries on this day.

  1. Pricing

    JPY prices for AP packs move to the invoice lane rate on Sep 30; USD prices are unchanged

    AP packs can be bought from two sellers: AICU Inc. in USD, and AICU Japan K.K. in JPY. The JPY lane exists for customers who need a Japanese qualified invoice (適格請求書), pay by bank transfer against an invoice, or commit an annual budget in advance. From 2026-09-30 05:00 UTC the JPY prices are set from a billing rate of 1 USD = ¥180: Pack S ¥1,700 → ¥1,800 (100,000 AP), Pack M ¥8,400 → ¥9,000 (500,000 AP), Pack L ¥33,500 → ¥36,000 (2,000,000 AP). USD prices do not change: $10.00 / $50.00 / $200.00. Validity stays 24 months. From now on the JPY price is always at least 10% above the USD price converted at the market rate, and we check it every week against the published USD/JPY table. That gap is the price of the invoice lane, not a currency surcharge — if you do not need a qualified invoice, the USD lane is the cheaper one and stays open. Announced nine days ahead, per our price-revision rule (increases get 7 days’ notice and take effect on a Wednesday at 05:00 UTC). The same notice retires two old JPY-only routes that priced the same AP *below* the USD lane: the legacy AP packages (POST /v1/stripe/checkout, ¥100 / ¥980 / ¥9,500) and the monthly JPY subscription plans (POST /v1/stripe/subscribe). Both now return HTTP 410 and point at the pack catalogue. No account was subscribed to either.

    AP packs ↗
  2. Model

    New image models: GPT Image 2.5 Flare and Sunburst are serving now

    gpt-image-2.5-flare is the one to reach for by default. It is better than the 2 series and takes about half the time (typically 85 s against 170 s), and it keeps reference-image support, so a character stays the same character across images. gpt-image-2.5-sunburst trades time for control: finer editing, typically 200 s. Sizes are 1024×1024, 1536×1024 and 1024×1536. Flare at 1024×1024 is 700 AP on low, 1,600 AP on medium and 6,400 AP on high; the wide and tall sizes are 1,300 / 2,300 / 5,100 AP. Every price is in GET /v1/models — read it from there rather than keeping a copy. Both models regularly run past 100 seconds, which is longer than the edge will hold a connection: if the HTTP call ends in 524, the image is not lost. Keep the id from the response (or the X-AICU-Image-Id header when streaming) and collect it with GET /v1/images/status/{id}. Use the id, not GET /v1/images/recent, whenever more than one generation can be in flight on the same key.

    Image API ↗
  3. Feature

    Jev: get a typed answer back with a confidence value, not prose

    POST /v1/jev sends your state and your questions to Jev (TypeSafe AI) and returns typed answers with a confidence value — a boolean, a number or a choice, in the shape you asked for. No prompt engineering to keep the model from replying in paragraphs, and no parsing of free text at your end. It is the piece you want when a decision sits inside your control flow: should this be escalated, is this record complete, which of these three queues. It uses your existing llm scope, so keys that already work need no change, and it is fast enough to sit on a request path. Billing is per call and small — a two-question decision costs single-digit AP.

    API reference ↗