The score, by dimension
- the same for all 7
- #5 of 7 · best 17.8
- the same for all 7
- the same for all 7
- the same for all 7
Tick: the best in this ranking · Methodology v2026.11.1
Keep3r Network
Onchain keeper marketplace
#5 of all 7 worldwide65
- Rank
- #5 of all 7 worldwidere-runs: scores 63–66 and ranks #4–#5
- Your cost
- Not priced on this basis
- Evidence
- High4 of 4 criteria sourced
- Licence
- No MiCA record on file
- Freshness
- Read September 2026checked · re-read due
Check availability for your country
Keep3r Network · docs.keep3r.network. Provider links appear once we know which country you are browsing from: ChainChoice links to providers only where it serves in full.
Commission: This provider pays ChainChoice nothing for this link. Disclosure
Crypto products are high risk. Check the provider is authorised where you live before you deposit.
The verdict
Keep3r Network is #5 of 7 published automation & keepers; it scores 9/10 on survives the vendor, the category best. Its widest gap is trigger surface and predicate locus: 2/10, where Reactive Network scores 8. Choose Reactive Network if trigger surface and predicate locus matter most.
Is Keep3r Network right for you?
Suits you if
- Whether the job survives the vendor: who else can turn the crank, and what end-of-life is published9/10, the category best
Look elsewhere if
- What can fire the call, against what target, and who can check the condition was true2/10 here; Reactive Network scores 8
- Whether a run that never happened is visible, or the job just goes quiet4/10 here; Reactive Network scores 7
- The lateness the vendor will put in writing, and the conditions under which it declines to execute4/10 here; DeFi Saver Automation 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 automation network shows where it lands for you.
What will Keep3r Network cost you?
Not priced on this basis
- Usage per month
- 10
How safe is Keep3r Network?
- Evidence: verified4 of 4 criteria rest on quoted, sourced receipts. Read September 2026.
- LicenceMiCA (EU): no register record on file here.
Entity: not verified. No hand-confirmed record on file ties Keep3r Network to the company that runs it, so this page cannot say which other products that company operates. Read the legal entity in its terms before you deposit. How we read the evidence
Open the evidenceIf it doesn’t fit, choose
Compare all 4- 3Reactive NetworkIf trigger surface and predicate locus matter most: 83 points above · stronger on trigger surface and predicate locus (8 against 2)68
- 4DeFi Saver AutomationIf published lateness bound matters most: 91 point above · stronger on published lateness bound (9 against 4)66
- 6Mimic ProtocolIf trigger surface and predicate locus matter most: 62 points below · stronger on trigger surface and predicate locus (6 against 2)63
Provider at a glance
- Category
- Automation & Keepers
- Entity
- Not verified
- Official website
- docs.keep3r.network
Independent rankingchecked How it works
Details
Scored 65 out of 100 under methodology 2026.11.1, from the evidence read in September 2026.
For your setup
Find out if Keep3r Network fits you
The rank above is the published one — the same for every visitor. Answer the category's questions and this section shows where Keep3r Network 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 automation networkNothing is inferred from clicks, popularity or commercial value.
Why this rank
Why Keep3r Network ranks #5
Each strength is read from evidence on a 0–10 ladder and weighted as the published methodology states. The 32 objective points these produce (15.8 here) sit inside the score; availability, friction, trust record and measured data add the rest. Best in this ranking on 1 of 4.
4 published criteria · Σ weight 100
CriterionWeightStrength · 0–10ScoreContrib.MedianBestRankEvidence
282+1.796.08#7/7
Primary
Provider page · read 2026-09-28309+8.644.09#1/7
Primary
Provider page · read 2026-09-28244+3.075.07#5/7
Primary
Provider page · read 2026-09-28184+2.306.09#7/7
Primary
Provider page · read 2026-09-28Hairline = best in this ranking · tick = its median · a missing bar is "not scored", never zero
Margin−1behind DeFi Saver Automation, #4 of all 7 worldwide, on the published score
RobustnessOne point from changingacross a one-point change to each of its 4 criterion scores, the re-run scores 63–66 and ranks #4–#5
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 Keep3r Network’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 can fire the call, against what target, and who can check the condition was true 2 → 3 on its ladder · passes DeFi Saver Automation+166#5 → #4
Whether the job survives the vendor: who else can turn the crank, and what end-of-life is published 9 → 10 on its ladder · passes DeFi Saver Automation+166#5 → #4
Whether a run that never happened is visible, or the job just goes quiet 4 → 5 on its ladder · passes DeFi Saver Automation+166#5 → #4
The lateness the vendor will put in writing, and the conditions under which it declines to execute 4 → 6 on its ladder · passes DeFi Saver Automation+267#5 → #4
What can fire the call, against what target, and who can check the condition was true 2 → 0 on its ladder · Mimic Protocol passes it−261#5 → #6
Whether the job survives the vendor: who else can turn the crank, and what end-of-life is published 9 → 7 on its ladder · Mimic Protocol passes it−261#5 → #6
Whether a run that never happened is visible, or the job just goes quiet 4 → 2 on its ladder · Mimic Protocol passes it−262#5 → #6
Smallest climb: what can fire the call, against what target, and who can check the condition was true 2 → 3 passes DeFi Saver Automation, #4.
Strengths
1 from the score dataWhere it leads
Best for readers who weight
- Whether the job survives the vendor: who else can turn the crank, and what end-of-life is published — 9/10, the category best
Tradeoffs
3 from the score dataWhere it trails
Not for readers who put first
- What can fire the call, against what target, and who can check the condition was true — 2/10 against a category best of 8/10
- Whether a run that never happened is visible, or the job just goes quiet — 4/10 against a category best of 7/10
- The lateness the vendor will put in writing, and the conditions under which it declines to execute — 4/10 against a category best of 9/10
Record watch-outs
- Four things a ranking must not smooth over, all re-verified onchain 2026-08-14. (1) The network is live but singular: 527 executions in 30 days, every one of them on a single job (YearnFactoryHarvestV1, 0xf4F748D45E03a70a9473394B28c3C7b5572DfA82), while the registry's jobs() getter reports 42 registered jobs on Ethereum. The five observed keepers are demonstrably willing to serve that one job; nothing establishes they would serve a new one, and the published decline condition — 'what transactions they deem profitable' — is exactly why they might not. A buyer registering a fresh job is buying a marketplace, not a service, and must make it worth someone's while. (2) Two signatures can move the parameters your reward depends on. The docs publish no governance identity anywhere across all 41 pages ('multisig' and 'Safe' return zero hits), but the registry's own governance() getter returns 0x0d5dc686d0a2abbfdafdfb4d0533e886517d4e83, which is a Gnosis Safe proxy (VERSION() decodes to '1.4.1') with six owners and getThreshold() = 2. Per https://docs.keep3r.network/roles/governance that role can set the fee, the bond time, the approved liquidities, force-mint credits and — materially — swap the Keep3rHelper address, which is where minBoost/maxBoost live. (3) The self-rescue path is structurally sound but operationally decayed: the CLI the docs call 'all the necessary code required to run your own keeper' was last pushed 2022-01-03 and still defaults to the V1 contract; the boilerplate the onboarding rules require (defi-wonderland/keep3r-cli-job-boilerplate) is HTTP 404; the keeper script for the only live job (defi-wonderland/yearn-keeper-scripts) is HTTP 404; the job registry the docs send you to is archived and self-declared deprecated. Self-rescue means writing your own executor, not installing theirs. (4) Chain coverage is real as deployment and hollow as activity. Ethereum is confirmed by 527 events. Optimism's Keep3r V2 at 0x745a50320B6eB8FF281f1664Fc6713991661B129 holds 24,374 bytes of code and its jobs() getter returns 3 registered jobs, but a complete 30-day scan (blocks 154,262,412–155,558,412, 2026-07-15T13:53:21Z to 2026-08-14T13:53:21Z) returned ZERO registry log entries of any kind. Polygon's V2 at the same address holds 24,454 bytes and 2 registered jobs; only the most recent 89,100 blocks (91,918,007–92,007,107, roughly 2.2 days) were readable — zero registry events there, and every public endpoint tried had pruned the older history, so Polygon beyond that is INCONCLUSIVE, not negative. Sepolia and OP Sepolia are also configured in the frontend and are testnets, so they are excluded.
Competitive position
How Keep3r Network places on each criterion
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.
Against the leader
80 vs 65 · gap 15.0Why TukTuk (Helium) ranks above Keep3r Network
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 15.0 to within rounding.
DimensionThisTukTuk (Helium)Gap share
Availability · 23% weight · constant here14.014.0same
Published criteria · 35% weight11.917.8−15.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 criterionThisTukTuk (Helium)Points
What can fire the call, against what target, and who can check the condition was true · w2828−5.38, worse
Whether the job survives the vendor: who else can turn the crank, and what end-of-life is published · w3098+0.96, better
Whether a run that never happened is visible, or the job just goes quiet · w2447−2.30, worse
The lateness the vendor will put in writing, and the conditions under which it declines to execute · w1846−1.15, worse
Net6580−15.0
Your scenario
Keep3r Network 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 September 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 · USDTypical costNot statedFewer than 5 priced rows: no typical cost is named · 0 of 7 rows priced
Lowest fee, priced rowsNone 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 typical, not counted as free.
Evidence
Evidence read 28 September 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 #4 to #5 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 10 November 2026; this category's reading is older. The scores stand as read on 28 September 2026.
CriterionSourceTypeReadFreshnessStatusReceipt
What can fire the call, against what target, and who can check the condition was truestrength 2 · weight 28Report an errorProvider's own page28 September 2026…
Verified
The published strength matches the evidence cell and a source page is on file.Whether the job survives the vendor: who else can turn the crank, and what end-of-life is publishedstrength 9 · weight 30Report an errorProvider's own page28 September 2026…
Verified
The published strength matches the evidence cell and a source page is on file.Whether a run that never happened is visible, or the job just goes quietstrength 4 · weight 24Report an errorProvider's own page28 September 2026…
Verified
The published strength matches the evidence cell and a source page is on file.The lateness the vendor will put in writing, and the conditions under which it declines to executestrength 4 · weight 18Report an errorProvider's own page28 September 2026…
Verified
The published strength matches the evidence cell and a source page is on file.How you can lose money here, and what the ranking scores
- Control failure (Keep3r Network 2/10): a key or vote changes the rules, freezes or mints.Scored by What can fire the call, against what target, and who can check the condition was true · 28%
- Liveness failure (Keep3r Network 4/10): the operator stops, censors you or loses data.Scored by Whether a run that never happened is visible, or the job just goes quiet · 24%
- Execution failure (Keep3r Network 4/10): you get a worse price, later, or nothing.Scored by The lateness the vendor will put in writing, and the conditions under which it declines to execute · 18%
- Exit failure (Keep3r Network 9/10): you cannot get out at par, on time, or with what is yours.Scored by Whether the job survives the vendor: who else can turn the crank, and what end-of-life is published · 30%
Every failure family that applies to this category is scored.
Facts
facts, not scoresWhat the record publishes
- Pricing
- No pricing page exists: https://
docs .keep3r .network /pricing returned HTTP 404 on 28 September 2026. What the docs say a job pays is on https:// docs .keep3r .network /core /jobs, fetched 28 September 2026 and unchanged: "The above will make sure the caller is a registered keeper as well as reward them with an amount of KP3R equal to their gas spent + premium. Make sure to have enough credits assigned in the Keep3r system for the relevant job." The premium is never given a number on any docs page. Chain read, not a page price: the helper the live V2 registry points at, keep3rHelper() = 0xeDDe080E28Eb53532bD1804de51BD9Cd5cADF0d4, returned minBoost() = 11000 and maxBoost() = 12000 at Ethereum block 26,077,597 on 28 September 2026. Against BOOST_BASE 10000 that is a keeper reward of 1.10x to 1.20x of gas spent, paid in KP3R and scaling with the keeper's bond. Governance can set a liquidity fee ("function setFee(uint256 _fee) external;", https:// docs .keep3r .network /roles /governance). August read fee() as 30 against a base of 10,000; that value was not re-read on 28 September 2026. Recorded as disclosure only; price ranks in no criterion on this page.Keep3r Network — official pricing page ↗ · 28 September 2026 - Prices published in
- USDKeep3r Network — official pricing page ↗ · 28 September 2026
- Licences held
- Not published
- Compliance level
- partial
- Regulatory note
- Not published
- Supported chains
- ethereum, optimism, polygon
- Markets served
- global
- Primary markets
- Not published
- Restricted markets
- Not published
- Operating limits
- Not published
- Availability note
- Re-verified 2026-08-14: no geographic restriction is published anywhere on the product. The strings 'jurisdic', 'restrict', 'prohibit', 'OFAC', 'sanction', 'United States', 'KYC' and 'resident' each return zero hits across all 41 documentation pages enumerated at https://
docs .keep3r .network /llms .txt, and no terms, legal or privacy page exists to carry one — https:// keep3r .network /terms, https:// keep3r .network /legal, https:// keep3r .network /privacy and https:// docs .keep3r .network /terms all return HTTP 404. Access is by direct contract call on Ethereum mainnet (addJob and bond are both permissionless), with no account, no signup and no vendor-side gate, so availability is a function of RPC access rather than of the vendor. Practical caveats that are not geography: participation requires KP3R or an approved kLP liquidity position to fund a job, and the sole hosted UI at keep3r.network carries the footer 'This project is in beta. Use at your own risk.'
No confirmed legal entity is on file for this record. Nothing is inferred from the brand name.
If something goes wrong with Keep3r Network: 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
- 28 September 2026Current verified snapshot · methodology 2026.11.1Score 65, #5 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.11.1, the same published run every visitor sees · receipt automation_keepers:keep3r:2026.11.1:89ccfa60e9be
Are you Keep3r Network? 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.