Developer Documentation

Changelog

Changes that affect developers, newest first. The API is versioned by its /v1 prefix: additive changes ship without a version bump, so ignore response fields you don't recognise.

  1. MCP server open to every developer account

    Any developer account with a card on file can enable MCP in the developer dashboard and call Augure models as a tool from Claude Code. See the MCP server docs.

  2. rosedale-1: use reasoning_effort "low" for fast answers

    rosedale-1 has no true thinking-off mode. A "none" is now served as "low", which answers with a very short thinking phase. "minimal" and "medium" do not reduce cost on this model. No change for other models.

  3. tofino-2.5 retired

    A developer key naming tofino-2.5 now gets HTTP 400 model_retired. The gpt-4o-mini and gpt-3.5-turbo aliases are served by tofino-3, and their responses carry _augure.retired.

  4. ossington-3 retirement announced for October 15, 2026

    ossington-3 is replaced by rosedale-1. Until the date, its responses carry _augure.deprecation; from the date, developer keys get model_retired. model: "auto" now routes general requests to rosedale-1. See Models and lifecycle.

  5. Lower ossington-4-1 output price; image reading in Calgary

    ossington-4-1 output drops from $8.00 to $6.00 per million tokens (input unchanged at $2.50). Image reading now runs on Augure-operated GPU infrastructure in Calgary, Alberta; those responses report inference_region: ca-ab-calgary. Keys with a Canada-only residency policy are never failed over and get 503 residency_unavailable instead.

  6. tofino-3 launched; tofino-2.5 retirement announced

    tofino-3 is the light tier: 256K context, 16,384-token output cap, thinking always off, served in Canada with no failover outside Canada. tofino-2.5 was announced for retirement on September 19, 2026.

  7. reasoning_effort is honoured on the reasoning models

    ossington-5, ossington-4, ossington-4-1 and rosedale-1 accept OpenAI-style reasoning_effort. "none" turns the thinking channel off, which is much faster on short mechanical tasks. Invalid values return a 400.

  8. Reliable JSON output on the reasoning models

    response_format (json_object or json_schema) could return malformed JSON on the reasoning models. It is now enforced with a directive that includes your schema. Parse content, and validate and retry once on a parse failure.

  9. ossington-5 available on the API

    The newest reasoning model, fast and strong at code. 256K context. Listed in GET /v1/models.