We've added Transak to our suite of supported onramp providers in the Universal Bridge. Along with Coinbase and Stripe, Transak brings the total supported countries to over 160, and supported direct onramp tokens to over 170. Explore all the countries and tokens Transak supports.

When used with Universal Bridge, our onchain routing allows you to onramp to thousands of tokens. Some of the notable countries the Universal Bridge now supports:

• Philippines
• South Korea
• Brazil
• Japan
• Indonesia
• Hong Kong

To get an onramp link and quote using the Universal Bridge API, use the following:

const res = await fetch(
  "https://bridge.thirdweb.com/v1/onramp/prepare",
  {
    method: "POST",
    headers: {
      "Content-Type": "application/json",
      "x-secret-key": process.env.THIRDWEB_SECRET_KEY,
    },
    body: JSON.stringify({
      onramp: "transak",
      chainId: 4337,
      tokenAddress: "0xAFf7314Bc869f4AB265ec7EfA8E442F1D978d7a",
      maxSteps: 2,
      amount: "200000000000000000",
      currency: "USD",
      receiver: "0x2a4f24f935eb178e3e7ba9b53a5ee6d8407c0709",
    }),
  },
);
 
const data = await res.json();

The returned quote will look something like this:

{
    "data": {
        "id": "3179cf89-e915-4103-b61e-991bf3a33e93",
        "link": "https://global.transak.com/...",
        "destinationAmount": "2000010000000000",
        "timestamp": 1747165958956,
        "expiration": 1747169558945,
        "intent": {
            "chainId": 4337,
            "tokenAddress": "0xAff7314Bc869ff4AB265ec7Efa8E442F1D978d7a",
            "amount": "2000010000000000",
            "receiver": "0x2a4f24F935Eb178e3e7BA9B53A5Ee6d8407C0709",
            "onramp": "transak",
            "currency": "USD",
            "maxSteps": 2
        },
        "steps": [
            {
                "originToken": {
                    "chainId": 4337,
                    "address": "0xEeeeeEeeeEeEeeEeEeEeeEEEeeeeEeeeeeeeEEeE",
                    "symbol": "BEAM",
                    "name": "Beam",
                    "decimals": 18,
                    "priceUsd": 0.00974066,
                    "iconUri": "https://coin-images.coingecko.com/coins/images/32417/large/chain-logo.png?1698114384"
                },
                "destinationToken": {
                    "chainId": 4337,
                    "address": "0xAff7314Bc869ff4AB265ec7Efa8E442F1D978d7a",
                    "symbol": "FP",
                    "name": "Forgotten Playland",
                    "decimals": 18,
                    "priceUsd": 0.0006662,
                    "iconUri": "https://coin-images.coingecko.com/coins/images/35339/small/FP-Token-Icon_%281%29.png?1744266332"
                },
                "transactions": [
                    {
                        "type": "eip1559",
                        "to": "0xF8Ab2dBE6c43bf1a856471182290f91D621Ba76d",
                        "from": "0x2a4f24F935Eb178e3e7BA9B53A5Ee6d8407C0709",
                        "value": "142478928995176",
                        "data": "...",
                        "chainId": 4337,
                        "action": "buy",
                        "id": "0xb15a4e9999fc5504e64085dd812b33090e33e3b3b84f4d1adbaf52e6587af8f1",
                        "spender": "0x965B104e250648d01d4B3b72BaC751Cde809D29E"
                    }
                ],
                "originAmount": "142478928995176",
                "destinationAmount": "2000010000000000",
                "estimatedExecutionTimeMs": 12000
            }
        ],
        "currency": "USD",
        "currencyAmount": 1.06
    }
}

You can then use the top-level id to get the onramp's status:

const res = await fetch(
  "https://bridge.thirdweb.com/v1/onramp/status?id=3179cf89-e915-4103-b61e-991bf3a33e93",
  {
    method: "GET",
    headers: {
      "Content-Type": "application/json",
      "x-secret-key": process.env.THIRDWEB_SECRET_KEY,
    },
  },
);
 
const data = await res.json();

The returned status:

{
    "data": {
        "status": "COMPLETED",
        "transactions": [
            {
                "chainId": 4337,
                "transactionHash": "0xd36a649a23044e980446a3183c6cfe9016d539a6ff88f31b611a1614b1d265aa"
            }
        ],
        "purchaseData": null
    }
}

To learn more about how to use thirdweb's Universal Bridge for onramping, bridging, or swapping, check out the API reference or docs.

We've improved token balance fetching in the PayEmbed for near-instant balance display. We check thousands of tokens for possible routes and return any the user can use to perform their desired transaction in less than a second.

The improved performance is available as of TypeScript SDK v5.99.0. Try it out for yourself on the thirdweb playground.

Version 5.99.0 of the TypeScript thirdweb SDK brings first-class support for EIP-5792. The new implementation streamlines how you batch calls, sponsor gas and track confirmations, while aligning our API with the final EIP-5792 spec.

Highlights:

• New React hooks – useSendAndConfirmCalls, useWaitForCallsReceipt
• Simpler useSendCalls / sendCalls signatures – no more explicit client prop, aligned return types with v2.0.0 of the EIP
• Decoupled receipt handling for flexible UI handling of receipts
• Easy wallet-capability detection

As usual, you can try out the integration on the live playground:

TypeScript (node / backend)

import { sendCalls, waitForCallsReceipt } from "thirdweb";
 
// Build your calls array (tx1, tx2 … conforming to EIP-5792 structure)
const result = await sendCalls({
  calls: [tx1, tx2],
  sponsorGas: true, // optional gas sponsorship
});
 
// Later - or in a different process
const receipt = await waitForCallsReceipt(result.id);
 
console.log("First tx hash:", receipt.receipts[0].transactionHash);

React (front-end)

1 – Fire-and-forget, then wait for the receipt

const { mutate: sendCalls } = useSendCalls();
const { data: result } = await sendCalls({ calls: [tx1, tx2] });
 
// later, or in another component
const { data: receipt, isLoading } = useWaitForCallsReceipt(
  result.id,
);

2 – One-liner helper

const { mutate: sendAndConfirmCalls, data: receipt } =
  useSendAndConfirmCalls();
 
await sendAndConfirmCalls({ calls: [tx1, tx2] });
console.log("Bundle confirmed:", receipt.bundleHash);

The previous version of the SDK had beta support for 5792, which got some breaking changes in this version, listed below:

React

TypeScript / non-React

Any existing code that relies on the old return type must now read result.id and call waitForCallsReceipt (or the React hook) to obtain transaction receipts.

We recommend upgrading as soon as possible to leverage gas sponsorship and the simplified developer experience. For a full diff, see PR #7003 on GitHub.

As soon as the Pectra Ethereum Upgrade was released, so were our next-gen 7702 smart accounts - read more about them here!

Today, we introduce support for more chains that upgraded to Pectra!

Arbitrum Sepolia: RPC and Chain Settings

Use the best Arbitrum Sepolia RPC and add to your wallet. Discover the chain ID, native token, explorers, and more.

Base Sepolia Testnet: RPC and Chain Settings

Use the best Base Sepolia Testnet RPC and add to your wallet. Discover the chain ID, native token, explorers, and more.

Soneium Minato: RPC and Chain Settings

Use the best Soneium Minato RPC and add to your wallet. Discover the chain ID, native token, explorers, and faucet options.

OP Sepolia Testnet: RPC and Chain Settings

Use the best OP Sepolia Testnet RPC and add to your wallet. Discover the chain ID, native token, explorers, and faucet options.

Unichain Sepolia Testnet: RPC and Chain Settings

Use the best Unichain Sepolia Testnet RPC and add to your wallet. Discover the chain ID, native token, explorers, and more.

Ink Sepolia: RPC and Chain Settings

Use the best Ink Sepolia RPC and add to your wallet. Discover the chain ID, native token, explorers, and more.

TypeScript / React

// plain TypeScript
import { inAppWallet } from "thirdweb/wallets";
 
const wallet = inAppWallet({
  executionMode: {
    mode: "EIP7702",
    sponsorGas: true,
  },
});

// React (e.g. Next.js)
import { inAppWallet } from "thirdweb/wallets";
import { ConnectButton } from "thirdweb/react";
 
<ConnectButton
  client={client}
  wallets={[
    inAppWallet({
      executionMode: {
        mode: "EIP7702",
        sponsorGas: true,
      },
    }),
  ]}
/>;

.NET / Unity

// .NET (server, Godot C#, MAUI, etc.)
var smartEoa = await InAppWallet.Create(
    client: thirdwebClient,
    authProvider: AuthProvider.Google,
    executionMode: ExecutionMode.EIP7702Sponsored
);

// Unity (C#)
var wallet = await ConnectWallet(
    new WalletOptions(
        provider: WalletProvider.InAppWallet,
        chainId: 11155111,
        inAppWalletOptions: new InAppWalletOptions(
            authprovider: AuthProvider.Google,
            executionMode: ExecutionMode.EIP7702Sponsored
        )
    )
);

This release includes significant improvements to the Nebula agent's architecture, entity memory management, error handling, and documentation search capabilities. Key updates focus on simplifying blockchain entity handling, improving transaction management, supporting more content types in chat, and enhancing error messaging for a better user experience.

• New Content Support in Chat
  • Add support for image and transaction content types in chat messages

{
  "messages": [
     { 
       "role": "user", 
       "content": [
         { "type": "image", "image_url": "ipfs://Qmefr67P2qZS5BS9KBbZVgVXAYCdeezkN4je4tnd6xib4c" }, 
         { "type": "text", "text": "Please describe the image" }
       ]
     }],
     "stream": "true", 
}

• Enable transaction hash messages for blockchain status checks

{
  "messages": [
     { 
       "role": "user", 
       "content": [
          { "type": "transaction", "transaction_hash": "0x112c7d127dbd1fef1006aa6211462a2635b504fc42f71aad0cae4b1e7ddba32a", "chain_id": 1 }
        ]
     }],
     "stream": "true", 
}

• Enhanced Entity Management
  • Simplify loading entities by type with a cleaner implementation
  • Improve entity memory formatting for better readability
  • Reduce database operations for improved performance
  • Add user wallet as parsed entity for better context
• Documentation and Search Improvements
  • Implement new LLMs documentation search with better context retrieval
  • Add URL to web search results for better source attribution
  • Format blockchain entities as links in responses
• Improved Error Handling
  • Better error messaging for deployment and payment issues
  • Add instructions to help users correct chain context issues
  • Support graceful error handling in streaming responses

• New agent action types for better request handling
• Support for image and transaction inputs in chat messages
• More structured error responses with helpful suggestions
• Revised agent action structure to use more specific types
• Updated event streaming format for better client compatibility

• Fix undefined behavior when no routes found in Universal Bridge
• Handle payment required errors from storage service
• Fix wallet balance formatting and improve entity display
• Ensure price and token supply data is displayed correctly

Ready to try out all these new features? Give it a spin at https://nebula.thirdweb.com!

We just added Universal Bridge support for $HONEY, Berachain's stablecoin. You can now pay with or accept HONEY for any transaction on any chain.

Introducing Engine Cloud — read and write to the blockchain at scale, without the cost or complexity of traditional blockchain API setups.

Engine Cloud is our answer to lowering the barrier to developing high volume applications onchain- with fully-hosted, scalable APIs that let you perform on-chain actions from your backend. No upfront costs. Only pay-as-you-go.

It includes a non-custodial way to manage your wallets and ready-to-go API calls that do things like mint NFTs, transfer tokens, airdrops, sponsor gas for users — on any contract, across any EVM chain.

Engine Cloud includes:

• Server Wallets managed via Vault (our new key management system)
• New Transaction Gateway with retry logic, nonce management, and sub-second speed
• New transaction API improved DX, new typescript SDK integration, and more
• Secure, granular access tokens to work with multiple wallets and teams via vault access tokens and permissions
• No more manual gas top-ups or alerts— we handle that for you by topping through our paymasters from your payment on file.

Learn more about use cases and benefits of using Engine Cloud.

1. Create a thirdweb project — this will include a ready-to-go Engine server for you to start making API calls on.
2. Get your Vault Admin Key + Access Tokens — via the dashboard. Learn more about Vault.
3. Create a server wallet — for secure, granular signing and management. You can create one or multiple server wallets.
4. Start calling the API — write and send transactions from your backend using the simple API endpoints. All API endpoints can be accessed via the dashboard or through the API reference.

Engine will be free during beta without charging for any requests until May 19th. You can integrate it to your application today.

For any questions or feedback, please reach out to our support team.

EIP-7702 unlocks a new capability for externally-owned accounts (EOAs): the ability to behave like smart contract accounts. The latest SDK let you enable 7702 on any of your in-app wallets with one line of code, giving your users gas-sponsored, batched and automated transactions faster and more efficiently than ever before.

Once an in-app wallet is running in EIP-7702 mode you can:

• Sponsor gas so users can sign transactions with zero ETH in their balance.
• Batch transactions so multiple contract calls clear in a single signature.
• Add session keys to automate on-chain actions safely (think scheduled mints, subscription based payments or game loops).
• …and any other capability you’d expect from smart accounts—all while your user keeps their familiar EOA address.

All it takes is a tiny config change.

But what about EIP-4337 smart wallets?
In our testing, using 7702 is up to twice as fast and orders of magnitude cheaper than using 4337 smart contract wallets!

Don't take our word for it, try it yourself on the live playground:

https://playground.thirdweb.com/connect/account-abstraction/7702

In-app wallets lets you create wallets for your users based on standard logins like email, passkey or Google. Below are drop-in examples to turn those wallets into 7702 smart accounts for every stack the thirdweb SDK supports today.

TypeScript / React

// plain TypeScript
import { inAppWallet } from "thirdweb/wallets";
 
const wallet = inAppWallet({
  executionMode: {
    mode: "EIP7702",
    sponsorGas: true,
  },
});

// React (e.g. Next.js)
import { inAppWallet } from "thirdweb/wallets";
import { ConnectButton } from "thirdweb/react";
 
<ConnectButton
  client={client}
  wallets={[
    inAppWallet({
      executionMode: {
        mode: "EIP7702",
        sponsorGas: true,
      },
    }),
  ]}
/>;

. NET / Unity

// .NET (server, Godot C#, MAUI, etc.)
var smartEoa = await InAppWallet.Create(
    client: thirdwebClient,
    authProvider: AuthProvider.Google,
    executionMode: ExecutionMode.EIP7702Sponsored
);

// Unity (C#)
var wallet = await ConnectWallet(
    new WalletOptions(
        provider: WalletProvider.InAppWallet,
        chainId: 11155111,
        inAppWalletOptions: new InAppWalletOptions(
            authprovider: AuthProvider.Google,
            executionMode: ExecutionMode.EIP7702Sponsored
        )
    )
);

Heads-up EIP-7702 only works on chains that enable it. Ethereum mainnet and Sepolia already support it, with more coming soon; keep an eye on the thirdweb blog for other chain activation dates.

Don’t want to embed an in-app wallet? No problem. EIP-5792 lets you tap into the same 7702 capabilities from any external wallet—like Metamask and Coinbase Wallet —via the sendCalls RPC method.

Sponsoring Gas & Batching Transactions

The useSendCalls React hook (or the plain sendCalls function in vanilla TypeScript) lets you bundle multiple calls into one and attach a paymaster so your dApp covers the gas:

import { useSendCalls } from "thirdweb/react";
 
const { mutate: sendCalls, data: bundleId } = useSendCalls();
await sendCalls({
  client,
  calls: [sendTx1, sendTx2],
  capabilities: {
    paymasterService: {
      url: `https://${CHAIN.id}.bundler.thirdweb.com/${client.clientId}`,
    },
  },
});

Thie enabled single signature, gas-free, batched execution on exernal wallets like Metamask!

Documentation links: React API | TypeScript API

Upgrade your thirdweb SDK to the latest version, flip on executionMode: "EIP7702" or use EIP5792's sendCalls, and your users instantly level-up to smart-account features—no new wallets, no migrations, just better UX.

Got questions or feedback? Jump into the thirdweb Discord and let us know what you’re building!

With the latest release of Universal Bridge, we've added a number of new filters to make building advanced payment UIs more convenient. These are available starting in v5.97.0 of the TypeScript SDK.

The /routes endpoint (API) and Bridge.routes function (SDK) now have an optional sortBy option to determine how the returned routes will be ordered. The first option we've made available is sortBy: "popularity", which will ordered the returned routes based on the number of times they've been used. The following will return the 10 most popular routes originating from ETH on mainnet:

import { Bridge } from "thirdweb";
 
const routes = await Bridge.routes({
  originChainId: 1,
  originTokenAddress: "0xEeeeeEeeeEeEeeEeEeEeeEEEeeeeEeeeeeeeEEeE",
  limit: 10,
  offset: 0,
  sortBy: "popularity",
  client: thirdwebClient,
});

[
  {
    "originToken": {
      "chainId": 8453,
      "address": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
      "iconUri": "https://coin-images.coingecko.com/coins/images/6319/large/usdc.png?1696506694",
      "symbol": "USDC",
      "name": "USD Coin",
      "decimals": 6
    },
    "destinationToken": {
      "chainId": 466,
      "address": "0x675C3ce7F43b00045a4Dab954AF36160fb57cB45",
      "iconUri": "https://coin-images.coingecko.com/coins/images/6319/large/usdc.png?1696506694",
      "symbol": "USDC",
      "name": "USD Coin",
      "decimals": 6
    }
  },
  {
    "originToken": {
      "chainId": 42161,
      "address": "0xaf88d065e77c8cC2239327C5EDb3A432268e5831",
      "iconUri": "https://ethereum-optimism.github.io/data/USDC/logo.png",
      "symbol": "USDC",
      "name": "USD Coin",
      "decimals": 6
    },
    "destinationToken": {
      "chainId": 466,
      "address": "0x675C3ce7F43b00045a4Dab954AF36160fb57cB45",
      "iconUri": "https://coin-images.coingecko.com/coins/images/6319/large/usdc.png?1696506694",
      "symbol": "USDC",
      "name": "USD Coin",
      "decimals": 6
    }
  },
  {
    "originToken": {
      "chainId": 1,
      "address": "0xEeeeeEeeeEeEeeEeEeEeeEEEeeeeEeeeeeeeEEeE",
      "iconUri": "https://assets.relay.link/icons/1/light.png",
      "symbol": "ETH",
      "name": "Ether",
      "decimals": 18
    },
    "destinationToken": {
      "chainId": 8453,
      "address": "0xEeeeeEeeeEeEeeEeEeEeeEEEeeeeEeeeeeeeEEeE",
      "iconUri": "https://assets.relay.link/icons/1/light.png",
      "symbol": "ETH",
      "name": "Ether",
      "decimals": 18
    }
  },
  ...
]

The maxSteps filter already allows you to filter routes based on the number of steps required to fulfill a routes. With this update, we've added this same option to the Buy.quote, Buy.prepare, Sell.quote, and Sell.prepare functions, as well as their corresponding API endpoints. You can now guarantee the quote returned uses a certain number of steps or fewer:

import { Bridge } from "thirdweb";
 
const quote = await Bridge.Buy.quote({
  originChainId: 1,
  originTokenAddress: "0x...",
  destinationChainId: 137,
  destinationTokenAddress: "0x...",
  amount: 1000000n,
  maxSteps: 2,
});
 
const preparedQuote = await Bridge.Buy.prepare({
  originChainId: 1,
  originTokenAddress: "0x...",
  destinationChainId: 137,
  destinationTokenAddress: "0x...",
  amount: 1000000n,
  sender: "0x...",
  receiver: "0x...",
  maxSteps: 2,
});
 
const quote = await Bridge.Sell.quote({
  originChainId: 1,
  originTokenAddress: "0x...",
  destinationChainId: 137,
  destinationTokenAddress: "0x...",
  amount: 1000000n,
  maxSteps: 3,
});
 
const preparedQuote = await Bridge.Sell.prepare({
  originChainId: 1,
  originTokenAddress: "0x...",
  destinationChainId: 137,
  destinationTokenAddress: "0x...",
  amount: 1000000n,
  sender: "0x...",
  receiver: "0x...",
  maxSteps: 3,
});

We've added a new endpoint and SDK function to get all chains supported by Universal Bridge along with their name, icon, and native currency.

import { Bridge } from "thirdweb";
 
const chains = await Bridge.chains({
  client: thirdwebClient,
});

This will return:

[
  {
    "chainId": 1868,
    "name": "Soneium Mainnet",
    "icon": "ipfs://QmPSGdP5WKe2bC5JCo43JjWff8Agw7dg6WQpmUktyW7sat",
    "nativeCurrency": {
      "name": "Ethereum",
      "symbol": "ETH",
      "decimals": 18
    }
  },
  {
    "chainId": 466,
    "name": "AppChain",
    "icon": "ipfs://bafybeigx76uxvcvet7365sjdzuxxcgl5auzck6vbbigu2jeg6ixl5k3tya",
    "nativeCurrency": {
      "name": "Ether",
      "symbol": "ETH",
      "decimals": 18
    }
  },
  {
    "chainId": 42161,
    "name": "Arbitrum One",
    "icon": "ipfs://QmcxZHpyJa8T4i63xqjPYrZ6tKrt55tZJpbXcjSDKuKaf9/arbitrum/512.png",
    "nativeCurrency": {
      "name": "Ether",
      "symbol": "ETH",
      "decimals": 18
    }
  },
  ...
]

• Fixed an issue where Coinbase onramps were not returning the associated transaction hash
• Fixed routes returning the zero address rather than the native token address

You can now verify a domain for your team!

• Teams can verify their domain (e.g. @yourcompany.com)
  → When logged in, navigate to Settings`→ General and scroll down Domain Verification to verify your domain.
• To complete the verification, you'll need to add a DNS TXT record to your domain. This part must be completed through your domain provider's dashboard.
• Please note you may only verify one domain per team.

• Verified badge: Your team gets a special badge, so it’s easier to confirm you're in the right place.
• Recommended team members: On the Settings → Members page, you’ll see users with emails that match your domain but aren’t in the team yet — making it super easy to invite everyone on the team.

• Instant invite alerts: Team owners will get a notification (in the dashboard and optionally via email) when someone signs up with your verified domain — with a 1-click invite option.
• Recommended teams for users: New users with a matching email domain will see teams they can request to join, giving team owners control to approve or deny.

For any questions or support please reach out to our support team.

In preparation for Ethereum’s upcoming Pectra upgrade this May, the thirdweb Pack contract has been officially deprecated and is no longer deployable via the dashboard, SDK, or CLI.

Important: Existing Pack contracts are not compatible with the Pectra upgrade.

We strongly recommend that users abandon or conclude any unopened packs as soon as possible to avoid potential issues once the upgrade goes live.

For any questions or support, please reach out to the official thirdweb team support channel.

TL;DR: Update your SDK to 5.96.9+ to fix external wallet mobile connections.

A recent chrome update introduced a change in websockets that broke Wallet Connect connection flows on mobile. This resulted in users not being able to connect their wallets to mobile websites, infinitely loading. All wallet providers were affected. A bug fix was shipped by the Wallet Connect team to support the latest version of Chrome, and we immediately adopted the new version in the latest version of the thirdweb SDK.

Version 5.96.6 and above includes the fix, so update your library to resolve this issue.

Nebula v0.0.12 brings significant improvements to the user experience and functionality. This release focuses on enhancing transaction management, adding support for NFTs and tokens, and improving the overall user interface. Key highlights include improved deployment workflows, better transaction formatting, and new token management capabilities.

• More sophisticated entity tracking system
• Better persistence of blockchain interactions
• Enhanced context enrichment for more relevant responses

• Add ERC20 token transfer and approve functionality
  • Transferring tokens between addresses
  • Granting spending allowances to contracts
  • Add ERC721 transfer support for NFT management
• Add minting capabilities
  • New NFT minting tool for creating digital collectibles
  • Token minting functionality with improved user feedback
• Support for images in tokens and NFTs
  • Add rendering support for NFT and token images on the frontend

• Enhanced deployment workflows
  • Improve deployments to include more detailed information as markdown
  • Support multi-stage deployments for complex contract setups
  • Better UI feedback during deployment processes
• Transaction array support
  • New functionality to handle batched transactions
• Unify simulation and execution outputs
  • Consistent formatting for all transaction operations
  • Better readability of transaction details
• Add rate limit checks to RPC calls
  • Prevent API throttling issues with improved handling

• Fix native transfer rendering
  • Correct display of native token transfers in UI
• Fix deploy UI issues
  • Address multiple UI bugs in the deployment interface
  • Fix early yielding creating duplicate UI cards
• Fix contract output when metadata is missing
  • Better handling of contracts with missing information
• Token Bridging / Swapping (Universal Bridge) fixes
  • Switch to new endpoints for improved reliability
  • Fix ABI handling for better contract interaction
• Fix image parsing
  • Correct handling of image data in responses

Try it out today at https://nebula.thirdweb.com!

There are 2 changes to the Insight API to improve usability and fix a numeric overflow in Javascript.

The NFT and Token transfer endpoints have been changed and now the owner_address query param is not mandatory anymore, enabling queries for all transfers on a chain.

Since this query can be heavy, we also added block number filters. You can narrow down the query using block_number_from and block_number_to query params.

Since Solidity supports numbers larger the Javascript's max number, APIs consuming the decoded events and transactions would receive some numeric values in scientific notation, losing precision.

We updated the decoded data to return large numeric values as string to prevent this. This is what a decoded transaction would look like now

{
  "data": [
    {
      ...rest of transaction...
      "decoded": {
        "name": "transfer",
        "signature": "transfer(address,uint256)",
        "inputs": {
          "_to": "0x28c6c06298d514db089934071355e5743bf21d60",
          "_value": "4179950264410000000000"
        }
      }
    }
  ]
}

Note that the _value uint256 input is returned as string 4179950264410000000000

📖 Learn more about Insight - it’s open source and ready to power your applications!

This release introduces new image generation capabilities, improves error handling for rate limits, and fixes several key components including IPFS functionality and token minting. Performance optimizations have also been implemented to make token queries faster.

• Add image generation functionality - Implement new image generation capabilities. Create assets with generative artwork in a single prompt!
• Improve rate limit handling - Add ability to gracefully abort execution when API rate limits are reached
• Optimize token information retrieval - Add option to exclude price data for faster query performance

Check it out at https://nebula.thirdweb.com

The latest thirdweb typescript SDK release - v5.96.4 - adds a new way to make the Connect modal feel like your own by adding custom metadata to in-app wallets.

In wide mode, you can customize the name and icon of your in-app wallet in the list of wallets, and the image above the login options separately.

In compact mode, only the image above the login options is displayed.

Simply pass your app metadata along the other options when creating your inAppWallet , then pass it as one of the available wallets in the ConnectButton or ConnectEmbed.

const wallets = [
  inAppWallet({
    // your auth options
    auth: {
      options: ["google", "x", "passkey"],
    },
    // your app metadata
    metadata: {
      name: "My App", // name for the wallet list
      icon: "/twcoin.svg", // icon for the wallet list
      image: {
        src: "/twcoin.svg", // image above the login options
        width: 100,
        height: 100,
        alt: "My App",
      },
    },
  }),
  createWallet("io.metamask"),
  createWallet("com.coinbase.wallet"),
  createWallet("io.rabby"),
];
 
<ConnectButton client={client} wallets={wallets} />;

Happy building! 🛠️

This release focuses on improving reliability, performance, and user experience with several key enhancements:

1. Universal Bridge: Enables bridge and swapping
2. Search: Enhances search capability to improve onchain knowledge and optimizes thirdweb documentation search and access
3. Contract Interaction: Simulates transactions result and improves contract information retrieval
4. Performance: Improves contract interaction latency and performance

• Improves token balance display with native token support
• Fixes intermittent failure when interacting with newly deployed contracts
• Improves error message formatting with actionable suggestions
• Improves handling of missing contracts with better error messages

This release significantly enhances Nebula's blockchain integration capabilities with a focus on improved multichain support, better token and NFT handling, and more robust authentication.

The model has been upgraded to provide more accurate and consistent responses more quickly. Users can now see the model's step-by-step thinking process as it performs tasks.

New approach to chain management. By default, only mainnet chains are enabled, to enable testnet requires setting context.networks = "testnet" in the /chat endpoint. The Chain IDs in the context may also be updated through conversations.

Breaking Changes 🔨

• Model Updates: Experience more accurate and consistent responses with the improved t0_003 model.
• Chain Management: Defaults to mainnet only. Enabling testnets require specific flag in the context. By setting, context.networks = "testnet"
• Delegate Auth: Create a SIWE delegated auth tokens for scoped API access to chat and session.

Features ✨

• Guided Tool Prompts: More accurate tool selection by AI agents, resulting in fewer errors and more relevant responses.
• Improved Output Consistency: More standardized and predictable response formats, making automated parsing of outputs more reliable.
• Chain ID Parameter Prioritization: Explicit control over which blockchain they're interacting with, reducing confusion and errors from context-switching
• Comprehensive Blockchain Data Retrieval: Access detailed information about blocks, transactions, and events, enabling more complex analyses within the tool.
• Multi-chain Insight Support: Perform cross-chain operations and comparisons without needing to use separate tools or interfaces.
• Domain Name Resolution: Interact with human-readable domain names (like ENS) instead of complex addresses, improving usability.
• Human-readable Timestamps: See dates and times in standard formats rather than UNIX epochs, making information immediately understandable.

• Creating Assets: create different token standards (ERC20, ERC721, ERC1155) more easily.
• NFT Collection Name Display: Friendly collection names rather than just contract addresses, making NFT identification more intuitive.
• Better Wallet Balance Display: Updated token balances with proper decimal divisions, showing correct human-readable amounts. Correct token names for native blockchain currencies (e.g., ETH, MATIC).

• Nebula Auth Method: Developer can delegate scoped account access, improving security while maintaining functionality.
• Smart Account Validator: Smart contract wallets (using ERC-1271 and ERC-6492) can now authenticate with Nebula Auth.

We just released one of our biggest updates yet to the Universal Bridge API. These changes will be coming soon to the SDK and UI components.

The new response schema includes a steps field, which gives you all the info you need to build a comprehensive bridge and swap UI. This includes token metadata, price, expected execution time, input and output amounts, and the transactions to be executed.

A buy, sell, or transfer prepared quote will now look something like this:

{
    "data": {
        "id": "0x11cb09cf545d9c1c1cc12aa20aaee180a59336ec72701b148f452734c50f1bbf",
        "originAmount": "17055594260",
        "destinationAmount": "10000001000001000005",
        "blockNumber": "22325874",
        "timestamp": 1745340923953,
        "estimatedExecutionTimeMs": 22000,
        "intent": {
            "originChainId": 1,
            "originTokenAddress": "0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48",
            "destinationChainId": 8453,
            "destinationTokenAddress": "0xEeeeeEeeeEeEeeEeEeEeeEEEeeeeEeeeeeeeEEeE",
            "amount": "10000001000001000005",
            "sender": "0x2a4f24F935Eb178e3e7BA9B53A5Ee6d8407C0709",
            "receiver": "0x2a4f24F935Eb178e3e7BA9B53A5Ee6d8407C0709"
        },
        "steps": [
            {
                "originToken": {
                    "chainId": 1,
                    "address": "0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48",
                    "symbol": "USDC",
                    "name": "USD Coin",
                    "decimals": 6,
                    "priceUsd": 0.999949,
                    "iconUri": "https://coin-images.coingecko.com/coins/images/6319/large/usdc.png?1696506694"
                },
                "destinationToken": {
                    "chainId": 8453,
                    "address": "0xEeeeeEeeeEeEeeEeEeEeeEEEeeeeEeeeeeeeEEeE",
                    "symbol": "ETH",
                    "name": "Ether",
                    "decimals": 18,
                    "priceUsd": 1695.537726,
                    "iconUri": "https://assets.relay.link/icons/1/light.png"
                },
                "transactions": [
                    {
                        "chainId": 1,
                        "to": "0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48",
                        "data": "0x095ea7b3000000000000000000000000f8ab2dbe6c43bf1a856471182290f91d621ba76d00000000000000000000000000000000000000000000000000000003f897b714",
                        "type": "eip1559",
                        "id": "0xe984ce73defcb35a2decb07b1cbadb57bea0e9bd4c3d919f286988daae5e98a8",
                        "action": "approval"
                    },
                    {
                        "type": "eip1559",
                        "to": "0xF8Ab2dBE6c43bf1a856471182290f91D621Ba76d",
                        "from": "0x2a4f24F935Eb178e3e7BA9B53A5Ee6d8407C0709",
                        "value": "0",
                        "data": "0x...",
                        "chainId": 1,
                        "action": "buy",
                        "id": "0x3b575d76157c50c94c61f0e1265dee784d00d2ad7502f1c6a6dba938e270b196",
                        "spender": "0xfCEF2Fe72413b65d3F393d278A714caD87512bcd"
                    }
                ],
                "originAmount": "17055594260",
                "destinationAmount": "10000001000001000005",
                "estimatedExecutionTimeMs": 22000
            }
        ]
    }
}

Onramp quotes will now have the following schema:

{
    "data": {
        "id": "5a066908-82da-4d31-8dea-99c45f72e98b",
        "link": "https://pay.coinbase.com/buy/select-asset?appId=41cbb2fb-8b35-45b9-949b-9672bc8edb78&addresses=%7B%220x2247d5d238d0f9d37184d8332aE0289d1aD9991b%22%3A%5B%22unichain%22%5D%7D&assets=%5B%22USDC%22%5D&defaultAsset=USDC&defaultNetwork=unichain&presetCryptoAmount=1716.321932&fiatCurrency=USD&partnerUserId=7d789de0-b4e0-4aac-84b4-5e13b11c896d",
        "destinationAmount": "1000000100000010000",
        "timestamp": 1745341089555,
        "expiration": 1745344689547,
        "intent": {
            "chainId": 324,
            "tokenAddress": "0xEeeeeEeeeEeEeeEeEeEeeEEEeeeeEeeeeeeeEEeE",
            "amount": "1000000100000010000",
            "receiver": "0x2247d5d238d0f9d37184d8332aE0289d1aD9991b",
            "onramp": "coinbase",
            "currency": "USD",
            "maxSteps": 2,
            "excludeChainIds": []
        },
        "steps": [
            {
                "originToken": {
                    "chainId": 130,
                    "address": "0x078D782b760474a361dDA0AF3839290b0EF57AD6",
                    "symbol": "USDC",
                    "name": "USDCoin",
                    "decimals": 6,
                    "priceUsd": 0.999949,
                    "iconUri": "https://ethereum-optimism.github.io/data/USDC/logo.png"
                },
                "destinationToken": {
                    "chainId": 324,
                    "address": "0xEeeeeEeeeEeEeeEeEeEeeEEEeeeeEeeeeeeeEEeE",
                    "symbol": "ETH",
                    "name": "Ether",
                    "decimals": 18,
                    "priceUsd": 1691.447,
                    "iconUri": "https://assets.relay.link/icons/1/light.png"
                },
                "transactions": [
                    {
                        "chainId": 130,
                        "to": "0x078D782b760474a361dDA0AF3839290b0EF57AD6",
                        "data": "0x095ea7b3000000000000000000000000f8ab2dbe6c43bf1a856471182290f91d621ba76d00000000000000000000000000000000000000000000000000000000664cfe8c",
                        "type": "eip1559",
                        "id": "0xb1ec1d50e1ef52ebb5fab91103f05605e9d24fb8ff26c4e5ef728e41ff82b788",
                        "action": "approval"
                    },
                    {
                        "type": "eip1559",
                        "to": "0xF8Ab2dBE6c43bf1a856471182290f91D621Ba76d",
                        "from": "0x2247d5d238d0f9d37184d8332aE0289d1aD9991b",
                        "value": "0",
                        "data": "0x...",
                        "chainId": 130,
                        "action": "buy",
                        "id": "0x1c66f9e7aefee5ffcc9b22595d07c3eedfa89deaec189707f73272f8e52d1d7b",
                        "spender": "0x078D782b760474a361dDA0AF3839290b0EF57AD6"
                    }
                ],
                "originAmount": "1716321932",
                "destinationAmount": "1000000100000010000",
                "estimatedExecutionTimeMs": 2000
            }
        ],
        "currency": "USD",
        "currencyAmount": 1716.321932
    }
}

The steps are to be completed after the use has done the initial onramp.

You can find all this and more in our API reference docs.

• steps parameter for all quotes with prepared transactions and estimates
• Faster approximate quote responses
• Onramping with post-onramp cross-chain swaps
• Fiat quote included in onramp responses

• Removed ZK chains from intermediate steps, due to inconsistent addresses when using smart wallets

We have added CLI and SDK support for Stylus contracts.

This allows developers to use thirdweb CLI to create, publish, and deploy their contracts written with Stylus. The deployed contracts can be used via thirdweb dashboard or SDK.

• Rust toolchain should be installed (https://www.rust-lang.org/tools/install)
• Solidity (solc) should be installed (https://docs.soliditylang.org/en/latest/installing-solidity.html)

You can also use the Stylus quickstart guide for reference: https://docs.arbitrum.io/stylus/quickstart

Setup a starter repo (can be skipped if you already have a Stylus project)

npx thirdweb create-stylus

This will setup a project containing a template contract.

You can now publish this contract by running the publish command:

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

Publishing a contract saves the contract metadata to an onchain registry, and creates a contract page from where you can deploy a specific version of this contract multiple times.

This is how it will look:

Alternatively, you can use the deploy command to do a one-time deployment:

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

After deployment, the contract will be available on thirdweb dashboard. You can interact with it via dashboard or integrate it in your app using the code snippets as shown below:

We've significantly increased the number of onramp routes available in the Universal Bridge widget. You can now onramp to chains like Mantle, Unichain, Lens, Treasure, and more. No SDK upgrade necessary. Try it out on the bridge page here.

We’ve fixed the issues with how metadata links are resolved — and introduced a new way to give you control over it.

• Fixed a bug where metadata responses sometimes included incorrectly resolved URLs.
• Added validation logic to detect bad URIs in cached or stored metadata — and automatically re-fetches only the original source.

• Introduced a new resolve_metadata_links parameter (default: true) to all NFT endpoints which can return metadata.
• When set to false, the response will return original links such as ipfs:// and ar://, instead of their resolved HTTP versions.

This gives clients full control — whether you want cleanly resolved URLs or raw metadata as authored on-chain.

We're excited to announce a major enhancement to the thirdweb TypeScript SDK that will significantly improve the developer experience when building blockchain applications. With release 5.95.0, we've supercharged the SDK by integrating it with Insight - our in-house indexer - replacing traditional RPC calls for fetching contract state, events, balances, NFT metadata, and more.

The Power of Insight

Until now, the thirdweb SDK has relied primarily on RPC calls to fetch on-chain data. While functional, this approach sometimes faced limitations in terms of speed, reliability, and functionality. By integrating Insight directly into our SDK, we've addressed these challenges head-on, offering:

• Significantly faster queries for contract events, balances, and NFTs
• Enhanced reliability with reduced dependency on mutli roundtrip RPC calls
• Cross-chain functionality that lets you query data across multiple blockchains in a single call
• Advanced filtering capabilities for more precise data retrieval

The Connect UI modal now uses Insight to give your users a full wallet experience directly in your websites:

• Shows all ERC20 token balances
• Show all NFTs
• Shows past transactions of the connected wallet

Your favorite thirdweb functions have been turbocharged with Insight integration:

• getContractEvents
• getOwnedNFTs
• getNFTs
• getNFT

These functions now automatically leverage our indexer on supported chains, with a graceful fallback to traditional RPC calls when needed.

If you're already using those functions in your app, no changes needed on your end, you'll just get the improved functionality out of the box.

If for any reason you need to turn off that behavior, you can pass useIndexer: false to always use RPC.

We've added a dedicated Insight namespace with powerful new functions:

• Insight.getOwnedTokens() - Get ERC20 tokens owned by an address across multiple chains
• Insight.getOwnedNFTs() - Get NFTs (ERC721 and ERC1155) owned by an address
• Insight.getNFTs() - Get NFTs (ERC721 and ERC1155) for a given contract
• Insight.getNFT() - Get NFTs metadata for a given contract and tokenId
• Insight.getTransactions() - Get all transactions for a given wallet address
• Insight.getContractEvents() - Query indexed events with advanced filtering options

You can import those with import { Insight } from "thirdweb"

For developers who need direct access to our indexer API, we've released a standalone package: @thirdweb-dev/insight. This lightweight API wrapper provides:

• Typed functions, request bodies, and responses
• Always stays in sync with the Insight API
• Perfect for backend applications requiring optimized blockchain data access, without the rest of the SDK

For the existing functions, you will get the improved functionality out of the box without any changes. If you want to use the new multichain capabilities directly, here's some examples using the new Insight namespace:

import { Insight } from "thirdweb";
 
const tokens = await Insight.getOwnedTokens({
  client,
  ownerAddress,
  chains: [base, polygon, arbitrum],
});

With just a few lines of code, you can now retrieve all ERC20 tokens owned by an address across Base, Polygon, and Arbitrum networks simultaneously!

import { Insight } from "thirdweb";
 
const nfts = await Insight.getOwnedNFTs({
  client,
  ownerAddress,
  chains: [sepolia],
});

import { Insight } from "thirdweb";
 
const transactions = await Insight.getTransactions({
  client,
  walletAddress,
  chains: [sepolia],
});

import { Insight } from "thirdweb";
 
const events = await Insight.getContractEvents({
  client,
  chains: [sepolia],
  contractAddress: "0x...",
  event: transferEvent(),
  decodeLogs: true,
});

For developers who want low level access to the Insight API with type-safe functions, here's how to use the standalone @thirdweb-dev/insight package:

import { configure } from "@thirdweb-dev/insight";
 
// Call this once at the startup of your application
configure({
  clientId: "<YOUR_CLIENT_ID>",
});

import { getV1Events } from "@thirdweb-dev/insight";
 
const events = await getV1Events({
  query: {
    chain: [1, 137],
    filter_address: "0x1234567890123456789012345678901234567890",
  },
});

These functions will map one to one with the Insight OpenAPI spec and will stay in sync as the service changes.

These new features are available now in thirdweb SDK v5.95.0 and the new @thirdweb-dev/insight v1.0.0 package.

To get started:

npm install thirdweb@latest
# Or if you need the standalone package
npm install @thirdweb-dev/insight

Looking for dotnet/unity? It's already out, head over to the dotnet documentation to learn more.

This Insight integration is just the beginning. We're continuously working to enhance the thirdweb developer experience with more powerful indexing capabilities, additional cross-chain functionality, and deeper integration with our developer tools ecosystem.

Stay tuned for more updates, and as always, happy building!

For more detailed documentation on these new features, visit portal.thirdweb.com.

Insight adds more data to token price API to also return market data, historical price data and holder count in addition to the price!

The following data is now included by default for each token:

percent_change_24h - Percentage change of the price over the last day

volume_24h_usd - Trading volume in USD over the last day

volume_change_24h - Percentage change of volume over the last day

market_cap_usd - Market cap value in USD

By specifying include_holders=true query param the number of on-chain holders of the token will also be returned

By including include_historical_prices=true query param, the response will contain a list of token prices per hour over the last 30 days.

Here is an example response for USDC on Ethereum

{
    "data": [
        {
            "chain_id": 1,
            "address": "0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48",
            "symbol": "USDC",
            "price_usd": 0.9998078912327243,
            "price_usd_cents": 100,
            "percent_change_24h": -0.02612099,
            "market_cap_usd": 60411059379,
            "volume_24h_usd": 10036602253,
            "volume_change_24h": 6.5387,
            "historical_prices": [
                {
                    "date": "2025-03-18 11:00:00",
                    "price_usd": 0.9998556959666844,
                    "price_usd_cents": 100
                },
                {
                    "date": "2025-03-18 12:00:00",
                    "price_usd": 0.9998533259452913,
                    "price_usd_cents": 100
                },
                {
                    "date": "2025-03-18 13:00:00",
                    "price_usd": 0.9998012400259259,
                    "price_usd_cents": 100
                },
                .... and so on over the next 30 days...
                
            ],
            "holders": 2994360
        }
    ]
}

Try it out in our playground

📖 Learn more about Insight - it’s open source and ready to power your applications!

We're constantly working to improve the developer and administrative experience of ecosystem wallets. Today, we're excited to announce two significant enhancements to Ecosystem Wallets, designed to give you more flexibility and control:

1. Unified User Search: Find users faster, regardless of the address you have.
2. Better Ecosystem Analytics: You can now see how each partner brings users to your ecosytem over time
3. Collaborative Partner Management: Empower your team to manage ecosystem partners and rules directly.

Let's dive into the details:

Managing users within your ecosystem just got easier. When you enable Account abstraction for you ecosystem, you can now query with users based on their originating Externally Owned Account (EOA) or their deployed Smart Account address. Previously, only EOA search was allowed.

What's New:

• You can now search for specific users within the Ecosystem Wallets dashboard using either their Signer Address (EOA) or their specific Smart Account address associated with your project.

How to Use:

const userDetails = await getUser({
  client,
  walletAddress: "0x...", // can be either EOA or smart account address
});

You can also use the backend API directly.

You can now view how much each partner is contributing to your ecosystem over time. Previously you could only see overall stats for the ecosystem.

What's New:

• Your ecosystem dashboard now shows connection analytics broken down by partner. So you can measure the success of each partner in your ecosystem.

How to Use:

• Simply navigate to your ecosystem page in the dashboard, and go to the analytics tab to see the new stats.

Managing the partners and rules that govern your ecosystem can now be done by anyone in your team. Previously, these configurations might have been restricted to the team owner.

What's New:

• Authorized team members within your thirdweb project now have the ability to add new Ecosystem Partners and edit the configurations and rules for existing partners directly from the dashboard.

How to Use:

• Team members with appropriate permissions can access the Ecosystem Partner configuration section within the thirdweb dashboard to add or modify partner details and rules. (Ensure your project's team roles are configured accordingly in the thirdweb dashboard settings).

These updates are live now in your thirdweb dashboard and SDKs.

Happy building!

We’ve just completed a full rollout of metadata performance upgrades across all NFT-related API routes — and started extending the same treatment to ERC20s.

Every API call involving NFT metadata now performs a single, efficient data read per request — even for multichain queries. Whether you're pulling transfers, balances, or metadata directly, things just got a whole lot faster.

🚀 Performance Gains: NFT Metadata Latency Drops by 10x+

We’ve slashed the latency for NFT metadata queries — and the numbers speak for themselves. For example, data for GET /v1/nfts/:contract_address

• GET /v1/nfts and GET /v1/nfts/transfers also saw solid improvements in the ~1.1× to 2.9× range, with reduced tail latencies and smoother performance across the board.
• Not just faster — more consistent, with reduced tail latencies and fewer spikes in production.
• These performance gains are now live for all metadata queries hitting the NFT endpoints.

We’ve started persisting ERC20 metadata as well, laying the foundation for more efficient token balance queries with rich metadata. Stay tuned — optimized joined queries are on the way.

We’ve consolidated NFT balance queries under a single route:
/v1/nfts/balance/{ownerAddress}
This new endpoint works across ERC721 and ERC1155 standards, supports multichain queries out of the box, and is the one we recommend going forward.

Heads up: the old ERC721/ERC1155-specific balance endpoints are still live, but are now officially deprecated.

This makes it easier than ever to query, display, and work with NFTs and tokens at scale — with less overhead and more consistency.

Insight adds two new endpoints - one to lookup a token based on symbols and one to retrieve an NFT collection's metadata.

Search for tokens by their symbol across 6000+ tokens.

Symbols are not unique nor strictly curated however, so be careful with how you use them!

To fetch all tokens with symbol ETH on Ethereum and B3

const lookupTokens = async (symbol: string) => {
  try {
    const response = await fetch(
      `https://insight.thirdweb.com/v1/tokens/lookup?symbol=${symbol}&chain=1`,
      {
        headers: {
          "x-client-id": <THIRDWEB_CLIENT_ID>,
        },
      },
    );
    const res = await response.json();
    return res.data;
  } catch (error) {
    console.error("Error:", error);
  }
};
await lookupTokens("ETH")

Try it out in our playground

Get metadata about an NFT collection.

By including a include_stats=true query param, you can also get the following statistics about a collection:

• owner_count - Amount of distinct addresses that hold the NFTs
• mint_count - Amount of NFT tokens that have been minted
• token_count - Amount of distinct token IDs that currently exist
• total_quantity - Amount of tokens that currently exist

const getCollectionMetadata = async (contractAddress: string) => {
  try {
    const response = await fetch(
      `https://1.insight.thirdweb.com/v1/nfts/collection/${contractAddress}?include_stats=true`,
      {
        headers: {
          "x-client-id": <THIRDWEB_CLIENT_ID>,
        },
      },
    );
    const res = await response.json();
    return res.data;
  } catch (error) {
    console.error("Error:", error);
  }
};

Try it out in our playground

📖 Learn more about Insight - it’s open source and ready to power your applications!

We're excited to announce that thirdweb Insight has expanded its blockchain data querying capabilities to 84 chains, adding these 17 new chains:

• Shape
• Unichain Sepolia
• Forma
• Flare
• Flare Coston2
• Berachain
• Berachain Bepolia
• Plume testnet
• Lens
• Mode testnet
• Blast Sepolia
• Arbitrum Nova
• World Chain Sepolia
• 0g Newton testnet
• Scroll Sepolia
• Linea Sepolia
• MegaETH testnet

What This Means For Developers
With these additions, you can now use all of Insight's powerful features across these new chains.

Try them out on the playground!

View All Supported Chains
For a complete list of supported chains and their respective chain IDs, check the thirdweb chainlist.

📖 Learn more about Insight - it’s open source and ready to power your applications!

We've added support for MAGIC on Treasure (61166) and GHO on Lens (232) to our Universal Bridge, bringing the total number of routes available to over 35,000. Check out the full API reference here to get started, or try it in the playground.

We’ve rolled out a series of performance upgrades across the board to make NFT metadata queries faster, smarter, and more reliable than ever.

• NFT metadata, ownership info, and token data are now pulled in a single optimised query internally, reducing the number of round trips and improving latency consistency.
• This makes NFT-related endpoints much more consistent at scale.

• Metadata is now fetched on-demand only when needed, skipping unnecessary lookups for already known or irrelevant data.
• We've introduced a system to automatically skip refetching metadata that’s deemed not worth roundtrips — improving efficiency without losing accuracy.

• Queries for metadata are now parallelised, making better use of compute resources.
• Owner and balance aggregations are now handled more effectively, ensuring both speed and correctness in multi-owner or high-traffic collections.

• Fixed a major issue where NFT transfers were duplicated across chains. Transfer data is now properly filtered per chain, ensuring clean and accurate results.
• Transfer endpoints now properly correlated to chain identification to avoid any confusion in multichain contexts.

All of these improvements won’t just apply to NFTs — we’re extending the same performance, consistency, and metadata logic enhancements to ERC20 tokens as well.

🔁 What's next? All of these improvements won’t just apply to NFTs — we’re extending the same performance, consistency, and metadata logic enhancements to ERC20 tokens as well.

💡 Result? lower and more predictable response times, better metadata hygiene, and fewer redundant operations — even across large multichain datasets.

Let us know what you think — or better yet, try it out and feel the speed.

Ever wondered if your token is supported on Universal Bridge? You can check all routes for a given token using the routes page. Search by chain ID, token address, token symbol, or name for all origin and destination routes. You can access the site at thirdweb.com/routes.

You can use the transactions array returned by a Universal Bridge prepared quote to easily execute a full route from origin to destination. This pattern is now even easier with transaction action fields included to denote what each transaction does. The most important of these actions is the approval type, which represents a pre-assembled approval transaction. The approval will account for the sender's existing set allowance and what token is needed for the next step.

A quote response might look something like this:

{
  id: "0xf04cca9127820d71ab8fe588ed9532d14d61ee883bfe29870873258646d8a03e",
  originAmount: "1003793",
  destinationAmount: "1000000",
  blockNumber: "133945469",
  timestamp: 1743489718527,
  estimatedExecutionTimeMs: 62000,
  intent: {
    originChainId: 10,
    originTokenAddress: "0x0b2C639c533813f4Aa9D7837CAf62653d097Ff85",
    destinationChainId: 8453,
    destinationTokenAddress: "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
    buyAmountWei: "1000000",
    sender: "0x2a4f24F935Eb178e3e7BA9B53A5Ee6d8407C0709",
    receiver: "0x2a4f24F935Eb178e3e7BA9B53A5Ee6d8407C0709",
  },
  transactions: [
    {
      chainId: 10,
      to: "0x0b2C639c533813f4Aa9D7837CAf62653d097Ff85",
      data: "0x...",
      type: "eip1559",
      id: "0x723a578f5f04178f410da8e2029c138d4cad76900a9d9e650603fc64e56e113b",
      action: "approval",
    }, {
      to: "0x81d57DD01a15BC1C19563693902df621500D4d2A",
      value: "0",
      data: "0x...",
      chainId: 10,
      from: "0x2a4f24F935Eb178e3e7BA9B53A5Ee6d8407C0709",
      type: "eip1559",
      action: "buy",
      id: "0x3f0cb9f8a3e8649284d5c3f44648237f821c19de490fce9572509d79292867dc",
    }
  ],
}

To execute this bridge with the TypeScript SDK, use sendAndConfirmTransaction to send each transaction, and wait for a successful Bridge.status response for each non-approval transaction:

import { Bridge, sendAndConfirmTransaction } from "thirdweb";
 
for (const tx of preparedBuy.transactions) {
  const hash = await sendAndConfirmTransaction({
    transaction: prepareTransaction(tx),
    account, // Learn to generate a thirdweb account https://portal.thirdweb.com/connect/wallet/get-started
  });
 
  if (tx.action !== "approval") {
    // Wait for Bridge.status to return "COMPLETED" status
  }
}

It's that easy to implement bridging and swapping in your app. Want to get started? You can find the full API reference here.

Insight now supports webhooks so you can build pipelines and receive notifications when specific blockchain events or transactions occur!

With the introduction of webhook support in Insight, you can now seamlessly integrate blockchain data into your applications or workflows. Webhooks allow you to automatically receive near real-time notifications whenever specific blockchain events or transactions occur, eliminating the need for constant polling of the blockchain.

• Automate Workflows: Trigger actions in your applications or services when a specific blockchain event happens (e.g., a token transfer, contract interaction, or wallet activity).
• Monitor Blockchain Events: Stay updated on relevant events without manually querying the blockchain.
• Build Custom Pipelines: Use webhooks to feed blockchain data into analytics tools, databases, or other systems for further processing.
• Filter Specific Data: Configure webhooks to only receive notifications for events or transactions that meet your specific criteria, such as a particular contract address or event type.

Yes! Insight webhooks provide decoded data for events and transactions. This means you’ll receive human-readable payloads that include all relevant details, such as parameters and values associated with the event or transaction. This makes it easier to process and use the data directly in your applications without additional decoding steps.
To enable this, you have to define specific event signatures / function signatures and partial ABIs in the webhook filter configurations.

For more details on setting up and managing webhooks, visit the following resources:

• Managing Webhooks
• Filtering Webhook Data
• Webhook Payload Structure
• API Reference

📖 Learn more about Insight - it’s open source and ready to power your applications!

We’ve released the Agglayer Module, designed to enable secure and seamless cross-chain transfers of ERC-20 tokens using Agglayer, an interoperability protocol. Learn more about Agglayer.

Please note: This module is currently in beta while the Agglayer bridge is not live in implementation. This means deployments are limited to Sepolia and Cardona as it requires Ethereum as an L1 and zkEVM as L2.

The Agglayer Module is a module contract that can be added to any ERC-20 modular contract built with thirdweb’s modular framework. It allows developers to bridge ERC-20 tokens across any EVM-compatible chain.

As the Ethereum ecosystem continues to grow with the introduction of more Layer 2 networks, fragmented liquidity and isolated user experiences have become major challenges. Without interoperability, assets are locked within specific chains, limiting usability and adoption.

The Agglayer Module helps address this by enabling interoperability at the contract level—allowing tokens to move freely across chains, reducing fragmentation, and improving the overall developer and user experience.

• EVM-compatible – Works across all EVM chains
• Modular and upgradeable – Can be installed or removed from any ERC-20 modular contract
• Dashboard integration – Easily install through the thirdweb dashboard with no additional configuration
• Cross-chain functionality – Mint tokens and send them to other chains seamlessly

• The module currently only works with ERC-20 modular contracts
• It must be installed on the contract in order to function

1. Use or deploy an ERC-20 modular contract
2. Add the Agglayer Module through the thirdweb dashboard
3. Mint and bridge tokens as needed

📚 View the full tutorial

As always, please don't hesitate to contact us for any questions or support.

Insight added support for querying a wallet's transactions (both inbound and outbound). Previously this had to be two separate queries, but can now be done by a single query.

Try it out in our playground

To fetch a wallet's transactions on Ethereum

const getWalletTransactions = async (walletAddress: string) => {
  try {
    const response = await fetch(
      `https://1.insight.thirdweb.com/v1/wallets/${walletAddress}/transactions`,
      {
        headers: {
          "x-client-id": <THIRDWEB_CLIENT_ID>,
        },
      },
    );
    const res = await response.json();
    return res.data;
  } catch (error) {
    console.error("Error:", error);
  }
};

📖 Learn more about Insight - it’s open source and ready to power your applications!

With v5.93.0 of the TypeScript SDK, we've added full beta functionality for thirdweb's new Universal Bridge. The bridge currently covers 50+ chains and over 30,000 routes.

• Bridge.Buy - Specify an exact destination amount to receive
  • quote: Get estimates without a wallet connection
  • prepare: Get finalized quotes with transaction data
• Bridge.Sell - Specify the exact origin amount to send
  • quote: Get estimates without a wallet connection
  • prepare: Get finalized quotes with transaction data

When you call prepare, you might get multiple transactions back. You must send all transactions in order and sequentially for the full route to succeed. Before sending each transaction, call Bridge.status for the previous transaction until it returns COMPLETED. Do not simply wait for the transaction receipt, as this doesn't account for the destination chain transaction (if there is one).

The transactions returned do not include approvals. Send any necessary approvals before their corresponding transactions.

• Bridge.routes - Advanced function to discover and filter available bridge routes
  • Filter by token address, chain ID, or both
  • Full pagination support with customizable limit and offset
• Bridge.status - Comprehensive transaction status tracking
  • Clear status indicators: "COMPLETED", "PENDING", "FAILED", or "NOT_FOUND"
  • Detailed transaction reporting including origin and destination amounts and chains

• Standardized error handling with descriptive, formatted error messages
• Four underlying types are exported for use with the bridging functions:
  • Route: Defines bridge routes between chains and tokens
  • Status: Represents bridge transaction status data
  • Quote: Contains detailed bridge transaction quote information
  • PreparedQuote: Extends Quote with complete transaction data

import { Bridge, toWei, NATIVE_TOKEN_ADDRESS } from "thirdweb";
 
// First, get a quote to see approximately how much you'll pay
const buyQuote = await Bridge.Buy.quote({
  originChainId: 1, // Ethereum
  originTokenAddress: NATIVE_TOKEN_ADDRESS,
  destinationChainId: 10, // Optimism
  destinationTokenAddress: NATIVE_TOKEN_ADDRESS,
  buyAmountWei: toWei("0.01"), // I want to receive 0.01 ETH on Optimism
  client: thirdwebClient,
});
 
console.log(
  `To get ${buyQuote.destinationAmount} wei on destination chain, you need to pay ${buyQuote.originAmount} wei`,
);
 
// When ready to execute, prepare the transaction
const preparedBuy = await Bridge.Buy.prepare({
  originChainId: 1,
  originTokenAddress: NATIVE_TOKEN_ADDRESS,
  destinationChainId: 10,
  destinationTokenAddress: NATIVE_TOKEN_ADDRESS,
  buyAmountWei: toWei("0.01"),
  sender: "0x...", // Your wallet address
  receiver: "0x...", // Recipient address (can be the same as sender)
  client: thirdwebClient,
});
 
// The prepared quote contains the transactions you need to execute
console.log(
  `Transactions to execute: ${preparedBuy.transactions.length}`,
);

import { Bridge, toWei } from "thirdweb";
 
// First, get a quote to see approximately how much you'll receive
const sellQuote = await Bridge.Sell.quote({
  originChainId: 1, // Ethereum
  originTokenAddress: NATIVE_TOKEN_ADDRESS,
  destinationChainId: 10, // Optimism
  destinationTokenAddress: NATIVE_TOKEN_ADDRESS,
  sellAmountWei: toWei("0.01"), // I want to sell 0.01 ETH from Ethereum
  client: thirdwebClient,
});
 
console.log(
  `If you send ${sellQuote.originAmount} wei, you'll receive approximately ${sellQuote.destinationAmount} wei`,
);
 
// When ready to execute, prepare the transaction
const preparedSell = await Bridge.Sell.prepare({
  originChainId: 1,
  originTokenAddress: NATIVE_TOKEN_ADDRESS,
  destinationChainId: 10,
  destinationTokenAddress: NATIVE_TOKEN_ADDRESS,
  sellAmountWei: toWei("0.01"),
  sender: "0x...", // Your wallet address
  receiver: "0x...", // Recipient address (can be the same as sender)
  client: thirdwebClient,
});
 
// Execute the transactions in sequence
for (const tx of preparedSell.transactions) {
  // Send the transaction using your wallet
  // Wait for it to be mined
}

import { Bridge, NATIVE_TOKEN_ADDRESS } from "thirdweb";
 
// Get all available routes
const allRoutes = await Bridge.routes({
  client: thirdwebClient,
});
 
// Filter routes for a specific token or chain
const filteredRoutes = await Bridge.routes({
  originChainId: 1, // From Ethereum
  originTokenAddress: NATIVE_TOKEN_ADDRESS,
  destinationChainId: 10, // To Optimism
  client: thirdwebClient,
});
 
// Paginate through routes
const paginatedRoutes = await Bridge.routes({
  limit: 10,
  offset: 0,
  client: thirdwebClient,
});

import { Bridge } from "thirdweb";
 
// Check the status of a bridge transaction
const bridgeStatus = await Bridge.status({
  transactionHash:
    "0xe199ef82a0b6215221536e18ec512813c1aa10b4f5ed0d4dfdfcd703578da56d",
  chainId: 8453, // The chain ID where the transaction was initiated
  client: thirdwebClient,
});
 
// The status will be one of: "COMPLETED", "PENDING", "FAILED", or "NOT_FOUND"
if (bridgeStatus.status === "completed") {
  console.log(`
    Bridge completed!
    Sent: ${bridgeStatus.originAmount} wei on chain ${bridgeStatus.originChainId}
    Received: ${bridgeStatus.destinationAmount} wei on chain ${bridgeStatus.destinationChainId}
  `);
} else if (bridgeStatus.status === "pending") {
  console.log("Bridge transaction is still pending...");
} else {
  console.log("Bridge transaction failed");
}

try {
  await Bridge.Buy.quote({
    // ...params
  });
} catch (error) {
  // Errors will have the format: "ErrorCode | Error message details"
  console.error(error.message); // e.g. "AmountTooHigh | The provided amount is too high for the requested route."
}

The Bridge module is accessible as a top-level export:

import { Bridge } from "thirdweb";

Use Bridge.Buy, Bridge.Sell, Bridge.routes, and Bridge.status to access the corresponding functionality.

Or, import the functions directly from the module:

import { Buy, Sell, routes, status } from "thirdweb/bridge";

We've built Universal Bridge to allow your users to use any asset on any chain, and it's ready for you to try.

This integration simplifies onchain asset trading, and we've added extensions in .NET to integrate with any IThirdwebWallet nicely.

The design is akin to letting us know what your intent is.

• Buy: "I want to buy x USDC on y Chain using z Token"
• Sell: "I want to sell x USDC on y Chain for z Token"
• Transfer: "Just transfer all my money to vitalik"

We will return the transactions needed to achieve whatever you desire.
You may then handle execution yourself or use our extensions.

using Thirdweb.Bridge;
// Create a ThirdwebBridge instance
var bridge = await ThirdwebBridge.Create(client);

var buyQuote = await bridge.Buy_Quote(
    originChainId: 1,
    originTokenAddress: "0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48", // USDC on Ethereum
    destinationChainId: 324,
    destinationTokenAddress: Constants.NATIVE_TOKEN_ADDRESS, // ETH on zkSync
    buyAmountWei: BigInteger.Parse("0.1".ToWei())
);
Console.WriteLine($"Buy quote: {JsonConvert.SerializeObject(buyQuote, Formatting.Indented)}");

var preparedBuy = await bridge.Buy_Prepare(
    originChainId: 1,
    originTokenAddress: "0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48", // USDC on Ethereum
    destinationChainId: 324,
    destinationTokenAddress: Constants.NATIVE_TOKEN_ADDRESS, // ETH on zkSync
    buyAmountWei: BigInteger.Parse("0.1".ToWei()),
    sender: await Utils.GetAddressFromENS(client, "vitalik.eth"),
    receiver: await myWallet.GetAddress()
);
Console.WriteLine($"Prepared Buy contains {preparedBuy.Transactions.Count} transaction(s)!");

var sellQuote = await bridge.Sell_Quote(
    originChainId: 324,
    originTokenAddress: Constants.NATIVE_TOKEN_ADDRESS, // ETH on zkSync
    destinationChainId: 1,
    destinationTokenAddress: "0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48", // USDC on Ethereum
    sellAmountWei: BigInteger.Parse("0.1".ToWei())
);
Console.WriteLine($"Sell quote: {JsonConvert.SerializeObject(sellQuote, Formatting.Indented)}");

var preparedSell = await bridge.Sell_Prepare(
    originChainId: 324,
    originTokenAddress: Constants.NATIVE_TOKEN_ADDRESS, // ETH on zkSync
    destinationChainId: 1,
    destinationTokenAddress: "0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48", // USDC on Ethereum
    sellAmountWei: BigInteger.Parse("0.1".ToWei()),
    sender: await Utils.GetAddressFromENS(client, "vitalik.eth"),
    receiver: await myWallet.GetAddress()
);
Console.WriteLine($"Prepared Sell contains {preparedSell.Transactions.Count} transaction(s)!");

Why not just transfer with the SDK? Stay tuned for webhooks, think direct payments!

var preparedTransfer = await bridge.Transfer_Prepare(
    chainId: 137,
    tokenAddress: Constants.NATIVE_TOKEN_ADDRESS, // ETH on zkSync
    transferAmountWei: BigInteger.Parse("0.1".ToWei()),
    sender: await Utils.GetAddressFromENS(client, "vitalik.eth"),
    receiver: await myWallet.GetAddress()
);
Console.WriteLine($"Prepared Transfer: {JsonConvert.SerializeObject(preparedTransfer, Formatting.Indented)}");

This is not production code, we're just showcasing some of the APIs that would help you execute and poll status here.

// You may use our extensions to execute yourself...
var myTx = await preparedTransfer.Transactions[0].ToThirdwebTransaction(myWallet);
var myHash = await ThirdwebTransaction.Send(myTx);
// ...and poll for the status...
var status = await bridge.Status(transactionHash: myHash, chainId: 1);
var isComplete = status.StatusType == StatusType.COMPLETED;
Console.WriteLine($"Status: {JsonConvert.SerializeObject(status, Formatting.Indented)}");
// Or use our Execute extensions directly to handle everything for you!

The SDK comes with some extensions that you'll see on a lot of ThirdwebBridge objects, and the main one is Execute.

// Execute a prepared Buy
var buyResult = await bridge.Execute(myWallet, preparedBuy);
var buyHashes = buyResult.Select(receipt => receipt.TransactionHash).ToList();
Console.WriteLine($"Buy hashes: {JsonConvert.SerializeObject(buyHashes, Formatting.Indented)}");
// Execute a prepared Sell
var sellResult = await bridge.Execute(myWallet, preparedSell);
var sellHashes = sellResult.Select(receipt => receipt.TransactionHash).ToList();
Console.WriteLine($"Sell hashes: {JsonConvert.SerializeObject(sellHashes, Formatting.Indented)}");
// Execute a prepared Transfer
var transferResult = await bridge.Execute(myWallet, preparedTransfer);
var transferHashes = transferResult.Select(receipt => receipt.TransactionHash).ToList();
Console.WriteLine($"Transfer hashes: {JsonConvert.SerializeObject(transferHashes, Formatting.Indented)}");

Full Bridge .NET Reference

.NET Release | NuGet Release | Unity Release
Documentation | Support

We've built Universal Bridge to allow your users to use any asset on any chain, and it's ready for you to try. If you're interested in joining the private beta for Universal Bridge, complete this form (or reach out to anyone from the thirdweb team).

Do you need to accept fiat and crypto payments in your app? Are you struggling to find reliable onchain liquidity for swaps? Are you tired of implementing bespoke bridges for multiple chains? Universal Bridge is for you.

Bridging, swapping, and accepting payments each bring their own challenges. The existing options are unreliable, complicated, and reliant on poor design choices. Universal Bridge is the easiest way to route assets in your app. Swap tokens, bridge between chains, onramp assets, accept onchain payments, and more all with a simple, unified API.

We already support 30,000+ routes across 50+ chains and are adding more every day. We're running detailed routing and reliability tests across all of them to guarantee a great experience for users.

Universal Bridge uses a combination of existing protocols and onramps with thirdweb's own onchain and off-chain infrastructure for maximum coverage and reliability. The result is a "best case scenario" for buying, selling, and transferring assets between any EVM chain.

Our Private Beta starts today, and your app can be one of the first to use it. Just complete this form or reach out to anyone on the team to get access. Or, try the playground widget here.

We're excited to announce that thirdweb Insight has expanded its blockchain data querying capabilities to 67 chains, including these 7 new chains:

• Sonic testnet
• Scroll
• Linea
• Zero mainnet
• Zero testnet
• Blast
• Mode

What This Means For Developers
With these additions, you can now use all of Insight's powerful features across these new chains.

Try them out on the playground!

View All Supported Chains
For a complete list of supported chains and their respective chain IDs, check the thirdweb chainlist.

📖 Learn more about Insight - it’s open source and ready to power your applications!

We've revamped our metadata storage and refresh mechanisms to provide a more reliable, scalable, and efficient experience when working with NFT collections metadata through Insight!

• Replaced the previous caching approach with a more permanent storage solution, ensuring faster retrieval and better consistency across requests.
• Metadata is now stored and accessed in a way that eliminates potential inconsistencies, making it the single source of truth for retrieval.

To give developers more control, we’ve introduced dedicated API endpoints for refreshing metadata on demand:

• Collection Metadata Refresh
  • GET v1/nfts/metadata/refresh/:contract_address
• Token Metadata Refresh
  • GET v1/nfts/metadata/refresh/:contract_address/:token_id
• Both endpoints fully support multichain operations via chain query parameters.
• Refreshing token metadata also ensures collection-level metadata stays up to date.

✅ Improved Data Consistency – Eliminates mismatches between different layers, ensuring metadata stays accurate.
✅ Simplified Architecture – No more juggling between temporary and permanent storage solutions.
✅ Better Scalability – Optimized for large-scale metadata operations, enabling more efficient handling of growing datasets.
✅ Multichain-Ready – Works seamlessly across chains, just like you’re used to.

We’re actively working on further performance optimizations by consolidating multiple separate queries into more efficient, single-fetch operations. This will unlock even faster metadata retrieval without sacrificing accuracy. Stay tuned with more updates to thirdweb Insight! 🚀

This new update includes several changes to the tools in thirdweb MCP (Model Context Protocol) Server – improving overall accuracy in tool selection and speed performance for some onchain queries.

Improvement and Fixes

• Improved onchain query performance and tool selection
• Fixed Engine service auth requests that were not configured properly
• Updated thirdweb-ai to v0.1.4 (see full changelog)

A few prompts and guide to try out:

• What is the price of ETH? or What is the price of UNI token?
• Show me the recent events for 0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48 on Ethereum (1)
• What are the recent transactions from 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045 on Base (8453)?
• What is the ABI of 0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48 on Ethereum (1)
• Transfer 0.00001 ETH to 0xEb0effdFB4dC5b3d5d3aC6ce29F3ED213E95d675 on Sepolia (11155111)

Always provide a fully valid wallet address, and include chain id along with the chain name.

Upgrade Guide

# Using pipx
pipx upgrade thirdweb-mcp
 
# Using uvx
uvx --upgrade thirdweb-mcp

This new update focuses on improving the accuracy of tool selection by consolidating tools, picking better default values, and giving developers the ability to override tool description prompts.

New Features

• Override service tools' description prompts

from thirdweb_ai import Insight
 
insight = Insight(secret_key=...)
 
# using default tool description
tools = [insight.get_all_transactions()]
 
# using custom tool description
tools = [insight.get_all_transactions(description="Call this to fetch transactions for account")]

Improvements

• Insight always requests with most recent and decoded data
• Insight performance improvement by using the correct sort key
• Updated resolve tool prompt to provide a more accurate description
• Reduced number of tools with similar functionality:
  • Merged get_contract_abi into get_contract_metadata
  • Merged get_contract_events_by_signature into get_all_events

Bug Fixes

• Fixed invalid auth for Engine requests due to headers not being set correctly
• Fixed some invalid paths or bodies for Engine and Insight tools
• Fixed improper schema error from OpenAI Agents adapter when a tool schema contains anyOf, oneOf, or allOf

Upgrade Guide

# pip
pip install thirdweb-ai --upgrade
# poetry
poetry update thirdweb-ai
# uv
uv add thirweb-ai --upgrade

We just released a new live playground that lets you customize and interact with the Universal Bridge via the prebuilt UI component.

Try it out at: https://playground.thirdweb.com/connect/pay

The playground lets you customize:

• Payment mode: fund wallets, direct payments or onchain transactions
• Price, chain and token information
• Payment methods
• Metadata
• Theme
• Gas sponsorship

Every customization shows you the changes in a live preview, as well as the corresponding code to copy paste into your projects.

Happy building! 🛠️

We're excited to announce the first release of thirdweb ai, a powerful Python library (TypeScript coming soon) that enables AI agents to interact with any EVM chains autonomously using thirdweb. This is a significant step forward in our mission to make web3 more accessible and empower developers to build the next generation of AI-powered onchain applications.

As Large Language Models (LLMs) and AI Agents continue to evolve as transformative technologies, we recognized the need for these systems to interact with blockchain networks autonomously. We believe that giving AI agents the ability to perform onchain actions based on real-time data will unlock new possibilities.

With thirdweb ai, you can create AI agents that:

• Manage wallets and transactions securely using Engine
• Retrieve and analyze on-chain data in real-time using Insight
• Delegate complex onchain executions to Nebula agents

All of this functionality integrates smoothly with the AI agent framework of your choice, including OpenAI Agents, LangChain, AgentKit, GOAT, AutoGen, LlamaIndex, and many more.

Install the core package with all adapters:

pip install "thirdweb-ai[all]"

Or choose specific framework adapters:

# For OpenAI Agents
pip install "thirdweb-ai[openai]"
 
# For LangChain
pip install "thirdweb-ai[langchain]"
 
# For AutoGen
pip install "thirdweb-ai[autogen]"
 
# For LlamaIndex
pip install "thirdweb-ai[llama-index]"
 
# For additional frameworks
pip install "thirdweb-ai[goat]"
pip install "thirdweb-ai[agentkit]"
pip install "thirdweb-ai[mcp]"
pip install "thirdweb-ai[smolagents]"
pip install "thirdweb-ai[pydantic-ai]"

See here for the full list of supported framework and installation guides.

from thirdweb_ai import Engine, Insight, Nebula, Tool
 
# Initialize thirdweb services
insight = Insight(secret_key=...)
nebula = Nebula(secret_key=...)
engine = Engine(secret_key=..., engine_url=..., engine_auth_jwt=...)
 
# Get available tools
tools = [
    # Access powerful web3 tools
    # Optionally, select tool from each services
    *insight.get_tools(),  # Giving agents real-time on-chain data access
    *engine.get_tools(),   # Wallet and transaction management
    *nebula.get_tools(),   # Agent for complex blockchain tasks
]

from thirdweb_ai import Tool
from thirdweb_ai.adapters.openai import get_openai_tools
 
# Initialize your thirdweb tools
tools = [...]  # List of thirdweb tools
 
# Convert to OpenAI tools
openai_tools = get_openai_tools(tools)
 
# Use in your OpenAI Agent
agent = Agent("thirdweb_agent", tools=openai_tools, ...)

from thirdweb_ai import Tool
from thirdweb_ai.adapters.langchain import get_langchain_tools
 
# Initialize your thirdweb tools
tools = [...]  # List of thirdweb tools
 
# Convert to LangChain tools
langchain_tools = get_langchain_tools(tools)
 
# Use in your LangChain agent
agent = create_tool_calling_agent(tools=langchain_tools, ...)

When building applications that integrate LLMs with thirdweb's blockchain capabilities, you can enhance your results by including thirdweb context files:

• Basic context: https://portal.thirdweb.com/llms.txt
• Comprehensive context: https://portal.thirdweb.com/llms-full.txt

• Check out our GitHub repository for more examples

Get started with thirdweb-ai today and join us in building the future of onchain AI agents!

We just shipped a big upgrade to partner management for ecosystems. You can now specify what type of signatures are permitted for each partner, as well as granular controls on what exactly can be signed. As an ecosystem owner, this means you have full control of what each partner is able to do with your user's ecosystem wallets, like restricting to particular assets or actions.

In your ecosystem dashboard, you'll find a new option for "Access Control" when you create or edit an ecosystem partner. You can setup these signing restrictions in 2 ways: your own server verification, or built in rules.

This is the most flexible and powerful option - every signature request will flow through your own server and you get to perform your own logic for allowing or disallowing a particular signature.

The response from your sever should just be a simple JSON body with the following format.

{ 
  isAllowed: boolean;
  reason?: string;
}

You can also set your rules directly in the dashboard. These include what signature types you would like to allow, and granular permissions per signature type, like the chain, contract addresses or function selectors that are allowed to be called.

For ecosystems that use smart accounts, since those require personal_sign signatures, we've added a user operation filter that lets you control which smart account operations are allowed to be signed by the ecosystem wallets.

These controls are low level and powerful, letting you tightly control what can and cannot be done with wallets on a per-partner basis.

We're continuously improving this UI to make it easier for ecosystem owners to setup these rules. Your feedback is appreciated and help us make this product better for everyone!

We're excited to announce improvements to our Token and NFT APIs in Insight. We've recently added support to get all token transfers by owner, wallet, and token contracts. We've also included in this release major performance improvements to existing NFT endpoints.

The following endpoints are now available to use.