Ramp Network is listed on Algorand and Mercuryo on Filecoin, but neither sells that network's asset

[EazyHood]

What is wrong

Two ramp listings claim a network whose native asset the provider does not sell:

listing	provider's own asset list	result
listings/specific-networks/algorand/ramps.csv → ramp-network	Ramp Network lists no Algorand asset	nothing to buy on Algorand
listings/specific-networks/filecoin/ramps.csv → mercuryo	Mercuryo lists no FIL	nothing to buy on Filecoin

The contribution rules list "providers that do not support the claimed network" among the errors that cost rewards, and a buyer following either row lands on a widget without that asset. Open PR #2957 would also add a Buy button to the Algorand row pointing at ramp.network/buy?defaultAsset=ALGO, which has no ALGO to load.

How this was checked

Two instruments per provider, each tested with a positive control on an asset the provider does sell:

Ramp Network — no Algorand

1. GET https://api.ramp.network/api/host-api/assets returns 213 assets on 53 chains. FILECOIN is among the chains (control: FIL is present); ALGORAND is not, and no asset has the symbol ALGO.
2. GET https://api.ramp.network/api/host-api/v3/assets and https://docs.ramp.network/supported-assets contain no ALGO and no "Algorand" either.

Mercuryo — no Filecoin

1. GET https://api.mercuryo.io/v1.6/lib/currencies lists 54 cryptocurrencies. ALGO is there with network ALGORAND (control), and FIL is not.
2. GET https://api.mercuryo.io/v1.6/public/currencies-buy, its public list of buyable assets, includes ALGO and not FIL.

For comparison, the other rows on the same two files that I checked with the same method hold up: MoonPay lists both algo and fil, Ramp Network lists FIL, and Mercuryo lists ALGO.

What I'd suggest

Remove both rows. I haven't sent that as a pull request because #2951 and #2957 already edit these files and #2957 edits the ramp-network row itself, so a removal there would only create a conflict. If you'd rather have the patch, I'll open it once those two land.