HTTP API

https://exen.wraxyn.io/v1/quote?chainId=8453&mode=sell&…

Every route is served without credentials. Sending a partner key in the x-api-key header unlocks the partner configuration held against it:

• A rate budget of your own, instead of sharing the anonymous per-IP one with everyone else on your network.
• Attribution. Your partner id is hashed into the on-chain tag of every settlement, so fills you routed are identifiable on-chain and reconcilable to your responses.
• A negotiated fee policy, which overrides any fee in the request.
• Access to gated venues. A few venues price only for allowlisted parties (tokenised real-world assets, for instance) and are invisible without an approved key.

Limits are applied at the edge, before a request reaches the engine.

• Over-budget requests are rejected at the edge. Back off and retry rather than retrying immediately — a tight retry loop spends the next second's budget too.
• Cache nothing that prices. A quote is a point in time; a cached one is not a cheaper quote, it is a wrong one.
• If you need a lot of quotes, timeLimitMs is the lever that matters more than the rate — see latency.

Solves the best route for a pair and size at the current block and returns exact integer amounts, the per-hop route breakdown, gas and USD values.

curl -s "https://exen.wraxyn.io/v1/quote\
?chainId=8453&mode=sell\
&sellToken=0xeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee\
&buyToken=0x833589fcd6edb6e08f4c7c32d4f71b54bda02913\
&sellAmount=1000000000000000000\
&slippagePct=0.5" \
  -H "x-api-key: $EXEN_KEY"

Identical pricing and identical parameters, plus a required taker. It then firms up any market-maker legs with their makers and encodes the route into a transaction. The response is the quote body flattened at the top level plus the execution fields.

The budget is stamped when the request arrives, so queueing counts against it. Enforcement is best-effort: direct routes are always evaluated, and deeper search stops at the deadline.

• Fees are taken on the buy token, and buyAmount / minBuyAmount are returned net of them — you can show the returned number to your user as-is.
• Set your own with feeBps + feeRecipient (capped at 1500 bps = 15%). A request-supplied fee splits 85% to your recipient, 15% to the protocol.
• A fee policy negotiated against your API key overrides anything in the request.
• On a buy, the routing target is grossed up so your user still receives exactly what they asked for after the fee.

warnings[] is omitted when empty. Every code leaves the transaction executable — a warning means the response degraded on the way, never that the calldata is unusable. A request that cannot produce an executable route returns an error instead.

The body is { "error": "…" }. There are no stable machine codes on errors — branch on the status, never on the message text. (Success-path degradations do have stable codes: the warnings above.)

The venue labels routable on a chain — the exact strings route[].source reports and excludeVenues / includeVenues accept. It is the only place those strings are enumerated, so read them from here rather than hard-coding a list that grows without you.

curl -s "https://exen.wraxyn.io/v1/base/sources"

{ "chain_id": 8453, "chain": "base",
  "sources": ["aerodrome-v1", "uniswap-v3", "uniswap-v4:doppler", …] }

{chain} is a path segment here, not the chainId query parameter quote and swap use: a name (ethereum, base, arbitrum, bsc, avalanche, xlayer), a common alias (eth, bnb, avax) or the numeric id. This response is snake_case, unlike quote and swap — a known inconsistency, not a typo in your client.

The API has a full OpenAPI 3.1 specification — every path, parameter, schema and error response, suitable for generating a typed client or loading into Swagger, Redoc, Postman or Insomnia. Everything in it is also written out on this page in prose, so you can integrate without it.

It is not yet published at a public URL. Ask admin@wraxyn.io and we will send you the current file. If the spec and this page ever disagree, the spec is right — it is generated alongside the wire contract and this page follows it.

# 1. Build the transaction (native sell ⇒ no approval needed)
curl -s "https://exen.wraxyn.io/v1/swap\
?chainId=1&mode=sell\
&sellToken=0xeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee\
&buyToken=0xdac17f958d2ee523a2206206994597c13d831ec7\
&sellAmount=1000000000000000000\
&taker=$TAKER&slippagePct=0.3&timeLimitMs=299" \
  -H "x-api-key: $EXEN_KEY" \
  | jq '{buyAmount, minBuyAmount, gasUsd,
         to: .transaction.to, value: .transaction.value,
         route: [.route[] | {source, bps, amountIn, amountOut}]}'

# 2. eth_estimateGas against .transaction  — the final validity check
# 3. Sign and send it from $TAKER

# ERC-20 sell instead? One extra step first:
#   approve(<allowanceTarget from the response>, <sellAmount>)  from $TAKER

timeLimitMs=299 above is the latency-critical profile: on-chain venues only, deterministic. Drop it (or raise it past 300) to let market makers compete for the fill.