my-app-name with your partner key and userAddress with the executing wallet.
Gasless Delta swap
The default flow for swaps that need MEV protection or gasless execution. The server quotes; the Delta order itself is built, signed, and submitted through the Delta API, outside the server.- Route the intent (skip if you already know the mode):
velora_decide_execution_route
recommendedMode: "DELTA" with the reasoning.
- Quote with
mode=DELTA:
velora_get_quote
responseType: "delta" and the raw quote under result.raw, with agentHints spelling out the completion path.
- Complete the order outside the MCP server, exactly as the hints say:
- Pass the quote’s route verbatim to
POST /v2/delta/orders/build, which returns unsigned EIP-712 typed data. - Have the user’s wallet sign that typed data. The MCP server never signs.
- Submit the signed order via
POST /v2/delta/ordersand track it by order ID.
- Pass the quote’s route verbatim to
delta payload and its hmac exactly between steps. Any mutation invalidates the order.
Market swap with an unsigned transaction
For immediate on-chain settlement where the user pays gas.- Quote with
mode=MARKET:
velora_get_quote
responseType: "market" and a priceRoute inside result.raw.market.
- Build the unsigned transaction, passing
priceRouteverbatim:
velora_build_transaction
result.raw is the unsigned transaction (from, to, value, data, gas fields). The warnings array reminds you every time: review and sign externally with the user’s wallet.
- Sign and broadcast with the user’s wallet, then track the transaction hash. For an ERC-20 source token, check the allowance to the Augustus v6.2 router first; see Token approvals.
mode=ALL with fallback handling
Let Velora pick the best path, then branch on what came back.-
Quote with
mode: "ALL"(or omitmode; ALL is the default). The same arguments as above apply. - Branch on the response shape, never on the request:
velora_explain_quote
responseType: "delta"→ continue with the Delta build → sign → submit path.responseType: "market"→ continue withvelora_build_transaction.- A
fallbackReason({ errorType, details }) means Delta pricing was skipped and Velora fell back to Market. Surface it to the user if the intent required Delta-only properties such as MEV protection, then requote withmode=DELTAor adjust the trade.
Validate a plan before executing it
Run any multi-step plan through the validator before the first call. Here is a plan with two classic mistakes:velora_validate_agent_plan
networkmust bechainId(warning).- MEV protection requires
mode=DELTA, notMARKET(warning). - A signing step with a stored key is flagged critical — signing belongs to the user’s wallet, never to the agent or the server.
Ground your agent in the docs
Before generating integration code, pull canonical material instead of relying on training data:velora_search_docswith a behavior question, for example{ "query": "mode=ALL response shape" }.velora_get_docs_pagewith a result’s slug, for example{ "slug": "integrate/trading-modes" }, to load the full page as markdown.- For broad work, read the
velora://docs/llmsresource to map the docs, andvelora://docs/llms-fullwhen you want the entire documentation in context. The OpenAPI resources (velora://docs/openapi/delta-v2,velora://docs/openapi/market,velora://docs/openapi/rfq) keep generated request and response types honest.
Next steps
Five-call recipe
The same flows over raw HTTP, with failure handling per step.
Available tools
Full parameter reference for every tool used above.