Skip to main content

Endpoint

Path Parameters

non-7702:presign mode is not yet implemented. Only 7702 and non-7702:on-demand modes are currently functional.

Request Body by Mode

For EIP-7702 intents, simply trigger execution:
The solver executes the delegated calls using the stored authorization.

Response

Success Response (200)

Already Processed (202)

If the step is not in created status:

Execution Flow

7702 Mode

  1. Solver retrieves stored calls and authorization
  2. Broadcasts transaction with delegated execution
  3. Updates step status on confirmation

non-7702:on-demand Mode

When action: "execute" with a transaction hash:
  1. Verify Transaction: Check tx exists on-chain and succeeded
  2. Replay Prevention: Reject if hash already processed
  3. Update Balances: Credit user’s Spice balance from token transfers
  4. Execute Solver Transfers: Send tokens on destination chain(s)
  5. Auto-Advance: Automatically execute remaining steps (solver transfers)
When action: "register":
  1. Verify Transaction: Check tx exists and succeeded
  2. Store Reference: Save hash for tracking, no balance updates
  3. Status: Set to registered instead of success

Error Responses

400 Bad Request

404 Not Found

500 Internal Server Error

Example Requests

7702 Mode

non-7702:on-demand Mode

Notes

  • Steps must be executed in order (0, 1, 2, …)
  • For non-7702:on-demand, the user is responsible for sending the source chain transaction
  • After a successful execute action, remaining steps (solver transfers on destination chains) are auto-executed