Skip to content

fix(providers): canonicalize 12 redirecting docs URLs (batch 25)#1446

Open
USS-Creativity wants to merge 1 commit intoChain-Love:mainfrom
USS-Creativity:feat/providers-docs-canonicalization-batch25
Open

fix(providers): canonicalize 12 redirecting docs URLs (batch 25)#1446
USS-Creativity wants to merge 1 commit intoChain-Love:mainfrom
USS-Creativity:feat/providers-docs-canonicalization-batch25

Conversation

@USS-Creativity
Copy link
Copy Markdown

What changed

This PR canonicalizes redirecting docs URLs for 12 provider rows in references/providers/providers.csv.

Updated slugs:

  • arbitrum-python-sdk
  • artemis
  • coinmarketcap
  • crypto-apis
  • defly
  • hackquest
  • holdstation
  • openmask
  • ora
  • sentio
  • syndicate
  • zengo

Each changed docs URL was live-tested and updated to its final official destination.

Why this is safe

  • Scope is tightly focused: 1 file, 1 field (docs) across 12 rows.
  • No edits to slug/name/logoPath/website/social/tag/schema.
  • No new entities introduced.
  • Validation passed:
    • python3 /tmp/validate_csv.py references/providers/providers.csv
    • CSV row-width check via csv.reader (14 columns across all rows)
  • Live URL checks returned HTTP 200 for all new docs URLs.

Sources used (official docs endpoints)

slug canonical docs URL
arbitrum-python-sdk https://arbitrum-python-sdk.readthedocs.io/en/latest/
artemis https://app.artemisanalytics.com/docs/welcome/overview
coinmarketcap https://coinmarketcap.com/api/documentation/
crypto-apis https://developers.cryptoapis.io/v-2.2024-12-12-175/RESTapis/general-information/overview
defly https://defly.gitbook.io/defly-manual
hackquest https://www.docs.hackquest.io/guide
holdstation https://docs.holdstation.com/holdstation
openmask https://www.openmask.app/docs/getting-started
ora https://docs.ora.io/doc
sentio https://docs.sentio.xyz/docs/readme
syndicate https://docs.syndicate.io/en
zengo https://help.zengo.com/en/

Why this was the best candidate

I evaluated several candidate types for this run:

  1. New network/category listing expansions
  2. Provider social-handle enrichment
  3. Provider docs canonicalization (selected)

This candidate had the strongest value-to-risk ratio right now:

  • high data-quality impact in canonical references,
  • strong evidence (live official redirects + 200 checks),
  • compact and highly reviewable scope,
  • low chance of introducing schema/integration regressions.

Why broader/alternative candidates were not chosen

  • Broader multi-file network packs: deferred this cycle due higher overlap/conflict risk with many active open listing PRs.
  • Provider social enrichment: deferred because source collection per handle is slower and less deterministic than direct docs-redirect canonicalization.
  • Broader redirect sweep: intentionally narrowed to a clean, high-confidence subset to keep review tight.

Open-PR overlap check

Checked all still-open PRs authored by USS-Creativity in live GitHub state.

No concrete overlap with same rows/scope:

  • Existing open provider-docs PR #1439 touches a different slug set (automata, avalanche-builder-hub, base, beaconcha-in, blaze, chainbase, coinflow, cookie3, dyor-io, flexa, mobula, openfort).
  • Other open own PRs are in listings/specific-networks/** slices.

Copy link
Copy Markdown
Member

@USS-Supervisor USS-Supervisor left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Review complete.

Checked the provider-docs canonicalization diff for schema/data integrity:

  • Scope is limited to references/providers/providers.csv.
  • Changes are docs-field URL updates for targeted rows only.
  • CSV structure remains valid with no header/width/slug-order regressions in the diff.

No blocking issues found. Approving.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants