Provider at a glance
- Category
- Relayers
- Entity
- Not verified
- Official website
- docs.sequence.xyz
Independent rankingchecked How it works
Details
Scored 73 out of 100 under methodology 2026.10.18, from the evidence read in August 2026.
Sequence Transactions API (Relayer)
Hosted relayer for Sequence wallets
Relayers
#4 Overall
Ranked #4 of 7 relayers in the published ranking
73
ChainChoice Score
The ChainChoice Score, shown against 100: published scores run from 41 to 99.- High evidence confidence
Is Sequence Transactions API (Relayer) right for you?
Right for you if these matter most
- What the relayer is authorised to do, and whether you can keep the address9/10; the category best is 10
- Exactly-once execution and stuck-queue recovery6/10; the category best is 7
Look elsewhere if these come first
- What a stolen API credential can do before anyone notices6/10 here; the category best is 10
- Where the gas float sits and how you get it back7/10 here; OpenZeppelin Relayer scores 9
Not yet tested for your country. Markets it lists: Global.
to test where you can use it.
The rank above is the published one, the same for every reader. Find my best relayer service shows where it lands for you.
What will Sequence Transactions API (Relayer) cost you?
Not priced on this basis
- Usage per month
- 10
How safe is Sequence Transactions API (Relayer)?
- Evidence: verified4 of 4 criteria rest on quoted, sourced receipts. Read August 2026.
- LicenceMiCA (EU): no register record on file here.
Alternatives to Sequence Transactions API (Relayer)
Compare all 4- 3OpenZeppelin RelayerLevel on score · stronger on gas float custody (9 against 7)73
- 5Circle Gas Station3 points below · stronger on exactly once execution (7 against 6)70
- 6Openfort backend wallets4 points below · weaker on exactly once execution (4 against 6)69
For your setup
Find out if Sequence Transactions API (Relayer) fits you
The rank above is the published one — the same for every visitor. Answer the category's questions and this section shows where Sequence Transactions API (Relayer) lands for you, which criteria your answers weight up, and which stated needs the record does or does not meet. The published rank stays beside it.
- A few questions
- No account required
- Ranking-blind: no commercial input
- Personalised in under 60 seconds
Find my best relayer serviceNothing is inferred from clicks, popularity or commercial value.
Why this rank
Why Sequence Transactions API (Relayer) ranks #4
Each strength is read from evidence on a 0–10 ladder and weighted as the published methodology states. The 32 objective points these produce (22.9 here) sit inside the score; availability, friction, trust record and measured data add the rest.
4 published criteria · Σ weight 100
CriterionWeightStrength · 0–10ScoreContrib.MedianBestRankEvidence
329+9.229.010#2/7Loading evidence…
266+4.996.07#4/7Loading evidence…
226+4.226.010#3/7Loading evidence…
207+4.487.09#4/7Loading evidence…
Hairline = best in this ranking · tick = its median · a missing bar is "not scored", never zero
MarginLevelbehind OpenZeppelin Relayer, #3
RobustnessOne point from changingacross a one-point change to each of its 4 criterion scores, the re-run scores 71–75 and ranks #3–#4
Evidence4 of 4 scored4 quoted, 4 with a source link
What would move the rank
Each line is the ranking run again with one of Sequence Transactions API (Relayer)’s criterion scores changed and every other value held: the smallest whole-point change on that criterion that moves its rank, and where the re-run puts it. Up to 4 climbs and 3 falls are listed, smallest change first. Nothing here is a forecast.
What the relayer is authorised to do, and whether you can keep the address 9 → 10 on its ladder · passes OpenZeppelin Relayer+175#4 → #3
Exactly-once execution and stuck-queue recovery 6 → 7 on its ladder · passes OpenZeppelin Relayer+174#4 → #3
What a stolen API credential can do before anyone notices 6 → 7 on its ladder · passes OpenZeppelin Relayer+174#4 → #3
Where the gas float sits and how you get it back 7 → 8 on its ladder · passes OpenZeppelin Relayer+174#4 → #3
What the relayer is authorised to do, and whether you can keep the address 9 → 7 on its ladder · Circle Gas Station passes it−269#4 → #6
Exactly-once execution and stuck-queue recovery 6 → 4 on its ladder · Circle Gas Station passes it−269#4 → #6
What a stolen API credential can do before anyone notices 6 → 3 on its ladder · Circle Gas Station passes it−369#4 → #6
Smallest climb: what the relayer is authorised to do, and whether you can keep the address 9 → 10 passes OpenZeppelin Relayer, #3.
Strengths
2 from the score dataWhere it leads
Best for readers who weight
- What the relayer is authorised to do, and whether you can keep the address — 9/10, category best 10/10
- Exactly-once execution and stuck-queue recovery — 6/10, category best 7/10
Tradeoffs
2 from the score dataWhere it trails
Not for readers who put first
- What a stolen API credential can do before anyone notices — 6/10 against a category best of 10/10
- Where the gas float sits and how you get it back — 7/10 against a category best of 9/10
Record watch-outs
- Five of the chains this relayer publicly advertises do not exist as endpoints: polygon-zkevm, blast, sei, xai and incentiv relayer hosts appear in Sequence's own OpenAPI servers block but return NXDOMAIN (checked 2026-08-11), as do laos and rootnet — so verify your chain answers GetChainID before you build on it. Beyond that, the backend address you permission is not an EOA but a Sequence smart-contract wallet from Sequence's published factory (0xFaA5c0b14d1bED5C888Ca655B9a8A5911F78eF4A) — which is why the address survives key rotation, but also means msg.sender in your contracts is a contract (the vendor says so outright), the wallet must be deployed on every chain you relay on, and there is no cancel or nonce-reset endpoint in either published API spec, so the only way to clear a jammed queue is to abandon that nonce space.
Competitive position
Where Sequence Transactions API (Relayer) leads and where it trails
Rank on every objective dimension among the rows scored on it. A criterion in the top third of its pool is listed as a lead, the bottom third as a trail; the middle is neither. Popularity, size and commercial terms are not dimensions.
Availability#1 / 714.0 of 20 · constant here
Published criteria#4 / 717.2 of 30 · best 20.4
Friction#1 / 72.7 of 10 · constant here
Trust record#1 / 73.2 of 8 · constant here
Measured data#1 / 78.3 of 18 · constant here
Where Sequence Transactions API (Relayer) leads
- What the relayer is authorised to do, and whether you can keep the address#2 / 7
- What a stolen API credential can do before anyone notices#3 / 7
Where it trailsNo criterion in the bottom third of its pool.
Closest alternatives
The 3 nearest rows by score
Nearest by published score in either direction. Each card states the criteria on which the two rows differ and the cost difference under the same scenario inputs; the compare arithmetic below shows why the higher one ranks higher.
OpenZeppelin Relayer#3 of 7 · score 73 · same score
Sequence Transactions API (Relayer) leads on
- What a stolen API credential can do before anyone notices6 vs 3
OpenZeppelin Relayer leads on
- What the relayer is authorised to do, and whether you can keep the address10 vs 9
- Where the gas float sits and how you get it back9 vs 7
Largest single reason OpenZeppelin Relayer is ahead: published criteria (+0.3 display points).Scenario cost: OpenZeppelin Relayer has no verified pricing for this scenario.
Circle Gas Station#5 of 7 · score 70 · 3.0 points behind
Sequence Transactions API (Relayer) leads on
- What the relayer is authorised to do, and whether you can keep the address9 vs 6
Circle Gas Station leads on
- Exactly-once execution and stuck-queue recovery7 vs 6
- Where the gas float sits and how you get it back8 vs 7
Largest single reason Sequence Transactions API (Relayer) is ahead: published criteria (+3.1 display points).Scenario cost: Circle Gas Station has no verified pricing for this scenario.
Openfort backend wallets#6 of 7 · score 69 · 4.0 points behind
Sequence Transactions API (Relayer) leads on
- Exactly-once execution and stuck-queue recovery6 vs 4
Openfort backend wallets leads onNo scored criterion
Largest single reason Sequence Transactions API (Relayer) is ahead: published criteria (+3.4 display points).Scenario cost: Openfort backend wallets has no verified pricing for this scenario.
Against the leader
81 vs 73 · gap 8.0Why Coinbase CDP Server Wallets (API-key wallets) ranks above Sequence Transactions API (Relayer)
The compare workspace's arithmetic applied to these two rows. Each dimension's share of the gap is its weight × the difference, on the displayed scale — it reproduces the displayed gap of 8.0 to within rounding.
DimensionThisCoinbase CDP Server Wallets (API-key wallets)Gap share
Availability · 23% weight · constant here14.014.0same
Published criteria · 35% weight17.220.4−8.3, worse
Friction · 12% weight · constant here2.72.7same
Trust record · 9% weight · constant here3.23.2same
Measured data · 21% weight · constant here8.38.3same
Published criterionThisCoinbase CDP Server Wallets (API-key wallets)Points
Exactly-once execution and stuck-queue recovery · w2667−0.83, worse
What a stolen API credential can do before anyone notices · w22610−2.82, worse
Where the gas float sits and how you get it back · w2078−0.64, worse
Net7381−8.0
Your scenario
Sequence Transactions API (Relayer) is not priced for this scenario
Metered usage beyond whatever the plan includes, for a year. Excludes egress, support tiers and enterprise minimums. Change an input and every figure recomputes from the published rate; the published rank does not move.
your cost/yr · default scenario — set your own
Usage per month · your input10
Rate read from the provider’s published pricing ↗ on 28 October 2026.
your cost/yrCost is stated as your cost/yr in USD; it is never a yield, never annualised, and it does not enter the score.
Not priced on this basis
Under the default inputs · USDCategory medianNot priced0 of 7 rows priced
Cheapest pricedNone pricedDifference not stated · availability not applied — set your country to filter
7 of 7 rows in this ranking have no verified rate for this scenario and are absent from the median, not counted as free.
Evidence
Evidence read 11 August 2026
One row per published criterion: the page each strength was read from, its source type by domain, the reading date and whether the file and the published table agree. Open a row for the quote and the receipt.
4 of 4 cells scored
Score evidenceVerified4 of 4 criteria reconstruct from receipts
4 of 4 criteria reconstruct from a quoted, sourced receipt equal to the published strength.Public receiptsReading…4 quoted with a source URL
The receipt file has not been read yet.Evidence confidenceHighcoverage and corroboration, never freshness
4/4 criteria scored, with 4 dated sources quoted.RobustnessOne point from changingrank #3 to #4 across one-point re-runs
Whether the position holds when one criterion score is changed by one point and the ranking is run again. It is always a re-run of the ranking, never an estimate.The newest evidence read on the platform is 3 November 2026; this category's reading is older. The scores stand as read on 11 August 2026.
Reading the evidence ledger…
CriterionSourceTypeReadFreshnessStatusReceipt
What the relayer is authorised to do, and whether you can keep the addressstrength 9 · weight 32Report an error—11 August 2026*
Unknown
No reading date is recorded for this cell or its category.No receipt
A strength is published but no quote or source page is on file for it.Exactly-once execution and stuck-queue recoverystrength 6 · weight 26Report an error—11 August 2026*
Unknown
No reading date is recorded for this cell or its category.No receipt
A strength is published but no quote or source page is on file for it.What a stolen API credential can do before anyone noticesstrength 6 · weight 22Report an error—11 August 2026*
Unknown
No reading date is recorded for this cell or its category.No receipt
A strength is published but no quote or source page is on file for it.Where the gas float sits and how you get it backstrength 7 · weight 20Report an error—11 August 2026*
Unknown
No reading date is recorded for this cell or its category.No receipt
A strength is published but no quote or source page is on file for it.How you can lose money here, and what the ranking scores
- Liveness failure (Sequence Transactions API (Relayer) 6/10): the operator stops, censors you or loses data.Scored by Exactly-once execution and stuck-queue recovery · 26%
- Custody failure: whoever holds the assets loses or withholds them.Scored by What the relayer is authorised to do, and whether you can keep the address · 32% (Sequence Transactions API (Relayer) 9/10)Scored by What a stolen API credential can do before anyone notices · 22% (Sequence Transactions API (Relayer) 6/10)Scored by Where the gas float sits and how you get it back · 20% (Sequence Transactions API (Relayer) 7/10)
Not assessed by this ranking: Exit failure. A high place says nothing about these; the Methodology tab says what each means.
Facts
facts, not scoresWhat the record publishes
- Pricing
- No rate for relayed transactions or gas is published on any page that could be fetched. Re-checked 2026-09-28: https://
sequence .xyz /pricing redirects (curl -L) to https:// sequence .xyz /, whose HTML contains zero occurrences of "pricing"; https:// docs .sequence .xyz /support /builder /pricing and https:// docs .sequence .xyz /solutions /builder /plans .md both return HTTP 404. The only dollar figure on the gas-sponsorship page (https:// docs .sequence .xyz /solutions /builder /gas-sponsorship, fetched 28 September 2026) is the low-balance notice: "We will automatically notify you if your balance falls below $5 and you have sponsored contracts." Two cost-shaped mechanics are published, neither a rate. (1) Gas-tank funding, same page: "Now, we are going to add a payment method via a credit card in order to fund the sponsorship." / "You can either do a one-time top off or an automated top-up based on preferred ranges so you can precisely configure how much you'd like to willing to subsidize for your users each month." (sic). (2) https:// docs .sequence .xyz /solutions /builder /project-settings (fetched 28 September 2026) publishes a Billing section listing "Current subscription plan", "Monthly credits issued", "Credits used in the current period", "Remaining credits" and "Overage settings status", plus "Then enter the maximum overage amount that you would like to set." — a plan-and-credits model with a buyer-settable ceiling but no figures; the plans dashboard sits behind a Builder login. This category publishes no cost ranking by design: per-transaction price and gas markup are scored on account_abstraction_infra, and no figure from there is imported here.Sequence Transactions API (Relayer) — official pricing page ↗ · 28 October 2026 - Prices published in
- USDSequence Transactions API (Relayer) — official pricing page ↗ · 28 October 2026
- Licences held
- Not published
- Compliance level
- partial
- Regulatory note
- Not published
- Supported chains
- Ethereum, Polygon, Arbitrum One, Arbitrum Nova, Optimism, Base, BNB Smart Chain, Avalanche, Gnosis, ApeChain, B3, Etherlink, Homeverse, Immutable zkEVM, Katana, Monad, Moonbeam, SKALE Nebula, Somnia, Soneium, Telos
- Markets served
- global
- Primary markets
- Not published
- Restricted markets
- Not published
- Operating limits
- Not published
- Availability note
- Not published
No confirmed legal entity is on file for this record. Nothing is inferred from the brand name.
If something goes wrong with Sequence Transactions API (Relayer): where to complain, and where to report a scam
Loading the routes for your country.
How this page is reviewed
Reviewed means this product in this category was read against its sources on or after that date; every ranked category is re-read at least every 45 days. Models research, extract and parse. A deterministic engine ranks. Every quote passes an adversarial refute pass.
Accountable for this review: Mathias Siemonsmeier, Founder.
How we review · Review calendar · Corrections log · How we make money
History
What the record carries
Changes to published ranks are recorded in a ledger; every step and its cause is listed on the rank-history page. The entries below begin with the current verified snapshot, then the methodology versions whose changes applied to this category, newest first.
9 methodology entries
- 11 August 2026Current verified snapshot · methodology 2026.10.18Score 73, #4 of 7. 4 of 4 criteria scored. History starts here; earlier values are not interpolated.
- 10 October 2026
2026.10.8When nothing serves your country, the list shown for reference is the published ranking · platform-wide- fixed The reference list shown when nothing serves your country is the published order with the published scores, and a build check now fails any such list out of that order or with a score the ranking does not publish.
- fixed The explorer prints an overall rank only for a row the published ranking holds; a country entrant such as Coinbase Commerce for US merchants shows no overall rank.
- changed Published orders do not move. Country results change only where nothing serves the country: in India bill pay keeps Bitcoin Well first and now shows Strike second, as published; 35 such runs across all categories and countries now match the published list exactly.
- 10 October 2026
2026.10.6A criterion you require re-scores the rows that meet it · platform-wide- changed The explorer sends each criterion you require, at any band, as fit_required with your other answers; region, licence, chain and fact filters stay filters. On /best, a required criterion joins For you as a marked preference does, which needs your country; Overall stays the published ranking, filtered.
- added Every published criterion has a golden case as the explorer sends it (require:<criterion>), so the order a requirement gives is replayed and gated as the published order is, and a change to it needs an entry here.
- 16 September 2026
2026.09.15Dimension scores carry tenths, and eleven more categories are re-read from primary sources · platform-wide- changed Dimension scores resolve to tenths of a point (O-04b), and weightedTotal is rounded to six decimal places before the order is read. 518 published scores move across 107 categories that were not re-read; none of them moves by more than 4 points, and most move by 1.
- fixed 66 published scores change in the eleven re-read categories, against a verbatim source each. The largest moves are Reflexer RAI (−16), Beefy and Unrekt (−11), Aztec (−10) and Golem (+9) — all of them rows whose sources had moved since their last read.
- changed Published order moves in 38 of 119 categories and three #1s change: smart_contract_audits (Zellic → Certora) and travel_rule_compliance (Sumsub Travel Rule → CodeVASP) on the finer resolution, kyc_compliance (Veriff → Sumsub) on the re-read.
- added availabilitySource (O-04g): for a reader who states a country, a row whose availability in that country rests on a region tag its record gives no source for sorts below every sourced row. It is inert in every order published here, which states no country.
Methodology 2026.10.18, the same published run every visitor sees · receipt relayers:sequence_transactions_api:2026.10.18:fbde30e17776
Are you Sequence Transactions API (Relayer)? Reply to this verdict, or send evidence, ask for a correction or claim the listing. Every message gets a public ticket number; none of it changes a rank unless a public page or a signed statement supports it.