Read the docs

OFFPEAK JOURNAL

From quote to receipt.

OFFPEAK

Developers · Product preview

The proposed OFFPEAK API makes the spending boundary explicit. An application discovers a model, inspects a quote, authorizes a cap, and submits the request. This guide illustrates that flow without inventing a live endpoint or SDK.

Explore the planned request flow

The example stages below describe the intended pilot. They use pseudocode and cannot submit a paid request. The initial scope supports non-streaming text and EOA wallet authorization; direct x402 payments and delegated permissions are later work.

  1. {n}

    Pick a stage

    Explore the request lifecycle. These examples are planned API pseudocode, not a working SDK.

  2. {n}

    Choose the exact request

    Select a supported model revision, provide the prompt, and set the maximum output length. The initial catalog is pending validation.

  3. {n}

    Inspect the example

    // Planned API pseudocode
quote = requestQuote(model, prompt, outputLimit)
review(quote.rates, quote.maxCharge, quote.expiresAt)
  4. {n}

    Review the rates and maximum charge

    A quote is planned to expire after 30 seconds. A changed prompt requires a fresh quote. Capacity and funds are not reserved yet.

  5. {n}

    Know the boundary

    Accept only while the quote and capacity are valid. An unexpired quote may still encounter unavailable capacity.

    Read the docs ↗

Based on the supplied OFFPEAK version 1.0 product and build briefs. Read the overview ↗

← All articles