Add Blockdaemon API listings to Avalanche network

[augustodluis]

Summary

Add Blockdaemon as an API/RPC provider listing on the Avalanche network. Six canonical !offer: references to existing Blockdaemon offers, Avalanche mainnet. No new offers or providers created.

Type of change

• Add data rows

Scope

• Networks affected: avalanche
• Categories affected: apis
• Additional notes: 6 rows added (174 cells, under the 200-cell ceiling). Alphabetical order verified (between ankr-* and blockeden-*). Blockdaemon officially supports Avalanche — https://www.blockdaemon.com/protocols/avalanche and https://docs.blockdaemon.com/reference/avalanche-methods-rpc-api

Validation checklist

• I followed the Style Guide and Column Definitions...
• I personally opened and verified every new link I'm adding...
• I personally confirmed the provider currently supports the adjusted network(s)...
• This PR is not a blind AI-generated submission

Optional

• Rewards address: 0x1506B57B83C7cd1c9809225496dC0857cF8ed80c

[github-actions]

Summary

Status	Count
🔍 Total	2
✅ Successful	2
⏳ Timeouts	0
🔀 Redirected	0
👻 Excluded	0
❓ Unknown	0
🚫 Errors	0
⛔ Unsupported	0

Full Github Actions output

[USS-Supervisor]

Verdict: APPROVE
Risk: LOW
Summary: The PR adds six Avalanche mainnet API listings that reference existing Blockdaemon canonical API offers. Required CI is passing and the current review-cycle link-check completed successfully.
Findings: None.
Confidence: HIGH

[USS-Supervisor]

Hi @eugene17kotov, this PR has passing required checks and has been waiting more than 3 days since the last review update. Could you take a look when you have a chance?

[USS-Supervisor]

Hi @eugene17kotov - friendly follow-up on this stale PR. Required CI is still passing and I do not see a creator-side blocker, so this remains ready for reviewer action. Could you take a look when you have a chance?

[USS-Supervisor]

Hi @eugene17kotov - friendly follow-up on this stale PR. Required CI is passing and I do not see a current creator-side blocker, so this is still waiting on reviewer action. Could you please take a look when you have a chance?

[USS-Supervisor]

Hi @eugene17kotov - friendly follow-up on this stale PR. Required CI is passing and I do not see a current creator-side blocker, so this is still waiting on reviewer action. Could you please take a look when you have a chance?

[eugene17kotov]

@augustodluis
Thanks for the PR

Blockdaemon looks valid as an Avalanche API/RPC provider.

Avalanche support is confirmed by Blockdaemon’s Avalanche protocol page and Avalanche RPC API docs. Avalanche Builder Hub also lists Blockdaemon as an infrastructure/API provider for Avalanche.

I would keep the recent-state entries:

• blockdaemon-mainnet-dedicated-recent-state
• blockdaemon-mainnet-enterprise-recent-state
• blockdaemon-mainnet-free-recent-state
• blockdaemon-mainnet-growth-recent-state
• blockdaemon-mainnet-starter-recent-state

However, I would not approve this entry yet:

• blockdaemon-mainnet-free-full-archive

Blockdaemon has historical/archive data capabilities, but I could not confirm that the Free plan includes full archive access for Avalanche specifically. Please provide a source confirming free full-archive support for Avalanche, or change/remove this row.

[augustodluis]

Thanks @eugene17kotov! You're right — I couldn't confirm free-tier full-archive for Avalanche either. I've removed blockdaemon-mainnet-free-full-archive, keeping the five recent-state entries (dedicated, enterprise, free, growth, starter).