relay
Native relay API (assign, relay, intent status, per-intent SSE).
Assign one relayer in the sender's shard and issue a lease. Nothing is reserved yet.
Call it just before the user signs: the relayer address goes into the transaction, so the user signs
Submit one user-signed Relayed-V3 transaction for co-signing and broadcast.
The idempotency key is `(tx.sender, tx.nonce)` plus the SHA-256 of the canonical signing bytes.
Intent status by intent id (`<sender>:<nonce>`) or by transaction hash.
Resolver in front of `GET /v1/intents/{sender}/{nonce}` (authoritative) and `GET /v1/tx/{hash}`. Same response schema.
Server-sent events for one intent until it is terminal and final, or 120 000 ms elapsed.
Event name `intent`, data = `Intent`. `id:` is the per-intent sequence. The server closes the
Authoritative, cross-host intent status keyed by (sender, nonce).
Authoritative, cross-host intent status keyed by (sender, nonce).
Convenience lookup by transaction hash. Terminal state is still decided by (sender, nonce) and chain facts.
Convenience lookup by transaction hash. Terminal state is still decided by (sender, nonce) and chain facts.
RU weight and price of a transaction (signed or unsigned). No reservation, no signer call.
RU weight and price of a transaction (signed or unsigned). No reservation, no signer call.
Run the relay checks (static checks, signatures, account and nonce, simulation) without a lease, a reservation or a co-signature.
Backs the MCP tool `validate_transaction`. Rate limit 2/s per IP because it may trigger a gateway simulation.