Prime

When one model isn't enough

A curated swarm of frontier models runs in parallel and picks the best answer

For complex tasks, irreversible actions, and the moments when your agent needs to be right.

Beats
Frontiers

Multiple models run in parallel. The strongest answer wins.

Built
for Agents

Native MCP. One skill to add, works in any workflow.

Doesn't Break
Under Pressure

When one model is misled, others correct it.

ReasoningHighest
SpeedMedium
InputText
OutputText
Context window500,000 tokens
Max output tokens128,000 tokens
ToolsWeb search
Price per 1M tokens

$10 input · $30 output

Start using Fortytwo Prime

1

Choose where you want to use Fortytwo Prime

Agent

Send this to your agent

Your App

Follow an integration guide from documentation

Integration Guide
2

Provide your agent or app with web3 wallet with USDC on Monad or Base.
We use x402Escrow protocol to handle secured payments.

3

Use the command Ask Fortytwo to get the best answer from the network.
Your agent will automatically invoke it when needed to solve complex tasks.

Fortytwo Platform

Monitor calls, usage, and cost across your agents

Continue with web3 wallet

FAQs

Fortytwo MCP is an orchestration layer that allows any MCP-compatible client to access Fortytwo Network directly.

It implements the Model Context Protocol—a standard that exposes available tools to applications, AI models, and agents so they can interact with external services.

Yes. MCP is a protocol that exposes Fortytwo tools to an app, model, or agent so that they can easily access Fortytwo.

Yes. MCP works without an API key. Instead, x402Escrow protocol will serve as your authorization and payment method by utilizing your web3 wallet.

x402Escrow enables low-cost payments for AI inference while allowing the user to remain in control of their wallet and expenses.

x402Escrow is a special variation of x402 protocol that is designed by Fortytwo specifically to enable usage-based, pay-per-token billing for AI services, charging only for the tokens used. It works in two steps:

  1. Estimated USDC amount is reserved in an escrow contract.
  2. Inference result is provided to the user, the amount for that result is charged, and the remaining funds are released back to the user.

The key difference between x402 and x402Escrow:

  • x402 protocol relies on fixed price endpoints where costs are known before the operation.
  • x402Escrow is specifically built to handle AI inference usage cases, where the costs are unknown at request time and only become known when inference is completed.

Learn more here:

x402Escrow requires at least 2 USDC on Base or Monad. This should be enough to cover multiple requests within a session.

USDC payments are accepted on:

  • Monad eip155:143
  • Base eip155:8453

The contract is deployed on Monad and Base networks: