Spiral gives your agent every tool with one account. Browse the tools →

Muse Code · Developer

How to Use OpenAI model specifications in Muse Code

Returns an OpenAI model's documented specifications, including context window, knowledge cutoff, and supported endpoints. Use it to check whether a specific model fits your workload.

Prompts to try with OpenAI model specifications in Muse Code

Copy an example into Muse Code, or ask in your own words.

Use OpenAI model specifications for gpt-6.2-sol and check whether this project's document chunking and output limits fit the documented model limits.

OpenAI model specificationsMuse Code
Try asking
  • Use OpenAI model specifications to look this up and give me the result as a table. Save the result in ./assets.

  • Pull the latest numbers from OpenAI model specifications and tell me what changed since last week.

  • Check OpenAI model specifications and summarize what you find in three bullet points.

  • Pull the newest data from OpenAI model specifications and give me the result as a table.

How to set up OpenAI model specifications in Muse Code

Pick the way that suits you. Each takes about two minutes.

Use Spiral's MCP server

  1. Install Muse Code
    curl -fsSL https://dev.meta.ai/install.sh | bash
  2. Ask Muse to add the server

    Start muse and ask:

    Add the Spiral MCP server at https://api.spiral.ai/mcp
  3. Sign in

    In your terminal, run:

    muse mcp login spiral

Use the Spiral skill

  1. Send Muse Code this message

    Your agent reads Spiral's skill and sets itself up.

    set up https://spiral.ai/SKILL.md
  2. Sign in or paste a key

    Approve Spiral in the browser, or give the agent a key from the console.

Use the Spiral CLI

  1. Install and sign in

    Installs the Spiral CLI, signs you in and adds its skill to your coding agents.

    npx -y spiral-cli@latest init

Call the Spiral API

  1. Create an API key

    In the console, under API keys.

  2. Run OpenAI model specifications

    One request; the result comes back by polling or a webhook.

    curl https://api.spiral.ai/v1/runs \
      -H "Authorization: Bearer $SPIRAL_API_KEY" \
      -H "Content-Type: application/json" \
      -H "Idempotency-Key: $(uuidgen)" \
      -d '{
        "provider": "alexandria",
        "model": "developers-openai-com/developer-docs/get_model",
        "input": {
          "model": "<model>"
        }
      }'

Then paste one of the prompts above: Muse Code finds OpenAI model specifications on Spiral, shows the price and runs it.

OpenAI model specifications providers and prices

Spiral runs OpenAI model specifications through Alexandria. Open a card for today's price, with every fee included.

AlexandriaDeveloper
OpenAI developer docs · Get model
developers-openai-com/developer-docs/get_model

What can you do with OpenAI model specifications in Muse Code?

Produce an OpenAI integration review tied to the project's actual requests and model choices. A coding agent can compare those choices with official specifications, reference fields, guides, and dated announcements before proposing edits.

Plan a Chat Completions migration

Build a migration checklist from dated API changes, request and response definitions, model capabilities, retirement notices, and published billing categories. Link each proposed code change to the relevant guide.

Write a model selection decision

Evaluate models for a document extraction application using catalog entries, specifications, endpoint definitions, lifecycle notices, billing units, and implementation guides. Include recent announcements that affect the decision.

Check a Responses API implementation

Compare a request builder and response parser with the documented method, then read the guides for the features the application uses. Check model specifications and dated changes when behavior depends on the selected model.

Prepare a release readiness review

Before shipping an OpenAI integration, review its selected models, documented limits, API schemas, lifecycle status, and billing assumptions. Use the changelog and guides to identify documentation changes that need engineering review.

Check workload sizing assumptions

Compare candidate models' context, input, and output limits with the application's expected document sizes. Review the published token billing categories and relevant guides before building an estimate.

Prepare retirement handoff briefs

Turn announced shutdowns into engineering handoff briefs with affected model IDs, proposed replacements, specification differences, schema checks, and billing considerations. Include migration guides and related announcements.

Investigate request compatibility errors

Check a failing OpenAI request against the method reference and selected model's specifications. Read the relevant guide and dated announcements to identify documented compatibility changes.

Questions about OpenAI model specifications in Muse Code

Can Muse Code use OpenAI model specifications?

Yes. Add Spiral to Muse Code as an MCP server, and Muse Code can find and run OpenAI model specifications like any built-in tool.

How much does OpenAI model specifications cost in Muse Code?

$0.00873 per call. You pay from your Spiral balance as you go, with no subscription, and a failed run is not charged. Your Muse Code plan is separate.

Do I need an Alexandria account to use OpenAI model specifications in Muse Code?

No. Spiral runs OpenAI model specifications on its own Alexandria account. You sign in to Spiral once and never paste a key.

How long does it take to set up OpenAI model specifications in Muse Code?

About two minutes: install Muse Code, then ask Muse to add the server, then sign in.

Does Muse Code wait while OpenAI model specifications runs?

OpenAI model specifications runs in the background. Muse Code starts the run, checks on it and gives you the json when it's ready.

What public material does this source cover?

OpenAI's documentation service provides read-only search and page content. The page reader covers official guides, references, and cookbook pages.

Does the model catalog include deprecated models?

Yes. OpenAI explicitly includes deprecated models in its full catalog, so a listed model still needs a lifecycle check.

How detailed are the model specifications?

They distinguish context capacity from input and output limits. For example, GPT-6.2 Sol lists a 1,050,000-token context window, 922,000 maximum input tokens, and 128,000 maximum output tokens.

Are API announcements dated?

Yes. The changelog's November 17, 2026 entry identifies GPT-6.2 Astra and GPT-6.2 Sol and tags the Responses and Chat Completions APIs.

Can an agent read a specific part of a guide?

Yes. The documentation page reader provides Markdown content with an outline and section reads for guides, references, and cookbook pages.

Get started

Start using OpenAI model specifications in Muse Code

One Spiral account for every tool your agent needs. No subscription; you pay per run.

Paste this into Muse Code:

Set up Muse Code

set up https://spiral.ai/SKILL.md
Are you an AI agent? See setup options