Changelog

Instant Wallet Creation - Users can now create ephemeral wallets instantly without providing email, phone, or social accounts. Perfect for demos, testing, or onboarding new users to your dApp.

// Create a guest wallet instantly
const response = await fetch(
  "https://api.thirdweb.com/v1/auth/complete",
  {
    method: "POST",
    headers: {
      "x-secret-key": "your-secret-key",
      "Content-Type": "application/json",
    },
    body: JSON.stringify({
      method: "guest",
      sessionId: "optional-session-id", // Auto-generated if not provided
    }),
  },
);
 
const { walletAddress, token } = await response.json();

• Zero Friction - No user information required
• Instant Setup - Wallets created in milliseconds
• Session Support - Optional sessionId for temporary persistence
• Full Functionality - Sign messages, send transactions, interact with contracts
• Easy Migration - Users can upgrade to permanent accounts later

• Demo Applications - Let users try your dApp immediately
• Testing Environments - Quick wallet creation for integration tests
• Onboarding Flows - Reduce barriers for new users
• Temporary Sessions - Perfect for short-lived interactions

• POST /v1/auth/complete - Create guest wallet
• GET /v1/wallets/me - Get wallet info (with Bearer token)
• All existing wallet operations work with guest wallets

Ready to reduce onboarding friction? Get started with guest auth →

This guide helps you migrate from the legacy Nebula API (nebula-api.thirdweb.com/chat) to the new thirdweb AI Chat API (api.thirdweb.com/ai/chat).

• Old URL: https://nebula-api.thirdweb.com/chat
• New URL: https://api.thirdweb.com/ai/chat

fetch("<https://nebula-api.thirdweb.com/chat>", {
  method: "POST",
  headers: {
    "Content-Type": "application/json",
    "x-secret-key": "your-secret-key",
  },
  body: JSON.stringify({
    message: "Send 0.01 ETH to vitalik.eth",
    stream: false,
    session_id: "your-session-id",
    context: "{ chainIds: [1]; walletAddress: '0x123...'; }",
  }),
});

fetch("<https://api.thirdweb.com/ai/chat>", {
  method: "POST",
  headers: {
    "Content-Type": "application/json",
    "x-secret-key": "your-secret-key",
  },
  body: JSON.stringify({
    context: {
      chain_ids: [1],
      from: "0x123...",
      session_id: "your-session-id", // Optional
    },
    messages: [
      {
        role: "user",
        content: "Send 0.01 ETH to vitalik.eth",
      },
    ],
    stream: false,
  }),
});

Change your base URL from:

<https://nebula-api.thirdweb.com/chat>

to:

<https://api.thirdweb.com/ai/chat>

Convert the single message field to a messages array:

Old format:

message: "Your message here";

New format:

messages: [
  {
    role: "user",
    content: "Your message here",
  },
];

Supported roles:

• user - Messages from the user
• assistant - Messages from the AI
• system - System messages for context

Old format (string):

context: "{ chainIds: [1, 137]; walletAddress: '0x123...'; }";

New format (object):

context: {
  chain_ids: [1, 137],  
  from: "0x123...",  
  session_id: "optional-session-id"
}

• Session ID is now optional and nested within the context object
• If not provided, a new session will be created automatically
• Sessions enable conversation continuity

function migrateToNewAPI(oldRequest) {
  // Parse old context string  const contextString = oldRequest.context;  const contextData = parseContextString(contextString); // Implement this helper
  return {
    context: {
      chain_ids: contextData.chainIds,
      from: contextData.walletAddress,
      session_id: oldRequest.session_id,
    },
    messages: [
      {
        role: "user",
        content: oldRequest.message,
      },
    ],
    stream: oldRequest.stream || false,
  };
}

• Standard Chat Format: Follows industry-standard conversational AI patterns
• Better Message History: Support for multi-turn conversations with role-based messages
• Structured Context: Type-safe object format instead of string parsing
• Enhanced Session Management: More flexible session handling
• Future-Proof: Aligned with modern chat API standards

1. Update your endpoint URL
2. Transform your request payload structure
3. Test with a simple message first
4. Verify session continuity works as expected
5. Test complex scenarios with multiple messages

We’ve added an OpenAI-compatible AI Chat endpoint specialized for blockchain interactions, powered by thirdweb’s 't0' model. It can query live on-chain data, analyze transactions, prepare contract calls, swaps, and more via a single /ai/chat call.

Docs: https://portal.thirdweb.com/ai/chat
Playground: https://playground.thirdweb.com/ai/chat
API reference: https://api.thirdweb.com/reference#tag/ai/post/ai/chat

• Realtime chain data: balances, prices, metadata, transaction & contract insights.
• Prepare on-chain operations: contract writes, native/token transfers, swaps, and deployments. Generates call data & parameters.
• Actionable outputs: returns structured actions (e.g., sign_transaction) you can pass to your signing/execution flow.
• Context-aware: include wallet + chain context for targeted answers.
• OpenAI-compatible: works with standard Chat Completions clients using model: "t0".

1. Explore blockchain data — find interesting contract and tokens, analyze transactions, follow transfers, etc
2. Wallet assistant — “Send 10 USDC on Base to vitalik.eth”, "Swap 0.1 ETH to USDT on Arbitrum", etc
3. Token launcher — Create tradeable tokens with natural language, generate images for the metadata.

const res = await fetch("https://api.thirdweb.com/ai/chat", {
  method: "POST",
  headers: {
    "content-type": "application/json",
    "x-secret-key": process.env.THIRDWEB_SECRET_KEY!, // project secret
  },
  body: JSON.stringify({
    messages: [
      {
        role: "user",
        content: "Transfer 0.01 ETH to vitalik.eth on Base",
      },
    ],
    stream: false,
    context: {
      from: "0xYourWallet",
      chain_ids: [8453], // Base
    },
  }),
});
const json = await res.json();
// json.actions[0] may be { type: "sign_transaction", data: { to, value, data, chainId } }

from openai import OpenAI
 
client = OpenAI(
    base_url="https://api.thirdweb.com/ai",           # uses OpenAI-compatible interface
    api_key="YOUR_TW_SECRET_KEY",                  # maps to x-secret-key
)
 
resp = client.chat.completions.create(
    model="t0",
    messages=[{"role": "user", "content": "What's my USDC balance?"}],
    stream=False,
    extra_body={ "context": { "from": "0xYourWallet", "chain_ids": [8453] } },
)
print(resp)

{
  "message": "I've prepared a native transfer. Do you want to execute it?",
  "session_id": "123",
  "request_id": "456",
  "actions": [
    {
      "type": "sign_transaction",
      "data": {
        "chainId": 8453,
        "to": "0x...",
        "value": "10000000000000000",
        "data": "0x"
      },
      "source": "model"
    }
  ]
}

Docs: https://portal.thirdweb.com/ai/chat
Playground: https://playground.thirdweb.com/ai/chat
API reference: https://api.thirdweb.com/reference#tag/ai/post/ai/chat

We’ve expanded the Thirdweb API with three new endpoints that make it easier than ever to swap, send, and execute payments in just a few calls. Whether you’re moving tokens across chains, building custom checkout flows, or resuming a previously prepared payment, these new endpoints give you full control over the payment lifecycle — all with the same developer-friendly API.

Instantly swap between tokens and across chains using any thirdweb wallet via POST /v1/payments/swap. Use the exact parameter to specify whether your amount is the input (pay) or output (receive) side.

curl -sS -X POST "https://api.thirdweb.com/v1/payments/swap" \
  -H "Content-Type: application/json" \
  -H "x-secret-key: <YOUR_SECRET_KEY>" \
  -d '{
    "from": "0xYOUR_WALLET",
    "exact": "input",                 
    "tokenIn":  { "address": "0xaf88d065e77c8cC2239327C5EDb3A432268e5831", "chainId": 42161, "amount": "1000000" },
    "tokenOut": { "address": "0xFd086bC7CD5C481DCC9C85ebE478A1C0b69FCbb9", "chainId": 42161, "minAmount": "990000" }
  }'

API Reference →

Create an end-to-end payment that can bridge and/or swap under the hood with POST /v1/payments. Perfect for P2P transfers, checkouts, and payouts when you want a single call that returns the prepared steps to execute. Supports metadata and webhooks.

curl -sS -X POST "https://api.thirdweb.com/v1/payments" \
  -H "Content-Type: application/json" \
  -H "x-secret-key: <YOUR_SECRET_KEY>" \
  -d '{
    "name": "Course",
    "description": "The complete JS course",
    "imageUrl": "https://example.com/course.png",
    "recipient": "0xMERCHANT_WALLET",
    "token": { "address": "0xaf88d065e77c8cC2239327C5EDb3A432268e5831", "chainId": 42161, "amount": "1000000" }
  }'

API Reference →

Submit a previously created payment with POST /v1/payments/{id}. Use this to continue processing a payment you created earlier (for example after client-side signing/approval), while preserving the same payment ID for tracking and webhooks.

curl -sS -X POST "https://api.thirdweb.com/v1/payments/<ID>" \
  -H "Content-Type: application/json" \
  -H "x-secret-key: <YOUR_SECRET_KEY>" \
  -d '{ "from": "0xBUYER_WALLET" }'

API Reference →

We've added Stargate to our growing list of supported providers in thirdweb Payments. This unlocks a number of chains such as Fuse, Kaia, and more. This will also augment all existing routes to provide better prices (when possible).

thirdweb Payments are built with a "single input" philosophy, meaning you will only need to hold one input token to complete a payment. Stargate and other LayerZero-based bridges require fees to be paid in the native token, which normally breaks the "single input" philosophy. We've rolled Stargate's fees into the input token, allowing for even LayerZero bridges to be used with a single input token.

Try Stargate and all other payments in the HTTP API or the SDK.

The thirdweb API is your unified toolkit for building next-generation blockchain apps. From AI-powered smart contract interactions to seamless authentication across 13+ providers, it delivers everything you need in one place.

Build Web3 apps with Web2-level simplicity—no more juggling multiple services or fragmented workflows. Everything you need is streamlined into a consistent, reliable interface.

One universal flow for all modern authentication methods:

• 13+ OAuth Providers – Google, Apple, Discord, GitHub, X, Coinbase, Farcaster, and more
• Modern Methods – SMS, Email, Passkeys, SIWE
• Custom – JWT tokens, custom endpoints

POST /v1/auth/initiate
POST /v1/auth/complete

Result: User wallet + JWT token, ready to use.

• Authentication – Universal flow for all methods
• Wallets – Balances, transactions, NFTs, signing, transfers
• Contracts – Deploy, read, write, manage
• Transactions – Advanced management & monitoring
• Payments – Token swaps, hosted checkout
• Tokens – Discovery & ownership tracking
• AI – Natural language blockchain interactions

AI Blockchain Control

POST /ai/chat

Deploy contracts, run DeFi strategies, or send transactions in plain English.

Payment Infrastructure
Optimal token swaps, hosted checkouts, ETH/ERC-20/NFT support.

Smart Contract Tools
Batch operations, auto-deploy, real-time data, rich metadata.

Cross-Chain Ready
Query balances, send transactions, and deploy on any chain.

• Gaming & NFTs – In-game trading, marketplaces, multi-chain economies
• DeFi & Payments – Cross-chain payments, automated strategies
• Enterprise – Corporate wallets, supply chain tracking, tokenized rewards
• Consumer Apps – Social tokens, creator platforms, subscriptions

• Docs: api.thirdweb.com/reference
• Quick Start: Auth, Smart Contracts, AI, Payments

Build faster. Scale easier. Launch smarter with the thirdweb API.

Arbitrum Stylus brings a second, WebAssembly (WASM) virtual machine to every Arbitrum chain, so you can write contracts in Rust (or C/C++) while staying 100 % interoperable with existing Solidity code.

Under the hood, Stylus executes WASM thousands of times faster than the EVM, so transactions are metered in a new, much-smaller unit called ink rather than gas — translating to dramatic fee savings for compute- or memory-heavy logic.

To take advantage of the interoperability and fee savings, we are working with Arbitrum to bring you thirdweb contract developer tooling to Stylus

• Airdrop tokens pre-built smart contracts available on Explore
  • Airdrop ERC-20
  • Airdrop ERC-721
  • Airdrop ERC-1155
• ERC-20, ERC-721, and ERC-1155 token templates written in Stylus available to deploy through the CLI.

| Learn how to deploy and interact with Stylus contracts through thirdweb documentation

• Deploy contracts written with Stylus through the thirdweb

npx thirdweb deploy-stylus -k <YOUR SECRET KEY>

• Publish Stylus-written contracts through the thirdweb CLI

npx thirdweb publish-stylus -k <YOUR SECRET KEY>

• Interact with Stylus contracts using thirdweb SDKs.

Learn how to do this through the Stylus guide.

Stylus + thirdweb lets you trade Solidity’s familiar syntax for Rust’s performance without losing any of the tooling you love, and simplifies your deployment and tooling integration.

We will be creating additional contracts with Stylus. If you are interested in being notified on release or have any feedback, please join our Telegram community and let us know.

• thirdweb Arbitrum Documentation
• Arbitrum Stylus Documentation
• Stylus Airdrop ERC-721 Template

Need help? Please reach out to our support team.

A cleaner, smarter interface to help you discover features and navigate the Playground more efficiently.

• New home page with Table of Contents
• Updated product grouping in the sidebar
• Clearer titles and descriptions
• A cleaner and more user friendly sidebar
• Added light mode support

Breaking Change: /v1/nfts/transfers Requirements

• Requests to /v1/nfts/transfers now require at least one of the following parameters:
  • block_timestamp_from
  • block_number_from

Status: Read-Only (No New Blocks)

• The following chain IDs have been deprecated and will no longer receive new block updates
• Historical data remains accessible for all deprecated chains
• Affected Chain IDs: 30, 302, 919, 5031, 6283, 9746, 9899, 11690, 16600, 31911, 41455, 42019, 42026, 98865, 555271, 555272, 978658, 4457845, 28122024, 168587773, 531050104, 1660990954, 2734060341882000

• Update any /tokens/transfers paginated requests to include required time or block range parameters
• Consider migrating from deprecated chains to active alternatives where applicable

The Transactions API now supports EIP7702 session key authorization for gasless transaction execution. Server wallets can execute transactions on behalf of user accounts with full gas sponsorship from the infrastructure.

Implementation

curl -X POST "https://engine.thirdweb.com/v1/write/transaction" \
  -H "content-type: application/json" \
  -H "x-secret-key: <your-secret-key>" \
  -d '{
    "executionOptions": {
      "type": "EIP7702",
      "chainId": "84532",
      "sessionKeyAddress": "<server-wallet-address>",
      "accountAddress": "<user-account-address>"
    },
    "params": [
      {
        "to": "0x...",
        "data": "0x...",
        "value": "0x0"
      }
    ]
  }'

Parameters

• sessionKeyAddress: Server wallet address with session key authorization
• accountAddress: User account that issued the session key
• type: Must be set to EIP7702 for session key execution
• Gas costs: Fully sponsored by Transactions API infrastructure

Your server wallet must be registered as authorized session key signer on the accountAddress you want to send this transaction on behalf of.

We just enabled batch execution for EOAs, allowing you to execute multiple transactions atomically in a single call.

How to use batch execution

Simply pass multiple items in your params array. All transactions will be executed atomically:

curl -X POST "https://engine.thirdweb.com/v1/write/transaction" \
  -H "content-type: application/json" \
  -H "x-secret-key: <your-secret-key>" \
  -d '{
    "executionOptions": {
      "type": "EOA",
      "chainId": "84532",
      "from": "<your-eoa-address>"
    },
    "params": [
      {
        "to": "0x...",
        "data": "0x...",
        "value": "0x0"
      },
      {
        "to": "0x...",
        "data": "0x...",
        "value": "0x0"
      },
      {
        "to": "0x...",
        "data": "0x...",
        "value": "0x0"
      }
    ]
  }'

EOA Upgrade Required

Engine uses EIP7702 internally for batch execution, which requires your EOA to be "upgraded". If your EOA isn't already upgraded, you can send a no-op EIP7702 transaction to upgrade it:

curl -X POST "https://engine.thirdweb.com/v1/write/transaction" \
  -H "content-type: application/json" \
  -H "x-thirdweb-secret-key: <your-secret-key>" \
  -d '{
    "executionOptions": {
      "type": "EIP7702",
      "chainId": "84532",
      "from": "<your-eoa-address>"
    },
    "params": [
      { "to": "<your-eoa-address>"}
    ]
  }'

After this upgrade transaction, you can use batching with the same EOA.

Happy building! 🛠️

You can now instantly swap between tokens and chains using any thirdweb wallet with the https://api.thirdweb.com/v1/payments/swap endpoint. Using exact you can toggle between specifying an input and output amount to be received. Learn more and see the full reference here.

We just enabled AWS KMS wallet support for the Transactions API, allowing you to use your AWS KMS-managed keys directly.

How to use AWS KMS wallets

Add the AWS KMS headers to your Engine API calls:

curl -X POST "https://engine.thirdweb.com/v1/write/transaction" \
  -H "content-type: application/json" \
  -H "x-secret-key: <your-secret-key>" \
  -H "x-aws-kms-arn: <your-kms-key-arn>" \
  -H "x-aws-access-key-id: <your-access-key>" \
  -H "x-aws-secret-access-key: <your-secret-key>" \
  -d '{
    "executionOptions": {
      "type": "EOA",
      "chainId": "1",
      "from": "<your-kms-wallet-address>"
    },
    "params": [{
      "to": "0x...",
      "data": "0x...",
      "value": "0x0"
    }]
  }'

Migrating from Engine v2?

If you're using AWS KMS wallets with Engine v2, you can now migrate to Engine Cloud seamlessly using the same KMS configuration.

Please avoid using EOA execution on both Engine v2 and Engine Cloud simultaneously with the same wallet on the same chain - this will cause nonce conflicts. Consider testing your integration on a different chain, and them migrating fully.

Happy building! 🛠️

We've made significant changes to how the payment widgets (BuyWidget, CheckoutWidget, and TransactionWidget) generate quotes for every available token. This allows users to find the best possible quote available to them, rather than needing to guess with token to pay with.

Try the improved quote discovery in our playground or on version 5.105.24 or later of the React SDK.

Unreal Engine 5.6 is now supported by thirdweb's Unreal Plugin.

You can download the plugin from our Github Release.

This release is also available on the Fab marketplace!

thirdweb Payments have made it easy to integrate monetization tools into apps with drop-in widgets and SDKs. Now, we're making it even easier with hosted payment links.

You can get paid by anyone, anywhere, and in any token using thirdweb's Payment Links. Links can be created in the dashboard or via the payments API. We've also redesigned our payment's dashboard for easier feature discovery and usage.

Full support for v7 Account Factories and Entrypoints has been added.

Rust static libraries have been updated, and Smart Wallet creation now includes a new advanced EntryPoint parameter.

When using our default v7 Account Factory, or a custom one based on the v7 standard, you can provide the v7 EntryPoint address to override the default v6 behavior.

• v6 Default Factory: 0x85e23b94e7F5E9cC1fF78BCe78cfb15B81f0DF00
• v6 EntryPoint: 0x5FF137D4b0FDCD49DcA30c7CF57E578a026d2789
• v7 Default Factory: 0x4bE0ddfebcA9A5A4a617dee4DeCe99E7c862dceb
• v7 EntryPoint: 0x0000000071727De22E5E9d8BAf0edAc6f37da032

You can find the latest release on Github.

We’ve rebuilt the thirdweb developer platform for the AI-native era. You can now build apps 80% faster with our new HTTP API, MCP server and new LLM optimized documentation. We've also re-organized the platform to be simpler and better organized.

• New HTTP API → We created a new API which combines all services with a simplified interface. Optimized for humans and agents.
• New MCP server → Interact with the thirdweb platform from your favorite LLM client.
• New LLM-optimized documentation → inject these into your prompts to instruct coding agents to build with thirdweb
• New Project and documentation organization → Projects and docs are now organized to follow the new product structure

• Manage user and server wallets
• Transact gasless-ly with highly performant EIP7702 execution
• Query any blockchain data both indexed and real time
• Monitor all your transactions on your project dashboard

Check out the full api reference.

The entire thirdweb platform is now available as a remote MCP server: https://api.thirdweb.com/mcp. Perfect for building agents, or directly interacting with the thirdweb platform from your favorite LLM client.

Check out our new MCP documentation for more details.

Inject knowledge into your coding agent by copying our new llms.txt into your project or your prompts. Example prompt:

Add a login screen that lets the user enter the email and confirm a verification code, then display their email and wallet address in the header. Docs: https://api.thirdweb.com/llms.txt

Check out our available llm optimized doc files.

We've organized the dashboard and documentations around our new main categories: Wallets, Transactions, Contracts, Payments, Tokens and Marketplace.

You'll see this grouping reflected all across the product for a more cohesive and predictable experience.

1. Create a new or use an existing project in the thirdweb dashboard
2. Discover the new API: authenticate using your project’s secret key and start exploring the new endpoints for Wallets, Contracts, Payments, etc. See the documentation reference.
3. Work with AI: test the MCP server in your favorite LLM client, or inject our new llms.txt and build apps in minutes

If you’re already using our APIs or SDKs, no action is required.

• You can continue using your existing setup
• Gradual adoption is supported, if desired, and you can migrate endpoint-by-endpoint if you like
• Your current auth keys and project still work and nothing is changing on your current build.

If you use the upgraded API, all actions — whether client-side or server-side — show up in the dashboard. That means better monitoring, logs, transaction lifecycle tracking, and visibility across your app.

Q: Will the old APIs or SDKs be deprecated?

No. SDKs and dedicated service APIs are here to stay and will continue to evolve as before towards the new product simplification without any breaking changes.

Q: How are the upgraded services priced?

Services are priced as they are currently- no changes. Requests will be charged based on usage to the underlying infrastructure. See our pricing page for more details.

Q: Will portal docs change?

Yes. We’re gradually reorganizing our portal to match the new interfaces. You will see a lot of changes coming up daily. We will still ensure users on existing services have relevant documentation available.

If you need help on finding anything please let us know.

And as always, we are here for support. Our team will be on standby for support around the upgraded API. Please join us for any feedback or questions in our community Telegram channel.

What’s New

• Support Tab: A new “Support” tab is now available on the team sidebar
• AI Agent: Get quick answers with our built-in AI support chat
• Case Management: Create, track, and manage support cases directly from your dashboard

How It Works

• Open a new case for the thirdweb team to review
• View the status and history of existing cases
• Use the AI agent for instant guidance on common issues

Next Steps

• Go to your team in the dashboard and click on the Support tab
• For support SLAs by plan, visit: thirdweb.com/pricing
• For general response time expectations, see: portal.thirdweb.com/knowledge-base#3-response-time-expectations

We just enabled EOA execution for server wallets, allowing you to self fund your own server wallets, and directly executing onchain transactions from them.

Set type: "EOA" in your executionOptions and pass your server wallet EOA address (signer).

Remember to fund the EOA with some native currency on that chain!

curl -X POST "https://engine.thirdweb.com/v1/write/contract" \
  -H "Content-Type: application/json" \
  -H "x-secret-key: <your-project-secret-key>" \
  -d '{
    "executionOptions": {
      "type": "EOA",
      "from": "<your-EOA-server-wallet-address>",
      "chainId": "84532"
    },
    "params": [
      {
        "contractAddress": "0x...",
        "method": "function mintTo(address to, uint256 amount)",
        "params": ["0x...", "100"]
      }
    ]
  }'

If your EOA runs out of funds, the transactions will be paused until you send some funds to it, then all transactions will resume automatically.

Happy building! 🛠️