BlockRun
Get an API key
Back to Models

o1 API

openai/o1

openai

Advanced reasoning model for complex tasks

Code Examples

from blockrun_llm import LLMClient

client = LLMClient()  # Uses BLOCKRUN_WALLET_KEY (never sent to server)
response = client.chat("openai/o1", "Hello!")
import { LLMClient } from '@blockrun/llm';

const client = new LLMClient();  // Uses BLOCKRUN_WALLET_KEY (never sent to server)
const response = await client.chat('openai/o1', 'Hello!');
curl -X POST https://blockrun.ai/api/v1/chat/completions \
  -H "Content-Type: application/json" \
  -H "PAYMENT-SIGNATURE: <payment_header>" \
  -d '{
    "model": "openai/o1",
    "messages": [{"role": "user", "content": "Hello!"}],
    "max_tokens": 1024
  }'

On BlockRun since 2026-02-21. Measured on BlockRun: fewer than 100 calls to o1 this week — price only.

Pricing

Input$15.00 / 1M tokens
Output$60.00 / 1M tokens
Context200K tokens
Max Output100K tokens

No markup on official OpenAI rates; $0.001 fee per call.

Payment

Network
Base
Currency
USDC
Protocol
x402

Pay per request with USDC on Base. No subscription required.

Try It

Send a message to try o1

Connect your wallet to enable payments

About OpenAI o1

o1 is a reasoning and coding model from OpenAI with a 200K-token context window and up to 100K tokens of output per call. It is billed per token at the provider's list rate, with no markup on chat tokens. It is served through BlockRun's OpenAI-compatible API, so it can be called without an account, an API key, or a subscription.

Use o1 for

  • Multi-step reasoning: planning, analysis and math that need thinking before an answer
  • Coding agents: writing, reviewing and refactoring code across a repository
  • Chat assistants and agents that answer, summarise and draft

What it costs

o1 is billed per token. The underlying rates are $15.00 per million input tokens and $60.00 per million output tokens with no platform margin on chat tokens; only a small per-transaction fee covering on-chain settlement is added on top, and the resulting price is quoted in the 402 before you pay. You are charged for the tokens a request actually consumes — there is no monthly commitment and no unused balance to forfeit. With a context window of 200,000 tokens and up to 100,000 tokens of output, a single call can carry a substantial working set.

Specifications

Context window
200,000 tokens
Maximum output
100,000 tokens
API compatibility
OpenAI-compatible
Payment
USDC via x402
Categories
chat, reasoning, coding

Calling it from your code

Pass openai/o1 as the model field. Because the endpoint mirrors the OpenAI chat completions schema, any existing OpenAI client works by changing the base URL — streaming, tool use, and multi-turn messages all behave the same way.

The first request returns a 402 carrying the exact price; a signed retry runs it, and client libraries fold the two into one call — how the payment works. See the documentation for request and response shapes, the LLM API page for every model on this endpoint, or browse the full catalog of 90 chat models to compare alternatives.

o1 or another model

The closest alternatives by price that do the same kind of work. Each is called on the same endpoint with the same request, so comparing two is a one-line change.

ModelPriceContext
OpenAI o1 (this page)$15.00 in / $60.00 out per 1M200K context
Anthropic Claude Fable 5$10.00 in / $50.00 out per 1M1M context
Anthropic Claude Fable 5.1$10.00 in / $50.00 out per 1M1M context
OpenAI GPT-6 Astra$10.00 in / $50.00 out per 1M1.05M context

o1 API questions

How much does the o1 API cost?

$15.00 per million input tokens and $60.00 per million output tokens, with cached input at $7.50 per million. There is no markup on chat tokens; a small per-call transaction fee is added, and the price is quoted in the 402 before the call runs.

What is o1's context window?

200,000 tokens of context, with up to 100,000 tokens of output per call.

Is the o1 API OpenAI-compatible?

Yes. Send an OpenAI chat-completions request with "model": "openai/o1" to the BlockRun endpoint. An existing OpenAI client works by changing the base URL; streaming and multi-turn messages behave the same way.

Do I need an API key to use o1?

No. Each request carries its own payment, so an agent or script can call o1 with no account and no key. Teams that prefer one can use an API key with card or invoice billing instead.

What happens if o1 is unavailable?

A request that fails is not charged.

Related models

Every model on BlockRun is reached through the same endpoint and the same payment flow, so switching is a one-line change to the model field. These are the closest alternatives to o1:

Two ways to run this

Get an API key

Sign in, get a key, and call the same endpoints with usage billed to your account. For teams that want one invoice instead of one wallet.

Get an API key 

Or let your agent pay per call, in USDC

No account, no API key. Three steps, and the last one is the request this page is about.

  1. 01
    Point your agent at BlockRun

    Install ClawRouter, or add the BlockRun MCP server to Claude Code, Cursor, Codex or OpenClaw. Any OpenAI-compatible client works too — change the base URL, nothing else.

    curl -fsSL https://blockrun.ai/ClawRouter-update | bash
  2. 02
    Fund a wallet with USDC

    Send USDC to a wallet on Base, Solana or Arc. There is no account to create and no API key to issue: the wallet is the account, and it pays per call.

  3. 03
    Call o1

    The first call returns HTTP 402 with the exact price, your agent signs it, and the answer comes back. Payment settles on-chain; nothing is charged if the call fails.

    curl -X POST https://blockrun.ai/api/v1/chat/completions \
  -H "Content-Type: application/json" \
  -d '{"model": "openai/o1", "messages": [{"role": "user", "content": "Hello!"}]}'
ClawRouter setup →How paying per call works →

Explore everything on BlockRun