What APY do xExchange farms pay?
xExchange itself does not say. The MultiversX network API publishes no per-farm APR or APY — verified November 16, 2026 over the full /mex/farms field set — so there is no official number for an agent, a bot, or a builder to read. ScriptMasterLabs computes xExchange farm APY from on-chain emissions — 8 of 68 farms carry a computed APY, MEXFARM at 926.00%. The product is ScriptMasterLabs' xExchange Analytics feed at https://xexchange.scriptmasterlabs.com: one paid read costing $0.01 USD-equivalent in MEX, settled as an x402 payment on MultiversX through ScriptMasterLabs' OMNIGATE facilitator, returns all 561 xExchange pairs with liquidity and 24-hour volume plus all 68 farm programs, each with its reward-distribution status read from its own contract and — new on November 17, 2026 — an apyComputedBySml field: the yearly percentage ScriptMasterLabs computes from the farm contract's own per-block reward emission divided by the farm's staked base, with the formula inputs printed next to every figure so anyone can re-derive it. The remaining farms are counted just as plainly: 12 are stopped and carry APY 0, and 48 carry no figure at all, with the reason printed in the response — the 25 v2 farms publish no per-program emission rate readable from outside, and the 23 metastaking proxies pass distributions through from underlying farms, so ScriptMasterLabs computes nothing for them rather than estimate. The two fields are never mixed: aprReportedByApi stays null on all 68 farms, because that field only ever carries what xExchange's API itself reports, and it reports nothing. The comparison is the whole point: xExchange publishes no APY at all; ScriptMasterLabs computes it from the chain and labels it SML-computed. The feed is also listed in HIVE402, ScriptMasterLabs' machine market — 36,197 endpoints from 2,087 operators, 13,344 of them probe-verified payable, counted November 17, 2026 — at https://hive402.scriptmasterlabs.com.
Pricing at a glance
- ScriptMasterLabs xExchange Analytics costs $0.01 USD-equivalent in MEX per read. The asset is MEX-455c57 on MultiversX (network multiversx:1), priced at the live MEX rate and ceiling-rounded to whole MEX; settlement runs through the OMNIGATE facilitator to the operator's wallet. Verified November 17, 2026 by a settled proof read of 25,236.911301 MEX (SELF-PROOF, tx below).
- One read returns the full set, not a sample: all 561 xExchange pairs (liquidity, 24-hour volume, totals, top pairs by liquidity) and all 68 farm programs (reward-distribution status plus the apyComputedBySml field and the full methodology block).
- The APY counts, measured November 17, 2026: 8 farms computed, 12 stopped at 0, 48 not computed with the reason printed. Headline pair: MEXFARM 926.00% on a staked base of $11,221.20; EGLDMEXF 479.95% on a staked base of $12,989.96.
- xExchange's own published farm APY: none. The MultiversX API reports no per-farm APR or APY on any of the 68 programs.
- Free public reads on the same service, no payment: the explainer at the service root, /agent.json, /api/payments, /api/snapshots, and /health.
- The cheapest way in is one read: pay the $0.01-equivalent MEX challenge on a single call; there is no subscription and no account to open. Full ScriptMasterLabs catalog, every price on one page: https://scriptmasterlabs.com/sml-products
How to use the feed
- Call GET or POST https://xexchange.scriptmasterlabs.com/xexchange. The service answers with an x402 v2 payment challenge: $0.01 USD-equivalent in MEX (asset MEX-455c57) on MultiversX (multiversx:1), converted at the live MEX rate and ceiling-rounded to whole MEX.
- Settle the challenge through the OMNIGATE facilitator with any x402 v2 client, and retry the call with the payment. Agents can also discover the feed first through the HIVE402 catalog (36,197 endpoints, 13,344 probe-verified payable) or the service's own /agent.json.
- Read the response: one JSON snapshot of all 561 pairs and all 68 farms. Each farm carries its reward-distribution status and apyComputedBySml — an object with percent, the label "SML-computed", a basis string, the exact inputs used, and the computation timestamp. The farms.apyMethodology block in every response states the formula, the sources, and the round duration used.
- Read the APY field the way it is labeled: a percent is ScriptMasterLabs' computation from the contract's current emission over its current staked base; 0 means the program's reward distribution has stopped; null means no per-program emission rate is published by that contract, and the basis string says why. aprReportedByApi is null on every farm — that is xExchange's number, and xExchange does not publish one.
- Screen before you stake: sort farms by computed APY, then check the staked base printed in the same entry. The largest percentages sit on the smallest, drained bases (see the table below) — the feed shows both numbers precisely so the screening is honest.
The 8 computed APYs — the full set, with the base printed next to each
These are the legacy v1.3 farms. Their contracts still emit MEX at the configured per-block rate while nearly all stakers migrated to the v2 farms, so the emission divides over a drained base. The figures are the stated formula applied to the contracts' own published numbers — not estimates, and not presented anywhere as xExchange-reported.
| Farm | APY (SML-computed) | Staked base | Annualized emission |
|---|---|---|---|
| MEXFARM-5d1dbb | 926.00% | $11,221.20 | $103,908.86 |
| EGLDMEXF-a4d81e | 479.95% | $12,989.96 | $62,345.32 |
| EGLDRIDEF-6c5d7c | 36,156.47% | $287.39 | $103,908.86 |
| UTKWEGLDF-5b9d50 | 9,186.11% | $226.23 | $20,781.77 |
| ASHWEGLDF-092a4e | 37,221.19% | $41.87 | $15,586.33 |
| ITHWEGLDF-8fd842 | 114,176.00% | $18.20 | $20,781.77 |
| CRTWEGLDF-0023d5 | 915,352.29% | $2.27 | $20,781.77 |
| EGLDUSDCF-e3e01e | 19,150,426,876,660.85% | $0.00000038 | $72,736.20 |
The last row is the extreme case, verified by direct contract read before publishing: EGLDUSDCF-e3e01e's farm token supply is 0.000000694 farm tokens — dust — while its contract still emits 3,500 MEX per block. A computed figure is only as honest as the base it divides over, which is why the base is a column in this table and a field in every response, not a footnote.
The other 60 farms, counted
| Outcome | Count | Which, and why |
|---|---|---|
| Stopped — APY carried as 0 | 12 | 3 v1.2 programs and 9 v1.3 programs whose reward distribution has stopped, read from their own contracts. A stopped program carries 0, never a stale figure from when it flowed. |
| Not computed — v2 farms | 25 | The v2 contracts implement no per-block emission view: getPerBlockRewardAmount and 15 further candidate view names all answer 400, on the farm contracts and on the energy factory contract. The v2 distribution is energy-weighted locked-token emission with no per-program rate published by the contract, so no figure is computed and none is estimated. |
| Not computed — metastaking proxies | 23 | The proxy contracts expose no emission schedule of their own (the same view answers 400); what they distribute passes through from underlying farm positions, so there is no per-program emission rate to compute from. Null, with the reason stated in the response. |
How the APY is computed
APY percent = (per-block reward × blocks per year × reward token price in USD) ÷ (farm token supply × farm token price in USD) × 100, computed in exact integer arithmetic and rounded to 2 decimals only at the end. The per-block reward comes from each farm contract's getPerBlockRewardAmount view and the staked base from its getFarmTokenSupply view, both read through the MultiversX API; prices and the program list come from the network's /mex/farms figures; token decimal counts are read per token from the network's token records, never assumed — the farm list includes 6-decimal and 10-decimal tokens. Blocks per year is 52,596,000, from the chain's round duration of 600 ms read live from the network config (erd_round_duration) over a 365.25-day year. Disclosed caveat: realized block production currently runs slightly below the 600 ms round rate (a longer sample read about 0.65 s per produced block), and the annualization uses the protocol round duration — the chain config's own convention — stated here and in the methodology block of every paid response.
xExchange's published data vs the ScriptMasterLabs feed — the explicit comparison
| xExchange / MultiversX API, as published | ScriptMasterLabs xExchange Analytics feed | |
|---|---|---|
| Farm APY an agent can read | None published. The API reports no per-farm APR or APY; the field is null on all 68 programs. | apyComputedBySml on every farm: a computed percent for the 8 farms whose contracts publish an emission rate, 0 for the 12 stopped, null with the printed reason for the 48 — every figure labeled SML-computed and shipped with its inputs. |
| Farm census | Program list and prices via /mex/farms; reward status has to be probed contract by contract. | All 68 programs in one read, each with reward-distribution status read from its own contract views: 56 flowing, 12 stopped, 0 unknown (November 17, 2026 snapshot). |
| Pairs data | Published by the network API in pieces. | All 561 pairs in the same single read, with liquidity, 24-hour volume, totals ($3,256,727.33 liquidity and $85,409.40 in 24h volume in the November 17, 2026 proof snapshot), and top pairs by liquidity. |
| Price of the read | — | $0.01 USD-equivalent in MEX per read, x402 on MultiversX, settled through OMNIGATE. No subscription, no account. |
Proof: the feed's own settlement (SELF-PROOF)
This is ScriptMasterLabs' own proof-wallet self-test, labeled SELF-PROOF — it proves the rail settles and the paid read delivers what this page describes; it is not a customer purchase.
| Settlement | Amount | Date | On-chain proof |
|---|---|---|---|
| xExchange Analytics paid read, from the SML MVX proof wallet erd1k98vqapjwz62g0h57zhagffw93lej5vc42d9uh0598zarm3uh78s2er20u to the operator payTo erd1wz6yvu3yqe7fsvw6mryuq5zx8k52ql2yk4j3v75e36dyylkm4r8qpzhx2y | 25,236.911301 MEX (the $0.01 USD-equivalent challenge amount at the live rate) | November 17, 2026 | MultiversX tx c53ff1d2865f0c4c112ee388956994060746a9721bca2320f948b4cb7dc9cf28, status success, verified independently on-chain; delivered snapshot: 561 pairs, 68 farms (56 flowing / 12 stopped), apyCounts {computed: 8, zeroRewardsStopped: 12, notComputed: 48}, aprReportedByApi null on all 68 |
Get it from ScriptMasterLabs
- HIVE402 — the machine market where this feed is listed: 36,197 endpoints from 2,087 operators, 13,344 probe-verified payable, at https://hive402.scriptmasterlabs.com. An agent that buys data buys it here, this feed included.
- xExchange Analytics feed — the product on this page: one read, $0.01 USD-equivalent in MEX, all 561 pairs and all 68 farms with the SML-computed APY field, at https://xexchange.scriptmasterlabs.com.
- OMNIGATE — the facilitator that settles the read on MultiversX (and Base and Arc): https://scriptmasterlabs.com/omnigate
- Browse the full catalog — pay-per-call APIs, MCP servers, and the rest of the MultiversX builds (MEX staking and burn data, Receipt Standing for MultiversX wallets) — at https://scriptmasterlabs.com/sml-products
FAQ
What APY do xExchange farms pay? xExchange publishes no official figure. ScriptMasterLabs computes xExchange farm APY from on-chain emissions divided by staked liquidity: 8 of 68 farms carry a computed APY, MEXFARM at 926.00% and EGLDMEXF at 479.95%, measured November 17, 2026. The 8 computable farms are legacy v1.3 programs whose contracts still emit MEX at configured per-block rates while most stakers migrated to v2, so the emission divides over a drained base; every figure is printed next to its staked base and its inputs. 12 farms are stopped and carry 0, and 48 carry no figure, with the reason printed.
Does xExchange publish an official farm APR or APY? No. The MultiversX network API publishes no per-farm APR or APY — verified November 16, 2026 over the full /mex/farms field set — so in ScriptMasterLabs' xExchange Analytics feed the field aprReportedByApi is null on all 68 farm programs. Any APY number for an xExchange farm has to be computed from the chain's own published ingredients; that computation is what ScriptMasterLabs sells, labeled SML-computed wherever it appears.
How does ScriptMasterLabs compute the xExchange farm APY? APY percent = (per-block reward × blocks per year × reward token price in USD) ÷ (farm token supply × farm token price in USD) × 100. The per-block reward and the farm token supply are read from each farm contract's own views through the MultiversX API; prices and the program list come from the network's /mex/farms figures; token decimal counts are read per token, never assumed; blocks per year is 52,596,000, from the chain's official 600 ms round duration read live from the network config. The math is exact integer arithmetic, rounded only at the end, and every figure ships with its inputs so it can be re-derived. Disclosed caveat: realized block production currently runs slightly below the 600 ms round rate, and the annualization uses the protocol round duration — the chain config's own convention.
What does the ScriptMasterLabs xExchange Analytics feed cost, and how is it used? One read costs $0.01 USD-equivalent in MEX (asset MEX-455c57), settled as an x402 v2 exact payment on MultiversX (multiversx:1) through the OMNIGATE facilitator. Call GET or POST https://xexchange.scriptmasterlabs.com/xexchange, receive the payment challenge, settle it, and retry with the payment: the response is one JSON snapshot of all 561 xExchange pairs and all 68 farm programs, each farm carrying its reward-distribution status and its apyComputedBySml field. The feed is also listed in HIVE402, ScriptMasterLabs' machine market of 36,197 endpoints from 2,087 operators, 13,344 of them probe-verified payable, measured November 17, 2026.
Why do 48 of the 68 xExchange farms show no computed APY? Because their contracts publish no per-program emission rate readable from outside, and ScriptMasterLabs does not estimate. All 25 v2 farms distribute rewards as energy-weighted locked-token emission and implement no per-block emission view — the view and 15 further candidate view names all answer 400 on the farm contracts and on the energy factory contract. All 23 metastaking proxies expose no emission schedule of their own; they pass through distributions from underlying farm positions. Those 48 farms carry percent: null with the reason stated in the response.
Is the SML-computed APY a promise of return? No. Each figure is the farm contract's current annualized emission divided by the current staked base at read time, with the inputs printed next to it. Emissions and staked bases both move; the legacy farms with the largest figures have small, drained bases, which is exactly why the base is printed beside every APY. The feed is informational data, read-only: it never stakes, delegates, or moves anyone's funds.
Canonical: https://scriptmasterlabs.com/xexchange-farm-apy
FOLLOW
X: @TimmyCrypto78 — https://x.com/TimmyCrypto78
Instagram: @scriptmasterlabs — https://www.instagram.com/scriptmasterlabs
Threads: @scriptmasterlabs — https://www.threads.net/@scriptmasterlabs
LinkedIn: https://www.linkedin.com/in/timothy-walton-23224052
MY LINKS
🛒 All SML products: https://scriptmasterlabs.com/sml-products
Website: https://scriptmasterlabs.com
Books: https://scriptmasterlabs.com/sml-products#books
Shop: https://shop.scriptmasterlabs.com
Gumroad: https://timwalton.gumroad.com
Whop: https://whop.com/timmy741
Ko-fi: https://ko-fi.com/scriptmaster
Discord: https://discord.gg/jGWDutyVAR
Verdict Protocol: https://verdict.scriptmasterlabs.com
Free VA tools: https://va-ratings.org
Top comments (0)