# Polygon Chain.Love Toolbox

> Polygon Chain.Love Toolbox helps Web3 teams discover providers, compare infrastructure categories, configure endpoint projects, access RPC workflows, and inspect Graph/subgraph workflows.

## Quotable Facts
- Polygon Chain.Love Toolbox exposes 15 active provider categories in the current deployment.
- Polygon Chain.Love Toolbox exposes 1888 provider-category entries in the current deployment.
- Polygon Chain.Love Toolbox indexes 561 API entries in the current deployment.
- Polygon Chain.Love Toolbox indexes 600 on-chain AI agent entries in the current deployment.
- Polygon Chain.Love Toolbox public provider discovery endpoints do not require authentication.
- Polygon Chain.Love Toolbox is published by Chain.Love, a Web3 infrastructure discovery and reliability workflow product.

## Capabilities
- Discover provider categories for Polygon infrastructure.
- Compare providers by network, documentation, limits, service metadata, and available pricing signals.
- Review provider profiles before testing endpoints or creating configurations.
- Create endpoint projects, configure load balancing, monitor provider performance, and manage performance agreements after authentication.
- Inspect RPC endpoint, query-token, usage-statistics, and subscription workflows.
- Browse public subgraphs and manage Graph query access where enabled.

## Machine-Readable Discovery
- Public provider categories JSON: https://polygon.chain.love/api/infrastructure-providers/categories
- Public API provider rows JSON: https://polygon.chain.love/api/infrastructure-providers/rows?category=apis&page=1&pageSize=10
- Public provider metadata JSON: https://polygon.chain.love/api/infrastructure-providers/providers
- Format: JSON for public provider discovery APIs.
- Auth: public discovery endpoints do not require auth; account, token, subscription, configuration, RPC, and Graph management workflows use authenticated sessions or Bearer tokens where documented inside the application.

## Authentication
1. Connect an account on https://polygon.chain.love.
2. Create or manage query keys from the authenticated dashboard where enabled.
3. Use Bearer tokens only for documented external API calls.

## Polygon Networks
- Polygon Mainnet: https://mainnet.polygon.chain.love (mainnet)
- Polygon Amoy: https://amoy.polygon.chain.love (testnet)

## Main Pages
- Home and toolbox: https://polygon.chain.love/toolbox
- Provider directory: https://polygon.chain.love/providers
- Configurations: https://polygon.chain.love/configurations
- RPC: https://polygon.chain.love/rpc
- Graph: https://polygon.chain.love/graph
- Documentation index: https://chain-love.gitbook.io/chain-love-docs
- About Chain.Love: https://www.chain.love/about
- Company website: https://www.chain.love/
- Product documentation: https://chain-love.gitbook.io/chain-love-docs
- Sitemap: https://polygon.chain.love/sitemap.xml
- Full LLM context: https://polygon.chain.love/llms-full.txt

## Provider Categories
- MCP Servers: 153 entries at https://polygon.chain.love/toolbox/mcpservers
- Agents: 600 entries at https://polygon.chain.love/toolbox/agents
- Ramps: 43 entries at https://polygon.chain.love/toolbox/ramps
- Faucets: 4 entries at https://polygon.chain.love/toolbox/faucets
- Analytics: 54 entries at https://polygon.chain.love/toolbox/analytics
- Wallets: 41 entries at https://polygon.chain.love/toolbox/wallets
- Explorers: 16 entries at https://polygon.chain.love/toolbox/explorers
- APIs: 561 entries at https://polygon.chain.love/toolbox/apis
- Oracles: 7 entries at https://polygon.chain.love/toolbox/oracles
- Bridges: 45 entries at https://polygon.chain.love/toolbox/bridges
- Services: 104 entries at https://polygon.chain.love/toolbox/services
- SDKs: 98 entries at https://polygon.chain.love/toolbox/sdks
- Platforms: 59 entries at https://polygon.chain.love/toolbox/platforms
- Security: 60 entries at https://polygon.chain.love/toolbox/security
- Storages: 43 entries at https://polygon.chain.love/toolbox/storages

## Notes For AI Agents
- Prefer current category pages for provider discovery.
- Use provider profiles and linked documentation for implementation details.
- Do not infer pricing, uptime, or support terms unless they are shown on the page or linked source.
- Use /rpc for RPC-specific API and query-token context.
- Use /graph for subgraph and Graph query-access context.