-
Notifications
You must be signed in to change notification settings - Fork 54
Common Columns
Unique identifier for the entry.
Blank: No
Format: text (kebab-case)
Examples: quicknode-mainnet-growth-archive, flare-mainnet-public.
Tips:
- Must be unique within a file.
- Include provider + chain for clarity.
- Can't contain spaces
Links to useful resources (website, docs, dashboards).
Blank: Yes
Format: JSON list
Examples: ["[Docs](https://docs.quicknode.com/)"]
Tips:
- Max 2 buttons.
- Use short labels: Docs, Website, GitHub, Buy.
- Do not repeat labels for the same entity
- Link directly to the most relevant page (e.g., provider page for that network).
-
Public endpoints -
Send Requestsbutton with direct link. -
Enterprise provers -
Contact Salesbutton with contact form link.
Search tags.
Blank: Yes
Format: JSON list
Examples: ["JavaScript","Testing"]
Marks whether a provider is featured.
Blank: No
Format: TRUE/FALSE (uppercase)
Examples: TRUE, FALSE
Tips:
- Default is
FALSEunless explicitly approved.
Display name of the provider company/organization.
Blank: No
Format: text
Examples: QuickNode, Alchemy, Dune
Tips:
- Use canonical official provider name.
- Keep it consistent across all categories/files.
- Do not put offer/product names here.
Offer name or offer reference for inheritance.
Blank: No (except provider-only metadata tables)
Format: text or !offer:<slug> reference
Examples: Growth, Bundler, !offer:quicknode-growth
Tips:
- Use plain offer name in
references/offers/<category>.csv. - Use
!offer:<slug>in listings when inheriting from references. - Keep offer naming stable to avoid accidental duplicates.
Service target chain/scope.
Blank: No
Format: text
Examples: mainnet, testnet
Tips:
- Use common names like
mainnet,testnet,sepolia. - Default to
mainnet/testnetunless a chain name (e.g.,sepolia) is more specific or widely used. - Do not put this in
""(quotes) unless strictly necessary. - Always lowercase in all CSV files.
Pricing model.
Blank: Yes
Format: text
Examples: $0, $X/month, Custom
Tips:
- Write $0 for free access.
- Keep it short.
Plan/tier category according to Chain.Love's classification.
Blank: No
Format: text
Examples:
-
Free- no payments needed; -
One-time payment- pay once, use forever, "lifetime license"; -
Dedicated- pay monthly, not depending on usage; -
Pay-As-You-Go- your payment depends on your usage and does not require you to change plan when usage spikes; -
Tiered- your payment depends on your usage, so you have to choose plan that suits your needs in advance; -
Enterprise- custom pricing, usually requires "Contact us" or "Talk to sales" to use this plan.
Tips:
- Pick from example plans; if none match, choose closest or submit DBIP (Database Improvement Proposal) issue to propose adding new option.
Plan/tier name according to provider's specification. Should be empty if the same as planType
Blank: Yes
Format: text
Examples: Developer, Team, Growth, etc.
Trial available.
Blank: No
Format: TRUE/FALSE