Repository navigation
chore: remove the retired Surf integration - #502
Merged
Merged
Conversation
BlockRun retired the Surf data API on 2026-09-06; every /api/v1/surf/* path now answers 410 endpoint_retired. ClawRouter still shipped a skill, a proxy whitelist entry, telemetry branches, README/skill sections and a plugin description that sent agents at it. - Delete skills/surf/ (shipped via package.json "skills" and the plugin manifest's "./skills" directory, so removing the folder drops it from both). - proxy.ts: drop surf from the paid partner-prefix regex, the isSurf label/telemetry branches (tier SURF, service surf), and the 404 hint's prefix list. Wallet mode now refuses /v1/surf/* locally with unsupported_endpoint (nothing signed, nothing sent); API-key mode forwards it through the account passthrough and relays the gateway's 410. - openclaw.plugin.json: drop the Surf clause and the unguarded hand-typed "82 models" count (the guarded 84% savings figure stays). - skills/clawrouter/SKILL.md: drop the Surf section and its seven triggers. - README: drop the "Crypto Data (Surf)" section and the Surf mention in the API-key coverage list; api-key.ts 404 hint likewise. - Tests: replace the regex-mirror proxy.surf-routing.test.ts with a behavioural proxy.surf-retired.test.ts (wallet: local 404, gateway never hit; key: 410 relayed, no payment header); drop the surf rows from the account-services forwarding table.
|
Note Currently processing new changes in this PR. This may take a few minutes, please wait... ⚙️ Run configuration
📒 Files selected for processing: 9
✨ Finishing Touches
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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
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.
BlockRun retired the Surf data API on 2026-09-06.
GET https://blockrun.ai/api/v1/surf/*now returns410 endpoint_retiredwithretired_on: 2026-09-06(re-verified with curl today). #501 dropped Surf from the clawrouter skill's description; this removes the rest.Removed / changed
skills/surf/SKILL.md: deleted. Skills ship as the wholeskills/directory (package.jsonfilesandopenclaw.plugin.json"skills": ["./skills"]), so deleting the folder removes it from both. No other index lists skills by name.src/proxy.ts:surfis out of the paid partner-prefix regex, theisSurflabel and telemetry branches (tier: "SURF",service: "surf") are gone, and so issurfin theunsupported_endpointhint's prefix list. Nothing else read the SURF tier or the surf service.openclaw.plugin.json: the Surf clause is gone, and so is the hand-typed "82 models". No test guards that count;brand-numbers.test.tsonly guards theNN% cost savingsfigure, which stays.skills/clawrouter/SKILL.md: removed the "Crypto Data (Surf)" section and its seven Surf-only triggers (blockrun surf,surf crypto api,on-chain sql query,clickhouse onchain,wallet labels api,crypto mindshare,crypto news api).api-key.ts404 hint.What
/v1/surf/*does now404 unsupported_endpoint. Nothing reaches the gateway and nothing is signed.410 endpoint_retired, including itsalternativeshint.There's no special-case code. The path just falls through to the handling every other non-partner path already gets.
Tests
src/proxy.surf-routing.test.tsis replaced bysrc/proxy.surf-retired.test.ts. The old file was a copy of the regex. The new one is a behavioural test against a stub gateway. In wallet mode it checks for a local 404 and that the gateway is never hit. In key mode it checks that the 410 is relayed and no payment header is sent. Againstorigin/main'sproxy.tsthe two wallet cases fail, so the test does catch the change.proxy.api-key-services.test.tsforwarding table.proxy.solana-batch.test.tshit a 30s timeout under load. Run on its own it passed 6/6, and a full rerun was all green.npm run lint,npm run typecheck, prettier on the touched files, andnode scripts/sync-brand-numbers.mjs --checkall pass.Dated CHANGELOG history is left alone. This repo has no "Unreleased" section; its CHANGELOG entries are written at release time, so the next release entry should mention this removal.