Skip to content

MEV Intelligence#174

Open
ValoremFoundation wants to merge 1 commit into
coinbase:mainfrom
ValoremFoundation:add-advalorem-mev-intelligence
Open

MEV Intelligence#174
ValoremFoundation wants to merge 1 commit into
coinbase:mainfrom
ValoremFoundation:add-advalorem-mev-intelligence

Conversation

@ValoremFoundation
Copy link
Copy Markdown

This PR adds MEV Intelligence to the x402 ecosystem under Services/Endpoints.

What it is
A live, paid x402 service that exposes real-time MEV intelligence to AI agents and quant systems:

GET /intelligence/feed — $0.10 — risk-enriched MEV opportunity stream

GET /intelligence/searcher-leaderboard — $0.25 — landed-bundle searcher rankings

GET /intelligence/builder-recommendation — $0.25 — builder routing recommendations from telemetry

GET /intelligence/liquidation-waves — $0.50 — oracle deltas + borrower health-factor distribution

All endpoints accept USDC on Base via the exact scheme. Free preview mirrors are exposed at /preview/* for evaluation.

Why it's useful to the ecosystem
The service sits on top of a real Ethereum L1 + Base L2 liquidation infrastructure with sub-100ms seen→priced latency. It's an example of an x402-monetized intelligence layer that gives AI agents forward-looking signals (what's about to happen on-chain) rather than just historical data — useful as a reference for any agent system that wants to act before opportunities are consumed.

Compliance with category requirements (Services/Endpoints)
✅ Working mainnet integration (live on Base)

✅ API documentation: OpenAPI 3.1 at https://mev.advalorem.io/intelligence/openapi

✅ 100% uptime since deploy (PM2, 0 restarts)

✅ Discoverable via discoverable: true bazaar metadata on each route

Files added
typescript/site/app/ecosystem/partners-data/advalorem-mev-intelligence/metadata.json

typescript/site/public/logos/advalorem.png (1024×1024 placeholder; happy to swap for a final brand asset on request)

Live URL: https://mev.advalorem.io/intelligence/openapi

@cb-heimdall
Copy link
Copy Markdown

cb-heimdall commented May 19, 2026

🟡 Heimdall Review Status

Requirement Status More Info
Reviews 🟡 0/1
Denominator calculation
Show calculation
1 if user is bot 0
1 if user is external 0
2 if repo is sensitive 0
From .codeflow.yml 1
Additional review requirements
Show calculation
Max 0
0
From CODEOWNERS 0
Global minimum 0
Max 1
1
1 if commit is unverified 1
Sum 2

@ValoremFoundation ValoremFoundation force-pushed the add-advalorem-mev-intelligence branch from 09bd4a2 to dd138f6 Compare May 19, 2026 11:53
@TateLyman
Copy link
Copy Markdown

Ran a no-payment external pass using x402-surface-check@0.2.33 against the public OpenAPI surface.

Repro:

npx --yes x402-surface-check@0.2.33 \
  https://mev.advalorem.io/intelligence/openapi \
  --limit 12 \
  --origin https://mev.advalorem.io

curl -i -X OPTIONS 'https://mev.advalorem.io/intelligence/feed?limit=50' \
  -H 'Origin: https://mev.advalorem.io' \
  -H 'Access-Control-Request-Method: GET' \
  -H 'Access-Control-Request-Headers: X-PAYMENT'

What looks good:

  • OpenAPI is public and machine-readable at the listed URL.
  • The four paid /intelligence/* GET routes return 402 before data when no payment header is sent.
  • Observed prices match the PR/OpenAPI: $0.10, $0.25, $0.25, $0.50.
  • The PAYMENT-REQUIRED header carries a Base mainnet USDC exact-payment challenge with the documented recipient.
  • The /preview/* routes return free, rate-limited preview data as documented, so I did not treat those as paid-route bypasses.

Patch notes before merge:

  • P1: browser preflight currently returns 404 and does not allow X-PAYMENT; browser-based agents will not be able to retry with a payment header from the listed origin.
  • P1: actual 402 responses do not include Access-Control-Allow-Origin, so browser clients cannot read the payment requirements even if the challenge is present in the response headers.
  • P2: each accepts[] leg should repeat the exact canonical paid resource URL, not only the top-level challenge resource, so spend maps and replay/resource binding can be verified per payment option.
  • P3: add explicit Cache-Control: no-store on paid 402 challenges and paid responses. The current paid and preview responses did not expose a cache policy in this pass.

I did not send payment headers, sign requests, or attempt paid calls.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

3 participants