Quote Pipeline & Auction#

The RFQ auction engine is the core of TetraFi's execution layer. It broadcasts trade requests to qualified solvers, collects competing quotes, and selects the winner using UCCP pricing.

const rfq = await tetrafi.rfq.create({
  pair: "USDC/USDT",
  side: "buy",
  amount: "1000000.00",
  corridor: "ethereum-optimism",
  maxSlippage: 0.001,
});
console.log(`RFQ: {rfq.id}, status: {rfq.status}`);

Four modes via quotePreference parameter:

Every RFQ is either Exact Input ("I have X, how much Y?") or Exact Output ("I need Y, how much X does it cost?"). The swap type is carried on the MandateOutput context byte and resolved by the OutputSettler at fill time.

See Settlement Flows → Order Types for the full context-byte reference, including Limit, Dutch Auction, and Exclusive variants.

Solver selection is configured per-request via solverOptions. Three strategies control which solvers receive the RFQ:

Solver reliability is tracked on a 24-hour rolling window. Fill rate = successful_fills / (successful_fills + repudiations).

When multiple RFQs arrive for the same corridor within a batch window, the engine can net them - offsetting flows cancel out, reducing solver capital and gas costs. Four matching modes (Simple, Batching, Intermediate, Ring) are covered in detail in Intent Netting → Matching Engine.

If no solver responds within the RFQ window, the order can fall back to a Dutch auction mode with three time-based phases:

The fee ramps linearly between phases, attracting solvers by offering improving economics over time.

Two-layer adapter pattern normalizes solver protocols:

• Layer 1 (SolverAdapter) - protocol-specific → standard GetQuoteRequest/Response
• Layer 2 (SolverAdapterTrait) - runtime config, metrics, error categorization, timeouts

The contract below is the Open Intents Framework v0 REST spec - an open standard, not a TetraFi-specific protocol. Any solver already OIF-compliant against other intent networks can be pointed at TetraFi with configuration alone. On-chain, TetraFi implements ERC-7683 StandardOrder typed data, signed by takers via EIP-712.

TetraFi's aggregator calls your HTTPS endpoints during the auction window. You do not maintain a persistent connection to TetraFi to receive RFQs - there is no SDK or WebSocket required for quote participation.

Four endpoints your solver must expose (OIF v0, camelCase wire format):

Request

1{
2  "user": "0x…",
3  "intent": { "inputToken": "0x…", "outputToken": "0x…", "inputAmount": "1000000000000", "originChainId": 8453, "destinationChainId": 10 },
4  "supportedTypes": ["oif-swap", "oif-escrow-v0"]
5}

Response

1{
2  "quotes": [
3    {
4      "quoteId": "qt_…",
5      "order": { /* StandardOrder - see Settlement Flows */ },
6      "validUntil": 1734375600,
7      "eta": 12,
8      "provider": "acme",
9      "failureHandling": "refund",
10      "partialFill": false,
11      "preview": { "outputAmount": "999725000000", "feeBps": 2.75 },
12      "metadata": {}
13    }
14  ]
15}

Request

1{
2  "order": { /* StandardOrder */ },
3  "signature": "0x…",
4  "quoteId": "qt_…",
5  "originSubmission": { "txHash": "0x…" },
6  "metadata": {}
7}

Response: { "orderId": "…", "status": "Deposited | Filled | Attested | Claimed | Refunded", "message": "…", "order": { … }, "metadata": {} }

Either JWT via POST /auth/register + POST /auth/refresh (OIF-defined), or a pre-shared bearer header - configured per solver at onboarding.

The aggregator terminates early once min_quotes have been received, avoiding unnecessary wait time.