Add APIs provider entry for Bitquery

[Yassinesayahlembarek]

Summary

Added APIs data via the provider entry. Provider slug: bitquery-free-ton.

Type of change

• Add data rows
• Update data rows
• Remove data rows
• Schema change (requires linked DBIP)
• Documentation/metadata only

Scope

• Networks affected: global
• Categories affected: apis
• Additional notes (constraints, naming, normalization), additional context / screenshots: Generated via Chain.Love Contributor by @Yassinesayahlembarek.

CSV preview:

bitquery-free-ton,Bitquery,"[""[Website](https://bitquery.io)"",""[Docs](https://docs.bitquery.io/)""]",Developer Plan,Free,Archive,GraphQL,TON,0$,0$,,,,99.9%,,,Telegram Community,FALSE,FALSE,"[""address_stats"",""transaction_logs""]","[""Free Points-based limiting""]",,,,,0x40614e6249b73cd48a9d7c43604ae815abfc4b2e

Links

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

Validation checklist

• I followed the Style Guide and Column Definitions
  • Style Guide: https://github.com/Chain-Love/chain-love/wiki/Style-Guide
  • Column Definitions: https://github.com/Chain-Love/chain-love/wiki
• Rows are placed in the correct folder(s) and CSV(s)
  • networks/<chain>/<category>.csv for chain-scoped entries
  • providers/<category>.csv when the provider/service is chain-agnostic or cross-chain
• No duplicate entries (by provider + chain + relevant key columns)
• CSV formatting: comma-delimited, quote fields as needed, UTF-8, no BOM
• Values match defined types/enums per Column Definitions
• No unintended whitespace, trailing commas, or empty lines

Optional

• Rewards address (for data patching rewards): Not provided
• Twitter (X) post link (for +10% of rewards to this PR): Not provided

[Yassinesayahlembarek]

My wallet
0x40614E6249b73cD48A9d7c43604aE815AbfC4B2e