feat(bridge): add Near Intents provider to quote-latency and bridge-fee benches - #593
Merged
Merged
Conversation
Adds the Near Intents 1Click API provider to both bridge benchmarks. Metrics will start populating once the bridge-monitor harness is redeployed with the nearintents_bridge.go integration shipped on mobula-api side and the NEARINTENTS_API_KEY env var set on Railway. Includes Near Protocol logo (public/logos/near-intents.svg), provider registry entry with longDescription + docs link, and YAML provider entries on both bridge-quote-latency and bridge-fee with the post-#584 avg(...) wrapper on success queries. SEO cohort copy updated to include Near Intents in both benches.
Flotapponnier
added a commit
that referenced
this pull request
Jun 19, 2026
…ee (#593) (#594) Adds the Near Intents 1Click API provider to both bridge benchmarks. Metrics will start populating once the bridge-monitor harness is redeployed with the nearintents_bridge.go integration shipped on mobula-api side and the NEARINTENTS_API_KEY env var set on Railway. Includes Near Protocol logo (public/logos/near-intents.svg), provider registry entry with longDescription + docs link, and YAML provider entries on both bridge-quote-latency and bridge-fee with the post-#584 avg(...) wrapper on success queries. SEO cohort copy updated to include Near Intents in both benches.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds Near Intents (1Click API, NEAR Protocol) as a fifth provider to both bridge benchmarks.
Touched files:
benchmarks/bridge-quote-latency.yml— provider entry + cohort copybenchmarks/bridge-fee.yml— provider entry + cohort copysrc/data/provider-registry.ts— registry entry with longDescription, docs linksrc/lib/logo-manifest.ts— logo registrationpublic/logos/near-intents.svg— Near Protocol logoWhen metrics start flowing
The label
bridge="near-intents"does not exist in Prometheus yet. It will start appearing once:nearintents_bridge.goNEARINTENTS_API_KEYis set on the Railway bridge-monitor serviceUntil then the provider renders as awaiting first run on the page (materialize layer handles this gracefully via the existing draftBenchmark fallback).
Auth scheme used (FYI for the harness PR)
Authorization: Bearer <JWT>works. The X-API-Key header documented in the OpenAPI spec returns 401 in practice. The harness should use Bearer.Live test results with the partner JWT (USDC $50 all 4 routes)
Partner key waives the 10 bps appFee that anonymous calls would pay.