Add Validation Cloud API listings to Avalanche network

[augustodluis]

Summary

Add Validation Cloud as an API/RPC provider listing on the Avalanche network. Six canonical !offer: references to existing Validation Cloud offers (free, scale, private), Avalanche mainnet. No new offers or providers created.

Type of change

• Add data rows
• Update data rows
• Remove data rows
• Schema change
• Documentation/metadata only

Scope

• Networks affected: avalanche
• Categories affected: apis
• Additional notes, additional context / screenshots: 6 rows added (174 cells, under the 200-cell ceiling). Slugs kept in ascending alphabetical order. Validation Cloud supports Avalanche via its Node API — listed on its official network hub: https://www.validationcloud.io/network

Links

• Related issue(s)/ DB Improvement Proposal (if schema-related): N/A

Validation checklist

• I followed the Style Guide and Column Definitions. I'm aware of what is !provider syntax, and that entities in /networks sub-folders inherits records from /providers folder
• I personally opened and verified every new link I'm adding. I can confirm, that all the links I'm adding are valid.
• If I added new entries - I personally confirmed that the provider I'm adding (modifying) currently supports the adjusted network(s). I've also verified that value in every cell I'm changing is correct according to my best understanding
• This PR is not a blind AI-generated submission

Optional

• Rewards address (for data patching rewards): 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: Required CI passed, the current-cycle link-check completed successfully, and the six Avalanche API listing rows are structurally consistent with the existing dataset.
Findings: None. Verified the added rows keep the expected 29-column CSV shape, use existing canonical !offer:validation-cloud-* references, introduce no duplicate Avalanche API listing slugs, target the existing mainnet chain/logo, and the cited Validation Cloud links are reachable.
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.

Validation Cloud looks valid as an Avalanche API/RPC provider.

Validation Cloud docs include Avalanche API methods, so the recent-state entries look acceptable:

• validation-cloud-mainnet-free-recent-state
• validation-cloud-mainnet-private-recent-state
• validation-cloud-mainnet-scale-recent-state

However, I would not approve the full-archive entries yet:

• validation-cloud-mainnet-free-full-archive
• validation-cloud-mainnet-private-full-archive
• validation-cloud-mainnet-scale-full-archive

Validation Cloud’s general docs say they aim to provide archive/full-history access on each supported blockchain, but they also say each chain overview page should show whether archive access is currently available. I could not confirm archive/full-history access for Avalanche specifically.

Please provide an Avalanche-specific source showing archive/full-history access is currently available, or remove/change the full-archive rows to recent-state.

Also, please use the docs domain:

https://docs.validationcloud.io/v1

instead of:

https://www.validationcloud.io/docs

[augustodluis]

Thanks @eugene17kotov! Same fix:

Removed the three full-archive entries (kept recent-state: free, private, scale).
Updated the documentation links to https://docs.validationcloud.io/v1.

[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 Avalanche Validation Cloud API listing now keeps only the recent-state rows requested in review, uses the docs-domain action button, and preserves the listing schema. Required validation is passing and a fresh current-cycle link-check completed successfully.

Findings: None. The added rows keep valid CSV width, use existing !offer:validation-cloud-* refs, avoid duplicate Avalanche API slugs, and target the existing mainnet chain/logo.
Confidence: HIGH

[USS-Compensator]

Suggested compensation for PR #1800 by @augustodluis

This is a suggested compensation only, based on the current interpretation of the reward program. Final compensation may be altered by a human reviewer.

Basis checked:

• Discussion #41 first post: 0.06 USDC per improved non-null cell; current bounty networks are Arbitrum, Algorand, Ethereum, Filecoin, and Somnia; Base and Avalanche are removed from the bounty list from July 1, 2026.
• Discussion #839 latest weekly digest: apis multiplier x0.61.
• Deterministic command: python3 compensator.py --repo Chain-Love/chain-love --pr 1800 --no-header --key-config compensator.key-config.json --json.

Calculation:

• Raw deterministic count: 12 non-null billable cells in listings/specific-networks/avalanche/apis.csv.
• Eligible current-network cells: 0.
• Excluded: Avalanche is outside the current bounty network list after the July 1, 2026 removal.
• 200-cell cap: not reached.
• Quality gateway deduction: not applied because the network eligibility filter already reduces the suggested compensation to zero.
• Twitter bonus: none found.

Final suggested compensation: 0.00 USDC.