docs(nodes): add node101 to Celo service providers

[girginomer10]

The hole, and the fix

The As a Service directory does not list node101. This change adds a Celo-specific entry with a service link, mainnet support, and Celo Sepolia access on request. It gives developers another commercial provider to evaluate.

What this does NOT do / residual risk

This is a provider directory update. It creates no public RPC endpoint and changes no Celo network configuration. Availability and performance figures below are provider-published service information, not independent benchmarks. Maintainer approval and publication remain pending.

Judgement calls

Keep the entry in the existing provider description, supported-networks list, and Card format. Put package details in this PR description and link the canonical service page from the directory.

Issues

No existing issue is claimed as closed or resolved.

Stacking / conflicts

Branched from the current main branch, independent of my other open PRs. The upstream target file matched the reviewed source, and the node101 duplicate search returned no existing proposal.

Provider information

node101 provides paid Celo RPC services and managed dedicated nodes for application developers, wallets, exchanges, and analytics teams.

Service features

• JSON-RPC access for reading blockchain data and submitting transactions.
• 101 Dashboard for usage, endpoints, performance, and service status. Available on Business, Expert, and Enterprise plans.
• Distributed request handling across multiple nodes for availability and consistent performance.
• 24/7 technical support from the infrastructure team.
• Incident reports covering service disruption impact, cause, and resolution. Available on Business, Expert, and Enterprise plans.
• Managed node operations and real-time infrastructure monitoring through monitor101, with traffic and log tracking.
• Managed infrastructure, node maintenance, monitoring, and API key management across shared plans. Technical support is standard on Starter, advanced on Business, and priority on Expert. Incident tracking is available on Business and Expert.

Available on request

• Celo Sepolia testnet RPC is available on request.
• Archive node services for historical blockchain data are available on request.
• Dedicated deployment options in Türkiye, Europe, and the United States. Türkiye-hosted infrastructure can be scoped for local hosting and regulatory requirements. The deployment region and configuration are agreed during onboarding.
• Additional features and custom configurations may increase the price.

Plans and access

Plan	Monthly price, USD	CUPS	Monthly requests	Published average response time
Starter	$119	250	648M	250 ms
Business	$249	500	1.29B	250 ms
Expert	$499	1,000	2.59B	250 ms
Enterprise	$999	2,000	Unlimited	200 ms

Prices exclude taxes. CUPS means compute units per second, while the monthly quota counts requests. An unlimited monthly quota retains the plan's throughput limit. Response times are published averages, not per-request guarantees.

This is a commercial, closed-source service. No free public RPC, free tier, or free trial is offered. To get started, visit the node101 Celo service page, choose a plan or request a dedicated deployment, and discuss the required network and configuration with the infrastructure team.

Service availability, maintenance, incident handling, and service credits are governed by the applicable Service-Level Agreement.

Verification evidence

• mint broken-links on the submission branch: success no broken links found.
• Ran mint dev and reviewed /tooling/nodes/overview in Chrome, including the node101 description, mainnet/testnet list, and service card.
• Rechecked the provider page, plan qualifications, deployment options, and paid-only access model.
• git diff --check passes. No executable code or dependency change is included.

Checklist

• Scoped Conventional Commits title.
• Provider entry and plan qualifications reviewed against published service information.
• No secrets or customer endpoint URLs added.
• mint broken-links passes on the submission branch.
• Rendered page reviewed locally.
• Submission approved by the node101 representative.

Code tests and mutation tests: N/A for this directory-only change; mutation count 0. Maintainer review and publication remain pending.

[Copilot]

🟡 Changes recommended

The new section introduces an inconsistent “Supported networks” heading casing versus the established “Supported Networks” convention used throughout the page.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Pull request overview

Adds node101 to the “As a Service” node providers directory so developers can evaluate an additional paid Celo RPC / managed node provider, including mainnet support and Celo Sepolia access on request.

Changes:

• Added a new provider section for node101 with a short service description.
• Documented supported networks (Celo Mainnet and Celo Sepolia on request) and added a service link card.

File summaries

File	Description
tooling/nodes/overview.mdx	Adds a new node101 provider entry (description, supported networks list, and service link card) to the node services directory.

Review details

• Files reviewed: 1/1 changed files
• Comments generated: 1
• Review effort level: Lite

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[girginomer10]

Keeping Supported networks in sentence case to follow the current AGENTS.md heading rule, which explicitly requires sentence case for new and rewritten headings. The guidance also says to follow that rule when existing page conventions conflict with it.